ERA12CA111 · Ercoupe 415-C
Ercoupe 415-C · Accident: runway excursion during landing
From DeKalb Peachtree Airport (PDK) to Wakulla County Airport (2J0)
Event
- NTSB case
- ERA12CA111
- 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
Ercoupe 415-C
- Aircraft type
- Ercoupe 415
- 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
- N99576
- Operator
- Loumakis Kyriakos J
- Onboard fatalities
- Unknown
- Route
- From DeKalb Peachtree Airport (PDK), Chamblee, GATo Wakulla County Airport (2J0), Panacea, FL
- 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
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he was on the final approach leg of the traffic pattern at 80 mph. During the landing roll on the 2,590-foot, turf runway, the pilot applied the brakes, but the airplane continued off the end of the runway, impacted a fence, and came to rest in a nose-low position, sustaining substantial damage to the wing spars. Examination of the wreckage, which included an operational check of the wheel braking system, revealed no preaccident mechanical malfunctions or failures that would have precluded normal operation of the airplane. According to the Ercoupe Instruction Manual, the recommended landing approach airspeed was "between 60 and 70 mph." The instruction manual also indicated that landing the airplane at a higher airspeed and applying the brakes "will require decidedly less overall distance than it would if the airplane were held off the ground until minimum speed had been reached." A published landing distance table for the airplane indicated that, with an approach speed of 75 mph, the landing distance over a 50-foot obstruction on a paved runway would be about 1,800 feet.
Probable cause
The pilot did not attain the proper touchdown point during landing, which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12CA111
- Event ID
- 20111219X92426
- Case number
- ERA12CA111
- 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. 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: fe5e67e5691e1673525517466a7ba828a29c5db95bc79a5b7e6811ed8043951f; retrieved 2026-09-15T17:00:51.514Z.