FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW02LA058 · Cessna 172

17 Dec 2001 · New Braunfels, TX, United States

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

From New Braunfels National Airport (BAZ) to an unrecorded destination

Report a problem

Event

NTSB case
FTW02LA058
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 172

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
N5181R
Operator
Unknown
Onboard fatalities
Unknown
Route
From New Braunfels National Airport (BAZ), New Braunfels, TXTo 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
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

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

NTSB narrative

This was the 30-hour student pilot's second supervised solo flight. The student pilot stated that he set up for a normal approach to runway 36, landing on the first 1,000 feet of the runway. Just after landing, the airplane veered to the right 15 - 20 degrees. The airplane exited the right side of the runway, crossed a taxiway, impacted soft terrain, nosed over, and came to rest inverted. The wind at the time of the accident was reported to be from 350 degrees at 7 knots.

Probable cause

The student pilot's failure to maintain directional control of the airplane during the landing roll. A contributing factor was the soft terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW02LA058
Event ID
20011227X02452
Case number
FTW02LA058
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: e4cc107d8f7c69001fae118c7370cf901eb3fe9a3f2ba39e0644ac3618463637; retrieved 2026-09-22T11:14:59.735Z.