FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL03LA081 · Beech A100

17 Mar 2003 · Carrollton, GA, United States

Beech A100 · Accident: overrun during landing

From F24 · Minden, LA to West Georgia Regional Airport / O V Gray Field (CTJ)

Report a problem

Event

NTSB case
ATL03LA081
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

Beech A100

Aircraft type
Beechcraft 100
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
N227BC
Operator
Unknown
Onboard fatalities
Unknown
Route
From F24 · Minden, LATo West Georgia Regional Airport / O V Gray Field (CTJ), Carrollton, 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 › Airspeed, misjudged
  • Pilot in command › Performance data, not calculated

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 departed with the flaps of the airplane inoperative and stowed in the up position. At the time of landing, runway 34 was wet and there was precipitation in the area. The airplane hydroplaned down the runway and rolled off the departure end of the runway into a muddy area. The airplane nosed over and the nose gear collapsed. The pilot stated that she did not compute the landing roll distance needed for landing on the wet runway. The Safety Information Section of the Pilots Operating Handbook states a caution when landing on runways covered by water. Examination of the airplane revealed that the propeller assemblies and both engines were damaged.

Probable cause

The pilot misjudged the approach and touchdown airspeeds that resulted in the overrun of the runway during a landing. Factors were the wet runway and hydroplaning conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL03LA081
Event ID
20030425X00571
Case number
ATL03LA081
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: 0a9222e1df9218ef2b9373134363594ffbb89b5600c17a769077393cfc7ee28b; retrieved 2026-09-22T09:30:05.504Z.