Cae approach controllers report of operational error due to coordination or lack of on headings.

Attributes
ACN	1168343
Time
Date	201405
Local Time Of Day	1201-1800
Place
Locale Reference	CAE.TRACON
State Reference	SC
Aircraft 1
Make Model Name	Light Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 19.1
Person 2
Function	Approach Trainee Handoff / Assist Departure
Qualification	Air Traffic Control Developmental
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Narrative:

Aircraft Y; inbound to cae from the west. Aircraft Y was on H110 for descent behind traffic. Once clear of that aircraft; and crossing the extended centerline of runway 23 south of the airport; I cleared aircraft Y to the VOR; descending to 022. I had a departure strip for aircraft X; off runway 23; H330. Local control coordinated with ran to leave aircraft X runway heading due to a departure off runway 29. Ran approved the request and advised me of same. Aircraft X departed runway 23 climbing to 40; but never called departure. I turned aircraft Y to H090 then called aircraft X; he responded; I turned him right H290.better coordination and planning. Instead of runway heading aircraft X should have been given H250 or 270 to ensure separation from the downwind arrival and still not conflict with the runway 29 departure. I should have requested ran to go back and coordinate that heading.

Original NASA ASRS Text

Title: CAE Approach Controllers report of operational error due to coordination or lack of on headings.

Narrative: Aircraft Y; inbound to CAE from the west. Aircraft Y was on H110 for descent behind traffic. Once clear of that aircraft; and crossing the extended centerline of RWY 23 south of the airport; I cleared Aircraft Y to the VOR; descending to 022. I had a departure strip for Aircraft X; off RWY 23; H330. LC coordinated with RAN to leave Aircraft X runway heading due to a departure off RWY 29. RAN approved the request and advised me of same. Aircraft X departed RWY 23 climbing to 40; but never called Departure. I turned Aircraft Y to H090 then called Aircraft X; he responded; I turned him right H290.Better coordination and planning. Instead of runway heading Aircraft X should have been given H250 or 270 to ensure separation from the downwind arrival and still not conflict with the RWY 29 departure. I should have requested RAN to go back and coordinate that heading.

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.