ANC95LA041 · Cessna 170A
Cessna 170A · Accident: loss of control in flight on approach
From Lake Hood Airport (Z41) to Goose Bay Airport (Z40)
Event
- NTSB case
- ANC95LA041
- 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 170A
- Aircraft type
- Cessna 170
- 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
- N1364D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lake Hood Airport (Z41), AKTo Goose Bay Airport (Z40)
- 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
- Approach · VFR go-around
- 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 in flight
- 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 › Torque/p-factor, not corrected
Approximate · Estimated position: the centre of Anchorage, AK, the place the record names. Not the accident site.
NTSB narrative
THE STUDENT PILOT WAS PRACTICING TOUCH AND GO LANDINGS AT A GRAVEL AIRSTRIP THAT HAD SNOWBERMS ALONG EACH SIDE OF THE RUNWAY. DURING THE NINTH APPROACH FOR LANDING, THE PILOT FLARED TOO HIGH AND BALLOONED UPWARD. HE ADDED POWER TO ARREST THE DESCENT, THEN, DECIDED TO BEGIN A GO-AROUND. THE PILOT ADDED FULL POWER AND THE AIRPLANE VEERED TO THE LEFT. THE PILOT THEN BANKED THE AIRPLANE TO THE RIGHT AND THE RIGHT MAIN LANDING GEAR STRUCK THE SNOWBERM ALONG THE LEFT SIDE OF THE RUNWAY. THE PILOT HAD ACCRUED 56 TOTAL FLIGHT HOURS WITH 4.3 HOURS AS SOLO FLIGHT.
Probable cause
THE PILOT'S FAILURE TO CORRECT FOR TORQUE/P FACTOR WHEN ADDING ENGINE POWER FOR THE GO-AROUND MANEUVER. THE PILOT'S MISJUDGED FLARE, DELAYED GO-AROUND, AND LACK OF TOTAL EXPERIENCE WERE FACTORS IN THE ACCIDENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC95LA041
- Event ID
- 20001207X03058
- Case number
- ANC95LA041
- 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: 5b8f2894021306ea3b757de77bc0006b1d9a599485bb0143c4a140c83fa49b54; retrieved 2026-09-23T00:06:46.899Z.