BFO92LA067 · Ercoupe (Eng & Research Corp.) 415C
Ercoupe (Eng & Research Corp.) 415C · Accident: on ground/water collision with object while taxiing
From KY70 · KY to KY70 · KY
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- BFO92LA067
- 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.) 415C Possible conflict
- Aircraft type
- Ercoupe (eng Research 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
- N93426
- Operator
- John Anderson
- Onboard fatalities
- Unknown
- Route
- From KY70 · KYTo KY70 · KY
- 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
- Taxi
- 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
- On ground/water collision with object
- 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 › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT HE WAS TAXIING TO THE WEST, AND THAT HE TURNED TO THE LEFT TOWARD THE PARKING AREA WHEN A GUST OF WIND LIFTED THE AIRCRAFT. HE STATED THAT HE TRIED TO CONTROL THE AIRCRAFT BY USING THE THROTTLE, AILERON AND RUDDER, BUT ALL WERE UNSUCCESSFUL. THE PILOT ALSO INDICATED THERE WERE WIND GUSTS FROM THE NORTH AT 20 KNOTS. THE AIRCRAFT COLLIDED WITH THE GROUND AND SLID INTO ANOTHER PARKED AIRCRAFT ABOUT 300 FEET FROM THE CENTERLINE OF THE RUNWAY.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN DIRECTIONAL CONTROL. CONTRIBUTING FACTORS WERE WIND GUSTS AND THE PILOT'S INADEQUATE COMPENSATION FOR WIND.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO92LA067
- Event ID
- 20001211X14592
- Case number
- BFO92LA067
- 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: 76dea764e809fa6a0dde04c09305c5d8eefb45408ed3cd72de83bffe49fa4499; retrieved 2026-09-23T03:08:49.511Z.