# NTSB ERA17FA210: Piper PA28, N199PA, Fort Myers, FL, June 24, 2017 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: June 24, 2017, 07:48 local (11:48 UTC) - Place: Fort Myers, FL - Coordinates: 26.578611, -81.852775 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=26.5786&lon=-81.8528&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: Fatal - Injuries: 1 fatal, 1 serious - Status: Completed, report May 9, 2018 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: Lycoming, FAA, Piper Aircraft Co. - NTSB case key (mKey): 95425 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA17FA210 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/95425/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=95425 - Page: https://openairdocs.org/ntsb/ERA17FA210 ## Probable cause 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Piper PA-28-181, 8 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7102807), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Piper PA-28-181, 26 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7102807), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Initial climb: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-28-181, 70 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102807), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## 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 toFederal 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. ## Aircraft - Registration: [N199PA](https://openairdocs.org/deregistered/N199PA-2017-08-14), registration cancelled 2017-08-14, S/N 2843218, built 1999 (OpenAirDocs) - Reported make and model: PIPER PA28 (181) - Registry model: [Piper PA-28-181](https://openairdocs.org/model/piper-pa-28-181) (registry code 7102807) (OpenAirDocs) - Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 2843218 - Year built: 1999 - Airframe hours: 1847.1 - Engines: LYCOMING O&VO-360 SER 180 horsepower reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, June 20, 2017, 5 hours before - Departed: FMY, Fort Myers, FL - Destination: X35, DUNNELLON, FL - Flight plan: IFR - Airport: FMY, Page Field, runway 13, 4,912 × 150 ft, asphalt - Equipment: Stall warning system, Auto-pilot, Electronic flight bag or handheld device ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 55; injuries: serious; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 555 total, 158 in this make and model, 509 as pilot in command, 32 in the last 90 days, 3 in the last 30 days, 0 in the last 24 hours - Pilot-rated passenger; age 37; injuries: fatal; private; airplane ratings: single-engine land; medical: class 3, unknown; seat: right; restraint: 3-point; toxicology performed; flight hours: 115 total, 9,999 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 100° at 4 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 79 °F - Altimeter: 30.04 inHg - Observed at: FMY, 1 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20170624011419A](https://openairdocs.org/incident/20170624011419A), Jun 24, 2017: Piper PA-28-181, Fort Myers, FL, Substantial damage, 1 fatal. On June 24, 2017, at approximately 0748 EDT, N199PA, a Piper PA28-18, took off from page field (fmy) in ft. Myers, Florida. The aircraft, for undetermined… ## Docket (9 files) The files NTSB released with the investigation on April 30, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=95425. 20.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 491 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462754&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Memorandum for Record - Interview, Pilot (item 2, .PDF, 236 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462755&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20-%20Interview,%20Pilot-Master.PDF - Interview Summaries (item 3, .PDF, 234 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462756&FileExtension=.PDF&FileName=Interview%20Summaries-Master.PDF - Video File (item 4, MP4, 2.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462757&FileExtension=mp4&FileName=Video%20File-Master - Maintenance Records (item 5, .PDF, 11.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462758&FileExtension=.PDF&FileName=Maintenance%20Records-Master.PDF - Investigative Photos (item 6, .PDF, 4 photos, 1.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462759&FileExtension=.PDF&FileName=Investigative%20Photos-Master.PDF - Toxicological Report (item 7, .PDF, 303 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462760&FileExtension=.PDF&FileName=Toxicological%20Report-Master.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 8, .PDF, 771 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462761&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Master.PDF - Statement of Party Representatives to NTSB Investigation (item 9, .PDF, 2.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462762&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.