FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC82DA065 · Maule M-4-210C

3 Aug 1982 · Eagle River, AK, United States

Maule M-4-210C · Accident: in flight collision with object during initial climb

From Eagle River, AK to Eagle River, AK

Report a problem

Event

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

Maule M-4-210C

Aircraft type
Maule M-4
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
N9872M
Onboard fatalities
Unknown
Route
From Eagle River, AKTo Eagle River, 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
Initial climb
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); Stall/mush
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 › Aborted takeoff, not performed
  • Pilot in command › Preflight planning/preparation, inadequate

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

NTSB narrative

THE PILOT REPORTED THAT HE PREFLIGHTED THE FLOAT PLANE, PUMPED THE FLOATS, AND CHECKED FOR WATER. AFTER THE ENGINE START, TAXI, AND PRETAKEOFF CHECKS, HE SET THE FLAPS AT THE FIRST NOTCH. HE ABORTED HIS FIRST TAKEOFF RUN AND TAXIED BACK FOR A LONGER RUN. THE PILOT STATED THAT THE ENGINE WAS PRODUCING NORMAL POWER, BUT THE AIRCRAFT STILL TOOK LONGER THAN NORMAL TO REACH FLYING SPEED. AT 55 MPH, THE PILOT SET A SECOND NOTCH OF FLAPS AND THE AIRCRAFT LIFTED OUT OF THE WATER. HOWEVER, THE PILOT REPORTED THE AIRSPEED WAS DECREASING, SO HE LOWERED THE NOSE SLIGHTLY, BUT THE SPEED CONTINUED TO DECREASE. SUBSEQUENTLY, THE PLANE SETTLED INTO TREES NEAR THE END OF THE LAKE. THE AIRCRAFT WAS ESTIMATED TO BE 21 LBS OVER ITS MAXIMUM GROSS WEIGHT LIMIT. THE ELEVATION OF THE LAKE WAS ABOUT 300 FT, BUT THE DENSITY ALTITUDE WAS ABOUT 688 FT. THE WATER ON THE LAKE WAS REPORTED TO BE CALM.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ANC82DA065
Event ID
20020917X02657
Case number
ANC82DA065
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 1982-08-04.
  • API snapshot SHA-256: 7b8e4743c26396f3acebb7e4807f16a7921704bcd83b710cdb6ab7f31de57152; retrieved 2026-09-24T01:50:01.245Z.