CHI07CA110 · Engineering & Research Ercoupe 415-C
Engineering & Research Ercoupe 415-C · Accident: in flight collision with object on approach
From Brighton Airport (45G) to 45G
Event
- NTSB case
- CHI07CA110
- 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
Engineering & Research Ercoupe 415-C
- Aircraft type
- Engineering Research 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
- N99811
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Brighton Airport (45G), Brighton, MITo 45G
- 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
- Approach · VFR pattern final
- 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
- In flight 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 › Proper glidepath, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane impacted terrain while on final approach to runway 22 (3,120 feet by 24 feet, asphalt). The student pilot stated that the airplane "was caught in a downdraft/wind shear and was not able to clear perimeter fence, even with application of full power." The pilot reported there was a small valley to the northeast of the airport which "probably caused the downdraft." An on-scene investigation revealed that the airplane impacted the radio-antenna of a passenger vehicle operating on the road adjacent to the airport. The airplane then impacted a rising embankment and proceeded through the airport perimeter fence, coming to rest short of the approach threshold. The student pilot was flying with an expired 90 day solo endorsement and did not have a medical certificate. The student pilot was operating the airplane as a light-sport pilot. A local weather reporting station reported the winds were from 260 magnetic degrees at 4 knots at the time of the accident.
Probable cause
The student pilot's failure to maintain proper glidepath to the runway. Contributing factors to the accident included the passenger vehicle, the rising embankment, and the airport perimeter fence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07CA110
- Event ID
- 20070507X00520
- Case number
- CHI07CA110
- 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, 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: 62ab464f4216366e1018c9424a0c49b31264eb3264ba850d5b7725c274c7419f; retrieved 2026-09-22T03:53:40.027Z.