United Airlines Flight 345
Boeing 757 222 · Accident: tailstrike during landing
From George Bush Intercontinental Airport (IAH) to San Diego International Airport (SAN)
Event
- NTSB case
- DCA14LA137
- 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
- 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
- Airline
- 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 222
- 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
- N553UA
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From George Bush Intercontinental Airport (IAH), Houston, TXTo San Diego International Airport (SAN), San Diego, CA
- Aircraft age
- About 22 years (built 1992)
- 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
- Landing · flare/touchdown
- 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
- Tailstrike
- 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
On July 29, 2014, about 2240 pacific daylight time, United Airlines flight 345, a Boeing 757-222, N553UA, experienced a tailstrike while landing at the San Diego International Airport (SAN), San Diego, California. There were no injuries to the 174 persons onboard. The airplane sustained substantial damage. The flight was operating under 14 Code of Federal Regulations Part 121 as a regularly scheduled passenger flight from George Bush Intercontinental Airport (IAH), Houston, Texas, to SAN.
According to the operator, the first officer (FO) was the pilot flying and the captain was the pilot monitoring. The accident flight was the second flight of the day for both crew members. The climb, cruise, and descent portions of the flight were uneventful. The airplane was configured for a flaps 30 landing with the autopilot off for the visual approach to runway 27. The target airspeed for the landing was 130 knots, 5 knots above VREF.
An airplane performance study was completed based on the FDR data from the flight. The study showed the wind was constant during the final descent to the runway with about a 4-knot headwind component. At about 50 feet radio altitude, the FO began to gradually pull back on the column until the elevators deflected 12 degrees airplane nose up at touchdown. Touchdown occurred with a sink rate near 0, a pitch attitude of about 6 degrees and an airspeed of 120 knots (5 knots below VREF). After touchdown, thrust was commanded to idle and the speedbrakes were deployed. The FO then began to gradually release column backpressure; however, pitch attitude continued to increase towards the gear-struts-compressed tail strike pitch attitude. The airplane's pitch attitude eventually exceeded the gear struts compressed tail strike attitude of 10.5 degrees. The FO commanded reverse thrust as the tail strike occurred and then increased to maximum reverse thrust after derotation had occurred.
Published Flight Operations Technical Bulletins issued by the manufacturer in 1988 and 1990 instructed pilots to immediately lower the nose after touchdown (i.e. apply forward pressure) and warned pilots that bleeding off airspeed below VREF prior to touchdown will increase body attitude and thereby increase the likelihood of a tail strike. In this accident, touchdown occurred about 5 knots below VREF and the nose-up elevator remained for nearly 3.5 seconds, causing the aft fuselage to contact the runway.
Inspection of the airplane revealed substantial abrasion damage to two aft, lower skin panels spanning an area about 4 feet long by 1.5 feet wide. In addition, the forward and aft lower chords on the aft pressure bulkhead (APB) were deformed and the lower APB web was buckled.
Probable cause
the first officer's failure to maintain the correct airspeed and pitch attitude during landing that resulted in a tailstrike.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA14LA137
- Event ID
- 20140806X21104
- Case number
- DCA14LA137
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2014-07-30.
- API snapshot SHA-256: aa05d49bcad6cc510137bcdeda5734f5fc36aa2e9191fdc90b982f83b9310515; retrieved 2026-09-16T01:36:25.269Z.