FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15LA244 · Raddatz Steve RV 8

6 Jun 2015 · Monroe, NC, United States

Raddatz Steve RV 8 · Accident: runway excursion during landing

From Tuscaloosa National Airport (TCL) to Charlotte-Monroe Executive Airport (EQY)

Report a problem

Event

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

Raddatz Steve RV 8

Aircraft type
Raddatz Steve RV-8
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
N323RP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tuscaloosa National Airport (TCL), Tuscaloosa, ALTo Charlotte-Monroe Executive Airport (EQY), Monroe, NC
Aircraft age
About 13 years (built 2002)
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
Defining eventThe 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
Runway excursion
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

The airline transport pilot stated that he made a "normal" landing in the tailwheel airplane and that the airplane began to veer right. The pilot applied rudder correction, but the airplane continued to the right, departed the runway, and traveled down an embankment. Examination of the runway revealed tire skid marks from the main landing gear consistent with the airplane touching down to the right of centerline, slightly angled toward the right side of the runway. The skid marks continued right, and departed the paved surface at an approximate 90° angle. There were no skid marks from the tailwheel. The pilot later stated that when the airplane was lifted, the tailwheel was unlocked, but the investigation could not determine whether it was unlocked before the accident or during the accident sequence. The pilot noted that postaccident maintenance of the airplane revealed no anomalies with the braking system.

Probable cause

The pilot's failure to maintain directional control during the landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15LA244
Event ID
20150619X15215
Case number
ERA15LA244
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: a88c491ac9ab73cb8019d912cf748c1455d1e502f52e948dda7f50d222f04d02; retrieved 2026-09-16T02:26:30.469Z.