CEN11CA154

NTSB accident investigation · Powerchute Airwolf 912ULS · Alexandria, IN · January 14, 2011

Accident · Serious injuriesData collectionFinal report
Date
January 14, 2011, 16:00 local (21:00 UTC)
Place
Alexandria, IN
Injuries
1 serious
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N4306PPowerchute Airwolf 912ULS
Defining event
Approach-VFR go-around: Collision during takeoff/land
Weather
Visual (VMC) · Day
Status
Completed · report May 26, 2011
Report
Approved by Office Director
NTSB office
Central Region
Parties
Federal Aviation Administration
FAA report
20110114000299A
Case key
78195

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot's failure to maintain clearance with trees during an initial climb following an aborted landing.

Findings · 1

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: altitudeAircraft › Aircraft oper/perf/capability · Not attained/maintainedPowrachute AIRWOLF 912ULS: 2 casesAll aircraft: 1,310 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot of the powered parachute stated that he performed several touch-and-go landings at the departure airport. He then flew to his house where he attempted a landing on a 600-foot-long flat grass strip. During the landing attempt, the pilot was focused on the touchdown point and, when he looked up he noticed that the powered parachute veered off the right side of the grass strip. He added full engine power and attempted an aborted landing. During the initial climb, the powered parachute struck the tree tops. The pilot stated that the powered parachute can take off and land in about 50 feet and that he had not previously attempted a landing at his residence.

Factual narrative

The pilot of the powered parachute stated that he performed several touch and go landings at the departure airport. He then flew to his house where he attempted a landing on a 600 foot long and flat grass strip. During the landing attempt, the pilot was "focused" on the touchdown point and when he looked up, he noticed that the powered parachute veered off the right side of the grass strip. He added full engine power and attempted an aborted landing. During the initial climb, the powered parachute struck the tree tops. The powered parachute frame was bent. The pilot sustained a serious injury due to a fractured ankle. The pilot stated that the powered parachute can take off and land in about 50 feet and that he had not previously attempted a landing at his residence.

Aircraft

Registration
N4306P
Reported as
Powerchute Airwolf 912ULS
Category
Powered parachute
Serial number
A146ULS
Engine
Rotax, 100 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Pilot
Registered owner
Pilot
Airworthiness certificate
Special, Experimental light sport (Special)
Departed
Alexandria, IN
Destination
PVT · Alexandria, IN
Airport
PVT · Private, runway 27, 600 × ft, grass/turf

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
49
Injuries
Serious
Certificates
Recreational, Sport Pilot
Airplane ratings
Single-engine land
Medical
Sport pilot
Seat
Center
Flight hours
20 total · 20 in this make and model

Weather

Conditions
Visual (VMC) · Day
Wind
180° at 5 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
27 °F, dew point 18 °F
Altimeter
30.23 inHg
Observed at
AID

Docket · 1

The files NTSB released with the investigation on February 23, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 814 KB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.