37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 709369 |
Time | |
Date | 200609 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : zzz.airport |
State Reference | US |
Altitude | agl single value : 0 |
Environment | |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : ttpp.tower |
Operator | common carrier : air carrier |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
ASRS Report | 708309 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | non adherence : company policies non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | Company |
Primary Problem | Company |
Narrative:
When taking off to the north; the primary runway departure is runway 35L not runway 36R; when departing to the south it is runway 17R not runway 18L. The takeoff performance computer and FMS seems to put in the incorrect runways. Flts can be delayed by rebriefing new runway and rechking and xchking the data downloaded after load closeout because of wrong runway data sent to FMS; not to mention unnecessary heads down time by one of the pilots typing in the correct data. Obviously the FMS should be checked by both pilots. But when the route study and FMS is checked at the gate during a relaxed setting; then the takeoff data is automatically downloaded during taxiing with the wrong runway downloaded; one of the pilots has to reload the correct data (heads down). This is a setting for potential error during a critical phase of flight. Suggestion: the correct runway should be #1 on the takeoff performance computer and downloaded to the FMS initially at the gate.
Original NASA ASRS Text
Title: B757-200 FO RPTS TKOF PERFORMANCE COMPUTER FAILS TO DISPLAY DATA FOR THE MOST LIKELY TKOF RWYS. FLT CREW MUST REDO TKOF DATA FOR CORRECT RWY AFTER GATE DEP; CAUSING DISTR DURING TAXI.
Narrative: WHEN TAKING OFF TO THE N; THE PRIMARY RWY DEP IS RWY 35L NOT RWY 36R; WHEN DEPARTING TO THE S IT IS RWY 17R NOT RWY 18L. THE TKOF PERFORMANCE COMPUTER AND FMS SEEMS TO PUT IN THE INCORRECT RWYS. FLTS CAN BE DELAYED BY REBRIEFING NEW RWY AND RECHKING AND XCHKING THE DATA DOWNLOADED AFTER LOAD CLOSEOUT BECAUSE OF WRONG RWY DATA SENT TO FMS; NOT TO MENTION UNNECESSARY HEADS DOWN TIME BY ONE OF THE PLTS TYPING IN THE CORRECT DATA. OBVIOUSLY THE FMS SHOULD BE CHKED BY BOTH PLTS. BUT WHEN THE RTE STUDY AND FMS IS CHKED AT THE GATE DURING A RELAXED SETTING; THEN THE TKOF DATA IS AUTOMATICALLY DOWNLOADED DURING TAXIING WITH THE WRONG RWY DOWNLOADED; ONE OF THE PLTS HAS TO RELOAD THE CORRECT DATA (HEADS DOWN). THIS IS A SETTING FOR POTENTIAL ERROR DURING A CRITICAL PHASE OF FLT. SUGGESTION: THE CORRECT RWY SHOULD BE #1 ON THE TKOF PERFORMANCE COMPUTER AND DOWNLOADED TO THE FMS INITIALLY AT THE GATE.
Data retrieved from NASA's ASRS site as of January 2009 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.