Buckeye DREAM MACHINE accident near Hartford, Kentucky, July 10, 2016
On July 10, 2016 at about 11:45 pm local time, a 2002 Buckeye DREAM MACHINE (powered parachute), registered N3519T, was substantially damaged in an accident during takeoff (rejected takeoff) near Hartford, Kentucky (Ohio County airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
A partial loss of engine power for reasons that could not be determined and the pilot’s failure to maintain directional control during the aborted takeoff.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 10, 2016 · about 11:45 pm local time
- Place
- Hartford, Kentucky · Ohio County · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Buckeye DREAM MACHINE NO SERIES, built 2002 · all DREAM MACHINEs on the register
- Registration
- N3519T · registry record · serial 4064
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The student pilot of the powered parachute reported that, during the takeoff roll from an airport parking lot, the engine started to "sputter," so he chose to abort the takeoff. While attempting to do so, he lost control of the powered parachute and collided with a fence, which resulted in substantial damage to the airframe. A postaccident examination and test run of the engine revealed no evidence of preimpact mechanical malfunctions or anomalies that would have precluded normal operation.
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
What happened, in order
- Loss of engine power (partial) during takeoff
- Loss of control on ground during takeoff (rejected takeoff) defining event
- Miscellaneous/other during takeoff
- Collision with terrain or object (not controlled flight into terrain) during takeoff
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- Environmental issues › Physical environment › Object/animal/substance › Fence/fence post › Contributed to outcome
Dual student
- Certificate: student
- Flight time: 30 hours in all; 15 in this make and model
- Medical certificate: Sport Pilot
- Seat: ctr
- Injury: serious injuries
The aircraft
- Airframe total time: 197 hours
- Last inspection: condition inspection, May 15, 2016
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 582 (piston); 197 hours total
The flight
- Departed from: JQD Hartford KY at 9:45 pm
- Destination: JQD Hartford KY
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 270° at 3 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 4,600 ft
- Temperature: 88°F (31°C), dew point 64°F (18°C)
- Altimeter: 30.00 inHg
- Observation at 11:56 pm from OWB, 22 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flig | 1 |
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA16LA254.