37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1721373 |
Time | |
Date | 202001 |
Place | |
Locale Reference | OEJD.ARTCC |
State Reference | FO |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb Parked |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
Person 2 | |
Function | First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Unable to obtain clearance from departure airport in doha; qatar as flight planned for ZZZZ1 due to saudi refusing our filed route. Doha relays the 'preferred' routing over the restricted gulf region. Dispatch unable to produce a [flight plan] with the preferred routing due to the NOTAM and performance engineering having more or less blacked out those specific routes in the software. Dispatch escalated and involves some of the duty pilots and managers while also speaking directly with saudi; bahrain; and doha. Dispatch is able to refile us only by free text for the preferred route and ATC accepts the refiling. We obtain clearance and launch to ZZZZ1 without a valid signed [flight plan] in hand because there is no other possible way to do it. Dispatch can't even generate a new top sheet to send via ACARS for fuel planning purposes because of the block in the software. Thinking outside the box is the order of the day. After departure; doha vectors us off route straight toward iran due to traffic congestion and says to expect to remain on that heading for 4 minutes. That time frame will put us well into tehran. I inform doha my intentions if that is what they expect to be their plan while also trying to mitigate that threat with tehran ADIZ of which tehran will not answer any radio calls. We initiate min clean speed at FL230 and prepare to declare mayday if necessary at a specific point to justify a turn away from iran. Min clean is approved and we are issued small step climbs higher. We are shortly turned back onto our route ultimately placing us within 10 nm of tehran. Transferred to next sector and scolded for still being filed on the wrong route even though it was the preferred route relayed to us on the ground by doha. Rerouted differently again. Finally made it to FL360; normal speed; over the gulf for the entire flight; at least we are going away from tehran. Given the latest in the gulf region; the guideline notams; the FAA clarifications issued; and exceptions granted; you all need to be aware that ultimately saudi is going to be in control of their airspace regardless of what the USA FAA says; that while showing the FAA we at [company] are mitigating the threat by restricting the software from planning anything over the gulf; that alone presents a caveat of having to decide whether or not to launch without a valid [flight plan] in hand by the PIC and the dispatcher when saudi refuses to approve a clearance as filed.
Original NASA ASRS Text
Title: Air carrier flight crew reported being vectored off route toward Tehran ADIZ; placing the flight at risk for penetrating the restricted airspace.
Narrative: Unable to obtain clearance from departure airport in Doha; Qatar as flight planned for ZZZZ1 due to Saudi refusing our filed route. Doha relays the 'preferred' routing over the restricted gulf region. Dispatch unable to produce a [flight plan] with the preferred routing due to the NOTAM and performance engineering having more or less blacked out those specific routes in the software. Dispatch escalated and involves some of the duty pilots and managers while also speaking directly with Saudi; Bahrain; and Doha. Dispatch is able to refile us only by free text for the preferred route and ATC accepts the refiling. We obtain clearance and launch to ZZZZ1 without a valid signed [flight plan] in hand because there is no other possible way to do it. Dispatch can't even generate a new top sheet to send via ACARS for fuel planning purposes because of the block in the software. Thinking outside the box is the order of the day. After departure; Doha vectors us off route straight toward Iran due to traffic congestion and says to expect to remain on that heading for 4 minutes. That time frame will put us well into Tehran. I inform Doha my intentions if that is what they expect to be their plan while also trying to mitigate that threat with Tehran ADIZ of which Tehran will not answer any radio calls. We initiate min clean speed at FL230 and prepare to declare MayDay if necessary at a specific point to justify a turn away from Iran. Min clean is approved and we are issued small step climbs higher. We are shortly turned back onto our route ultimately placing us within 10 nm of Tehran. Transferred to next sector and scolded for still being filed on the wrong route even though it was the preferred route relayed to us on the ground by Doha. Rerouted differently again. Finally made it to FL360; normal speed; over the gulf for the entire flight; at least we are going away from Tehran. Given the latest in the gulf region; the guideline NOTAMs; the FAA clarifications issued; and exceptions granted; you all need to be aware that ultimately Saudi is going to be in control of their airspace regardless of what the USA FAA says; that while showing the FAA we at [Company] are mitigating the threat by restricting the software from planning anything over the gulf; that alone presents a caveat of having to decide whether or not to launch without a valid [flight plan] in hand by the PIC and the Dispatcher when Saudi refuses to approve a clearance as filed.
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.