FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA186 · Cessna 172 M

12 Mar 2017 · Hillsboro, OR, United States

Twin Oaks Airpark Cessna 172 M · Accident: loss of control on ground during landing

From Stark's Twin Oaks Airpark (7S3) to Stark's Twin Oaks Airpark (7S3)

Report a problem

Event

NTSB case
GAA17CA186
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 172 M

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
N5440H
Onboard fatalities
Unknown
Route
From Stark's Twin Oaks Airpark (7S3), Hillsboro, ORTo Stark's Twin Oaks Airpark (7S3), Hillsboro, OR
Aircraft age
About 42 years (built 1975)
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
Landing · landing roll
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 on ground
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

The pilot reported that, during the landing roll with a "light quartering tailwind," the airplane veered off the runway to the left into soft mud and nosed over.

The vertical stabilizer and rudder sustained substantial damage.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

The nearest automated weather observation station, located 7 nautical miles from the accident airport, about the time of the accident, recorded variable wind at 5 knots. The pilot reported that he landed on runway 2.

Probable cause

The pilot's failure to maintain directional control during the landing roll in quartering tailwind conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA186
Event ID
20170314X91011
Case number
GAA17CA186
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: 1886dc43da4984eb590f4552d21ebe49774c53457d396ea520352d97f4c3a2f8; retrieved 2026-09-16T05:05:57.837Z.