WPR09CA424 · Silvaire LUSCOMBE 8A
Silvaire LUSCOMBE 8A · Accident: runway excursion during landing
From Lenhardt Airpark (7S9) to Sandy River Airport (03S)
Event
- NTSB case
- WPR09CA424
- 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
Silvaire LUSCOMBE 8A
- Aircraft type
- Silvaire LUSCOMBE 8
- 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
- N2218K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lenhardt Airpark (7S9), Hubbard, ORTo Sandy River Airport (03S), Sandy, 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
- 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
- Runway excursion
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The wind was calm as the pilot approached the airport's 2,115-foot-long Runway 26 and attempted to land. The pilot stated that he terminated his first two approaches to the runway because he was too fast and too high. In part, this event was due to "obstacles" in proximity to the approach end of the runway. The Federal Aviation Administration's "Airport Facility Directory" indicates that the closest obstacle to the runway's approach end is located 115 feet from the runway's extended centerline. During the pilot's third attempted landing, he was also too high and too fast but he decided to land anyway. The airplane touched down long, overran the departure end, impacted vines, and nosed over. According to the pilot, there was no mechanical malfunction with his airplane and the accident could have been prevented had he made a go-around.
Probable cause
The pilot's decision to continue the landing rather than execute a go-around. Contributing to the accident was the pilot's failure to maintain proper airspeed and altitude during the approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09CA424
- Event ID
- 20090828X04455
- Case number
- WPR09CA424
- 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, coordinates. 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: 55d730f91cb2499ced75016ace4a3121075add43312e7176d9d54fc19bce79b6; retrieved 2026-09-15T12:51:33.959Z.