FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA013 · Cessna A185 F

7 Oct 2016 · San Antonio, TX, United States

Cessna A185 F · Accident: loss of control on ground during landing

From Conroe-North Houston Regional Airport (CXO) to San Antonio International Airport (SAT)

Report a problem

Event

NTSB case
GAA17CA013
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 A185 F

Aircraft type
Cessna 185
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
N4924E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Conroe-North Houston Regional Airport (CXO), Houston, TXTo San Antonio International Airport (SAT), San Antonio, TX
Aircraft age
About 37 years (built 1979)
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
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 on ground
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 › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

The pilot of a tailwheel equipped airplane reported that, while landing at a tower controlled airport, he performed a wheel landing and as the tail settled to the runway, in a "fraction of a second" the airplane was "sideways on the runway." He further reported that the airplane skidded off the runway to the right, the right main landing gear collapsed, and the right wing impacted the terrain.

The right wing sustained substantial damage.

The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

The automated weather observing system at the accident airport, about two minutes before the accident, recorded the wind at 360 degrees true at 11 knots. In addition, a wind shift and frontal passage was recorded about 3 minutes before the accident. The pilot reported that he landed on runway 12 left.

The pilot submitted an additional statement, which in part stated: "1) Tower assigned a runway with a known quartering tail wind, up to 18 knots. 2) As pilot in command, I did not process the wind call out prior to landing."

According to the Federal Aviation Administration Chart Supplement, within the final approach path, a wind sock was located to the left of the runway. The flight was flown under day visual meteorological conditions, the airplane entered the pattern on a left downwind, and would have likely been visible to the pilot. However, the pilot reported that he did not observe the wind sock.

According to an Air Traffic Control transcript of tower and ground communications, the accident occurred about 3 minutes and 8 seconds after the accident airplane's initial contact with the tower, when the accident airplane reported, 3 miles east inbound. The tower responded to the initial call with, wind 010 at 18, cleared to land 12 left.

About 40 seconds later, a ground controller held a taxiing jet stating in part: "hold out right there, we're not sure what we're going to be doing with the airport right now, [wind] 360 at 16, that's a pretty strong tailwind for you guys."

About 30 seconds later, tower directed the accident airplane to enter left downwind for 12 left and provided the landing clearance a second time for runway 12 left.

About 20 seconds later, a second airplane reported inbound and 8 seconds later was directed by tower to enter left downwind for 12 left. The airplane subsequently repeated the instruction and the tower reported wind 360 at 15.

About 25 seconds later, the second airplane requested to land runway 30 right instead of runway 12 left. The tower subsequently directed this second airplane to enter a left downwind for runway 30 left, while the accident airplane continued and landed on runway 12 left.

According to 14 CFR Part 91.3 titled, "Responsibility and authority of the pilot in command," sub bullet (a) states, "The pilot in command of an aircraft is directly responsible for, and is the final authority as to, the operation of that aircraft."

Probable cause

The pilot's failure to recognize the tailwind condition and maintain directional control during the landing roll, which resulted in a runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA013
Event ID
20161011X30638
Case number
GAA17CA013
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: c29bdb065c3387a202d6649158d0ba67b81feabc710e53248477ac1d57b40bad; retrieved 2026-09-16T04:22:40.025Z.