FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Fresh Water Adventures Grumman G-44 accident

2 Sept 1998 · Dillingham, AK, United States

Grumman G-44 · Accident: in flight collision with terrain/water while maneuvering

From Dillingham Airport (DLG) to an unrecorded destination

Report a problem

Event

NTSB case
ANC98LA138
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
Visual Meteorological Cond

Grumman G-44

Aircraft type
Grumman G-44
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
N139F
Onboard fatalities
Unknown
Route
From Dillingham Airport (DLG), 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
Maneuvering · turn to reverse direction
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 terrain/water
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 › Clearance, not maintained

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

NTSB narrative

The commercial pilot departed under special VFR conditions on a CFR part 135 flight for a remote lake. During the flight, low clouds, rain, and fog were present in an area of mountainous terrain along the route of flight. The pilot stated that he intended to utilize a narrow mountain pass to transit the area, and as he entered the mountain pass, discovered that the ceiling and visibility would not allow safe passage. He said that he made an emergency 180 degree turn in an attempt to exit the pass, and subsequently collided with terrain. After initial impact, the airplane slid downhill about 100 feet, and came to rest on a 35 degree slope. The pilot stated that weather conditions at the time of the accident consisted of: Ceiling, 500 foot overcast; visibility, 2 miles with rain and fog; wind 360 degrees, at 8 knots. The pilot noted that there were no preaccident anomalies with the airplane.

Probable cause

The pilot's failure to maintain clearance with terrain. Contributing factors were the pilot's delayed remedial action (course reversal), low ceilings, rain, fog, and mountainous terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC98LA138
Event ID
20001211X10971
Case number
ANC98LA138
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: a6b86d541dd3599517d7f854bec4511cd7164ca583c36291b8d8c8947ccb5b65; retrieved 2026-09-18T17:05:20.413Z.