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.
Synopsis
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.
Second reporter narrative
We had been handed off to Charlotte Approach and issued a clearance to descend to 9;000 FT and turn right to heading 100 for vectors to 36L. Shortly after; we were told to slow to 210 KTS and descend to 7;000 FT. As we were passing through 9;500 FT; I noticed an aircraft on our TCAS approximately 6 miles and 600 FT descending; that was headed directly for us with a very slight movement from our left to right. We he crossed inside the 5 mile ring on the MFD; I tried to query ATC; but the frequency was congested and I was unable to get through. Things started happening very rapidly. At 2.5 miles the other aircraft was still descending and at 300 FT above us. At that point the TCAS issued a RA to climb. My First Officer disconnected the autopilot and arrested the descent to comply. We still did not have a visual with the other aircraft. Initially the climb command was for only 300 FPM; but quickly went to +3;000 FPM. I notified ATC that we were complying with the RA and we were instructed to return to 7;000 FT when able. At the closest point; the MFD showed we were about 1.5 miles and at the same altitude. Cause; ATC vectored us too close to conflicting traffic.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.