ERA09CA129 · Buckeye Dream Machine
Buckeye Dream Machine · Accident: collision with terrain/object (non-CFIT) while maneuvering
From Valkaria Airport (X59) to Sebastian Municipal Airport (X26)
Event
- NTSB case
- ERA09CA129
- 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
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
Buckeye Dream Machine
- Aircraft type
- Buckeye DREAM MACHINE
- Category
- Powered Parachute
- 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
- N6068E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Valkaria Airport (X59), Valkaria, FLTo Sebastian Municipal Airport (X26), Sebastian, FL
- 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 · low-altitude flying
- Defining eventThe 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
- Collision with terrain/object (non-CFIT)
- 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
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
The pilot's failure to maintain clearance from the wire.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA129
- Event ID
- 20090105X10554
- Case number
- ERA09CA129
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 715816527ef3acd8c95fe4041de8a7bd08a2ff162aa56adc3f13bdf08f47219f; retrieved 2026-09-15T10:39:53.977Z.