Powrachute Sky Rascal accident near Indio, California, March 30, 2012
On March 30, 2012 at about 1:35 am local time, a Powrachute Sky Rascal (powered parachute), registered UNREG, was substantially damaged in an accident during initial climb near Indio, California. It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The operation of an airplane by a non-certificated pilot. Contributing to the accident was the non-certificated pilot's failure to maintain clearance from powerlines during initial climb in gusty wind conditions.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 30, 2012 · about 1:35 am local time
- Place
- Indio, California · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Powrachute Sky Rascal
- Registration
- UNREG · no longer on the register · serial None
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The non-certificated pilot reported that he waited for the wind to subside before taking off. The pilot said that when the wind subsided, he departed, but during the initial climb, the powered parachute encountered either a downdraft or a gust of wind and collided with a set of powerlines. The powered parachute was subsequently consumed by fire after becoming entangled in the wires. The pilot reported no mechanical malfunctions or failures with the aircraft 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
- Turbulence encounter during initial climb defining event
- Collision with terrain or object (not controlled flight into terrain) during initial climb
The NTSB's findings
- factor Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained
- Environmental issues › Conditions/weather/phenomena › Wind › Gusts › Effect on operation
- Environmental issues › Physical environment › Object/animal/substance › Wire › Effect on operation
- cause Personnel issues › Experience/knowledge › Experience/qualifications › Qualification/certification › Pilot
Pilot
- Medical certificate: None
- Seat: sngl
- Injury: serious injuries
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 600 lb
- Seats: 1
- Landing gear: fixed
- Engine: Rotax 503 (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: Indio CA at 1:35 am
- Destination: Indio CA
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 100° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 84°F (29°C), dew point 37°F (3°C)
- Altimeter: 29.79 inHg
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.
Other NTSB records under UNREG the same tail number, which may have belonged to a different aircraft at the time
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.