 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737-300 flight crew failed to xchk the cleared route against the FMC route and flew the wrong arrival. The company had failed to update the FMC database.
| Attributes | |
| ACN | 435308 |
| Time | |
| Date | 199904 |
| Day | Wed |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : gjt.airport |
| State Reference | CO |
| Altitude | msl bound lower : 29000 msl bound upper : 35000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zdv.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other |
| Flight Phase | cruise : enroute altitude change |
| Route In Use | arrival star : nootn |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : cfi pilot : instrument pilot : commercial |
| Experience | flight time last 90 days : 150 flight time total : 5000 flight time type : 1400 |
| ASRS Report | 435308 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : commercial pilot : instrument |
| Events | |
| Anomaly | aircraft equipment problem : less severe maintenance problem : non compliance with mel non adherence : clearance |
| Independent Detector | other controllera other flight crewa other flight crewb |
| Resolutory Action | controller : issued new clearance |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
ATC queried our route. We acknowledged that 'as filed' was assigned by den clearance control. Our filed route differed from our computer/FMC company route. ATC assigned us nootn arrival to las and requested us to descend to FL290. We realized that company FMC route had us flying the crowe arrival, which is no longer used and was not the filed route. After this incident I informed the responsible party at my company and was told the FMC route will be changed at a later date. Also during the routing change, we did not descend to FL290 until ATC asked us a second time. I verify the filed route versus company FMC route every time except this time.
Original NASA ASRS Text
Title: A B737-300 FLC FAILED TO XCHK THE CLRED RTE AGAINST THE FMC RTE AND FLEW THE WRONG ARR. THE COMPANY HAD FAILED TO UPDATE THE FMC DATABASE.
Narrative: ATC QUERIED OUR RTE. WE ACKNOWLEDGED THAT 'AS FILED' WAS ASSIGNED BY DEN CLRNC CTL. OUR FILED RTE DIFFERED FROM OUR COMPUTER/FMC COMPANY RTE. ATC ASSIGNED US NOOTN ARR TO LAS AND REQUESTED US TO DSND TO FL290. WE REALIZED THAT COMPANY FMC RTE HAD US FLYING THE CROWE ARR, WHICH IS NO LONGER USED AND WAS NOT THE FILED RTE. AFTER THIS INCIDENT I INFORMED THE RESPONSIBLE PARTY AT MY COMPANY AND WAS TOLD THE FMC RTE WILL BE CHANGED AT A LATER DATE. ALSO DURING THE ROUTING CHANGE, WE DID NOT DSND TO FL290 UNTIL ATC ASKED US A SECOND TIME. I VERIFY THE FILED RTE VERSUS COMPANY FMC RTE EVERY TIME EXCEPT THIS TIME.
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.