Narrative:

Aircraft 1 a BE36 on an IFR flight plan going to rdu departed assigned runway heading (055) climbing to 6;000; the second aircraft departed a cessna 350 on an IFR flight plan to int assigned a heading of 030 and an altitude of 2;000 which was coordinated by writing it on the strip per facility SOP; both strips were dropped at the same time to the departure controller. After both aircraft were tagged up in ARTS on radar I transferred both aircraft to the departure controller the first immediately followed by the second. The departure controller then turned the first aircraft on course to rdu approximately 350 heading which turned him into the second aircraft causing a loss of separation. Since both aircraft were northwest bound; I assigned the second aircraft a heading that would turn him inside the on course heading of the first aircraft due to the second aircraft going to further northwest then the first; I waited until the departure controller had the information on both of the aircraft prior to transferring communication of either aircraft. While both aircraft were initially separated and coordination was written on the strip of the second departing aircraft it was not written on the strip of the first aircraft or verbally coordinated; which would have prevented the departure controller from turning the first departure on course before turning the second departure and prevented a loss of separation. Recommendation; call the radar controller to inform him of the plan.

Google
 

Original NASA ASRS Text

Title: ILM Controllers described a loss of separation event when the Local Controller failed to properly coordinate departure headings with the RADAR Controller prompting a turn of the first departure in front of the second.

Narrative: Aircraft 1 a BE36 on an IFR flight plan going to RDU departed assigned runway heading (055) climbing to 6;000; the second aircraft departed a Cessna 350 on an IFR flight plan to INT assigned a heading of 030 and an altitude of 2;000 which was coordinated by writing it on the strip per facility SOP; both strips were dropped at the same time to the Departure Controller. After both aircraft were tagged up in ARTS on RADAR I transferred both aircraft to the Departure Controller the first immediately followed by the second. The Departure Controller then turned the first aircraft on course to RDU approximately 350 heading which turned him into the second aircraft causing a loss of separation. Since both aircraft were northwest bound; I assigned the second aircraft a heading that would turn him inside the on course heading of the first aircraft due to the second aircraft going to further northwest then the first; I waited until the Departure Controller had the information on both of the aircraft prior to transferring communication of either aircraft. While both aircraft were initially separated and coordination was written on the strip of the second departing aircraft it was not written on the strip of the first aircraft or verbally coordinated; which would have prevented the Departure Controller from turning the first departure on course before turning the second departure and prevented a loss of separation. Recommendation; call the RADAR Controller to inform him of the plan.

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