The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB DCA24FA120 · Final report

Boeing 737-8 accident near Houston, Texas, March 8, 2024

On March 8, 2024 at about 1:58 pm local time, a 2023 Boeing 737-8, registered N27290, was substantially damaged in an accident during taxi (from runway) near Houston, Texas (George Bush Intcntl/Houston airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 166 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The captain's decision not to establish and maintain deceleration devices in accordance with company training and standard operating procedures.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 8, 2024 · about 1:58 pm local time
Place
Houston, Texas · George Bush Intcntl/Houston · map
Type
Accident
Injuries
No one was hurt; 166 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Boeing 737-8, built 2023 · all 737-8s on the register
Registration
N27290 · registry record · serial 44309
Damage
Substantial damage
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative final · quoted from the NTSB record

United Airlines flight 2477 departed taxiway SC while turning off of runway 27 at high speed after landing at George Bush Houston Intercontinental Airport (IAH), Houston, Texas. As flight 2477 departed the paved taxiway, the left main landing gear impacted a concrete structure recessed in the ground adjacent to taxiway SC. This impact resulted in separation of the left main landing gear. Postaccident examination of the airplane found nothing anomalous that precluded normal operation of the landing gear and the wheel braking system. Furthermore, the flight crew reported no anomalous operation of the autobrake system, the speedbrake system, or the thrust reversers during the landing rollout. The captain stated, and the flight data recorder (FDR) data confirmed, that he retracted the speedbrakes about 6 seconds after landing in order to turn off the autobrakes. Additionally, only engine idle reverse thrust was used after touchdown. By not using maximum reverse thrust upon touchdown and by turning off the autobrakes shortly after landing, the captain failed to follow multiple company standard operating procedures (SOPs) that would have assured deceleration of the airplane. The captain delayed application of maximum manual wheel braking after turning off the autobrakes, and the airplane remained at high speed as it neared the end of the runway. Speedbrake deployment increases wing aerodynamic drag and reduces wing aerodynamic lift, thereby slowing the airplane and increasing main landing gear wheel loading for more effective wheel braking. By stowing the speedbrakes shortly after landing, the wheel brakes were less effective in decelerating the airplane when the captain eventually applied maximum manual wheel braking. Had the captain used timely and effective manual wheel braking with the speedbrakes deployed, the airplane would have been capable of decelerating to a safe taxi speed before exiting the runway. The flight crew did not conduct a thorough briefing of the airplane’s landing performance when the captain changed the autobrake setting from 2 to 1, which decreased the target deceleration rate for the autobrake system. Furthermore, the flight crew did not effectively discuss potential threats, such as the wet runway condition, and appropriate threat mitigations in an arrival briefing. When the captain changed the autobrake setting to 1, the first officer (FO) accepted this deviation from the established autobrake SOP without further discussion, missing an opportunity to exhibit good crew resource management by discussing potential risks associated with this action. Lastly, a thorough arrival briefing could have identified and reminded the flight crew of a paved blast pad within the normal runway safety area (RSA) at the end of runway 27. This blast pad and RSA infrastructure provided an opportunity to decelerate to a safe taxi speed for full stop on paved and non-paved, obstacle-free surfaces instead of attempting to turn onto taxiway SC at high speed.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Landing gear collapse during taxi (from runway)
  2. Loss of control on ground during taxi (from runway) defining event

The NTSB's findings

  • Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • Personnel issues › Task performance › Planning/preparation › Flight planning/navigation › Flight crew
  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Flight crew

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 20,500 hours in all; 15,192 in this make and model; 152 in the last 90 days; 89 in the last 30 days; 11,635 as pilot in command; 528 on instruments
  • Last flight review: August 6, 2023
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane; rotorcraft: helicopter
  • Flight time: 4,900 hours in all; 1,200 in this make and model; 104 in the last 90 days; 60 in the last 30 days; 2,600 as pilot in command; 2,300 on instruments
  • Last flight review: October 12, 2023
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Seats: 175
  • Landing gear: retractable
  • Engine 1: Cfm Intl LEAP-1B28 SER (turbofan); 2,632 hours total
  • Engine 2: Cfm Intl LEAP-1B28 SER (turbofan); 2,632 hours total
  • Operator: United Airlines INC

The flight

  • Departed from: MEM Memphis TN
  • Flight plan: IFR
  • Runway 09/2, 10,000 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 190° at 5 knots
  • Visibility: 1.5 statute miles
  • Sky: broken clouds at 800 ft
  • Temperature: 73°F (23°C), dew point 72°F (22°C)
  • Altimeter: 29.71 inHg
  • Observation at 7:53 am from KIAH, 1 miles away

Weather report (METAR): KIAH 081353Z 19005KT 1 1/2SM BR BKN008 OVC018 23/22 A2971 RMK AO2 SFC VIS 2 1/2 SLP059 T02280217

Injuries

FatalSeriousMinorNone
Cabi4
Flig2
Passengers160

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number DCA24FA120.