ANC16LA060 · Piper PA 18-150
Piper PA 18-150 · Accident: VFR encounter with IMC en route
From Chena Marina Airport (AK28) to Salcha, AK
Event
- NTSB case
- ANC16LA060
- 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
- 0 · 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 18-150
- Aircraft type
- Piper PA-18
- 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
- N8998Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chena Marina Airport (AK28), Fairbanks, AKTo Salcha, AK
- Aircraft age
- About 41 years (built 1975)
- 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
- 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
- Tree(s)
- 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
- Personnel issues › Experience/knowledge
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot stated that he was conducting a solo cross-country flight when he entered instrument meteorological conditions (IMC) during the en route portion of the flight. In an attempt to exit IMC, the pilot continued straight ahead and began a descent. While descending, he saw trees through the fog and attempted to climb just prior to impacting the trees. Following the impact, a post-crash fire ensued.
The accident pilot's flight instructor stated that he departed about 10 minutes ahead of the accident pilot in the same direction, but due to low cloud ceilings had returned to his departure airport. When he landed and turned on his cell phone, he received a voicemail from the accident pilot stating that he had crashed, there was a post-crash fire, and he needed help.
Probable cause
The pilot's decision to continue visual flight into instrument meteorological conditions, which resulted in an in-flight collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC16LA060
- Event ID
- 20160829X85955
- Case number
- ANC16LA060
- 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. 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: 7988a1191a4893e7d8ba6d281dbd38c1794115bed76dc669229ec71c2dab6220; retrieved 2026-09-16T04:12:25.534Z.