CHI08CA059 · Infinity Commander
Infinity Commander · Accident: in flight collision with object during initial climb
From Hot Springs Vlg, AR to an unrecorded destination
Event
- NTSB case
- CHI08CA059
- 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
Infinity Commander
- Aircraft type
- Infinity COMMANDER
- 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
- N719AR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hot Springs Vlg, ARTo not recorded
- 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
- Initial climb
- First occurrenceThe 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Pilot in command › Altitude/clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that during a local personal flight he was climbing after a touch and go. He stated that he "started feeling the [powered parachute] start rocking and rolling. ... We were climbing well enough to clear any trees. As we approached the north end of the pasture I lost altitude and began to swing, as if there were turbulence in that area of the pasture. I realized that I may not clear the trees so I began to cut a sharp right turn to avoid the trees and the propeller caught a branch and shattered and we went down next to a creek bed." The pilot reported no mechanical malfunctions with the powered parachute reference the accident flight.
Probable cause
The pilot not maintaining clearance/altitude from the trees during takeoff initial climb. Factors were the trees and reported turbulent winds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08CA059
- Event ID
- 20080116X00054
- Case number
- CHI08CA059
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: e5194643f5c2dfa8fc243def528f63369cd01fe9bb62db3fce4555ddc130d96a; retrieved 2026-09-21T08:41:03.617Z.