2025-04 · NASA ASRS report 2229930
A319 flight crew reported during the initial approach. ATC cleared them for the visual for the runway. The captain set the altitude for 2000 feet instead of the published altitude of 2900 feet and as they were descending; they received an altitude alert from ATC.
Captain was the PF. Descending via the arrival for RWY XXR; before reaching the last fix on the arrival (ZZZZZ); ATC gave us 4;000ft; I don't recall if a Heading (HDG) was also given. As we were still descending to 4 thousand feet; ATC asked if airport was in sight. The reply was affirmative and we were cleared for the visual approach RWY XXR. CA selected direct to the FAF (ZZZZZ1) and set on the altitude window 2;000 ft (instead of the published ALT of 2;900 ft) thinking that that was the published minimum altitude for that segment. We kept descending; intending to slow and configure once at 2;000 ft. before reaching ZZZZZ1. As we are descending thru 2;900 ft; sometime after; ATC issues and altitude alert. Not aware until this moment that I had set the wrong ALT; neither my error was caught by PM; We descended below the minimum altitude (2;900) to the FAF. At 2;000 ft; reacting to the ATC ALT alert; PF disconnects Autopilot (AP); Flight Director (FD); and begins a climb back to a safe altitude. Shortly after ATC advises that the minimum altitude for our position was 2;300 ft. PF leveled off then; and continued decelerating and configuring for the final segment of the approach. Cause: The causal factor for this event; was not realizing the error PF made. As I looked to the approach plate to confirmed the ALT for the FAF while descending and flying direct to ZZZZZ1; I cannot clearly state why 2;000 ft was selected. Certainly selecting direct to the FAF also caused the distance to descent to be less leading me to rush the descent. This could have been avoided by simply staying on the arrival and join from there to the approach; this would have been the best choice as it provided more time and I could have seen the altitudes in the Multi-Function Flight Display (MFD) as well.
Near ZZZZZ intersection; ATC confirmed we had the field in sight and cleared us for the visual to XXR. Captain had briefed an expected visual; and we were using navigational approach data from Jepp chart; ILS XXR. I acknowledged to ATC we were cleared for the visual to RW XXR; and turned to look at the approach plate (the specific reason I do not remember); Captain quickly and firmly addressed to me we were cleared for the visual while adjusting the aircraft course direct to ZZZZZ1--within the parameters of our clearance; though it was unexpected; causing me to take a moment to consider why he cutout the other fixes before acknowledging the change to a direct to ZZZZZ1. While descending; I recognized we were lower than expected and indicated this to the Captain. I began to review the approach plate as the sight picture was to low in altitude and to distant from the airport; this is about when ATC instructed us to check our altitude as we were lower than the appropriate altitude. I checked the altitude for ZZZZZ1; which was 2900. We were at 2000. I indicated to the Captain we were too low and stated to ATC we were beginning a climb. Captain adjusted altitude and began a gradual climb; with ATC later indicating minimum altitude for our location was 2300. We were about 2400 at that time and I indicated to ATC 'we are above that altitude' (2300). Final was intercepted and altitude eventually aligned with completing the visual to a landing.Cause: I did not immediately realize the Captain changed the altitude to 2000 when he went direct to ZZZZZ1; I was ascertaining why he decided to go direct--this is; of course; when altitude limits on the original course were erased. I do not know if I unknowingly acknowledged the 2000. My actual acknowledgment was in reference to the course change; not altitude. My primary error; as pilot monitoring; was not confirming our altitude was consistent with present position and aligned with passing ZZZZZ at 2900.
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.