ERA12LA259

NTSB accident investigation · Cessna 172P · Brooksville, FL · March 24, 2012

Accident · No injuriesLimited investigationFinal report
Date
March 24, 2012, 13:15 local (17:15 UTC)
Place
Brooksville, FL
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N99087Cessna 172P
Defining event
Landing-flare/touchdown: Hard landing
Weather
Visual (VMC) · Day
Status
Completed · report December 5, 2012
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
Civil Air Patrol, FAA/FSDO
FAA report
20120324017339A
Case key
83258

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 pilot's improper landing flare, which resulted in a hard landing.

Findings · 2

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.

Performance/control parameters: landing flareAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 172P: 38 casesAll aircraft: 1,285 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotCessna 172P: 76 casesAll aircraft: 9,295 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

An airport ramp employee reported observing the airplane "porpoise" three times during the landing, followed by a tail strike, which he saw and heard. The pilot performed a go-around and remained in the traffic pattern for a full stop landing. The ramp employee observed the pilot and his passengers leave the airplane without performing an external inspection. During postaccident interviews, the pilot who was flying the airplane reported that he was performing a touch-and-go landing and bounced once during the initial touchdown. He stated that he did not land hard or experience a tail strike. The damage to the cabin floor, the engine firewall, and the tail strike bar was discovered later in the day by another pilot preparing to fly the airplane.

Factual narrative

On March 24, 2012, about 1315 eastern daylight time, a Cessna 172P, N99087, was substantially damaged during a hard landing at Hernando County Airport (BKV), Brooksville, Florida. The commercial pilot and two passengers were not injured. The airplane was operated by the Civil Air Patrol (CAP) under the provisions of 14 Code of Federal Regulations Part 91, for the purpose of giving orientation flights to new cadets. The flight originated at Tampa Executive Airport (VDF), Tampa, Florida at 1245. Damage to the airplane was reported by a CAP pilot after it was discovered during a pre-flight inspection on the afternoon of March 24, 2012. CAP safety personnel initiated an internal investigation to determine who was flying the airplane when the damage occurred. Initially, no pilots that were contacted reported any abnormal activity or were aware of the damage. A ramp employee at BKV reported the following. He was driving a fuel truck on the ramp about 1315 on March 24, 2012 and observed the accident airplane on final approach for runway 21. Since he was also a pilot, he pulled over and stopped the truck to watch the airplane land. He observed the airplane "porpoise" three times and he saw and heard the tail strike the runway. The pilot then added full power and commenced a go-around. The ramp employee also watched the airplane taxi to the ramp after the flight. He stated that the pilot did not perform an exterior walk-around inspection to check for any damage. The ramp employee proceeded into the fixed base operator's office to report the event. An inspector with the Federal Aviation Administration obtained copies of flight log entries for the accident airplane. He then interviewed the pilot that was flying the airplane at the time reported by the ramp employee at BKV. The pilot reported that he was performing an approach to runway 21 for a touch-and-go landing. He recalled the winds from the southwest at 8 knots with gusts to 13 knots. During the landing, the airplane bounced at first, then settled back down to the runway. He executed a full power takeoff and remained in the traffic pattern for a full stop landing. He stated that he performed a post-flight inspection and noted no discrepancies. He flew the airplane back to VDF without further incident. The pilot reported that he did not land lard or experience a tail strike. The FAA inspector examined the airplane and noted buckling damage to the cabin floor, the engine firewall, and a bent tail strike bar. Weather, reported at BKV at 1253, included surface winds from 230 degrees at 12 knots with gusts to 18 knots.

Aircraft

Registration
N99087
Reported as
Cessna 172P
Category
Airplane
Serial number
17276400
Airframe hours
4,553
Engine
Lycoming 0-320 SERIES, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Other work use · Part 91
Operator
Civil Air Patrol Inc
Registered owner
Civil Air Patrol Inc
Airworthiness certificate
Standard, Normal
Last inspection
Annual · March 1, 2012 · 19 hours before
Departed
VDF · Tampa, FL
Destination
BKV · Brooksville, FL
Airport
BKV · Hernando County Airport, runway 21, 5,015 × 150 ft, concrete

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
Pilot
Age
70
Injuries
None
Certificate
Commercial
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Seat
Left
Flight hours
355 total

Weather

Conditions
Visual (VMC) · Day
Wind
230° at 12 knots, gusting 18
Visibility
10 statute miles
Lowest ceiling
None
Temperature
82 °F, dew point 64 °F
Altimeter
30.01 inHg
Observed at
BKV

Docket · 8

The files NTSB released with the investigation on October 10, 2012, on NTSB’s docket system: statements, records, photos and specialists’ reports. 12.1 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.