NTSB investigations: Boeing 737-222
5 cases on aircraft the registry lists as Boeing 737-222, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1984 | 1 |
|---|---|
| 1990 | 2 |
| 1992 | 1 |
| 1996 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1384473')
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\" = 130))
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 ('1384473')
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" = 130))
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 CHI97FA030Accident · Serious injuriesField investigationFinal reportBoeing 737-222 · Grand Rapids, MIa passenger sustained a fractured ankle during an emergency evacuation for undetermined reasons.NTSB FTW92IA184Incident · No injuriesIncident investigationFinal reportBoeing 737-222 · Oklahoma City, OKHydraulic fluid exhaustion due to the chafed 'a' system hydraulic line and the improper installation by unknown maintenance personnel of the 'b' system line.NTSB DEN90IA189Incident · Minor injuriesIncident investigationFinal reportBoeing 737-222 · Denver, COThe failure of the flight crew to follow emergency procedures/directives. Factors were the failure of the aircraft electrical system (relays) and the failure of the company to provide a jetway operator.NTSB ATL90FA146Accident · Minor injuriesField investigationFinal reportBoeing 737-222 · Kinston, NCFailure of the fuel pump control shaft because of improper machining by the repair facility during maintenance modification of the pump and improper procedures during overhaul of the nose landing gear.NTSB SEA84IA168Incident · No injuriesIncident investigationFinal reportBoeing B-737-222 · Portland, ORAfter takeoff, the acft was climbing thru about 4000 ft when the APU fire warning light illuminated. The flt crew discharged the fire extinguishing units & requested an emergency landing. A teardown of the APU revealed evidence that a hard object was injested…