NTSB CAROL · Event
Event ERA25LA025
Registry · N926MK
FAA Aircraft Registry record.
Make / Model
PIPER PA-28-140
Year of manufacture
1971 · 53 years old at event
Engine
LYCOMING 0-320 SERIES (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19710125
ADS-B equipped
Yes — Mode-S ACD591
Registrant of record
TOOTHMAN JOHN C
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The student pilot’s improper flare, which resulted in a bounced landing and subsequent loss of directional control.
Factual narrative
On October 27, 2024, at 1130 eastern standard time, a Piper PA-28-140, N926MK, was substantially damaged when it was involved in an accident near Fairmont, West Virginia. The student pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. The pilot reported that he departed with light winds and completed a series of maneuvers before successfully landing. During the next takeoff and landing, the pilot attempted a landing but initiated a go-around due to the airplane being high on final approach. On the second landing attempt, the pilot noted that the "winds picked up." During this landing, the airplane bounced, was "pushed" to the left, and despite corrective inputs the airplane veered off the runway, impacted a guardrail, and a postimpact fire ensued. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation. A FAA inspector responded to the accident site, examined the wreckage, and confirmed substantial damage to the airplane’s left wing. The student pilot reported that after a successful first landing, he attempted a second landing but initiated a go-around due to the airplane being high on final approach. On the second attempt, he noted that the wind velocity had increased. During the landing, the airplane bounced and was pushed to the left. Despite corrective inputs, the airplane veered off the runway, impacted a guardrail, and a postimpact fire ensued. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation. 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).
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained
Verbatim from NTSB's published report. Source file
NTSB_2024_ERA25LA025.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 (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗