SMA HAD NMAC WITH ANOTHER SMA; SAYS TRAFFIC CALLS WERE INCORRECT; BOTH ACFT VFR.
Synopsis
SMA HAD NMAC WITH ANOTHER SMA; SAYS TRAFFIC CALLS WERE INCORRECT; BOTH ACFT VFR.
Narrative
ENRTE FROM CHARLIE BAKER ARPT (2M8) TO W MEMPHIS ARPT (AWM) RECEIVING TFC ADVISORIES FROM MEMPHIS RADAR ON 119.1. I WAS SQUAWKING ON XXXX MODE C. ALL TFC ADVISORIES DURING THIS FLT AND THE RETURN FLT WERE BEING CALLED OUT TO ME AS COMING FROM THE OPPOSITE DIRECTION FROM WHICH THEY WERE ACTUALLY COMING FROM. THIS SPECIFIC INCIDENT INVOLVED MY SMA X AND A CONFLICTING SMA Y. THE CONFLICTING SMA Y WAS CALLED OUT TO ME AS TFC AT 11 O'CLOCK; ALT UNKNOWN. I SCANNED MY 11 O'CLOCK POS; SAW NO TFC AND THEN SCANNED MY 9; 12; 1 AND 3 O'CLOCK POSITIONS. AT MY 2 O'CLOCK POS I SPOTTED MY TFC MOVING FROM THE 3 TO THE 9 O'CLOCK POS. WITHIN 3 SECS; THE CONFLICTING TFC CROSSED MY 12 O'CLOCK; SLIGHTLY HIGH (APPROX 400'). I MENTIONED THIS TO THE CTLR AND HE STATED THAT MY TFC HAD MOVED TO MY 1 O'CLOCK POS WHERE; IN FACT; IT WAS MOVING PAST THE 11 O'CLOCK POS. IN SUMMARY; A POTENTIAL MIDAIR COLLISION OCCURRED BECAUSE OF AN INCORRECT TFC CALL. TFC ACTUALLY COMING FROM MY RIGHT TO LEFT WAS CALLED AS COMING FROM MY LEFT TO RIGHT; THEREBY DISTRACTING MY SCAN FOR A FEW CRITICAL SECS.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.