Piper PA-28-236 accident near Chester, Connecticut, July 10, 2012
On July 10, 2012 at about 2:57 pm local time, a Piper PA-28-236, registered N777AF, was substantially damaged in an accident during landing (landing roll) near Chester, Connecticut (Chester 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 failure to execute a go-around following an approach that was high and fast, which resulted in a runway overrun.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 10, 2012 · about 2:57 pm local time
- Place
- Chester, Connecticut · Chester Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-236 · all PA-28-236s on the register
- Registration
- N777AF · no longer on the register · serial 28-7911328
- 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 he made two unsuccessful attempts to land. On his third approach, although the airplane was high and fast, he continued the landing. He landed long, and the airplane overran the runway and struck a fence. During the accident sequence, the airplane's nose landing gear collapsed, resulting in substantial damage to the firewall and fuselage. Examination of the wreckage did not reveal any preimpact mechanical malfunctions, and the pilot did not report any preaccident 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
- Runway excursion during landing (landing roll) defining event
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 1,013 hours in all; 1,013 in this make and model
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Maximum gross weight: 2,150 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming 0-540 SERIES (piston); 0 hours total
- Operator: Learning Unlimited INC
The flight
- Departed from: FOK West Hampton Be NY at 2:20 pm
- Destination: SNC Chester CT
- Flight plan: none
- Runway 35, 2,566 ft by 50 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 81°F (27°C), dew point 59°F (15°C)
- Altimeter: 30.19 inHg
- Observation at 2:55 pm from SNC
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.