ATL04LA068 · Cessna 182L
Cessna 182L · Accident: hard landing
From KDKS · Knoxville, TN to McGhee Tyson Airport (KTYS)
Event
- NTSB case
- ATL04LA068
- 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 182L
- 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
- N3191R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From KDKS · Knoxville, TNTo McGhee Tyson Airport (KTYS), Knoxville, 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 › Compensation for wind conditions, inadequate
- 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
The airplane was being flown to a nearby airport for an annual inspection. Upon arriving at the destination airport , the pilot checked the local weather, and discovered that the winds were 230-degrees at 16 knots gusting to 24 knots. The airport information revealed that there was a wind shear alert in effect also. The pilot stated that the flight was vectored to runway 23R, and while on the approach to land the flight encountered turbulent weather conditions. During the landing flare, the flight encountered a wind gust, and the airplane climbed several feet higher above the ground. The airplane was then slammed onto the runway and bounced several times. The pilot taxied the airplane to the ramp without further incident. The post-accident examination of the airplane revealed that the engine firewall was buckled.
Probable cause
The pilot's improper flare and his inadequate compensation for wind conditions. Wind gust was a factor
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL04LA068
- Event ID
- 20040122X00088
- Case number
- ATL04LA068
- 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: cc53ea2ee8691bff95ab1c47f0d8dcb8d8c407030d59f775e804617109ab2453; retrieved 2026-09-22T08:04:33.570Z.