NTSB investigations: Cessna 172RG, VA
5 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
| 1984 | 1 |
|---|---|
| 1988 | 1 |
| 1990 | 1 |
| 1994 | 1 |
| 1997 | 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\" = 'VA' 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" = 'VA' 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 NYC97LA158Accident · No injuriesLimited investigationFinal reportCessna 172 RG · Quinton, VAThe pilot's failure to identify an unsafe landing gear condition. A factor in the accident was the loss of electrical power.NTSB NYC94FA119Accident · 1 fatalField investigationFinal reportCessna 172RG · Kiptopeka, VAInadequate visual lookout by the flightcrew of the helicopter. A factor related to the accident was: failure of the departure controller to issue a traffic advisory.NTSB BFO90DID01Accident · 2 fatalFinal reportCessna 172RG · Onancock, VAThe inflight loss of control because the pilot experienced spatial disorientation. Other factors related to the accident are VFR flight into IMC, night conditions.NTSB BFO88LA048Accident · No injuriesLimited investigationFinal reportCessna 172RG · Mathew, VAThe plt stated he did a soft field takeoff using 10 degs of flaps. The acft lifted off at about 55 to 60 KTS but according to the plt, was unable to climb out of groundeffect. Since he was too FAR down the rwy to abort the takeoff the plt increased pitch to…NTSB ATL84FA095Accident · 1 fatalField investigationFinal reportCessna 172RG · Chesapeake, VAPrior to departure, the plt was twice advised that the destination wx was below most users minimums. The non-instrument rated plt then departed dulles arpt on an IFR flt plan in IMC. After departure, he did not follow assigned headings, & for a period of…