Aviation Crash Map

Boeing 767-322 N641UA

29 July 2023 · Houston, Texas, United States · No injuries

Summary

On 29 July 2023 at about 15:34 local time, a Boeing 767-322 registered N641UA, operated by United Airlines Inc, was involved in an accident near Houston, Texas, United States. 202 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 15:34
Classification
Accident
Location
Houston, Texas, United States
Nearest airport
George Bush Intcntl/Houston (IAH)
Coordinates
29.9838, -95.3382
Aircraft
Boeing 767-322
Registration
N641UA
Category
Airplane
Year built
1991
Engines
2
Operating rule
Part 121: Air Carrier
Phase of flight
Not recorded
Route
Newark → Unknown
Aircraft damage
Substantial
Weather
VMC
Light
Day
NTSB number
DCA23LA384

People

Nobody was injured.

On board Died Serious Minor Uninjured
202 0 0 0 202

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full 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.

Quoted verbatim from the NTSB record.

Other Boeing 767 accidents

Date Aircraft Location Operator Outcome Died
3 Jan 2023 Boeing 767
N496MM
Incheon, Republic Of Korea
no coordinates
- Unknown -
5 Jan 2023 Boeing 767-31B
N664GT
Hahn, Germany
no coordinates
Atlas Air Unknown -
20 Jun 2023 Boeing 767
CC-CXK
Frankfurt, Germany
no coordinates
LATAM Airlines Unknown -
3 Aug 2023 Boeing 767-322
N676UA
Chantilly, Virginia, United States United Airlines Inc Unknown -
25 Jan 2023 Boeing 767
JA603A
Narita, Japan All Nippon Airways Co., Ltd. No injuries -
12 Jul 2023 Boeing 767-300
JA614J
Chitose, Japan Japan Airlines Co., Ltd No injuries -

All 237 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
24 Sep 2023 Beechcraft C23
N18994
Gonzales, Texas, United States - Minor injuries -
14 Mar 2023 Bell APT70
N314AL
Mineral Wells, Texas, United States Bell Textron Inc No injuries -
1 Mar 2023 Cessna 150F
N3090X
Hillsboro, Texas, United States - Unknown -
14 May 2023 Robinson R22 BETA
N40506
Brady, Texas, United States - Fatal 1
7 Aug 2023 Taylorcraft F21
N2005J
Holliday, Texas, United States - No injuries -
9 May 2023 Cirrus SR22
N433CF
Midland, Texas, United States - No injuries -

All 170,864 records in United States