B737 MAX 9 flight crew reported encountering wake turbulence from preceding B737 on approach to SAN. Tower issued go-around clearance at low altitude after the preceding B737 failed to clear the runway in time for a safe landing.

2023-09 · NASA ASRS report 2037409

Date: 2023-09 · Aircraft: B737 MAX 9 · Phase: approach

Anomalies: conflict-ground-conflict|less-severe|inflight-event-encounter-wake-vortex-encounter

Synopsis

B737 MAX 9 flight crew reported encountering wake turbulence from preceding B737 on approach to SAN. Tower issued go-around clearance at low altitude after the preceding B737 failed to clear the runway in time for a safe landing.

Narrative

Arriving on the LUCKI1; cleared for approach; we loaded and were flying the LYNDI transition for the RNP Z 27. ATC provided several speed reductions; which were effectively managed. Previous A/C was a 737; being vectored on from the north downwind; we had that aircraft in sight as they were being vectored.They were given an intercept to final and cleared for the approach; at which point we visually observed them turning from that intercept heading to the south; 90 degrees away from the final. ATC noticed and issued urgent instructions to turn back; they casually responded that they were in the turn. We were asked and called them in sight; cleared for the visual to follow.Following them down final; they were all over the place. They pulled away from us; but were extremely high - this made it a challenge to judge our distance on the ND (Navigation Display)/ TCAS using only the distance and not the altitude differential. During the approach we experienced significant wake turbulence while in full manual controls requiring large aileron input to stop the roll. That episode lasted approximately 5-10 seconds in the area of 3-4000 ft; other shorter and more benign wake turbulence events were also encountered during the approach. During this time; the B737 went from being extremely high on approach to very low; while we remained on the vertical path. Tower was working us as well as several GA targets over downtown - ATC was about to have one cross the final in front of us when ATC changed their mind due to inadequate spacing and then told us to be ready for a go around. The B737 was told to expedite off; however had not fully vacated the runway and Tower called the go around at approximately 200 ft.The go around was performed nominally and we were vectored back for a visual approach. The Final Controller remarked that spacing had seemed ok; that the B737 hit the brakes hard.

Second reporter narrative

Captain and I were on our approach into SAN on RWY 27 on a VMC day. At 6;000 ft near the IAF (LYNDI) we were cleared for the visual into 27. Captain disengaged the autopilot and began hand flying. We were following an aircraft coming in from the other side from the west. Traffic in front of us; a B737 overshot the final resulting in their airplane being high on approach. Their mistake also led to the decrease in separation between us and them. Without confirming; the B737 decided to slow way down and do a steep dive making us ride their wake all the way down to approach. As a result; we queried Approach to see if we can slow down to create more distance. I do not recall the exact airspeed but we were somewhere around 200-210 KIAS. Somewhere between 5;000 ft and the runway; we were in their wake and airplane began to roll to the right. Captain gave it a full aileron input to the left to keep the plane coordinated. No upset was experienced as per the definition calls for a larger bank angle. However we were definitely in an undesirable aircraft state for a couple seconds before recovering. Aircraft was brought under control and we continued the approach. Around 500 ft Tower acknowledged the loss of separation and prepared us for a go-around. Eventually around 200 ft ish; Tower instructed us to go-around.We did a left turn lap and landed on the 2nd time with no other events noted.

NASA callback

Reporter stated his report covered all aspects of the encounter.

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

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.