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

Cessna 172D accident near Auburn, Washington, December 7, 2017

On December 7, 2017, a 1962 Cessna 172D, registered N2351U, was substantially damaged in an accident during approach (VFR pattern final) near Auburn, Washington (Auburn Muni airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's loss of airplane control for reasons that could not be determined based on the available information.

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

What the record shows

Date
December 7, 2017
Place
Auburn, Washington · Auburn Muni · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172D D, built 1962 · all 172Ds on the register
Registration
N2351U · no longer on the register · serial 17249951
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that the airplane yawed right, and he experienced a loss of aileron control effectiveness while on final approach for landing. He applied engine power to go around, which he perceived to worsen the problem, then chose to reduce power and land. The airplane touched down on the runway about 45° off runway heading, continued off the runway, and impacted a water retention pond. Examination of the aileron flight control system revealed no evidence of a mechanical failure or malfunction. There was evidence that the right wing contacted the runway during landing, and aileron control cable tension could not be measured due to the damage to the wing. The reason for the reported aileron flight control malfunction could not be determined.

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. Flight control sys malf/fail during approach (VFR pattern final)
  2. Loss of control in flight during approach (VFR pattern final) defining event
  3. Collision with terrain or object (not controlled flight into terrain) during approach (VFR pattern final)

The NTSB's findings

  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: private
  • Ratings: single-engine land; single-engine sea
  • Flight time: 911 hours in all; 911 in this make and model; 11 in the last 90 days; 4 in the last 30 days; 811 as pilot in command
  • Last flight review: June 21, 2016
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,024.7 hours
  • Last inspection: annual inspection, January 25, 2017; 47 hours since
  • Landing gear: fixed
  • Engine: Continental O-300 (piston); 0 hours total

The flight

  • Departed from: S50 Auburn WA at 11:30 pm
  • Destination: S50 Auburn WA
  • Flight plan: none
  • Runway 16, 3,400 ft by 75 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 48°F (9°C), dew point 36°F (2°C)
  • Altimeter: 30.47 inHg
  • Observation at 11:53 pm from KSEA, 8 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

3 documents, released by the NTSB on December 15, 2020. 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.