NTSB investigations: Cessna 172N, OR
39 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
| 1977 | 1 |
|---|---|
| 1978 | 2 |
| 1979 | 4 |
| 1980 | 3 |
| 1981 | 1 |
| 1982 | 1 |
| 1984 | 4 |
| 1985 | 1 |
| 1986 | 3 |
| 1987 | 1 |
| 1988 | 2 |
| 1989 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1992 | 2 |
| 1994 | 1 |
| 1995 | 1 |
| 1997 | 1 |
| 2000 | 1 |
| 2002 | 1 |
| 2003 | 1 |
| 2004 | 1 |
| 2008 | 1 |
| 2010 | 1 |
| 2012 | 1 |
| 2020 | 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\" = 'OR' 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" = 'OR' 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 WPR20CA071Accident · No injuriesData collectionFinal reportCessna 172 · Sun River, ORThe pilot's failure to maintain directional control during the landing roll on a runway with icy patches, which resulted in impact with a snowbank and a subsequent nose-over.NTSB WPR12CA345Accident · No injuriesData collectionFinal reportCessna 172N · Ashland, ORThe student pilot's improper flare, which resulted in a hard landing.NTSB WPR11CA008Accident · No injuriesData collectionFinal reportCessna 172N · Salem, ORThe pilot's failure to maintain directional control during the landing roll.NTSB LAX08CA053Accident · Minor injuriesData collectionFinal reportCessna 172N · Beaver Marsh, ORThe pilot's inadequate in-flight planning/decision to land on a snow covered runway without first determining the depth of the snow.NTSB SEA04LA052Accident · No injuriesLimited investigationFinal reportCessna 172N · Creswell, ORThe pilot's attempting takeoff with the fuel selector in the OFF position resulting in fuel starvation. Contributing factors were the change in habit pattern and expectancy of the fuel selector position as well as the fence and tree.NTSB SEA03LA036Accident · No injuriesLimited investigationFinal reportCessna 172N · McMinnville, ORThe pilot's inadequate compensation for wind conditions and his failure to maintain directional control during the landing roll. Factors include gusty crosswinds and soft terrain in the area where the aircraft departed the side of the runway.NTSB SEA02FA125Accident · 2 fatalField investigationFinal reportCessna 172N · Otis, ORThe pilot's failure to maintain adequate clearance with power lines while conducting low altitude flight resulting in a loss of control and subsequent collision with terrain. Contributing factors were the pilot's low altitude flight and the power lines.NTSB SEA00LA155Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Gleneden Beach, ORThe pilot's failure to remove the control lock during his preflight inspection. Factors contributing to the accident were the pilot's failure to follow the BEFORE TAKEOFF checklist, trees beyond the upwind end of the runway, and the pilot's self-induced…NTSB SEA97LA059Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Madras, ORThe pilot's inadvertent visual flight rules (VFR) flight into instrument meteorological conditions (IMC). Factors include the pilot's improper decision to fly under a low ceiling while in mountainous/hilly terrain, and his encounter with fog and low clouds…NTSB SEA96LA035Accident · No injuriesLimited investigationFinal reportCessna 172N · Pacific City, ORThe pilot's delay in aborting the landing, which resulted in his failure to clear the perimeter fence. Factors relating to the accident were: the tailwind, and the pilot's failure to land at the proper touchdown point.NTSB SEA95FA018Accident · 1 fatalField investigationFinal reportCessna 172N · Klamath Falls, ORThe VFR pilot's attempt to continue the flight into instrument meteorological conditions, and his failure to maintain altitude/clearance with the mountainous terrain below him. Contributing to the accident was a downdraft.NTSB SEA92LA090Accident · No injuriesLimited investigationFinal reportCessna 172N · Parkdale, ORThe pilot's failure to use the proper touchdown point for landing. A factor relating to the accident was the soft dirt runway surface.NTSB SEA92LA084Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Grants Pass, ORA failure to maintain runway alignment, and a delayed go-around. Factors include a crosswind, gusts, and a fence in the go-around path.NTSB SEA91LA253Accident · No injuriesLimited investigationFinal reportCessna 172N · Chiloquin, ORThe loss of engine power in flight due to improper maintenance inspections. A factor relating to the accident was the rough terrain at the accident site.NTSB SEA90LA134Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Yamhill, ORThe pilot's failure to retract the flaps during go-around.NTSB SEA89LA110Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Chemult, ORImproper inflight planning/decision by the pilot, which resulted in a sudden altitude deviation, and his delay in initiating remedial action to maintain clearance from the trees. Contributing factors were the downdrafts, high density altitude, the pilot…NTSB SEA89LA022Accident · No injuriesLimited investigationFinal reportCessna 172 · Oregon City, ORThe pilot was landing his aircraft on a very wet 1,170 foot grass runway. The pilot was not able to stop the aircraft before it collided with a fence at the end of the runway. According to the manufacturers performance figures, under the given temperature and…NTSB SEA88LA157Accident · No injuriesLimited investigationFinal reportCessna 172N · Tyge Valley, ORThe pilot reported that late in the apch, the acft developed a high sink rate. However, he used elevator only to correct the sink rate. The aircraft impacted the runway and bounced. On the third bounce, the nose gear failed and the aircraft nosed over. The…NTSB SEA87LA085Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Ritter Butte, ORDuring a cross country flt the plt noticed that he was gradually losing his communications radio and navigational instruments. Shortly afterwards the plt noticed that the fuel gauges were quickly approaching empty. Since hostile terrain was ahead the plt…NTSB SEA87LA002Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Roseburg, ORThe plt initiated the takeoff from a taxiway with a 100 ft obscured sky and 1/4 visibility in fog. The non-instrument rated plt was unable to maintain the rwy heading during initial climb. The acft drifted to the right of the taxiway and struck trees located…NTSB SEA87LA008Accident · No injuriesLimited investigationFinal reportCessna 172N · Madras, OROn landing touchdown, aircraft nose tire blew out. The student pilot over-corrected with controls and power, causing the aircraft to balloon into the air and touch down a second time in a flat attitude, resulting in a hard landing.NTSB SEA86LA236Accident · No injuriesLimited investigationFinal reportCessna 172N · Lord Flat, ORThe plt elected to go-around at about four feet AGL. Flaps were reduced from 40 degrees of flaps to 20 degrees of flaps and a gentle right turn was made due to rising terrain. The acft then settled onto the ground and crossed two ditches before coming to…NTSB SEA85FA233Accident · 2 fatalField investigationFinal reportCessna 172N · Remote, ORDuring a wx briefing, the non-instrument plt was adzd that VFR flt was not recommended due to low clouds & adverse wx along the route. However, he filed a VFR flt plan & depd arcata, CA at 1240 PDT. At 1339, in the vcnty of wilderville, OR, the plt got a wx…NTSB SEA84FYK01Accident · Serious injuriesFinal reportCessna 172N · Creswell, ORThe acft collided with wires during an attempted go-around. The plt stated that he had made one go-around and on the 2NDLANDING attempt he landed hard in gusty wind & bounced. During the 2nd go-around he collided with wires & crashed.NTSB SEA84LA169Accident · No injuriesLimited investigationFinal reportCessna 172NII · Hillsboro, ORWhile taxing on a ramp area the plts attention was diverted to adjusting the transponder code. The left wing of the acft contacted a moving fuel truck.NTSB SEA84LA082Accident · No injuriesLimited investigationFinal reportCessna 172N · Harrisburg, ORThe plt reported that after the sun had set, a haze formed near the ground. He used visual references to align the acft with the private rwy at dusk. As he approached, he saw what he thought was hedge on the edge of the arpt & then made a soft field landing.…NTSB SEA84LA057Accident · No injuriesLimited investigationFinal reportCessna 172N · Roseburg, ORThe acft drifted left during the student pilots landing and collided with VASI lights. After the collision the acft nosed over. The CFI on the ground said the wind shifted just prior to the last landing.NTSB SEA82FYM24Accident · 2 fatalFinal reportCessna 172P · 3nm Se Scappoos, ORThe acft struck & severed power lines strung between two 90-foot towers located about 1500 feet apart. The power lines were about 50 to 60 feet above the water at the lowest point of the line sag.NTSB SEA81DYK09Accident · No injuriesClosedCessna 172 · Sunriver, ORNTSB SEA80FA046Accident · 1 fatalClosedCessna 172N · Pendleton, ORNTSB SEA80DYM58Accident · No injuriesClosedCessna 172 · Molalla, ORNTSB SEA80FA020Accident · 3 fatalClosedCessna 172N · Dufur, ORNTSB SEA79DYM42Accident · Minor injuriesClosedCessna 172 · Baker, ORNTSB SEA79FYK08Accident · No injuriesClosedCessna 172N · Bend, ORNTSB SEA79FYM25Accident · Serious injuriesClosedCessna 172N · Pendleton, ORNTSB SEA79DYM20Accident · No injuriesClosedCessna 172 · Independence, ORNTSB SEA79FYK03Accident · Serious injuriesClosedCessna 210 · Triangle Lake, ORNTSB SEA79DYM05Accident · No injuriesClosedCessna 172 · Portland, ORNTSB SEA77FYK08Accident · No injuriesClosedCessna 172 · Crescent Lake, OR