FTW03LA175 · Cessna 172L
Check Six Aviation Cessna 172L · Accident: overrun during landing
From Stinson Municipal Airport (SSF) to an unrecorded destination
Event
- NTSB case
- FTW03LA175
- 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 172L
- 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
- N912KD
- Operator
- Check Six Aviation
- Onboard fatalities
- Unknown
- Route
- From Stinson Municipal Airport (SSF), San Antonio, 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
- 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
- Substantial
Cause areas
- Pilot in command › Airspeed, misjudged
- Pilot in command › Altitude, misjudged
- Pilot in command › Go-around, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was simulating a forced landing from the downwind position for runway 31. He set the power at idle and turned the airplane towards the runway. During the landing on the 2,880-foot long by 100-foot wide grass airstrip, he landed the airplane "long and fast, failed to stop, and hit [a] fence post at the end of the runway." The operator/owner safety recommendation block stated "Better pilot judgment, electing to do a go-around rather than land long." The weather observation facility at the departure airport, reported the wind from 180 degrees at 8 knots, and the density altitude was calculated at 2,352 feet.
Probable cause
The pilot misjudged his altitude and airspeed, and his failure to perform a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW03LA175
- Event ID
- 20030625X00953
- Case number
- FTW03LA175
- 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: 02127aaac365e7ee547b7e8177df4f4c6f03713b5c8b54e814091abd8bb88adc; retrieved 2026-09-21T09:26:54.473Z.