# NTSB GAA17CA067: Cessna 172, N53402, Concord, NH, November 10, 2016

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: November 10, 2016, 17:00 local (22:00 UTC)
- Place: Concord, NH
- Coordinates: 43.202777, -71.50222 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=43.2028&lon=-71.5022&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 February 6, 2017
- Report: Approved by Office Director
- NTSB office: General Aviation Accidents
- Parties: FAA
- NTSB case key (mKey): 94376
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA17CA067
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94376/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94376
- Page: https://openairdocs.org/ntsb/GAA17CA067

## Probable cause

The pilot's improper landing flare, which resulted in a hard landing.

## 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 172P, 76 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072436), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172P, 38 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072436), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/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 172P, 16 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072436), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md)
- [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092); cases with it: [Cessna 172P, 39 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072436), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md)

## Analysis

The pilot reported that during the second landing of a closed traffic pattern flight, the airplane "ballooned" in the landing flare and touched down "hard." The pilot further reported that she aborted the landing and landed without further incident. The firewall sustained substantial damage. The pilot reported no preaccident mechanical malfunctions or failures with the airplane would have precluded normal operation.

## Factual narrative

The pilot reported that during the second landing of a closed traffic pattern flight, the airplane "ballooned" in the landing flare and touched down "hard." The pilot further reported that she aborted the landing and landed without further incident. The firewall sustained substantial damage. The pilot reported no preaccident mechanical malfunctions or failures with the airplane would have precluded normal operation.

## Aircraft

- Registration: [N53402](https://openairdocs.org/aircraft/N53402), registered now, S/N 17274743, built 1981 (OpenAirDocs)
- Reported make and model: CESSNA 172 (P)
- Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17274743
- Year built: 1981
- Airframe hours: 9037.8
- Engines: LYCOMING O-320-D2J 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Concord Aviation Services
- Registered owner: Anvab Inc.
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, September 6, 2016
- Departed: CON, CONCORD, NH
- Destination: CON, CONCORD, NH
- Airport: CON, Concord Muni, runway 17, 6,005 × 100 ft, asphalt
- Equipment: None

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 30; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review December 11, 2015; seat: left; restraint: none; flight hours: 111 total, 38.2 in this make and model, 42.7 as pilot in command

## Weather

- Conditions: Visual (VMC), Day
- Wind: 190° at 5 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 48 °F, dew point 25 °F
- Altimeter: 29.72 inHg
- Observed at: KCON

## 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 20161110022779A](https://openairdocs.org/incident/20161110022779A), Nov 10, 2016: Cessna 172P, Concord, NH, Substantial damage. The PIC was practicing landings in the aircraft on runway 17. On the second landing, the PIC stated that her approach to the runway was faster than usual. She…

## Docket (2 files)

The files NTSB released with the investigation on January 11, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94376. 1.9 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40448216&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Accident Photo (item 2, .PDF, 370 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40448217&FileExtension=.PDF&FileName=Accident%20Photo-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.