# NTSB WPR19LA105: Piper PA18, N215T, Copalis, WA, March 30, 2019 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 3 · Limited · Final report - Date: March 30, 2019, 12:56 local (19:56 UTC) - Place: Copalis, WA - Coordinates: 47.069999, -124.11972 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=47.0700&lon=-124.1197&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: FAA - SAIBs cited in the narratives: [SAIB CE-09-35](https://openairdocs.org/saib/CE-09-35) (OpenAirDocs) - NTSB case key (mKey): 99226 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR19LA105 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/99226/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=99226 - Page: https://openairdocs.org/ntsb/WPR19LA105 ## Probable cause An off-airport landing under circumstances that could not be determined based on the available information, which resulted in substantial damage to the airplane. ## 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-18-105 SPECIAL, 2 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7101808), [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. - [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Piper PA-18-105 SPECIAL, 2 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=7101808), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-18-105 SPECIAL, 4 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7101808), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot, who was the owner of the airplane, was conducting a personal cross-country flight to an airport that was a designated section of a sandy ocean beach. Most of the flight was conducted at an altitude of about 2,300 ft, and most of the underlying enroute terrain was inhospitable for landing. The pilot reported that, about 90 minutes into the flight, and 5 minutes after conducting a series of low altitude maneuvers and climbing to about 1,000 ft above the ground, the engine began running roughly and losing power. He said that he activated the carburetor heat, but that did not improve the situation, and he landed the airplane on a logging road in a forest clearing, during which the airplane impacted stumps and debris, resulting in substantial damage. Examination revealed that the airplane was destroyed by fire. There was no evidence of any pre-impact failures or malfunctions. Fire and impact damage prevented determination of the pre-accident condition or functionality of any of the engine components, or of the engine itself. Temperature and dew point values from an airport located about 9.5 miles from the accident site on a graph of carburetor icing potential indicated the potential for serious icing at cruise power. The altitude, speed, and ground track traces of the approach to the logging road, which included level-offs and speed increases, were consistent with a normal traffic pattern flown with an engine developing sufficient power for the entirety of the approach. The fact that both propeller blades were damaged, as well as their damage patterns, also indicated that the engine was developing power. Based on the available information, the circumstances under which the pilot conducted the off-airport landing could not be determined. ## Factual narrative Accident Site Location Based on Google Earth imagery, the logging road selected by the pilot as his intended landing site was in a forest clearing that was roughly circular in shape, with a diameter of about 2,300 ft. The logging road bisected the clearing and was oriented on a true heading of about 290°, which was parallel to the airplane's cruise flight track. The flight track was south of the clearing, and at the point where it was abeam the eastern edge of the clearing, was about the same distance north of a straight 12,000 ft segment of a two-lane paved road that was oriented on a true heading of about 270°. The center of the forest clearing was about 13,000 ft from the linear shoreline that was oriented approximately perpendicular to the flight track. The shoreline consisted of a sandy beach that was about 600 ft wide and extended at least 5 miles each way to the north and south. The pilot's destination airport, S16, was situated on that same linear stretch of shoreline/beach, about 4 miles north of where the flight track would have intersected the shoreline if the pilot did not turn towards the forest clearing and logging road that became the accident site. In its landing circuit for the forest clearing, the airplane traveled a total distance of about 16,000 ft from the point where it began the descent and turn from cruise flight to the last recorded data point (See Figure 1). From that same top of descent point and before the turn, the airplane was about 12,000 ft from, and headed almost directly toward, the shoreline/beach. Figure 1. Landing/Accident Site Approach Flight Path (Note proximity to road and beach) On March 30, 2019, about 1256 Pacific daylight time, a Piper PA-18-105 airplane, N215T, was destroyed when it was involved in an accident near Copalis Beach, Washington. The pilot sustained minor injuries. The personal flight was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, the preflight inspection, start-up, taxi out and takeoff were all normal. About 70 minutes into the cross-country flight, the engine "started acting up" by running "rough" and losing power. The pilot activated the carburetor heat and manipulated the throttle, but the engine operation did not improve, and he was unable to restore the engine to cruise power. The pilot reported that the airplane was at an altitude of 2,000 ft, and that he "did not have any time or altitude" to try to glide to a nearby airport. He performed an emergency landing on a "logging road" in a clearcut forest area. The pilot reported that, during the landing roll, the left wing impacted stumps before coming to rest in a nose-down attitude. The pilot saw fuel "pouring" into the cockpit and onto him; he believed that the fuel was coming from the left side of the airplane. The pilot left the airplane and hiked out of the area to find help. He reported the accident two days later, and when first responders arrived at the airplane it hadbeen consumed by a post-impact fire. The pilot also reported that the airplane was susceptible to carburetor icing and he had to use carburetor heat on several recent flights. The pilot stated later that the "altitude started declining as soon as the engine started running rough," and that he turned towards the logging road "as soon as [he] saw" that the airplane was losing power and altitude. He estimated that it was only a few minutes between the power loss and the landing. When asked about his approach to the selected landing location, the pilot reported that he "still had enough [power] to circle around while loosing [sic] altitude and tried to aim for that little gravel road there which looked like my best bet due to the circumstances." According to the icing probability chart in FAA Special Airworthiness Information Bulletin (CE-09-35) – Carburetor Icing Prevention, weather conditions were conducive to “Serious Icing – Cruise Power”. The airplane came to rest about 20 ft from the side of the logging road, in a clutter of various-sized cut tree branches and stumps. The airplane was upright, pitched nose down, with its tail about 6 ft off the ground. The fabric skin of the airplane, the tires, and most of the interior components were consumed or significantly damaged by fire. The cockpit was destroyed by fire, and the left wing was canted forward about 85o. Portions of the forward fuselage frame were impact damaged. The engine remained attached to the airframe and enclosed by the aluminum cowl, both sustained fire damage. The two-bladed aluminum propeller remained attached to the engine and the spinner was undamaged. Both propeller blades exhibited moderate twisting and bending deformation on their outboard half-spans. The outboard end of one blade was embedded into the top of a previously cut tree stump, but still attached to the remainder of the blade. That blade end was bent in a tip-aft arc, and the cut displayed similar curvature at the blade's entry point into the stump. The stump bore a similar but linear cut about 10 inches behind (relative to airplane travel direction) the embedded propeller blade, consistent with another, previous blade strike. Examination revealed that the engine was fire and impact damaged but did not exhibit any exterior evidence of any non-impact related damage. The top spark plugs were removed and examined. They did not display any evidence of mechanical failure or excessive wear. Manual rotation of the engine resulted in thumb compressions on all cylinders. The engine control cables remained connected to their respective engine components, but operability was impeded or prohibited due to impact and fire damage. Fire damage to the engine accessories, including the magnetos, as well as all fuel system components including the carburetor, prevented determination of their pre-accident condition and functionality. Fire and impact damage to the engine prevented determination of its pre-accident condition andfunctionality. ## Aircraft - Registration: [N215T](https://openairdocs.org/deregistered/N215T-2019-06-21), registration cancelled 2019-06-21, S/N 18-2329, built 1952 (OpenAirDocs) - Reported make and model: Piper PA18 (105 SPECIA) - Registry model: [Piper PA-18-105 SPECIAL](https://openairdocs.org/model/piper-pa-18-105-special) (registry code 7101808) (OpenAirDocs) - Registry engine: [Lycoming 0-235 series](https://openairdocs.org/engine/lycoming-0-235-series) (registry code 41505, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 18-2329 - Year built: 1952 - Airframe hours: 4371 - Engines: Lycoming O-320 SERIES 160 hp reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, December 21, 2018 - Departed: PUL, Puyallup, WA - Destination: S16, Copalis, WA - Equipment: ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 27; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review January 11, 2019; seat: front; restraint: 4-point; flight hours: 145 total, 31 in this make and model, 58 as pilot in command, 67 in the last 90 days, 48 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 230° at 8 knots - Visibility: 9 statute miles - Lowest ceiling: none - Temperature: 54 °F, dew point 48 °F - Altimeter: 30.38 inHg - Observed at: HQM, 10 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 20190330002189A](https://openairdocs.org/incident/20190330002189A), Mar 30, 2019: Piper PA-18-105 SPECIAL, Ocean City, WA, Substantial damage. PIC stated he experienced engine problems 3 miles east of Ocean City, WA. Engine was hesitating/sputtering. Applied and removed carb heat to try to remedy the… ## Other investigations on N215T (1) 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. - [NTSB ANC74DAG79](https://openairdocs.org/ntsb/ANC74DAG79), Nov 17, 1973: Piper PA-18 (N215T), Talkeetna, AK, substantial damage ## Docket (18 files) The files NTSB released with the investigation on November 3, 2021, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=99226. 22.2 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 9 pages, 7.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9684646&FileExtension=pdf&FileName=1%20-%20Form%206120%20N215T_Redacted-Rel.pdf - Metars (item 2, PDF, 1 page, 37 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9684682&FileExtension=pdf&FileName=16%20-%20METARs-Rel.pdf - FAA carburetor ice chart (item 3, PDF, 1 page, 262 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9685147&FileExtension=pdf&FileName=17%20-%20FAA%20Carb%20Ice%20Chart-Rel.pdf - Pilot email regarding flaps (item 4, PDF, 1 page, 42 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9684655&FileExtension=pdf&FileName=4%20-%20PIC%20Email%20re%20Flaps_Redacted-Rel.pdf - Record of conversation (pilot) April 2 (item 5, PDF, 2 pages, 61 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9684853&FileExtension=pdf&FileName=2%20-%20Record%20of%20Conversations%20PIC%20april%202%20%26%203-Rel.pdf - Record of communications (PIC) April 18 (item 6, PDF, 3 pages, 125 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9684574&FileExtension=pdf&FileName=3%20-%20Record%20of%20Communications%20PIC-Rel.pdf - Record of conversation (PIC) December 13 (item 7, PDF, 1 page, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9684862&FileExtension=pdf&FileName=5%20-%20Record%20of%20Conversation%20PIC%20Dec%2013%202019-Rel.pdf - Record of communications (PIC) may 13, 2020 (item 8, PDF, 1 page, 78 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9684664&FileExtension=pdf&FileName=6%20-%20Record%20of%20Comms%20PIC%20May%2013%2020-Rel.pdf - Record of conversation (FAA inspector) (item 9, PDF, 1 page, 80 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9685120&FileExtension=pdf&FileName=7%20-%20Record%20of%20Conversation%20FAA%20McKee-Rel.pdf - FAA exam photos (item 10, PDF, 4 pages, 8 photos, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9684391&FileExtension=pdf&FileName=9%20-%20FAA%20Exam%20Photos-Rel.pdf - FAA form 337 for bushwheels (item 11, PDF, 2 pages, 195 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9685129&FileExtension=pdf&FileName=10%20-337%20Bushwheels_Redacted-Rel.pdf - FAA form 337 for vortex generators (item 12, PDF, 2 pages, 216 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9684969&FileExtension=pdf&FileName=11%20-%20337%20VGs_Redacted-Rel.pdf - ADS-B data (item 13, XLSX, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9684673&FileExtension=xlsx&FileName=12%20-%20FAA%20ADSB%20March%2030-Rel.xlsx - Kml file of flight (item 14, KML, 2.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9684872&FileExtension=kml&FileName=13%20-%20WPR19LA105-Full-Rel.kml - Annotated track depictions (item 15, PDF, 10 pages, 10 photos, 3.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9685138&FileExtension=pdf&FileName=14%20-%20Annotated%20Track%20Depictions-Rel.pdf - Altitude and speed plots (item 16, PDF, 3 pages, 208 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9685156&FileExtension=pdf&FileName=15%20-%20Alt%20and%20Speed%20Plots-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 17, PDF, 1 page, 76 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9685366&FileExtension=pdf&FileName=18%20-%20N215T%20Wreckage%20Release%20_Redacted-Rel.pdf - Photos (item 18, PDF, 11 pages, 15 photos, 4.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9686743&FileExtension=pdf&FileName=8%20-%20N215T%20photos-Rel.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.