ERA24LA229
2024-05-26 · Salisbury, Maryland, United States · Serious · 1 aircraft · Status: Completed
Airport 1N5
Current FAA registration · N818K
- Make / Model
- GREAT LAKES 2T-1(MENASCO SPECIAL
- Year of manufacture
- 1929 · 95 years old at event
- Engine
- MENASCO PIRATE C4 D4 (125 hp)
- Seats / Engines
- 2 seats · 1 engine
- Last airworthiness date
- 19651203
- ADS-B equipped
- Yes — Mode-S AB27F5
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s exceedance of the airplane’s critical angle of attack, resulting in an aerodynamic stall and loss of control.
Factual narrative
On May 26, 2024, at 1200 eastern daylight time, a Great Lakes 2T-1 (Menasco Special), N818K, was substantially damaged when it was involved in an accident near Salisbury, Maryland. The pilot and pilot-rated passenger were seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The airplane was an open-cockpit, 2-place, tandem-seat vintage biplane equipped with a 125 -horsepower reciprocating engine. The pilot had a total of 14,135 hours of flight experience, of which 30 hours were in the accident airplane make and model. The pilot flew the airplane from the rear seat and the pilot-rated passenger was in the front seat. The airplane departed from Bennett Airport (1N5), Salisbury, Maryland, just before 1200. According to the pilot-rated passenger, this was the second flight of the day for the pilot and airplane. The pilot had completed a flight previously with another passenger that was uneventful. The passenger stated that she remembered taxiing out to runway 35 for departure, and normal engine operation to that point. She stated that during the flight the airplane felt “slow and mushy,” but thought that this feeling may have been because she was unfamiliar with the airplane. She stated that she was not flying the airplane when the accident occurred and could not recall any other details from the accident flight. The passenger from the previous flight watched the airplane depart on runway 35 for the accident flight and make a right turn. Shortly after the right turn, he watched the airplane make a 180° turn back toward the airport. The airplane was descending and went behind trees where he lost sight of it. He then reported hearing a “thud” and saw a puff of dust in the distance. He could not remember hearing the engine due to his distance from the accident site. The witness also recorded a video of the takeoff that concluded shortly after the airplane’s initial turn to the right. Strong engine noise could be heard for the duration of the video. The pilot stated that he could not remember the accident, but did recall some of the details from earlier that day. Before the first flight of the day, the pilot and both passengers completed a preflight inspection of the airplane that included adding 5 gallons of fuel to the single fuel tank. The pilot recalled that the airplane was holding about 20 gallons total of 100LL fuel and that he had filled the fuel tank from a gasoline canister that he kept in his hangar. The pilot also commented that the airplane had three gallons of oil in it. The pilot was asked if the passenger flew the airplane on the first flight of the day and the pilot stated that they may have but he was unsure. The pilot was unable to recall if the passenger on the accident flight was intending to fly the airplane. The airplane came to rest in a grassy open field about ½-mile northeast of 1N5, and the wreckage displayed damage signatures that were consistent with a left wing- and nose-low attitude at impact. The empennage was mostly undamaged. Postaccident examination of the airplane confirmed control cable continuity from the flight controls in the cockpit to each flight control surface. Examination of the engine did not reveal evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. The pilot and pilot-rated passenger departed the runway in the vintage biplane for a local flight. The pilot and passenger each had limited recollections of the accident flight, but the passenger remembered that, during the flight, the airplane felt “slow and mushy.” A witness on the ground recorded a video of the airplane’s takeoff and initial turn to the right, and strong engine noise could be heard throughout the video. The witness described that, shortly after he stopped recording, the airplane completed an approximate 180° turn back toward the airport. He then saw the airplane descend out of sight behind trees before he heard a “thud” and saw a puff of dust. The airplane came to rest in a grassy open field and exhibited damaged signatures consistent with a relatively low-energy, left-wing- and nose-low impact attitude. A postaccident examination of the airframe and engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Given the findings of the postaccident examination, including the impact signatures observed on the wreckage as well as the passenger’s description that the airplane felt “slow and mushy,” it is most likely that the pilot exceeded the airplane’s critical angle of attack while maneuvering, which resulted in an aerodynamic stall, loss of control, and subsequent impact with terrain. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Not attained/maintained
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2024_ERA24LA229.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (stall, loss of control). All research papers
- Semantic Scholar 2016 · Article (Interacción) Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- NASA NTRS 2026 · Conference Paper Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER) A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- Semantic Scholar 2024 · Article (International Conference on Networking and Services) Risk Assessment of Loss of Control In-Flight Trajectories for Urban Air Mobility Safety
In Urban Air Mobility (UAM), maintaining a minimum separation between aircraft is a safety requirement, which becomes challenging amidst congested air traffic and off-nominal conditions, such as Loss …