FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 1894 · Piper PA-32

15 Jan 2002 · Haines, AK, United States

Piper PA-32 · Accident: in flight collision with object en route

From Skagway Airport (PAGY) to Haines Airport (PAHN)

Report a problem

Event

NTSB case
ANC02FA010
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
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
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-32

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
N30004
Operator
Unknown
Onboard fatalities
Unknown
Route
From Skagway Airport (PAGY), Skagway, AKTo Haines Airport (PAHN), Haines, 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 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
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 object
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); 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

  • Pilot in command › VFR flight into imc, continued

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

NTSB narrative

The commercial certificated air taxi pilot, the sole occupant, was scheduled to depart on a domestic passenger flight for an intermediate airport, located 14 miles south of the departure airport. The pilot was to pick up two passengers for a continuing flight to the planned destination. The route of the flight was along fjord type terrain, consisting of steep mountain slopes above a long inlet of water. The flight to the intermediate airport usually took about 10 minutes. The pilot delayed his departure for about 10 minutes while he waited for weather conditions along the route to improve. After departure, the pilot reported via radio that he was at a commonly used visual reporting point, about four miles south of the departure airport. The airplane did not arrive at the intermediate airport, and no further communication was received from the accident airplane. An aerial search located the wreckage in an area of steep forested terrain, 300 feet above the inlet water. The airplane collided with several trees before descending to the ground. Visual meteorological conditions prevailed at the intermediate airport, but low cloud conditions prevailed along the route of flight from the departure airport. At the time of the accident, an automated weather observation system (ASOS), located 5 miles southwest of the accident site, was reporting the weather conditions, in part, as having a visibility of four statute miles in light freezing rain and mist; clouds and sky condition, 800 feet overcast; temperature, 32 degrees F; dew point, 31 degrees F. The terminal forecast for the departure airport, and the area forecast, contained low visibilities in light rain and mist. An AIRMET was issued for mountain obscuration in clouds and precipitation.

Probable cause

The pilot's continued VFR flight into instrument meteorological conditions, and subsequent collision with trees while in cruise flight. Factors in the accident were weather conditions consisting of freezing rain, mist, and low ceilings.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC02FA010
Event ID
20020204X00181
Case number
ANC02FA010
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, 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: 09e2b70f33f87cac45766714a523a70342be3aecfb1ecfab4b6963abe71e79a0; retrieved 2026-09-18T13:07:39.028Z.