Narrative:

I was working sector 19 and had a crj descending into the el paso terminal area. The crj was on the star at this time. A VFR BE20 called for VFR flight following the aircraft was leaving el paso approach's airspace climbing. So to understand the picture the crj was just about head on with the BE20. The BE20 was going to pass maybe a 1/4 mile north of the crj. El paso approach called me and said to stop the crj at 14;000 ft and told me nothing about the BE20; I then told him I had already shipped him and proceed to give el paso control. At this point I was gathering all the BE20's info to put in the computer as well as verifying the mode C; radar identification; type and route. By this point the crj and the rebel were in very close proximity. At this point I was unaware of the altitude the BE20 was climbing to. Then when I saw the BE20 climbing thru 13;500; I asked him what he was climbing to he said 16;500. I issued vectors to the BE20 to clear the crj. Both aircraft got within .25 mile or less at the same altitude. After the situation I asked the BE20; was el paso approach proving you flight following? He replied yes; but they canceled my flight following and had me contact you. All this could have been avoided if he was not terminated. In my opinion el paso approach was not providing any service to this VFR aircraft. I noticed the situation late on my end; and I should have caught it quicker; but my question is who terminates flight following on an aircraft with IFR traffic descending thru his flight path. My opinion el paso approach was using careless air traffic control and was not providing safety. If they would have flashed me the BE20 data block this would not of happened. I spent precious seconds gathering all the info on the BE20 when he came over putting me way behind that is why my response was late. We need to work better as a team.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZAB Controller describes a conflict between a VFR BE20 departing El Paso eastbound and a CRJ arriving from the east. The BE20 was receiving flight following from El Paso Departure but was canceled before being switched to ZAB; wasting precious seconds.

Narrative: I was working sector 19 and had a CRJ descending into the El Paso terminal area. The CRJ was on the star at this time. A VFR BE20 called for VFR flight following the aircraft was leaving El Paso Approach's airspace climbing. So to understand the picture the CRJ was just about head on with the BE20. The BE20 was going to pass maybe a 1/4 mile north of the CRJ. El Paso Approach called me and said to stop the CRJ at 14;000 FT and told me nothing about the BE20; I then told him I had already shipped him and proceed to give El Paso control. At this point I was gathering all the BE20's info to put in the computer as well as verifying the mode C; radar identification; type and route. By this point the CRJ and the rebel were in very close proximity. At this point I was unaware of the altitude the BE20 was climbing to. Then when I saw the BE20 climbing thru 13;500; I asked him what he was climbing to he said 16;500. I issued vectors to the BE20 to clear the CRJ. Both aircraft got within .25 mile or less at the same altitude. After the situation I asked the BE20; was El Paso Approach proving you flight following? He replied yes; but they canceled my flight following and had me contact you. All this could have been avoided if he was not terminated. In my opinion El Paso Approach was not providing any service to this VFR aircraft. I noticed the situation late on my end; and I should have caught it quicker; but my question is who terminates flight following on an aircraft with IFR traffic descending thru his flight path. My opinion El Paso Approach was using careless Air Traffic Control and was not providing safety. If they would have flashed me the BE20 data block this would not of happened. I spent precious seconds gathering all the info on the BE20 when he came over putting me way behind that is why my response was late. We need to work better as a team.

Data retrieved from NASA's ASRS site 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.