37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 226706 |
Time | |
Date | 199211 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : abe |
State Reference | PA |
Altitude | msl bound lower : 29000 msl bound upper : 29000 |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zny artcc : zny |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport |
Navigation In Use | Other Other |
Flight Phase | cruise other descent other |
Route In Use | enroute airway : zny |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : flight engineer pilot : commercial pilot : atp |
Experience | flight time last 90 days : 255 flight time total : 20000 flight time type : 255 |
ASRS Report | 226706 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : atp pilot : commercial |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | atc equipment other atc equipment : unspecified other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation |
Narrative:
I had the same air carrier aircraft flight from phl to orh and then back to phl. Inserted route 1 from phl to orh and computer would not accept route. I then inserted jet airway manually and it would not accept that either. It finally accepted point to point which matched the airway. On the next leg (orh-phl) I again inserted route 1 per the flight release. Upon closer examination, I discovered that the FMC route and dispatch release had 2 different initial points and victor airways. One went to baf, the other went to center. I corrected the route and proceeded on. The corrected route later had us going on V147 from avp over etx to mazie intersection. After avp the aircraft proceeded direct to mazie. ATC picked up the deviation first and then cleared us direct to mazie. The company later confirmed the route discrepancy and issued a notice to future crews to ignore the FMC route. Why the aircraft went to mazie I'm still not sure. One thing I am sure is that manual VOR backup is still a necessity.
Original NASA ASRS Text
Title: FLC OF ACR MLG ACFT DEVIATED FROM ASSIGNED RTE DUE TO AN ERROR IN THE ACFT FMC PREPROGRAM RTE.
Narrative: I HAD THE SAME ACR ACFT FLT FROM PHL TO ORH AND THEN BACK TO PHL. INSERTED RTE 1 FROM PHL TO ORH AND COMPUTER WOULD NOT ACCEPT RTE. I THEN INSERTED JET AIRWAY MANUALLY AND IT WOULD NOT ACCEPT THAT EITHER. IT FINALLY ACCEPTED POINT TO POINT WHICH MATCHED THE AIRWAY. ON THE NEXT LEG (ORH-PHL) I AGAIN INSERTED RTE 1 PER THE FLT RELEASE. UPON CLOSER EXAMINATION, I DISCOVERED THAT THE FMC RTE AND DISPATCH RELEASE HAD 2 DIFFERENT INITIAL POINTS AND VICTOR AIRWAYS. ONE WENT TO BAF, THE OTHER WENT TO CTR. I CORRECTED THE RTE AND PROCEEDED ON. THE CORRECTED RTE LATER HAD US GOING ON V147 FROM AVP OVER ETX TO MAZIE INTXN. AFTER AVP THE ACFT PROCEEDED DIRECT TO MAZIE. ATC PICKED UP THE DEV FIRST AND THEN CLRED US DIRECT TO MAZIE. THE COMPANY LATER CONFIRMED THE RTE DISCREPANCY AND ISSUED A NOTICE TO FUTURE CREWS TO IGNORE THE FMC RTE. WHY THE ACFT WENT TO MAZIE I'M STILL NOT SURE. ONE THING I AM SURE IS THAT MANUAL VOR BACKUP IS STILL A NECESSITY.
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.