 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An air carrier flight crew in an medium large transport entered the next waypoint into the FMC incorrectly and did not verify the entry. Later, a controller questioned their route of flight and they then noted the error.
| Attributes | |
| ACN | 375010 |
| Time | |
| Date | 199707 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : iah |
| State Reference | TX |
| Altitude | msl bound lower : 20000 msl bound upper : 20000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zhu |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other Other |
| Flight Phase | climbout : intermediate altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : instrument pilot : commercial pilot : atp |
| Experience | flight time last 90 days : 150 flight time total : 12000 flight time type : 2500 |
| ASRS Report | 375010 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : commercial |
| Events | |
| Anomaly | non adherence : far non adherence : clearance other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | flight crew : returned to intended course or assigned course other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Copilot was flying. We were cleared direct lfk. I read back then entered in FMC. 1 of 2 things then happened, 1) I selected wrong fix, or 2) FMC updated just prior to my selecting lfk causing motly intersection to jump to the line I selected. Failure by either myself or the copilot to verify where we were going resulted in another call from a different controller that we were cleared direct lufkin. Copilot and I then saw we were headed direct to motly intersection. We entered direct lufkin into FMC and proceeded on course. There was never any traffic conflict. Complacency, how often do we have to hear about it? This kind of failure to verify navigation position in mountainous terrain could be fatal. I've learned my lesson. Set it, verify it and verify it again and question it if it doesn't make sense.
Original NASA ASRS Text
Title: AN ACR FLC IN AN MLG ENTERED THE NEXT WAYPOINT INTO THE FMC INCORRECTLY AND DID NOT VERIFY THE ENTRY. LATER, A CTLR QUESTIONED THEIR RTE OF FLT AND THEY THEN NOTED THE ERROR.
Narrative: COPLT WAS FLYING. WE WERE CLRED DIRECT LFK. I READ BACK THEN ENTERED IN FMC. 1 OF 2 THINGS THEN HAPPENED, 1) I SELECTED WRONG FIX, OR 2) FMC UPDATED JUST PRIOR TO MY SELECTING LFK CAUSING MOTLY INTXN TO JUMP TO THE LINE I SELECTED. FAILURE BY EITHER MYSELF OR THE COPLT TO VERIFY WHERE WE WERE GOING RESULTED IN ANOTHER CALL FROM A DIFFERENT CTLR THAT WE WERE CLRED DIRECT LUFKIN. COPLT AND I THEN SAW WE WERE HEADED DIRECT TO MOTLY INTXN. WE ENTERED DIRECT LUFKIN INTO FMC AND PROCEEDED ON COURSE. THERE WAS NEVER ANY TFC CONFLICT. COMPLACENCY, HOW OFTEN DO WE HAVE TO HEAR ABOUT IT? THIS KIND OF FAILURE TO VERIFY NAV POS IN MOUNTAINOUS TERRAIN COULD BE FATAL. I'VE LEARNED MY LESSON. SET IT, VERIFY IT AND VERIFY IT AGAIN AND QUESTION IT IF IT DOESN'T MAKE SENSE.
Data retrieved from NASA's ASRS site as of July 2007 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.