Piper PA-32R-300 accident near Whiteville, North Carolina, October 3, 2009
On October 3, 2009 at about 11:30 pm local time, a Piper PA-32R-300, registered N8809C, was substantially damaged in an accident during landing (flare/touchdown) near Whiteville, North Carolina (Columbus County Municipal 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 improper flare and subsequent hard landing during an intentional gear-up landing following multiple mechanical malfunctions. Also causal to the accident was an inoperative landing gear emergency-down valve which had blockage for undetermined reasons.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 3, 2009 · about 11:30 pm local time
- Place
- Whiteville, North Carolina · Columbus County Municipal · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-32R-300 · all PA-32R-300s on the register
- Registration
- N8809C · no longer on the register · serial 32R-7680139
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported a complete loss of electrical power and that he was unable to lower the landing gear as a result. Several attempts to lower the landing gear using the emergency procedures published in the Pilot’s Operating Handbook were also unsuccessful. A mechanic and the pilot reviewed the procedure by cellular telephone as the airplane circled over the airport, but the landing gear would not deploy. After an estimated 90 minutes of maneuvering and troubleshooting, the pilot announced that he would land the airplane with the gear up. According to the mechanic, the airplane was at low altitude over the approach end of the runway when the pilot “chopped the power.” He said, “He chopped the power too high, and didn’t have enough ‘flare speed’ and hit the runway pretty hard.” Examination of the airplane at the scene revealed substantial damage to the firewall, fuselage, and empennage structures. Detailed examination of the airplane by the mechanic and Federal Aviation Administration inspectors revealed that the air conditioning compressor had seized, the compressor belt had broken, which then fouled the alternator belt. Once the alternator belt broke, the battery power was exhausted, and the airplane experienced a complete electrical failure. Examination of the landing gear revealed that with electrical power applied, the landing gear would operate as designed. With electrical power removed, the “emergency down valve” which allowed the gear to free-fall into position, would not release the hydraulic pressure to allow the gear to lower. Instead, the pressure was released by opening a hydraulic line, and the gear then lowered as designed. The emergency down valve was found with blockage. The aircraft manufacturer calls for the landing gear system to be tested each 100 flight hours. The last inspection was performed 10.5 months and 20 flight hours before the accident.
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
- Electrical system malf/failure during enroute (cruise)
- Sys/Comp malf/fail (non-power) during approach
- Landing gear not configured during landing (flare/touchdown)
- Hard landing during landing (flare/touchdown) defining event
The NTSB's findings
- cause Aircraft › Aircraft systems › Landing gear system › Gear extension and retract sys › Inoperative
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 320 hours in all; 88 in this make and model
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,902 hours
- Last inspection: annual inspection, November 20, 2008; 20 hours since
- Maximum gross weight: 3,600 lb
- Seats: 7
- Landing gear: retractable
- Engine: Lycoming TI0-540 SER (piston); 0 hours total
- Operator: Carolinas Aviation LLC
The flight
- Departed from: CPC Whiteville NC at 9:30 pm
- Destination: CPC Whiteville NC
- Flight plan: not recorded
- Runway 24, 5,500 ft by 75 ft
Weather at the time
- Light: night, bright
- Wind: from 190° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 66°F (19°C)
- Altimeter: 29.87 inHg
- Observation at 11:34 pm from CPC
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 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.
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.