Narrative:

I was working all of the tower positions. Aircraft X departed runway 31 on a 360 heading; wanting to go eastbound on course. Aircraft Y departed runway 4 about a minute later heading 060. Aircraft Y's flight plan was erroneously removed due to a miscommunication with the departure controller; and we both worked to figure out what the problem was. At the time I launched aircraft Y; both aircraft were separated by headings. However; in the process of correcting aircraft Y's flight plan; I failed to advise departure not to turn aircraft X until they were talking to aircraft Y.this resulted in aircraft X being turned eastbound toward the aircraft Y. By the time the flight plan issue was resolved and I noticed the conflict; aircraft Y was already through aircraft X's flight path with course divergence; however I did not ensure separation prior to that; and may have lost radar separation. Further compounding this scenario was the fact that on ground control I had taxiway/runway closures; painting; mowing; and approach light maintenance vehicles needing attention and movement.I allowed myself to get distracted by ground/flight data duties during the conflict. In the future I will not ship an aircraft that may become a conflict until proper coordination has been done. Flight data duties can wait; if necessary.

Related reports:

Google
 

Original NASA ASRS Text

Title: SPI Tower Controller departed a slow aircraft and minutes later departed a faster aircraft. The controller forgot to advise the departure controller not to turn the slower aircraft until they were turning the faster aircraft. The controller then went to work on putting in a new flight plan on the faster departure because somehow it was removed. The controller does not know if there was a loss of separation.

Narrative: I was working all of the tower positions. Aircraft X departed Runway 31 on a 360 heading; wanting to go eastbound on course. Aircraft Y departed Runway 4 about a minute later heading 060. Aircraft Y's flight plan was erroneously removed due to a miscommunication with the Departure Controller; and we both worked to figure out what the problem was. At the time I launched Aircraft Y; both aircraft were separated by headings. However; in the process of correcting Aircraft Y's flight plan; I failed to advise departure not to turn Aircraft X until they were talking to Aircraft Y.This resulted in Aircraft X being turned eastbound toward the Aircraft Y. By the time the flight plan issue was resolved and I noticed the conflict; Aircraft Y was already through Aircraft X's flight path with course divergence; however I did not ensure separation prior to that; and may have lost radar separation. Further compounding this scenario was the fact that on ground control I had taxiway/runway closures; painting; mowing; and approach light maintenance vehicles needing attention and movement.I allowed myself to get distracted by Ground/Flight Data duties during the conflict. In the future I will not ship an aircraft that may become a conflict until proper coordination has been done. Flight data duties can wait; if necessary.

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