# NTSB investigations: Cessna 172N, OR

NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports.

## Latest cases

- [NTSB WPR20CA071](https://openairdocs.org/ntsb/WPR20CA071.md): Cessna 172 · Sun River, OR · Accident · No injuries · Data collection · Final report · Jan 20, 2020 · N73707 · Substantial damage
  > The 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 WPR12CA345](https://openairdocs.org/ntsb/WPR12CA345.md): Cessna 172N · Ashland, OR · Accident · No injuries · Data collection · Final report · Jul 25, 2012 · N738AJ · Substantial damage
  > The student pilot's improper flare, which resulted in a hard landing.
- [NTSB WPR11CA008](https://openairdocs.org/ntsb/WPR11CA008.md): Cessna 172N · Salem, OR · Accident · No injuries · Data collection · Final report · Oct 2, 2010 · N545DS · Substantial damage
  > The pilot's failure to maintain directional control during the landing roll.
- [NTSB LAX08CA053](https://openairdocs.org/ntsb/LAX08CA053.md): Cessna 172N · Beaver Marsh, OR · Accident · Minor injuries · Data collection · Final report · Jan 25, 2008 · N734KU · Substantial damage
  > The pilot's inadequate in-flight planning/decision to land on a snow covered runway without first determining the depth of the snow.
- [NTSB SEA04LA052](https://openairdocs.org/ntsb/SEA04LA052.md): Cessna 172N · Creswell, OR · Accident · No injuries · Limited investigation · Final report · Mar 21, 2004 · N739HQ · Substantial damage
  > The 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 SEA03LA036](https://openairdocs.org/ntsb/SEA03LA036.md): Cessna 172N · McMinnville, OR · Accident · No injuries · Limited investigation · Final report · Feb 8, 2003 · N734KU · Substantial damage
  > The 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 SEA02FA125](https://openairdocs.org/ntsb/SEA02FA125.md): Cessna 172N · Otis, OR · Accident · 2 fatal · Field investigation · Final report · Jul 6, 2002 · N738QT · Destroyed
  > The 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 SEA00LA155](https://openairdocs.org/ntsb/SEA00LA155.md): Cessna 172N · Gleneden Beach, OR · Accident · Minor injuries · Limited investigation · Final report · Aug 9, 2000 · N737CM · Substantial damage
  > The 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 SEA97LA059](https://openairdocs.org/ntsb/SEA97LA059.md): Cessna 172N · Madras, OR · Accident · Serious injuries · Limited investigation · Final report · Feb 7, 1997 · N5618J · Substantial damage
  > The 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 SEA96LA035](https://openairdocs.org/ntsb/SEA96LA035.md): Cessna 172N · Pacific City, OR · Accident · No injuries · Limited investigation · Final report · Dec 24, 1995 · N738ME · Substantial damage
  > The 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 SEA95FA018](https://openairdocs.org/ntsb/SEA95FA018.md): Cessna 172N · Klamath Falls, OR · Accident · 1 fatal · Field investigation · Final report · Nov 9, 1994 · N584WA · Destroyed
  > The 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 SEA92LA090](https://openairdocs.org/ntsb/SEA92LA090.md): Cessna 172N · Parkdale, OR · Accident · No injuries · Limited investigation · Final report · May 4, 1992 · N5096E · Substantial damage
  > The pilot's failure to use the proper touchdown point for landing. A factor relating to the accident was the soft dirt runway surface.
- [NTSB SEA92LA084](https://openairdocs.org/ntsb/SEA92LA084.md): Cessna 172N · Grants Pass, OR · Accident · Minor injuries · Limited investigation · Final report · Apr 26, 1992 · N9403E · Substantial damage
  > A failure to maintain runway alignment, and a delayed go-around. Factors include a crosswind, gusts, and a fence in the go-around path.
- [NTSB SEA91LA253](https://openairdocs.org/ntsb/SEA91LA253.md): Cessna 172N · Chiloquin, OR · Accident · No injuries · Limited investigation · Final report · Sep 26, 1991 · N9403E · Substantial damage
  > The 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 SEA90LA134](https://openairdocs.org/ntsb/SEA90LA134.md): Cessna 172N · Yamhill, OR · Accident · Minor injuries · Limited investigation · Final report · Jul 13, 1990 · N733GJ · Destroyed
  > The pilot's failure to retract the flaps during go-around.
- [NTSB SEA89LA110](https://openairdocs.org/ntsb/SEA89LA110.md): Cessna 172 · Chemult, OR · Accident · Serious injuries · Limited investigation · Final report · Jun 12, 1989 · N1365E · Destroyed
  > Improper 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 SEA89LA022](https://openairdocs.org/ntsb/SEA89LA022.md): Cessna 172 · Oregon City, OR · Accident · No injuries · Limited investigation · Final report · Nov 19, 1988 · N6408G · Substantial damage
  > The 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 SEA88LA157](https://openairdocs.org/ntsb/SEA88LA157.md): Cessna 172N · Tyge Valley, OR · Accident · No injuries · Limited investigation · Final report · Aug 20, 1988 · N737RB · Substantial damage
  > The 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 SEA87LA085](https://openairdocs.org/ntsb/SEA87LA085.md): Cessna 172N · Ritter Butte, OR · Accident · Minor injuries · Limited investigation · Final report · Apr 25, 1987 · N1935F · Destroyed
  > During 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 SEA87LA002](https://openairdocs.org/ntsb/SEA87LA002.md): Cessna 172N · Roseburg, OR · Accident · Serious injuries · Limited investigation · Final report · Oct 4, 1986 · N734EP · Destroyed
  > The 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 SEA87LA008](https://openairdocs.org/ntsb/SEA87LA008.md): Cessna 172N · Madras, OR · Accident · No injuries · Limited investigation · Final report · Oct 2, 1986 · N4693J · Substantial damage
  > On 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 SEA86LA236](https://openairdocs.org/ntsb/SEA86LA236.md): Cessna 172N · Lord Flat, OR · Accident · No injuries · Limited investigation · Final report · Aug 29, 1986 · N737NT · Substantial damage
  > The 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 SEA85FA233](https://openairdocs.org/ntsb/SEA85FA233.md): Cessna 172N · Remote, OR · Accident · 2 fatal · Field investigation · Final report · May 23, 1985 · N4871G · Destroyed
  > During 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 SEA84FYK01](https://openairdocs.org/ntsb/SEA84FYK01.md): Cessna 172N · Creswell, OR · Accident · Serious injuries · Final report · Aug 11, 1984 · N3278E · Destroyed
  > The 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 SEA84LA169](https://openairdocs.org/ntsb/SEA84LA169.md): Cessna 172NII · Hillsboro, OR · Accident · No injuries · Limited investigation · Final report · Jul 9, 1984 · N5280E · Substantial damage
  > While 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 SEA84LA082](https://openairdocs.org/ntsb/SEA84LA082.md): Cessna 172N · Harrisburg, OR · Accident · No injuries · Limited investigation · Final report · Apr 14, 1984 · N734JW · Substantial damage
  > The 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 SEA84LA057](https://openairdocs.org/ntsb/SEA84LA057.md): Cessna 172N · Roseburg, OR · Accident · No injuries · Limited investigation · Final report · Feb 18, 1984 · N733VX · Substantial damage
  > The 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 SEA82FYM24](https://openairdocs.org/ntsb/SEA82FYM24.md): Cessna 172P · 3nm Se Scappoos, OR · Accident · 2 fatal · Final report · Sep 15, 1982 · N7335F · Destroyed
  > The 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 SEA81DYK09](https://openairdocs.org/ntsb/SEA81DYK09.md): Cessna 172 · Sunriver, OR · Accident · No injuries · Closed · Jul 4, 1981 · N4854G · Substantial damage
- [NTSB SEA80FA046](https://openairdocs.org/ntsb/SEA80FA046.md): Cessna 172N · Pendleton, OR · Accident · 1 fatal · Closed · Sep 7, 1980 · N3444E · Destroyed
- [NTSB SEA80DYM58](https://openairdocs.org/ntsb/SEA80DYM58.md): Cessna 172 · Molalla, OR · Accident · No injuries · Closed · Sep 4, 1980 · N4923D · Substantial damage
- [NTSB SEA80FA020](https://openairdocs.org/ntsb/SEA80FA020.md): Cessna 172N · Dufur, OR · Accident · 3 fatal · Closed · Feb 24, 1980 · N2340E · Destroyed
- [NTSB SEA79DYM42](https://openairdocs.org/ntsb/SEA79DYM42.md): Cessna 172 · Baker, OR · Accident · Minor injuries · Closed · Jun 19, 1979 · N733QW · Substantial damage
- [NTSB SEA79FYK08](https://openairdocs.org/ntsb/SEA79FYK08.md): Cessna 172N · Bend, OR · Accident · No injuries · Closed · Apr 17, 1979 · N1365E · Substantial damage
- [NTSB SEA79FYM25](https://openairdocs.org/ntsb/SEA79FYM25.md): Cessna 172N · Pendleton, OR · Accident · Serious injuries · Closed · Apr 2, 1979 · N737CD · Substantial damage
- [NTSB SEA79DYM20](https://openairdocs.org/ntsb/SEA79DYM20.md): Cessna 172 · Independence, OR · Accident · No injuries · Closed · Mar 13, 1979 · N738AJ · Substantial damage
- [NTSB SEA79FYK03](https://openairdocs.org/ntsb/SEA79FYK03.md): Cessna 210 · Triangle Lake, OR · Accident · Serious injuries · Closed · Nov 13, 1978 · N5733J · Substantial damage
- [NTSB SEA79DYM05](https://openairdocs.org/ntsb/SEA79DYM05.md): Cessna 172 · Portland, OR · Accident · No injuries · Closed · Nov 1, 1978 · N737BZ · Substantial damage
- [NTSB SEA77FYK08](https://openairdocs.org/ntsb/SEA77FYK08.md): Cessna 172 · Crescent Lake, OR · Accident · No injuries · Closed · May 20, 1977 · N733XZ · Substantial damage

## The whole list in SQL

Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS:

```sql
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
```

This list as a web page: https://openairdocs.org/ntsb?model=2072434&state=OR

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
