Final NTSB investigations: Boeing 767-322
15 cases on aircraft the registry lists as Boeing 767-322. 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
| 1993 | 1 |
|---|---|
| 1994 | 1 |
| 1997 | 1 |
| 2006 | 1 |
| 2007 | 1 |
| 2010 | 1 |
| 2013 | 1 |
| 2014 | 1 |
| 2016 | 1 |
| 2019 | 1 |
| 2022 | 1 |
| 2023 | 2 |
| 2024 | 2 |
Where
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.\"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 ('1385200'))
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 ('1385200'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun 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 DCA25LA091Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 767-322 · Gulf of America (Gulf of Mexico)An encounter with an area of clear air turbulence during cruise, which resulted in a serious injury to a flight attendant.NTSB DCA25LA023Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 767-322 · Kingston, JamaicaAn inadvertent encounter with convective turbulence while in enroute cruise flight.NTSB DCA23LA409AccidentClass 4 · LimitedFinal reportBoeing 767-322 · Chantilly, VAImproper overhaul of the trunnion cross-pin hole that resulted in the development of stress corrosion cracking and eventual failure of the right forward trunnion.NTSB DCA23LA384Accident · No injuriesClass 3 · LimitedFinal reportBoeing 767-322 · Houston, TXThe first officer’s improper control inputs after the airplane touched down. Contributing to the severity of the damage was the flight crew’s lack of recognition that the speedbrakes were not armed, which led to their delayed deployment.NTSB DCA23LA093Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 767-322 · Newark, NJAn inadvertent encounter with clear air turbulence during descent.NTSB DCA19CA189Accident · Serious injuriesClass 4 · Data collectionFinal reportBoeing 767 · San Juan, PRAn encounter with convective turbulence during cruise flight.NTSB DCA16CA220Accident · Serious injuriesData collectionFinal reportBoeing 767 322 · International Waters, A1an inadvertent encounter with severe convective turbulence.NTSB DCA14CA157Accident · Serious injuriesData collectionFinal reportBoeing 767 322 · Reykjavik, IcelandThe capabilities of the beverage cart were exceeded which resulted in the cart toppling over and fracturing the flight attendant's foot.NTSB DCA14CA014Accident · Serious injuriesData collectionFinal reportBoeing 767 322 · Houston, TXThe airplane's inadvertent encounter with clear air turbulence during cruise flight, which resulted in a serious injury to a flight attendant.NTSB DCA10IA082Incident · Minor injuriesIncident investigationFinal reportBoeing 767-322 · Chicago, ILthe brake fire after landing was caused by hydraulic fluid leaking on to hot brakes.NTSB CHI07LA093Accident · No injuriesLimited investigationFinal reportBoeing 767-300 · Chicago, ILThe contained fan blade tip separation following the ingestion of several birds into the left engine during takeoff and the lack of an adequate response time available to crew to avert the bird strike.NTSB NYC06LA151Accident · No injuriesLimited investigationFinal reportBoeing 767-300 · Dulles, VAThe driver's failure to follow company standard operating procedures. A factor was the driver's diverted attention to an on-time departure.NTSB LAX97LA112Accident · Serious injuriesLimited investigationFinal reportBoeing 767-300 · San Francisco, CAan encounter with unforecasted moderate clear air turbulence, while descending over mountainous terrain.NTSB MIA94IA043Incident · No injuriesIncident investigationFinal reportBoeing 767-322 · Miami, FLEmergency procedure initiated by an unqualified person.NTSB MIA94LA010Accident · Serious injuriesLimited investigationFinal reportBoeing 767-300 · Atlantic Ocean (Atlantic Ocean)Encounter with unforecasted weather (moderate turblence) resulting in injury to three passengers.