37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1516986 |
Time | |
Date | 201802 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | MD-11 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 150 Flight Crew Total 7500 Flight Crew Type 3000 |
Person 2 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 50 Flight Crew Total 12000 Flight Crew Type 3600 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
When initially taxiing out I was expecting runway xxl full length based on the departure ATIS. As we taxied we were told to get data for xxl/a and xxr/a. We initially loaded data for xxl/a which included a takeoff flaps setting of 17. We referenced the QRH and ran the runway change procedure. As we were holding short of xxl; my mental picture was that we were still going to depart from xxl/a. The captain and I discussed the heavy load of arrivals on runway xxl. Shortly after; we were cleared to cross runway xxl/a and immediately cleared for takeoff on runway xxr/a. I should have spoken up and said I needed more time to stop and run the runway change procedure again; but I didn't. I quickly loaded the new departure runway and then loaded the proper takeoff data. I assumed that the takeoff data would be the same for both runways.I quickly verified the V speeds that were loaded were correct; but failed to notice that the flap setting for takeoff had changed from 17 to flaps 13. The flap setting changed because runway xxl/a is about 300 feet shorter than runway xxr/a. As we took the runway and pushed the power up for takeoff; we noticed that we had no green box. The captain called reject at approximately 35 knots. We slowed to taxi speed and exited the runway. We turned onto [the] taxiway; stopped; reviewed the takeoff data and found our error immediately. We ran the full runway change procedure and ensured we were properly configured for takeoff. We taxied back to runway xxr/a and departed normally. Once airborne; the captain entered the rejected takeoff in the logbook per fom guidance.this error could have easily been trapped by not letting ATC rush us for takeoff. We should have crossed xxl; stopped; and run the full runway change procedure before departing. Additionally; the captain and I could have had better communication about our expectations. This would have trapped the error by eliminating my expectation bias regarding the departure runway.
Original NASA ASRS Text
Title: MD-11 flight crew reported that due to a late runway change the aircraft was not configured correctly for takeoff.
Narrative: When initially taxiing out I was expecting Runway XXL full length based on the departure ATIS. As we taxied we were told to get data for XXL/A and XXR/A. We initially loaded data for XXL/A which included a takeoff flaps setting of 17. We referenced the QRH and ran the runway change procedure. As we were holding short of XXL; my mental picture was that we were still going to depart from XXL/A. The Captain and I discussed the heavy load of arrivals on Runway XXL. Shortly after; we were cleared to cross Runway XXL/A and immediately cleared for takeoff on Runway XXR/A. I should have spoken up and said I needed more time to stop and run the runway change procedure again; but I didn't. I quickly loaded the new departure runway and then loaded the proper takeoff data. I assumed that the takeoff data would be the same for both runways.I quickly verified the V speeds that were loaded were correct; but failed to notice that the flap setting for takeoff had changed from 17 to flaps 13. The flap setting changed because Runway XXL/A is about 300 feet shorter than Runway XXR/A. As we took the runway and pushed the power up for takeoff; we noticed that we had no green box. The Captain called reject at approximately 35 knots. We slowed to taxi speed and exited the runway. We turned onto [the] taxiway; stopped; reviewed the takeoff data and found our error immediately. We ran the full runway change procedure and ensured we were properly configured for takeoff. We taxied back to runway XXR/A and departed normally. Once airborne; the Captain entered the rejected takeoff in the logbook per FOM guidance.This error could have easily been trapped by not letting ATC rush us for takeoff. We should have crossed XXL; stopped; and run the full runway change procedure before departing. Additionally; the Captain and I could have had better communication about our expectations. This would have trapped the error by eliminating my expectation bias regarding the departure runway.
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.