WPR23LA281 · SIX Chuter Inc SR7
SIX Chuter Inc SR7 · Accident: collision during takeoff/landing
Event
- NTSB case
- WPR23LA281
- 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
- Event fatalities
- Unknown
- 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
SIX Chuter Inc SR7
- Aircraft type
- Six Chuter SR7
- Category
- Ultralight
- 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
- N942WA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 26 years (built 1997)
- 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 103: Ultralight
- 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 during takeoff/landing
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the powered parachute reported that, after raising the wing and during takeoff, the powered parachute experienced an unexpected right turn. He checked to see if any steering lines were tangled but could not confirm that they were. He attempted to increase the right turn to avoid impacting a tree but was unable to clear it, and the powered parachute came to rest in the treeThis is not supported in the 6120 in the docket. You’ll need to add a record of conversation if you want to keep it. . A stabilizer tube and a center of gravity tube sustained substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the powered parachute that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain directional control during takeoff and subsequent impact with a tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR23LA281
- Event ID
- 20230724192684
- Case number
- WPR23LA281
- 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, cause areas. 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: 83d037d53d2f2ab5a42e62f9700d29feaa6a87fe08e8f9f851fba70d0530f510; retrieved 2026-09-16T17:53:24.687Z.