FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11CA345 · Stinson 108-1

23 Jul 2011 · Moses Lake, WA, United States Narrative disagrees

Stinson 108-1 · Accident: loss of control on ground during takeoff

From Moses Lake Municipal Airport (W20) to Moses Lake Municipal Airport (W20)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR11CA345
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

Stinson 108-1

Aircraft type
Stinson 108
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
N8318K
Onboard fatalities
Unknown
Route
From Moses Lake Municipal Airport (W20), Moses Lake, WATo Moses Lake Municipal Airport (W20), Moses Lake, WA
Aircraft age
Not recorded
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
Takeoff · rejected takeoff
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 stated that during the takeoff roll he had trouble maintaining directional control of the airplane. He elected to abort the takeoff and reduced the throttle to idle while applying both brakes. The airplane veered to the left off of the runway, nosed over, and came to rest inverted. The airplane's left wing strut and rudder received substantial damage. The pilot reported no preimpact mechanical malfunctions or failures that would have precluded normal operations.

Probable cause

The pilot's failure to maintain directional control during an aborted takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11CA345
Event ID
20110725X22913
Case number
WPR11CA345
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: 260bb12cfc011c3ecbd0fb331e000aae15b015fe88146f75f575cae41601a80f; retrieved 2026-09-15T16:30:09.806Z.