37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 961171 |
Time | |
Date | 201107 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZID.ARTCC |
State Reference | IN |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Center inquired where we were heading sometime after passing air VOR. We responded 'KI570' [kilo india five seven zero]; and were given an immediate clearance to proceed direct to stl; our next flight plan fix. We were in LNAV and on the active route line. Approximately 40 minutes later; kansas city center gave us a phone number to contact indianapolis center upon landing. The controller advised me that we were approximately 28 miles north of course before giving us direct stl and asked if I had any idea what happened. At the time I thought that we were heading to KI570 and couldn't explain what exactly happened. Fortunately; there was no reported traffic conflict.in retrospect; during preflight; I couldn't get the FMC to recognize KI570; even after entering it several different ways. I couldn't find it on the enroute chart (until much later after the message from kansas city center) so I constructed a fix from the flight plan off the air VOR. Apparently; I must have entered the wrong bearing; although I recall that the distance was correct; and we did not notice the error during our preflight route verification check. I have never had this sort of waypoint in a clearance before. After my phone conversation with the controller; I researched the fom and found a short narrative on nrs [navigational reference system] waypoints and how they are named. My error had been trying to enter a 'one' for the 'I'; along with a 'zero' for the 'O'; with several variations of each. Regretfully; I never entered the 'I' and the 'O' at the same time. Although this is not an excuse for my error; my attention had been preoccupied with several other issues during the boarding process and I allowed myself to be somewhat rushed and allowed an unintentional faulty FMC entry to occur and subsequently missed it during the route verification process. Although I consider myself more aware of nrs waypoints; I would recommend that the 'I''s and the 'O''s be omitted from the naming process since they are difficult to distinguish on the flight plan lettering format. In the future; I will not be satisfied until the waypoint format is accepted by the FMC database.
Original NASA ASRS Text
Title: The Flight Crew of a B757-200 flight received a clearance including the waypoint KI570 but were unable to successfully load it in their FMC. They then 'built' a fix off of AIR VOR. Ultimately this fix turned out to be incorrect; ATC intervened and the Flight Crew learned that they had failed to attempt loading the proper alphanumeric form of the I/1 and the O/0.
Narrative: Center inquired where we were heading sometime after passing AIR VOR. We responded 'KI570' [Kilo India five seven Zero]; and were given an immediate clearance to proceed direct to STL; our next flight plan fix. We were in LNAV and on the active route line. Approximately 40 minutes later; Kansas City Center gave us a phone number to contact Indianapolis Center upon landing. The controller advised me that we were approximately 28 miles north of course before giving us direct STL and asked if I had any idea what happened. At the time I thought that we were heading to KI570 and couldn't explain what exactly happened. Fortunately; there was no reported traffic conflict.In retrospect; during preflight; I couldn't get the FMC to recognize KI570; even after entering it several different ways. I couldn't find it on the enroute chart (until much later after the message from Kansas City Center) so I constructed a fix from the flight plan off the AIR VOR. Apparently; I must have entered the wrong bearing; although I recall that the distance was correct; and we did not notice the error during our preflight route verification check. I have never had this sort of waypoint in a clearance before. After my phone conversation with the controller; I researched the FOM and found a short narrative on NRS [Navigational Reference System] waypoints and how they are named. My error had been trying to enter a 'one' for the 'I'; along with a 'zero' for the 'O'; with several variations of each. Regretfully; I never entered the 'I' and the 'O' at the same time. Although this is not an excuse for my error; my attention had been preoccupied with several other issues during the boarding process and I allowed myself to be somewhat rushed and allowed an unintentional faulty FMC entry to occur and subsequently missed it during the route verification process. Although I consider myself more aware of NRS waypoints; I would recommend that the 'I''s and the 'O''s be omitted from the naming process since they are difficult to distinguish on the flight plan lettering format. In the future; I will not be satisfied until the waypoint format is accepted by the FMC database.
Data retrieved from NASA's ASRS site as of April 2012 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.