Narrative:

ZNY sector N10 shipped us an aircraft (E145) with unrestricted right deviation direct mol when able. This aircraft was level at FL300. Immediately behind him was another aircraft (A320) attempting to climb through him to FL340 with an overtake. It appeared that the trailing aircraft (A320) had leveled off at an altitude below the leading aircraft (E145) FL290 temporarily even though the data block indicated he was climbing. I called N10 and asked him to leave the aircraft level at FL290 since they were still in radio communications with it and they did not know who I was talking about. I tried to help them understand the situation at hand and they appeared to be unaware of the fact that they were climbing the trail aircraft through the lead aircraft without proper longitudinal separation. At this time I hear my r-side yell across they land line that he needed to talk to the A320 immediately since he was overtaking and climbing through another aircraft ahead at FL320. The A320 then checked in with us and was vectored away from traffic. I feel that N10 forgot about the E145 since he was not expecting him to deviate that far right; dropped the data block right at the boundary and climbed the A320. It appeared that the N10 controller had him stopped at FL290 and then launched him through traffic with obvious lack of separation. Perhaps he had a d-side that dropped the data block and he looked and climbed without remembering the traffic. [We needed] better and timely coordination; proper technique on weather deviations; basic separation skills; LOA use of interim altitudes [and] ability to pvd data tags back and forth between ZDC/ZNY.

Google
 

Original NASA ASRS Text

Title: ZDC Controller described an unsafe event when trailing traffic was being cleared to climb through an occupied altitude; the reporter suggesting a number of 'good practices'; which if followed should prevent future same type occurrences.

Narrative: ZNY Sector N10 shipped us an aircraft (E145) with unrestricted right deviation direct MOL when able. This aircraft was level at FL300. Immediately behind him was another aircraft (A320) attempting to climb through him to FL340 with an overtake. It appeared that the trailing aircraft (A320) had leveled off at an altitude below the leading aircraft (E145) FL290 temporarily even though the Data Block indicated he was climbing. I called N10 and asked him to leave the aircraft level at FL290 since they were still in radio communications with it and they did not know who I was talking about. I tried to help them understand the situation at hand and they appeared to be unaware of the fact that they were climbing the trail aircraft through the lead aircraft without proper longitudinal separation. At this time I hear my R-side yell across they land line that he needed to talk to the A320 immediately since he was overtaking and climbing through another aircraft ahead at FL320. The A320 then checked in with us and was vectored away from traffic. I feel that N10 forgot about the E145 since he was not expecting him to deviate that far right; dropped the Data Block right at the boundary and climbed the A320. It appeared that the N10 Controller had him stopped at FL290 and then launched him through traffic with obvious lack of separation. Perhaps he had a D-side that dropped the Data Block and he looked and climbed without remembering the traffic. [We needed] better and timely coordination; proper technique on weather deviations; basic separation skills; LOA use of interim altitudes [and] ability to PVD Data Tags back and forth between ZDC/ZNY.

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