 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An ERJ170 flight crew failed to note the duplication of waypoint musca in their legs page after programming the STAR and expected ILS approach into the FMS on arrival to dtw. Track and altitude deviations resulted when the autoflight system attempted to return to musca as the aircraft approach the subsequent fix; gloze.
| Attributes | |
| ACN | 937132 |
| Time | |
| Date | 201102 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | D21.TRACON |
| State Reference | MI |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 170/175 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR GEMNI TWO |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Pilot Not Flying First Officer |
| Person 2 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Conflict Airborne Conflict Deviation - Altitude Overshoot Deviation - Track / Heading All Types |
Narrative:
We were on the gemni two arrival into dtw. We had passed musca and were headed to gloze. Prior to reaching gloze; the FMS cycled back to musca and the aircraft began a left turn back to the fix. The captain was the pilot flying and; upon query by ATC; used the tcs button to intervene and turn the aircraft back toward the fix gloze. As he made the correction we were asked by ATC where we were turning and were subsequently given a new heading and reconfirmation of altitude (we experienced an altitude deviation of less than 200 ft low during the correction). The controller asked why we had turned and advised we had almost created a traffic conflict. I told him that there had been an aberration with the FMS. This event could be avoided in the future by more careful verification of points along the route after addition of runways or arrivals and added vigilance to the FMS as it cycles from point to point; as well as quicker intervention in the event of an unscheduled turn.
Original NASA ASRS Text
Title: An ERJ170 flight crew failed to note the duplication of waypoint MUSCA in their legs page after programming the STAR and expected ILS approach into the FMS on arrival to DTW. Track and altitude deviations resulted when the autoflight system attempted to return to MUSCA as the aircraft approach the subsequent fix; GLOZE.
Narrative: We were on the GEMNI Two Arrival into DTW. We had passed MUSCA and were headed to GLOZE. Prior to reaching GLOZE; the FMS cycled back to MUSCA and the aircraft began a left turn back to the fix. The Captain was the pilot flying and; upon query by ATC; used the TCS button to intervene and turn the aircraft back toward the fix GLOZE. As he made the correction we were asked by ATC where we were turning and were subsequently given a new heading and reconfirmation of altitude (we experienced an altitude deviation of less than 200 FT low during the correction). The Controller asked why we had turned and advised we had almost created a traffic conflict. I told him that there had been an aberration with the FMS. This event could be avoided in the future by more careful verification of points along the route after addition of runways or arrivals and added vigilance to the FMS as it cycles from point to point; as well as quicker intervention in the event of an unscheduled turn.
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.