FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09LA555 · Destiny Powered Parachutes LLC DESTINY 2000

24 Aug 2009 · Arcanum, OH, United States

Destiny Powered Parachutes LLC DESTINY 2000 and Phantom Aircraft Phantom X-1E · Accident: midair collision on approach

Report a problem

Event

NTSB case
CEN09LA555
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
1 · 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

Aircraft 1 · Destiny Powered Parachutes LLC DESTINY 2000

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
N5604B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Arcanum, OH (private airstrip)To Arcanum, OH (private airstrip)
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
Approach · VFR pattern final
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
Midair collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Aircraft 2 · Phantom Aircraft Phantom X-1E

Aircraft type
Phantom PHANTOM
Category
Airplane
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
UNREG
Operator
Unknown
Onboard fatalities
Unknown
Route
From Arcanum, OH (private airstrip)To Arcanum, OH (private airstrip)
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
Midair collision
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

  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.”

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09LA555
Event ID
20090902X21452
Case number
CEN09LA555
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2009-08-25.
  • API snapshot SHA-256: 180ad2901072f90ef6cf357a17f19947cc9ccea91d07946a11536c1afd1c4f98; retrieved 2026-09-13T18:04:48.980Z.