Miami Air 737-800 Runway Excursion Into St. Johns River (N732MA)

On May 3, 2019, Miami Air International Flight 293, a Boeing 737-81Q (N732MA), departed the end of Runway 10 while landing at Jacksonville Naval Air Station (NIP) in Jacksonville, Florida. The airplane crossed the runway end, impacted a seawall, and came to rest in shallow water in the St. Johns River; one minor injury was reported and the remaining occupants were not injured. Federal investigators examined the approach and landing performance, runway surface conditions, and operator procedures associated with the runway excursion.

Accident Summary

What Happened

According to the NTSB final report, the flight’s takeoff, climb, and cruise were uneventful, and the crew deviated around weather as it approached the Jacksonville area. During the arrival, air traffic control advised the crew of moderate-to-heavy precipitation near the airfield, and the crew discussed runway changes before ultimately flying the RNAV (GPS) approach to Runway 10 at NIP. Runway 10 was ungrooved and had a displaced threshold that left 8,006 feet of available landing distance.

As the airplane descended on final, the report describes increasing airspeed, an approach that became high on the glidepath, and enhanced ground proximity warning system “sink rate” alerts in the final seconds. Touchdown occurred about 1,580 feet beyond the displaced threshold, beyond the operator’s specified touchdown zone, and the airplane was still above target speed with a tailwind component. The speedbrakes were not placed in the armed position before landing and deployed several seconds after touchdown.

After touchdown, the captain applied braking and deployed reverse thrust on the No. 2 (right) engine; the No. 1 (left) thrust reverser was inoperative and deferred in accordance with the minimum equipment list. The crew reported the airplane did not decelerate as expected and began drifting laterally. The airplane exited the paved runway surface, crossed the end of the runway, impacted a seawall, and came to rest in the St. Johns River, after which the crew initiated an emergency evacuation.

Aircraft and Operational Context

The aircraft was a Boeing 737-81Q, N732MA, operated as a Part 121 supplemental non-scheduled passenger flight. The captain was the pilot flying and also served as a check airman while the first officer, who had limited experience in the Boeing 737, was completing operating experience training. Dispatch paperwork and operational briefings anticipated convective activity near the destination around the scheduled arrival time.

The NTSB report describes heavy rain and thunderstorms in the vicinity of the airfield during the approach and landing window. Observations around the accident time indicated heavy rain, thunderstorms, and a rapid rainfall rate consistent with standing water developing on portions of the runway surface. The report also describes the runway’s characteristics, including the ungrooved surface and displaced threshold, and notes that the airfield had short-field arresting gear rigged on Runway 10.

Accident Investigation

As explained in our overview of the NTSB investigation process, investigations typically combine recorded data, weather information, runway characteristics, and physical evidence to reconstruct how an approach and landing unfolded before conclusions are reached. In this accident, the NTSB reviewed flight recorder data and conducted a performance study to estimate the airplane’s position, speed, and deceleration during the approach and landing roll. The report also examined runway macrotexture, drainage and cross-slope, rainfall rates, and evidence from tire marks and the airplane’s trajectory beyond the pavement.

The NTSB concluded that the airplane experienced an extreme loss of braking friction due to heavy rain and water depth on the ungrooved runway, resulting in viscous hydroplaning. The report explains that, even with the crew’s approach speed, tailwind, and delayed speedbrake deployment, the airplane would have been able to stop on the runway if it had achieved braking friction consistent with “good” wet-runway assumptions. However, standing water on portions of the runway reduced braking friction to levels consistent with viscous hydroplaning, and performance calculations indicated the airplane could not have stopped before reaching the end of the paved runway under the conditions present.

Operational and Regulatory Issues

The report describes how the tailwind, excessive approach speed, and delayed speedbrake deployment increased the energy with which the airplane departed the runway and impacted the seawall. It also found that the approach did not meet the operator’s stabilized approach criteria, with cues that would typically require a go-around under standard operating procedures, including excessive airspeed, high glidepath indications, and descent-rate alerts. The report discusses factors that contributed to continuing an unstabilized approach, including plan continuation bias, increased workload, and limited first-officer experience.

The NTSB also addressed runway-condition assessment and landing-distance decision-making. It found that the operator’s guidance for evaluating braking conditions and conducting en route landing distance assessments was inadequate for the conditions encountered, and it discussed FAA Safety Alerts for Operators concerning landing performance shortfalls on wet runways in moderate-to-heavy rain. The report emphasized that when rainfall intensity suggests the runway may be more than merely “wet,” pilots may need to assume worse braking action for time-of-arrival landing performance and consider go-around, holding, or diversion if conditions exceed acceptable limits.

Aviation Accident Litigation

Separate from the safety investigation, runway excursion events can lead to civil claims involving passenger injuries, evacuation-related issues, and property damage, as described in our overview of aviation accident litigation. In a case involving runway surface conditions, the evidentiary record often includes performance calculations, operator procedures, dispatch and crew briefings, runway maintenance and drainage documentation, and the timing and content of weather and braking-action information available to decision-makers. The analysis is fact-dependent and should follow the verified investigative record.

Depending on the facts developed, litigation may also examine how organizational guidance addressed wet-runway stopping margins, how landing-distance assessments were expected to be performed, and whether operational policies adequately accounted for known wet-runway performance shortfalls in moderate-to-heavy rain. Similar categories of operational and procedural issues arise in matters described in our representative aviation matters, particularly when the accident sequence involves an interaction between weather, runway condition, and flight crew decision-making under time constraints.

Where cases resolve, outcomes typically turn on detailed technical proof and individualized damages evidence, and examples of resolved aviation matters are summarized in our collection of selected aviation verdicts and settlements. In runway excursion cases, that proof often includes expert analysis of stopping performance, runway condition characterization, and the relationship between approach profile and available stopping margin under the conditions actually present.

Broader patterns in civil outcomes can vary significantly based on event severity, injury mix, and operational setting, as discussed in our overview of aviation crash verdict trends. For this event, the NTSB’s findings centered on viscous hydroplaning from standing water on an ungrooved runway, with contributing factors related to operator guidance and the continuation of an unstabilized approach. Any civil evaluation should remain anchored to the documented performance evidence, procedures, and condition data developed in the official record.