NTSB investigations: Boeing 737-322
4 cases on aircraft the registry lists as Boeing 737-322, where the first occurrence was “Near collision between aircraft”. 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
| 1987 | 1 |
|---|---|
| 1997 | 1 |
| 2006 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('138447Y')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 280))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('138447Y')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 280))
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 OPS06IA008Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Chicago, ILThe failure of the ORD tower south local controller to monitor Atlas Air flight 6972 on arrival to runway 14R and subsequently clearing United Airlines flight 1015 for takeoff on intersecting runway 27L causing a loss of separation between the two aircraft.NTSB OPS06IA007Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · Chicago, ILThe probable cause of this incident was the ORD tower local controller's failure to provide sufficient separation between two aircraft departing intersecting runways. Contributing to the incident was the ORD local monitor's failure to monitor the situating…NTSB CHI97LA162Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Valparaiso, INa delay by the pilot of the other aircraft in turning on his mode C transponder.NTSB CHI88IA015Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Chicago, ILThe south rwys (32L, 9R, & 4R) were being ctld by the south LCL ctlr (slc) & the north rwys (9L & 4L) were ctld by the north LCL ctlr (nlc). At 1543:26, slc told united flt 973 (Boeing 737) to hold on 32L & expect a 3 min delay bfr tkof. Air Wisconsin flt 954…