The U.S. aircraft register, updated daily
Accidents · NTSB ERA09CA129 · Final report

Buckeye Dream Machine accident near Grant, Florida, December 28, 2008

On December 28, 2008 at about 1:50 pm local time, a Buckeye Dream Machine (powered parachute), registered N6068E, was substantially damaged in an accident during maneuvering (low-alt flying) near Grant, Florida (Valkaria Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain clearance from the wire.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
December 28, 2008 · about 1:50 pm local time
Place
Grant, Florida · Valkaria Airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Buckeye Dream Machine · all Dream Machines on the register
Registration
N6068E · no longer on the register · serial 4332
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot of the powered parachute was flying at an altitude of 500 feet above ground level when he elected to descend to identify an object he observed on a road. After descending over the roadway and identifying the object as "black cloth of some sort," the pilot noticed an overhead cable that appeared to be "fast approaching." The pilot maintained a low altitude; however, the top of the canopy collided with the unmarked wire. The aircraft swung upward, descended, and impacted the ground. The left main landing gear collapsed and several airframe braces were substantially damaged.

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

  1. Collision with terrain or object (not controlled flight into terrain) during maneuvering (low-alt flying) defining event

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained
  • cause Environmental issues › Physical environment › Object/animal/substance › Wire › Response/compensation
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: sport pilot
  • Flight time: 452 hours in all; 452 in this make and model; 6 in the last 90 days
  • Medical certificate: None
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: condition inspection
  • Maximum gross weight: 840 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 582DCDI (piston); 0 hours total

The flight

  • Departed from: X59 Valkaria FL
  • Destination: X26 Sebastian FL
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 59°F (15°C), dew point 57°F (14°C)
  • Altimeter: 30.27 inHg
  • Observation at 1:53 pm from MLB, 13 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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.