SEA02FA109 · Beech A35
Beech A35 · Accident: in flight collision with object during landing
From S67 · Nampa, ID to Atlanta Airport (55H)
Event
- NTSB case
- SEA02FA109
- 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
- 2 · 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
Beech A35
- 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
- N658B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From S67 · Nampa, IDTo Atlanta Airport (55H), Atlanta, 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
- Landing · aborted
- 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
- Tree(s)
- 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 › Clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Witnesses reported observing the aircraft circle the airport before setting up an approach to runway 34. The witnesses reported that the aircraft was too high on final approach and the pilot aborted the landing about mid-field to two-thirds of the way down the runway and 20 to 30 feet agl. The aircraft made a right turn and collided with trees and subsequently the terrain within one-half mile from the departure end of the runway. A post-crash fire consumed the wreckage. Documentation of the accident site noted that the aircraft collided with the tops of approximately four trees before colliding with the ground. The airport facilities directory for this airstrip states, "Airport is located in mountainous area, high timbered ridges limit maneuvering area." "Recommend land Rwy 34, depart Rwy 16..." Post-accident examination of the engine did not reveal evidence of a mechanical failure or malfunction.
Probable cause
Clearance from an object was not maintained during an aborted landing. Trees and mountainous terrain were factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA02FA109
- Event ID
- 20020625X00964
- Case number
- SEA02FA109
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2002-06-22.
- API snapshot SHA-256: 4c1f5d4d682d69658d7e0b9ad7c0d015a5d043fff1dfa9d84135bb2e99912ffb; retrieved 2026-09-20T19:59:07.047Z.