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

Amateur-built STARDUSTER SA-300 accident near Vidalia, Louisiana, April 27, 2012

On April 27, 2012 at about 9:15 pm local time, a amateur-built STARDUSTER SA-300, registered N4523, was substantially damaged in an accident during landing near Vidalia, Louisiana (Concordia Parish airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The failure of the airplane’s right main landing gear due to a pre-existing fatigue crack and corrosion.

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

What the record shows

Date
April 27, 2012 · about 9:15 pm local time
Place
Vidalia, Louisiana · Concordia Parish · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Amateur-built STARDUSTER SA-300
Registration
N4523 · registry record · serial 259
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

While on the landing roll in a grassy area with rough terrain, the airplane's right main landing gear broke and separated from the airplane. The pilot was then unable to maintain directional control of the airplane, which then nosed over and came to rest inverted with substantial damage to the upper wing and rudder. A postaccident examination of the airplane revealed that the right landing gear strut had a pre-existing fatigue fracture with interior corrosion, which was not discovered during a previous inspection.

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. Landing gear collapse during landing defining event

The NTSB's findings

  • cause Aircraft › Aircraft systems › Landing gear system › Main landing gear › Failure
  • cause Aircraft › Aircraft systems › Landing gear system › Main landing gear › Fatigue/wear/corrosion

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 2,761 hours in all; 69 in this make and model; 18 in the last 90 days; 6 in the last 30 days; 2,690 as pilot in command
  • Last flight review: August 12, 2011
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: rear
  • Injury: no injuries

The aircraft

  • Airframe total time: 427 hours
  • Last inspection: condition inspection, September 2, 2011
  • Maximum gross weight: 1,750 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Cont Motor C-125-2 (piston); 0 hours total

The flight

  • Departed from: 0R4 Vidalia LA at 9:00 pm
  • Destination: 0R4 Vidalia LA
  • Flight plan: none
  • Runway 14, 3,700 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 150° at 7 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 4,600 ft
  • Temperature: 81°F (27°C), dew point 63°F (17°C)
  • Altimeter: 30.00 inHg
  • Observation at 9:15 pm from KHEZ, 11 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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.