Approach controller experienced a loss of separation while attending to an emergency aircraft; faili...

Narrative:

Both aircraft were on radar vectors for visual approach. Traffic conditions were heavy but generally routine until a C130 was handed off to my position in an extremely unusual position and altitude. This aircraft had declared an emergency (smoke and fumes) in the cockpit. I felt the need to get aircraft in vicinity down to 3;000 so that the C130 could be issued 4;000 as soon as possible. I did so with aircraft X sooner than I would have under normal circumstances. The C130 contacted me at descending out of 14;000 ft approximately 15 miles north northeast of the emergency's airport of intended landing. I became distracted trying to find out what the C130 desired and other pertinent information concerning its situation. Subsequently; I noticed aircraft X on a converging course with aircraft Y. I issued a traffic advisory to aircraft X; but it could not see aircraft Y. I issued instructions to aircraft X 'turn right heading 260 and expedite turn'. It appeared separation was lost perhaps prior any instructions or advisories I issued. Perhaps a reminder to air traffic controllers to turn aircraft first then try to get the aircraft to see each other; especially when the situation is not noticed until separation is lost or nearly lost.

Original NASA ASRS Text

Title: Approach Controller experienced a loss of separation while attending to an emergency aircraft; failing to secure visual separation in time to prevent an Operational Error.

Narrative: Both aircraft were on RADAR vectors for visual approach. Traffic conditions were heavy but generally routine until a C130 was handed off to my position in an extremely unusual position and altitude. This aircraft had declared an emergency (smoke and fumes) in the cockpit. I felt the need to get aircraft in vicinity down to 3;000 so that the C130 could be issued 4;000 ASAP. I did so with Aircraft X sooner than I would have under normal circumstances. The C130 contacted me at descending out of 14;000 FT approximately 15 miles north northeast of the emergency's airport of intended landing. I became distracted trying to find out what the C130 desired and other pertinent information concerning its situation. Subsequently; I noticed Aircraft X on a converging course with Aircraft Y. I issued a traffic advisory to Aircraft X; but it could not see Aircraft Y. I issued instructions to Aircraft X 'Turn right heading 260 and expedite turn'. It appeared separation was lost perhaps prior any instructions or advisories I issued. Perhaps a reminder to Air Traffic Controllers to turn aircraft first then try to get the aircraft to see each other; especially when the situation is not noticed until separation is lost or nearly lost.

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	919952
Time
Date	201011
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.TRACON
State Reference	US
Aircraft 1
Make Model Name	MD-83
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Gulfstream III (G1159A)
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Approach controller experienced a loss of separation while attending to an emergency aircraft; failing to secure visual separation in time to prevent an operational error.