37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 861962 |
Time | |
Date | 200911 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | CMH.Airport |
State Reference | OH |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
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) |
Person 2 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Clearance |
Narrative:
The original aircraft for the flight had a maintenance issue that required us to swap aircraft. We never looked at the original aircraft dispatch release. Upon receiving clearance we were given 'cleared to ZZZ via radar vectors; dqn; cvg; iiu then as filed'. Our flight plan that we had on the paperwork was dqn; cvg; pxv; tiide; lit; J180; .... When the first officer picked up the clearance I was listening and programmed the FMS; he verified it. Once airborne we were cleared direct to pxv; the controller then changed it to direct iiu and said pxv was not on our flight plan. We then queried him; and got clarification on the actual route that they showed for us. He explained; dqn; cvg; iiu; J39; bna; jan; aex; ... We then entered the correct flight plan in the FMS; then contacted dispatch to verify that we would have enough fuel to take that route (and we did). After I got fuel burn from dispatch I asked him what could have gone wrong. He explained that he did not refile the flight plan after the plane swap. We continued the flight; were asked to contact indy center upon landing. I contacted them and dispatch to clarify. There were two main issues here. When we were given the clearance we simply added iiu after cvg. We both failed to realize that iiu was not on the original route. We simply added iiu in between the two fixes we originally had. If we had not done this we would have discovered the next issue. The second issue was the fact that after a change in planes the dispatcher put a different route on the paperwork than what he had filed with ATC. This brings up obvious issues. Even though all of this occurred we never flew off course; we just had a communication issue; and the issue was resolved with no incident.
Original NASA ASRS Text
Title: An aircraft swap prior to departure results in the Dispatcher using a different route on the new release but not filing a new flight plan.
Narrative: The original aircraft for the flight had a maintenance issue that required us to swap aircraft. We never looked at the original aircraft dispatch release. Upon receiving clearance we were given 'Cleared to ZZZ via radar vectors; DQN; CVG; IIU then as filed'. Our flight plan that we had on the paperwork was DQN; CVG; PXV; TIIDE; LIT; J180; .... When the FO picked up the clearance I was listening and programmed the FMS; he verified it. Once airborne we were cleared direct to PXV; the controller then changed it to direct IIU and said PXV was not on our flight plan. We then queried him; and got clarification on the actual route that they showed for us. He explained; DQN; CVG; IIU; J39; BNA; JAN; AEX; ... We then entered the correct flight plan in the FMS; then contacted Dispatch to verify that we would have enough fuel to take that route (and we did). After I got fuel burn from Dispatch I asked him what could have gone wrong. He explained that he did not refile the flight plan after the plane swap. We continued the flight; were asked to contact Indy Center upon landing. I contacted them and Dispatch to clarify. There were two main issues here. When we were given the clearance we simply added IIU after CVG. We both failed to realize that IIU was not on the original route. We simply added IIU in between the two fixes we originally had. If we had not done this we would have discovered the next issue. The second issue was the fact that after a change in planes the Dispatcher put a different route on the paperwork than what he had filed with ATC. This brings up obvious issues. Even though all of this occurred we never flew off course; we just had a communication issue; and the issue was resolved with no incident.
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.