Final NTSB investigations: Boeing 737-201
7 cases on aircraft the registry lists as Boeing 737-201. 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
| 1989 | 2 |
|---|---|
| 1990 | 1 |
| 1992 | 1 |
| 1996 | 1 |
| 1997 | 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 ('1384454'))
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 ('1384454'))
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 FTW97IA363Incident · Minor injuriesIncident investigationFinal reportBoeing 737-200RS · Salt Lake City, UTThe captain's failure to maintain directional control during landing roll. Factors were the loss of hydraulic pressure in the 'A' hydraulic system, the thrust reverser failure on the number one engine, and flight crew coordination not being maintained.NTSB FTW97LA177Accident · Serious injuriesLimited investigationFinal reportBoeing 737-201 · Denver, COThe flight attendant's failure to assure that the jetway was placed in the proper position prior to opening the forward cabin entry door.NTSB FTW96LA271Accident · Serious injuriesLimited investigationFinal reportBoeing 737-201 · Granite, COAn encounter with clear air turbulence.NTSB MIA92LA167Accident · Serious injuriesLimited investigationFinal reportBoeing 737-200 · Miami, FLFailure (short) of a diode located inside a transformer which is located in the no. 1 generator control unit.NTSB CHI90IA090Incident · No injuriesIncident investigationFinal reportBoeing 737-200 · Cleveland, OHThe improper taxi speed to be able to negotiate a safe turn off the snow covered runway.NTSB ATL89IA099Incident · No injuriesIncident investigationFinal reportBoeing 737-201 · Dayton, OHAn excessively worn outflow valve in the cabin evironmental/pressurization system that resulted in a rapid cabin depressurization.NTSB CHI89MA046Accident · No injuriesMajor investigationFinal reportBoeing 737-201 · Chicago, ILPrevious damage to the aft cone (engine mounting) bolt, which resulted in mismatched surfaces between the bolt and isolation mount, loss of torque during cyclic loading of the mounting bolt, and subsequent fatigue failure of the bolt.