# NTSB NYC06CA221: Cessna 172P, N65659, Baltimore, MD, September 4, 2006

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: September 4, 2006, 16:00 local (20:00 UTC)
- Place: Baltimore, MD
- Coordinates: 39.325553, -76.413612
- Nearby events: https://openairdocs.org/map.md?lat=39.3256&lon=-76.4136&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report December 28, 2006
- Report: Approved by Office Director
- Parties: Baltimore FSDO
- NTSB case key (mKey): 64505
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC06CA221
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/64505/pdf
- Page: https://openairdocs.org/ntsb/NYC06CA221

## Probable cause

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

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Hard landing, landing - flare/touchdown
  - flare - improper, pilot in command (cause)

## Analysis

During the landing flare, the airplane "ballooned up a little," and then landed hard.  The student pilot then performed four more landings, before taxiing the  airplane to the hangar without further incident. The pilot stated that no damage was evident during the post-flight examination of the airplane. A subsequent examination by a Federal Aviation Administration inspector revealed a misaligned nose gear assembly, a buckled firewall, buckled fuselage flooring, and a buckled left wing outboard of the wing spar.

## Factual narrative

According to the student pilot of a Cessna 172P, during the landing flare, the airplane "ballooned up a little," and then had a "hard landing." He stated that he performed four more landings, and then taxied the airplane to the hangar without further incident. The pilot further stated that no damage was evident during the postflight examination of the airplane. A subsequent examination by a Federal Aviation Administration inspector revealed a misaligned nose gear assembly, a buckled firewall, buckled fuselage flooring, and a buckled left wing outboard of the wing spar.

## Aircraft

- Registration: [N65659](https://openairdocs.org/deregistered/N65659-2013-08-23), registration cancelled 2013-08-23, S/N 17275805, built 1982 (OpenAirDocs)
- Reported make and model: Cessna 172P
- Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs)
- Registry engine: [Lycoming IO-320 series](https://openairdocs.org/engine/lycoming-io-320-series) (registry code 41509, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17275805
- Engines: Lycoming IO-320 150 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Phoenix Aviation Inc.
- Airworthiness certificate: Standard, Normal
- Departed: KMTN, Baltimore, MD
- Destination: KMTN, Baltimore, MD
- Airport: KMTN, Martin State Airport, runway 33, 6,996 × 180 ft, concrete

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 28; injuries: none; student; medical: class 3, with waivers/limitations; seat: left; flight hours: 15 total, 15 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Wind: 340° at 6 knots
- Visibility: 7 statute miles
- Lowest ceiling: 5,000 ft broken
- Temperature: 91 °F, dew point 72 °F
- Altimeter: 29.87 inHg
- Observed at: KMTN

## Other investigations on N65659 (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ERA11CA385](https://openairdocs.org/ntsb/ERA11CA385), Jul 6, 2011: Cessna 172P (N65659), Baltimore, MD, substantial damage. Probable cause: The student pilot's failure to maintain aircraft control following a bounced landing.

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.