37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 942285 |
Time | |
Date | 201104 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ATL.Airport |
State Reference | GA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
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 Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Just before pushback; we received an ACARS text message that we had been rerouted over SUMMT4 and that release 2 was ready. Release 2 route matched the message. The pre departure clearance showed two routes. One was an incomplete version of our original route using the dawgs 4; and a complete version of our new route. The ACARS west/B came back with data for release 2; reinforcing that the new data was correct. I have not encountered this pre departure clearance format for a route change. As far as I can tell there is nothing in any manual explaining how and why you would have two routes on a pre departure clearance or the proper format. My assumption was that the second route would be listed second; and a route with no clearance limit was not a valid route; so I discounted the dawgs route. Maybe it is not a good idea to put a route on a pre departure clearance that has no validity or reason for being there. Why do I want or need to know where I am not going? If the FAA has a reason to put where I am not going on a clearance; why don't they write english words indicating what they really want instead of nonsense dashes; or asterisks. Compounding the problem is the extreme pressure from the company to get the flight off on time. So there was no time for reflection with the last minute change. If a well rested 25;000 hour pilot with no history of enforcement actions cannot get through this minefield without a deviation; human factors may need another look.
Original NASA ASRS Text
Title: A flight crew described the confusion which resulted from a ACARS PDC with two routes and how they chose the incorrect routing. They question why during a reroute the invalid clearance is included in the final PDC paper work.
Narrative: Just before pushback; we received an ACARS text message that we had been rerouted over SUMMT4 and that Release 2 was ready. Release 2 route matched the message. The PDC showed two routes. One was an incomplete version of our original route using the DAWGS 4; and a complete version of our new route. The ACARS W/B came back with data for Release 2; reinforcing that the new data was correct. I have not encountered this PDC format for a route change. As far as I can tell there is nothing in any manual explaining how and why you would have two routes on a PDC or the proper format. My assumption was that the second route would be listed second; and a route with no clearance limit was not a valid route; so I discounted the DAWGS route. Maybe it is not a good idea to put a route on a PDC that has no validity or reason for being there. Why do I want or need to know where I am NOT going? If the FAA has a reason to put where I am not going on a clearance; why don't they write English words indicating what they really want instead of nonsense dashes; or asterisks. Compounding the problem is the extreme pressure from the Company to get the flight off on time. So there was no time for reflection with the last minute change. If a well rested 25;000 hour pilot with no history of enforcement actions cannot get through this minefield without a deviation; human factors may need another look.
Data retrieved from NASA's ASRS site as of April 2012 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.