TRACON controller described a loss of separation event between an IFR departure and an IFR practice ...

Narrative:

I was working east feeder radar position. A B737; departed the runway; flight progress strip showed aircraft on 340 heading. I called local control to confirm this heading and was told yes the B737 was given the turn. Following immediately after the B737 was a BE20; on an IFR practice approach. The BE20 had been coordinated to fly runway heading on departure. After issuing radar contact to the B737; I noticed the aircraft did not turn to the 340 heading. Then the BE20 checked in on departure with the B737 in sight. I then told the BE20 to maintain visual separation from the B737 and issued a right turn to 040. I realized when the B737 did not turn and the BE20 was right behind him a possible loss of separation may be occurring. I immediately took steps to re-establish separation. Make sure both tower and TRACON controllers are aware of what other operations are going on adjacent their respective areas of control. The tower controller could have coordinated a turn for the BE20 when he knew he was going to try and get the B737 out before the BE20's approach.

Original NASA ASRS Text

Title: TRACON Controller described a loss of separation event between an IFR departure and an IFR practice missed approach; indicating the Local Controller should have coordinated for separation headings.

Narrative: I was working East Feeder RADAR position. A B737; departed the runway; flight progress strip showed aircraft on 340 heading. I called Local Control to confirm this heading and was told yes the B737 was given the turn. Following immediately after the B737 was a BE20; on an IFR practice approach. The BE20 had been coordinated to fly runway heading on departure. After issuing RADAR contact to the B737; I noticed the aircraft did not turn to the 340 heading. Then the BE20 checked in on departure with the B737 in sight. I then told the BE20 to maintain visual separation from the B737 and issued a right turn to 040. I realized when the B737 did not turn and the BE20 was right behind him a possible loss of separation may be occurring. I immediately took steps to re-establish separation. Make sure both Tower and TRACON Controllers are aware of what other operations are going on adjacent their respective areas of control. The Tower Controller could have coordinated a turn for the BE20 when he knew he was going to try and get the B737 out before the BE20's approach.

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.

Attributes
ACN	978517
Time
Date	201111
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.TRACON
State Reference	US
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	Super King Air 200
Flight Phase	Initial Climb
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Flight Data / Clearance Delivery
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

TRACON controller described a loss of separation event between an IFR departure and an IFR practice missed approach; indicating the local controller should have coordinated for separation headings.