FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC26FA057 · Piper PA20

18 Jun 2026 · Cordova, AK, United States

Piper PA20 · Accident: controlled flight into terrain/object (CFIT) en route

From Yakutat Airport (YAK) to Merle K (Mudhole) Smith Airport (CDV)

Report a problem

Event

NTSB case
ANC26FA057
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
Ongoing
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 PA20

Aircraft type
Piper PA20
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
N7635K
Onboard fatalities
Unknown
Route
From Yakutat Airport (YAK), Yakutat, AKTo Merle K (Mudhole) Smith Airport (CDV), Cordova, AK
Aircraft age
About 76 years (built 1950)
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 · cruise
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
Controlled flight into terrain/object (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

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

On June 18, 2026, at approximately 1200, an experimental Piper PA-20 airplane, N7635K, was destroyed when it was involved in an accident about 44 miles southeast of Cordova, Alaska. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to a close family member, the pilot departed Brownsville Airpark (2CL1), Brownsville, California on the afternoon of June 15 and was en route to Fairbanks, Alaska where he was relocating with his girlfriend to pursue a job as a bush pilot after taking a year off from flying. According to witnesses, the pilot arrived at Yakutat Airport (YAK) Yakutat, Alaska on the afternoon of June 17; upon arriving, the pilot was told that there was no 100LL aviation fuel available. The fuel in YAK had been NOTAM’d as unavailable since September 2025. A family member confirmed that the pilot had three 5-gallon fuel jugs installed in the back of the airplane and a fuel valve which distributed fuel from the fuel jugs into the airplane’s fuel system. The family member reported that the pilot purchased about 45 gallons of automotive gas from the local gas station on June 17. Witnesses stated that the pilot departed YAK on the afternoon of June 17; however, the pilot returned to YAK a short time after departure because “ceilings too low and tops too high.” According to the family member the pilot spent the night in Yakutat and on the morning of June 18 he purchased another 15 gallons of automotive gas from the local gas station. A review of Federal Aviation Administration (FAA) archived audio files revealed that the airplane departed YAK on June 18, about 1028. At the time of departure visual meteorological conditions (VMC) existed at YAK, ceilings were few at 5,500 ft and overcast at 7,500 ft with 10 miles visibility and light rain. The airplane was believed to be enroute to Cordova; however, there was no flight plan filed and no other communication was reported between the pilot and JNU FSS or any other air traffic control facility. Instrument meteorological conditions (IMC) existed at CDV at the time of departure on June 18, and the forecast for CDV from June 18 at 1000 to June 19 at 1000 called for 6 miles visibility, mist, ceilings broken at 600 ft, and temporarily on June 18 between 1000 and 1300, local conditions were forecast to be 4 miles visibility with light drizzle, mist and ceilings at 600 ft. Automatic Dependent Surveillance - Broadcast (ADS-B) data did not capture the airplane’s route of flight on the day of the accident. The airplane was reported overdue to the Juneau Flight Service Station at about 1910 on June 18, by a concerned relative. The airplane wreckage was discovered at about 1530 on June 19 by the Alaska Army National Guard. The airplane impacted steep, mountainous terrain about 44 miles southeast of Cordova, at an elevation of about 1190 ft msl. A postcrash fire incinerated much of the wreckage. The National Transportation Safety Board (NTSB) investigator-in-charge responded to the accident site and examined the wreckage on June 25. The examination was delayed due to adverse weather conditions at the accident site.

The right wing remained attached to the fuselage, the left wing was separated and was located with the main wreckage; it was completely destroyed by the postcrash fire. Control cable continuity was established between the control surfaces and the fuselage on both wings. During recovery efforts the fuselage tubular frame and control cables to the tail were cut; as a result, the tail section became separated and was located about 30 feet downhill from the fuselage. The rudder, tailwheel and empennage were observed to be intact, the fabric on the empennage was consumed during the post-crash fire.

The Lycoming O-320 series engine was observed to be embedded in the soft terrain and was found with the main wreckage. The propeller appeared to be connected at the flange and one of the two blades was observed to have an “S” curve; the second propeller blade and left side of the engine were not observed because they were deeply embedded in the soft terrain. The pilot held a commercial pilot certificate with ratings for airplane single engine land (ASEL), airplane multiengine land (AMEL) and instrument airplane. According to FAA records, the pilot’s certificate was suspended on June 4, 2025, because of multiple enforcement actions. Furthermore, he reported 1,300 total hours of civilian flight experience and 100 hours in the last six months as of his last medical exam, which was performed on March 2, 2023. The pilot was issued a first class medical without limitations. The pilot’s most recent valid medical certificate expired in March 2025.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ANC26FA057
Event ID
20260620203200
Case number
ANC26FA057
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. 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: 8c5cac7dc3d80b704e26970dbe30d273f8dadc6fc0f50aae6f00c211ace268ee; retrieved 2026-09-15T09:17:05.859Z.