NTSB investigations: Cessna 172RG, NM
8 cases on aircraft the registry lists as Cessna 172RG. 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
| 1980 | 1 |
|---|---|
| 1981 | 2 |
| 1985 | 1 |
| 1990 | 1 |
| 1994 | 1 |
| 2002 | 1 |
| 2008 | 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\" = 'NM' 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 ('2072438'))
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" = 'NM' 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 ('2072438'))
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 DFW08CA227Accident · No injuriesData collectionFinal reportCessna 172RG · Almogordo, NMThe pilot's failure to extend the airplane's landing gear before landing.NTSB FTW02LA128Accident · No injuriesLimited investigationFinal reportCessna 172RG · Alamogordo, NMthe loss of engine power for an undetermined reason, which resulted in a forced landing after takeoff.NTSB FTW94FA101Accident · 4 fatalField investigationFinal reportCessna 172RG · Dulce, NMFailure by the pilot in command to properly plan the flight and calculate performance data.NTSB DEN90LA116Accident · No injuriesLimited investigationFinal reportCessna 172RG · Albuquerque, NMThe cfi's improper procedures during takeoff. Factors were premature liftoff and inadvertent stall/mush.NTSB DEN86LA055Accident · No injuriesLimited investigationFinal reportCessna 172RG · Las Vegas, NMAccording to the plt, he was attempting to depart from a pvt grass strip, which is located on a plateau at an elev of aprx 6,400 MSL. The grass strip, which is aprx 3,000 ft in length, has an upslope of about 10% for the first half and a downslope at about…NTSB FTW81FQA42Accident · Serious injuriesClosedCessna 172RG · Eagle Nest, NMNTSB FTW81FA091Accident · 3 fatalClosedCessna 172RG · Grants, NMNTSB FTW80FQA32Accident · No injuriesClosedCessna 172RG · Albuquerque, NM