FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC89LA045 · Cessna 152

19 Feb 1989 · CHUGIAK, AK, United States

Elmendorf Aero Club Cessna 152 · Accident: loss of control on ground/water during takeoff

From Elmendorf Air Force Base (EDF) to an unrecorded destination

Report a problem

Event

NTSB case
ANC89LA045
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 152

Aircraft type
Cessna 152
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
N5312Q
Onboard fatalities
Unknown
Route
From Elmendorf Air Force Base (EDF), ELMENDORF AFB, 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 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
Loss of control on ground/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 › Directional control, not maintained

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

NTSB narrative

THE 78 HOUR PRIVATE PILOT WAS ATTEMPTING A TOUCH AND GO LANDING. AFTER A SUCCESSFUL TOUCH DOWN, HE ADDED POWER TO TAKE OFF. AS THE POWER INCREASED, THE AIRPLANE VEERED QUICKLY TO THE LEFT ON THE ICY RUNWAY. HE REDUCED POWER, BUT WAS UNABLE TO REGAIN COMPLETE DIRECTIONAL CONTROL, AND COLLIDED WITH TWO SNOW BERMS AS HE WENT OFF THE LEFT SIDE OF THE RUNWAY. THE NOSE GEAR COLLAPSED WHEN THE AIRPLANE STRUCK THE SECOND BERM. THE PILOT STATED THAT HE HAD LAST FLOWN ON JANUARY 8, 1989, AND HAD APRX 11 HOURS OF FLIGHT TIME SINCE HE RECEIVED HIS AIRMAN'S CERTIFICATED ON AUGUST 31, 1988.

Probable cause

THE PILOT'S FAILURE TO MAINTAIN DIRECTIONAL CONTROL DURING A TOUCH AND GO LANDING. A CONTRIBUTING FACTOR IS THE PILOT'S LACK OF TOTAL FLIGHT EXPERIENCE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC89LA045
Event ID
20001213X27681
Case number
ANC89LA045
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: 9e0ec55d62318c8f0b8796c7f1412bb72cd40d28512bc85efb30edbde1e7afb9; retrieved 2026-09-23T07:52:22.279Z.