- Date
- June 25, 2010, 11:42 local (15:42 UTC)
- Place
- Salisbury, MD
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N2373KCessna 172S
- Defining event
- Landing: Abnormal runway contact
- Weather
- Visual (VMC) · Day
- Status
- Completed · report December 20, 2010
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20100625037109A
- Case key
- 76538
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 student pilot's improper recovery from a bounced 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.
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
According to the student pilot, he had conducted a 1.5-hour solo cross country flight and was landing at the destination airport. The student pilot stated that the airplane was "too high and too fast" on the landing approach, and the airplane "bounced" on touchdown. The student pilot "dove for the runway" in an attempt to recover, the airplane's nose landing gear contacted the runway, and the tire "blew." Postaccident examination by a Federal Aviation Administration inspector revealed substantial damage to the engine firewall. The student pilot reported there were no mechanical malfunctions or anomalies He also reported 54 hours of total flight experience.
Factual narrative
According to the student pilot, he had conducted a 1.5-hour solo cross country flight and was landing at the destination airport. The student pilot stated that the airplane was "too high and too fast" on the landing approach, and the airplane "bounced" on touchdown. The student pilot "dove for the runway" in an attempt to recover, the airplane's nose landing gear contacted the runway, and the tire "blew." Postaccident examination by a Federal Aviation Administration inspector revealed substantial damage to the engine firewall. The student pilot reported there were no mechanical malfunctions or anomalies He also reported 54 hours of total flight experience.
Aircraft
- Registration
- N2373K
- Reported as
- Cessna 172S
- Category
- Airplane
- Serial number
- 172S8074
- Airframe hours
- 2,319
- Engine
- Lycoming IO-360 SER, 180 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Instructional · Part 91
- Operator
- Reading Aero Club Inc
- Registered owner
- Reading Aero Club Inc
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · March 3, 2010
- Departed
- RDG · Reading, PA
- Destination
- SBY · Salisbury, MD
- Airport
- SBY · Salisbury-Ocean City, runway 05, 5,000 × 100 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
- 61
- Injuries
- None
- Certificate
- Student
- Medical
- Class 3, With waivers/limitations
- Seat
- Left
- Flight hours
- 54 total · 53 in this make and model · 11 as pilot in command · 17 in the last 90 days · 6 in the last 30 days · 0 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 100° at 6 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 82 °F, dew point 64 °F
- Altimeter
- 30.04 inHg
- Observed at
- SBY
Docket · 2
The files NTSB released with the investigation on September 19, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 467 KB 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.