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

Piper PA-18-150 accident near Burlington, North Carolina, April 29, 2012

On April 29, 2012 at about 9:30 pm local time, a Piper PA-18-150, registered N91250, was substantially damaged in an accident during landing (landing roll) near Burlington, North Carolina (Burlington Almance Regional airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s loss of directional control during the landing roll, which resulted in a runway excursion.

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

What the record shows

Date
April 29, 2012 · about 9:30 pm local time
Place
Burlington, North Carolina · Burlington Almance Regional · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-18-150 · all PA-18-150s on the register
Registration
N91250 · registry record · serial 18-8209015
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

According to the pilot, during the landing roll, the airplane veered to the left. The pilot applied right rudder in an attempt to arrest the turn, but the airplane continued to the left, ran off the runway, and struck a runway sign, resulting in substantial damage to the left wing. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

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. Runway excursion during landing (landing roll) defining event
  2. Collision during takeoff/land during landing (landing roll)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 260 hours in all; 32 in this make and model; 2 in the last 90 days; 1 in the last 30 days
  • Last flight review: June 18, 2010
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: frt
  • Injury: no injuries

The aircraft

  • Airframe total time: 675 hours
  • Last inspection: annual inspection, July 29, 2011
  • Maximum gross weight: 1,750 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-320 SERIES (piston); 0 hours total

The flight

  • Departed from: 59NC Gibsonville NC at 9:00 pm
  • Destination: BUY Burlington NC
  • Flight plan: none
  • Runway 24, 5,000 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 130° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 72°F (22°C), dew point 61°F (16°C)
  • Altimeter: 30.12 inHg
  • Observation at 9:53 pm from BUY

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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.