NTSB investigations: Cessna 172G, MS
7 cases on aircraft the registry lists as Cessna 172G. 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
| 1968 | 1 |
|---|---|
| 1969 | 1 |
| 1970 | 1 |
| 1972 | 1 |
| 1984 | 1 |
| 1989 | 1 |
| 1999 | 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\" = 'MS' 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 ('2072420'))
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" = 'MS' 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 ('2072420'))
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 MIA00LA015Accident · No injuriesLimited investigationFinal reportCessna 172G · Itta Bena, MSa loss of engine power for undetermined reasons resulting in a forced landing that was short of the intended touchdown point, and the subsequent impact with the ground.NTSB MIA89LA199Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Forest, MSFailure of the pilot to maintain runway alignment and partial loss of power from water in the fuel. Contributing factors were: uneven runway, pilot's improper recovery from a bounced landing, a gusty crosswind condition, and trees.NTSB ATL84LA212Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Grenada, MSDuring arrival to an uncontrolled arpt, the plt made an apch while following about 1/4 mi behind a UH-1 helicopter. At that time, there was a quartering head wind at about 4 KTS. While on final apch at an alt of about 200 ft AGL, the Cessna 172 encountered…NTSB MKC73AK004Accident · 1 fatalClosedCessna 172 · Tunica, MSNTSB MIA70FKQ05Accident · No injuriesClosedCessna 172G · Purvis, MSNTSB MIA70A0041Accident · 1 fatalClosedCessna 172G · Hazelhurst, MSNTSB MIA68F0548Accident · No injuriesClosedCessna 172G · Bay St.Louis, MS