Piper PA34 accident near Northampton, Massachusetts, September 23, 2010
On September 23, 2010 at about 6:30 pm local time, a Piper PA34, registered N56196, was substantially damaged in an accident during landing (flare/touchdown) near Northampton, Massachusetts (Northampton 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 recovery from a bounced landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 23, 2010 · about 6:30 pm local time
- Place
- Northampton, Massachusetts · Northampton Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA34 200 · all PA34s on the register
- Registration
- N56196 · no longer on the register · serial 34-7350301
- 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 it was his first landing at the accident airport. While in the traffic pattern and on the approach for landing, he stated that he became preoccupied with the terrain surrounding the airport and landed at a higher than normal airspeed. Upon touchdown, the airplane bounced. On the second touchdown, the airplane's nose landing gear contacted the runway, the airplane shifted to the right, and the left propeller impacted the runway. Postaccident examination revealed substantial damage to both wings, and no preimpact mechanical malfunctions or anomalies with the airplane were identified.
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
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine sea; instrument: airplane
- Flight time: 499 hours in all; 76 in this make and model; 4 in the last 90 days; 418 as pilot in command
- Last flight review: July 5, 2010
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 6,678 hours
- Maximum gross weight: 4,200 lb
- Seats: 6
- Landing gear: fixed
- Engine 1: Lycoming IO-360 (piston); 0 hours total
- Engine 2: Lycoming IO-360 (piston); 0 hours total
- Operator: Louis Fly Academy Ltd
The flight
- Departed from: EEN Keene NH at 5:45 pm
- Destination: FRG Farmingdale NY
- Flight plan: none
- Runway 32, 3,365 ft by 50 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 79°F (26°C), dew point 52°F (11°C)
- Altimeter: 30.17 inHg
- Observation at 6:55 pm from CEF, 9 miles away
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.
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.