TRACON controller described a go around event between two IFR arrivals; initially planned for visual...

Narrative:

The C182 was IFR inbound from the west with the EA50 inbound IFR from the south. The C182 was well ahead of the EA50 and called the airport in sight. Knowing that the C182 would beat the EA50 to the airport; I cleared him for the visual approach to runway 17R. When the C182 was approximately 10 miles northwest of the airport; I went to switch him to the tower. He advised me that he needed to make a couple 360's too loose some altitude and it appeared he would still be well in front of the EA50 so I approved it. By the time two 360's were complete the C182 advised me he needed another couple so I extended the EA50 a little thinking it would still work. After believing the C182 was turning in to the runway; I cleared the EA50 for the visual approach to runway 17R. As the situation got closer I realized it was not going to work so the tower sent the C182 around. I should not have allowed the EA50 to turn in to the airport when I did. As soon as I did it tied my hands and forced me to drive the two airplanes together. Recommendation; I believe that the best thing to avoid this event in the future is to ensure the airplane entering from the west have enough airspace to get down safely for the runway prior to issuing the va clearance. Also; possibly vectoring the aircraft entering from the west out to the east to help ensure they can get down safely for the approach would have been prudent.

Original NASA ASRS Text

Title: TRACON Controller described a go around event between two IFR arrivals; initially planned for Visual Approaches in-trail; the reporter misjudging the separation and the required time to loose altitude.

Narrative: The C182 was IFR inbound from the West with the EA50 inbound IFR from the south. The C182 was well ahead of the EA50 and called the airport in sight. Knowing that the C182 would beat the EA50 to the airport; I cleared him for the Visual Approach to Runway 17R. When the C182 was approximately 10 miles northwest of the airport; I went to switch him to the Tower. He advised me that he needed to make a couple 360's too loose some altitude and it appeared he would still be well in front of the EA50 so I approved it. By the time two 360's were complete the C182 advised me he needed another couple so I extended the EA50 a little thinking it would still work. After believing the C182 was turning in to the runway; I cleared the EA50 for the Visual Approach to Runway 17R. As the situation got closer I realized it was not going to work so the Tower sent the C182 around. I should not have allowed the EA50 to turn in to the airport when I did. As soon as I did it tied my hands and forced me to drive the two airplanes together. Recommendation; I believe that the best thing to avoid this event in the future is to ensure the airplane entering from the west have enough airspace to get down safely for the runway prior to issuing the VA clearance. Also; possibly vectoring the aircraft entering from the west out to the east to help ensure they can get down safely for the approach would have been prudent.

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	974505
Time
Date	201110
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	Skylane 182/RG Turbo Skylane/RG
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict

TRACON controller described a go around event between two IFR arrivals; initially planned for visual approaches in-trail; the reporter misjudging the separation and the required time to loose altitude.