FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC21LA007 · Cessna 150L

16 Nov 2020 · Colton, OR, United States

Cessna 150L · Accident: collision with terrain/object (non-CFIT) en route

From Salem-Willamette Valley Airport/McNary Field (KSLE) to Portland Troutdale Airport (KTTD)

Report a problem

Event

NTSB case
ANC21LA007
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Cessna 150L

Aircraft type
Cessna 150
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N18666
Operator
Unknown
Onboard fatalities
Unknown
Route
From Salem-Willamette Valley Airport/McNary Field (KSLE), Salem, ORTo Portland Troutdale Airport (KTTD), Portland-Troutdale, OR
Aircraft age
About 48 years (built 1972)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Collision with terrain/object (non-CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC21LA007
Event ID
20201117102299
Case number
ANC21LA007
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: ebe358857ad9d497de94b3a3c933eeaf0a694c273bf001ddc124df11e52fa623; retrieved 2026-09-15T07:22:40.661Z.