Narrative:

While 4 aircraft were inbound to phl on the BUNTS1 arrival, I noticed a limited data block 1200 code, climbing out of 7800 ft. I issued traffic to air carrier X, the first aircraft, saying traffic was 1 O'clock position, 7 mi wbound, type unknown, appears to be climbing out of 7800 ft. This aircraft was on a 1200 code, not being worked by any controller. The VFR aircraft continued to climb through 8000 and 9000 ft and higher. I issued traffic again to air carrier X. Since it appeared to be a definite head-on situation, I told the air carrier X to turn left if you don't have traffic in sight. He replied we don't have him but have him on TCASII. Without the left turn, they would have possibly hit or been very close to it. I then had to turn another aircraft to follow the first one and also avoid the VFR. The VFR aircraft came close to 3 aircraft, without calling for advisories. I then got air carrier X back on course and now had to issue hold for 4 aircraft. After it was over, the captain of air carrier X called our area to express his gratitude for my timely TA's and his concern that this VFR aircraft could be so close without being in communication with ATC. He stated that without the turn he took, it could have been a collision. He was very concerned about this VFR aircraft. I was too. The VFR aircraft called on west of lrp (on the wrong frequency) and was told by that controller that aircraft had to take evasive action. He was not too concerned. Supplemental information from acn 386359: while executing the BUNTS1 arrival to phl, at 11000 ft just east of lrp VOR, we received a TA from ZNY. The reported traffic was in our 1-2 O'clock position, 10 DME and at 8500 ft and climbing and closing (constant bearing, decreasing range). I searched visually but unable to see the conflicting traffic. Next the TCASII issued a TA. At this point the captain elected to deviate left (away) from the traffic. ATC then issued the same clearance just as I was about to transmit our deviation intentions (ATC cleared us to deviate as necessary to the left). Now a TCASII RA was issued. The captain responded immediately to the RA, a climb was made to 12300 ft. The TCASII RA at this point ceased. A clearance to descend and vector was then issued by ATC to rejoin the arrival, no further incidents occurred. We never had the other aircraft visually. Later on we were told that the other aircraft (a super king air) had us visually. TCASII saved 55 lives that day on our aircraft. For corrective action, the other aircraft should never have climbed through our altitude, period. There was an obvious misjudgment by the other aircraft crew on separation of aircraft. Another contributing factor was that the other aircraft was operating on a different ATC frequency. WX was not a factor. The actual closest point of intercept, may have been a lot less than 1.5 NM and 400 ft. I spent most of the time of this incident looking outside so to visually see the traffic conflict.

Google
 

Original NASA ASRS Text

Title: ARTCC RADAR CTLR ISSUED UNKNOWN TFC TO A DC9, THE DC9 FLC COULD NOT SEE THE TFC, HOWEVER, THEY RECEIVED A TCASII RA WHEN THE UNKNOWN TFC GOT CLOSER AND TOOK EVASIVE ACTION BY CLBING. THE CTLR ALSO ISSUED A TURN AWAY FROM THE OTHER ACFT.

Narrative: WHILE 4 ACFT WERE INBOUND TO PHL ON THE BUNTS1 ARR, I NOTICED A LIMITED DATA BLOCK 1200 CODE, CLBING OUT OF 7800 FT. I ISSUED TFC TO ACR X, THE FIRST ACFT, SAYING TFC WAS 1 O'CLOCK POS, 7 MI WBOUND, TYPE UNKNOWN, APPEARS TO BE CLBING OUT OF 7800 FT. THIS ACFT WAS ON A 1200 CODE, NOT BEING WORKED BY ANY CTLR. THE VFR ACFT CONTINUED TO CLB THROUGH 8000 AND 9000 FT AND HIGHER. I ISSUED TFC AGAIN TO ACR X. SINCE IT APPEARED TO BE A DEFINITE HEAD-ON SIT, I TOLD THE ACR X TO TURN L IF YOU DON'T HAVE TFC IN SIGHT. HE REPLIED WE DON'T HAVE HIM BUT HAVE HIM ON TCASII. WITHOUT THE L TURN, THEY WOULD HAVE POSSIBLY HIT OR BEEN VERY CLOSE TO IT. I THEN HAD TO TURN ANOTHER ACFT TO FOLLOW THE FIRST ONE AND ALSO AVOID THE VFR. THE VFR ACFT CAME CLOSE TO 3 ACFT, WITHOUT CALLING FOR ADVISORIES. I THEN GOT ACR X BACK ON COURSE AND NOW HAD TO ISSUE HOLD FOR 4 ACFT. AFTER IT WAS OVER, THE CAPT OF ACR X CALLED OUR AREA TO EXPRESS HIS GRATITUDE FOR MY TIMELY TA'S AND HIS CONCERN THAT THIS VFR ACFT COULD BE SO CLOSE WITHOUT BEING IN COM WITH ATC. HE STATED THAT WITHOUT THE TURN HE TOOK, IT COULD HAVE BEEN A COLLISION. HE WAS VERY CONCERNED ABOUT THIS VFR ACFT. I WAS TOO. THE VFR ACFT CALLED ON W OF LRP (ON THE WRONG FREQ) AND WAS TOLD BY THAT CTLR THAT ACFT HAD TO TAKE EVASIVE ACTION. HE WAS NOT TOO CONCERNED. SUPPLEMENTAL INFO FROM ACN 386359: WHILE EXECUTING THE BUNTS1 ARR TO PHL, AT 11000 FT JUST E OF LRP VOR, WE RECEIVED A TA FROM ZNY. THE RPTED TFC WAS IN OUR 1-2 O'CLOCK POS, 10 DME AND AT 8500 FT AND CLBING AND CLOSING (CONSTANT BEARING, DECREASING RANGE). I SEARCHED VISUALLY BUT UNABLE TO SEE THE CONFLICTING TFC. NEXT THE TCASII ISSUED A TA. AT THIS POINT THE CAPT ELECTED TO DEVIATE L (AWAY) FROM THE TFC. ATC THEN ISSUED THE SAME CLRNC JUST AS I WAS ABOUT TO XMIT OUR DEV INTENTIONS (ATC CLRED US TO DEVIATE AS NECESSARY TO THE L). NOW A TCASII RA WAS ISSUED. THE CAPT RESPONDED IMMEDIATELY TO THE RA, A CLB WAS MADE TO 12300 FT. THE TCASII RA AT THIS POINT CEASED. A CLRNC TO DSND AND VECTOR WAS THEN ISSUED BY ATC TO REJOIN THE ARR, NO FURTHER INCIDENTS OCCURRED. WE NEVER HAD THE OTHER ACFT VISUALLY. LATER ON WE WERE TOLD THAT THE OTHER ACFT (A SUPER KING AIR) HAD US VISUALLY. TCASII SAVED 55 LIVES THAT DAY ON OUR ACFT. FOR CORRECTIVE ACTION, THE OTHER ACFT SHOULD NEVER HAVE CLBED THROUGH OUR ALT, PERIOD. THERE WAS AN OBVIOUS MISJUDGMENT BY THE OTHER ACFT CREW ON SEPARATION OF ACFT. ANOTHER CONTRIBUTING FACTOR WAS THAT THE OTHER ACFT WAS OPERATING ON A DIFFERENT ATC FREQ. WX WAS NOT A FACTOR. THE ACTUAL CLOSEST POINT OF INTERCEPT, MAY HAVE BEEN A LOT LESS THAN 1.5 NM AND 400 FT. I SPENT MOST OF THE TIME OF THIS INCIDENT LOOKING OUTSIDE SO TO VISUALLY SEE THE TFC CONFLICT.

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.