Luscombe 8E accident near Selinsgrove, Pennsylvania, June 9, 2012
On June 9, 2012 at about 3:30 pm local time, a Luscombe 8E, registered N2052K, was substantially damaged in an accident during takeoff near Selinsgrove, Pennsylvania (Penn Valley 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 failure to maintain airplane control during the takeoff.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 9, 2012 · about 3:30 pm local time
- Place
- Selinsgrove, Pennsylvania · Penn Valley · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Luscombe 8E · all 8Es on the register
- Registration
- N2052K · registry record · serial 4779
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that the airplane suddenly veered to the left during the takeoff roll and that he was unable to stop the airplane before it departed the left side of the runway. A witness at the airport observed the airplane airborne over the grass area between the runway and taxiway, and the right wing struck the ground. The airplane then bounced on the right and left main landing gears before coming to rest on the grass. The airplane's right wing was substantially damaged. Postaccident examination of the airplane did not reveal any preimpact mechanical malfunctions or failures 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
- Loss of control in flight during takeoff defining event
- Runway excursion during takeoff
- Collision with terrain or object (not controlled flight into terrain) during takeoff
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 353 hours in all; 139 in this make and model; 30 in the last 90 days; 7 in the last 30 days; 201 as pilot in command
- Last flight review: May 30, 2012
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,823 hours
- Last inspection: annual inspection, October 14, 2011
- Maximum gross weight: 1,400 lb
- Seats: 2
- Landing gear: fixed
- Engine: Cont Motor C85 SERIES (piston); 0 hours total
The flight
- Departed from: SEG Selinsgrove PA at 3:30 pm
- Destination: SEG Selinsgrove PA
- Flight plan: none
- Runway 17, 4,760 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 230° at 5 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 120,000 ft
- Temperature: 81°F (27°C), dew point 57°F (14°C)
- Altimeter: 29.95 inHg
- Observation at 3:53 pm from SEG
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.