The U.S. aircraft register, updated daily
Accidents · NTSB WPR21LA337 · Final report

Cessna 172E accident near Enterprise, Oregon, September 2, 2021

On September 2, 2021 at about 6:30 pm local time, a 1964 Cessna 172E, registered N3965S, was substantially damaged in an accident during landing (flare/touchdown) near Enterprise, Oregon (Enterprise Municipal Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The fatigue fracture of the nose gear upper torque link, which resulted in the separation of the torque link from the shock strut and a loss of directional control.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 2, 2021 · about 6:30 pm local time
Place
Enterprise, Oregon · Enterprise Municipal Airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172E, built 1964 · all 172Es on the register
Registration
N3965S · registry record · serial 17251165
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

During landing, when the nose gear contacted the runway, the airplane immediately veered to the right, exited the runway surface, nosed over, and came to rest inverted. Postaccident examination of the airplane revealed that the nose gear upper torque link had fractured near the shock strut mount and separated from the shock strut, which resulted in a loss of directional control. Metallurgical examination of the fracture surfaces of the upper torque link revealed signatures consistent with a fatigue fracture.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Sys/Comp malf/fail (non-power) during landing (flare/touchdown) defining event

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Attain/maintain not possible
  • Aircraft › Aircraft systems › Landing gear system › Nose/tail landing gear › Fatigue/wear/corrosion

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 932 hours in all; 880 in this make and model; 22 in the last 90 days; 6 in the last 30 days; 855 as pilot in command
  • Last flight review: November 12, 2020
  • Medical certificate: BasicMed (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,151.5 hours
  • Last inspection: annual inspection, December 31, 2020; 35.7 hours since
  • Maximum gross weight: 2,300 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental O-300D (piston); 4,187 hours total

The flight

  • Departed from: OR8 Dug Bar OR at 11:30 am
  • Flight plan: none
  • Runway 30, 2,850 ft by 50 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 64°F (18°C), dew point 27°F (-3°C)
  • Altimeter: 30.10 inHg
  • Observation at 11:35 am from KJSY, 4 miles away

Weather report (METAR): KJSY 021835Z AUTO 00000KT 10SM CLR 18/M03 A3010 RMK AO2 T01821034

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

5 documents, released by the NTSB on February 28, 2023. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.