FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC00LA013 · Maule M7-235C

15 Nov 1999 · Palmer, AK, United States

Maule M7-235C · Accident: in flight encounter with weather during initial climb

From Four Corners Airport (14AK) to MYSTIC LAKE, AK

Report a problem

Event

NTSB case
ANC00LA013
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 M7-235C

Aircraft type
Maule M7
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
N5657A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Four Corners Airport (14AK)To MYSTIC 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
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 encounter with weather
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)
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 › Flight into known adverse weather, intentional

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

NTSB narrative

The pilot reported he was attempting to takeoff in gusty, crosswind conditions. Once airborne, he said the strong right crosswind required almost a 90 degree crab. He stated the left wing contacted the trees, and the plane settled into the trees upright. The owner of the 1,500 feet long by 100 feet wide, north-south airstrip, who witnessed the accident, said winds and downdrafts were strong, gusty, and 'rolling over the trees.' The witness said the right crosswind pushed the airplane into the trees. The weather observation from an airport four miles to the west recorded winds from 040 degrees at 13 knots, gusting to 25 knots.

Probable cause

The pilot's intentional takeoff into known adverse weather. Factors associated with this accident are crosswinds, gusts, and downdrafts.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC00LA013
Event ID
20001212X20062
Case number
ANC00LA013
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: c18f885af37b5d746d731b267effcdd75a70c476d348b2b2de85b74024dc122e; retrieved 2026-09-22T13:41:04.744Z.