# NTSB GAA16CA187: Cessna 172, N6023V, Scottsdale, AZ, March 6, 2016

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: March 6, 2016, 09:45 local (16:45 UTC)
- Place: Scottsdale, AZ
- Coordinates: 33.619998, -111.913887 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=33.6200&lon=-111.9139&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report June 15, 2016
- Report: Approved by Office Director
- NTSB office: General Aviation Accidents
- Parties: FAA
- NTSB case key (mKey): 92994
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA16CA187
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/92994/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=92994
- Page: https://openairdocs.org/ntsb/GAA16CA187

## Probable cause

The failure of the student pilot to maintain pitch control while landing, which resulted in a hard landing, loss of directional control, and runway excursion.

## Findings

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

- [Performance/control parameters: pitch control](https://openairdocs.org/ntsb-findings/01062022): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172S, 26 cases](https://openairdocs.org/ntsb-findings/01062022/cases.md?model=2072439), [All aircraft, 526 cases](https://openairdocs.org/ntsb-findings/01062022/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 172S, 66 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072439), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)

## Sequence of events

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

- [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072439), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md)
- [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172S, 76 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072439), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)

## Analysis

The solo student pilot reported that the airplane bounced after touched down, then veered off the runway to the left and came to a stop in gravel. A postaccident exam revealed substantial damage to the firewall. According to the student pilot there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

## Factual narrative

The solo student pilot reported that the airplane bounced after touched down, then veered off the runway to the left and came to a stop in gravel. A postaccident exam revealed substantial damage to the firewall. According to the student pilot there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

## Aircraft

- Registration: [N6023V](https://openairdocs.org/aircraft/N6023V), registered now, S/N 172S10198, built 2006 (OpenAirDocs)
- Reported make and model: CESSNA 172 (S)
- Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs)
- Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 172S10198
- Year built: 2006
- Engines: LYCOMING IO-360-L2A 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Sawyer Aviation
- Registered owner: Sawyer Aviation
- Airworthiness certificate: Standard, Normal
- Departed: SDL, Scottsdale, AZ
- Destination: SDL, Scottsdale, AZ
- Airport: SDL, Scottsdale, runway 03, 8,249 × 100 ft, asphalt
- Equipment: Electronic multifunction display

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 35; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; restraint: 3-point; flight hours: 11 total, 11 in this make and model, 11 in the last 90 days, 1.5 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 140° at 7 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 70 °F, dew point 27 °F
- Altimeter: 29.95 inHg
- Observed at: KSDL

## 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 20160306024339A](https://openairdocs.org/incident/20160306024339A), Mar 6, 2016: Cessna 172S, Scottsdale, AZ, Minor damage. On March 6, 2016, an 11:45 l, student pilot on first solo flight departed side of runway into gravel between runway and taxi way. Aircraft was CE-172S. VFR…

## Other investigations on N6023V (1)

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.

- [NTSB GAA19CA225](https://openairdocs.org/ntsb/GAA19CA225), Apr 20, 2019: Cessna 172 (N6023V), Scottsdale, AZ, substantial damage. Probable cause: The pilot's improper rudder inputs and failure to maintain directional control during landing with a crosswind, which resulted in a runway excursion and impact with a runway sign.

## Docket (2 files)

The files NTSB released with the investigation on May 31, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=92994. 628 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 522 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440600&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Accident Photo (Courtesy of FAA) (item 2, .PDF, 1 photo, 106 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440601&FileExtension=.PDF&FileName=Accident%20Photo%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.