ERA15CA038

NTSB accident investigation · Cessna 172P · Miami, FL · October 30, 2014

Accident · No injuriesData collectionFinal report
Date
October 30, 2014, 07:48 local (11:48 UTC)
Place
Miami, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N97277Cessna 172P
Defining event
Landing-flare/touchdown: Hard landing
Weather
Visual (VMC) · Day
Status
Completed · report December 15, 2014
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20141030021859A
Case key
90342

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 failure of the student pilot to achieve a proper touchdown during a touch-and-go landing resulting in a hard landing and substantial damage.

Findings · 4

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 · Student/instructed pilotCessna 172P: 76 casesAll aircraft: 9,295 casesProbable cause
Performance/control parameters: landing flareAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 172P: 38 casesAll aircraft: 1,285 casesProbable cause
Info processing/decision: decision making/judgmentPersonnel issues › Action/decision · Student/instructed pilotCessna 172P: 20 casesAll aircraft: 3,098 casesProbable cause

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 student pilot had performed three uneventful landings with his instructor on board; his certified flight instructor later stated that the student, "… performed way above the standards needed to show me he would be safe during solo flight." While flying solo for the first time, the student performed one uneventful touch-and-go landing and remained in the traffic pattern for runway 9R. With a calm wind, the student pilot reported that the approach was normal; however, the landing was harder than normal. He continued the takeoff roll for another touch-and-go landing but reported hearing a weird sound. He added power, and believe that was the moment when the nose landing gear tire deflated. He then felt a, "strange movement and I felt the nose falling." He reduced power to abort the takeoff and then heard and felt something touching the floor. After coming to rest he contacted the air traffic control tower and reported what occurred. Postaccident inspection of the airplane by several FAA inspectors revealed the wings, upper fuselage, cabin, tail, main landing gear, primary flight controls, engine, and engine mount were intact. The nose landing gear inner cylinder was pushed up through the upper housing, and the firewall was damaged on the left, right, and aft sides of the nose landing gear mount. The upper quadrant of the firewall also exhibited a seven inch buckle. Following recovery of the airplane, the engine was started and found to operate normally. The operator also reported that the cabin floor was bent.

Factual narrative

The student pilot had performed three uneventful landings with his instructor on board; his certified flight instructor later stated that the student, "… performed way above the standards needed to show me he would be safe during solo flight." While flying solo for the first time, the student performed one uneventful touch-and-go landing and remained in the traffic pattern for runway 9R. With a calm wind, the student pilot reported that the approach was normal; however, the landing was harder than normal. He continued the takeoff roll for another touch-and-go landing but reported hearing a weird sound. He added power, and believe that was the moment when the nose landing gear tire deflated. He then felt a, "strange movement and I felt the nose falling." He reduced power to abort the takeoff and then heard and felt something touching the floor. After coming to rest he contacted the air traffic control tower and reported what occurred.Postaccident inspection of the airplane by several FAA inspectors revealed the wings, upper fuselage, cabin, tail, main landing gear, primary flight controls, engine, and engine mount were intact. The nose landing gear inner cylinder was pushed up through the upper housing, and the firewall was damaged on the left, right, and aft sides of the nose landing gear mount. The upper quadrant of the firewall also exhibited a seven inch buckle. Following recovery of the airplane, the engine was started and found to operate normally. The operator also reported that the cabin floor was bent.

Aircraft

Registration
N97277
Reported as
Cessna 172P
Category
Airplane
Serial number
17276172
Built
1984
Airframe hours
13,239.4
Engine
Lycoming O-320-D2J, 150 horsepower, reciprocating
Damage
Substantial damage
Flight
Instructional · Part 91
Operator
ADF Airways
Registered owner
Elide Leasing Inc
Airworthiness certificate
Standard, Utility; Standard, Normal
Last inspection
100 hour · October 22, 2014 · 20 hours before
Departed
TMB · Miami, FL
Destination
TMB · Miami, FL
Airport
KTMB · Kendall-Tamiami Executive Airp, runway 9R, 5,999 × 1,500 ft, asphalt
Equipment
Stall warning system

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
Student pilot
Age
18
Injuries
None
Certificate
Student
Medical
Class 1, Without waivers/limitations
Seat
Left
Restraint
3-point
Flight hours
51 total · 51 in this make and model · 0 as pilot in command · 51 in the last 90 days · 25 in the last 30 days · 0 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
Calm
Visibility
10 statute miles
Lowest ceiling
None
Altimeter
29.96 inHg
Observed at
TMB

Docket · 7

The files NTSB released with the investigation on December 9, 2014, on NTSB’s docket system: statements, records, photos and specialists’ reports. 7.4 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 N97277 · 2

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