FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL06CA033 · Cessna 172H

6 Dec 2005 · Waycross, GA, United States

Arnzen Cessna 172H · Accident: hard landing

From Waycross Ware County Airport (KAYS) to Waycross Ware County Airport (KAYS)

Report a problem

Event

NTSB case
ATL06CA033
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 172H

Aircraft type
Cessna 172
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
N1689F
Operator
Arnzen
Onboard fatalities
Unknown
Route
From Waycross Ware County Airport (KAYS), Waycross, GATo Waycross Ware County Airport (KAYS), Waycross, GA
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

  • Dual student › Flare, improper
  • Pilot in command(cfi) › Supervision, inadequate

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 certified flight instructor (CFI), the purpose of the flight was to give dual instruction to the student pilot. The flight departed the Waycross Municipal Airport, Georgia where they remained in the traffic pattern for takeoffs and landings. The CFI stated that they made a "harsh" landing on the third landing on runway 36. After the airplane was taxied back to the ramp, a brief inspection of the landing gear was conducted by the CFI, and no sign of damage was noted. In a record of telephone conversation with the Waycross Aviation School mechanic, he stated that two days after the flight, he noticed that the nose wheel rim of the accident airplane was bent. After further inspection the mechanic also observed that the firewall was buckled.

Probable cause

The student pilot's improper landing flare and the CFI's inadequate supervision resulting in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL06CA033
Event ID
20060130X00130
Case number
ATL06CA033
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: d9cdff36a792b63dd770de40bddd7f1f75ef0ddc706f3c04369727f55855eb76; retrieved 2026-09-22T05:12:55.374Z.