WPR09LA195 · Sungkwon KIM LONG-EZE
Sungkwon KIM LONG-EZE · Accident: loss of engine power (total) en route
From Redding Municipal Airport (RDD) to Eugene Airport (EUG)
Event
- NTSB case
- WPR09LA195
- 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
Sungkwon KIM LONG-EZE
- Aircraft type
- Sungkwon Kim LONG-EZE
- 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
- N342MS
- Operator
- Sung Kwon Kim
- Onboard fatalities
- Unknown
- Route
- From Redding Municipal Airport (RDD), Redding, CATo Eugene Airport (EUG), Eugene, 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
- En route · cruise
- 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 engine power (total)
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During cruise flight, the airplane's engine lost power. The pilot attempted to restart the engine, but was unsuccessful. He maneuvered the airplane for a forced landing onto an interstate highway. As the airplane descended, the wind became turbulent and gusty. According to the pilot, a wind gust "hit [the airplane's] nose suddenly." The pilot lost control of the airplane, and it impacted trees and came to rest next to the highway. Post-examination of the engine revealed no evidence of a mechanical malfunction that would have prevented the engine from developing power. The airframe gascolator contained debris, but the debris obstructed less than 5 percent of the screen and would not have affected fuel flow to the engine. The reason for the loss of engine power was not determined.
Probable cause
The loss of engine power for undetermined reasons. Contributing to the accident was the pilot's failure to maintain aircraft control during the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09LA195
- Event ID
- 20090416X72850
- Case number
- WPR09LA195
- 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: 1710ee17a7f4b11e50b54c5eb6c76fe7d599be53f88d522cdec1517ea642d213; retrieved 2026-09-15T10:56:41.421Z.