- Date
- June 24, 1994, 17:00 local (23:00 UTC)
- Place
- Scottsbluff, NE
- Injuries
- 1 serious
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N3147BMustari Dragonfly Mark II
- Weather
- Visual (VMC) · Day
- Status
- Completed · report January 12, 1995
- Report
- Approved by Office Director
- FAA report
- 19940624016719A
- Case key
- 9338
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
the private pilot's inadequate preflight planning/preparation. A related factor is the high density altitude.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
The pilot reported during departure the homebuilt airplane reached about 150 to 200 feet above the ground, and wouldn't climb any further. He attempted to return to the airport, but the airplane struck power lines and came to rest in a soybean field. The pilot reported the temperature was 92 degrees fahrenheit at the time of the accident, and the airport elevation is 3,965 feet. He stated he could have avoided the accident 'by restricting my flights to lower elevation airports when temp. Is above 90 degrees.'
Factual narrative
On June 24, 1994, at 1700 mountain daylight time, a Mustari Dragonfly Mark II, N3147B, piloted by the private pilot/owner, sustained substantial damage when it struck power lines while maneuvering after takeoff from the William B. Heilig Airport, in Scottsbluff, Nebraska. The pilot, the sole occupant, received serious injuries. Visual meteorological conditions prevailed for the flight, no flight plan was filed. The personal flight was originating from Scottsbluff, Nebraska, with an intended destination of Hastings, Nebraska.
The pilot stated he flew to Scottsbluff to visit his mother in the hospital. He arrived about midday, and had the airplane topped off with 100LL fuel. It was about 1650 when the pilot attempted to depart the Scottsbluff airport. He stated: "Aircraft ascended to about 150 - 200 feet AGL and would no longer climb. Because of rising terrain I decided to turn back to the airport. I knew I would lose altitude on my turn...Once I got turned around I was looking at two sets of power lines...." The airplane struck the first set of power lines and came to rest in a soybean field.
The pilot stated the airport elevation was 3,965 feet, the temperature was 92 degrees Fahrenheit, and density altitude had decreased the airplanes performance. He stated there was no mechanical malfunction, and indicated he could have prevented the accident "...by restricting my flights to lower elevation airports when temp. is above 90 [degrees]."
Aircraft
- Registration
- N3147B
- Reported as
- Mustari Dragonfly Mark II (DRAGONFLY)
- Category
- Airplane, amateur-built
- Serial number
- 225
- Airframe hours
- 169
- Engine
- Unknown, 71 horsepower, reciprocating
- Damage
- Destroyed
- Flight
- Personal · Part 91
- Operator
- Fowler, Kevin A.
- Registered owner
- Fowler, Kevin A.
- Airworthiness certificate
- Special, Experimental (Special)
- Last inspection
- Continuous airworthiness · October 27, 1993 · 69 hours before
- Destination
- HSI · Hastings, NE
- Airport
- BFF · William B. Heilig Field, runway 30, 8,280 × 150 ft
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 36
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, Valid Medical--no waivers/lim.
- Seat
- Left
- Flight hours
- 605 total · 100 in this make and model · 562 as pilot in command · 27 in the last 90 days · 15 in the last 30 days · 3 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 10° at 4 knots
- Visibility
- 25 statute miles
- Lowest ceiling
- None
- Temperature
- 91 °F, dew point 43 °F
- Altimeter
- 29.00 inHg
- Observed at
- BFF, 1 nm away
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.