 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 MAX8 first officer reported an altitude deviation due to an intermediate level off by the aircraft automation.
| Attributes | |
| ACN | 1593701 |
| Time | |
| Date | 201811 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 454 Flight Crew Type 454 |
| Events | |
| Anomaly | Deviation - Altitude Undershoot Deviation - Procedural Clearance |
Narrative:
We were climbing from fl 330 given a clearance to fl 360. Aircraft briefly leveled at initial cruise altitude fl 340 before aircrew intervention. [Center] queried if we received the clearance to fl 360. As a result of the brief delay [center] issued brief off course vectors to both us and converging traffic. Causal factors were equipment: not much experience in maximum-800; as a result; still have to search for everything. Automation: upon receipt of fl 360 clearance and after the captain dialed the MCP altitude 36;000 ft; I should have; but failed to; ensured the cruise altitude reflected fl 360. Engaging the altitude intv button would have facilitated the process. The solution is to verify/verbalize/monitor. Verifying the CDU cruise altitude (navigation 2/3) would have prevented the temporary level off. Monitoring would have mitigated the delay at fl 340 but could have been timelier. As a relatively new first officer; I had not seen this issue. However; I could have done a better job with vvm (verbalize; verify; monitor) to back up the captain with his duties while flying. Had I seen the momentary level off; I might have been able to alert ATC of it; avoiding any confusion or deviation of what the expectations were.
Original NASA ASRS Text
Title: B737 MAX8 First Officer reported an altitude deviation due to an intermediate level off by the aircraft automation.
Narrative: We were climbing from FL 330 given a clearance to FL 360. Aircraft briefly leveled at initial cruise altitude FL 340 before Aircrew intervention. [Center] queried if we received the clearance to FL 360. As a result of the brief delay [Center] issued brief off course vectors to both us and converging traffic. Causal factors were equipment: not much experience in MAX-800; as a result; still have to search for everything. Automation: Upon receipt of FL 360 clearance and after the Captain dialed the MCP Altitude 36;000 FT; I should have; but failed to; ensured the cruise altitude reflected FL 360. Engaging the ALT INTV button would have facilitated the process. The solution is to Verify/Verbalize/Monitor. Verifying the CDU cruise altitude (NAV 2/3) would have prevented the temporary level off. Monitoring would have mitigated the delay at FL 340 but could have been timelier. As a relatively new First Officer; I had not seen this issue. However; I could have done a better job with VVM (Verbalize; Verify; Monitor) to back up the Captain with his duties while flying. Had I seen the momentary level off; I might have been able to alert ATC of it; avoiding any confusion or deviation of what the expectations were.
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.