FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC04LA019 · Gothard Super Cuby

4 Jan 2004 · Palmer, AK, United States

Gothard Super Cuby · Accident: loss of engine power during initial climb

From Anderson Lake Airport (0AK1) to Anderson Lake Airport (0AK1)

Report a problem

Event

NTSB case
ANC04LA019
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
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

Gothard Super Cuby

Aircraft type
Gothard SUPER CUBY
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
N3354B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Anderson Lake Airport (0AK1), Anderson Lake, AKTo Anderson Lake Airport (0AK1), Anderson 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
Loss of engine power
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

  • Reason for occurrence undetermined

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

NTSB narrative

The ski-equipped experimental airplane lost all engine power shortly after takeoff from a frozen lake and descended into trees. The airplane received structural damage to the left wing and spar, and the pilot received minor injuries. The pilot did not provide any information relating to the preaccident mechanical condition of the airplane, or what may have precipitated the loss of engine power.

Probable cause

The loss of engine power after takeoff for an undetermined reason, which resulted in a forced landing and in-flight collision with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC04LA019
Event ID
20040109X00045
Case number
ANC04LA019
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: ce76131df31de207df4043039b8c2190ba5ccdc1f64a9622144b527b78f16c90; retrieved 2026-09-21T19:18:13.049Z.