NTSB investigations: Cessna 172F
11 cases on aircraft the registry lists as Cessna 172F, where the first occurrence was “In flight collision with object”. 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
| 1983 | 2 |
|---|---|
| 1984 | 1 |
| 1985 | 1 |
| 1986 | 1 |
| 1992 | 1 |
| 1995 | 1 |
| 1998 | 3 |
| 2006 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072414')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072414')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220))
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 DFW06CA164Accident · Serious injuriesData collectionFinal reportCessna 172F · Marietta, OKThe pilot's improper weather evaluation. Contributing factors were the strong tailwind and the high density altitude.NTSB CHI99FA042Accident · 2 fatalField investigationFinal reportCessna 172F · Coleman, WIpilot's failure to maintain clearance from the trees and his intentional flight into IMC conditions. Factors contributing to this accident were the pilot's lack of instrument certification, his becoming lost in the poor weather, his inadequate preparation for…NTSB ATL99LA001Accident · No injuriesLimited investigationFinal reportCessna C-172F · Ball Ground, GAThe pilots failure to maintain directional control of the airplane on take-off, during gusty conditions, resulting in a collision with a tree.NTSB MIA98LA216Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Tuskegee, ALThe pilot's failure to attain adequate airspeed, and his failure to abort the takeoff.NTSB ATL95FA079Accident · 1 fatalField investigationFinal reportCessna 172F · Seneca, SCThe pilot's inadequate visual lookout while maneuvering near utility lines, which resulted in a collision with the wires.NTSB CHI93LA381Accident · No injuriesLimited investigationFinal reportCessna 172 · Union Center, SDImproper planning/decision by the pilot, and his failure to abort the takeoff, while there was sufficient runway remaining. Factors related to the accident were: the soft runway condition & fence at the end of the runway.NTSB MKC86LA097Accident · No injuriesLimited investigationFinal reportCessna 172F · Van Buren, MOThe pilot states that he had been advised of utility lines on both ends of the airstrip, and that several aircraft had previously experienced landing problems there. He further states that as he initiated a go-around he was caught in a downdraft he could not…NTSB ATL85LA255Accident · No injuriesLimited investigationFinal reportCessna 172E · Villa Rica, GAThe plt took off from the stockmar arpt on a local flt. After flying in the local area, he returned at dusk to land, but inadvertently made an approach to another arpt that was located about 1/2 mi from the stockmar arpt. He did not realized that he was…NTSB CHI84LA299Accident · No injuriesLimited investigationFinal reportCessna 172 · Alpena, MIThe plt stated that while flaring for their 5th stop-&-go at night, a deer ran out onto the rwy. The acft collided with the deer & the left main landing gear was sheared off. The acft then veered off the rwy.NTSB NYC83FNC09Accident · Serious injuriesFinal reportCessna 172 · Enosburg Falls, VTThe plt reported that when he was on final to land on a dark night, the acft had electrical failure & he had no lights. He reported that this occurred when he had started his flare & that was all he could remember until after he had regained consciousness…NTSB ATL83FIG03Accident · 1 fatalFinal reportCessna 172F · Hancock, MDThe aircraft collided with the top two wires of a powerline during a low altitude sight-seeing flight along the potomac river. The pilot stated he was maintaining visual contact with the ground should an emergency landing become necessary. He was staying high…