SEA92LA102 · Beech S35
Beech S35 · Accident: in flight collision with terrain/water en route
From Renton Municipal Airport (RNT) to Coeur D'Alene Airport - Pappy Boyington Field (COE)
Event
- NTSB case
- SEA92LA102
- 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
Beech S35
- Aircraft type
- Beechcraft 35
- 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
- N9015S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Renton Municipal Airport (RNT), Renton, WATo Coeur D'Alene Airport - Pappy Boyington Field (COE), Coeur d'Alene, ID
- 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
- 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 terrain/water
- 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 › In-flight planning/decision, poor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A CROSS COUNTRY FLIGHT, THE AIRPLANE COLLIDED WITH HILLY TERRAIN. IMPACT SIGNATURES INDICATE THAT THE AIRPLANE COLLIDED WITH A HILL IN LEVEL FLIGHT, APPROXIMATELY 120 FEET BELOW THE RIDGE LINE. THE AIRPLANE CONTINUED UP THE HILL, THEN BECAME AIRBORNE AND TRAVELLED ANOTHER 190 FEET THROUGH POWER LINES, WHICH SEPARATED THE LEFT WING AND RUDDERVATOR. THE AIRPLANE CONTINUED OVER THE CREST, IMPACTING THE GROUND AND SLIDING DOWN THE OPPOSITE SIDE OF THE HILL. THE ENGINE CONTINUED ACROSS A VALLEY IMPACTING ANOTHER HILL. THE REMAINDER OF THE FUSELAGE WAS DESTROYED BY FIRE. DURING THE POST CRASH INVESTIGATION THERE WAS NO EVIDENCE TO INDICATE A MECHANICAL FAILURE OR MALFUNCTION.
Probable cause
POOR IN FLIGHT PLANNING/DECISION. FACTORS TO THE ACCIDENT WERE: MOUNTAINOUS/HILLY TERRAIN AND TERRAIN CLEARANCE WAS NOT MAINTAINED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA92LA102
- Event ID
- 20001211X14734
- Case number
- SEA92LA102
- 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: 8bbce03d55cbefe16e209abd1b6479ae79d05327173c730cad0ad77cff6cc1d3; retrieved 2026-09-21T01:12:05.171Z.