37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1186944 |
Time | |
Date | 201407 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | IAH.Airport |
State Reference | TX |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Wrong RNAV departure transition selected after runway change. Originally we were filed for the bndto 1 departure jct transition so that is what was printed on our release. However; our clearance was amended to the pitzz 1 departure crger transition. We were unsure of the runway that we were to be assigned; so we input runway 15R because the day before we were given the exact same scenario. The FMS was loaded correctly and verified to match the amended clearance prior to taxi. However; when we called for push back and advised ramp control of our assigned departure we were told to expect runway 15L. Being a very studios first officer; the non-flying pilot input runway 15L however he selected the pitzz 1 jct transition. I was taxiing and looked down and verified the jct transition against the release instead of the amended clearance. Therefore we now had the wrong transition loaded in the FMS with the correct runway. After departure we were advised by ATC that we were tracking the wrong transition.one threat is that two different departures have the same name in the transitions. Another threat is that ramp control is advising crews of the runway to expect while taxiing. Therefore any changes to the FMS are done during a higher workload period such as taxiing. Some airports have RNAV departures that are runway specific and it is very important to input the correct runway. However; in houston we would have been better off leaving the wrong runway in the FMS because the procedure is the same for both departure runways.in the future; I think I will cross out the amended clearance on the release and then write down the new clearance above the original filed route. Also; I think clearance delivery should include the expected runway for departure with the clearance. That way we can verify the flight plan while at the gate without the distractions of taxiing. I believe this is especially true at airports where the runway is very important for the departure flown; such as atl. I understand that the runway may change after taxi out; however when this occurs ATC should recognize that we crew need time to make the changes without distractions.
Original NASA ASRS Text
Title: Air Carrier flight crew reports a track deviation departing IAH on the PITZZ 1 RNAV. The SID was changed by Clearance Delivery prior to taxi and the runway was changed by Ground Control during taxi. When the SID is reentered into the FMC after the runway change the wrong transition is selected.
Narrative: Wrong RNAV departure transition selected after runway change. Originally we were filed for the BNDTO 1 departure JCT transition so that is what was printed on our release. However; our clearance was amended to the PITZZ 1 departure CRGER transition. We were unsure of the runway that we were to be assigned; so we input Runway 15R because the day before we were given the exact same scenario. The FMS was loaded correctly and verified to match the amended clearance prior to taxi. However; when we called for push back and advised Ramp Control of our assigned departure we were told to expect Runway 15L. Being a very studios First Officer; the non-flying pilot input Runway 15L however he selected the PITZZ 1 JCT transition. I was taxiing and looked down and verified the JCT transition against the release instead of the amended clearance. Therefore we now had the wrong transition loaded in the FMS with the correct runway. After departure we were advised by ATC that we were tracking the wrong transition.One threat is that two different departures have the same name in the transitions. Another threat is that ramp control is advising crews of the runway to expect while taxiing. Therefore any changes to the FMS are done during a higher workload period such as taxiing. Some airports have RNAV departures that are runway specific and it is very important to input the correct runway. However; in Houston we would have been better off leaving the wrong runway in the FMS because the procedure is the same for both departure runways.In the future; I think I will cross out the amended clearance on the release and then write down the new clearance above the original filed route. Also; I think Clearance Delivery should include the expected runway for departure with the clearance. That way we can verify the flight plan while at the gate without the distractions of taxiing. I believe this is especially true at airports where the runway is very important for the departure flown; such as ATL. I understand that the runway may change after taxi out; however when this occurs ATC should recognize that we crew need time to make the changes without distractions.
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.