# NTSB ANC21LA007: Cessna 150L, N18666, Colton, OR, November 16, 2020 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Limited · Final report - Date: November 16, 2020, 06:04 local (14:04 UTC) - Place: Colton, OR - Coordinates: 45.05, -122.156 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=45.0500&lon=-122.1560&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) - Highest injury: Fatal - Injuries: 2 fatal - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Alaska Regional Office - Parties: Textron Aviation, Federal Aviation Administration - NTSB case key (mKey): 102299 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ANC21LA007 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/102299/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=102299 - Page: https://openairdocs.org/ntsb/ANC21LA007 ## Probable cause The pilot’s failure to maintain positive control of the airplane in mountainous terrain during dark night conditions as a result of spatial disorientation which led to a loss of control and subsequent impact with terrain. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 150L, 9 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=2071826), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 150L, 26 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2071826), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) (defining event); cases with it: [Cessna 150L, 37 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2071826), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The instrument-rated pilot departed on an instrument flight rules (IFR) cross-country flight in dark night conditions. While enroute, the pilot cancelled his IFR clearance and reported to the air traffic controller that he was proceeding to another airport. Shortly thereafter, the pilot requested an IFR clearance to the original destination airport, then corrected himself and asked for an IFR clearance to the second airport. Shortly thereafter, the pilot declared an emergency and reported pitot system icing. The controller asked if the pilot could climb and maintain terrain clearance. The pilot replied that he thought he was climbing and asked the controller to verify the airplane’s altitude. However, recorded data showed the airplane in a rapidly steepening descending left turn in the vicinity of the accident site. The wreckage was located the following morning; however, due to the remote location of the site, it was not recovered or examined. The pilot reported loss of the pitot system due to icing which would have affected the accuracy and response of the airspeed indicator. However, the airplane was flying at altitudes below those forecast to support structural icing. The pilot’s subsequent request to ATC to verify his altitude and statement that he thought he was climbing while data showed the airplane was descending reflects confusion. Several minutes before the pilot’s declaration of emergency the airplane’s track was inconsistent with a direct route or the intended route to the destination airport, showing a series of left and right turns with reversing track changes of about 90 degrees. The distance over which these turns occurred is inconsistent with avoidance of precipitation depicted on a portable display or deviating around clouds to maintain VFR which would have been impossible to do so under dark night conditions over an area of sparse cultural lighting. The track changes prior to the declaration of emergency, the pilot’s reported confusion about the airplane’s vertical trajectory, and resultant loss of control in a descending turn are consistent with the known effects of spatial disorientation. Because the airplane was not recovered there is insufficient evidence whether this was due to a breakdown in the pilot’s scan under the forecasted turbulent conditions or whether failure of vacuum instruments providing attitude and directional information was involved. ## Factual narrative On November 16, 2020, about 0604 Pacific standard time, a Cessna 150L, N18666, was destroyed when it was involved in an accident near Colton, Oregon. The pilot and one passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to Federal Aviation Administration (FAA) air traffic control recordings and Automatic dependent surveillance-broadcast (ADS-B) track data, the pilot departed McNary Field Airport (SLE), Salem, Oregon, about 0515, on an instrument flight rules (IFR) flight plan with a destination of Portland-Troutdale (TTD) Airport, Portland, Oregon. Shortly after departure, the pilot cancelled his IFR flight plan and stated that he was bypassing TTD and proceeding to Eastern Oregon Regional Airport at Pendleton (PDT), Pendleton, Oregon. The controller advised the pilot of precipitation depicted northwest of Mount Hood and stated that the pilot could obtain an IFR flight plan if needed. About 10 minutes later, the pilot requested visual flight rules (VFR) flight following to Baker City Municipal Airport (BKE), Baker City, Oregon. The pilot stated that he intended to fly north of Mount Hood along the Columbia River Gorge. The controller reported light to moderate precipitation northwest of Mount Hood, but stated that the area south of Mount Hood appeared to be clear. The pilot acknowledged and stated that he would stay south of Mount Hood if he could remain clear of terrain. The controller instructed the pilot to resume his own navigation and advised that he could activate an IFR clearance if needed, but the pilot declined. ADS-B data subsequently show that the airplane tracked largely to the southeast before making a series of left and right turns on a modal track to the south-southwest. About 0600, with ADS-B data showing the airplane between 6800-6900 ft mean sea level (msl) and tracking to the southwest, the pilot contacted the controller and requested an IFR clearance to SLE. When asked by the controller to confirm the destination, the pilot requested an IFR clearance to BKE and when confirming equipment on board the aircraft stated he had VOR, GPS, and ADS-B in. Shortly thereafter, the pilot declared an emergency and reported pitot system icing. The controller asked if the pilot was able to climb and the pilot responded that he thought he was climbing. About one minute later, the pilot asked the controller to verify the airplane’s altitude. There were no further transmissions from the accident airplane. The airplane momentarily flew to the northeast, then appeared to enter a descending left turn, shortly after which radar and radio contact was lost. The final minute of ADS-B data recorded by the FAA showed that the airplane lost about 800 feet of altitude in about 37 seconds followed by the loss of another 1000 of altitude in the remaining period before received data stopped at 4900 ft msl. According to coordinates provided by first responders the elevation atthe accident site was about 2500 ft msl. PERSONNEL INFORMATION The pilot reported on his most recent airman certificate application, dated October 9, 2020, a total of 238.1 hours of flight experience. The pilot’s personal logbooks were not available for review. AIRCRAFT INFORMATION The airplane’s maintenance logbooks were not recovered. METEOROLOGICAL INFORMATION FAA contract Flight Service Station (FSS) provider Leidos did not provide the pilot any preflight weather briefings, but were contacted at 0506 when the pilot activated his IFR clearance. At that time, the pilot was advised of several AIRMET advisories current for the route of flight for IFR, mountain obscuration, icing, turbulence, and low-level wind shear, and was advised that the current radar depicted several scattered moderate rain showers across the region. The pilot filed his IFR flight plan through ForeFlight at 0502 for an estimated departure time of 0510. The pilot also viewed weather imagery through the ForeFlight app, which included the forecast charts from the current conditions and the 12/24-hour Low-Level Significant Weather Prognostic Chart. At the time of the accident, the sun was 11° below the horizon at an azimuth of 105°, and official nighttime prevailed. The moon was 28° below the horizon at an azimuth of 94°, and the phase was a waxing crescent with 3% of the moon’s disk illuminated. The closest weather reporting facility to the accident site was Aurora State Airport (UAO), Aurora, Oregon, about 29 miles west of the accident site an elevation of 200 ft msl. About the time of the accident, the recorded observation included wind from 360° at 6 knots, 10 miles or more visibility, ceiling broken at 5,500 ft above ground level (agl), overcast at 8,000 ft agl, temperature 8°C, dew point 7°C, and an altimeter setting of 30.02 inches of mercury. A base reflectivity image depicted very light intensity echoes over the flight path and supported light precipitation and clouds at the airplane’s cruise altitude. The freezing level in the area varied from 7,172 ft to 9,272 ft msl; however, in both soundings, the freezing level was above the airplane’s cruise altitude. WRECKAGE AND IMPACT INFORMATION The highly fragmented wreckage was located by search crews on November 17 in an area of steep, heavily wooded, mountainous terrain that had been burned by recent wildfires. The wreckage was not recovered due to its remote location. ## Aircraft - Registration: [N18666](https://openairdocs.org/deregistered/N18666-2022-09-26), registration cancelled 2022-09-26, S/N 15074027, built 1972 (OpenAirDocs) - Reported make and model: CESSNA 150L - Registry model: [Cessna 150L](https://openairdocs.org/model/cessna-150l) (registry code 2071826) (OpenAirDocs) - Registry engine: [Continental 0-200 series](https://openairdocs.org/engine/continental-0-200-series) (registry code 17020, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 15074027 - Year built: 1972 - Engines: Continental Motors O-200 SERIES reciprocating - Damage: Destroyed - Flight: Personal, Part 91 - Registered owner: Capitol Home Investments Inc - Airworthiness certificate: Standard, Normal - Departed: KSLE, Salem, OR - Destination: KTTD, Portland-Troutdale, OR - Flight plan: IFR - Equipment: ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 19; injuries: fatal; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1; last flight review October 9, 2020; seat: left; toxicology performed; flight hours: 238.1 total ## Weather - Conditions: Instrument (IMC), Night/dark - Wind: 360° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: 5,500 ft broken - Temperature: 46 °F, dew point 45 °F - Altimeter: 30.02 inHg - Observed at: KUAO, 29 nm away - METAR: KUAO 161353Z AUTO 36006KT 10SM BKN055 OVC080 08/07 A3002 RMK AO2 RAE11 SLP166 P0000 T00830067 ## 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 20201116017999A](https://openairdocs.org/incident/20201116017999A), Nov 16, 2020: Cessna 150L, Colton, OR, Destroyed, 2 fatal. N18666 departed salem (ksle) airport with IFR flight plan to troutdale (kttd) airport at approximately 13:15Z. At approximately 13:23Z)the pilot cancels IFR… ## Docket (10 files) The files NTSB released with the investigation on August 24, 2022, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=102299. 36.2 MB in all. - Meteorology specialist factual report (item 1, PDF, 27 pages, 3.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11934108&FileExtension=pdf&FileName=ANC21LA007%20-%20Colton,%20OR%20WX%20Factual-Rel.pdf - Meteorology attachment 1 - foreflight weather briefing (item 2, PDF, 17 pages, 3.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11934550&FileExtension=pdf&FileName=Attachment%201%20-%20ForeFlight%20Weather%20Briefing-Rel.pdf - Roc (item 3, PDF, 1 page, 122 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13570346&FileExtension=pdf&FileName=ROC-Rel.pdf - ATC (item 4, PDF, 3 pages, 483 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13385770&FileExtension=pdf&FileName=20-004%20Report-Rel.pdf - Flight track (item 5, PDF, 3 pages, 1.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13534754&FileExtension=pdf&FileName=Flight%20Track-Rel.pdf - ADS-B data (item 6, PDF, 2,574 pages, 21.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13386022&FileExtension=pdf&FileName=ANC21LA007%20-%20ADS-B%20Data-Rel.pdf - Medical and pathological information (item 7, PDF, 1 page, 127 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13571956&FileExtension=pdf&FileName=Medical%20and%20Pathological%20Information-Rel.pdf - Toxicological report (item 8, PDF, 1 page, 662 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13571656&FileExtension=pdf&FileName=Toxicology%20Report_Redacted-Rel.pdf - Statement of party representatives to NTSB investigation (Textron) (item 9, PDF, 1 page, 170 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13599228&FileExtension=pdf&FileName=Party%20Form%20Textron%20Aviation_Redacted-Rel.pdf - Accident pictures (item 10, PDF, 4 pages, 5.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12828591&FileExtension=pdf&FileName=Accident%20Pictures-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.