AN MLG ACR CREW MADE AN ALTDEV IN RESPONSE TO TCASII. NO TFC WAS SEEN VISUALLY OR ON RADAR. THE FAA IS INVESTIGATING THE INCIDENT.
Synopsis
AN MLG ACR CREW MADE AN ALTDEV IN RESPONSE TO TCASII. NO TFC WAS SEEN VISUALLY OR ON RADAR. THE FAA IS INVESTIGATING THE INCIDENT.
Narrative
ON THE FINAL ENRTE PHASE TO SMF FROM SAN; WE RECEIVED A TCASII TA AT AN ALT OF 11000 FT IN CRUISE. THE TFC SHOWED UP AT ABOUT 5 MI N OF OUR LOCATION AND SHOWED 300 FT BELOW. AT ABOUT 3 MI N WE RECEIVED A TCASII RA. THE TCASII RESOLUTION SHOWED THAT WE SHOULD CLB AT ABOUT 1200 FPM TO RESOLVE THE SITUATION. I CLBED AT ABOUT 1300 FPM TO ABOUT 11700 FT UNTIL WE WERE A COUPLE OF MI PAST THE TFC; THEN DSNDED TO 11000 FT. APCH SAID THEY DID NOT HAVE TFC IN THAT AREA. WE NEVER LOCATED THE TFC THAT TCASII SHOWED AS WE WERE APPROX 10 MI S OF SAC VOR ON THE STAR WHEN THE TCASII NOTIFIED US OF THE TFC. APCH WAS NOTIFIED OF A TCASII ALERT AND WAS TOLD WE WERE CLBING TO AVOID TFC. WHEN WE GOT ON THE GND; GND CTL GAVE US A NUMBER TO CALL APCH CTL AND THE CAPT WAS TOLD THEY WERE FILING AN ALTDEV ON US FOR CLBING ON TCASII INSTRUCTIONS. I DO NOT UNDERSTAND THE REASON FOR THE VIOLATION AS WE WERE FOLLOWING PROC. THERE NEEDS TO BE A CLR CUT PROC DEFINED BY THE FAA IN THESE CASES AS I'M SURE ITS NOT THE FIRST TIME THIS HAS HAPPENED AND IT WILL NOT BE THE LAST; EVEN BY MYSELF.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.