CHI00FA200 · Beech 35
Beech 35 · Accident: in flight collision with object while maneuvering
Event
- NTSB case
- CHI00FA200
- 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 35
- 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
- N947V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- Maneuvering
- 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 › Altitude/clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was destroyed after impacting power lines and terrain. Witnesses reported that the aircraft was flying at a low altitude when it hit the power lines. One witness stated that he had seen the aircraft "...flying low one time before down river." The azimuth and elevation of the sun were found to be 276.4 degrees and 25.9 degrees respectively. The wreckage path started about 100 feet from a set of approximately 60-foot high power lines and was oriented on an approximately 260-degree magnetic heading. The main wreckage was located about 440 feet from the power lines. The aircraft was equipped with a "V-tail" empennage. The tail surfaces were examined and both were found to have leading edge damage at the mid-span location. The leading edge skins of both surfaces were torn and exhibited longitudinal scratches back to the spar/stringer location. The entire tail assembly was broken loose from the airframe at the mount. The tail assembly was found about halfway between the power lines and the main wreckage. No anomalies, with regard to the airframe, engine, or systems were detected that could be associated with a preexisting condition.
Probable cause
the failure of the pilot to maintain clearance from the power line. Factors were the sunglare and the wire.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI00FA200
- Event ID
- 20001212X21370
- Case number
- CHI00FA200
- 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: 427a4d391fa86be8acb12ab58a2abf74da62daf44df54fef97cddb8d5942074f; retrieved 2026-09-20T21:02:12.320Z.