FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA99LA162 · Stinson 108-2

15 Sept 1999 · Burley, ID, United States

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

From Southwest Wyoming Regional Airport (RKS) to Roseburg Regional Airport (RBG)

Report a problem

Event

NTSB case
SEA99LA162
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
N9358K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Southwest Wyoming Regional Airport (RKS), Rock Springs, WYTo Roseburg Regional Airport (RBG), Roseburg, OR
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
Landing · landing roll
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 › Directional control, not maintained

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

NTSB narrative

The pilot made an approach and landing to a 4,094 feet long by 80 feet wide, asphalt runway. During the landing roll, the pilot applied light braking to slow for an upcoming taxiway. While braking, the aircraft drifted left of the runway centerline. The pilot then applied right rudder and right brake which, the pilot believed to be ineffective. The aircraft veered off the runway and collided with a taxiway marker, resulting in the collapse of the left main gear and substantial damage to the fuselage. A post-accident examination of the braking system revealed no malfunction or failure.

Probable cause

The pilot's failure to maintain directional control during the landing roll. Factors include a taxiway marking sign located adjacent to the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA99LA162
Event ID
20001212X19883
Case number
SEA99LA162
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: 5ea7a38e15500a824d311daa7ec301127f1c7f542375ab12e358e40ee84f0f6c; retrieved 2026-09-22T14:07:58.936Z.