Beech 35-C33 accident near Burlington, North Carolina, August 22, 2012
On August 22, 2012 at about 4:20 pm local time, a Beech 35-C33, registered N331DP, was substantially damaged in an accident during landing (flare/touchdown) near Burlington, North Carolina (Burlington-Alamance Regional 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 pilot's improper landing flare, which resulted in a hard landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 22, 2012 · about 4:20 pm local time
- Place
- Burlington, North Carolina · Burlington-Alamance Regional · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Beech 35-C33 · all 35-C33s on the register
- Registration
- N331DP · registry record · serial CD-954
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot stated that the purpose of the flight was for him to demonstrate to a Federal Aviation Administration inspector, who was on the ground witnessing the flight, his ability to land an airplane. On the first landing, the airplane landed hard, and the right main landing gear tire deflated. The airplane veered off the right side of the runway and came to rest, damaging the right wing spar and fuselage. The pilot reported there was no preimpact mechanical failure or malfunction that caused the hard landing.
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
- Hard landing during landing (flare/touchdown) defining event
- Loss of control on ground during landing (landing roll)
- Runway excursion during landing (landing roll)
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 726 hours in all; 221 in this make and model; 20 in the last 90 days; 4 in the last 30 days; 726 as pilot in command
- Last flight review: November 20, 2011
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 6,250 hours
- Last inspection: annual inspection, September 29, 2011
- Maximum gross weight: 3,300 lb
- Seats: 4
- Landing gear: retractable
- Engine: Cont Motor I0-470-K (piston); 0 hours total
- Operator: Mac Air INC
The flight
- Departed from: BUY Burlington NC at 4:15 pm
- Destination: BUY Burlington NC
- Flight plan: none
- Runway 06, 4,999 ft by 99 ft
Weather at the time
- Light: daylight
- Wind: at 4 knots
- Visibility: 7 statute miles
- Sky: broken clouds at 1,300 ft
- Temperature: 75°F (24°C), dew point 70°F (21°C)
- Altimeter: 30.13 inHg
- Observation at 3:54 pm from BUY
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
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.
Other NTSB records under N331DP the same tail number, which may have belonged to a different aircraft at the time
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.