DCA24LA043 · Boeing 787 8
United Airlines Boeing 787 8 · Incident: ground collision while taxiing
From Newark, NJ to an unrecorded destination
Event
- NTSB case
- DCA24LA043
- 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
- Incident
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- 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
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Boeing 787 8
- Aircraft type
- Boeing 787
- 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
- N30913
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From Newark, NJTo not recorded
- Aircraft age
- About 9 years (built 2014)
- 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 91: General Aviation
- 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
- Ground collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Personnel issues › Psychological
- Personnel issues › Task performance
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 (UAL) flight 3885, a Boeing 787, impacted a hangar with its right-wing tip while taxiing to parking at Chicago O’Hare International Airport (KORD), Chicago, Illinois. The flight was a maintenance ferry flight conducted under Title 14 Code of Federal Regulations Part 91 from Newark Liberty International Airport (KEWR), Newark, New Jersey. According to the flight crew, after landing on runway 10C at ORD they were cleared to taxi to a UAL maintenance facility via taxiways P to Z. After receiving an air traffic control (ATC) clearance, they crossed runway 10L, continued via taxiway Z crossing both runways 9R and 9C before making a right turn onto taxiway D. Ground control cleared them to enter the ramp at taxiway YY1 and to contact UAL’s Maintenance Ramp frequency. UAL maintenance subsequently instructed them to make a left on YY, which was incorrect, and proceed to the north side of the ramp, where a truck with marshallers would be waiting to guide them to parking. After completing the left turn on YY, the flight crew realized they were about to enter an American Eagle ramp area instead of their intended destination of the UAL ramp area. Unfamiliar with the area they stopped the airplane and queried UAL maintenance as to where they should park. UAL maintenance asked the flight crew to proceed onto the American Eagle ramp and make a 180° turn. The captain noted no wingspan restrictions on the airport charts and no obstacles other than hangars in the area. He stated that there were no taxiway lights; however, there was adequate overhead lighting on the ramp. The captain then asked the first officer (FO) if they were clear to the right, to which the FO responded “yes”. Shortly thereafter, while proceeding onto the ramp and on the associated taxiway line they heard a loud bang and the airplane veered to the right. The FO looked out his window and stated, “we hit the hangar”.
UAL Maintenance Ramp Area
Figure 1 - Google Earth image with taxi route in red. The inset photo of accident site was provided by United Airlines. Green arrow indicates the location of United Airlines maintenance ramp area. The right-wing tip of the airplane struck a hanger resulting in minor damage to the wing. The damage to the hanger was estimated at about $236,000. A B787 has a wingspan of 197 feet 3 inches. The distance from the taxiway centerline to the hangar was about 98 ft accommodating a wingspan of about 196 ft. Had the marshallers met the airplane at American Eagle ramp and provided obstruction clearance guidance and/or the flight crew requested additional ground handling support before attempting to turn around in an unfamiliar area it is likely that the collision would not have occurred.
Probable cause
The flight crew’s misperception of the distance required to safely pass the hangar and failure to request additional ground handling support while taxiing, which resulted in a collision with a hangar. Contributing to the accident was United Airlines Maintenance Ramp personnel’s ambiguous taxi instructions and lack of obstruction clearance guidance.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA24LA043
- Event ID
- 20231219193541
- Case number
- DCA24LA043
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2023-10-19.
- API snapshot SHA-256: fd7f4c1617d47b8cb93c0be54cf6438a44adfc21c108befd15c4c5122f496de9; retrieved 2026-09-16T18:22:48.318Z.