Destiny Powered Parachutes LLC DESTINY 2000 and Phantom Aircraft Phantom mid-air collision near Arcanum, Ohio, August 25, 2009
On August 25, 2009, 2 aircraft, Destiny Powered Parachutes LLC DESTINY 2000 (N5604B) and Phantom Aircraft Phantom (UNREG), were involved in a mid-air collision near Arcanum, Ohio (Private airport). 1 person was killed and 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
The failure of pilot of the other aircraft to maintain an adequate visual lookout in order to avoid the collision with an aircraft on final approach to land.
The failure of pilot to maintain an adequate visual lookout in order to avoid the collision with an aircraft on final approach to land.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 25, 2009
- Place
- Arcanum, Ohio · Private · map
- Type
- Accident · mid-air collision
- Injuries
- 1 person was killed and 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Destiny Powered Parachutes LLC DESTINY 2000 · all DESTINY 2000s on the register
- Registration
- N5604B · no longer on the register · serial 1C0301RWB
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
- Aircraft 2
- Phantom Aircraft Phantom X-1E, amateur-built
- Registration
- UNREG · no longer on the register · serial 05300021
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative for the Destiny Powered Parachutes LLC DESTINY 2000 final · quoted from the NTSB record
The Destiny 2000 powered parachute and the Phantom aircraft were returning from separate local flights when the in-flight collision occurred. The powered parachute was operating out of an east-west grass airstrip located on the pilot’s property. The pilot of the Phantom aircraft was operating out of a separate nearby north-south grass airstrip located on his property. The Phantom aircraft pilot reported that he intended to make one more “large circle” around his property, about 50 feet above ground level, before landing. He reported that as he was coming out of the turn he saw a car on the road and when he looked up again the powered parachute was directly in front of him. He stated that he did not see the powered parachute prior to the collision and believed that the pilot of the powered parachute did not see his aircraft. He noted that trees may have obscured the pilots’ view of the other aircraft. A witness stated that the pilot of the powered parachute appeared to be on final approach to land to the east as the Phantom aircraft converged from the south. The aircraft collided over the west end of the runway. The witness added that neither aircraft appeared to be experiencing any difficulties prior to the collision. A postaccident examination of both aircraft did not reveal any anomalies consistent with a preimpact failure or malfunction. Weather conditions were clear with light winds at the time of the accident. The accident occurred approximately 23 minutes after sunset. Both aircraft were equipped with operating strobe lights. Regulations state that aircraft approaching to land have the right-of-way over other aircraft. However, they also state that “vigilance shall be maintained by each person operating an aircraft so as to see and avoid other aircraft.”
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 NTSB's narrative for the Phantom Aircraft Phantom final · quoted from the NTSB record
The Destiny 2000 powered parachute and the Phantom aircraft were returning from separate local flights when the in-flight collision occurred. The powered parachute was operating out of an east-west grass airstrip located on the pilot’s property. The pilot of the Phantom aircraft was operating out of a separate nearby north-south grass airstrip located on his property. The Phantom aircraft pilot reported that he intended to make one more “large circle” around his property, about 50 feet above ground level, before landing. He reported that as he was coming out of the turn he saw a car on the road and when he looked up again the powered parachute was directly in front of him. He stated that he did not see the powered parachute prior to the collision and believed that the pilot of the powered parachute did not see his aircraft. He noted that trees may have obscured the pilots’ view of the other aircraft. A witness stated that the pilot of the powered parachute appeared to be on final approach to land to the east as the Phantom aircraft converged from the south. The aircraft collided over the west end of the runway. The witness added that neither aircraft appeared to be experiencing any difficulties prior to the collision. A postaccident examination of both aircraft did not reveal any anomalies consistent with a preimpact failure or malfunction. Weather conditions were clear with light winds at the time of the accident. The accident occurred approximately 23 minutes after sunset. Both aircraft were equipped with operating strobe lights. Regulations state that aircraft approaching to land have the right-of-way over other aircraft. However, they also state that “vigilance shall be maintained by each person operating an aircraft so as to see and avoid other aircraft.”
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 for the Destiny Powered Parachutes LLC DESTINY 2000 from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during approach (VFR pattern final) defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot of other aircraft
- Environmental issues › Conditions/weather/phenomena › Light condition › Low light › Effect on operation
Pilot
- Medical certificate: None
- Seat: sngl
- Injury: fatal
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 650 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 582 (piston); 0 hours total
The flight
- Departed from: PVT Arcanum OH at 11:45 pm
- Destination: PVT Arcanum OH
- Flight plan: none
- Runway 09, 1,200 ft by 50 ft
Weather at the time
- Light: dusk
- Wind: from 130° at 4 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 70°F (21°C), dew point 57°F (14°C)
- Altimeter: 30.15 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
The factual record for the Phantom Aircraft Phantom from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during maneuvering (low-alt flying) defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
- Environmental issues › Conditions/weather/phenomena › Light condition › Low light › Effect on operation
Pilot
- Certificate: sport pilot
- Ratings: single-engine land; rotorcraft: powered-lift
- Flight time: 297 hours in all; 65 in this make and model; 293 as pilot in command
- Medical certificate: Sport Pilot
- Seat: sngl
- Injury: serious injuries
The aircraft
- Airframe total time: 74 hours
- Last inspection: condition inspection, January 25, 2009
- Maximum gross weight: 550 lb
- Seats: 1
- Landing gear: fixed
- Engine: Rotax 503 (piston); 0 hours total
The flight
- Departed from: PVT Arcanum OH
- Destination: PVT Arcanum OH
- Flight plan: none
- Runway 36, 700 ft by 50 ft
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight 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.
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 documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text 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 CEN09LA555.