CHI05CA132

NTSB accident investigation · Cessna 182F · Osage Beach, MO · May 30, 2005

Accident · No injuriesData collectionFinal report
Date
May 30, 2005, 16:00 local (21:00 UTC)
Place
Osage Beach, MO
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3225UCessna 182F
Weather
Visual (VMC) · Day
Status
Completed · report September 13, 2005
Report
Approved by Office Director
Parties
Kansas City, MO FSDO
FAA report
20050530009789A
Case key
61621

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 flare and his inadequate recovery from the bounced landing which resulted in a hard landing. A factor associated with the accident was the improper landing flare.

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.

Hard landingLanding - flare/touchdown
Flare - improperPilot in commandCause
Recovery from bounced landing - inadequatePilot in commandCause
Porpoise/pilot-induced oscillation - inadvertentPilot in command
In flight collision with terrain/waterLanding - flare/touchdown
Terrain condition - runway

Analysis

The airplane impacted the runway following a loss of control while landing. The pilot stated that upon returning to the airport the winds were reported over the UNICOM frequency as being calm, so he entered the he entered the traffic pattern for runway 14. He stated he that he was too high during this landing attempt so he initiated a go-around. The pilot stated he extended his final approach during the next landing attempt. He stated the approach looked good, but he "misjudged the flare and porpoised several times." The pilot stated he realized the airplane was damaged when he heard a clicking sound while using the right rudder pedal.

Factual narrative

On May 30, 2005, at 1600 central daylight time, a Cessna 182F, N3225U, experienced a hard landing on runway 14 (3,205 feet by 60 feet, asphalt) at the Grand Glaize Airport (K15), Osage Beach, Missouri. The private pilot and three passengers were not injured. The airplane received substantial damage. The 14 Code of Federal Regulations Part 91 personal flight was operating in visual meteorological conditions without a flight plan. The local flight originated from K15 at 1530.

The pilot stated that upon returning to the airport the winds were reported over the UNICOM frequency as being calm, so he entered the he entered the traffic pattern for runway 14. He stated he that he was too high during this landing attempt so he initiated a go-around. The pilot stated he extended his final approach during the next landing attempt. He stated the approach looked good, but he "misjudged the flare and porpoised several times." The pilot stated he realized the airplane was damaged when he heard a clicking sound while using the right rudder pedal.

Aircraft

Registration
N3225U
Reported as
Cessna 182F
Category
Airplane
Serial number
18254625
Engine
Continental O-470-R, 230 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Thomas S. Gittemeier, Jr.
Registered owner
Daniel Boone Flying Club, Inc.
Airworthiness certificate
Standard, Normal
Departed
K15 · Osage Beach, MO
Destination
K15

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
38
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
December 1, 2004
Seat
Left
Flight hours
180 total · 77 in this make and model · 138 as pilot in command · 3 in the last 90 days · 3 in the last 30 days · 0 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
40° at 7 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
82 °F, dew point 61 °F
Altimeter
29.93 inHg
Observed at
AIZ

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.