Probable cause
The pilot’s delayed decision to abort the takeoff.
NTSB analysis
According to the pilot, he performed a run-up and proceeded to the departure end of the runway. He applied full power and began the takeoff roll. With the airplane about halfway down the runway, the pilot realized that the airplane was not developing as much airspeed as he expected. As the airplane approached the end of the runway, he decided to abort the takeoff. He pulled back the throttle and applied the brakes but the airplane did not slow down quickly enough. The airplane ran off the end of the runway, traveled down an embankment, and came to rest in a marshy area, substantially damaging the forward section of the fuselage. The pilot noted that he had forgotten to set the flaps properly for takeoff. During a postaccident examination of the wreckage, a Federal Aviation Administration inspector found no preexisting mechanical anomalies with the airplane.
Text from the NTSB. Open the NTSB docket for ERA10CA388 for the full record.
Event
- Date
- Aug 1, 2010
- Type
- Accident
- Place
- Middleberry, Vermont
- Nearest airport
- Middlebury State Airport (6B0)
- Highest injury
- Minor
- Minor injuries
- 2
- Weather
- Visual (VMC)
- Light
- Day
Cessna 177B
- N-number
- N34641
- Category
- Airplane
- Damage
- Substantial
- Operating rule
- Part 91 (general aviation)
- Purpose of flight
- Personal
From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.