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

Piper PA-22 accident near Star City, Arkansas, September 1, 2008

On September 1, 2008 at about 3:15 pm local time, a Piper PA-22, registered N7253D, was substantially damaged in an accident during landing (landing roll) near Star City, Arkansas (Star City, Ar airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot failed to maintain directional control during landing. Contributing to the accident were the crosswinds and the rough terrain near the runway.

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

What the record shows

Date
September 1, 2008 · about 3:15 pm local time
Place
Star City, Arkansas · Star City, Ar · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-22 · all PA-22s on the register
Registration
N7253D · no longer on the register · serial 22-5079
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The commercial pilot stated that, on landing, he overflew the airport and, based on his observations, he anticipated ground turbulence. During the landing roll he encountered a gust of wind and lost control of the airplane. The plane departed the runway and fell off a 2-foot drop. Examination of the airplane revealed the left wing spar and left elevator were bent.

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. Other weather encounter during landing (landing roll)
  2. Loss of control on ground during landing (landing roll) defining event
  3. Runway excursion during landing (landing roll)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • factor Environmental issues › Physical environment › Terrain › Rough terrain › Contributed to outcome
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Response/compensation

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land
  • Flight time: 1,608 hours in all; 222 in this make and model; 71 in the last 90 days; 17 in the last 30 days
  • Medical certificate: Class 2
  • Injury: no injuries

The aircraft

  • Seats: 4
  • Landing gear: fixed
  • Engine: Textron Lycoming O-320 (piston); 0 hours total

The flight

  • Departed from: 5M1 De Witt AR
  • Destination: 55m Star City AR
  • Flight plan: none
  • Runway 18

Weather at the time

  • Light: daylight
  • Wind: from 070° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 81°F (27°C), dew point 70°F (21°C)
  • Altimeter: 30.05 inHg
  • Observation at 9:53 am from KPBF

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

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.