Casualties unknown

Hard Landing Results in Structural Damage to Nose Gear, Firewall, Flooring, and Wing (N65659)

Baltimore, MD, US

On September 4, 2006, a Cessna 172P (registration N65659) was involved in an aviation accident near Baltimore, MD. Investigators recorded the probable cause as: The pilot's improper flare, which resulted in a hard landing. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-07-04Data APIEditorial standards

During landing flare, the airplane ballooned and landed hard. Subsequent inspection by an FAA inspector revealed structural damage, including a buckled firewall and wing, despite no apparent damage during post-flight check by the student pilot.

Incident Overview

A student pilot experienced a hard landing during the flare, causing the airplane to "balloon up a little" before touching down firmly. The landing was part of a training flight, after which the student pilot completed four additional landings without further incident before taxiing the airplane to the hangar.

Post-Flight Examination

The student pilot stated that a post-flight examination of the airplane revealed no visible damage. The airplane was secured in the hangar without any immediate signs of structural issues.

FAA Inspection

A subsequent examination by a Federal Aviation Administration inspector identified several structural discrepancies. These included a misaligned nose gear assembly, a buckled firewall, buckled fuselage flooring, and a buckled left wing outboard of the wing spar. The damage was discovered during the inspection, indicating that the hard landing had caused significant structural deformation that was not immediately apparent.

Findings

The hard landing during the flare resulted in damage to multiple components of the airframe, including the nose gear, firewall, flooring, and left wing. No other incidents occurred during the subsequent landings or taxi.

Frequently asked questions

What happened in the 4 Sept 2006 Cessna 172P accident near Baltimore, MD?

During landing flare, the airplane ballooned and landed hard. Subsequent inspection by an FAA inspector revealed structural damage, including a buckled firewall and wing, despite no apparent damage during post-flight check by the student pilot.

What aircraft was involved and where did it happen?

The accident on 4 Sept 2006 involved a Cessna 172P, registration N65659, at Baltimore, MD.

What was the probable cause of the accident?

The pilot's improper flare, which resulted in a hard landing.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20061027X01571. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.