37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1051173 |
Time | |
Date | 201211 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZOB.ARTCC |
State Reference | OH |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Not Flying |
Experience | Flight Crew Last 90 Days 200 Flight Crew Total 20000 Flight Crew Type 7000 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
On the ground before departure we loaded the route supplied by the flight plan. After receiving an updated clearance; we loaded the new route. The new route included the wynde 4 arrival into ord. En route to ord the first officer briefed the arrival and runway that was selected to land in ord. The route was double checked by both of us. Somewhere around the fnt VOR; it appeared that the FMC had a momentary malfunction. The route came up but before we could check the route; we had passed fnt and the FMC started toward dewit intersection. The controller asked if we were heading toward emmma intersection that was on the arrival. I responded that we were past emmma as; (looking at the FMC) emmma intersection had disappeared. The controller advised that we were 3 miles southeast of emmma. He then cleared us to grr to rejoin the arrival. The first officer entered grr in the FMC and we proceeded to grr. I asked the controller is there were any separation problems; and he responded no and there were no problems. Since we were within 3 miles of emmma when the problem was resolved; it appears that there were no pilot deviations before the correction. As for the FMC; it appeared that emmma and ltour intersections had disappeared. Grr was in the box and the first officer just brought up grr to get back on the arrival. I made a logbook entry as to the failure of the FMC.
Original NASA ASRS Text
Title: A B737 FMS dropped a WYNDE 4 RNAV segment immediately after FNT and proceeded to a DEWIT Intersection which was not on the flight plan. ATC caught the deviation and cleared the flight direct GRR.
Narrative: On the ground before departure we loaded the route supplied by the flight plan. After receiving an updated clearance; we loaded the new route. The new route included the WYNDE 4 arrival into ORD. En route to ORD the First Officer briefed the arrival and runway that was selected to land in ORD. The route was double checked by both of us. Somewhere around the FNT VOR; it appeared that the FMC had a momentary malfunction. The route came up but before we could check the route; we had passed FNT and the FMC started toward DEWIT Intersection. The Controller asked if we were heading toward EMMMA Intersection that was on the arrival. I responded that we were past EMMMA as; (looking at the FMC) EMMMA Intersection had disappeared. The Controller advised that we were 3 miles southeast of EMMMA. He then cleared us to GRR to rejoin the arrival. The First Officer entered GRR in the FMC and we proceeded to GRR. I asked the Controller is there were any separation problems; and he responded NO and there were no problems. Since we were within 3 miles of EMMMA when the problem was resolved; it appears that there were no pilot deviations before the correction. As for the FMC; it appeared that EMMMA and LTOUR intersections had disappeared. GRR was in the box and the First Officer just brought up GRR to get back on the arrival. I made a logbook entry as to the failure of the FMC.
Data retrieved from NASA's ASRS site as of July 2013 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.