Skip to content

Atlas / NTSB / SEA05LA047

NTSB CAROL · Event

Event SEA05LA047

2004-12-27 Olympia, Washington, United States Airport · KOLM None 1 aircraft Status: Completed

Registry · N2536Q

FAA Aircraft Registry record.

Make / Model

CESSNA 182K

Year of manufacture

1966 · 38 years old at event

Engine

CONT MOTOR O-470 SERIES (230 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

19661125

ADS-B equipped

Yes — Mode-S A265DC

Registrant of record

WIEBE TIM

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's improper flare. Factors include too high of an airspeed and an inadvertent porpoise.

Factual narrative

On December 27, 2004, approximately 1520 Pacific standard time, a Cessna 182K, N2536Q, impacted the surface of the runway during an inadvertent hard landing at Olympia Regional Airport, Olympia, Washington. The private pilot and his passenger were not injured, but the aircraft, which is owned and operated by the pilot, sustained substantial damage. The 14 CFR Part 91 personal cross-country flight, which departed Rohnerville, California, about three hours and twenty minutes prior to the accident, was being operated in visual meteorological conditions. No flight plan had been filed. There was no ELT activation. According to the pilot, during his VFR approach to Olympia Airport, he decided to keep the aircraft's speed fairly high because he had been sequenced ahead of a couple of other aircraft that were on long final approaches. He therefore crossed the runway threshold at a higher speed than he would normally use, and after he initiated the landing flare, the aircraft began to porpoise. He then attempted to push it onto the runway surface by applying forward pressure on the control yoke, but during that attempt, the aircraft descended at a rate that resulted in it hitting the runway surface hard enough to bend the engine firewall. When the aircraft hit the runway surface, the pilot added power and executed a go-around, ultimately returning for an uneventful full-stop landing. According to the pilot, there were no problems with the aircraft's engine or flight controls, but instead he had just simply over-controlled the pitch input. During a VFR approach the pilot decided to keep the aircraft's speed fairly high because he had been sequenced ahead of a couple of other aircraft that were on long final approaches. He therefore crossed the runway threshold at a higher speed than he would normally use, and after he initiated the landing flare, the aircraft began to porpoise. He then attempted to push it onto the runway surface by applying forward pressure on the control yoke, but during that attempt, the aircraft descended at a rate that resulted in it hitting the runway surface hard enough to bend the engine firewall. It was determined that there were no problems with the aircraft's engine or flight controls, but instead the pilot had simply over-controlled the pitch input. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2004_SEA05LA047.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗