Cockpit Transcript Reveals Pilot Panic After United Boeing 737 MAX Skids Off Houston Runway

January 1, 2026 at 09:57 PM•3 min read

United Airlines Boeing 737-8 MAX veered off a wet Houston runway on March 8, 2024; NTSB documents reveal pilot concern over braking procedures and the resulting excursion.

Key Points

1United Flight UA2477, a Boeing 737-8 MAX, skidded off a wet runway at Houston's George Bush Intercontinental Airport on March 8, 2024.
2NTSB documents revealed the captain misjudged the runway condition (3/3/3, slippery when wet) and used a low autobrake setting, delaying manual braking.
3Cockpit audio captured the captain's panic and apology after the aircraft failed to decelerate sufficiently, resulting in substantial damage to the left main landing gear.
4The investigation highlights risks associated with runway condition assessment and external pressure to expedite runway exit.

Newly released documents detail a United Boeing 737 MAX runway excursion incident. The aircraft, a Boeing 737-8 MAX, skidded off the tarmac. This happened after landing at George Bush Intercontinental Airport (IAH) in Houston, Texas. The incident occurred on a wet runway on March 8, 2024. No injuries were reported among the 160 passengers and six crew members.

Incident Details and Cockpit Transcript

The flight, UA2477, originated from Memphis, Tennessee. Surveillance footage captured the aircraft unable to slow sufficiently. It veered off the paved surface while attempting to exit the runway. The plane came to rest on the grass beside the runway. The left main landing gear separated after hitting a concrete structure.

The National Transportation Safety Board (NTSB) released a public docket. This included the cockpit voice recorder transcript. The audio revealed the conversation between the two pilots. As the plane struggled to slow, the Captain stated, "Oh my god, I can't believe that happened." He repeatedly apologized to the First Officer. "Sorry, man, to get you into this mess," the Captain said. He also expressed concern about the incident appearing on social media. This NTSB cockpit transcript offers a rare look at the crew's immediate reaction.

NTSB Findings on Braking and Conditions

Investigators determined the aircraft failed to decelerate adequately. This was a key factor in the runway excursion incident. The NTSB preliminary report highlighted a misjudgment of conditions. The Captain recalled seeing a runway condition code of 5/5/5 (good braking). However, the actual code for runway 27 was 3/3/3. Code 3/3/3 indicates a wet runway landing with noticeably reduced braking.

Operational Factors

The Captain selected the lowest autobrake setting. He delayed manual braking until approximately 4,000 feet from the end. This decision was made to minimize runway occupancy and maximize comfort. It contradicted the airline's policy for uncertain conditions. An NTSB performance study confirmed the aircraft deceleration failure. Data showed the speed brakes retracted, disengaging the auto brakes. Reverse thrust was also reduced, further hindering the slowdown.

Air traffic control (ATC) also instructed the crew to "keep your speed up." This instruction may have contributed to the urgency to clear the runway. The investigation is ongoing to fully determine the probable cause.

Safety Implications for Commercial Aviation

This event underscores the importance of accurate runway condition assessment. It highlights the risks when flight crew procedures deviate from policy. Regulators like the FAA emphasize adherence to braking protocols. Misjudging a pilot braking action on a wet surface can be critical. This incident serves as a reminder for all commercial aviation safety stakeholders. It stresses the need for clear communication and threat briefing. It also raises questions about pressure to expedite runway exit. Industry bodies like IATA continuously review best practices. For more updates on global aviation news, visit the flying.flights commercial aviation news page.