FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18LA047 · Cessna 172D D

7 Dec 2017 · Auburn, WA, United States

Cessna 172D D · Accident: loss of control in flight on approach

From Auburn Municipal Airport (S50) to Auburn Municipal Airport (S50)

Report a problem

Event

NTSB case
WPR18LA047
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 172D D

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N2351U
Operator
Unknown
Onboard fatalities
Unknown
Route
From Auburn Municipal Airport (S50), Auburn, WATo Auburn Municipal Airport (S50), Auburn, WA
Aircraft age
About 55 years (built 1962)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern final
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Not determined › Not determined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18LA047
Event ID
20171214X32057
Case number
WPR18LA047
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 3273c515da7cc6401d7f2accda9379973e6f8f92411255e266833c7211cc2d2b; retrieved 2026-09-16T06:08:57.725Z.