Piper PA-23-250 accident near Summerville, South Carolina, October 21, 2009
On October 21, 2009 at about 10:24 am local time, a Piper PA-23-250, registered N62635, was substantially damaged in an accident during initial climb near Summerville, South Carolina (Summerville Airport). It was a personal flight under general aviation rules (Part 91). 4 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Flight into terrain for undetermined reasons.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 21, 2009 · about 10:24 am local time · cases in 2009
- Place
- Summerville, South Carolina · Summerville Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 4 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-23-250 · all PA-23-250s on the register
- Registration
- N62635 · no longer on the register · serial 27-7654103
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
During an early morning departure, prior to sunrise, the aircraft impacted trees and terrain immediately after takeoff. Witnesses reported the sound of the engines were loud, although they did not observe the airplane take off. A postaccident examination of the airplane and engines revealed no mechanical discrepancies that would have precluded normal operation. The damage to both propeller assemblies was consistent with impact and fire damage. Although the forward baggage door had a gouge mark, it was not consistent with a baggage door coming in contact with a propeller blade in flight. The circumstances of the accident are potentially consistent with an incapacitating event involving this pilot, particularly, given evidence of coronary artery disease during the postmortem examination, or with spatial disorientation given the circumstances of the flight. The pilot was taking off during dark lighting conditions, over a dark unpopulated area. The absence of external visual cues and the accelerations associated with the takeoff and initial climb could have led to erroneous sensations of the airplane’s attitude which, if not effectively managed by the pilot, could explain the circumstances of the accident. There is insufficient evidence, however, to allow a conclusive determination as to which scenario, if either, actually occurred.
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
- Unknown or undetermined during initial climb defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
- Explosion (post-impact) during post (impact)
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
- Personnel issues › Physical › Health/Fitness › Predisposing condition › Pilot
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 4,326 hours in all
- Last flight review: January 29, 2008
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: unk
- Injury: fatal
The aircraft
- Airframe total time: 5,100 hours
- Last inspection: annual inspection, May 1, 2009; 85 hours since
- Maximum gross weight: 5,200 lb
- Seats: 6
- Landing gear: retractable
- Engine 1: Lycoming IO-540-C4B5 (piston); 0 hours total
- Engine 2: Lycoming IO-540 SER (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: DYB Summerville SC at 10:24 am
- Destination: FPR Ft. Pierce FL
- Flight plan: IFR
- Runway 24, 3,700 ft by 75 ft
Weather at the time
- Light: night, dark
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 39°F (4°C), dew point 37°F (3°C)
- Altimeter: 30.26 inHg
- Observation at 10:15 am from DYB
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
24 documents, released by the NTSB on August 19, 2011. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N62635 the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N62635: not on the register today · the record of its deregistration
- Piper PA-23 Apache and Aztec 1,316 registered today · the model family and its accident history
- Piper 44,844 aircraft on the register
- Engine: Lycoming IO-540-C4B5 179 aircraft carry this series today · as the NTSB recorded it
- Engine: Lycoming IO-540 SER 4,222 aircraft carry this series today · as the NTSB recorded it
- Summerville Airport · nearest airport
- Treasure Coast International · bound for
- Accidents and incidents in South Carolina 1,036 since 1982 · 173 in the last ten years
- South Carolina 3,118 aircraft registered
- Other NTSB records under N62635 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/ERA10FA024.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.