Narrative:

I'm a fully qualified controller working phl approach and was taking a briefing on the radar position called yardley high. This sector handles arrival jet and turboprop inbnds to phl from ny ARTCC over lrp and etx vortacs, plus overflt traffic from ny approach. After assuming the position, there were approximately 7 aircraft on frequency. 3 aircraft were holding, 3 aircraft on radar vectors, and 1 overflt. As I was vectoring aircraft into an approach sequence (about 10 mins on position) I was scanning strips and realized I had one strip too many. I scanned the final controllers sequence and didn't see medium large transport X, also called tower to see if medium large transport X had already landed (it hadn't). I called back previous controller to find where medium large transport X was at and he responded that medium large transport X was on an 070 degree heading during briefing. I then called medium large transport X on frequency. He responded and I sought his position. His reply was 27 mi east of lga VORTAC. I immediately called metropolitan sector at ny approach to relay position and block altitude 8000' east of lga. After advising supervisor, I continued to seek medium large transport X's position, since metropolitan sector advised no target was shown. Medium large transport X replied once again he was 21 mi east of lga, then again he replied 12 mi east of lga. All this while he was tracking eastbound. After an identify of his transponder was issued, metropolitan sector advised they had a target east of lga and issued a frequency for me to issue medium large transport X to switch for radar vectors back to phl. I do accept responsibility, some of factors possible to aircraft leaving my sector were: 1) medium large transport X transponder failing and a/north dropping of scope, 2) better vigilance on my part to scan radar scope and strips to update information.

Google
 

Original NASA ASRS Text

Title: RELIEVING CTLR WAS MISSING AN ACFT, IN CHECKING FOUND ACFT WAS IN ADJACENT APCH TCA WITHOUT COORD.

Narrative: I'M A FULLY QUALIFIED CTLR WORKING PHL APCH AND WAS TAKING A BRIEFING ON THE RADAR POS CALLED YARDLEY HIGH. THIS SECTOR HANDLES ARR JET AND TURBOPROP INBNDS TO PHL FROM NY ARTCC OVER LRP AND ETX VORTACS, PLUS OVERFLT TFC FROM NY APCH. AFTER ASSUMING THE POS, THERE WERE APPROX 7 ACFT ON FREQ. 3 ACFT WERE HOLDING, 3 ACFT ON RADAR VECTORS, AND 1 OVERFLT. AS I WAS VECTORING ACFT INTO AN APCH SEQUENCE (ABOUT 10 MINS ON POS) I WAS SCANNING STRIPS AND REALIZED I HAD ONE STRIP TOO MANY. I SCANNED THE FINAL CTLRS SEQUENCE AND DIDN'T SEE MLG X, ALSO CALLED TWR TO SEE IF MLG X HAD ALREADY LANDED (IT HADN'T). I CALLED BACK PREVIOUS CTLR TO FIND WHERE MLG X WAS AT AND HE RESPONDED THAT MLG X WAS ON AN 070 DEG HDG DURING BRIEFING. I THEN CALLED MLG X ON FREQ. HE RESPONDED AND I SOUGHT HIS POS. HIS REPLY WAS 27 MI E OF LGA VORTAC. I IMMEDIATELY CALLED METRO SECTOR AT NY APCH TO RELAY POS AND BLOCK ALT 8000' E OF LGA. AFTER ADVISING SUPVR, I CONTINUED TO SEEK MLG X'S POS, SINCE METRO SECTOR ADVISED NO TARGET WAS SHOWN. MLG X REPLIED ONCE AGAIN HE WAS 21 MI E OF LGA, THEN AGAIN HE REPLIED 12 MI E OF LGA. ALL THIS WHILE HE WAS TRACKING EBND. AFTER AN IDENT OF HIS XPONDER WAS ISSUED, METRO SECTOR ADVISED THEY HAD A TARGET E OF LGA AND ISSUED A FREQ FOR ME TO ISSUE MLG X TO SWITCH FOR RADAR VECTORS BACK TO PHL. I DO ACCEPT RESPONSIBILITY, SOME OF FACTORS POSSIBLE TO ACFT LEAVING MY SECTOR WERE: 1) MLG X XPONDER FAILING AND A/N DROPPING OF SCOPE, 2) BETTER VIGILANCE ON MY PART TO SCAN RADAR SCOPE AND STRIPS TO UPDATE INFO.

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.