SEA93LA117 · Stinson 108-1
Stinson 108-1 · Accident: in flight collision with object during initial climb
From an unrecorded airport to Ogden Hinckley Airport (OGD)
Event
- NTSB case
- SEA93LA117
- 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
- 1 · 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-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
- N8589K
- Operator
- Boren, Roland K. · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Ogden Hinckley Airport (OGD), Ogden, UT
- 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
- Initial climb
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Lift-off, premature
- Pilot in command › Proper climb rate, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PIC INITIATED A TAKEOFF FROM A RUNWAY INTERSECTION, LIFTED OFF PREMATURELY, AND THE ACFT SETTLED BACK ONTO THE RUNWAY. THE PIC CONTINUED THE TAKEOFF AND LIFTED OFF AT THE END OF THE RUNWAY. THE ACFT SETTLED SLIGHTLY AFTER TAKEOFF AND BEGAN A SHALLOW CLIMB. WHEN THE ACFT APPROACHED POWER LINES AT AN ALTITUDE TOO LOW TO CLEAR THE WIRES, THE PILOT ATTEMPTED TO TURN TO AVOID IMPACT. THE LEFT WING STRUCK POWER LINES LOCATED ABOUT 2500 FT FROM THE END OF THE RUNWAY, AND THE ACFT DESCENDED UNCONTROLLED AND IMPACTED THE GROUND.
Probable cause
THE PREMATURE LIFTOFF BY THE PIC AND HIS FAILURE TO ATTAIN PROPER RATE OF CLIMB. FACTORS RELATING TO THE ACCIDENT WERE THE GUSTY CROSSWIND WEATHER CONDITIONS, THE FAILURE OF THE PIC TO USE ALL AVAILABLE RUNWAY, AND TRANSMISSION WIRES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA93LA117
- Event ID
- 20001211X12484
- Case number
- SEA93LA117
- 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: cc7862d62046afcc1f21d3f5b061606740454570a8c9c954f3a6d50c3926f3bc; retrieved 2026-09-21T00:33:17.873Z.