Skip to content

Atlas / NTSB / ERA12CA377

NTSB CAROL · Event

Event ERA12CA377

2012-05-31 Lawrence, Massachusetts, United States Airport · LWN None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot's delayed decision to abort the takeoff, which resulted in a runway excursion.

Factual narrative

After flying for about 40 minutes without incident, the pilot returned to the departure airport to practice touch-and-go landings and takeoffs. The pilot stated that she landed on the 3,900-foot-long runway, as she normally did for a full-stop landing. She retracted the flaps, adjusted the trim, and advanced the throttle. As the airplane lifted off the ground, she became concerned that it was too far down the runway, and too low above the ground, to clear trees that were located beyond the departure end of the runway. She elected to abort the takeoff, and was not able to stop the airplane on the remaining runway. The airplane departed the end of the runway, rolled through grass, down an embankment, and nosed over. The airplane sustained substantial damage to its empennage. The pilot reported that she did not experience any mechanical malfunctions or failures during the accident. She further stated in retrospect, that she may taken too much time to transition the airplane for takeoff after landing, and also felt that if she had committed to the takeoff, the airplane would have adequately cleared the trees. After flying for about 40 minutes without incident, the pilot returned to the departure airport to practice touch-and-go landings and takeoffs. The pilot stated that she landed on the 3,900-foot-long runway as she normally did for a full-stop landing. She retracted the flaps, adjusted the trim, and advanced the throttle. As the airplane lifted off the ground, the pilot became concerned that it was too far down the runway and too close to the ground to clear trees that were located beyond the departure end of the runway. She elected to abort the takeoff and was not able to stop the airplane on the remaining runway. The airplane departed the end of the runway, rolled through grass, down an embankment, and nosed over. The airplane sustained substantial damage to its empennage. The pilot reported that the airplane did not experience any mechanical malfunctions or failures during the accident. She further stated that she may have taken too much time to transition the airplane for takeoff after landing and also thought that if she had committed to the takeoff, the airplane would have adequately cleared the trees. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • C Personnel issues-Action/decision-Action-Delayed action-Pilot - C
  • Environmental issues-Physical environment-Terrain-Sloped/uneven-Contributed to outcome

Verbatim from NTSB's published report. Source file NTSB_2012_ERA12CA377.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (runway excursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗