FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC98LA022 · Piper PA-18

22 Feb 1998 · TYONEK, AK, United States

Piper PA-18 · Accident: in flight encounter with weather en route

From ILIAMNA, AK to Soldotna Airport (SXQ)

Report a problem

Event

NTSB case
ANC98LA022
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
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-18

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
N1379A
Operator
Unknown
Onboard fatalities
Unknown
Route
From ILIAMNA, AKTo Soldotna Airport (SXQ), Soldotna, 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 encounter with weather
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
Fuel exhaustion; 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
Substantial

Cause areas

  • Fluid, fuel › Exhaustion
  • Pilot in command › Became lost/disoriented
  • Pilot in command › In-flight planning/decision, inadequate
  • Pilot in command › VFR procedures, continued

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

NTSB narrative

The pilot had departed from a remote off-airport area during a dark night. During the flight to the intended destination, a layer of clouds obscured the ground. The pilot continued in VFR on-top conditions and became lost. The pilot climbed to about 10,000 feet msl to remain above the clouds. The airplane was equipped with a turn and bank instrument, but did not have any instrument panel lighting. The airplane's radio was not functioning effectively to establish contact with an FAA facility. The pilot was using a flashlight to illuminate the instrument panel, but the bulb burned out. The passenger in the airplane contacted the Anchorage Air Route Traffic Control Center (ARTCC) via a cellular telephone and requested assistance in getting down through the clouds and locating an airport. The pilot, passenger, and FAA air traffic controllers, worked together for about 1 hour in an attempt to assist the flight. About 3 hours after takeoff, the airplane's engine ran out of fuel, and the pilot began a descent through the clouds. The pilot reported he attempted to maintain control of the airplane, but experienced two or three uncontrolled spins. As the airplane neared the ground, the passenger established visual contact with the ground and yelled to the pilot. The pilot then pulled back on the control stick, and the airplane struck ground in an area of small hills. Rescue personnel located the airplane the following day. The pilot did not have an instrument rating. His pilot's certificate contained a limitation that prohibited night flying.

Probable cause

The pilot's continued VFR over-the-top operation, becoming lost/disoriented, his inadequate in-flight planning/decision making, and subsequent fuel exhaustion. Factors in the accident were the presence of a cloud layer below the pilot's selected altitude, the pilot's spatial disorientation, the pilot's lack of night flying experience, dark night conditions, and the lack of instrument panel illumination.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC98LA022
Event ID
20001211X09505
Case number
ANC98LA022
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1998-02-23.
  • API snapshot SHA-256: 2d0f6687caa9075a4aca49ffb1298c8dbc395b215121b02026e592a76aabf6b5; retrieved 2026-09-21T20:55:49.524Z.