What happened
The aircraft was engaged in an on-demand commercial cargo operation when it collided with runway barricades and a rut during the initial phase of takeoff. The incident occurred at night on a runway that had been officially closed to traffic. Despite the closure, the pilot initiated a takeoff attempt on this inactive surface.
The investigation
Examination of the operational context revealed significant safety failures regarding airport status awareness. The runway in question was not only physically barricaded but also had its lighting systems disabled to indicate its inactive status. Official records confirmed that the airfield authority had listed the runway as closed in the Notices to Airman (NOTAMs). Furthermore, this closure status was actively recorded and reflected on the airport's automated surface observing system, providing real-time data to pilots.
Findings
The primary factor leading to the incident was the pilot's decision to utilize a runway that was clearly marked as closed. The barricades placed across the surface served as a physical deterrent, yet the aircraft proceeded toward them. Upon visual contact with the obstacles, the pilot attempted to maneuver around the barricades, but the collision had already been initiated or was unavoidable given the proximity and speed. The failure to recognize the runway's closed status, despite it being documented in NOTAMs and reflected on automated systems, underscores a critical lapse in pre-flight planning and situational awareness.