A B757 flight crew was given a runway and RNAV procedure change during pushback while the Captain was communicating with the pushback crew. The First Officer failed to communicate the RNAV changes and a track deviation resulted after takeoff.

Date: 2010-03 · Aircraft: B757-200 · Phase: initial_climb

Anomalies: atc-issue-all-types|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance

Synopsis

A B757 flight crew was given a runway and RNAV procedure change during pushback while the Captain was communicating with the pushback crew. The First Officer failed to communicate the RNAV changes and a track deviation resulted after takeoff.

Narrative

During pushback I was talking to the push crew while First Officer was contacting Ground for clearance. Apparently Ground also changed the runway and also issued a new a new departure procedure. All was normal up to takeoff on Runway 9. As we climbed out on the Departure (runway heading to 5000 FT); we were given a turn to the south and further climb was normal. Then the Controller asked us if we were on a RNAV departure. I thought we were on the one assigned on the PDC; but the First Officer remembered hearing a different RNAV during the pushback while I was off Ground and talking to the push crew. The flight clearance did clear us via an RNAV; and I did not know it had changed. There are times that ATC gives us clearance verbiage while on the rollout and I try not to respond as I feel we are busy still flying. Awhile talking to the push crew; I am a little out of the loop with Ground Control. The RNAV departures are still pretty new at this airport although not throughout the system. Maybe during pushback is a bad time for Ground to be changing our clearance.

Second reporter narrative

Early morning departure. Runway 15 was in use when the PDC was issued and our preflight duties were completed. We had set up for a RNAV departure (as indicated on the PDC) for Runway 15; agreed on this configuration and completed the checklist. We discussed the possibility of a runway change and agreed that it was a viable choice if presented. Upon contact with Clearance for pushback sequence; the Controller indeed asked if we could accept the new departure runway. The Captain was off frequency (as per procedure) in contact with the Ground Crew. I accepted the runway change. The Controller then assigned us the runway and gave us a different RNAV departure. I read back the change; switched to Ground frequency for push instructions; and I changed the runway in the Pegasus FMS. I had not yet communicated the change to the Captain when I was distracted by a call from Ground. We taxied out to the runway; and took off; flying the original Departure. Upon reaching 5000 FT; the Controller queried us about the departure we were flying and gave us a 160 heading. I told him the original PDC departure; and then realized that I had never communicated the change nor updated the FMS. His comment was that these SIDs are still new and gave us another heading and higher altitude. We continued the flight without further event.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.