Clt controller described a conflict event between a clt air carrier arrival and a parachute jump air...

Narrative:

While working west arrival; I had numerous aircraft inbound from the west of charlotte but also several aircraft from the east that were flowed over to my downwind to feed to runway 36L. The satellite did an automated point out for a BE90 [skydive operation] climbing through my airspace to a jump altitude of 14;500. I received a 30 second jump call on the parachutists so I vectored a CRJ7 to the south of the jump zone to avoid any conflict. While I was focused sequencing several converging aircraft all at different altitudes that were north of the airport; the BE90 aircraft began his descent. The satellite controller failed to notice that my aircraft were on a path south of the jump zone airport and allowed the BE90 aircraft to conflict with my arrival in his descent instead of having him descend north of the airport and my traffic. Recommendation; two solutions would be to either have the arrival controller work the jump aircraft or have the satellite controller insure that his aircraft stay away from inbound IFR aircraft.

Original NASA ASRS Text

Title: CLT Controller described a conflict event between a CLT Air Carrier arrival and a parachute jump aircraft descending; the reporter indicating the controller working the jump aircraft failed to note the developing problem.

Narrative: While working West Arrival; I had numerous aircraft inbound from the west of Charlotte but also several aircraft from the east that were flowed over to my downwind to feed to Runway 36L. The satellite did an automated point out for a BE90 [skydive operation] climbing through my airspace to a jump altitude of 14;500. I received a 30 second jump call on the parachutists so I vectored a CRJ7 to the south of the jump zone to avoid any conflict. While I was focused sequencing several converging aircraft all at different altitudes that were north of the airport; the BE90 aircraft began his descent. The Satellite Controller failed to notice that my aircraft were on a path south of the jump zone airport and allowed the BE90 aircraft to conflict with my arrival in his descent instead of having him descend north of the airport and my traffic. Recommendation; two solutions would be to either have the arrival controller work the jump aircraft or have the satellite controller insure that his aircraft stay away from inbound IFR aircraft.

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	962672
Time
Date	201108
Local Time Of Day	1801-2400
Place
Locale Reference	CLT.TRACON
State Reference	NC
Aircraft 1
Make Model Name	Regional Jet 700 ER/LR (CRJ700)
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	King Air C90 E90
Operating Under FAR Part	Other Part 105
Flight Phase	Descent
Flight Plan	VFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	ATC Issue All Types

Clt controller described a conflict event between a clt air carrier arrival and a parachute jump aircraft descending; the reporter indicating the controller working the jump aircraft failed to note the developing problem.