# NTSB ERA17LA097: Piper PA22, N3659Z, Georgetown, DE, January 28, 2017 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: January 28, 2017, 14:00 local (19:00 UTC) - Place: Georgetown, DE - Coordinates: 38.6875, -75.359169 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.6875&lon=-75.3592&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Fire/smoke (non-impact)](https://openairdocs.org/ntsb-events/150) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report March 18, 2019 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 94660 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA17LA097 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94660/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94660 - Page: https://openairdocs.org/ntsb/ERA17LA097 ## Probable cause An in-flight fire for reasons that could not be determined due to extensive thermal damage to the airplane. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Fuel system](https://openairdocs.org/ntsb-findings/01022800): Aircraft › Aircraft systems · Not specified (probable cause); cases with it: [Piper PA-22-150, 1 case](https://openairdocs.org/ntsb-findings/01022800/cases.md?model=7102210), [All aircraft, 181 cases](https://openairdocs.org/ntsb-findings/01022800/cases.md) - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Piper PA-22-150, 11 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7102210), [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: Fire/smoke (non-impact)](https://openairdocs.org/ntsb-events/150) (defining event); cases with it: [Piper PA-22-150, 1 case](https://openairdocs.org/ntsb-events/150/sequence.md?model=7102210), [All aircraft, 504 cases](https://openairdocs.org/ntsb-events/150/sequence.md) - [Emergency descent: Fire/smoke (non-impact)](https://openairdocs.org/ntsb-events/150); cases with it: [Piper PA-22-150, 1 case](https://openairdocs.org/ntsb-events/150/sequence.md?model=7102210), [All aircraft, 504 cases](https://openairdocs.org/ntsb-events/150/sequence.md) - [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-22-150, 19 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102210), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis According to the private pilot, shortly after takeoff, as the airplane reached 1,400 ft, he noticed "thick" smoke coming from behind the instrument panel and then the glareshield, followed by flames near his feet and legs. The pilot was able to return to the departure airport and land successfully. During the subsequent landing roll, the pilot reduced the throttle and mixture to shut down the engine and pulled the brake handle; however, the airplane did not slow, and he egressed the airplane while it was in motion. The airplane came to rest in a grass area right of the runway and was mostly consumed by fire. The pilot's description of the onset and growth of the fire was consistent with a fast-growing fire such as a fire fed by liquid fuel. Examination of the wreckage revealed that several sections of the fuel system were consumed or damaged by fire. The main fuel line from the fuel strainer to the carburetor was found loose on the carburetor side. The lower left portion of the engine cowling exhibited more thermal damage than the right side, which is consistent with the location of the loose fuel line supplying the carburetor; however, due to the extent of the thermal damage, the origination point of the in-flight fire could not be determined. ## Factual narrative On January 28, 2017, about 1400 eastern standard time, a Piper PA-22-150, N3659Z, was destroyed after it experienced an in-flight fire following takeoff from Delaware Coastal Airport (GED), Georgetown, Delaware. The private pilot sustained minor injuries. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight that was operated under the provisions of Title 14 Code of Federal Regulations Part 91.According to the pilot, prior to departing GED, he checked the engine oil level, performed a visual inspection of the engine compartment and an engine run-up with no anomalies noted. After departing runway 28, the airplane reached 1,400 feet, and the pilot noticed "thick" smoke coming from behind the instrument panel and then the glareshield. The pilot attempted to return to GED and opened the vent on the left door to evacuate smoke and allow him to search for a runway to land. He then noted flames by his feet and legs, and while "sideslipping" the airplane, burning portions of the roof lining began to fall on him. The airplane continued to descend, and during the subsequent landing roll, the pilot reduced the throttle and mixture to shut down the engine. He pulled on the brake handle; however, the airplane did not slow. The pilot proceeded to egress while the airplane was in motion. The airplane came to rest in a grass area off the right side of runway 4. Initial examination of the airplane revealed that the fuselage, empennage, and right wing were consumed by fire. The left wing was partially consumed by fire. The engine remained attached to the fuselage and the propeller remained attached to the engine. According to Federal Aviation Administration records, the airplane was manufactured in 1960 and registered to the pilot on June 13, 1990. It was equipped with a Lycoming O-320-A2B, a 150-horepower engine. According to the maintenance logbooks, the airplane's most recent annual inspection was performed on January 1, 2017, at a total time of 3,740.5 hours, about 2 operational hours prior to the accident. According to the Piper PA-22 Owner's Manual, the airplane was equipped with two 18-gallon fuel tanks located in the wings, which drained individually according to the position of the fuel selector valve on the left forward cabin wall. "The main fuel strainer, through which all fuel going to the carburetor flows, is located on the lower left engine side of the firewall…The engine primer pump on the right side of the instrument panel takes fuel from the main gascolator and pumps it directly to all four cylinders of the engine." According to an NTSB fire protection engineer who examined the wreckage, the pilot's description of the fire in the accident sequence was consistent with a liquid fuel-fed fire. Several sections of the airplane fuel system were consumed by fire. The fuel selector valve was thermally damaged and its function could not be verified. The output fuel line from the fuel selector to the firewall wasconsumed by fire. The input fuel line from the right-side wing tank was also consumed by fire. The engine primer pump was not located with the wreckage. The primer pump fuel lines were consumed by fire inside the cockpit. Several small sections of copper primer pump fuel lines were located on the firewall with melted ends. The fuel primer lines in the engine compartment remained intact and did not appear to leak. The main fuel line from the fuel strainer to the carburetor, which was located on the left side of the engine compartment, was found loose on the carburetor side. The lower left portion of the engine cowling exhibited more thermal damage than the right side. ## Aircraft - Registration: [N3659Z](https://openairdocs.org/deregistered/N3659Z-2017-10-03), registration cancelled 2017-10-03, S/N 22-7556, built 1960 (OpenAirDocs) - Reported make and model: PIPER PA22 (150) - Registry model: [Piper PA-22-150](https://openairdocs.org/model/piper-pa-22-150) (registry code 7102210) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 22-7556 - Year built: 1960 - Airframe hours: 3742.4 - Engines: LYCOMING O-320-A2B 150 horsepower reciprocating - Damage: Destroyed - Fire: Both - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 1, 2017, 2 hours before - Departed: GED, GEORGETOWN, DE - Destination: MD50, LUSBY, MD - Airport: GED, Delaware Coastal, runway 28, 3,109 × 75 ft, asphalt - Equipment: Onboard weather, Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 59; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review September 6, 2015; seat: left; restraint: 4-point; flight hours: 1,082 total, 870 in this make and model, 1,037 as pilot in command, 6 in the last 90 days, 2 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 240° at 14 knots, gusting 21 - Visibility: 10 statute miles - Lowest ceiling: 5,500 ft overcast - Temperature: 45 °F, dew point 21 °F - Altimeter: 29.77 inHg - Observed at: SBY, 22 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 20170128001289A](https://openairdocs.org/incident/20170128001289A), Jan 28, 2017: Piper PA-22-150, Georgetown, DE, Destroyed. Pilot took off using runway 28 from Delaware Coastal Airport (kged), as he climbed and reached 1400 feet, he noticed smoke coming from behind the instrument… ## Docket (6 files) The files NTSB released with the investigation on November 7, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94660. 7.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40468072&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Pilot Interview Summary (item 2, .PDF, 392 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40468073&FileExtension=.PDF&FileName=Pilot%20Interview%20Summary-Master.PDF - Maintenance Log Excerpts (item 3, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40468074&FileExtension=.PDF&FileName=Maintenance%20Log%20Excerpts-Master.PDF - Weather Observations (item 4, .PDF, 141 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40468075&FileExtension=.PDF&FileName=Weather%20Observations-Master.PDF - Materials Lab Report 17-058 Fire Investigation (item 5, .PDF, 7 photos, 716 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40468076&FileExtension=.PDF&FileName=Materials%20Lab%20Report%2017-058%20Fire%20Investigation-Master.PDF - Photos (item 6, .PDF, 4 photos, 632 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40468077&FileExtension=.PDF&FileName=Photos-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.