FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00LA255 · Stinson 108-2

8 Jul 2000 · Minden, NV, United States

Stinson 108-2 · Accident: loss of control on ground/water during takeoff

From Minden-Tahoe Airport (MEV) to Minden-Tahoe Airport (MEV)

Report a problem

Event

NTSB case
LAX00LA255
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
0
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-2

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
N264C
Operator
William E. Yoder · private individual
Onboard fatalities
Unknown
Route
From Minden-Tahoe Airport (MEV), Carson City, NVTo Minden-Tahoe Airport (MEV), NV
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
First occurrenceThe 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/water
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

  • Pilot in command › Compensation for wind conditions, inadequate
  • Pilot in command › Directional control, not maintained

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

NTSB narrative

After landing, the airplane was taxied back for departure. The airplane yawed to the left after application of power and the pilot corrected with right rudder. The takeoff was proceeding normally when the tail suddenly veered to the left and then to the right. The pilot thought he encountered a dust devil or gust of wind. At this time the airplane was 2 to 3 feet in the air and headed about 50 to 70 degrees to the runway heading. He did not feel it prudent to attempt to realign with the runway and continued straight ahead. About 50 feet past the edge of the runway, the propeller and wheels began contacting sage brush that was 2 to 5 feet high. The airplane descended into the ground and nosed over onto its back.

Probable cause

failure of the pilot to compensate for a sudden wind shift resulting in a loss of directional control and collision with high vegetation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00LA255
Event ID
20001212X21501
Case number
LAX00LA255
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: dbf84677b28997c81f5b89b118f66c8c9570ec33814cd2564e744a09ceb2c002; retrieved 2026-09-22T12:43:11.268Z.