- Date
- September 30, 2011, 08:00 local (12:00 UTC)
- Place
- Westminster, MD
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N11019Cessna 172S
- Defining event
- Landing-flare/touchdown: Hard landing
- Weather
- Visual (VMC) · Day
- Status
- Completed · report February 16, 2012
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20110930022239A
- Case key
- 82027
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 inadequate recovery from a bounced landing, which resulted in a loss of airplane control. Contributing to the accident was the pilot's improper approach airspeed for a short-field landing.
Findings · 3
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.
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 pilot stated that, during approach for landing on the 1,840-foot-long runway, the airplane's airspeed was higher than recommended for a short-field landing. He stated that, after the first touchdown, the airplane bounced and floated, then it touched down on the runway a second time and bounced again. The third touchdown was "firm," the airplane became airborne, and the pilot elected to conduct a go-around. The pilot returned to his airport of origin, and postflight examinations revealed damage to one propeller blade and substantial damage to the engine firewall. The pilot reported that there were no preaccident mechanical malfunctions or anomalies with the airplane.
Factual narrative
The pilot stated that during approach for landing at the 1,840-foot-long runway, the airplane's airspeed was higher than recommended for a short field landing. He stated that after the first touchdown, the airplane bounced and floated, then touched down on the runway a second time and bounced again. The third touchdown was "firm," the airplane became airborne, and the pilot elected to conduct a go-around. The pilot returned to his airport of origin, and postflight inspection revealed damage to one propeller blade. Further inspection revealed substantial damage to the engine firewall. The pilot reported there were no mechanical malfunctions or anomalies with the airplane.
Aircraft
- Registration
- N11019
- Reported as
- Cessna 172S
- Category
- Airplane
- Serial number
- 172S10300
- Airframe hours
- 2,124
- Engine
- Lycoming IO-360-L2A, 180 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- Frederick Flight Center, Inc
- Registered owner
- Morrow Airplane LLC
- Airworthiness certificate
- Standard, Normal
- Last inspection
- 100 hour · August 19, 2011
- Departed
- FDK · Frederick, MD
- Destination
- FDK · Frederick, MD
- Airport
- 2W2 · Clearview Airpark, runway 14, 1,840 × 30 ft, asphalt
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
- 43
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land, Multi-engine land
- Medical
- Class 3, Without waivers/limitations
- Last flight review
- July 15, 2011
- Seat
- Left
- Flight hours
- 2,500 total · 5 in this make and model · 1,950 as pilot in command · 5 in the last 90 days · 2 in the last 30 days · 0 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 230° at 4 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 61 °F, dew point 55 °F
- Altimeter
- 29.73 inHg
- Observed at
- FDK, 16 nm away
Docket · 2
The files NTSB released with the investigation on December 31, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.2 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.