B737 flight crew reported receiving a low altitude alert and a descent rate inquiry from ATC during the final approach segment of an RNAV approach. Flight crew over-corrected manually after failing to set the appropriate altitude in the alerter.

Date: 2026-01 · Aircraft: B737 Undifferentiated or Other Model · Phase: approach

Anomalies: Deviation altitude overshootInflight event encounter controlled flight toward/into terrainInflight event encounter unstabilized approach

Synopsis

B737 flight crew reported receiving a low altitude alert and a descent rate inquiry from ATC during the final approach segment of an RNAV approach. Flight crew over-corrected manually after failing to set the appropriate altitude in the alerter.

Narrative

On arrival into ZZZ we were cleared direct ZZZZZ RNAV W XX. Outside ZZZZZ 1600 was set in the FMC and we initiated the approach. Approaching ZZZZZ1 the FMC began to level off. Realizing I had not complied with my own briefing of setting touchdown inside ZZZZZ2; touchdown was set and I disconnected the Autopilot and hand flew to regain the path. Initially overcorrecting; I went below path before correcting back to path. The overcorrection prompted a low alt alert with tower; which they queried about; and we replied corrections were being made. The approach was stabilized above 500' and a normal landing was made.

Second reporter narrative

Flying the RNAV W to XX into ZZZ; we were vectored behind an A350 on the same approach. We were told to slow from 250 to 210; then 190; then 170 until ZZZZZ1. We were visual with the air carrier traffic ahead and were cleared the approach and cleared to land RWY XX. Airbus ahead of us was cleared to land; and tower also queried them as to why they were almost a mile east of course. They said that winds were very strong. We continued to fly the approach on the magenta line and at the required speeds from approach and tower. We kept the A350 visual as we commenced the approach.Passing ZZZZZ1; we were fully configured with landing checklist complete; when captain saw the jet leveling off and said touchdown zone". I looked up to see ALT HOLD with the FAF altitude of 1600 still set; and the Flight Directors were not commanding a descent on the glide path. I immediately spun the TDZE to 100' as the PF disconnected the autopilot to recapture the VNAV descent path and get us back to the glide slope. While doublechecking the TDZE altitude on the approach plate; I heard tower ask us to check our descent rate. Apparently; the PF had momentarily gone below vertical flight path; which he quickly corrected it and had stabilized as I responded to tower.Between ZZZZZ1 and ZZZZZ3 we had a brief glide path deviation where we were below VNAV glide path. The remainder of the approach and landing were uneventful. Both pilots got distracted with the traffic in front of us and missed setting TDZE at ZZZZZ2; which would have prevented the error."

More incidents for this aircraft family →

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