Piper PA-12 accident near Sebago Lake, Maine, February 5, 2011
On February 5, 2011 at about 9:00 pm local time, a Piper PA-12, registered N3806M, was substantially damaged in an accident during approach (VFR go-around) near Sebago Lake, Maine. It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilot’s initiation of a right turn with insufficient altitude remaining during an aborted landing resulting in a collision with the landing surface.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 5, 2011 · about 9:00 pm local time
- Place
- Sebago Lake, Maine · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Piper PA-12 · all PA-12s on the register
- Registration
- N3806M · registry record · serial 12-2563
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot, he was attempting to land on a frozen lake, about 200 yards off shore. He encountered severe snow conditions and aborted the landing. He banked the airplane, and the right wing contacted ice and snow on the lake surface. The right wing separated and the airplane crashed on the lake. The pilot reported that the airplane had just been fueled and was operating normally at the time of the accident.
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
- VFR encounter with IMC during landing
- Abnormal runway contact during approach (VFR go-around) defining event
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Lateral/bank control › Incorrect use/operation
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane; instrument: helicopter; rotorcraft: gyroplane; rotorcraft: helicopter
- Flight time: 3,100 hours in all; 100 in this make and model
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: frt
- Injury: serious injuries
The aircraft
- Airframe total time: 4,322 hours
- Last inspection: annual inspection, January 4, 2011
- Maximum gross weight: 1,750 lb
- Seats: 3
- Landing gear: fixed
- Engine: Lycoming O-360-A1D (piston); 0 hours total
The flight
- Departed from: 0B1 Bethel ME at 8:30 pm
- Destination: 0B1 Bethel ME
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 190° at 4 knots
- Visibility: 2 statute miles
- Sky: broken clouds at 1,400 ft
- Temperature: 30°F (-1°C), dew point 25°F (-4°C)
- Altimeter: 29.80 inHg
- Observation at 9:00 pm from PWM, 20 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.