Air Carrier flight crew reported receiving an ATC low altitude alert during approach. The flight crew immediately climbed to assigned altitude and continued the approach.

Date: 2022-09 · Aircraft: B737-800 · Phase: approach

Anomalies: aircraft-equipment-problem-less-severe|deviation-altitude-excursion-from-assigned-altitude|deviation-altitude-overshoot|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-clearance|inflight-event-encounter-cftt-cfit

Synopsis

Air Carrier flight crew reported receiving an ATC low altitude alert during approach. The flight crew immediately climbed to assigned altitude and continued the approach.

Narrative

While on approach; we were turned onto a base leg by ATC and given a clearance to turn; slow and descend to 8000 ft. I responded to ATC. However; the Captain was in the middle of finding out his HUD was inoperative. He made the turn but did not dial in the altitude in the MCP window. He realized that he had not put an altitude in the MCP panel and queried me what the altitude was. Unfortunately; I told him the wrong altitude of 7000 ft. We were both heads up at that time; looking for the proceeding aircraft turning final. Leveling off at 7000 ft.; I had a feeling something was not right. At that point; ATC issued an Altitude Alert and told us to climb back to 8000 ft. We climbed back to 8000 ft.; turned final and intercepted the localizer and landed.Several things where big contributors. I was tired. I had been working PM trips then switched to a early AM wakeup call. After the event; I called in fatigued. Possibly recognizing my night of poor rest; I should have called in fatigued earlier. Second the failure of us not following our standards in setting the MCP panel. I should have queried ATC again to verify our altitude when I realized the Captain did not know what it was. Last; the Captain was tasked saturated with dealing with the inoperative HUD. This definitely was an added distraction and we both should have been more aware of it interfering with tasks at hand.

Second reporter narrative

While on downwind I was trying to get the HUD to work when we were given turn to base and descend clearance at the same time. I heard the turn while I was extending a line in the FMS for final and asked what the altitude was; my FO (First Officer) thought it was seven thousand but wasn't sure. Typical approach in ZZZ was talking so much and so fast we couldn't get a verification. I looked at the FAF fix and saw 7000 ft. and figured that was the clearance. Approach then called us and advised the clearance was 8000 ft. and climb back to 8000 ft. and we complied and continued the approach with no further incident.Distractions with the HUD; ZZZ Approach speaking so fast and so much were certainly additive conditions. Its very hard to continually track ZZZ and all of their clearances. Insist on verification of clearance. Take some of the load of the PF; like requiring the Pilot Monitoring to do all radio and FMS programing while below 10;000 ft.; or all the time for that matter. That way; the Pilot Flying can concentrate on flying the aircraft and listen better to ATC clearances.

More incidents for this aircraft family →

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