Date: 201606
Local time of day: 1201-1800
Location: RSW.TRACON, FL
Flight conditions: VMC
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZMA
ATC / advisory: TRACON RSW
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Second reporter function: Captain; Pilot Flying
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: ATC Equipment / Nav Facility / Buildings; Aircraft
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: I was working Controller In Charge. The controller was working East and South combined. We were in the process of changing runways. Aircraft X was our last departure off of runway 6 before we switched to runway 24. As I switched my map; I noticed a VFR target along the departure corridor at 10;500 feet. I asked East if they saw the traffic. At the time; East was in the process of switching Aircraft X; but heard me and kept the aircraft. When I went over to the scope; the VFR target wasn't showing up with an altitude. It only showed 'rdr' [radar]. I told East the traffic was at 10;500 feet. Traffic was called. The controller told Aircraft X to turn left 20 degrees. The pilot seemed to slowly turn. East had APREQ (Approval Request) a higher altitude with ZMA to 15;000 feet to top the aircraft.As the two targets converged; Aircraft X reported that he was responding to a RA. He then told us that target never showed up on his TCAS until the RA and he thought the controller was calling a different target. Closest proximity between the VFR aircraft and Aircraft X was 0.2 miles and 0 feet.We need to discover why this target wasn't showing up properly on the radar scope and the pilot's TCAS; but it was showing up properly on the [map]. Controller should have given more of a drastic turn and possibly stopped Aircraft X below the target until it was apparent the targets would miss.


Second narrative: While on climb out from RSW; at approximately 10;000 feet; ATC asked us to turn left 15 (?) degrees for traffic. While in the turn; we responded to ATC we had an indication from the TCAS. Seconds later; ATC asked us to turn further left for the traffic. The initial traffic we saw on TCAS was a different aircraft. We were at approximately 10;500 feet. I caught just a glimpse of the traffic visually while turning and climbing; then glanced at the TCAS - we now had the correct traffic on the screen. He appeared to be within a mile and 500 - 700 feet from us; exiting a cloud and traveling to our right. I called him out to the FO as well while simultaneously receiving a TCAS RA to maintain vertical speed. FO let ATC know of the RA. It was somewhat disconcerting to have the conflict aircraft appear so late. No further conflict of RAs occurred. My apologies for the tardiness of this report.As stated; we were complying with ATC instructions for the traffic; so ATC knew of his location to us. The only issue we had was how close he seemed once we had a visual on him. The traffic literally did not show on TCAS until we were quite close. ATC did not say anything concerning loss of separation; but we filed this just in case and to state the lack of TCAS information until quite late in the maneuver.


Synopsis: An Air Traffic Controller reported that a VFR aircraft did not display on the radar display; and an air carrier departure received an RA on the VFR target as the Controller was issuing a vector to avoid.