GAA17CA013

NTSB accident investigation · Cessna A185 · San Antonio, TX · October 7, 2016

Accident · No injuriesData collectionFinal report
Date
October 7, 2016, 13:30 local (18:30 UTC)
Place
San Antonio, TX
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4924ECessna A185
Defining event
Landing-landing roll: Loss of control on ground
Weather
Visual (VMC) · Day
Status
Completed · report January 18, 2017
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20161007016559A
Case key
94176

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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.

Findings · 6

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotCessna A185F: 71 casesAll aircraft: 9,295 casesProbable cause
Performance/control parameters: directional controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna A185F: 56 casesAll aircraft: 3,958 casesProbable cause
Wind: tailwindEnvironmental issues › Conditions/weather/phenomena · Decision related to conditionCessna A185F: 5 casesAll aircraft: 594 cases
Wind: variable windEnvironmental issues › Conditions/weather/phenomena · Effect on operationCessna A185F: 1 caseAll aircraft: 113 cases

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

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."

Factual 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."

Aircraft

Registration
N4924E
Reported as
Cessna A185 (F)
Category
Airplane
Serial number
18503909
Built
1979
Airframe hours
2,442
Engine
Continental IO-550-D, 300 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · November 4, 2015
Departed
CXO · Houston, TX
Destination
SAT · San Antonio, TX
Airport
SAT · San Antonio Intl, runway 12L, 5,519 × 100 ft, asphalt
Equipment
Stall warning system, Electronic flight bag or handheld device, Electronic multifunction display, Electronic primary flight display

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
65
Injuries
None
Certificates
Private, Commercial, Airline transport
Airplane ratings
Multi-engine land, Single-engine land, Single-engine sea
Instrument ratings
Airplane
Medical
Class 3, Without waivers/limitations
Last flight review
August 17, 2016
Seat
Left
Restraint
4-point
Flight hours
4,500 total · 4,000 in this make and model · 4,500 as pilot in command · 35.4 in the last 90 days · 2.2 in the last 30 days · 1.2 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
360° at 11 knots
Visibility
10 statute miles
Lowest ceiling
11,000 ft broken
Temperature
82 °F, dew point 72 °F
Altimeter
30.04 inHg
Observed at
KSAT

Docket · 5

The files NTSB released with the investigation on December 1, 2016, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.3 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.

Other investigations on N4924E · 1

Matched to the same aircraft by N-number and date.