TRACON controller described a conflict event when the planning for the expedited handling of a lifeg...

Narrative:

I accepted a hand off on a BE40 landing ZZZ. Because he was a lifeguard; I was trying to give him expeditious service to runway 6 at ZZZ; as I was not overly busy when I formulated my plan. A few other aircraft came into the picture; including a departure from ilg landing ZZZ1 and requesting practice low approaches at ZZZ1; which we do not do. I got into a conversation with that pilot that may have distracted me from implementing my plan as I had envisioned it. I also misjudged what another sector would do and got myself in a position that I had to try to expedite the descent for the BE40 and vector to avoid traffic that I had not anticipated. I had expected the north satellite controller to leave ZZZ1 arrivals at 50 so I could get the lifeguard underneath at 40 to land straight in to runway 6. The controller did not do it and ran the traffic more to the SOP at ZZZ1 and I was left scrambling to try for separation. At the same time another aircraft had not descended as quickly as I hoped. It was a plan that would have worked out if I had been able to complete needed coordination; but I didn't. I think I should have worked my traffic closer to the SOP operations here rather than trying to provide expeditious service without complete coordination.

Original NASA ASRS Text

Title: TRACON Controller described a conflict event when the planning for the expedited handling of a Lifeguard aircraft was interrupted by several unexpected adjacent controller actions making the aforementioned planning ineffective.

Narrative: I accepted a hand off on a BE40 landing ZZZ. Because he was a Lifeguard; I was trying to give him expeditious service to Runway 6 at ZZZ; as I was not overly busy when I formulated my plan. A few other aircraft came into the picture; including a departure from ILG landing ZZZ1 and requesting practice low approaches at ZZZ1; which we do not do. I got into a conversation with that pilot that may have distracted me from implementing my plan as I had envisioned it. I also misjudged what another sector would do and got myself in a position that I had to try to expedite the descent for the BE40 and vector to avoid traffic that I had not anticipated. I had expected the North satellite controller to leave ZZZ1 arrivals at 50 so I could get the lifeguard underneath at 40 to land straight in to Runway 6. The controller did not do it and ran the traffic more to the SOP at ZZZ1 and I was left scrambling to try for separation. At the same time another aircraft had not descended as quickly as I hoped. It was a plan that would have worked out if I had been able to complete needed coordination; but I didn't. I think I should have worked my traffic closer to the SOP operations here rather than trying to provide expeditious service without complete coordination.

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	1022029
Time
Date	201207
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	Beechjet 400
Operating Under FAR Part	Part 91
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Descent
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 conflict event when the planning for the expedited handling of a lifeguard aircraft was interrupted by several unexpected adjacent controller actions making the aforementioned planning ineffective.