 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A321 first officer reported that even though the FMS was correctly programmed the aircraft descended below the entered altitude.
| Attributes | |
| ACN | 1570088 |
| Time | |
| Date | 201808 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | SCT.TRACON |
| State Reference | CA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | A321 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
During arrival preparation both the captain and I checked all the crossing altitudes to be correct and verified that there was no discrepancy on predicted flight path. When issued descend via clearance; I put in 4;300 feet. At top of descent I started down. As we approached [the] waypoint I saw that the aircraft was going to fly below the required altitude and immediately hit altitude hold to stop the descent. Even though the FMC (flight management computer) had the correct altitudes in; and the path showed we would cross in the required altitude window; the aircraft was diving low. All was done correctly and the FMA (flight mode annunciator) windows indicated all was correct; the aircraft was doing its own thing. This arrival descends through high rocky terrain. Had this threat not been trapped; a GPWS event was a real possibility. Even though I hit altitude hold as soon as I saw what was going to happen; we still went approximately 300 feet low on the crossing window.teach aircrews to never trust the airbus programming and maintain constant vigilance. Even though I am very comfortable on the airbus this was a new one on me.
Original NASA ASRS Text
Title: A321 First Officer reported that even though the FMS was correctly programmed the aircraft descended below the entered altitude.
Narrative: During arrival preparation both the Captain and I checked all the crossing altitudes to be correct and verified that there was no discrepancy on predicted flight path. When issued descend via clearance; I put in 4;300 feet. At top of descent I started down. As we approached [the] waypoint I saw that the aircraft was going to fly below the required altitude and immediately hit ALT Hold to stop the descent. Even though the FMC (Flight Management Computer) had the correct altitudes in; AND the PATH showed we would cross in the required altitude window; the aircraft was diving low. ALL was done correctly and the FMA (Flight Mode Annunciator) windows indicated all was correct; the aircraft was doing its own thing. This arrival descends through high rocky terrain. Had this threat not been trapped; a GPWS event was a real possibility. Even though I hit ALT HOLD as soon as I saw what was going to happen; we still went approximately 300 feet low on the crossing window.Teach aircrews to never trust the Airbus programming and maintain constant vigilance. Even though I am very comfortable on the Airbus this was a new one on me.
Data retrieved from NASA's ASRS site 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.