FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX07CA185 · Cessna 172S

2 Jun 2007 · Wendover, UT, United States

Cessna 172S · Accident: loss of control on ground/water during landing

From South Valley Regional Airport (KU42) to Wendover Airport (KENV)

Report a problem

Event

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

Cessna 172S

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
N65755
Operator
Jason S. Vance · private individual
Onboard fatalities
Unknown
Route
From South Valley Regional Airport (KU42), West Jordan, UTTo Wendover Airport (KENV), Wendover, UT
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 · flare/touchdown
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
Destroyed

Cause areas

  • Pilot in command › Directional control, not maintained

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

NTSB narrative

During the landing roll, the airplane veered off the runway into the sand infield where it was destroyed by an ensuing post impact ground fire. The pilot stated that he made a normal approach and landing on runway 08, and there appeared to be no crosswind or wind gusts. During the landing roll a wind gust lifted the left wing, the airplane went up on two wheels, and started to veer off the runway. He attempted to regain control and at one point, decided to add power to execute an aborted landing. The airplane did not accelerate quickly enough and veered off the runway into the sand infield. The pilot pulled off the power, the airplane hit three bumps, and came to a stop. When he egressed he noticed the airplane was on its belly. He assisted evacuating his wife and daughter just before the airplane erupted in flames and was destroyed. The pilot stated that the airplane and engine had no mechanical failures or malfunctions during the flight.

Probable cause

The pilot's failure to maintain directional control during the landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX07CA185
Event ID
20070710X00898
Case number
LAX07CA185
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: 3c4ecef3bf894d660d6ac1e439438191265d4f0522cae6d203caf63593a70fae; retrieved 2026-09-21T18:30:10.548Z.