FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10LA004 · Piper PA-32R-300

3 Oct 2009 · Whiteville, NC, United States

Carolinas Aviation Piper PA-32R-300 · Accident: hard landing

From Columbus County Municipal Airport (CPC) to Columbus County Municipal Airport (CPC)

Report a problem

Event

NTSB case
ERA10LA004
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-32R-300

Aircraft type
Piper PA-32
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N8809C
Onboard fatalities
Unknown
Route
From Columbus County Municipal Airport (CPC), Whiteville, NCTo Columbus County Municipal Airport (CPC), Whiteville, NC
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Hard landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10LA004
Event ID
20091003X14427
Case number
ERA10LA004
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 9f4738f6307969a75febfb47a9ad74e0f101fa7af6ca23f76d95f0a6cfd634ef; retrieved 2026-09-15T13:22:24.066Z.