Air carrier pilot reported a temporary loss of aircraft control caused by an incorrect aircraft handling while correcting a heading deviation. The airspeed and heading deviations were corrected which enabled the flight to continue uneventfully.

Date: 2023-11 · Aircraft: B737-800 · Phase: cruise

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-loss-of-aircraft-control

Synopsis

Air carrier pilot reported a temporary loss of aircraft control caused by an incorrect aircraft handling while correcting a heading deviation. The airspeed and heading deviations were corrected which enabled the flight to continue uneventfully.

Narrative

While at FL360 inbound to ZZZZ; we were given unexpected present position hold instructions for ATC spacing. The PF (Pilot Flying) incorrectly input the direction of the holding turn in the FMS; and executed the hold before PM (Pilot Monitoring) confirmation. When the aircraft turned the incorrect direction; the PF disengaged the autopilot to correct the turn direction. While correcting the turn; the airplane banked beyond 30 degrees; and the Bank Angle aural warning was triggered. In addition the aircraft had slowed to holding speed; and the PLI symbology appeared on the PFD; warning of an approach to stall speeds. No stall indications occurred. While the PF was correcting the bank angle; I manually increased the speed to 250 kt; well above the indicated stall speed. I set up the flight director panel for the PF; and he then re-engaged the auto pilot. The aircraft was stable in holding after the autopilot was re-engaged. After one 360 degree turn in holding ATC cleared us direct to the beginning of the STAR. The rest of the flight and landing was uneventful. The unexpected and short notice holding clearance paired with the PF not confirming the FMS programming before executing were causal factors. In addition; the PF disconnecting the autopilot; instead of correcting with Heading mode compounded the confusion and workload on the flight deck. Following company SOPs on FMC data entry; along with maximizing the proper use of automation would have prevented these errors.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.