NTSB investigations: Boeing 767-223

8 cases on aircraft the registry lists as Boeing 767-223. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.

Cases per year

19872026
NTSB investigations: Boeing 767-223 per year, 1987–2026: 8 cases
19871
19881
19961
19981
20012
20061
20101

Latest cases

Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
  FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
  WHERE c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1385123'))
  ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"

Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.

NTSB CEN10LA240Accident · Serious injuriesLimited investigationFinal reportBoeing 767 · Fort Dodge, IAThe flight crew's inadequate separation from convective activity that resulted in serious injury to an unrestrained flight attendant.Apr 30, 2010 · N320AA · No damageNTSB ENG06IA018Incident · No injuriesIncident investigationFinal reportBoeing 767-223(ER) · Los Angeles, CAThe HPT stage 1 disk failed from an intergranular fatigue crack because of GE's inadequate design of the CF6-80 series HPT stage 1 disk. The inadequate design of the disk resulted in a high stress area in the blade slot bottom aft corner that was at or nearly…Jun 2, 2006 · N330AA · Substantial damageNTSB DCA01MA060Accident · 92 fatalMajor investigationFinal reportBoeing 767-200ER · New York City, NYThe Safety Board did not determine the probable cause and does not plan to issue a report or open a public docket. The terrorist attacks of September 11, 2001 are under the jurisdiction of the Federal Bureau of Investigation. The Safety Board provided…Sep 11, 2001 · N334AA · DestroyedNTSB NYC01LA094Accident · No injuriesLimited investigationFinal reportBoeing 767-200ER · Boston, MAThe Boeing 767 captain's misjudgment of the distance between his airplane and the stationary Boeing 737, which resulted in a ground collision. A factor was sunglare.Apr 9, 2001 · N328AA · 2 aircraft · Minor damageNTSB CHI98LA269Accident · Serious injuriesLimited investigationFinal reportBoeing 767-223 · Peotone, ILIn-flight encounter with turbulence.Jul 22, 1998 · N335AA · No damageNTSB LAX96LA222Accident · No injuriesLimited investigationFinal reportBoeing 737-322 · San Francisco, CAinadequate visual lookout by the United Airlines tug driver during the pushback operation. Contributing factors were: the driver's reduced ability to observe the American B-767 due to the nighttime condition, and United Airlines management's failure to ensure…Jun 7, 1996 · N371UA · 2 aircraft · Substantial damageNTSB CHI88FA048Accident · Serious injuriesField investigationFinal reportBoeing 767-200 · Chicago, ILA flight attendant and a passenger received serious and minor injuries respectively during an inflight encounter with severe turbulence during an enroute descent. Greater than moderate turbulence was forecast to be in the area and severe turbulence had been…Jan 20, 1988 · N306AA · No damageNTSB DCA87RA047Incident · No injuriesForeign investigationBoeing B 767 200ER · Frankfurt, GermanyAug 16, 1987 · N332AA