Narrative:

I was working local control and had several aircraft in my pattern when luke RAPCON (our approach control facility) called on the land line and said that my aircraft in the west pattern were about 1 mi inside luke's airspace when they turned right base. When given this message by flight data, I said all my aircraft are flying normal patterns and according to my radar were well within my airspace. We're a level ii VFR tower but we have a d-brite display in the cabin attendant. During this exchange, small aircraft X called inbound from the west and I instructed him to make right traffic for runway 21. Luke RAPCON again called several more times about my aircraft and, although my aircraft were all flying normal patterns, I decided to stop all touch-and-go operations and make all aircraft turn an early base until the airspace discrepancy was cleared up. (Note -- luke's air traffic area was closed during this time for a demonstration by the blue angels aerobatic team). I was occupied with separating all my aircraft on the runway and in my pattern when small aircraft X again called and asked if I was talking to a small aircraft Y in his area. I replied that I wasn't. I looked at the d-brite and saw a target merge with my inbound aircraft. Bother were at 2000 MSL. The other aircraft was showing a call sign of Y and had a blinking symbol next to it indicating this aircraft was being handled by luke RAPCON. My inbound small aircraft X reported a near miss with small aircraft Y of about 300 ft. Flight data called luke and reported this but the only response was 'oh, okay.' luke switched the small aircraft Y to my frequency and I gave him landing instructions and clearance. This all happened outside my airspace and I believe the contributing factors were the approach control's loss of separation with an IFR/VFR aircraft and the VFR pilot's lack of awareness of other aircraft.

Related reports:

Google
 

Original NASA ASRS Text

Title: SMA X HAD A NMAC WITH SMA Y. SEE AND AVOID CONCEPT.

Narrative: I WAS WORKING LCL CTL AND HAD SEVERAL ACFT IN MY PATTERN WHEN LUKE RAPCON (OUR APCH CTL FAC) CALLED ON THE LAND LINE AND SAID THAT MY ACFT IN THE W PATTERN WERE ABOUT 1 MI INSIDE LUKE'S AIRSPACE WHEN THEY TURNED R BASE. WHEN GIVEN THIS MESSAGE BY FLT DATA, I SAID ALL MY ACFT ARE FLYING NORMAL PATTERNS AND ACCORDING TO MY RADAR WERE WELL WITHIN MY AIRSPACE. WE'RE A LEVEL II VFR TWR BUT WE HAVE A D-BRITE DISPLAY IN THE CAB. DURING THIS EXCHANGE, SMA X CALLED INBOUND FROM THE W AND I INSTRUCTED HIM TO MAKE R TFC FOR RWY 21. LUKE RAPCON AGAIN CALLED SEVERAL MORE TIMES ABOUT MY ACFT AND, ALTHOUGH MY ACFT WERE ALL FLYING NORMAL PATTERNS, I DECIDED TO STOP ALL TOUCH-AND-GO OPS AND MAKE ALL ACFT TURN AN EARLY BASE UNTIL THE AIRSPACE DISCREPANCY WAS CLRED UP. (NOTE -- LUKE'S ATA WAS CLOSED DURING THIS TIME FOR A DEMONSTRATION BY THE BLUE ANGELS AEROBATIC TEAM). I WAS OCCUPIED WITH SEPARATING ALL MY ACFT ON THE RWY AND IN MY PATTERN WHEN SMA X AGAIN CALLED AND ASKED IF I WAS TALKING TO A SMA Y IN HIS AREA. I REPLIED THAT I WASN'T. I LOOKED AT THE D-BRITE AND SAW A TARGET MERGE WITH MY INBOUND ACFT. BOTHER WERE AT 2000 MSL. THE OTHER ACFT WAS SHOWING A CALL SIGN OF Y AND HAD A BLINKING SYMBOL NEXT TO IT INDICATING THIS ACFT WAS BEING HANDLED BY LUKE RAPCON. MY INBOUND SMA X RPTED A NEAR MISS WITH SMA Y OF ABOUT 300 FT. FLT DATA CALLED LUKE AND RPTED THIS BUT THE ONLY RESPONSE WAS 'OH, OKAY.' LUKE SWITCHED THE SMA Y TO MY FREQ AND I GAVE HIM LNDG INSTRUCTIONS AND CLRNC. THIS ALL HAPPENED OUTSIDE MY AIRSPACE AND I BELIEVE THE CONTRIBUTING FACTORS WERE THE APCH CTL'S LOSS OF SEPARATION WITH AN IFR/VFR ACFT AND THE VFR PLT'S LACK OF AWARENESS OF OTHER ACFT.

Data retrieved from NASA's ASRS site as of July 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.