The U.S. aircraft register, updated daily
Accidents · NTSB CEN10LA492 · Final report

Infinity INFINITY accident near Little Rock, Arkansas, August 12, 2010

On August 12, 2010 at about 1:00 am local time, a Infinity INFINITY (powered parachute), registered N208FA, was substantially damaged in an accident during uncontrolled descent near Little Rock, Arkansas (None airport). It was a personal flight under general aviation rules (Part 91). 2 people were seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The failure of the control lanyard for undetermined reasons.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 12, 2010 · about 1:00 am local time
Place
Little Rock, Arkansas · None · map
Type
Accident
Injuries
2 people were seriously injured.
Weather
visual conditions (good weather)
Aircraft
Infinity INFINITY
Registration
N208FA · no longer on the register · serial IPP207
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

While the powered parachute was in a right descending spiral from 800 feet to 200 feet, the pilot and his passenger felt a violent shudder. The pilot could not visually detect anything unusual with the parachute and attempted to return to level flight by reducing engine power and adding opposite control input. Despite his efforts, the aircraft did not respond; it continued in a steep descending turn until it impacted the water. A postaccident examination of the aircraft revealed that the parachute experienced a seam failure at the 5th and 6th cell seam. In addition, a broken control lanyard was found. The reason for the control lanyard’s failure was not determined.

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

  1. Abrupt maneuver during maneuvering
  2. Flight control sys malf/fail during uncontrolled descent defining event
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Aircraft › Aircraft systems › Flight control system › (general) › Failure
  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: flight instructor, private, sport pilot
  • Ratings: single-engine land; instructor: powered-lift; rotorcraft: powered-lift
  • Flight time: 410 in this make and model
  • Medical certificate: None
  • Seat: frt
  • Injury: serious injuries

The aircraft

  • Last inspection: annual inspection
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 582 (piston); 0 hours total

The flight

  • Departed from: ORK N Little Rock AR at 1:15 am
  • Destination: ORK N Little Rock AR
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 91°F (33°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Flight crew2

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.

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.