What happened
On August 12, 2020, a Cessna 152, registration SP-KIW, was conducting a VFR flight from EPKA to EPML, with a subsequent destination of EPRZ. The aircraft was navigating via visual references as it lacked onboard GPS. Upon reaching the VFR PAPA waypoint near EPML, the pilot contacted AFIS to announce an intention to perform a convoy flight. The AFIS controller informed the pilot that runway 09 was in use and that a long straight-in approach was available.
After passing the JULIETT waypoint, the pilot executed a left turn and began following a traffic pattern path, but in the opposite direction of the established flow. During this maneuver, the pilot heard the ATIS for the neighboring airport, EPRZ, which reported runway 27 in use. At approximately 12:50 LMT, the pilot of SP-KIW positioned the aircraft on a straight-in approach for runway 27, while simultaneously reporting a straight-in approach for runway 09 via radio.
At that moment, another Cessma 152, registration SP-CAT, was departing from runway 09. The AFIS controller informed the pilot of SP-KIW that the runway was clear, even as SP-CAT was climbing toward 100 meters AGL. The pilot of SP-CAT observed the approaching SP-KIW and executed a left turn to avoid a collision. Upon noticing the runway 27 markings, the pilot of SP-KIW realized the error, announced the missed approach, and turned away from the runway.
The investigation
The PKBWL examined the flight paths, radio communications, and the pilot's navigation methods. The investigation focused on why the aircraft entered the pattern in the wrong direction and why the controller did not identify the incorrect flight path. The investigation also reviewed the impact of the pilot's decision to listen to the ATIS of a different airport during the approach phase.
Findings
- The primary cause of the near mid-air collision was the entry of SP-KIW into the runway 09 traffic pattern in the opposite direction of the established flow.
- The pilot's attention was diverted by listening to the ATIS for the adjacent airport (EPRZ), which reported runway 27 in use, contributing to the navigational error.
- The AFIS controller failed to notice that the aircraft was flying the traffic pattern in the incorrect direction.
Safety action
- The pilot of the involved aircraft was directed to complete a 6-hour stationary theoretical training course regarding flight regulations.
- A check flight was conducted to ensure the pilot did not exhibit difficulties in determining geographic directions.