FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC83LA179 · Cessna 180

18 Sept 1983 · Talkeetna, AK, United States

Cessna 180 · Accident: on ground/water collision with terrain/water during takeoff

From an unrecorded airport to Lake Hood Airport (Z41)

Report a problem

Event

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

Cessna 180

Aircraft type
Cessna 180
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
N9125T
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Lake Hood Airport (Z41), Anchorage, 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
Takeoff · roll/run
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
On ground/water 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 › Aborted takeoff, delayed
  • Pilot in command › Judgment, poor
  • Pilot in command › Lack of familiarity with geographic area
  • Pilot in command › Performance data, inaccurate
  • Pilot in command › Total
  • Pilot in command › Wrong runway, selected

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

NTSB narrative

THE ACFT COLLIDED WITH A SANDBAR AND COLLAPSED THE LEFT MAIN LANDING GEAR DURING AN ABORTED TAKEOFF. THE PILOT STATED THAT HE WAS ATTEMPTING A TAKEOFF FROM A SHORT AIRSTRIP AT AN ELEVATION OF 3000 FT MSL WHEN HE ENCOUNTERED A TAILWIND AT ROTATION & THE ACFT SETTLED BACK TO THE GROUND AND COLLIDED WITH A SANDBAR. THE ACFT WAS LOADED WITH 2 PASSENGERS A LARGE DOG (EST. 130 LBS) BAGGAGE AND 50 GALLONS OF FUEL. THE PILOT SAID THE ACFT WAS AT OR BELOW MAX GROSS WEIGHT. THE RWY IS 1000 FT LONG SURROUNDED BY TREES HIGH AND A VERTICAL DROP.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ANC83LA179
Event ID
20001214X44400
Case number
ANC83LA179
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: 8097557a2b5f017955afd4f7d40eb53566518f29d19320c85a324831a50c7328; retrieved 2026-09-23T21:20:54.578Z.