FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23FA059 · Engineering & Research ERCOUPE 415-C

5 Dec 2022 · Corning, IA, United States

Engineering & Research ERCOUPE 415-C · Accident: collision during takeoff/landing on approach

From Rankin Airport (78Y) to Corning Municipal Airport (CRZ)

Report a problem

Event

NTSB case
CEN23FA059
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
1 · 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

Engineering & Research ERCOUPE 415-C

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
N99345
Operator
Unknown
Onboard fatalities
Unknown
Route
From Rankin Airport (78Y), Maryville, MOTo Corning Municipal Airport (CRZ), Corning, IA
Aircraft age
About 76 years (built 1946)
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
Approach · VFR go-around
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
Collision during takeoff/landing
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Environmental issues › Physical environment
  • 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 student pilot was returning the airplane to his home airport following the completion of an annual inspection. Although there were no witnesses to the accident, one person near the airport saw the airplane approach “low and fast,” and another heard the sound of an engine “revving” before hearing the sound of impact. Examination of the wreckage revealed that the airplane impacted a powerline and a tree before contacting the ground. The airplane came to rest inverted about 500 ft beyond the departure end of the runway and was destroyed by impact forces and a post-crash fire. Flight control continuity was confirmed from the cockpit to all flight control surfaces. Examination of the airframe, engine, and propeller did not reveal any mechanical anomalies that would have precluded normal operation. The pilot’s logbook was not available for review, and his total flight experience could not be determined. Based on aircraft maintenance records, the pilot had accrued about 35 hours in the accident airplane since he purchased it about four years before the accident. The pilot did not hold, nor had he ever held, a Federal Aviation Administration medical certificate. Given the location of the airplane and the information provided by witnesses, it is likely that the pilot was attempting to conduct a go-around when the accident occurred, and failed to maintain sufficient altitude to avoid obstructions at the departure end of the runway, which resulted in impact with powerlines, a tree, and the ground. An autopsy of the pilot identi?ed extensive natural disease, including severe atherosclerosis of his cerebral arteries, coronary arteries, aorta, and kidney. Given the limited available information about the circumstances of the accident, whether the pilot's cardiovascular disease contributed to the outcome could not be determined. Toxicological testing detected the potentially impairing antihistamine medications diphenhydramine and cetirizine. Diphenhydramine and cetirizine independently can cause drowsiness and difficulty concentrating; combination use in elderly persons increases the risk of impairment in thinking, judgement, and motor coordination. It is not known whether the pilot’s ability to ?y the aircraft was impacted by his use of these medications as his level of ?ying experience was limited. The contribution to the accident of these medications individually or in combination could not be determined.

Probable cause

The pilot’s failure to maintain clearance from obstructions during a go-around, which resulted in impact with powerlines, a tree, and the ground.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23FA059
Event ID
20221205106417
Case number
CEN23FA059
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, cause areas. 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: f378cd529ed267b10e5f15de7fc4a828eb7a4c7f66001fda416c334b86936251; retrieved 2026-09-15T07:55:02.654Z.