NTSB CAROL · Event
Event ERA18LA023
Aircraft involved
Probable cause & findings
The pilot’s failure to maintain directional control during the attempted takeoff, which resulted in a runway excursion.
Factual narrative
On November 2, 2017, about 1400 eastern daylight time, a privately owned and operated Great Lakes Aircraft Company 2T-1A-2, N3512L, experienced a runway excursion during takeoff and nosed over at Turners Falls Airport (0B5), Montague, Massachusetts. The private pilot was not injured and the airplane, which was being operated under the provisions of 14 Code of Federal Regulations Part 91, as a personal flight, was substantially damaged. Visual meteorological conditions prevailed at the time and no flight plan was filed. The flight was originating at the time of the accident and was destined for the Orange Municipal Airport (ORE), Orange, Massachusetts.The pilot stated that he flew to 0B5 the day before the accident and assisted the mechanic with removing panels and bleeding the airplane's brakes as part of an annual inspection. He also reported that the left brake pads were replaced. He returned home that evening, then arrived at 0B5 the afternoon of the accident. After arrival he performed a preflight inspection, which included a visual inspection of the brakes, and rudder cables. He started the engine and began taxiing to the approach end of runway 16, reporting no discrepancies with the brakes while taxiing or during the run-up. He taxied onto the runway and with no wind, began the takeoff roll reporting all was normal for the first 200 ft. With the empennage off the runway, the airplane suddenly veered to the left, which he could not correct. The airplane went off the left side of the runway, down a sharp incline, then nosed over. He immediately released the restraint and exited the airplane. According to a Federal Aviation Administration inspector who examined the runway and airplane the same day, the airplane departed the left side of the runway about 425 from the approach end, and came to rest inverted in grass off the east side of the runway. Inspection of the runway revealed dark marks made by the right tire on runway centerline beginning about 350 feet from the approach edge of the runway. The marks were continuous off the east edge of the runway onto grass. Marks from the left tire were too light to capture in a photograph, while "squiggly" marks associated with the tailwheel tire began about 50 feet past the beginning of the right tire marks and continued off the east edge of the runway onto grass. The inspector reported no flat spots of either main landing gear tire. Visual inspection of the brakes while the airplane was inverted revealed both wheels rotated with no resistance. Both brakes were attached and appeared to be serviceable. The brake lines were also intact with no evidence of fluid loss. The airplane was then uprighted, which further damaged the right main landing gear, fractured the right brake line and right outer wheel half, and sheared a bolt of the brake caliper causing it to separate. Fluid was noted leaking from the right brake line when it fractured, leaving about a one-foot round stain on the pavement. Operational testing of the left brake revealed no evidence of failure or malfunction. The right brake could not be tested because of damage caused by recovery. Flight control continuity was confirmed for roll, pitch, and yaw with no evidence of binding or malfunction reported. The private pilot was initiating takeoff for the positioning flight with no winds and with the airplane's tail off the runway when the airplane suddenly veered left, which he could not correct. The airplane exited the left side of the runway and then slid down a sharp incline into a ditch and nosed over. Postaccident examination of the runway revealed skid marks made by the right main landing gear (MLG) tire that continued off the runway, and by the tailwheel tire, which began 50 ft past the beginning of the right MLG tire marks and also continued off the runway. The left MLG tire only made light tire marks, which indicates that the airplane was light on the left MLG tire during the takeoff. No flat spots were noted on either MLG tire, and examination of both brakes and the flight controls revealed no evidence of a preimpact mechanical malfunctions or failures that would have precluded normal operation. During an operational test, the left brake operated normally. The right brake could not be operationally tested due to damage to its components Given the evidence, it is likely that the pilot lost directional control during the attempted takeoff. 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 Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2017_ERA18LA023.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
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.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NTSB Aircraft Accident Reports 2019 · Accident report
Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- NASA NTRS 2025 · Presentation
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- NASA NTRS 2025 · Conference Paper
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Runway Safety Initiative Final Report (RSI)
Foundation Runway Safety Initiative final report — comprehensive analysis of runway excursion + incursion risk drivers worldwide.
- Semantic Scholar 2020 · Article
Towards online prediction of safety-critical landing metrics in aviation using supervised machine learning
Abstract In recent years, due to the increased availability of data and improvements in computing power, application of machine learning techniques to various aviation safety problems for identifying,…
Browse the full corpus — academia portal ↗