37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1009111 |
Time | |
Date | 201205 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZKC.ARTCC |
State Reference | KS |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | EMB ERJ 170/175 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Altitude Undershoot Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance |
Narrative:
We were in cruise at FL370 when given a descent to FL190 and to cross rba at or below FL230. Earlier; we had been given a crossing restriction at rba of FL240; and when entered saw an inverse video climb (cyan) above the altitude of FL240 on the right side of the FMS screen. When the crossing restriction was changed to FL230B; the climb annunciation remained. We discussed this; found it very curious; but continued. As I began the descent into mci; I utilized the profile mode of the mfd to assure compliance with the crossing restriction. It displayed that I would easily meet the requirements of the crossing restrictions. As we got closer; we were involved with the set up and the briefing of the approach and the in range call. I kept the descent as displayed on the profile view in my scan; but then realized about three miles northwest of rba that I was too high. It wasn't even close! I was at FL280; missing by about 5;000 ft. Again; the profile view depicted completely contradictory information. The controller was very understanding and said the restriction was not really critical; but my concern is that if this happens in a dense traffic area it is a problem. I'm not sure why our honeywell FMS is displaying such contradictory information; but it disturbs me.greater pressure needs to be put on honeywell to provide better programming of their equipment. This isn't new; these bugs need to be a thing of the past. The advantages of this technology are lost if we have to rely on cami procedures so heavily. The purpose is defeated. It needs to work as advertised; and after this many years; honeywell needs to have their act together. It isn't. The profile view; upon which we rely to be VNAV capable; has to give us reliable information. My scan was acceptable; the information was not.
Original NASA ASRS Text
Title: An ERJ-190 Captain advised his FMS 'Profile Mode' display failed to properly display a programmed crossing restriction showing them to be on profile when they were; in fact; about 5;000 FT high.
Narrative: We were in cruise at FL370 when given a descent to FL190 and to cross RBA at or below FL230. Earlier; we had been given a crossing restriction at RBA of FL240; and when entered saw an inverse video CLB (cyan) above the altitude of FL240 on the right side of the FMS screen. When the crossing restriction was changed to FL230B; the CLB annunciation remained. We discussed this; found it very curious; but continued. As I began the descent into MCI; I utilized the profile mode of the MFD to assure compliance with the crossing restriction. It displayed that I would easily meet the requirements of the crossing restrictions. As we got closer; we were involved with the set up and the briefing of the approach and the in range call. I kept the descent as displayed on the profile view in my scan; but then realized about three miles Northwest of RBA that I was too high. It wasn't even close! I was at FL280; missing by about 5;000 FT. Again; the profile view depicted completely contradictory information. The Controller was very understanding and said the restriction was not really critical; but my concern is that if this happens in a dense traffic area it is a problem. I'm not sure why our Honeywell FMS is displaying such contradictory information; but it disturbs me.Greater pressure needs to be put on Honeywell to provide better programming of their equipment. This isn't new; these bugs need to be a thing of the past. The advantages of this technology are lost if we HAVE to rely on CAMI procedures so heavily. The purpose is defeated. It needs to work as advertised; and after this many years; Honeywell needs to have their act together. It isn't. The profile view; upon which we rely to be VNAV capable; has to give us reliable information. My scan was acceptable; the information was not.
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.