 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737-700 crew programmed a 'canned' FMC routing instead of the amended filed flight plan and subsequently flew an incorrect route.
| Attributes | |
| ACN | 675428 |
| Time | |
| Date | 200510 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | navaid : rav.vortac |
| State Reference | PA |
| Altitude | msl single value : 40000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zob.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other vortac |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Experience | flight time last 90 days : 140 flight time total : 9500 flight time type : 3150 |
| ASRS Report | 675428 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | non adherence : clearance non adherence : company policies other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance flight crew : returned to intended or assigned course |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | Chart Or Publication Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
FMC programmed for '01' route. Did not notice 'see filed route' at top of page of release. Verified route to clearance. Seemed to agree. Captain verified FMC route to agree with clearance. Approximately first 4 fixes were the same as '01' route. However; the rest of the clearance was not. After rav; should have gone direct psb J60 gsh then the arrival to mdw. I saw on the route in the FMC a J64 which goes over fwa. The 2 jet airways were similar in number; so I did not notice I had incorrect routing in the FMC. Approximately 100 mi west of rav; ATC queried us as to where we were going. I said mdw. He then said 'what is your route?' I read back the filed. He said we missed our turn and were approximately 50 mi southwest of psb. He then gave us direct djb to get back on course and had us descend to FL380. After apologizing to ATC for the mistake; he stated he did not notice we were off course until his buddy next to him said something. I think having similar routing and airways having similar numbers were contributing factors. Not verifying all fixes along the route was the ultimate mistake on my part. In the future; I will verify the route and fixes and step-by-step compare it to the clearance. I will also be mindful of the route at the top of the dispatch release. Is it a '01' or 'see filed route' so as to alert me that the computer may not have the same route as programmed.
Original NASA ASRS Text
Title: A B737-700 CREW PROGRAMMED A 'CANNED' FMC ROUTING INSTEAD OF THE AMENDED FILED FLT PLAN AND SUBSEQUENTLY FLEW AN INCORRECT RTE.
Narrative: FMC PROGRAMMED FOR '01' RTE. DID NOT NOTICE 'SEE FILED RTE' AT TOP OF PAGE OF RELEASE. VERIFIED RTE TO CLRNC. SEEMED TO AGREE. CAPT VERIFIED FMC RTE TO AGREE WITH CLRNC. APPROX FIRST 4 FIXES WERE THE SAME AS '01' RTE. HOWEVER; THE REST OF THE CLRNC WAS NOT. AFTER RAV; SHOULD HAVE GONE DIRECT PSB J60 GSH THEN THE ARR TO MDW. I SAW ON THE RTE IN THE FMC A J64 WHICH GOES OVER FWA. THE 2 JET AIRWAYS WERE SIMILAR IN NUMBER; SO I DID NOT NOTICE I HAD INCORRECT ROUTING IN THE FMC. APPROX 100 MI W OF RAV; ATC QUERIED US AS TO WHERE WE WERE GOING. I SAID MDW. HE THEN SAID 'WHAT IS YOUR RTE?' I READ BACK THE FILED. HE SAID WE MISSED OUR TURN AND WERE APPROX 50 MI SW OF PSB. HE THEN GAVE US DIRECT DJB TO GET BACK ON COURSE AND HAD US DSND TO FL380. AFTER APOLOGIZING TO ATC FOR THE MISTAKE; HE STATED HE DID NOT NOTICE WE WERE OFF COURSE UNTIL HIS BUDDY NEXT TO HIM SAID SOMETHING. I THINK HAVING SIMILAR ROUTING AND AIRWAYS HAVING SIMILAR NUMBERS WERE CONTRIBUTING FACTORS. NOT VERIFYING ALL FIXES ALONG THE RTE WAS THE ULTIMATE MISTAKE ON MY PART. IN THE FUTURE; I WILL VERIFY THE RTE AND FIXES AND STEP-BY-STEP COMPARE IT TO THE CLRNC. I WILL ALSO BE MINDFUL OF THE RTE AT THE TOP OF THE DISPATCH RELEASE. IS IT A '01' OR 'SEE FILED RTE' SO AS TO ALERT ME THAT THE COMPUTER MAY NOT HAVE THE SAME RTE AS PROGRAMMED.
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.