FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL04LA081 · Cessna 182P

7 Mar 2004 · Nashville, TN, United States

Cessna 182P · Accident: hard landing

From IGX · Chapel Hill, NC to John C Tune Airport (JWN)

Report a problem

Event

NTSB case
ATL04LA081
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 182P

Aircraft type
Cessna 182
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N325LA
Onboard fatalities
Unknown
Route
From IGX · Chapel Hill, NCTo John C Tune Airport (JWN), Nashville, TN
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Hard landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Flare, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the pilot, as he landed on runway 01, the airplane bounced and touched down hard on the nose wheel. The pilot initiated a go-around and returned to land on runway 01. During the go-around the pilot reported that the airplane was shaking violently, and would not climb above 200 feet. After the pilot landed the airplane and stopped the engine he realized that he had a propeller strike. No flight control or mechanical anomalies were reported by the pilot prior to the hard landing. Examination of the airframe revealed the propeller was bent aft, and the lower firewall was buckled. Aircraft logbooks were not recovered for examination.

Probable cause

The pilot's improper landing flare and his inadequate recovery from a bounced landing resulting in a hard landing and propeller strike of the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04LA081
Event ID
20040310X00312
Case number
ATL04LA081
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 380a6785bdb8c2e5be40d64bbc280ee96c24b39fb3a86756c681ba98d68ee9a4; retrieved 2026-09-22T07:53:17.174Z.