NTSB investigations: Boeing 737-2H4, TX
6 cases on aircraft the registry lists as Boeing 737-2H4. 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
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1986 | 1 |
| 1991 | 1 |
| 1992 | 1 |
| 1995 | 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.\"eventStateOrRegion\" = 'TX' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('138448C'))
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."eventStateOrRegion" = 'TX' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('138448C'))
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 FTW95LA103Accident · Serious injuriesLimited investigationFinal reportBoeing 737-2H4 · Dallas, TXThe flight attendants' lack of supervision of deplaning passengers. A factor was lack of supervision by accident victims mother.NTSB FTW92LA142Accident · Serious injuriesLimited investigationFinal reportBoeing 737-200 · Palacios, TXThe flight's unexpected encounter with moderate turbulence.NTSB FTW92LA033Accident · No injuriesLimited investigationFinal reportBoeing 737-200 · Lubbock, TXThe in flight collision with geese. A factor was the dark night.NTSB FTW86MA030Incident · No injuriesMajor investigationFinal reportBoeing 737-2H4 · Dallas, TXThis incident occurred when the no. 2 engine experienced an aft engine mount cone bolt failure and the subsequent failure of the secondary support link (stainless steel cable). The failure of both aft engine support assemblies during the takeoff roll allowed…NTSB FTW83IA094Incident · No injuriesIncident investigationFinal reportBoeing B-737-200 · Lubbock, TXDuring taxi to takeoff the acft slid off the taxiway into the snow and became stuck. The taxiway was covered with snow &ice.NTSB FTW83LA033Accident · Serious injuriesLimited investigationFinal reportBoeing 737-200 · Austin, TXThe pilot penetrated the top of a cumulus cloud while climbing from 18000 to 20000 feet. A sharp jolt was felt and turbulence continued for 3-4 seconds. A stewardess fell and broke her ankle.