United Airlines Flight 2477
Boeing 737-8 · Accident: loss of control on ground while taxiing
From Frederick W. Smith International Airport (MEM) to an unrecorded destination
Event
- NTSB case
- DCA24FA120
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Boeing 737-8
- Aircraft type
- Boeing 737
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N27290
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From Frederick W. Smith International Airport (MEM), Memphis, TNTo not recorded
- Aircraft age
- About 1 year (built 2023)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Taxi · from runway
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control on ground
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
The captain's decision not to establish and maintain deceleration devices in accordance with company training and standard operating procedures.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA24FA120
- Event ID
- 20240308193898
- Case number
- DCA24FA120
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: a585aad6a5b231ed5c5ccfb2545eb22651346688adccbc31bd678a10dd5bb2ff; retrieved 2026-09-16T18:34:23.742Z.