Final NTSB investigations: Boeing 737-9
6 cases on aircraft the registry lists as Boeing 737-9. 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
| 2022 | 1 |
|---|---|
| 2023 | 3 |
| 2024 | 2 |
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 ('138470A', '138469A'))
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 ('138470A', '138469A'))
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 DCA25LA025Accident · No injuriesClass 4 · LimitedFinal reportBoeing 737-9 · Houston, TXBrake application before all three landing gears were on the ground, which caused the failure of the right main landing gear tires and resulted in tire fragments impacting the fuselage.NTSB DCA24MA063Accident · Minor injuriesClass 1 · MajorFinal reportBoeing 737-9 · Portland, ORthe in-flight separation of the left mid exit door (MED) plug due to Boeing Commercial Airplanes’ failure to provide adequate training, guidance, and oversight necessary to ensure that manufacturing personnel could consistently and correctly comply with its…NTSB DCA23LA468Accident · No injuriesClass 4 · LimitedFinal reportBoeing 737-9 · Denver, COOverheated brakes due to the extended taxi at a higher power setting in an attempt to burn off fuel to achieve the proper takeoff weight that resulted in a wheel fire during takeoff.NTSB DCA23LA445Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 737-9 · Hebron, KYAn inadvertent encounter with convectively induced turbulence (CIT) during descent.NTSB ENG23LA031Incident · No injuriesClass 3 · LimitedFinal reportBoeing 737-9 · Newark, NJA No. 1 (left) engine fire due a fuel leak that originated from the fuel nozzle 17 b-nut connection that was not properly torqued in accordance with the aircraft maintenance manual procedure.NTSB DCA22LA133Incident · No injuriesClass 3 · LimitedFinal reportBoeing 737-9 · Pittsburgh, PAThe flightcrew’s misidentification of the intended landing runway, which resulted in approach to and landing on the wrong runway. Contributing to the incident was the distraction caused by the dual reset of the flight management computer displays.