NTSB CAROL · Event
Event ERA15LA192
Aircraft involved
Probable cause & findings
The pilot's improper decision to land the airplane with a quartering, gusting tailwind and his subsequent failure to flare the airplane and maintain directional control after it bounced, which resulted in a runway excursion.
Factual narrative
On April 19, 2015, about 1455 eastern daylight time, a Cirrus Design Corp. SR22, N88AX, was substantially damaged when it impacted a parked airplane, a house, and trees during the landing at Pine Shadows Airpark (94FL), Fort Myers, Florida. The private pilot and three passengers were not injured. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight, which was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. The flight originated at Key West International Airport (EWY), Key West, Florida.According to the pilot, he listened to the weather information at Page Field Airport (FMY), Fort Myers, Florida, which was about 9 miles to the south of the accident location and elected to land on runway 09, a 3,200-foot-long, 50-foot-wide asphalt runway. He made visual contact with the runway about 1 mile from the airport. During the final approach leg of the traffic pattern, the airplane had a "steeper angle descent" to the runway when a crosswind "push[ed]" the airplane to the left. In addition, during the landing he did not flare the airplane, which resulted in a "bounce." The pilot added full throttle in an attempt to perform a go-around maneuver, but the airplane was off the runway "sliding towards [a] road and hangar." Then the pilot retarded the engine throttle, attempted to "straighten" out the landing roll, however, the airplane struck a tree, a parked airplane, a house, became airborne again, struck more trees, and finally came to rest upright near a house. All four occupants egressed without injury. The 1453 automated weather observation at FMY, included winds from 210 degrees at 13 knots, gusting to 20 knots, visibility 10 miles, clear skies, temperature 29 degrees C, dew point 22 degrees C, and an altimeter setting of 29.91 inches of mercury. According to the Federal Aviation Administration inspector that responded to the accident location, the airplane came to rest approximately 2,500 feet from the initial touch down point. The fuselage and wings were substantially damaged in the accident sequence. In addition, the empennage was separated from the fuselage. The pilot reported in the NTSB Pilot/Operator Aircraft Accident/Incident Report, Form 6120.1, that there were no mechanical malfunctions with the airplane that would have precluded normal operation. In addition, under the Operator/Owner Safety Recommendation section of the form, he stated that he would "fly over the field, evaluate wind sock, and longer approach flight pattern." The pilot stated that he checked the weather at a local airport and subsequently chose to land on a runway at his destination airport with a quartering tailwind and gusts to 20 knots. While the pilot was performing a steep approach to the runway, a crosswind "push[ed]" the airplane to the left. Further, the pilot did not flare the airplane, and, during the landing, the airplane touched down on the runway and bounced. The pilot added full throttle in an attempt to perform a go-around, but the airplane slid off the runway. He then retarded the engine throttle and attempted to "straighten" out the landing roll; however, the airplane struck a tree, became airborne again, struck more trees, and finally came to rest upright near a house. The pilot reported that there were no mechanical malfunctions with the airplane that would have precluded normal operation. In addition, he stated that the accident could have been prevented if he had flown over the field, evaluated the wind sock, and conducted a longer approach flight pattern. 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
- C Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot - C
- C Environmental issues-Conditions/weather/phenomena-Wind-Tailwind-Effect on operation - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
- C Environmental issues-Conditions/weather/phenomena-Wind-Gusts-Effect on operation - C
- — Environmental issues-Physical environment-Object/animal/substance-Tree(s)-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2015_ERA15LA192.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, 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.
- 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.
- 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.
Browse the full corpus — academia portal ↗