Narrative:

As the local sector controller; I observed a hand off that was inbound east of the RNAV arrival. I then observed VFR traffic converging at the same altitude; so I called ZZZ sector xx and advised him of the conflict. He did not take evasive action on his own. He said; 'what do you want me to do?' although the aircraft was still under his control and in his airspace; I told him to turn the brasilia emb-120 to a 170 heading and expedite to 120. At this time the aircraft were approximaetly 8 miles apart and both at 15;300. The controller acknowledged; but delayed the instructions; and did not transfer communications until both aircraft were in my airspace and converging at 12;500 with 2 miles of separation. I immediately issued a 'traffic alert' and a hard heading of 120 and the emb-120 reported the traffic in sight. I then issued visual separation instructions and coordinated with adjacent sectors. I feel very strongly that VFR aircraft are ignored in the center environment and the situation could have been catastrophic had ZZZ kept communications one minute longer. The emb-120 did not report and right/a and will probably file a near mid-air collision report. Management was notified. I recommend all centers take classes on obligations to miss air traffic including VFR. We are bound to keep IFR aircraft safe from other IFR traffic as well as VFR but I think this is ignored across the country. I also feel that the center controller was derelict in his duties and did not care that the aircraft were in conflict.

Google
 

Original NASA ASRS Text

Title: TRACON Controller described an IFR/VFR conflict resulting from the Center Controller's reported 'inaction' with regard to separating the aircraft in question.

Narrative: As the local sector Controller; I observed a hand off that was inbound East of the RNAV arrival. I then observed VFR traffic converging at the same altitude; so I called ZZZ Sector XX and advised him of the conflict. He did not take evasive action on his own. He said; 'What do you want me to do?' Although the aircraft was still under his control and in his airspace; I told him to turn the Brasilia EMB-120 to a 170 heading and expedite to 120. At this time the aircraft were approximaetly 8 miles apart and both at 15;300. The Controller acknowledged; but delayed the instructions; and did not transfer communications until both aircraft were in my airspace and converging at 12;500 with 2 miles of separation. I immediately issued a 'traffic alert' and a hard heading of 120 and the EMB-120 reported the traffic in sight. I then issued visual separation instructions and coordinated with adjacent sectors. I feel very strongly that VFR aircraft are ignored in the Center environment and the situation could have been catastrophic had ZZZ kept communications one minute longer. The EMB-120 did not report and R/A and will probably file a near mid-air collision report. Management was notified. I recommend all Centers take classes on obligations to miss air traffic including VFR. We are bound to keep IFR aircraft safe from other IFR traffic as well as VFR but I think this is ignored across the country. I also feel that the Center Controller was derelict in his duties and did not care that the aircraft were in conflict.

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.