FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW97LA197 · Cessna 172RG

22 May 1997 · Rio Hondo, TX, United States

West Houston Airport Cessna 172RG · Accident: overrun during landing

From Farm Services Inc Airport (XS64) to an unrecorded destination

Report a problem

Event

NTSB case
FTW97LA197
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 172RG

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
N9492D
Onboard fatalities
Unknown
Route
From Farm Services Inc Airport (XS64)To not recorded
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
Overrun
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 › All available runway, not used
  • Pilot in command › Proper touchdown point, not attained

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

NTSB narrative

The pilot was returning to land on runway 18 after a 1 hour local flight. His first approach was 'high', and during the approach, he observed a rain shower at the departure end, moving in a northerly direction. The pilot then elected to execute a go-around and set up for another approach. He extended 30 degrees of flaps on the second approach, which was also high, and the aircraft touched down about 1,100 feet down the 2,600 foot runway. The pilot applied brakes, but the aircraft 'hydroplaned' and skidded off the right side of the runway, past the departure end, and onto uneven grassy terrain. The left wing struck a tree and the aircraft came to rest in a drainage ditch. Witnesses reported that there was standing water on the runway when the aircraft landed.

Probable cause

failure of the pilot to use all of the available runway during landing, and his resultant failure to attain a proper touchdown point for a safe rollout. Factors relating to the accident were: the wet runway with hydroplaning conditions, the uneven terrain (after the aircraft exited the runway), and the proximity of tree(s).

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW97LA197
Event ID
20001208X07920
Case number
FTW97LA197
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: e2e4da6f37e46efe795bc7c359df19011b8334eda60535eb4ed0dcce9ac86720; retrieved 2026-09-21T21:26:32.400Z.