NTSB investigations: Cessna 172N, AR
16 cases on aircraft the registry lists as Cessna 172N. 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
| 1979 | 2 |
|---|---|
| 1982 | 1 |
| 1986 | 2 |
| 1988 | 2 |
| 1990 | 1 |
| 1994 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 1999 | 2 |
| 2009 | 2 |
| 2023 | 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\" = 'AR' 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 ('2072434'))
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" = 'AR' 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 ('2072434'))
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 CEN23LA271Accident · No injuriesClass 4 · LimitedFinal reportCessna 172N · Siloam Springs, ARThe pilot’s failure to maintain clearance from power lines while on final approach to land.NTSB CEN09CA292Accident · No injuriesData collectionFinal reportCessna 172N · Springdale, ARThe student pilot's failure to maintain control of the airplane during the landing roll and subsequent go-around.NTSB CEN09CA187Accident · No injuriesData collectionFinal reportCessna 172N · Carlisle, ARThe student pilot's improper recovery from a bounced landing.NTSB FTW99LA213Accident · No injuriesLimited investigationFinal reportCessna 172N · Hot Springs, ARthe pilot's failure to refuel the airplane which resulted in fuel exhaustion and a total loss of engine power. A factor was the lack of suitable terrain for a forced landing.NTSB FTW99LA110Accident · No injuriesLimited investigationFinal reportCessna 172N · Turrell, ARThe total loss of engine power as the result of improper maintenance which led to the number one cylinder intake valve rocker assembly stud bolt backing out rendering the valve inoperative. A factor was the lack of suitable terrain for the forced landing.NTSB FTW98FA358Accident · 1 fatalField investigationFinal reportCessna 172N · Cord, ARThe pilot's performance of low altitude flight and his failure to maintain obstacle clearance.NTSB FTW97FA221Accident · 2 fatalField investigationFinal reportCessna 172N · Greenbrier, ARThe pilot's failure to maintain aircraft control during a low altitude maneuver. Factors were the pilot's lack of total experience in the type of operation and inadequate training by the company management.NTSB FTW94LA083Accident · No injuriesLimited investigationFinal reportCessna 172N · Georgetown, ARA carburetor icing induced power loss due to the pilot's improper use of carburetor heat in conditions conducive to carburetor icing. A factor was the lack of suitable terrain onto which a forced landing could be executed.NTSB DEN90LA179Accident · No injuriesLimited investigationFinal reportCessna 172N · Lakeview, ARThe pilot's failure to maintain alignment during landing.NTSB MKC89LA003Accident · No injuriesLimited investigationFinal reportCessna 172 · West Memphis, ARThe pilot said he was unable to activate the runway lights on the designated frequencies during a night personal flight. He attempted to land without the aid of the runway lights, and touched down on the FAR end of the runway subsequently running off the end…NTSB MKC88LA106Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Lakeview, ARWhile attempting to land crosswind on a 'one way' runway, the plt said a gust of wind blew him towards some bordering trees, so he made a decision to 'go around'. The plt said he applied full throttle and raised the flaps from the full flap setting, and…NTSB MKC87LA032Accident · No injuriesLimited investigationFinal reportCessna 172P · Pine Bluff, ARThe pilot stated he had flown over trees from the southeast and descended to 50 ft. upon seeing trees in front of the acft he turned left, away from the trees. The left wing touched the ground followed by the nose gear. The acft then flipped forward to the…NTSB MKC86LA069Accident · No injuriesLimited investigationFinal reportCessna 172N · Warren, ARThe plt reports that a deer ran in front of the acft during the flare for a night landing. The prop hit and killed the deer and the nose gear and bottom of the eng compartment were damaged. After the collision the plt said he smelled fuel fumes and when the…NTSB FTW82DA349Accident · No injuriesFinal reportCessna 172N · Antoine, ARThe pilot stated that during the takeoff run from a private airstrip he allowed the aircraft to veer to the left and struck a drainage ditch.NTSB FTW79DPG78Accident · No injuriesClosedCessna 172N · Crossett, ARNTSB FTW79DPG19Accident · No injuriesClosedCessna 172 · Little Rock, AR