Final NTSB investigations: Cessna 188A
12 cases on aircraft the registry lists as Cessna 188A. 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
| 1967 | 1 |
|---|---|
| 1971 | 1 |
| 1972 | 1 |
| 1973 | 1 |
| 1975 | 1 |
| 1976 | 1 |
| 1980 | 1 |
| 1989 | 2 |
| 1992 | 1 |
| 2000 | 1 |
| 2016 | 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.\"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 ('2073006'))
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 ('2073006'))
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 GAA16CA393Accident · No injuriesData collectionFinal reportCessna 188 · What Cheer, IAThe loss of engine power for undetermined reasons due to the pilot not making the airplane or engine available for examination, which resulted in a forced landing and an impact with terrain.NTSB ATL00LA088Accident · No injuriesLimited investigationFinal reportCessna 188 · Tampa, FLThe failure of the number six-piston connecting rod that resulted in the total loss of engine power.NTSB FTW92DPJ03Accident · 1 fatalFinal reportCessna 188A · Idabel, OKPower loss for undetermined reasons. A factor was lack of unsuitable terrain for the forced landing.NTSB MIA89LA236Accident · Minor injuriesLimited investigationFinal reportCessna 188A · Milton, FLFlight in known adverse weather by the pilot. Turbulence from the nearby thunderstorm was a related factor.NTSB CHI89DEM01Accident · Serious injuriesFinal reportCessna 188A · Belding, MIThe pilot's poor preflight assessment of the runway condition/aircraft performance capabilities, and the aircraft's resultant failure to attain flying speed. Soft terrain is a factor in the accident.NTSB CHI80DER46Accident · No injuriesClosedCessna 188A · Grygla, MNNTSB MIA76FKQ01Accident · Minor injuriesClosedCessna 188A · Carthage, MSNTSB MKC75DCQ48Accident · No injuriesClosedCessna 188 · Selden, KSNTSB MIA74FLA10Accident · Serious injuriesClosedCessna 188 · Chipley, FLNTSB MIA72DKH03Accident · No injuriesClosedCessna 188 · Vienna, GANTSB MIA72FKQ08Accident · Minor injuriesClosedCessna 188A · Hollandale, MSNTSB FTW67F0534Accident · No injuriesClosedCessna 188 · Rosenberg, TX