Gustavus, OH, USA
N105MK
DIAMOND AIRCRAFT IND INC DA 40
The private pilot was maneuvering to land at the destination airport after a cross-country flight in dark night, visual meteorological conditions. The pilot reported that he became disoriented as he orbited the airport waiting for the airport manager to turn on the runway lights, which resulted in him believing that he was on final approach to runway 1 instead of runway 19. The pilot stated that, during final approach, he incorrectly identified a crossing road that he believed was about 3/4 mile south of the runway 1 approach threshold; however, the road he observed was about 1 mile north of the airport. The pilot stated that he and his passenger suddenly saw tree branches appear as the airplane descended on final approach. The pilot immediately increased engine power and airplane pitch in an attempt to avoid the trees, but the right wing impacted a tree, and the airplane subsequently impacted terrain about 1/2 mile north of runway 19. The pilot reported that there were no mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot had previously flown 7 hours during nighttime conditions; however, he had not flown at night within the 238 days preceding the accident. According to federal regulations, pilots are prohibited from acting as pilot-in-command with passengers at night unless they have completed three night takeoffs and three night landings within the previous 90 days. An ancillary benefit of pilots maintaining their regulatory night flight currency is that it demonstrates their having an adequate level of proficiency of night flight operations on a recurring basis. The pilot's lack of recent night flight experience likely contributed to his becoming disorientated while maneuvering in the airport traffic pattern, the airplane descending below a normal approach path, and the collision with trees.
On October 16, 2017, about 2112 eastern daylight time, a Diamond Aircraft Industries DA40 single-engine airplane, N105MK, collided with trees and terrain while on final approach to Gustavus Airport (OH33), Gustavus, Ohio. The private pilot was seriously injured, his passenger was not injured, and the airplane sustained substantial damage. The airplane was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations (CFR) Part 91 without a flight plan. Night visual meteorological conditions prevailed for the cross-country flight that departed at 1730 central daylight time from Bult Field Airport (C56), Monee, Illinois.The pilot reported that he had originally planned to land at Northeast Ohio Regional Airport (HZY), Ashtabula, Ohio; however, as the flight approached HZY he was unable to activate the airport's runway lights using the designated common traffic advisory frequency. The pilot subsequently diverted to OH33 and telephoned the airport manager to have the runway lights turned on. The pilot reported that he became disoriented as he orbited the airport waiting for the runway lights to be turned on, which resulted in him believing that he was on final approach to runway 1 instead of runway 19. The pilot stated that during final approach he incorrectly identified a crossing road that he believed was about 3/4 mile south of runway 1 approach threshold; however, the road he observed was about 1 mile north of the airport. The pilot stated that he and his passenger suddenly saw tree branches appear as the airplane descended on final approach. The pilot immediately increased engine power and airplane pitch in attempt to avoid the trees, but the right wing impacted a tree and the airplane subsequently impacted terrain about 1/2 mile north of runway 19. The right wing, aft fuselage, and empennage sustained substantial damage during the impact sequence. The pilot reported that there were no mechanical failures or malfunctions with the airplane that would have precluded normal operation. At 2051, the Youngstown-Warren Regional Airport automated surface observing system located about 12 miles south of the accident site reported: calm wind, a clear sky, 10 miles surface visibility, temperature 5°C, dew point 0°C, and an altimeter setting of 30.28 inches of mercury. The United States Naval Observatory data indicated that the sunset and end of civil twilight at the accident site were at 1840 and 1908, respectively. Moon transit, the time at which the moon is highest in the sky, occurred at 1051 and the moonset was at 1726. Additionally, the accident site was located in a sparsely populated area with minimal illumination from ground light sources. As such, dark nighttime conditions likely existed at the time of the accident. The pilot reported that he had previously flown 7 hours during nighttime conditions; however, he had not flown at night within the 90 days preceding the accident. He reported that his most recent night flight was completed on February 20, 2017, during which he made a night landing on runway 1 at OH33. According to federal regulation 14 CFR Part 61.57(b), pilots are prohibited from acting as pilot-in-command with passengers at night unless they have completed 3 night takeoffs and 3 night landings within the previous 90 days.
The pilot’s geographic disorientation while maneuvering in the airport traffic pattern in dark night conditions, which resulted in the airplane descending below a normal approach path and a collision with trees. Contributing to the accident was the pilot's lack of recent night flight experience.
Source: NTSB Aviation Accident Database
Aviation Accidents App
In-Depth Access to Aviation Accident Reports
