2025-06 · NASA ASRS report 2250489
Air carrier flight crew reported getting low on final approach to SAN; and as they noticed the deviation ATC gave them a low altitude warning. The flight landed safely after executing a go-around.
Passed over FAP (Final Approach Point) at 1600 MSL IMC and I crosschecked altitude and realized we were 400 feet low for TOKOE altitude. I verbalized to FO 'we are low and I think we need to go around.' Just then we popped out of overcast and I initiated the Go-around with FO concurring. As we started the go-around tower called Aircraft X 'low altitude alert'. FO acknowledged and told them we were executing missed approach. Missed approach was uneventful. Approach kept us 230 until LYNDI. In latter portion of the LUCKI 1 arrival approach gave us 230 kts till advised. They were keeping everyone fast and just inside LYNDI we requested slower. They gave us 170 or greater and we commenced expeditiously slowing and configuring for a planned F40 approach. LNAV AND VNAV PTH were engaged and FAF alt already set; path looked good and set TD zone altitude. We had to slow and configure aggressively and all seemed good and arrived at F40 and target speed a few miles outside of TOKOE. The FO remembers looking at Vert Dev on Prog pg 4 just a couple miles outside of TOKOE and the deviation was less than 100' and vertical path looked good. Neither the FO or I noted VNAV PTH FMA reverting to something else. We VVM'd (Verbalized; Verify; Monitor) the TOKOE altitude and decided to execute the missed approach. We thoroughly debriefed the approach and could not determine the reason/actions that lead us to being low and below path at the FAP.
Arrived via the Lucki1 RNAV arrival; cleared approach with instruction to maintain 230 knots until advised. We set FAP altitude (2000) when cleared for the approach. Inside Lyndi we set TDZE (100) and I requested slower speed. 170 or greater was approved; and the PF CA slowed on schedule accordingly. Changed to tower frequency; while checking PROG page 4/4 for vertical deviation within limits; which it was. With F40 set; Captain requested the Landing Checklist. After I verbalized and visually confirmed the checklist items; the Captain stated we were low and we should probably go-around. I concurred. As the Captain initiated the go-around; tower called a low altitude alert. A normal go-around was performed with vectors back for the same RNAV approach to a normal F40 landing.
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.