United Airlines Flight 702
Boeing 767-322 · Accident: hard landing
From Newark Liberty International Airport (EWR) to an unrecorded destination
Event
- NTSB case
- DCA23LA384
- 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
- Visual Meteorological Cond
Boeing 767-322
- Aircraft type
- Boeing 767
- 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
- N641UA
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From Newark Liberty International Airport (EWR), Newark, NJTo not recorded
- Aircraft age
- About 32 years (built 1991)
- 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
- Hard landing
- 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
- Organizational issues › Support/oversight/monitoring
- 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
After a stabilized approach, the main landing gear of United Airlines flight 702 touched down and the nosewheel contacted the runway harder than expected. The airplane then bounced, and the first officer (the pilot flying) reacted by pulling the control yoke aft to keep the nosewheel from impacting the runway a second time. The first officer applied the thrust reversers, the speed brakes deployed, and the nosewheel bounced a second time. Subsequently, the nosewheel impacted the runway a third time and, the airplane began to decelerate normally. The abnormal nosewheel impacts with the runway resulted in substantial damage to the fuselage.
Although the first officer stated he held aft pressure on the control column during the initial touchdown, flight data showed that he also made nosedown column inputs during the landing sequence. These nose-down inputs contributed to the nosewheel abnormally impacting the runway. Normal operation of the speedbrakes includes deployment during initial main gear touchdown, if the speedbrakes are in the armed position and the thrust levers are at idle. The only indication that the speedbrakes are armed is a demarcation line located on the control stand. If they do not automatically deploy during main gear touchdown, the pilot monitoring (in this case, the captain) announces the abnormal operation and slowly raises the speedbrake handle to the up position while the pilot flying slowly lowers the airplane’s nose to the runway. In addition, the speedbrakes will automatically deploy if the airplane is on the ground and either thrust lever is moved to the reverse idle detent. However, the speedbrakes were not armed before landing and after the airplane’s first bounce, data showed the speedbrakes automatically deployed with the first officer’s application of the thrust reversers, as designed. The deployment of the speedbrakes with the thrust reversers was while the nosewheel was still in the air. This likely contributed to the second abnormal runway contact of the nosewheel and the subsequent damage to the airplane. It is also likely that neither flight crewmember noticed that the speedbrakes were not armed before landing. Crew Performance De-rotation is the lowering of the aircraft’s nose gear to the runway following touchdown on the main gear during landing. The first officer’s nose-down column inputs were contrary to United Airlines’ procedures and training. The first officer’s training records showed inconsistencies in airplane handling as recent as a few months before the accident. He received an unsatisfactory performance rating and, upon re-evaluation, a satisfactory rating with a condition to recheck after 90 days (instead of 9 months). This was due to, among other things, marginal performance with landings. According to the check airman who completed the first officer’s second evaluation, the purpose of the recheck was to ensure, due to the first officer’s previous “struggles,” that his “proficiency is up to standards”. The first officer had accumulated about 129 flight hours in the accident airplane make and model. Due to the satisfactory performance rating on the first officers second evaluation, the investigation was unable to determine if the first officers training inconsistencies contributed to the accident.
Probable cause
The first officer’s improper control inputs after the airplane touched down. Contributing to the severity of the damage was the flight crew’s lack of recognition that the speedbrakes were not armed, which led to their delayed deployment.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA23LA384
- Event ID
- 20230731192744
- Case number
- DCA23LA384
- 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: 00da93d4a38db37eb0d9b57c7c8199c2b9a3c6c019c68d73de9a985c77e847fd; retrieved 2026-09-16T17:55:47.770Z.