FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11LA073 · Cessna 172K

15 Nov 2010 · San Antonio, TX, United States

Cessna 172K · Accident: loss of control in flight during landing

From Kerrville / Kerr County Airport at Louis Schreiner Field (KERV) to Kestrel Airpark (1T7)

Report a problem

Event

NTSB case
CEN11LA073
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 172K

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
N7183G
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kerrville / Kerr County Airport at Louis Schreiner Field (KERV), Kerrville, TXTo Kestrel Airpark (1T7), San Antonio, TX
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
Defining eventThe 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 in flight
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

  • Personnel issues › Task performance

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

NTSB narrative

According to several witnesses, the pilot was attempting to land with a tailwind. According to the pilot, he was trying to land when the wind became very strong and swirling. The pilot attempted to go around when the wing stalled. The airplane impacted several trees and came to rest inverted, resulting in substantial damage. An examination of the airframe and its systems revealed no anomalies. The closest weather observation station recorded wind from 190 degrees at 10 knots.

Probable cause

The pilot's failure to maintain aircraft control, which resulted in an aerodynamic stall. Contributing to the accident was the pilot's decision to land with a tailwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11LA073
Event ID
20101116X80945
Case number
CEN11LA073
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 4c33acdc8376792e44ece33c2f5b90facd267988d2a59ef826487e727d321919; retrieved 2026-09-15T15:34:22.088Z.