ANC02FA108 · Robinson R-44
Robinson R-44 · Accident: loss of control in flight en route
From Ketchikan International Airport (PAKT) to Winstanley Lake, AK
Event
- NTSB case
- ANC02FA108
- 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
- 2 · 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
- Visual Meteorological Cond
Robinson R-44
- Aircraft type
- Robinson R-44
- Category
- Helicopter
- 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
- N7189T
- Operator
- David Zampino
- Onboard fatalities
- Unknown
- Route
- From Ketchikan International Airport (PAKT), Ketchikan, AKTo Winstanley Lake, 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 · climb to 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
- Loss of control in flight
- 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 › Aircraft control, not maintained
- Pilot in command › Spatial disorientation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The owner/pilot and the sole passenger departed in the helicopter for a night cross country flight en route to a remote cabin on a lakeshore. When they did not return the next day, a search was initiated. The helicopter was discovered floating inverted in the lake near the remote cabin. The pilot's handheld GPS was found floating on the surface of the lake, and data from the accident flight was extracted from its memory. The GPS recorded date, time, position, groundspeed, heading, and altitude information. According to the GPS, the flight departed at 1940, about 9 minutes before official sunset, and followed a course along several coastal canals, and then headed inland to the lake where the accident occurred. The lake has a surface elevation of about 390 feet msl. The helicopter climbed to an altitude of 1,268 feet msl to clear terrain prior to reaching the lake, and once clear of terrain, the helicopter descended toward the lake. The GPS ground track indicates the helicopter followed the north shore of the lake to the area where the destination cabin was located, and descended to about 35 feet above lake level in the vicinity of the public use cabin. The helicopter maneuvered there for several minutes, and then reversed course. After the course reversal, the helicopter's ground speed and altitude began to increase, until the helicopter reached about 170 feet above lake level, and the helicopter's ground speed had decreased to about 15 mph. Seventeen seconds later, at 2025, the track ended, following a steep and rapid descent. The termination of the flight track was at an elevation consistent with the level of the lake. The accident site was situated in an area surrounded by hills and mountain ridges, and classified as a rainforest, which was receiving higher than normal amounts of rainfall. Area weather forecasts, before and after the accident, reflected scattered to broken cloud layers as low as 1,000 to 1,500 feet agl with mountaintops and ridges occasionally obscured by clouds, and overcast cloud layers as low as 2,500 feet agl. Visibility was generally greater than 3 miles with reports of marginal VFR and rain showers in some areas. An FAA inspector who was in the general vicinity when the helicopter departed for the cabin said the night was very dark due to low clouds and precipitation. The pilot held a commercial pilot certificate with a rotorcraft rating. He also held a flight instructor certificate for rotorcraft. According to FAA records, the pilot had accumulated about 838 total flying hours, of which 791 were in rotorcraft. The pilot was not instrument rated. An inspection of the helicopter did not reveal evidence of any preimpact mechanical anomalies.
Probable cause
The pilot's failure to maintain control of the helicopter in-flight due to spatial disorientation, which resulted in an uncontrolled descent and impact with the surface of a lake. Factors contributing to the accident were the high terrain surrounding the lake, and the lack of visual cues due to the dark night and low clouds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC02FA108
- Event ID
- 20020910X01577
- Case number
- ANC02FA108
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2002-08-29.
- API snapshot SHA-256: b19dde9eeb67dcbe64a10bea761118c91e5718ee5093ff5241f0e14d6feb6691; retrieved 2026-09-20T19:53:38.063Z.