ATL93LA005 · Cessna 172N
Raleigh East Airport Cessna 172N · Accident: overrun during landing
From Raleigh East Airport (W17) to an unrecorded destination
Event
- NTSB case
- ATL93LA005
- 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
Cessna 172N
- 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
- N4874D
- Operator
- Raleigh East Airport
- Onboard fatalities
- Unknown
- Route
- From Raleigh East Airport (W17), Knightdale, NCTo 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 · 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 › Compensation for wind conditions, inadequate
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE COMMERCIAL PILOT ELECTED TO GO AROUND ON HIS FIRST LANDING ATTEMPT AT THE PRIVATE, GRASS AIRSTRIP DUE TO CROSSWINDS. ON HIS SECOND ATTEMPT WITH 20 DEGREES FLAPS SELECTED, HE DETERMINED THAT HE COULD NOT STOP THE AIRCRAFT IN THE REMAINING RUNWAY, AND ABORTED THE LANDING. THE AIRCRAFT COLLIDED WITH A DITCH, AND NOSED OVER. AN FAA INSPECTOR WENT TO THE SITE IMMEDIATELY AFTER THE ACCIDENT AND REPORTED THAT TAILWINDS PREVAILED ON THE RUNWAY THAT THE PILOT SELECTED. HE ALSO REPORTED THAT THE 2,200 FOOT AIRSTRIP SLOPED DOWNHILL TOWARD THE ACCIDENT SITE. AN INSPECTION OF THE FLIGHT CONTROLS AND WHEEL BRAKES SHOWED NO EVIDENCE OF A MALFUNCTION OR FAILURE, AND NONE WAS REPORTED BY THE PILOT.
Probable cause
THE PILOT'S IMPROPER IN-FLIGHT PLANNING AND HIS INADEQUATE COMPENSATION FOR WIND CONDITIONS, WHICH RESULTED IN THE OVERRUN OF THE RUNWAY. FACTORS WERE THE TAIL WIND CONDITIONS, AND THE DOWNHILL, GRASS RUNWAY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL93LA005
- Event ID
- 20001211X15809
- Case number
- ATL93LA005
- 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: 979e3d3272525737e00a05b6b14828248477d3a0785a87fc03140886c8cdb727; retrieved 2026-09-21T23:06:19.967Z.