Casualties unknown

Ayres S2R-T34 noses over after landing on closed runway at Bethlehem (ZS-LUZ)

ZA

On May 18, 2026, an aircraft (registration ZS-LUZ) was involved in an aviation accident near ZA. Investigators recorded the probable cause as: The pilot landed on a runway that was closed for maintenance despite acknowledging the relevant NOTAM, causing the aircraft to enter soft ground and nose over. This summary draws on records from the South African Civil Aviation Authority (SACAA) Accident and Incident Investigations Division.

Sourcesthe South African Civil Aviation Authority (SACAA) Accident and Incident Investigations DivisionPrimary reportUpdated 2026-09-13Data APIEditorial standards

An Ayres S2R-T34 registered ZS-LUZ nosed over at Bethlehem Airfield after the pilot landed on a grass runway that was closed for maintenance, resulting in minor damage but no injuries.

What happened

On 18 May 2026, a private flight departed Bothaville Airfield (FABO) bound for Bethlehem Airfield (FABM) in the Free State province. The Ayres S2R-T34, registered ZS-LUZ, operated under visual meteorological conditions. After take-off and climb, the pilot commenced an approach to land on Runway 13. This grass runway was temporarily closed for maintenance works. During the landing roll, the aircraft skidded off the paved surface onto soft ground beyond the runway end. The main landing gear sank into the terrain, causing the nose to pitch down and the propeller to strike the ground. The aircraft subsequently nosed over, sustaining minor damage. The pilot exited the aircraft uninjured.

The investigation — what SACAA AIID examined and established

The inquiry reviewed the operational context and regulatory compliance at the aerodrome. It was established that a Notice to Airmen (NOTAM) had been issued alerting pilots to the closure of Runway 13/31 due to maintenance, with the closure period extended multiple times due to weather and work delays. The pilot acknowledged receiving this NOTAM via email prior to the flight. However, physical runway closure markings or signage were not displayed on the airfield at the time of the incident. These markers were only installed after the event occurred. The investigation noted that while Runway 11/29 remained operational, the absence of visual warnings on the closed runway contributed to the situation.

Findings

The primary cause was the pilot's decision to land on a runway that was officially closed for maintenance, despite having received and acknowledged the relevant NOTAM. This action led the aircraft onto soft ground, causing the gear to sink and the airframe to nose over. A significant contributing factor was the failure of the airfield operator to display required physical closure markings or signage, which contravened South African Civil Aviation Technical Standards (SA-CATS) 139.02.23, Subpart 12.

Safety action

SACAA AIID issued safety reminders for pilots to rigorously review and comply with all applicable NOTAMs during pre-flight planning and before landing. Additionally, the airfield operator was directed to review its procedures to ensure that closed runways are clearly marked in strict compliance with regulatory requirements.

Probable cause

The pilot landed on a runway that was closed for maintenance despite acknowledging the relevant NOTAM, causing the aircraft to enter soft ground and nose over. This was contributed to by the non-display of required runway closure signage or markings at the aerodrome.