FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02LA168 · Cessna 310L

15 Sept 2002 · Atlanta, GA, United States

Cessna 310L · Accident: overrun during landing

From Newnan Coweta County Airport (KCCO) to DeKalb Peachtree Airport (KPDK)

Report a problem

Event

NTSB case
MIA02LA168
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
Instrument Meteorological Cond

Cessna 310L

Aircraft type
Cessna 310
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
N73NR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Newnan Coweta County Airport (KCCO), Newnan, GATo DeKalb Peachtree Airport (KPDK), Atlanta, 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 · landing roll
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
Overrun
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 › Go-around, not performed
  • Pilot in command › Proper touchdown point, not attained

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

NTSB narrative

The pilot performed a VOR approach to the 3,378 foot-long, 0.7 percent upsloping runway which became in sight at the "visual descent point." The airplane was landed on the wet runway with full flaps approximately 1,500 feet from the approach end of the runway between 80 and 85 mph. After touchdown the pilot announced to the passenger of having no brakes and retracted the flaps. She announced to the passenger again of, "...still no brakes"; the airplane did not begin to slow until the flaps were retracted. The airplane traveled off the end of the runway and a left skid was initiated causing the right main landing gear to collapse. She further reported, "Note: this runway has been seal coated with black paint sealer. It is very slick when wet. Much more so than asphalt." Examination of the main landing gear tires by FAA revealed the damage was consistent with hydroplaning. Additionally, "Tread reversal is evident particularly on the right main tire. Both tires had a section of approximately 10 inches long across the entire width where tread separation was evident." Runway 9-27 was crack sealed and coal-tar sealer/rejuvenator was applied before the accident date. Following the process, wet friction tests on treated and untreated areas of the runway revealed the treated area of the runway experienced a loss of 0.05 to 0.08 Mu (friction coefficient value) when compared with the untreated area, but the total treated area had an average of 0.72 Mu. New design/runway construction Mu value is .72. No one of the airport director's staff are aware of any problems associated with the runway crack sealing/seal coating. The Aeronautical Information Manual (AIM) indicates in part that pilots are cautioned that descent from the MDA at the missed approach point (MAP) may be inadvisable or impossible, on a nonprecision approach even if current weather conditions meet the published ceiling and visibility. The aircraft's speed, height above runway, descent rate, and runway length need to be considered by the pilot to determine if a safe landing can be accomplished. The performance chart in the airplane owner's manual indicates the ground roll distance is 720 feet and the total distance over a 50-foot obstacle is 1,301 feet; the chart does not specify distance to add when landing on a wet runway or distance to subtract due to an upsloping runway .

Probable cause

The pilot's misjudgment of speed/altitude and her failure to perform a go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02LA168
Event ID
20020923X05203
Case number
MIA02LA168
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: 56e4382e7c729595e8fd99ed2c3504d0f1db03294b66b4b162a74f713f11e3d9; retrieved 2026-09-22T10:15:53.663Z.