Narrative:

Per our local SOP; I forwarded a departure strip for IFR departure off runway 13; within two minutes I forwarded a VFR departure strip for aircraft Y (amphibian aircraft) and another IFR jet departure strip. The local SOP is not clear on headings for VFR departures; except for not being in the arrival corridor. Aircraft Y was requesting a 125 heading and departing an intersection ahead of and air carrier X (who according to SOP would be runway heading.) I launched aircraft Y on a 100 heading knowing that would allow me separation with the faster jet departing behind him. After observing the turn on aircraft Y; I launched the air carrier X runway heading. I switched aircraft Y to departure; and moments later switched the air carrier X to departure. As I was giving a relief briefing; I noticed that aircraft Y appeared to be turning on course (125 heading) which would cause the faster jet to climb through him to get above him. I mentioned it to the relieving controller and he said that obviously they turned him. The local SOP for radar east states that 'the TRACON shall not cross or turn back into the ATIS departure corridor without prior coordination' which was not done. As I had sent three departure strips to radar within approximately two minutes; I thought it would be obvious to radar to not turn aircraft Y on course; as there would be two jet departures rolling shortly; and they are required to be runway heading. When my post brief time was complete; I stopped by the TRACON to [speak with] the radar trainee. The CIC2 asked what I was referring to I did not say anything because of the large number of trainees in his vicinity. The ojti (on the opposite side of room than CIC2 ) asked what he missed and I told him that the amphibian was turned back into the departure pie without coordination. Recommendation; the SOP needs to be clearer on heading assignments for VFR departures. The radar controller needs to be more aware of the SOP for turning departures; especially when he also should know about other departures because of the strips in front of him.

Related reports:

Google
 

Original NASA ASRS Text

Title: BTR Local Controller described potential conflict event when RADAR Controller turned VFR departure traffic into path of subsequent IFR departures contrary to local SOP requirements.

Narrative: Per our local SOP; I forwarded a departure strip for IFR departure off Runway 13; within two minutes I forwarded a VFR departure strip for Aircraft Y (amphibian aircraft) and another IFR jet departure strip. The local SOP is not clear on headings for VFR departures; except for not being in the arrival corridor. Aircraft Y was requesting a 125 heading and departing an intersection ahead of and Air Carrier X (who according to SOP would be runway heading.) I launched Aircraft Y on a 100 heading knowing that would allow me separation with the faster jet departing behind him. After observing the turn on Aircraft Y; I launched the Air Carrier X runway heading. I switched Aircraft Y to departure; and moments later switched the Air Carrier X to departure. As I was giving a relief briefing; I noticed that Aircraft Y appeared to be turning on course (125 heading) which would cause the faster jet to climb through him to get above him. I mentioned it to the relieving Controller and he said that obviously they turned him. The local SOP for RADAR East states that 'the TRACON shall not cross or turn back into the ATIS departure corridor without prior coordination' which was not done. As I had sent three departure strips to RADAR within approximately two minutes; I thought it would be obvious to RADAR to not turn Aircraft Y on course; as there would be two jet departures rolling shortly; and they are required to be runway heading. When my post brief time was complete; I stopped by the TRACON to [speak with] the radar trainee. The CIC2 asked what I was referring to I did not say anything because of the large number of trainees in his vicinity. The OJTI (on the opposite side of room than CIC2 ) asked what he missed and I told him that the amphibian was turned back into the departure pie without coordination. Recommendation; the SOP needs to be clearer on heading assignments for VFR departures. The radar Controller needs to be more aware of the SOP for turning departures; ESPECIALLY when he also should know about other departures because of the strips in front of him.

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.