CEN11CA154 · Powerchute LLC Airwolf 912ULS
Powerchute LLC Airwolf 912ULS · Accident: collision with terrain/object (non-CFIT) during takeoff
From Alexandria, IN to Alexandria, IN (private airstrip)
Event
- NTSB case
- CEN11CA154
- 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
Powerchute LLC Airwolf 912ULS
- Aircraft type
- Powerchute AIRWOLF 912
- 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
- N4306P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Alexandria, INTo Alexandria, IN (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
- Takeoff
- 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)
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB 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 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.
Probable cause
The pilot's failure to maintain clearance with trees during an initial climb following an aborted landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11CA154
- Event ID
- 20110119X73856
- Case number
- CEN11CA154
- 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. 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: 0a433d74ee031bb4985997bcf5920754271bd2b8c2ff21a40b4ab6529d44ee26; retrieved 2026-09-15T15:42:00.877Z.