37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1329436 |
Time | |
Date | 201602 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | DCA.Airport |
State Reference | DC |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Dispatcher |
Qualification | Dispatch Dispatcher |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Other / Unknown Inflight Event / Encounter Fuel Issue Inflight Event / Encounter Weather / Turbulence |
Narrative:
Although the original alternate selected for this flight was ric; I decided for operational considerations to change the alternate to bwi when the flight crew advised me that they were diverting to ric due to IMC/tailwind conditions at [the original destination]. Crew replied that ATC had advised them on numerous occasions that bwi was not accepting any diversions. I asked the ATC coordinator to call ATC and ask them why they would not allow my flight to divert to bwi. He was told by bwi ATC tower that the airport was open; and they would accept any of our flights. After PIC maintained that ATC would not let him divert to bwi; the ATC coordinator called dc center who advised him that there was some miscommunication between the controller and the PIC. Controller allegedly thought the flight wanted to divert to dca not bwi. After multiple ACARS exchanges with the crew relating to this matter; captain informed me that he was diverting to his original alternate ric. By that time he was committed anyway as he was already halfway there. After the flight landed; captain called me to explain why he could not go to bwi. I informed him of the 'miscommunication' issue ATC was claiming. Captain proceeded to tell me that I was given the wrong information. He confirmed that ATC informed all flights holding for dca at three different times that diversions to bwi were not allowed. ATC was clearly adamant about it. The event occurred because ATC was overstepping its authority. If an airport is open to landings; as confirmed by bwi ATC tower; I do not see why ATC center would keep any flight from diverting to that airport. Why do we need dispatchers if ATC steps in and takes over operational control whenever they feel like it? Flight landed in ric with only 3900 lbs of fuel on board; which is below min dispatch for [our carrier]. This was due to the confusing and conflicting information given by ATC; followed by their decision to send the flight to ric instead of bwi.ATC should be briefed on the scope of their authority and be exposed to the regulations outlined in far 121.533 (operational control). I do not believe they have a full understanding of our responsibilities as dispatchers. This is the second such incident in recent weeks; and both occurred in dc center airspace.
Original NASA ASRS Text
Title: Dispatcher reported confusion with ATC when a flight needed to divert; but ATC would not allow the aircraft to divert to the airport the Dispatcher had chosen.
Narrative: Although the original alternate selected for this flight was RIC; I decided for operational considerations to change the alternate to BWI when the flight crew advised me that they were diverting to RIC due to IMC/tailwind conditions at [the original destination]. Crew replied that ATC had advised them on numerous occasions that BWI was not accepting any diversions. I asked the ATC coordinator to call ATC and ask them why they would not allow my flight to divert to BWI. He was told by BWI ATC Tower that the airport was open; and they would accept any of our flights. After PIC maintained that ATC would not let him divert to BWI; the ATC coordinator called DC Center who advised him that there was some miscommunication between the Controller and the PIC. Controller allegedly thought the flight wanted to divert to DCA not BWI. After multiple ACARS exchanges with the crew relating to this matter; Captain informed me that he was diverting to his original alternate RIC. By that time he was committed anyway as he was already halfway there. After the flight landed; Captain called me to explain why he could not go to BWI. I informed him of the 'miscommunication' issue ATC was claiming. Captain proceeded to tell me that I was given the wrong information. He confirmed that ATC informed all flights holding for DCA at three different times that diversions to BWI were not allowed. ATC was clearly adamant about it. The event occurred because ATC was overstepping its authority. If an airport is open to landings; as confirmed by BWI ATC Tower; I do not see why ATC Center would keep any flight from diverting to that airport. Why do we need dispatchers if ATC steps in and takes over operational control whenever they feel like it? Flight landed in RIC with only 3900 lbs of fuel on board; which is below min dispatch for [our carrier]. This was due to the confusing and conflicting information given by ATC; followed by their decision to send the flight to RIC instead of BWI.ATC should be briefed on the scope of their authority and be exposed to the regulations outlined in FAR 121.533 (operational control). I do not believe they have a full understanding of our responsibilities as dispatchers. This is the second such incident in recent weeks; and both occurred in DC Center airspace.
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.