Airbus A321-271NX accident near San Francisco, California, February 9, 2026
On February 9, 2026 at about 9:51 pm local time, a 2024 Airbus A321-271NX, registered N2188J, was substantially damaged in an accident during landing (flare/touchdown) near San Francisco, California (San Francisco Intl airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 154 people were on board or involved. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 9, 2026 · about 9:51 pm local time
- Place
- San Francisco, California · San Francisco Intl · map
- Type
- Accident
- Injuries
- No one was hurt; 154 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Airbus A321-271NX, built 2024 · all A321-271NXs on the register
- Registration
- N2188J · registry record · serial 11955
- Damage
- Substantial damage
- Flight
- Flight · scheduled airline rules (Part 121)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Tailstrike during landing (flare/touchdown) defining event
The NTSB's findings
- Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Copilot
- Personnel issues › Action/decision › Action › Incorrect action performance › Copilot
- Aircraft › Aircraft structures › Fuselage › Fuselage main structure › Damaged/degraded
Pilot
- Certificate: airline transport pilot, flight instructor, commercial pilot, flight engineer
- Ratings: multi-engine land; instrument: airplane
- Flight time: 10,615 hours in all; 3,290.4 in this make and model
- Last flight review: November 21, 2025
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: no injuries
Co-pilot
- Certificate: airline transport pilot, commercial pilot
- Ratings: multi-engine land; instrument: airplane
- Flight time: 2,146 hours in all; 1,148.3 in this make and model
- Last flight review: November 3, 2025
- Medical certificate: Class 1
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 6,717 hours
- Last inspection: continuous airworthiness programme, February 9, 2026
- Maximum gross weight: 213,848 lb
- Seats: 171
- Landing gear: retractable
- Engine 1: Iae PW1133GA-JM (turbofan); 0 hours total
- Engine 2: Iae PW1133GA-JM (turbofan); 0 hours total
- Operator: Jetblue Airways CORP
The flight
- Departed from: BOS Boston MA at 3:21 pm
- Flight plan: IFR
- Runway 28L, 11,381 ft by 200 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 010° at 7 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 20,000 ft
- Temperature: 61°F (16°C), dew point 46°F (8°C)
- Altimeter: 30.06 inHg
- Observation at 1:56 pm from KSFO
Weather report (METAR): METAR KSFO 092156Z 01007KT 10SM BKN200 16/08 A3006 RMK AO2 SLP178 T01560083
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Cabi | 4 | |||
| Flig | 2 | |||
| Passengers | 148 |
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number DCA26LA115.
