FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI90LA057 · Ercoupe (Eng & Research Corp.) 415-CD

29 Dec 1989 · LIZTON, IN, United States

Ercoupe (Eng & Research Corp.) 415-CD · Accident: overrun during takeoff

From LIZTON, IN (no airport) to an unrecorded destination

Report a problem

Event

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

Ercoupe (Eng & Research Corp.) 415-CD

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
N3871H
Operator
Orr, Roy A. · private individual
Onboard fatalities
Unknown
Route
From LIZTON, IN (no airport)To 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
Takeoff · roll/run
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 › Aborted takeoff, not performed
  • Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, selected

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PILOT STATED THAT DURING AN ATTEMPTED TAKEOFF HE 'APPLIED FULL POWER, AIRPLANE TRAVELLED ACROSS THREE AREAS OF SNOW....FAILED TO OBTAIN FLYING SPEED...CONTACTED FENCE AND DITCH.' THE RUNWAY IN USE WAS A 1,550 FOOT LONG, SNOW-COVERED GRASS STRIP; THE PILOT STATED 'I KNEW BETTER, AND I SHOULD HAVE WAITED FOR BETTER RUNWAY CONDITIONS. I JUST SCREWED UP.' THE PILOT WAS ATTEMPTING TO REMOVE HIS AIRCRAFT FROM HIS EX-WIFE'S PROPERTY BECAUSE HE WAS 'CONCERNED WITH DAMAGE TO AIRCRAFT BY OTHER PARTIES....' THE COMMERCIALLY CERTIFICATED PILOT INDICATED A TOTAL FLIGHT TIME OF 1,600 HOURS, OF WHICH 1,500 HOURS WERE IN SINGLE-ENGINE AIRCRAFT. HE REPORTED THREE HOURS FLIGHT TIME IN THE ACCIDENT MAKE AND MODEL AIRCRAFT, ALL WITHIN THE PRECEDING 90 DAYS.

Probable cause

SELECTION OF UNSUITABLE TERRAIN BY THE PILOT AND HIS FAILURE TO ABORT THE TAKEOFF. FACTORS RELATED TO THE ACCIDENT WERE: INTERPERSONAL RELATIONS OF THE PILOT, TERRAIN CONDITION AND FENCE ON OR NEAR THE AIRSTRIP, THE PILOT'S LACK OF EXPERIENCE IN THE TYPE OF AIRCRAFT, AND HIS FAILURE TO ATTAIN AIRSPEED.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI90LA057
Event ID
20001213X29941
Case number
CHI90LA057
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: 34d551d49f6f6bbfe7bb5385d747d72ea29ea4396f4f1a705c6f9681cd40b224; retrieved 2026-09-23T06:53:36.345Z.