Beech 35 accident near Columbus, Nebraska, July 15, 2000
On July 15, 2000 at about 11:30 pm local time, a Beech 35, registered N947V, was destroyed in an accident near Columbus, Nebraska. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
the failure of the pilot to maintain clearance from the power line. Factors were the sunglare and the wire.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 15, 2000 · about 11:30 pm local time
- Place
- Columbus, Nebraska · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Beech 35 · all 35s on the register
- Registration
- N947V · no longer on the register · serial D-880
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 400 hours in all; 200 in this make and model
- Medical certificate: Class 3 (valid medical--no waivers/lim.)
- Seat: left
The aircraft
- Airframe total time: 3,841 hours
- Last inspection: annual inspection, January 20, 2000; 160 hours since
- Maximum gross weight: 2,550 lb
- Seats: 4
- Landing gear: retractable
- Engine: Continental E-185-8 (piston); 0 hours total
- Fire on the ground
The flight
- Flight plan: none
- Runway 0
Weather at the time
- Light: daylight
- Wind: from 120° at 9 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 190°F (88°C), dew point 162°F (72°C)
- Altimeter: 29.00 inHg
- Observation at 11:55 pm from OLU, 4 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.