 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Medium transport flight crew reported that a special company eat departure procedure conflicts with ATC expectations.
| Attributes | |
| ACN | 1351908 |
| Time | |
| Date | 201604 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | EAT.Airport |
| State Reference | WA |
| Aircraft 1 | |
| Make Model Name | Medium Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural FAR Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
[My company has a restriction] that says; when departing runway 30 in eat; we are not authorized to use the [obstacle departure procedure] due to the departure end of runway 30 being shortened. Instead; we are required to fly our engine inoperative turn procedure under a VFR climb clearance. Today; we obtained our IFR clearance to depart eat runway 30 and requested a VFR climb to the eat VOR and we were going to fly our turn procedure. The controller replied 'I cannot approve or deny that'. We were a little confused; and again told the controller we want a VFR climb to the eat VOR and we're going to fly our turn procedure. The controller again replied 'I cannot approve or deny that'. Since we had our clearance to depart; and informed the controller of our intentions multiple times; we departed and flew the turn procedure. When we contacted the controller again after departure; he told us we are not on course; and need to fly the published departure procedure when departing. Nothing else happened; but obviously there is a huge disconnect between our company procedure and ATC's expectations. ATC is not aware or on the same page as us regarding our company procedures for eat runway 30 departures.
Original NASA ASRS Text
Title: Medium transport flight crew reported that a special company EAT departure procedure conflicts with ATC expectations.
Narrative: [My company has a restriction] that says; when departing runway 30 in EAT; we are not authorized to use the [Obstacle Departure Procedure] due to the departure end of runway 30 being shortened. Instead; we are required to fly our engine inoperative turn procedure under a VFR climb clearance. Today; we obtained our IFR clearance to depart EAT runway 30 and requested a VFR climb to the EAT VOR and we were going to fly our turn procedure. The controller replied 'I cannot approve or deny that'. We were a little confused; and again told the controller we want a VFR climb to the EAT VOR and we're going to fly our turn procedure. The controller again replied 'I cannot approve or deny that'. Since we had our clearance to depart; and informed the controller of our intentions multiple times; we departed and flew the turn procedure. When we contacted the controller again after departure; he told us we are not on course; and need to fly the published departure procedure when departing. Nothing else happened; but obviously there is a huge disconnect between our company procedure and ATC's expectations. ATC is not aware or on the same page as us regarding our company procedures for EAT runway 30 departures.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.