FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA01LA215 · Cessna 182Q

12 Aug 2001 · Savannah, GA, United States

Cessna 182Q · Accident during landing

From Savannah Hilton Head International Airport (KSAV) to Savannah Hilton Head International Airport (KSAV)

Report a problem

Event

NTSB case
MIA01LA215
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 182Q

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
N4916N
Operator
Bruce H. Redler · private individual
Onboard fatalities
Unknown
Route
From Savannah Hilton Head International Airport (KSAV), Savannah, GATo Savannah Hilton Head International Airport (KSAV)
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
Miscellaneous/other
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 › Directional control, not maintained
  • Pilot in command › Recovery from bounced landing, delayed

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

NTSB narrative

Before taxiing, the pilot advised the controller that he had Automatic Terminal Information Service (ATIS) "Whiskey" which at that time indicated in part that the wind was variable at 7 knots. The pilot was cleared to taxi to runway 09, then was cleared to takeoff and remain in right traffic. The flight turned downwind, base, and final where during final approach with 30 degrees of flaps extended, the pilot later reported that he did not flare enough and the airplane bounced up "slightly." The airplane porpoised two times and he later learned that the propeller contacted the left runway edge. He attempted to takeoff again before the airplane departed the runway; this was unsuccessful. The airplane departed the left side of the runway, collided with a taxiway light, and rolled onto grass between the runway and taxiway E. The nose landing gear collided with a berm causing the nose landing gear to collapse; the airplane then nosed over. The pilot further stated that he lost consciousness when the flight contacted the berm and regained consciousness while inverted; both occupants exited the airplane through the passenger door. A METAR issued at 1153 local, indicates in part that the wind was from 170 degrees at 7 knots. Review of FAA Order 7110.65N, titled "Air Traffic Control" indicates, "ASOS/AWOS is to be considered the primary source of wind direction, velocity, and altimeter data for weather observation purposes..." The pilot received his high-performance signoff before the accident flight; the flight training for the signoff consisted of 5 hours.

Probable cause

The delay of the pilot to perform a go-around following a bounced landing and porpoise, and failure of the pilot to maintain directional control resulting in the airplane departing the runway and colliding with a berm.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA01LA215
Event ID
20010816X01698
Case number
MIA01LA215
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: 8d9556eee41992628038ea91f41516d8a95ca1ec1062f02b71fbf7b8a546829c; retrieved 2026-09-21T09:54:12.201Z.