Serious Incident Involving Piper Super Cub ZU-ITC at Karoo Gateway

Incident Overview and Flight Details On 4 August 2021 at approximately 0912Z, a Piper Super Cub with registration ZU-ITC was conducting a private repositioning flight from Krugersdorp Airfield (FAKR) to Robertson Airfield (FARS). The flight was intended to route via Welkom Airfield (FAWM), Tempe Airfield (FATP), and Beaufort West Airfield (FABW), now known as Karoo Gateway, for refueling. The aircraft was operated by a 60-year-old male pilot with 1,756.6 total flying hours and 10.1 hours on type, accompanied by one passenger. The aircraft had 10,651.8 total hours and was issued a special flight permit valid until 11 August 2021. ## Operational Context and Radio Communication At the time of the incident, clear weather conditions prevailed. Karoo Gateway had issued a Notice to Airmen (NOTAM) stating that the Aerodrome Flight Information Service (AFIS) was not operational and that Runway 12 was prohibited for all aircraft landings due to maintenance. The pilot confirmed awareness of this NOTAM. During the approach, the pilot attempted to establish contact with Karoo Radio on 125.60 MHz but received no reply. Subsequent attempts to contact the tower via the general flying area frequency (124.4 MHz), a passenger's telephone, and a portable radio on board were also unsuccessful. ## Approach, Go-Around, and Landing The pilot proceeded with a normal unmanned joining procedure on Runway 03, joining at 3,000 feet instead of the standard 2,000 feet to maintain a safety margin while searching for traffic. One other aircraft was identified in the circuit. The pilot descended to circuit height for a landing on Runway 03, which was favored by the wind. During the final approach, communication was successfully established, and the pilot was advised to go around. The pilot executed the go-around and was instructed to land on an alternative runway. The aircraft subsequently landed safely on Runway 35. The pilot noted that there were no markings or signage indicating that Runway 03 was closed. ## Post-Incident Findings and Safety Actions After shutdown, the pilot reported the radio issues to the tower. Troubleshooting revealed that the headset connection jack had corroded; cleaning the jack restored normal radio functionality. The aircraft was refueled and departed for Robertson Airfield, where it landed safely. The probable cause was identified as an attempt to land on a closed runway due to intermittent radio transmission and the non-availability of signage on the closed runway. A contributory factor was the failure to place required X signage on the closed runway, as mandated by SA-CATS Part 139.02.23.12. The investigation recommended that airfield management install visible signage on closed runways to warn pilots in accordance with regulatory requirements.