The U.S. aircraft register, updated daily
Accidents · NTSB DCA26LA142 · Final report

Boeing 787 accident near Houston, Texas, February 27, 2026

On February 27, 2026 at about 1:53 pm local time, a 2015 Boeing 787, registered JA873A, was substantially damaged in an accident during landing (flare/touchdown) near Houston, Texas (George Bush Intcntl/Houston airport). It was flown under foreign airline rules (Part 129). No one was hurt; 209 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The captain’s inadvertent activation of the takeoff/go around switch at touchdown that caused an increase in the airplane pitch attitude that was not corrected before the lower fuselage contacted the runway.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 27, 2026 · about 1:53 pm local time
Place
Houston, Texas · George Bush Intcntl/Houston · map
Type
Accident
Injuries
No one was hurt; 209 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Boeing 787 9, built 2015 · all 787s on the register
Registration
JA873A · no longer on the register · serial 34530
Damage
Substantial damage
Flight
Flight · foreign airline rules (Part 129)

The NTSB's narrative final · quoted from the NTSB record

All Nippon Airways (ANA) flight 114 experienced a tailstrike during landing on runway 26L at Houston George Bush Intercontinental Airport (IAH), Houston, Texas. The scheduled international passenger flight was operated under the provisions of Title 14 Code of Federal Regulations Part 129. The airplane sustained substantial damage and there were no injuries to the 12 crewmembers and 197 passengers on board. At the time of the accident, the captain was the pilot flying and the first officer (FO) was the pilot monitoring. According to the flight crew, the visibility at IAH was forecast to be poor due to fog. Based on the conditions at IAH, the flight crew elected to perform a Category III (CAT III) approach and landing using the airplane’s autoland system. The flight crew recalled no issues during the approach. When the airplane touched down, the captain stated he confirmed the engine thrust levers were at full idle. The captain recalled the speedbrakes deployed, and as he moved to raise the thrust reversers, he noted that the nose of the airplane rose unexpectedly. The captain manually pushed the control column forward with enough force to both disconnect the autopilot and lower the nose, but pulled the column back to prevent the nose landing gear from “slamming down.” The FO recalled the touchdown was smooth and recognized the speedbrakes had deployed. The FO was looking at the flight mode annunciator (FMA), located at the top on the primary flight display (PFD), and called out that the system entered takeoff/go around (TOGA) mode. The FO recalled the three fields for the FMA showed the following from left to right: 1) a blank field, 2) TOGA, and 3) TOGA. The captain and FO did not recall the TOGA switch was pressed. The flight crew recalled the pitch attitude rose to about 7.5° on the PFD. The flight crew did not recall any further issues during the remainder of the landing roll. While exiting the runway, the captain recalled seeing a “tailstrike” message on the engine indicating and crew alerting system (EICAS). Postlanding inspection of the airplane confirmed substantial damage to the lower fuselage consistent with its contact with the runway. Additionally, scraping damage was found on the tailstrike sensor and on an antenna on the lower fuselage. There was no reported mechanical malfunction that contributed to the excessive airplane pitch angle after the airplane touched down. The recorded flight data showed that the autopilot pitch mode and autothrottle mode were both in “flare” mode at the time the airplane touched down on the runway. About half a second after touchdown, the flight data showed the TOGA switch was pressed. As a result, the autopilot pitch and autothrottle modes both transitioned to TOGA mode. However, the autothrottle TOGA mode was canceled when the throttles were moved to reverse thrust. The autopilot pitch mode, still in TOGA mode, commanded the elevator and stabilizer to target a go-around pitch attitude, with the pitch attitude increasing from 3.5° to 7.4° over 2 seconds. About 5 seconds after TOGA mode was activated, the control column was pushed forward (airplane nose down) and 2 seconds later showed a peak control column force of 40 pounds, which disconnected the autopilot. At that time, the airplane pitch attitude reached 7.8°, sufficient to result in a tailstrike, with a subsequent peak value of 7.9°. The flight data also showed the tailstrike protection function had activated and was commanding an elevator deflection, after the TOGA switch was pressed, to reduce elevator deflection. However, the tailstrike protection function could not prevent the pitch attitude increase that resulted in the tailstrike due to its limited authority. According to flight crew statements, they did not recall pressing the TOGA switch and did not believe they pressed them. There was no evidence of an autopilot system malfunction, therefore it is likely the captain inadvertently pressed the TOGA switch when he reached for the thrust reversers at touchdown. According to the airplane manufacturer, the conditions that inhibit TOGA activation were not yet satisfied when the TOGA switch was pressed, allowing for both the autopilot pitch mode and autothrottle mode to transition to TOGA. The flight crew was unaware that TOGA mode was activated, and their delayed detection of the increase in pitch attitude prevented timely application of corrective pitch control inputs to avert the 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

  1. Tailstrike during landing (flare/touchdown) defining event

The NTSB's findings

  • Personnel issues › Action/decision › Action › Incorrect action selection › Pilot
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft structures › Fuselage › Fuselage main structure › Damaged/degraded

Pilot

  • Certificate: airline transport pilot, commercial pilot, private
  • Ratings: multi-engine land; instrument: airplane
  • Flight time: 16,413 hours in all; 2,969 in this make and model; 8,142 as pilot in command
  • Medical certificate: Unknown
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot, commercial pilot, private
  • Ratings: multi-engine land; instrument: airplane
  • Flight time: 3,929 hours in all; 2,575 in this make and model; 86 as pilot in command
  • Medical certificate: Unknown
  • Seat: rgt
  • Injury: no injuries

Other crew

  • Certificate: airline transport pilot, commercial pilot, private
  • Medical certificate: Unknown
  • Seat: rear
  • Injury: no injuries

The aircraft

  • Airframe total time: 44,393.8 hours
  • Last inspection: continuous airworthiness programme, February 23, 2026
  • Maximum gross weight: 561,500 lb
  • Seats: 231
  • Landing gear: retractable
  • Engine 1: Rolls-Royce Trent 1000K3 (turbofan); 6,168 hours total
  • Engine 2: Rolls-Royce Trent 1000K2 (turbofan); 28,851 hours total
  • Operator: All Nippon Airlines

The flight

  • Departed from: HND Tokyo OF at 2:10 am
  • Flight plan: IFR
  • Runway 08R/, 9,402 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Temperature: 63°F (17°C), dew point 63°F (17°C)
  • Altimeter: 29.99 inHg
  • Observation at 7:53 am from IAH

Injuries

FatalSeriousMinorNone
Cabi9
Flight crew3
Passengers197

Photographs from the investigation 2 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

4 documents, released by the NTSB on September 8, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.