Final NTSB investigations: Boeing 767-222
8 cases on aircraft the registry lists as Boeing 767-222. 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
| 1983 | 1 |
|---|---|
| 1992 | 1 |
| 1993 | 1 |
| 1995 | 1 |
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 1 |
Where
Open the mapLatest 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 ('1385122'))
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 ('1385122'))
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 IAD03IA007Incident · No injuriesIncident investigationFinal reportBoeing 767-222 · Boston, MAAn inadvertant collision with birds during the initial climb out.NTSB DCA01MA063Accident · 65 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…NTSB CHI00IA152Incident · No injuriesIncident investigationFinal reportBoeing 767-222 · Lafayette, INThe blocked drain lines in the canted pressure deck and the frozen aileron cable.NTSB NYC00IA036Incident · No injuriesIncident investigationFinal reportBoeing 767-200 · Jamaica, NYTotal failure of the stabilizer control system for undetermined reasons.NTSB CHI95LA188Accident · Serious injuriesLimited investigationFinal reportBoeing 767-222 · Champagne, ILan in-flight encounter with turbulence.NTSB DEN93IA025Incident · No injuriesIncident investigationFinal reportBoeing 767-222 · Denver, COMedical incapacitation of the first officer.NTSB LAX92IA209Incident · Minor injuriesIncident investigationFinal reportBoeing 767-222 · Los Angeles, CAA rupture in the airplane's air condition/heat/pressurization/apu duct, along its welded seam. Contributing to the incident was the manufacturers' failure to issue a service bulletin applicalbe to all APU ducts in the systems.NTSB DEN84IA041Incident · No injuriesIncident investigationFinal reportBoeing 767 · Denver, COOn takeoff roll the no 3 wheel on the right main landing gear fell off the acft. The acft returned and landed without further incident. The wheel bearing was found faileddue to cosmoline contamination.