A300 flight crew reported a controlled flight toward terrain event while being vectored for a visual approach in smoky/hazy conditions. ATC issued a low altitude alert to crew who climbed back to the cleared altitude and subsequently made an uneventful landing.
Synopsis
A300 flight crew reported a controlled flight toward terrain event while being vectored for a visual approach in smoky/hazy conditions. ATC issued a low altitude alert to crew who climbed back to the cleared altitude and subsequently made an uneventful landing.
Narrative
Weather was a broken ceiling with tops at 5500 and bottoms at 4500. We were VFR below 4500 feet. Air quality was condition moderate.On a 3000 feet downwind we were turned to a heading of 050 (80 degree cut); cleared to descend to 2500; and asked if we had the runway in sight. I was PM; repeated the directions; and said we were looking." PF started his turn; set 2500; and in the turn looked for the field.We were about 9 miles from the field; so wasn't easy to find at that altitude. There was a slight haze from the fires. Visual details were slightly monochromatic.As we rolled out on the 050 heading I felt even lower… vertical angle to the field was off when I called "field in sight." I then realized we were at 2000 feet and descending. We were still a mile from ZZZZZ [fix]; which is at 2600 feet. My first thought was; "we are cleared the visual" it's ok … then did the math and realized we were uncomfortably low. About that time we received the aircraft "One Thousand" cockpit call; tower said they had a low alert warning and I told the PF to climb back to 2500 feet. We hit ZZZZZ on altitude; fully configured; and returned to our approach. We were a little high and fast for most of the approach… wanting to be on the high side after that event.Landed safely; took a longer than normal debrief and again talked about it over dinner.Lessons Learned: Below Average on PM duties. PF was an excellent stick. On departure; he was on and on; very tight control of all axes. I let my guard down on the arrival; when it should've been higher. With the airport elevation at 950 feet I should have done the math sooner. I also didn't see what mode the PF selected on the descent from 3000 to 2500. I thought it was LVL/CH; but might have captured Vertical Speed and that's why it went below 2500. And in hind-sight he might have put in 2000 feet… but even so; it went below 2000 while PF was still in autopilot.Fatigue was not a factor; but complacency was. I did not realize we went right through 2500 ft in the turn. Normally; as PF; I set my wicket at the IAF. As PM I should have been more involved with that target; but I wasn't. Cause: Lack of altitude awareness. It was set; but both sets of eyes were looking for the field and not realizing we descended below our set altitude.Suggestions: Stick to the basics: Altitude; Heading; and Airspeed. I hate forgetting something I've learned; applied and taught for 30 years."
Second reporter narrative
PF for a single leg from ZZZ1 to ZZZ. Takeoff; departure and cruise were uneventful. Vectored letdown to a downwind then dogleg/base heading 050 for RWY XX at 3000 feet. On a heading of 050; tower states field at 2 o'clock; call the field in sight. We report field in sight. I hear descend 2000 and cleared visual approach Runway XX. I select 2000 ; LVL/CH and arm approach while slowing to configure. The FAF (ZZZZZ [Fix]) is at 2600 ft. which I had briefed however; it did not enter my mind that I had dialed an altitude below the FAF. As we started to approach ZZZZZ the CA states we are low and we're only cleared to 2500 ft. I instinctively dialed 2500 ft. into the FCP (Flight Control Panel) thinking we would level off there. We must have been below as the altitude never captured which allowed the descent to continue. Approaching ZZZZZ; I became somewhat channelized on finding the runway due to haze when the autopilot kicks off while still descending. We near simultaneously receive the 1000 ft. cockpit call and tower reports a low altitude alert. At that time the CA directs a climb back to 2500 ft. which we execute and then request and receive confirmation from the tower that we are on glide path. The approach is eventually stabilized and landing uneventful.Cause: PF error in visual approach procedures. CRM breakdown in communication. Channelized attention and poor cross-check. Suggestions: When proceeding into a visual field; I will foot stomp the FAF altitude as a no lower than altitude. Visualize and brief PF/PM responsibilities for the arrival and approach. Reset my personal procedures to instrument basics regardless of weather conditions. Finally; ensure all aircraft states are fully verbalized and acknowledged with clarity.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.