37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 714522 |
Time | |
Date | 200610 |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : dfw.airport |
State Reference | TX |
Altitude | agl single value : 0 |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B757 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : preflight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
ASRS Report | 714522 |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : published procedure non adherence : clearance other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | none taken : unable |
Supplementary | |
Problem Areas | Aircraft |
Primary Problem | Aircraft |
Narrative:
RNAV departures. We/us pilots keep receiving emails about deviations on RNAV departure because of the wrong runway in the FMC. Usually our tps will list 5 different runways; with the first runway on the list being primary. My experience is that on many departures this primary runway is not the preferred by ATC. The list of runways is decided by someone in a room in dfw; who isn't aware of local runway configns. Ord is a good example. One problem I've noticed is as follows: FMC is selected for the appropriate runway at gate; not the primary runway on tps. On taxi out once the load is received the FMC will default back to the primary runway on the tps. Running checklist; monitoring ATC on the taxi out; I've noticed many crew members don't catch the FMC defaulting back to the primary runway; not the runway selected at the gate to match airport operations. I am only familiar with the B767/B757; but with the FMC defaulting back to the tps primary runway might be creating some of the RNAV violations. The correct runway; SID and transition being selected before taxi but the FMC defaults back to the primary runway on the tps after load closeout; leaving the wrong runway in the FMC?
Original NASA ASRS Text
Title: A B757 PLT NOTES THAT AT DFW AN FMC WILL REVERT TO FLT PLANNED RWY DURING TAXI OUT CAUSING AN INCORRECT DEP RWY FOR THE DESIRED SID.
Narrative: RNAV DEPS. WE/US PLTS KEEP RECEIVING EMAILS ABOUT DEVS ON RNAV DEP BECAUSE OF THE WRONG RWY IN THE FMC. USUALLY OUR TPS WILL LIST 5 DIFFERENT RWYS; WITH THE FIRST RWY ON THE LIST BEING PRIMARY. MY EXPERIENCE IS THAT ON MANY DEPS THIS PRIMARY RWY IS NOT THE PREFERRED BY ATC. THE LIST OF RWYS IS DECIDED BY SOMEONE IN A ROOM IN DFW; WHO ISN'T AWARE OF LCL RWY CONFIGNS. ORD IS A GOOD EXAMPLE. ONE PROB I'VE NOTICED IS AS FOLLOWS: FMC IS SELECTED FOR THE APPROPRIATE RWY AT GATE; NOT THE PRIMARY RWY ON TPS. ON TAXI OUT ONCE THE LOAD IS RECEIVED THE FMC WILL DEFAULT BACK TO THE PRIMARY RWY ON THE TPS. RUNNING CHKLIST; MONITORING ATC ON THE TAXI OUT; I'VE NOTICED MANY CREW MEMBERS DON'T CATCH THE FMC DEFAULTING BACK TO THE PRIMARY RWY; NOT THE RWY SELECTED AT THE GATE TO MATCH ARPT OPS. I AM ONLY FAMILIAR WITH THE B767/B757; BUT WITH THE FMC DEFAULTING BACK TO THE TPS PRIMARY RWY MIGHT BE CREATING SOME OF THE RNAV VIOLATIONS. THE CORRECT RWY; SID AND TRANSITION BEING SELECTED BEFORE TAXI BUT THE FMC DEFAULTS BACK TO THE PRIMARY RWY ON THE TPS AFTER LOAD CLOSEOUT; LEAVING THE WRONG RWY IN THE FMC?
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.