# NTSB CHI07CA110: Engineering & Research Ercoupe 415-C, N99811, Brighton, MI, April 21, 2007 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 21, 2007, 13:40 local (17:40 UTC) - Place: Brighton, MI - Coordinates: 42.893611, -83.998886 - Nearby events: https://openairdocs.org/map.md?lat=42.8936&lon=-83.9989&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report June 27, 2007 - Report: Approved by Office Director - Parties: Federal Aviation Administration, Detroit FSDO - NTSB case key (mKey): 65667 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI07CA110 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/65667/pdf - Page: https://openairdocs.org/ntsb/CHI07CA110 ## 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with object, approach - vfr pattern - final approach - proper glidepath - not maintained, pilot in command (cause) - object - vehicle (contributing factor) - In flight collision with terrain/water, approach - vfr pattern - final approach - terrain condition - dirt bank/rising embankment (contributing factor) - object - fence (contributing factor) ## Analysis 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. ## Factual 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. ## Aircraft - Registration: [N99811](https://openairdocs.org/aircraft/N99811), registered now, S/N 2434, built 1946 (OpenAirDocs) - Reported make and model: Engineering & Research Ercoupe 415-C - Registry model: [Engineering & Research ERCOUPE 415-C](https://openairdocs.org/model/engineering-research-ercoupe-415-c) (registry code 0420312) (OpenAirDocs) - Registry engine: [Continental A&C75 series](https://openairdocs.org/engine/continental-a-c75-series) (registry code 17005, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 2434 - Engines: Continental C85 85 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 1, 2006, 42 hours before - Departed: 45G, Brighton, MI - Destination: 45G - Airport: 45G, Brighton Airport, runway 22, 3,120 × 24 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 72; injuries: none; student; seat: left; flight hours: 103 total, 73 in this make and model, 56 as pilot in command, 3 in the last 90 days, 3 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 260° at 4 knots - Lowest ceiling: none - Temperature: 70 °F, dew point 28 °F - Altimeter: 30.22 inHg - Observed at: OZW, 10 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20070421017459A](https://openairdocs.org/incident/20070421017459A), Apr 21, 2007: Univar 415C, Brighton, MI, Substantial damage. (-23) On April 21, 2007 at 10:30 the pilot [privacy data omitted] (sport-student pilot) departed manipulating the controls of N99811 (Ercoupe) on a day VFR… ## Other investigations on N99811 (2) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB CEN09LA291](https://openairdocs.org/ntsb/CEN09LA291), May 12, 2009: Univair Ercoupe (N99811), Brighton, MI, substantial damage. Probable cause: The pilot's failure to attain the proper touchdown point, and his failure to initiate a go-around. - [NTSB CHI06LA281](https://openairdocs.org/ntsb/CHI06LA281), Jan 10, 2006: Univar Ercoupe (N99811), Howell, MI, substantial damage. Probable cause: The student pilot's improper landing flare and lack of total experience. From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.