FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DCA24LA110 · Boeing 757-224

25 Feb 2024 · San Francisco, CA, United States

United Airlines Boeing 757-224 · Accident: abnormal runway contact during takeoff

Report a problem

Event

NTSB case
DCA24LA110
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
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 757-224

Aircraft type
Boeing 757
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
N13138
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 25 years (built 1999)
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
Takeoff
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
Abnormal runway contact
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

United Airlines (UA) flight 3872 experienced a tailstrike while taking off from San Francisco International Airport (SFO), San Francisco, California. The flight was a local maintenance test flight. The purpose of the test flight was to validate maintenance conducted after a write-up for abnormal flight deck noises that occurred on a previous flight. According to the flight crew, they conducted a flaps 5, reduced power takeoff from runway 28R. The captain recalled the aircraft accelerated faster than normal and had the propensity to lift off prior to the rotation speed of 127 knots. At rotation speed, the captain began a normal aft pull on the control yoke and the pitch attitude increased faster than expected. The captain just called “positive rate” when the crew heard and felt a “boom.” As this flight was a test flight, it was not loaded with passengers and cargo to a takeoff weight typical of flights the pilot flying normally flew. The pilot flying rotated at a rate “normal” to his experience, however because the accident aircraft was loaded lighter than normal, the normal rotation inputs resulted in an over-rotation. The crew assessed the instruments and controllability and decided to continue their climb to flight level (FL) 190 [19,000 feet] where they conducted the tailstrike checklist. They returned to SFO and conducted a flaps 30 landing with no further incident. Prior to leaving the flight deck after the flight, the first officer received the pitch report for takeoff which showed that tail contact occurred about 12.2 degrees during departure and the actual pitch for this departure reached 15.3 degrees. Inspection of the aircraft showed that the tail strike damaged the chord, web, and stiffeners of the auxiliary power unit firewall bulkhead. Because the damage would adversely affect the structural strength of the bulkhead and require major repair or replacement, the damage was considered substantial. The investigation determined that the maintenance conducted prior to this test flight was not related to the accident.

Probable cause

The crew’s over-rotation of the aircraft pitch during takeoff which resulted in a tailstrike.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA24LA110
Event ID
20240226193849
Case number
DCA24LA110
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, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2024-02-26.
  • API snapshot SHA-256: d5d89f189ed53e0dc393d57b3eed5b7e78ed1a0c198619cf68096ffedd3d188d; retrieved 2026-09-16T18:32:43.161Z.