FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC23LA002 · Piper PA-32-260

16 Oct 2022 · Cordova, AK, United States

Piper PA-32-260 · Accident: VFR encounter with IMC en route

From Yakutat Airport (PAYA) to Birchwood Airport (PABV)

Report a problem

Event

NTSB case
ANC23LA002
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
1 · 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

Piper PA-32-260

Aircraft type
Piper PA-32
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
N3432W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Yakutat Airport (PAYA), Yakutat, AKTo Birchwood Airport (PABV), Birchwood, AK
Aircraft age
About 56 years (built 1966)
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
VFR encounter with IMC
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

After departing on a cross-country flight, the pilot returned to the departure airport due to poor weather conditions along the route. After landing, the pilot discussed the poor weather with a friend and told him he wanted to fly to another airport where he could leave the airplane and continue his trip using a commercial airline. His friend recommended that he stay where he was until the weather improved. The pilot subsequently received two weather briefings informing him that visual flight rules (VFR) flight was not recommended along his planned route due to instrument meteorological conditions (IMC). The pilot departed on the flight and was in communication with flight service while airborne when the communications ended abruptly and an emergency locator transmitter (ELT) activated. An eyewitness saw the airplane flying in and out of clouds before disappearing into the clouds near the accident site location. The airplane wreckage was found along a steep mountainside at an elevation about 1,866 ft mean sea level. Examination of the wreckage did not reveal any anomalies that would have precluded normal operation. The weather forecast information applicable for the accident time indicated that an AIRMET was valid for mountain obscuration conditions, and a Terminal Area Forecast (TAF) near the accident site valid at the accident time stated that IMC conditions were likely. Toxicology testing detected the antidepressant amitriptyline and its active metabolite nortriptyline in the pilot’s blood at therapeutic levels. While these substances are associated with side effects such as drowsiness and dizziness, the operational findings of this accident do not suggest performance issues related to fatigue. Gabapentin and norcyclobenzaprine were detected in the pilot’s urine and not in his blood, so no therapeutic or side effects would be expected. Thus, the effects from the pilot’s use of amitriptyline, gabapentin, and cyclobenzaprine were not likely a factor in this accident. The pilot had high urinary glucose; the cause was unknown but could possibly be dietary, from kidney disease, from diabetes medications, or from being diabetic. However, no glucose was detected in his vitreous fluid and his hemoglobin A1C indicates his average blood glucose levels would be around 120 mg/dL. Thus, it is unlikely that the pilot had low blood glucose, which is the concern for flight safety. Based on the available information, the circumstances of the accident are consistent with the pilot’s decision to conduct a visual flight rules flight into instrument meteorological conditions, which resulted in controlled flight into terrain.

Probable cause

The pilot’s improper decision to continue visual flight rules flight into instrument meteorological conditions, which resulted in controlled flight into terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC23LA002
Event ID
20221017106134
Case number
ANC23LA002
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, 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: 917a2f1f2bc7fcfd00fa04bebcd3f2b461a539f465a61d9399c570af152273ba; retrieved 2026-09-15T07:52:55.775Z.