Narrative:

I was working the lga departure position. Aircraft #1, a PA31/right, departing frg, issued climb clearance to 8000 ft by jfk departure. I worked the aircraft climbing out of 5300 ft. I turned the aircraft left, heading 320 degrees, at approximately XX58 local. Air carrier #2, an MD80, departed lga runway 4. I should work this aircraft within 1 mi of departure. I made contact with air carrier #2, level at 5000, approximately 6-7 mi northeast of lga VOR. I radar idented aircraft and climbed to 7000 ft and turned left heading 320 degrees at approximately XX59 local. Air carrier #3, a 757/right, departed lga runway 4. I worked air carrier #3 leaving 1300 ft, idented, issued climb to 4000 ft and left turn heading 320 degrees. Traffic at 5000 ft was crossing, heading ese. When air carrier #3 was clear of the 5000 ft traffic, I issued climb to 7000 ft. At some point I turned air carrier #3 left, heading 280 degrees, thinking that I had climbed to 15000 ft. I became distracted by coordination regarding the 5000 ft traffic. I looked at scope and then strip to confirm what I had done -- 7000 ft issued to both aircraft. I issued traffic and climb to air carrier #2. Air carrier #2 advised he had air carrier #3 in sight. I then issued traffic to air carrier #3. He also advised he had air carrier #2 in sight. Air carrier #2 passed behind air carrier #3 at 7900 ft, climbing. At some point a computer dupe indicated that air carrier #2 leveled at 7000 ft and 1 3/4 mi to air carrier #3's left. At this point air carrier #3 was at 6400 ft, climbing. Both aircraft were equipped with TCASII (TA and collision avoidance system) and the computer system at new york TRACON has a collision avoidance alarm. No alarm, nor did either pilot advise of a resolution. 2 possible causes, other than the obvious -- the tower was late in their communication changes, third in less than 10 mins. This irritated me, and had set plan regarding air carrier #2 to climb and turn on contact. I did not adjust to the situation. Had handoff person, but I involved myself in something he could have handled, hence distracted!

Related reports:

Google
 

Original NASA ASRS Text

Title: OPERROR.

Narrative: I WAS WORKING THE LGA DEP POS. ACFT #1, A PA31/R, DEPARTING FRG, ISSUED CLB CLRNC TO 8000 FT BY JFK DEP. I WORKED THE ACFT CLBING OUT OF 5300 FT. I TURNED THE ACFT L, HDG 320 DEGS, AT APPROX XX58 LCL. ACR #2, AN MD80, DEPARTED LGA RWY 4. I SHOULD WORK THIS ACFT WITHIN 1 MI OF DEP. I MADE CONTACT WITH ACR #2, LEVEL AT 5000, APPROX 6-7 MI NE OF LGA VOR. I RADAR IDENTED ACFT AND CLBED TO 7000 FT AND TURNED L HDG 320 DEGS AT APPROX XX59 LCL. ACR #3, A 757/R, DEPARTED LGA RWY 4. I WORKED ACR #3 LEAVING 1300 FT, IDENTED, ISSUED CLB TO 4000 FT AND L TURN HDG 320 DEGS. TFC AT 5000 FT WAS XING, HDG ESE. WHEN ACR #3 WAS CLR OF THE 5000 FT TFC, I ISSUED CLB TO 7000 FT. AT SOME POINT I TURNED ACR #3 L, HDG 280 DEGS, THINKING THAT I HAD CLBED TO 15000 FT. I BECAME DISTRACTED BY COORD REGARDING THE 5000 FT TFC. I LOOKED AT SCOPE AND THEN STRIP TO CONFIRM WHAT I HAD DONE -- 7000 FT ISSUED TO BOTH ACFT. I ISSUED TFC AND CLB TO ACR #2. ACR #2 ADVISED HE HAD ACR #3 IN SIGHT. I THEN ISSUED TFC TO ACR #3. HE ALSO ADVISED HE HAD ACR #2 IN SIGHT. ACR #2 PASSED BEHIND ACR #3 AT 7900 FT, CLBING. AT SOME POINT A COMPUTER DUPE INDICATED THAT ACR #2 LEVELED AT 7000 FT AND 1 3/4 MI TO ACR #3'S L. AT THIS POINT ACR #3 WAS AT 6400 FT, CLBING. BOTH ACFT WERE EQUIPPED WITH TCASII (TA AND COLLISION AVOIDANCE SYS) AND THE COMPUTER SYS AT NEW YORK TRACON HAS A COLLISION AVOIDANCE ALARM. NO ALARM, NOR DID EITHER PLT ADVISE OF A RESOLUTION. 2 POSSIBLE CAUSES, OTHER THAN THE OBVIOUS -- THE TWR WAS LATE IN THEIR COM CHANGES, THIRD IN LESS THAN 10 MINS. THIS IRRITATED ME, AND HAD SET PLAN REGARDING ACR #2 TO CLB AND TURN ON CONTACT. I DID NOT ADJUST TO THE SIT. HAD HDOF PERSON, BUT I INVOLVED MYSELF IN SOMETHING HE COULD HAVE HANDLED, HENCE DISTRACTED!

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.