TRACON controller described a loss of separation event when traffic issued a heading initially turne...

Narrative:

Working all positions combined on my early shift. The RVR was dropping and I had a B737 on a base. I took a look at the RVR and was late on the turn to final from the north. I tried to turn him left on 040 to rejoin; thought I had time but it was to close to the approach gate. I went further left to 010 so I could get more space. I noticed it was too close; advised the aircraft that I would re-sequence him so turned him left to 250 heading. It appeared he started to turn right with out me instructing him to join the localizer; so I told him it appears you turned right; continue right heading 250. He then told me he was already turning left; so I went back and said continue left turn heading 250. At this time; I noticed we had a departure coming off runway 33; so I instructed the B737 to expedite turn and told tower to put the departure on a 360 heading. They might have gotten to close with no ensured separation; although I might have had divergence. Many things I could have done better. I was a bit tired from waking up early in the morning but that is not an excuse. I could have verified the B737 heading before assigning new turns. I could have climbed him to a safer altitude and stop the departure below him. The first time he went through final; I should have just re-sequenced him; instead of trying to correct in an IFR day. But the major one was verify his turn before assigning a new one. Not just get stuck in trying to help continue his turn; and just ask.

Original NASA ASRS Text

Title: TRACON Controller described a loss of separation event when traffic issued a heading initially turned the wrong direction; the reporter acknowledging several oversights on his part during the event.

Narrative: Working all positions combined on my early shift. The RVR was dropping and I had a B737 on a base. I took a look at the RVR and was late on the turn to final from the north. I tried to turn him left on 040 to rejoin; thought I had time but it was to close to the approach gate. I went further left to 010 so I could get more space. I noticed it was too close; advised the aircraft that I would re-sequence him so turned him left to 250 heading. It appeared he started to turn right with out me instructing him to join the localizer; so I told him it appears you turned right; continue right heading 250. He then told me he was already turning left; so I went back and said continue left turn heading 250. At this time; I noticed we had a departure coming off Runway 33; so I instructed the B737 to expedite turn and told Tower to put the departure on a 360 heading. They might have gotten to close with no ensured separation; although I might have had divergence. Many things I could have done better. I was a bit tired from waking up early in the morning but that is not an excuse. I could have verified the B737 heading before assigning new turns. I could have climbed him to a safer altitude and stop the departure below him. The first time he went through final; I should have just re-sequenced him; instead of trying to correct in an IFR day. But the major one was verify his turn before assigning a new one. Not just get stuck in trying to help continue his turn; and just ask.

Data retrieved from NASA's ASRS site as of July 2013 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	1078372
Time
Date	201304
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Landing
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Initial Climb
Person 1
Function	Approach Departure
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 when traffic issued a heading initially turned the wrong direction; the reporter acknowledging several oversights on his part during the event.