FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA07LA013 · Cessna 172S

31 Oct 2006 · Richfield, UT, United States

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

From Provo Municipal Airport (KPVU) to Richfield Municipal Airport (KRIF)

Report a problem

Event

NTSB case
SEA07LA013
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
N2097G
Onboard fatalities
Unknown
Route
From Provo Municipal Airport (KPVU), Provo, UTTo Richfield Municipal Airport (KRIF), Richfield, 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 · landing roll
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 › Compensation for wind conditions, inadequate

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

NTSB narrative

On his first approach, the student pilot was too high, and he executed a go-around. During his second attempt, he noticed that there were gusty crosswinds near the ground, but he felt that they were of a magnitude that he would be able to handle. The second approach and initial touchdown were without incident, but soon after the beginning of the landing roll, the airplane was hit by a gust of wind from the right. The gust pushed the airplane toward the left side of the runway, and lifted the right wing. Although the pilot attempted corrective action, he was unable to keep the airplane from departing the left side of the paved runway surface and entering an area of soft terrain. While he was attempting to get the airplane onto the runway, it encountered a mound/berm of dirt, and flipped over onto its back. There was no evidence of any flight control or nose wheel steering problems, and according to the student pilot, the only problem was his inability to compensate for the gusty crosswind conditions.

Probable cause

The student pilot's inability to compensate for the gusty crosswinds during the initial part of the landing roll, which resulted in a loss of control and a noseover. Factors associated with the accident are gusty crosswinds, and a mound/berm of dirt alongside the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA07LA013
Event ID
20061114X01672
Case number
SEA07LA013
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: babb02b8f6cff548a0b385fa18be9723b9d1e0fda40f54eed4964facd5b09f2f; retrieved 2026-09-22T04:16:33.677Z.