2024-06 · NASA ASRS report 2129474
Air carrier flight crew reported on arrival they descended below the ATC assigned altitude resulting in flying towards terrain and ATC issuing an alert and climb. Air crew climbed to a safe altitude and landed safely at their destination airport.
After checking in with the final ZZZ Approach Controller descending via the ZZZZZ arrival. We requested direct to the point ZZZZZ1 on the RNAV Visual [Runway] XX at ZZZ. We were then cleared direct to ZZZZZ once passing 11;000 and descend and maintain 7000. Then we were cleared to descend and maintain 5200. ZZZZZ has a published altitude of 5000A; then we were instructed to report the runway insight at our 1 to 2 o'clock. As we got lower the airfield was a bit difficult to identify with it being at dusk and slightly hazy. Also; with ZZZ1 airport being close by we wanted to ensure we did not mistake the wrong airport. As we approached closer to ZZZZZ we were told by Approach to continue the approach and report runway insight. We then set 4500 in the altitude window for the next point ZZZZZ2 with VNAV engaged. As we started descending at about 4900 feet the controller asked if we were at 5200 and that the MVA is 5200 and to expedite climb back to 5200 and if we can't report the runway insight within the next 2 miles we would be vectored for a different approach. We were able to acquire the correct runway and were then cleared the approach. We were high on profile and slowed to final approach configuration and meet stabilized approach criteria prior to 1000 feet. The rest of the flight was uneventful and landed safely.
Coming into ZZZ we elected to fly the RNAV Visual [Runway] XX since the winds favored it and ATIS was calling 10sm and clear. Approaching ZZZZZ1 I was unable get a visual of the airport since it was actually a little dark and hazy and I had not landed at ZZZ since Day 0. Approach said what I thought was cleared for the visual" and report the airport in sight; but in hindsight I think they said fly the published track only. We were high so I turned off autopilot and had the FO start putting in lower step down altitudes until I could get back on VNAV path or get the airport in sight. The FO had recently flown the approach and had the airport in sight the entire time. While approaching ZZZZZ2 (an above 4;500ft fix) descending through 4;900ft we got a low altitude alert from ATC so I started a climb and put autopilot back on. FO and I had a quick discussion about whether we were cleared or told to fly the track; regardless; about that time I got a visual of the airport. ATC asked us if we still wanted to fly it since we were very high now and I said yes so they cleared us for the visual. We were already near flaps 40 speed so it was not difficult to get back down on path prior to 1000ft. We had an uneventful landing to [Runway] XX."
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.