Plane Crash List

Airbus A321-271NX N2188J

9 February 2026 · San Francisco, California, United States · No injuries

Summary

On 9 February 2026 at about 21:51 local time, a Airbus A321-271NX registered N2188J, operated by Jetblue Airways Corp, was involved in an accident near San Francisco, California, United States. 154 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 21:51
Classification
Accident
Location
San Francisco, California, United States
Nearest airport
San Francisco Intl (SFO)
Coordinates
37.6189, -122.3750
Aircraft
Airbus A321-271NX
Registration
N2188J
Category
Airplane
Year built
2024
Engines
2
Operating rule
Part 121: Air Carrier
Phase of flight
Not recorded
Route
Boston → Unknown
Aircraft damage
Substantial
Weather
VMC
Light
Day
NTSB number
DCA26LA115

People

Nobody was injured.

On board Died Serious Minor Uninjured
154 0 0 0 154

Probable cause

The first officer’s excessive aft sidestick input combined with decaying airspeed during initiation of a go-around, resulting in an increase in the airplane pitch attitude and subsequent lower fuselage contacting the runway.

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

Read the full NTSB narrative

JetBlue Airways flight 2233 experienced a tailstrike while attempting to land on runway 28L at San Francisco International Airport (SFO), San Francisco, California. The scheduled domestic passenger flight was operated under the provisions of Title 14 Code of Federal Regulations Part 121. The airplane sustained substantial damage and there were no injuries to the 6 crew and 148 passengers onboard. According to the flight crew, the final approach and landing were uneventful, and the winds were described as “light”. The first officer (FO), who was the pilot flying, recalled the left main landing gear touched down before the right main landing gear and believed they encountered minor wake turbulence from the departing aircraft. The captain, who was the pilot monitoring, recalled the main landing gear touching down normally. The FO stated the airplane did not settle toward the runway as expected, at which point the FO decided to initiate a go-around because he was unsure if they would complete the transition to landing within the first 3,000 ft of runway. The captain shifted his attention during touchdown from the outside to the lower navigation display, then back to outside when the FO called out the go-around. The FO recalled feeling a “thud” during initiation of the go-around. The second approach and landing onto runway 28L at SFO was accomplished without incident. Postlanding inspection of the airplane by the captain revealed substantial damage to the lower fuselage consistent with its contact with the runway. There was no reported mechanical malfunction that contributed to excessive airplane pitch angle when the airplane touched down on the runway. The recorded flight data showed the airplane bounced after initial touchdown. About 3 seconds later, the FO sidestick parameter showed a full aft input, for a duration of 2 seconds, while the engine throttles advanced to takeoff/go-around (TOGA) power and the main landing gear was still contacting the ground. The airplane’s pitch angle increased from 5.4° to 11° during the 2-second full aft sidestick input, and the airplane’s pitch angle further increased and peaked at 15.4° two seconds later while the airplane was still in close proximity to the ground. During this timeframe, airspeed decayed to about 12 knots below the target approach speed during the full aft sidestick input before airspeed began to increase. The operator’s flight crew procedures for a bounce at touchdown include the instructions “do not allow the pitch attitude to increase…” and for a low bounce, the pilot should maintain pitch attitude and complete the landing while keeping the thrust at idle. Furthermore, for a high bounce, if the safe outcome of a bounce is in question, to maintain the pitch attitude and apply TOGA thrust. The anti-tailstrike protection feature of the airplane flight control system, which limits commanded pitch rate after touchdown, deactivated as designed when TOGA power was selected. The FO likely did not detect the bounce at touchdown based on their full aft sidestick input during initiation of the go-around, leading to a large increase in airplane pitch angle before the airplane climbed, resulting in a tailstrike.

Quoted verbatim from the NTSB record.

Other Airbus A321 accidents

Date Aircraft Location Operator Outcome Died
3 Jun 2026 Airbus A321
C-GOIO
Horley, United Kingdom
no coordinates
- Unknown -
8 Mar 2026 Airbus A321
OE-ISB
Málaga, Spain EasyJet Europe No injuries -
6 Jul 2026 Airbus A321-231
N943JT
Somerset, Colorado, United States Jetblue Airways Corp Serious injuries -
14 Jul 2026 Airbus A321-211
N382DN
New York, New York, United States Delta Air Lines Inc No injuries -
10 Jul 2026 Airbus A321
EC-OLE
San Andrés, Spain
no coordinates
- Unknown -
4 May 2026 Airbus A321
XA-VXK
Ciudad de México, Mexico
no coordinates
Viva Aerobus Unknown -

All 69 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
27 May 2026 Moose SR 2500
N135DS
Big Bend, California, United States JM Environmental INC Serious injuries -
13 Apr 2026 Alexander Schleicher Gmbh & ASH 31 MI
N77UK
Williams, California, United States - Minor injuries -
16 Feb 2026 Cessna 210B
N9735X
Camarillo, California, United States Rudolph Oelofse Fatal 1
11 Jun 2026 Cessna 172S
N55231
Morgan Hill, California, United States Golf November Aero LLC No injuries -
13 Apr 2026 Cirrus SR22T
N285AH
Fullerton, California, United States - Minor injuries -
17 Jun 2026 Cessna 172S
N96FA
Death Valley, California, United States - No injuries -

All 170,864 records in United States