- Date
- November 21, 2004, 15:25 local (20:25 UTC)
- Place
- Anderson, IN
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N967SACessna 172S
- Weather
- Visual (VMC) · Day
- Status
- Completed · report January 24, 2005
- Report
- Approved by Office Director
- Parties
- Federal Aviation Administration
- FAA report
- 20041121032199A
- Case key
- 60639
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 flare and his inadequate recovery from a bounced landing.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
The airplane, piloted by a student pilot, sustained substantial damage during a hard landing. The pilot stated that he propoised four times. He said, "I was surprised by the magnitude of the second bounce, which I estimated to be 5-6 feet. I added power to flatten the porpoise-condition, and retained the yoke in position. There was a brief delay in moving one hand from the yoke to the throttle plus the delay in recognition of the magnitude of the bounce and porpoising effect. However, it appears to me that at the time I added power, I was already in the downward arc of the porpoise. Adding power did little in that instant but drive the front down faster before the elevators could provide lift. I felt like I had a hard three-point landing or had struck the nose wheel first. I believe the propeller struck during the third contact, but I was not aware of it having happened then."
Factual narrative
On November 21, 2004, about 1525 eastern standard time, a Cessna 172S, N967SA, piloted by a student pilot, sustained substantial damage during a hard landing on runway 30 (5,400 feet by 100 feet, dry asphalt) at the Anderson Municipal Airport-Darlington Field (AID), near Anderson, Indiana. The solo instructional flight was operating under 14 CFR Part 91. Visual meteorological conditions prevailed at the time of the accident. The pilot reported that a visual flight rules flight plan was filed and that he sustained no injuries. The flight originated from the South Bend Regional Airport, near South Bend, Indiana, at 1400.
The pilot's accident report stated:
I approached AID 30 runway per instructions from tower.
On initial final I was high relative to glide slope indicator
showing 4 white lights. At that time airspeed was about
75 kias (faster than desired 68), flaps were at 30, and
engine rpms were 1300- 1400 (below target, with intent to
bring plane to glide slope). I held nose up to slow plane.
These tactics had the plane at 70-72 kias and on glide slope
one or two markers out from threshold. I expected that I
would have to arrest downward momentum more than usual,
so I set my touchdown point further down the runway to the
first bars on the runway. I heard the stall horn before initial
contact with the runway. The intention was to bleed the
excess speed and momentum sacrificing runway distance as
the runway was 5400 feet.
Given the downward momentum and the speed, I expected
the first bounce and its magnitude, which I estimated to be
1-2 feet. I maintained the pitch and flair for the second
contact. I heard the stall horn before second contact.
I was surprised by the magnitude of the second bounce, which
I estimated to be 5-6 feet. I added power to flatten the
porpoise-condition, and retained the yoke in position. There
was a brief delay in moving one hand from the yoke to the
throttle plus the delay in recognition of the magnitude of the
bounce and porpoising effect. However, it appears to me that
at the time I added power, I was already in the downward arc
of the porpoise. Adding power did little in that instant but
drive the front down faster before the elevators could provide
lift. I felt like I had a hard three-point landing or had struck
the nose wheel first.
I believe the propeller struck during the third contact, but I
was not aware of it having happened then.
The bounce from that contact was back to 1-2 feet reflecting
the countermeasures of increased throttle and yoke/pitch that
I had already put in place. The fourth contact was the final
and I continued to roll.
The Anderson tower appears to have been unaware of any
incident (other than possibly a sloppy landing) because he
simply instructed me to the taxi way and ramp.
It was not until I stopped at Law Aviation and shutdown the
engine that I noticed the bent prop. The bend was
approximately 3" long on both ends and pointed in the
direction of the cockpit/cowling. Neither I nor the line man
who directed me in to the T, noticed any different engine
sounds, or upon further inspection, other damage.
Aircraft
- Registration
- N967SA
- Reported as
- Cessna 172S
- Category
- Airplane
- Serial number
- 172S9067
- Engine
- Lycoming IO-360-L2A, 180 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- Victory Aviation
- Registered owner
- Faurote Equipment Leasing Inc.
- Airworthiness certificate
- Standard, Normal
- Last inspection
- 100 hour · September 22, 2004 · 69.1 hours before
- Departed
- SBN · South Bend, IN
- Destination
- AID · Anderson, IN
- Flight plan
- VFR
- Airport
- AID · Anderson Municipal-Darlington, runway 30, 4,500 × 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
- Student pilot
- Age
- 50
- Injuries
- None
- Certificate
- Student
- Airplane ratings
- Single-engine land
- Medical
- Class 3, Valid Medical--w/ waivers/lim
- Seat
- Left
- Flight hours
- 54 total · 54 in this make and model · 9 as pilot in command · 19 in the last 90 days · 10 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 340° at 4 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 48 °F, dew point 37 °F
- Altimeter
- 30.26 inHg
- Observed at
- AID
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.