CVG Controller issued an IFR clearance while below the MVA resulted in a CFTT and an traffic conflict situation.
Synopsis
CVG Controller issued an IFR clearance while below the MVA resulted in a CFTT and an traffic conflict situation.
Narrative
I was working satellite radar. CVG was landing Runway 27. Aircraft X called me VFR 6 miles north of the Runway 27 final; southbound approximately 1800 feet; asking for his IFR clearance to Walton at 3000 feet; 20 miles due south. Due to the airspace configuration and complexity; this was not a great space to be in. I immediately felt pressure; due to Runway 27 final being full of aircraft at that time. I made the foolish decision to issue the IFR [clearance]; thinking I could maneuver him through the traffic; particularly once he got to 3000 feet. Given his type aircraft and the small confines of the space I had; this quickly turned to the wrong call. Approximately 4 miles north of final; still below MVA; I turned the aircraft west to avoid the aircraft on final; though ensuring he could provide his own obstacle and terrain clearance; making another mistake. As a result; Aircraft X got 2.75 miles and 500 feet from Aircraft Y on final; paralleling him. In retrospect; the obvious thing I should have done is told Aircraft X to maintain VFR and vector east to where the aircraft on Runway 27 final are at a higher altitude; though this would have immediately conflicted with LUK airport to the East. My urgency to issue the IFR was unnecessary.Recommendation: I need to remember that an aircraft that is VFR asking for their IFR is not entitled to it immediately and they can maintain VFR until I can get them into a better position to issue IFR. Also; I cannot issue headings below the MVA. That was somewhat of a panic vector and not something I've done before.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.