FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW98LA041 · Cessna 172P

1 Nov 1997 · Tooele, UT, United States

Great Western Aviation Cessna 172P · Accident: loss of control on ground/water during landing

From Salt Lake City International Airport (SLC) to Dawei Airport (TVY)

Report a problem

Event

NTSB case
FTW98LA041
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 172P

Aircraft type
Cessna 172
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
N96575
Onboard fatalities
Unknown
Route
From Salt Lake City International Airport (SLC), Salt Lake City, UTTo Dawei Airport (TVY)
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
Landing
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
  • Pilot in command › Recovery from bounced landing, improper

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

NTSB narrative

The student pilot had planned to practice stop-and-go landings on runway 34. He said the airplane touched down on all three wheels simultaneously, because he did not flare sufficiently. The left main and nose wheel came up, but instead of going around, he pushed the nose down. The airplane began to veer to the left, and the student corrected by applying right rudder. When the left main wheel contacted the runway, the airplane veered further to the left. The student applied additional right rudder retracted the flaps and added power to abort the landing. As the airplane departed the left side of the runway, the student closed the throttle and applied brakes. The left wing struck a 3,000-foot marker sign, and the airplane collided with a fence.

Probable cause

failure of the pilot to maintain directional control of the airplane, while landing. Factors related to the accident were: the pilot's improper flare for landing, his delay in attempting to go around (abort the landing), and the encounter with a runway marker and a fence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW98LA041
Event ID
20001208X09172
Case number
FTW98LA041
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: d9f61f214460ef5acc76d879045bf9a8b283caf0d8cc9881f1c79962b2de8ea2; retrieved 2026-09-22T18:14:04.033Z.