NTSB investigations: Cessna 172M, AZ
39 cases on aircraft the registry lists as Cessna 172M. 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
| 1974 | 2 |
|---|---|
| 1975 | 3 |
| 1976 | 2 |
| 1977 | 2 |
| 1978 | 2 |
| 1979 | 1 |
| 1980 | 1 |
| 1982 | 2 |
| 1985 | 1 |
| 1986 | 2 |
| 1989 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 1998 | 2 |
| 2000 | 1 |
| 2001 | 2 |
| 2002 | 4 |
| 2003 | 1 |
| 2005 | 1 |
| 2006 | 1 |
| 2009 | 1 |
| 2013 | 1 |
| 2017 | 1 |
| 2018 | 1 |
| 2019 | 1 |
| 2023 | 1 |
Where
Latest 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\" = 'AZ' 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 ('2072418'))
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" = 'AZ' 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 ('2072418'))
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 WPR23LA135Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Skull Valley, AZThe pilot’s failure to maintain directional control of the airplane while landing in a crosswind.NTSB GAA19CA220Accident · No injuriesData collectionFinal reportCessna 172 · Prescott, AZThe student pilot's failure to maintain clearance from a fence post during taxi operations.NTSB GAA18CA141Accident · No injuriesData collectionFinal reportCessna 172 · Show Low, AZThe flight instructor’s failure to maintain directional control during the landing roll in gusting crosswind and tailwind conditions.NTSB GAA17CA318Accident · Minor injuriesData collectionFinal reportCessna 172 · Payson, AZThe pilot’s inadequate preflight planning that did not account for high-density altitude conditions and his subsequent attempted go-around in conditions that prevented the airplane from attaining a positive climb rate and resulted in its subsequent descent…NTSB WPR13LA113Accident · No injuriesLimited investigationFinal reportCessna 172 · Wilcox, AZThe loss of engine power for reasons that could not be determined because postaccident examination did not reveal any abnormalities that would have precluded normal operation.NTSB WPR10CA013Accident · No injuriesData collectionFinal reportCessna 172H · Tucson, AZThe pilot's failure to maintain directional control during the takeoff ground roll.NTSB LAX06CA117Accident · No injuriesData collectionFinal reportCessna 172M · Prescott, AZthe pilot's inadequate compensation for the crosswind conditions and his failure to maintain directional control.NTSB LAX05LA180Accident · No injuriesLimited investigationFinal reportCessna 172M · Tucson, AZThe student pilot's improper flare that induced a porpoise, which resulted in the overload failure of the nose wheel assembly.NTSB LAX03CA288Accident · No injuriesData collectionFinal reportCessna 172M · Tucson, AZthe pilot's improper flare. A contributing factor was the tailwind.NTSB LAX02LA199Accident · No injuriesLimited investigationFinal reportCessna 172M · Saint Johns, AZthe pilot's inadequate compensation for wind conditions resulting in a loss of directional control and collision with terrain. Related factors were the wind gusts, crosswind and soft terrain.NTSB LAX02LA153Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Green Valley, AZThe pilot's failure to identify the wind direction, which led to an attempted downwind landing approach that resulted in a hard landing and severe bounce. Also causal was the pilot's failure to promptly retract the flaps during the rejected landing after…NTSB LAX02LA106Accident · No injuriesLimited investigationFinal reportCessna 172M · Tucson, AZthe pilot's misjudged landing flare and improper bounced landing recovery.NTSB LAX02LA070Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Payson, AZFailure of the pilot to maintain directional control of the airplane. A contributing factor was the premature raising of the flaps.NTSB LAX02LA026Accident · No injuriesLimited investigationFinal reportCessna 172M · Chandler, AZFailure of the student pilot to maintain directional control during landing.NTSB LAX02LA017Accident · No injuriesLimited investigationFinal reportCessna 172M · Prescott, AZThe CFI's improper remedial action and failure to maintain directional control during landing in a strong crosswind condition.NTSB LAX00LA256Accident · No injuriesLimited investigationFinal reportCessna 172 · Chandler, AZfailure of the pilot-in-command to adequately compensate for a crosswind condition and maintain directional control during the landing roll, resulting in the airplane departing the runway and colliding with a sign.NTSB LAX98LA135Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Scottsdale, AZThe pilot's failure to maintain directional control and his inadequate compensation for the wind condition. A contributing factor was the crosswind.NTSB LAX98FA066Accident · 2 fatalField investigationFinal reportCessna 172M · Chandler, AZThe pilot's intentional flying at a low altitude and failure to see and avoid the power lines during dusk conditions.NTSB LAX96LA246Accident · No injuriesLimited investigationFinal reportCessna 172M · Sedona, AZthe pilot's improper recovery from a bounced landing. The variable/gusty/quartering tail wind was a related factor.NTSB LAX96LA073Accident · No injuriesLimited investigationFinal reportCessna 172 · Mohave Valley, AZthe failure of the pilot to assure that clearance was maintained while taxiing in proximity of buildings at an excessive taxi speed.NTSB LAX89LA256Accident · No injuriesLimited investigationFinal reportCessna 172M · Marana, AZInadequate preflight by the student pilot, inadequate supervision by the flight instructor (CFI), and fuel exhaustion due to lack of fuel. Related factors were: inoperative left fuel quantity gage, the cfi's decision to make the flight with a known deficiency…NTSB LAX86LA195Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Kearny, AZThe plt stated that he was on a sightseeing flt and was flying westbound at about 100 ft AGL along the gila river, when the acft struck powerlines. The acft then descended into the river bed. He futher stated that he observed the powerlines at the last minute…NTSB LAX86LA129Accident · No injuriesLimited investigationFinal reportCessna 172M · Springerville, AZA Cessna 172M experienced a loss of power and collided with rough terrain on landing. The pilot indicated he was cruising at 9500 feet MSL (1500 to 2000 feet AGL) with an OAT of 40 degrees fahrenheit. The carb heat handle was in the 'off' position when the…NTSB LAX85FA202Accident · 2 fatalField investigationFinal reportCessna 172M · Camp Verde, AZBoth acft involved in the collision were part of a 4-plane formation flt en route to a group fly-in. N6439R was seen to change positions several times during the flt while the other acft remained stable. Reports from witnesses say that N6439R made 'close…NTSB LAX82DA118Accident · No injuriesFinal reportCessna 172 · Dilkon, AZThe pilot elected to land on a paved road and during the landing roll collided with a road sign.NTSB LAX82DA052Accident · No injuriesFinal reportCessna 172 · Flagstaff, AZThe pilot made a night landing without landing lights. The runway was narrowed by snow banks inside the runway lights. The aircraft skidded on the icy runway and rode up onto the right snowbank, dragging the left wing. When the aircraft yawed to the right the…NTSB LAX80FA115Accident · 2 fatalClosedCessna 172M · Tombstone, AZNTSB LAX80DUJ24Accident · No injuriesClosedCessna 172M · Window Rock, AZNTSB LAX78DUJ69Accident · No injuriesClosedCessna 172M · Grand Canyon, AZNTSB LAX78DUJ44Accident · No injuriesClosedCessna 172 · Kayenta, AZNTSB LAX78FA011Accident · 4 fatalClosedCessna 177B · Tucson, AZNTSB LAX77FA051Accident · 3 fatalClosedCessna 172M · Peoria, AZNTSB LAX76DUK04Accident · No injuriesClosedCessna 150 · Prescott, AZNTSB LAX76DUJ62Accident · No injuriesClosedCessna 172 · Peoria, AZNTSB LAX76DUJ35Accident · No injuriesClosedCessna 172M · Nelson, AZNTSB LAX76DUJ05Accident · Minor injuriesClosedCessna 172 · Chandler, AZNTSB LAX75AL070Accident · 4 fatalClosedCessna 172M · Tsaile, AZNTSB LAX75DUJ44Accident · No injuriesClosedCessna 172 · Window Rock, AZNTSB LAX75AL021Accident · 2 fatalClosedCessna 172M · Fort Apache, AZ