Narrative:

My traffic situation was such that in planning ahead of handling the sequencing and descending of ewr arrs, reference swbnd large transport X at FL260 complete with halo, I had to force 2 flts in front of medium large transport Y through large transport X and top the large transport X flight with medium large transport Y at FL270 and later descend him to FL240 once clear of large transport X. At the time this was transpiring I suddenly received several handoffs, from both sectors 16 and 32, O/gve and O/fak which was a combination of lga/phl/mmu arrs, plus a bos overflt. The prime concern at this time was a pair of flts at FL290 converging on ott, plus insuring that medium large transport Z was out of FL250, reference large transport X. Additionally, in consideration of the need to devote much needed attention of separating and sequencing traffic in the western portion of the sector I decided to descend medium large transport Y from FL290 to FL270. I then continued to resolve the traffic situation to the west in the large transport X jet that had past off his right. Moments later I responded that the traffic was at FL260 and read back the same. At approximately the same time I observed medium large transport Y on the northeast edge of the halo of the swbnd large transport X at an altitude of FL262 (note: conflict alert started at this time). I advised the 'C' asic of the above incident and subsequently medium large transport Y advised me that he was filing a report. Up until this time I was sure the medium large transport Y flight had been assigned FL270 as I had planned and set up in the data block. It was not until I listened to the tape playback was I aware that I had misspoke and assigned FL260 as well as missed the pilots readback of FL260.

Google
 

Original NASA ASRS Text

Title: TWO ACR ACFT PASSED WITH LESS THAN STANDARD SEPARATION.

Narrative: MY TFC SITUATION WAS SUCH THAT IN PLANNING AHEAD OF HANDLING THE SEQUENCING AND DSNDING OF EWR ARRS, REFERENCE SWBND LGT X AT FL260 COMPLETE WITH HALO, I HAD TO FORCE 2 FLTS IN FRONT OF MLG Y THROUGH LGT X AND TOP THE LGT X FLT WITH MLG Y AT FL270 AND LATER DSND HIM TO FL240 ONCE CLR OF LGT X. AT THE TIME THIS WAS TRANSPIRING I SUDDENLY RECEIVED SEVERAL HDOFS, FROM BOTH SECTORS 16 AND 32, O/GVE AND O/FAK WHICH WAS A COMBINATION OF LGA/PHL/MMU ARRS, PLUS A BOS OVERFLT. THE PRIME CONCERN AT THIS TIME WAS A PAIR OF FLTS AT FL290 CONVERGING ON OTT, PLUS INSURING THAT MLG Z WAS OUT OF FL250, REFERENCE LGT X. ADDITIONALLY, IN CONSIDERATION OF THE NEED TO DEVOTE MUCH NEEDED ATTN OF SEPARATING AND SEQUENCING TFC IN THE WESTERN PORTION OF THE SECTOR I DECIDED TO DSND MLG Y FROM FL290 TO FL270. I THEN CONTINUED TO RESOLVE THE TFC SITUATION TO THE W IN THE LGT X JET THAT HAD PAST OFF HIS R. MOMENTS LATER I RESPONDED THAT THE TFC WAS AT FL260 AND READ BACK THE SAME. AT APPROX THE SAME TIME I OBSERVED MLG Y ON THE NE EDGE OF THE HALO OF THE SWBND LGT X AT AN ALT OF FL262 (NOTE: CONFLICT ALERT STARTED AT THIS TIME). I ADVISED THE 'C' ASIC OF THE ABOVE INCIDENT AND SUBSEQUENTLY MLG Y ADVISED ME THAT HE WAS FILING A RPT. UP UNTIL THIS TIME I WAS SURE THE MLG Y FLT HAD BEEN ASSIGNED FL270 AS I HAD PLANNED AND SET UP IN THE DATA BLOCK. IT WAS NOT UNTIL I LISTENED TO THE TAPE PLAYBACK WAS I AWARE THAT I HAD MISSPOKE AND ASSIGNED FL260 AS WELL AS MISSED THE PLTS READBACK OF FL260.

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.