# NTSB GAA18CA161: Cessna 172, N418DD, Green Valley, AZ, March 12, 2018

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: March 12, 2018, 14:00 local (21:00 UTC)
- Place: Green Valley, AZ
- Coordinates: 31.909166, -111.120834 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=31.9092&lon=-111.1208&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report August 27, 2018
- Report: Approved by Office Director
- NTSB office: General Aviation Accidents
- Parties: FAA
- NTSB case key (mKey): 96860
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA161
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96860/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96860
- Page: https://openairdocs.org/ntsb/GAA18CA161

## Probable cause

The pilot’s failure to maintain directional control of the airplane during landing with a tailwind.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172L, 24 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072432), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172L, 9 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072432), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md)
- [Wind: tailwind](https://openairdocs.org/ntsb-findings/03034015): Environmental issues › Conditions/weather/phenomena · Effect on operation (probable cause); cases with it: [Cessna 172L, 1 case](https://openairdocs.org/ntsb-findings/03034015/cases.md?model=2072432), [All aircraft, 594 cases](https://openairdocs.org/ntsb-findings/03034015/cases.md)
- [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 172L, 1 case](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=2072432), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna 172L, 13 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072432), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172L, 11 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072432), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Landing-landing roll: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cessna 172L, 1 case](https://openairdocs.org/ntsb-events/060/sequence.md?model=2072432), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md)

## Analysis

The pilot reported that during the landing roll he felt as though the airplane was being pushed to the left side of the runway so he applied full right rudder and left aileron. The airplane exited the left side of the runway, and he added power to prevent the airplane's nose from colliding with a drainage culvert, but the airplane accelerated and impacted a tree. The airplane sustained substantial damage to the leading edge of the left wing. The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. The pilot reported that the wind at the destination airport was from 90° at 10 knots, gusting to 15 knots. The airplane landed on runway 24. The pilot landed to runway 24 because of the 2.9-percent uphill gradient.

## Factual narrative

The pilot reported that during the landing roll he felt as though the airplane was being pushed to the left side of the runway and he applied full right rudder and left aileron. The airplane exited the left side of the runway, and he added power to prevent the airplane's nose from colliding with a drainage culvert, but the airplane accelerated and impacted a tree. The airplane sustained substantial damage to the leading edge of the left wing. The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. The pilot reported that the wind at the destination airport was 090 at 10 knots gusting to 15. The nearest weather reporting station, located 14 miles to the north at the departure airport, reported about the time of the accident the wind was from 040 at 3 knots. The airplane landed runway 24. The pilot landed to runway 24 because of the 2.9 percent uphill gradient.

## Aircraft

- Registration: [N418DD](https://openairdocs.org/deregistered/N418DD-2018-05-01), registration cancelled 2018-05-01, S/N 17260474, built 1972 (OpenAirDocs)
- Reported make and model: CESSNA 172 (L)
- Registry model: [Cessna 172L](https://openairdocs.org/model/cessna-172l) (registry code 2072432) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17260474
- Year built: 1972
- Airframe hours: 1690
- Engines: LYCOMING O-320-D2J 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, June 17, 2017
- Departed: RYN, Tucson, AZ
- Destination: 14AZ, Green Valley, AZ
- Airport: 14AZ, Ruby Star Airpark, runway 24, 4,300 × 50 ft, asphalt
- Equipment: Auto-pilot, Stall warning system

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 84; injuries: none; flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review June 19, 2017; seat: front; restraint: 4-point; flight hours: 2,993 total, 2,624 in this make and model, 2,720 as pilot in command, 24 in the last 90 days, 8 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 40° at 3 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 77 °F, dew point 39 °F
- Altimeter: 30.02 inHg
- Observed at: KRYN, 15 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20180312002409A](https://openairdocs.org/incident/20180312002409A), Mar 12, 2018: Cessna 172L, Sahuarita, AZ, Substantial damage. PIC stated the following: -Obtained all relevant information on 14AZ. -Obtained weather forecast info from national weather service. -Performed pre-flight…

## Docket (2 files)

The files NTSB released with the investigation on June 21, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96860. 4.3 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40464428&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Photo (Courtesy of FAA) (item 2, .PDF, 1 photo, 206 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40464429&FileExtension=.PDF&FileName=Photo%20(Courtesy%20of%20FAA)-Master.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
