ANC93FA134 · Piper PA-32R-300
Yutana Airlines Piper PA-32R-300 · Accident: in flight collision with terrain/water en route
From Galbraith Lake Airport (GBH) to Bettles Airport (BTT)
Event
- NTSB case
- ANC93FA134
- 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
- 0
- 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-32R-300
- 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
- N477JC
- Operator
- Yutana Airlines
- Onboard fatalities
- Unknown
- Route
- From Galbraith Lake Airport (GBH), GALBRAITH LAKE, AKTo Bettles Airport (BTT), BETTLES, AK
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- In flight collision with terrain/water
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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
- Pilot in command › Lack of familiarity with geographic area
- Pilot in command › VFR flight into imc, intentional
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT-IN-COMMAND WAS UNFAMILIAR WITH THE PASS AND WAS ADVISED THAT THE WEATHER IN THE PASS WAS VERY POOR. HE STATED HE WOULD GO TAKE A LOOK. THE PASS MAKES AN 'S' TURN AT THE TOP IN LESS THAN 1 MILE OF DISTANCE. THE AIRPLANE IMPACTED THE SIDE OF THE MOUNTAIN NEAR THE MIDDLE OF THE 'S' TURN. WEATHER REPORTED BY ANOTHER PILOT 15 TO 20 MINUTES EARLIER INDICATED THE PASS WAS CLOSED.
Probable cause
THE PILOT-IN-COMMAND'S INTENTIONAL VFR FLIGHT INTO INSTRUMENT METEOROLOGICAL CONDITIONS AND HIS UNFAMILIARITY WITH THE GEOGRAPHICAL AREA. FACTORS WERE THE RAIN AND FOG.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC93FA134
- Event ID
- 20001211X13020
- Case number
- ANC93FA134
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 053943300976d4bbcb3d794f9b0de8fbbb66540dd91b6c2102aeb8a36bb4bfc1; retrieved 2026-09-21T00:26:14.712Z.