NTSB investigations: Cessna 172, MD
12 cases on aircraft the registry lists as Cessna 172. 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
| 1965 | 2 |
|---|---|
| 1966 | 2 |
| 1967 | 1 |
| 1968 | 2 |
| 1972 | 1 |
| 1976 | 1 |
| 1988 | 2 |
| 1998 | 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\" = 'MD' 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 ('2072402'))
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" = 'MD' 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 ('2072402'))
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 IAD99LA018Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Essex, MDA loss of engine power for undetermined reasons. Factors were the lack of suitable terrain for a forced landing and dark night conditions.NTSB BFO88LA077Accident · No injuriesLimited investigationFinal reportCessna 172 · Oakland, MDAccording to the pilot the landing approach for runway 22 was made over power lines. He stated that during the approach the stall warning horn activated and he increased power to maintain 60 mph with 20 degs of flaps. Once estimating that his intended point…NTSB BFO88LA035Accident · No injuriesLimited investigationFinal reportCessna 172 · Elkton, MDDuring cruise flt at an alt of 1500 ft, the engine suddenly stopped producing power. The acft was landed on railroad tracks in order to avoid trees. The acft nosed over during the landing. Plt stated that the right fuel tank gauge indicated 1/4 tank and the…NTSB IAD76FIG19Accident · Minor injuriesClosedCessna 172 · Laurel, MDNTSB NYC73FIG14Accident · Minor injuriesClosedCessna 172 · Sharpsburg, MDNTSB DIA68D0236Accident · Minor injuriesClosedCessna 172 · Sykesville, MDNTSB DIA68F0206Accident · Minor injuriesClosedCessna 172 · Queenstown, MDNTSB DIA67D0081Accident · No injuriesClosedCessna 172 · Pittsville, MDNTSB NYC66A0714Accident · Serious injuriesClosedCessna 172 · Clinton, MDNTSB NYC66D0605Accident · No injuriesClosedCessna 172 · Taylorsville, MDNTSB NYC66D0342Accident · No injuriesClosedCessna 172 · College Park, MDNTSB NYC66D0140Accident · No injuriesClosedCessna 172 · Princess Anne, MD