Narrative:

I was working local control at a VFR control tower training a deviation. The approach control facility having IFR jurisdiction over my facility passed an medium large transport scheduled air carrier inbound from the east on a visibility approach for our southeast/northwest runway. The aircraft transferred communication from the approach control facility to my frequency, approximately 10 mi east, and was instructed to make a straight-in approach. When air carrier X was on a 5-MI final, a VFR small aircraft, on initial contact, reported over a VFR reporting point located 15 mi sse of airport. Air carrier X immediately reported traffic off his right wing and made an evasive turn to the left to avoid small aircraft Y. The aircraft were approximately 3-4 mi from airport. After air carrier X was clear of small aircraft Y, he turned back to the airport and landed west/O incident. Small aircraft Y admittedly reported over an incorrect VFR reporting point for his actual position. He may already have been inside the air traffic area prior to initial call. Result: air carrier X made evasive turn to avoid colliding with VFR small aircraft Y. Solution: my facility lacks the necessary operational equipment needed to safely separate IFR traffic and VFR traffic. The approach control facility having jurisdiction of IFR traffic for my facility has no responsibility to separate VFR traffic from IFR traffic. In this case, the approach controller never advised me air carrier X had traffic to contend with, nor was it his legal responsibility to do so. My facility is in desperate need of d-brite radar. With the equipment, I could have easily and necessarily instructed the air carrier X to make the needed turns to avoid the VFR traffic, and could have provided him with traffic advisories well in advance.

Related reports:

Google
 

Original NASA ASRS Text

Title: SMA Y ENTERED ATW CTL ZONE WITHOUT CLRNC. PLT DEVIATION.

Narrative: I WAS WORKING LCL CTL AT A VFR CTL TWR TRNING A DEV. THE APCH CTL FAC HAVING IFR JURISDICTION OVER MY FAC PASSED AN MLG SCHEDULED ACR INBND FROM THE E ON A VIS APCH FOR OUR SE/NW RWY. THE ACFT TRANSFERRED COM FROM THE APCH CTL FAC TO MY FREQ, APPROX 10 MI E, AND WAS INSTRUCTED TO MAKE A STRAIGHT-IN APCH. WHEN ACR X WAS ON A 5-MI FINAL, A VFR SMA, ON INITIAL CONTACT, RPTED OVER A VFR RPTING POINT LOCATED 15 MI SSE OF ARPT. ACR X IMMEDIATELY RPTED TFC OFF HIS RIGHT WING AND MADE AN EVASIVE TURN TO THE LEFT TO AVOID SMA Y. THE ACFT WERE APPROX 3-4 MI FROM ARPT. AFTER ACR X WAS CLR OF SMA Y, HE TURNED BACK TO THE ARPT AND LANDED W/O INCIDENT. SMA Y ADMITTEDLY RPTED OVER AN INCORRECT VFR RPTING POINT FOR HIS ACTUAL POS. HE MAY ALREADY HAVE BEEN INSIDE THE ATA PRIOR TO INITIAL CALL. RESULT: ACR X MADE EVASIVE TURN TO AVOID COLLIDING WITH VFR SMA Y. SOLUTION: MY FAC LACKS THE NECESSARY OPERATIONAL EQUIP NEEDED TO SAFELY SEPARATE IFR TFC AND VFR TFC. THE APCH CTL FAC HAVING JURISDICTION OF IFR TFC FOR MY FAC HAS NO RESPONSIBILITY TO SEPARATE VFR TFC FROM IFR TFC. IN THIS CASE, THE APCH CTLR NEVER ADVISED ME ACR X HAD TFC TO CONTEND WITH, NOR WAS IT HIS LEGAL RESPONSIBILITY TO DO SO. MY FAC IS IN DESPERATE NEED OF D-BRITE RADAR. WITH THE EQUIP, I COULD HAVE EASILY AND NECESSARILY INSTRUCTED THE ACR X TO MAKE THE NEEDED TURNS TO AVOID THE VFR TFC, AND COULD HAVE PROVIDED HIM WITH TFC ADVISORIES WELL IN ADVANCE.

Data retrieved from NASA's ASRS site as of August 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.