The U.S. aircraft register, updated daily
Accidents · NTSB GAA17CA067 · Final report

Cessna 172 accident near Concord, New Hampshire, November 10, 2016

On November 10, 2016 at about 10:00 pm local time, a 1981 Cessna 172, registered N53402, was substantially damaged in an accident during landing (flare/touchdown) near Concord, New Hampshire (Concord Muni airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 10, 2016 · about 10:00 pm local time
Place
Concord, New Hampshire · Concord Muni · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 P, built 1981 · all 172s on the register
Registration
N53402 · registry record · serial 17274743
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Abnormal runway contact during landing (flare/touchdown) defining event
  2. Hard landing during landing (flare/touchdown)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 111 hours in all; 38.2 in this make and model; 42.7 as pilot in command
  • Last flight review: December 11, 2015
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 9,037.8 hours
  • Last inspection: annual inspection, September 6, 2016
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320-D2J (piston); 5,458 hours total
  • Operator: Concord Aviation Services

The flight

  • Departed from: CON Concord NH at 9:30 pm
  • Destination: CON Concord NH
  • Flight plan: none
  • Runway 17, 6,005 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 190° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 48°F (9°C), dew point 25°F (-4°C)
  • Altimeter: 29.72 inHg
  • Observation at 9:51 pm from KCON

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

2 documents, released by the NTSB on January 11, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.