Skip to content

Final NTSB investigations: Boeing 767-332

18 cases on aircraft the registry lists as Boeing 767-332. 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.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19882026

Where

Latest cases

Query with SQL

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."completionStatus" = 'Completed' AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1385101')) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

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.\"completionStatus\" = 'Completed'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1385101'))
  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.

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."completionStatus" = 'Completed'
  AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1385101'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.

NTSB DCA22LA179Incident · No injuriesClass 4 · LimitedFinal reportBoeing 767-332 · New York, NYThe failure of maintenance personnel to close the drain mast heater circuit breakers which resulted in the formation of ice in the forward drain mast, an improper flow of wastewater into the main landing gear wheel well, and the formation of ice on one or…Jul 7, 2022 · N181DN · No damage NTSB DCA21LA229Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 767-332 · Seattle, WAThe flightcrew’s failure to set the hydraulic panel correctly during the execution of the pushback checklist, and when the hydraulic panel setting was corrected, that resulted in the airplane coming to a sudden stop and a flight attendant receiving a serious…Sep 1, 2021 · N196DN · No damage NTSB DCA19CA034Accident · Serious injuriesClass 4 · Data collectionFinal reportBoeing 767 · SUNNS intersection, Osaka, JapanThe airplane’s encounter with severe turbulence.Dec 4, 2018 · N193DN · No damage NTSB DCA18CA165Accident · No injuriesData collectionFinal reportBombardier CL600 2D24 · Queens, NYthe failure of the captain of Delta 212 to ensure adequate clearance while taxiing behind Endeavor 3413.May 1, 2018 · N606LR · 2 aircraft · Substantial damage NTSB ENG14IA019Incident · No injuriesIncident investigationFinal reportBoeing 767 332 · Los Angeles, CAThe combination of fuel leaking from the integrated drive generator (IDG) fuel/oil heat exchanger and the coincident arcing of the IDG power feeder cables that ignited the leaking fuel. Contributing to the ignition of the fuel was the misrouting of the IDG…Jul 11, 2014 · N139DL · Minor damage NTSB DCA11CA084Accident · No injuriesData collectionFinal reportBombardier CL600 2D24 · Boston, MAthe B767 Captain's failure to maintain a safe clearance between his wing and the tail of the CRJ900 that was stopped on a taxiway.Jul 14, 2011 · N132EV · 2 aircraft · Substantial damage NTSB DCA10FA076Accident · Serious injuriesField investigationFinal reportBoeing 767 · Pacific Ocean (Pacific Ocean)an inadvertent encounter with clear air turbulence.Jul 15, 2010 · N184DN · No damage NTSB ENG10IA038Incident · No injuriesIncident investigationFinal reportBoeing 767 · Athens, GreeceA short circuit involving the light in position L3 on the squib test panel. The specific cause of the short circuit could not be determined.Jun 16, 2010 · N196DN · Minor damage NTSB OPS10IA001Incident · No injuriesIncident investigationFinal reportBoeing 767 · Atlanta Hartsfield Intl. Apt. (KATL), GAThe flight crew’s failure to identify the correct landing surface due to fatigue. Contributing to the cause of the incident were (1) the flight crew’s decision to accept a late runway change, (2) the unavailability of the approach light system and the…Oct 19, 2009 · N185DN · No damage NTSB DCA09CA051Accident · Serious injuriesData collectionFinal reportBoeing 767 332 · San Juan, PRInadvertent encounter with convective turbulence while in cruise.May 20, 2009 · N129DL · No damage NTSB SEA01LA014Accident · Serious injuriesLimited investigationFinal reportBoeing 767-332ER · Portland, ORAn inflight encounter with turbulence that occurred before flight attendants could finish stowing a beverage cart and return to their seats.Nov 4, 2000 · N173DZ · No damage NTSB MIA00LA267Accident · Serious injuriesLimited investigationFinal reportBoeing 767-332ER · Atlanta, GAan in-flight encounter with turbulence in clouds during a normal descent, resulting in serious injuries.Sep 20, 2000 · N172DZ · No damage NTSB IAD00IA032Incident · No injuriesIncident investigationFinal reportBoeing 767-332 · New York City, NYThe first officer's failure to maintain control of the airplane during climb out over water at night, which was a result of spatial disorientation. Factors in the incident were the cloud layer and dark night.Mar 31, 2000 · N182DN · No damage NTSB MIA99LA272Accident · Serious injuriesLimited investigationFinal reportBoeing 767-332 · Atlanta, GAFAA approach/departure controller's improper service and failure to coordinate and resolve a conflict between aircraft prior to effecting a frequency change, and the improper application of visual separation rules to a flight in the clouds, resulting the crew…Sep 27, 1999 · N196DN · No damage NTSB NYC96IA131Incident · No injuriesIncident investigationFinal reportBoeing 767-332ER · Jamaica, NYthe improper installation of the generator feed cable by the manufacturer, which resulted in a severed aileron cable due to arcing between the generator feed cable and aileron cable.Jun 25, 1996 · N185DN · Minor damage NTSB SEA96IA131Incident · No injuriesIncident investigationFinal reportBoeing 767-332 · Salt Lake City, UTfailure of maintenance personnel to properly disconnect (disengage) the right integrated drive generator (IDG) in compliance with the MEL dispatch procedure, which allowed the right IDG to overheat. Factors relating to the incident were: low oil pressure in…Jun 20, 1996 · N136DL · Minor damage NTSB SEA96LA062Accident · Serious injuriesLimited investigationFinal reportBoeing 767-332 · Portland, ORthe passenger's unsuccessful (improper) evacuation of the aircraft. The malfunctioning APU was a related factor in that it torched and produced smoke, due to a faulty fuel control unit and/or gearbox shutoff valve, thereby prompting an emergency evacuation of…Feb 20, 1996 · N125DL · No damage NTSB ATL88FA239Accident · Serious injuriesField investigationFinal reportBoeing 767 · Charleston, SCAug 27, 1988 · N120DL · No damage