ASN Wikibase Occurrence # 242626
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Saturday 19 September 2020 |
| Time: | 06:38 |
| Type: |  Van's RV-9A |
| Owner/operator: | Private |
| Registration: | N94KJ |
| MSN: | 90322 |
| Year of manufacture: | 2006 |
| Total airframe hrs: | 395 hours |
| Engine model: | Lycoming IO320-D1A |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Ottawa Executive Airport (Z98), Zeeland, MI -
 United States of America
|
| Phase: | Initial climb |
| Nature: | Private |
| Departure airport: | Ottawa Executive Airport, MI (Z98) |
| Milton Airport, WV (12V) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot departed under visual flight rules (VFR) from a rural airport during dark night, VFR conditions. After climbing toward the destination for about 2 minutes, the pilot turned back to the airport and flew a visual approach. The airplane’s flight track was consistent with a go-around near the runway threshold, likely due to excessive airspeed, followed by a climb toward the downwind leg of the traffic pattern for the opposite runway. On an approximate left base leg, the airplane decelerated to stall speed and entered a right spin that continued until ground impact. The disposition of the wreckage was consistent with a low forward speed indicative of a stalled condition.
Two weeks before the accident, the airplane’s attitude heading reference system (AHRS) failed during a daytime flight. The pilot landed uneventfully by referencing the airplane’s backup (unlit) flight instruments located on the instrument panel’s far right side. After troubleshooting the AHRS failure, the pilot made repairs to a circuit card that involved intricate soldering of a capacitor and two diodes. The accident occurred on the second flight after this repair.
Examination revealed no engine or flight control anomalies. Fire damage precluded assessment of avionics anomalies. His disease placed him at increased risk of a sudden impairing or incapacitating cardiac event. It is possible that the pilot was experiencing symptoms of a heart-related medical event and that may have been the reason for his attempt to return to the airport. Furthermore, symptoms of such an event might have impaired his performance while maneuvering. However, there is no specific evidence that a such an event occurred and a systems failure involving the AHRS repair provides a reasonable alternate explanation for the pilot’s attempted return.
In such a scenario, challenges related to the failure and the dark conditions might explain his loss of control, even without impairment. Thus, whether the pilot’s severe coronary artery disease contributed to the accident could not be determined.
The pilot had not flown the accident airplane at night and his most recent night landing was about 5 years before the accident. The pilot’s lack of recent night experience likely contributed to his poor airspeed control during the two attempted approaches and the subsequent loss of aircraft control.
Probable Cause: The pilot’s failure to maintain airspeed during a visual approach in dark night conditions, which resulted in an aerodynamic stall and loss of airplane control. Contributing to the accident was the pilot’s lack of recent flight experience at night.
Accident investigation:
 |
|
Sources:
https://www.mlive.com/news/2020/09/2-dead-in-ottawa-county-plane-crash.html
https://www.google.com/amp/s/www.woodtv.com/news/ottawa-county/breakingplane-crash-in-zeeland-township/amp/
https://www.woodtv.com/news/ottawa-county/breakingplane-crash-in-zeeland-township/
NTSB
Location
Images:
Photo: NTSB
Media:
A closer look at the plane crash that left two people dead in Zeeland Township. A deputy from the Ottawa County Sheriff’s Office told me that the FAA’s investigation will provide answers as to why this happened, which could come any time. @WOODTV pic.twitter.com/ixQhFKEZ8h
— John Domol (@JohnnyDomol) September 19, 2020
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 19-Sep-2020 12:13 | Captain Adam | Added |
| 19-Sep-2020 12:36 | RobertMB | Updated [Time, Total fatalities, Total occupants, Other fatalities, Location, Phase, Nature, Departure airport, Source, Narrative] |
| 19-Sep-2020 14:05 | Geno | Updated [Location, Source] |
| 19-Sep-2020 16:51 | viking | Updated [Total fatalities, Total occupants, Other fatalities, Departure airport, Source, Damage] |
| 19-Sep-2020 16:53 | harro | Updated [Aircraft type, Registration, Cn, Operator, Other fatalities, Source, Embed code, Narrative] |
| 19-Sep-2020 17:56 | RobertMB | Updated [Time, Location, Phase, Nature, Departure airport, Source, Embed code, Narrative] |
| 19-Sep-2020 17:59 | RobertMB | Updated [Operator, Location, Narrative] |
| 19-Sep-2020 18:17 | Captain Adam | Updated [Narrative] |
| 22-Jun-2022 22:41 | Captain Adam | Updated [Time, Location, Phase, Destination airport, Source, Narrative, Category, Accident report, Photo] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation