FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI98LA228 · Cessna 172N

29 Jun 1998 · STONE LAKE, WI, United States

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

From South St Paul Municipal Airport/Richard E Fleming Field (SGS) to Private airstrip

Report a problem

Event

NTSB case
CHI98LA228
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 172N

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
N6596D
Operator
Unknown
Onboard fatalities
Unknown
Route
From South St Paul Municipal Airport/Richard E Fleming Field (SGS), SOUTH ST. PAUL, MNTo Private airstrip
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
Substantial

Cause areas

  • Aircraft performance, hydroplaning condition

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

NTSB narrative

The pilot stated that he used a slightly higher final approach airspeed to compensate for any possible wind gusts. After the aircraft touched down, a wind gust lifted the aircraft back off the runway surface. The aircraft settled back to the runway and the pilot immediately applied brakes, raised the flaps, and held the nose off the ground. The pilot reported that the braking action of the aircraft was minimal due to hydroplaning. The pilot stated that a go-around was not possible due to the length of runway remaining and a tree line that was present at the end of the runway. The aircraft traveled off the end of the runway where it impacted a deep rut in the terrain. The nose gear of the aircraft dug into the rut causing the aircraft to nose over. Post accident inspection of the airplane revealed evidence of reverted rubber on both the left and right main landing gears.

Probable cause

the lack of effective braking due to hydroplaning. Contributing factors to the accident were the trees off the end of the runway that made a go-around not possible and the ditch off the end of the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI98LA228
Event ID
20001211X10274
Case number
CHI98LA228
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: f62636b77f114d47482ca371890e869002e05617a44bfdacb69cfa385c219761; retrieved 2026-09-22T17:36:09.345Z.