B737 flight crew reported receiving a low altitude alert from ATC during approach. Flight crew corrected and continued approach.
Synopsis
B737 flight crew reported receiving a low altitude alert from ATC during approach. Flight crew corrected and continued approach.
Narrative
ZZZZZ arrival; vectors to visual approach XXR from ZZZZZ. Initial vector to base was a turn to 080deg and descend to 9;000 MSL . In the turn to base flaps were set 5 and speed 210. Next call was left 060 190 or greater and report field in sight. PM acknowledged field in sight. Controller responded with turn left HDG 020; maintain 170 or greater to ZZZZZ1; 8000 feet; cleared for the visual XXR. PM read back 020; 170 or greater till ZZZZZ1; 8000 feet; cleared visual XXR. Controller then gave a frequency change to contact tower. During this crew became task saturated while simultaneously changing Mode Control Panel (MCP) command speed; heading and APP mode was selected by PF and altitude and frequency by PM. PM mistakenly selected altitude window to 6000' and PF mistakenly confirmed 6000 feet. PF called for Gear down flaps 15 in the transition to 170 knots and selected Level change while PM made the initial call to Tower and received landing clearance at approximately 10nm to the field. As both PM and PF became focused on slowing to approach speed and configuring for landing PM realized well below glideslope for the ILS backup data to the visual approach and told the PF 'no lower' shortly after the crew began a correction for altitude the tower also made a low altitude alert call over tower frequency. PM directed to disconnect automation at approximately 6;400 feet and begin a climb. PF disconnected automation; started to climb and PM selected V/S on the MCP and gave a 500fpm rate of climb for vertical guidance. Visual contact with the runway environment; PAPI and clearance from obstacles was maintained at all times. Glideslope from the ILS was intercepted and all checks were completed by 1000' with stable parameters met by 500' for an uneventful landing.
Second reporter narrative
Following descent via ZZZZZ arrival; vectors to visual approach XXR from ZZZZZ. ATC directed turn to base HDG 080 and descend to 9;000 MSL . In the turn to base flaps were set 5 and speed 210. Subsequent turn was left 060 and 190KIAS. PM acknowledged field in sight. Controller responded with turn left HDG 020; maintain 170KIAS or greater to ZZZZZ1; 8000 feet; cleared for the visual XXR. PM provided correct readback to controller; but did not set the lower altitude in MCP. Controller then gave a frequency change to contact tower. During this crew became task saturated while simultaneously changing MCP command speed; switching radio frequency; dialing heading; and selecting APP mode. PF prompted the PM to set the lower altitude; but mistakenly called for 6;000' instead of 8;000'. PM selected altitude window to 6000' which was reconfirmed (erroneously by PF). PF called for Gear down; flaps 15 in the transition to 170 knots and selected Level change while PM made the initial call to Tower and received landing clearance. As both PM and PF became focused on slowing to approach speed and configuring for landing; PF recognized the outside site picture looked too flat. PM directed PF 'no lower' - shortly after the crew began a climb to correct for altitude. The tower also made a low altitude alert call over tower frequency. PF disconnected autopilot at approximately 6;400 feet and begin a climb. Visual contact with the runway environment and PAPI was maintained throughout. Clearance from obstacles was maintained at all times. Glideslope from the ILS was intercepted and all checks were completed by 1000' with stable parameters met by 500' for an uneventful landing.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.