FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Frontier Flying Service Piper PA-31-350 accident

4 Apr 1992 · Kotzebue, AK, United States

Piper PA-31-350 · Accident: in flight encounter with weather on approach

From Fairbanks International Airport (FAI) to an unrecorded destination

Report a problem

Event

NTSB case
ANC92LA058
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
Charter & commuter
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-31-350

Aircraft type
Piper PA-31
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
N3555C
Onboard fatalities
Unknown
Route
From Fairbanks International Airport (FAI), Fairbanks, AKTo not recorded
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 135: Air Taxi & Commuter
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
Approach · IFR initial approach
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
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

  • Pilot in command › Altitude, not maintained
  • Pilot in command › Proper glidepath, not maintained

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

NTSB narrative

DURING THE IFR APPROACH TO THE AIRPORT, THE FLIGHT HAD BEEN CLEARED FOR THE ILS/DME FOR RUNWAY 8. THE PILOT PERFORMED THE PUBLISHED PROCEDURE TURN AND WAS ESTABLISHED ON THE LOCALIZER AND GLIDE SLOPE AT ABOUT 5.5 MILES DME. THE FLIGHT CONTINUED THE DESCENT AS THE PILOT COMPLETED THE BEFORE LANDING CHECKLIST. AT ABOUT 5 MILES DME, THE PILOT ATTEMPTED TO CALL THE FSS TO REPORT FINAL APPROACH FIX INBOUND, HOWEVER, HE HAD TO WAIT FOR ANOTHER AIRPLANE TRANSMITTING. THE PILOT THEN CONTACTED THE FSS AND REPORTED 4.5 MILES DME. SHORTLY AFTER THE RADIO CALL, THE PILOT FELT THE AIRPLANE CONTACT THE GROUND. THE PILOT REPORTED THAT HIS LAST INSTRUMENT SCAN THAT HE COULD REMEMBER SHOWED THAT HE WAS ON THE GLIDE PATH AND LOCALIZER AT AN ALTITUDE OF 1,250 FEET. AFTER THE ACCIDENT, THE PILOT REPORTED THAT THE VISIBILITY WAS ABOUT 100 YARDS AND BLOWING SNOW.

Probable cause

PILOT FACTOR IN THAT THE PROPER GLIDEPATH AND ALTITUDE WAS NOT MAINTAINED. FACTORS TO THE ACCIDENT WERE: INATTENTIVENESS AND SNOW.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC92LA058
Event ID
20001211X14358
Case number
ANC92LA058
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: 7e21e4a5b12973c19b8f53d88a1f0d841ed0b996157c62f7346cdb3ab6cbc74f; retrieved 2026-09-18T18:47:28.247Z.