37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1236826 |
Time | |
Date | 201502 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 210 Flight Crew Total 14100 Flight Crew Type 1200 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
Prior to flight; we were reviewing the pre departure clearance which we got normally over ACARS. I noticed that the pilot alert/revised segment said none and that the filed route segment had a normal looking abbreviation of our route clearance. I happened to check the route in the FMC (which had been automatically up loaded) and noted that it was different from what was shown in the pre departure clearance. Upon further investigation; it turned out that the pre departure clearance showed '…zirkl mck lnk dsm evote nells *** [destination]'. The FMC and our sabre flight plan; however; showed …zirkl dsm evote nells and the rest of the route to destination. We checked with clearance delivery and he showed the same thing as the pre departure clearance. I called the dispatcher and he said that we had filed what was on the sabre plan; which did not include the two fixes mck and lnk. He said he would refile and check with the ATC coordinator and let me know what he found. I stated that I was more interested in resolving the issue for our flight and getting out than researching the problem right now; and he agreed to try to make that happen. We discussed the fact that both routes were very similar fuel wise; so the difference was negligible. We then called clearance delivery and negotiated the route that was on sabre. The clearance delivery guy stated that he initially had trouble getting the route to show zirkl dsm. He said that zirkl mck lnk dsm was what was filed by the company.the dispatcher said he would make an input to the sabre people to see what happened. I am concerned that what ATC thought was our filed route was not what we had filed. If the route is changed; it needs to show up in the pilot alert/revised segment part of the pre departure clearance.either what sabre sent to the ATC computers was not what sabre should have sent (i.e.; what was on the dispatcher's screen and what was on my flight plan); or ATC changed the route without telling anyone. Both are problematic. Also turns out we did not file an arrival. When we asked center about that; they said 'we show you filed slate run and the williamsport three arrival.' this is a second; separate change to our flight plan that it was impossible to catch on the pre departure clearance due to the 'nells***[destination]' way it was shown on the pre departure clearance. Note that in the event of lost comm; even after correcting the departure routing; we would not have flown the ATC expected arrival; since we would have thought (sure; it is weird; but it's what we filed; right?) we should fly the filed direct routing.
Original NASA ASRS Text
Title: The flight crew of a B737 noted a discrepancy between their flight planned/PDC cleared route and the route automatically downloaded to their FMC.
Narrative: Prior to flight; we were reviewing the PDC which we got normally over ACARS. I noticed that the PILOT ALERT/REVISED SEGMENT said NONE and that the FILED ROUTE segment had a normal looking abbreviation of our route clearance. I happened to check the route in the FMC (which had been automatically up loaded) and noted that it was different from what was shown in the PDC. Upon further investigation; it turned out that the PDC showed '…ZIRKL MCK LNK DSM EVOTE NELLS *** [Destination]'. The FMC and our SABRE flight plan; however; showed …ZIRKL DSM EVOTE NELLS and the rest of the route to destination. We checked with Clearance Delivery and he showed the same thing as the PDC. I called the dispatcher and he said that we had filed what was on the SABRE plan; which did not include the two fixes MCK and LNK. He said he would refile and check with the ATC coordinator and let me know what he found. I stated that I was more interested in resolving the issue for our flight and getting out than researching the problem right now; and he agreed to try to make that happen. We discussed the fact that both routes were very similar fuel wise; so the difference was negligible. We then called Clearance Delivery and negotiated the route that was on SABRE. The Clearance Delivery guy stated that he initially had trouble getting the route to show ZIRKL DSM. He said that ZIRKL MCK LNK DSM was what was filed by the company.The dispatcher said he would make an input to the SABRE people to see what happened. I am concerned that what ATC thought was our filed route was not what we had filed. If the route is changed; it needs to show up in the PILOT ALERT/REVISED SEGMENT part of the PDC.Either what SABRE sent to the ATC computers was not what SABRE should have sent (i.e.; what was on the Dispatcher's screen and what was on my flight plan); or ATC changed the route without telling anyone. Both are problematic. Also turns out we did not file an arrival. When we asked Center about that; they said 'we show you filed Slate Run and the Williamsport Three arrival.' This is a second; separate change to our flight plan that it was impossible to catch on the PDC due to the 'NELLS***[Destination]' way it was shown on the PDC. Note that in the event of Lost Comm; even after correcting the departure routing; we would not have flown the ATC expected arrival; since we would have thought (sure; it is weird; but it's what we filed; right?) we should fly the filed direct routing.
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.