NTSB CAROL · Event
Event ERA17FA210
Aircraft involved
Probable cause & findings
A partial loss of engine power during initial climb for reasons that could not be determined because extensive fire damage precluded thorough examination of the engine and its associated systems.
Factual narrative
HISTORY OF FLIGHT
On June 24, 2017, about 0748 eastern daylight time, a Piper PA28-181, N199PA, impacted a building and terrain during a forced landing shortly after takeoff from Page Field Airport (FMY), Fort Myers, Florida. The private pilot sustained serious injuries and the pilot-rated passenger was fatally injured; the airplane was destroyed by a postimpact fire. The airplane was operated by Fort Myers Flying Club in accordance with the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and an instrument flight rules flight plan was filed for the personal flight, which was destined for Marion County Airport, Dunnellon, Florida. The pilot stated that he conducted a normal preflight inspection of the airplane and observed no anomalies. He sampled fuel from both of the fuel tanks twice and found no water or debris. The engine start was normal with all instruments in the normal operating range, and he observed similar indications during the engine run-up. After starting the takeoff roll, he verified the engine power output, which was 2,450 rpm. The airplane lifted off the runway at 65 knots, and the pilot pitched the airplane to 5° nose up, with a goal of 80 knots airspeed. At 75 knots, he felt a loss of engine power and the indicated engine rpm started to decrease. He switched fuel tanks and applied carburetor heat, but the engine continued to lose power. The pilot decided to make a forced landing on a nearby road. He turned right to line up with the road, but the wing contacted a tree and the airplane collided with the side of a building before impacting the ground. A member of the flying club reported that he had experienced a loss of engine power in the accident airplane about 1 month before the accident when he was going to make a short flight to Orlando. During the initial climb after takeoff, about 100 ft above ground level, the engine experienced a partial loss of power. The pilot quickly reduced engine power further and landed straight-ahead on the remaining runway. The pilot taxied the airplane to a local maintenance facility, where maintenance personnel flushed the right and left fuel tanks, installed new fuel cap seals, drained the carburetor fuel bowl, cleaned and inspected the fuel filter, and flushed the fuel lines. They conducted a test run of the engine and found no anomalies. About 1 week later, another pilot was flying the accident airplane in cruise flight at 8,000 ft when the engine experienced a total loss of power. The pilot was maneuvering the airplane to land at a local airport when, at 3,000 ft, the engine regained power. The pilot decided to make a precautionary landing at the closest airport and have a local maintenance inspect the airplane. The maintenance facility took fuel samples and stated they were blue and clear of debris. The intake tube was unobstructed, and the engine performed satisfactorily during ground test runs.
PERSONNEL INFORMATION
According to Federal Aviation Administration (FAA) records, the pilot held a private pilot certificate with ratings for airplane single-engine land and instrument airplane. He held an FAA third-class medical certificate issued January 5, 2017. At the time of the medical examination, the pilot reported 523 total hours of flight experience. The pilot reported a total flight experience of 535 hours at the time of the accident, of which 155 hours were in the accident airplane make and model. The pilot had flown 13 and 2.7 hours during the 90-day and 30-day periods preceding the accident, respectively.
AIRCRAFT INFORMATION
The four-seat, low-wing airplane was manufactured in 1999. It was powered by a Lycoming O-360-A4M, 180-horsepower engine, equipped with a two-blade Sensenich propeller. According to the airplane logbook, the last annual inspection was performed on June 20, 2017. At that time, the airplane had accumulated a total time of 1,847.1 hours on both the airframe and engine.
METEOROLOGICAL INFORMATION
The 0753 recorded weather at FMY included wind from 100° at 4 knots, visibility 10 statute miles, and a clear sky.
WRECKAGE AND IMPACT INFROMATION
The airplane came to rest against a building across the street from the airport. The airframe was examined at the accident site, and all major components were accounted for at the scene. The engine compartment, cockpit, cabin area, empennage and the majority of both wings were consumed by post-crash fire. Flight control cable continuity was confirmed from the cockpit area to the flight control surfaces. The two-blade propeller fractured off the engine and was located in the ceiling of the building. One blade exhibited "S" bending; the other blade was fractured in several pieces. The starter ring gear, starter ring gear support, cowling, and windshield pieces were located inside the building. The engine was moved to a hangar at FMY for further examination. The rear-mounted engine accessories were damaged in the postcrash fire. The engine initially could not be rotated by hand due to impact damage to the No. 2 cylinder. The cylinders were removed, and the crankshaft was rotated by hand. Continuity of the crankshaft to the rear accessory gears and to the camshaft was confirmed. Continuity to the valvetrain was confirmed by visual examination. The interiors of the cylinders exhibited no anomalies. The magnetos and carburetor were fire damaged and could not be inspected.
MEDICAL AND PATHOLOGICAL INFORMATION
An autopsy was performed on the pilot-rated passenger by the Office of the Medical Examiner, Fort Myers, Florida. The report listed the cause of death as blunt force trauma. Forensic toxicology was performed on specimens from the pilot-rated passenger by the FAA Bioaeronautical Sciences Research Laboratory, Oklahoma City, Oklahoma. The results were negative for drugs and carbon monoxide. The private pilot and passenger were departing on a cross-country flight. Shortly after takeoff, the engine experienced a partial loss of power and the airplane would not climb. The pilot chose to perform a forced landing to a road, during which the airplane impacted a building, then the ground; a postimpact fire ensued. The airplane was operated by a flying club. On two separate occasions before the accident, two different pilots experienced a loss of engine power in the accident airplane. About 1 month before the accident, a pilot experienced a partial loss of engine power shortly after takeoff; he subsequently landed the airplane on the remaining runway. Following that incident, a maintenance inspection revealed no anomalies. Maintenance personnel flushed both right and left fuel tanks, installed new fuel cap seals, drained the carburetor fuel bowl, cleaned and inspected the fuel filter, and flushed the fuel lines. A subsequent test run of the engine revealed no anomalies. Another pilot reported that, about 2 weeks before the accident, while in cruise flight at 8,000 ft, the engine experienced a total loss of power. The pilot was able to restart the engine at an altitude of 3,000 ft and uneventfully performed a precautionary landing. A subsequent maintenance inspection did not reveal any anomalies. Postaccident examination of the engine did not reveal any preimpact mechanical malfunctions. Continuity of the crankshaft and camshaft were observed during manual rotation of the engine and the interiors of each cylinder revealed no anomalies. However, postimpact fire damage precluded a thorough examination of the ignition, fuel, and induction systems, and the reason for the partial loss of engine power could not be determined based on the available information. 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 Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
Verbatim from NTSB's published report. Source file
NTSB_2017_ERA17FA210.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 (stall, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- 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 …
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗