FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL94GA111 · Grumman G-164A

2 Jun 1994 · Savannah, GA, United States

Grumman G-164A · Accident: hard landing

Report a problem

Event

NTSB case
ATL94GA111
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
0
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

Grumman G-164A

Aircraft type
Grumman G-164
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
N9868
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Estimated position: the centre of Savannah, GA, the place the record names. Not the accident site.

NTSB narrative

DURING THE TAKEOFF ROLL, THE PILOT REPORTED A VIBRATION IN THE TAILWHEEL ASSEMBLY. HE CONTINUED THE TAKEOFF PROCEDURE BUT ELECTED TO RETURN TO THE AIRPORT FOR A PRECAUTIONARY LANDING BEFORE DISPENSING OR DUMPING THE 1500 POUNDS OF CHEMICALS. AT TOUCHDOWN THE TAILWHEEL ASSEMBLY COLLAPSED AND SEPARATED FROM THE AIRFRAME. THE PILOT LOST CONTROL OF THE AIRPLANE AS IT SKIDDED TO A STOP ON THE RUNWAY. EXAMINATION OF THE AIRCRAFT FAILED TO DISCLOSE A MATERIAL FAILURE OR SYSTEM MALFUNCTION. ACCORDING TO THE OPERATOR, THE PILOT HAD NOT MADE A LANDING WITH THE AIRPLANE IN A HEAVY OR LOADED CONFIGURATION WITHIN THE LAST TWENTY FOUR MONTHS. THE OPERATOR HAD NO FORMAL EMERGENCY DUMP POLICY TO PREVENT LANDING WITH CHEMICALS ONBOARD DURING AN EMERGENCY.

Probable cause

THE PILOT'S IMPROPER LANDING FLARE WHICH RESULTED IN A HARD LANDING. A FACTOR WAS THE OPERATORS FAILURE TO PROVIDE A FORMAL EMERGENCY DUMP PROCEDURE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL94GA111
Event ID
20001206X01426
Case number
ATL94GA111
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. 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: 8f519f820c0440386352136712da9dcb1862c05de5366d583e91b2a01abad3f1; retrieved 2026-09-23T01:02:47.364Z.