Narrative:

Aircraft X was inbound to the airport from the southeast. Apparently the aircraft was on an IFR flight plan and I completely overlooked that information. It took the aircraft traveling about 10 miles inside my airspace before the pilot called and made first contact with me. When the pilot finally called me and told me he had the current ATIS I had asked the pilot which route he wanted to take inbound to north las vegas airport. Again; I failed to look at all the information in the data block and treated him as if he was VFR. When I asked the pilot which route he wanted and he was open to either route; I gave the aircraft a clearance through the class bravo airspace and assigned a heading of 270 with no altitude assigned. A minute or so later I asked the pilot if he was familiar with the local flying area and the surrounding terrain; and after he replied in the affirmative; I instructed the pilot to resume own navigation then fly heading 360.after I got that read back; I instructed the pilot to cross the airport at and maintain 5;000 feet. A few minutes later as he approached the airport from the southeast and was approximately 6 miles to the southeast and over a 6;300 minimum vectoring altitude. I had noticed there were numerous VFR departures departing southbound; so I assigned a heading of 320 to stay away from the targets I saw departing. At this time the pilot had already begun his descent to comply with the VFR instructions that I had issued; and never mentioned that he was IFR. As stated before I didn't realize he was IFR. I had made a couple traffic calls regarding the departing aircraft who were not radar identified; and at that time a controller a few positions over mentioned the altitude of aircraft X and that was the first time I noticed the data block and all the information that I initially missed indicating that he was in fact IFR. At that point the aircraft was already at 5;500 feet heading northwest bound; and it was at this point that I and the supervisor talked about the aircraft and the situation at hand.I don't know that there are any recommendations or changes that can or should be made to prevent this from happening again in the future. I simply missed the information in the data block indicating that this aircraft was IFR. When I issued a class bravo clearance and all appropriate navigation and altitude instructions for a VFR aircraft; I had the expectation bias that the aircraft was indeed VFR when he accepted all the instructions and never questioned the clearance. I missed the indicators that he was on an IFR flight plan and there is nothing more to it and completely my fault and no one else's.

Related reports:

Google
 

Original NASA ASRS Text

Title: L30 TRACON Controller reported they issued VFR clearance instructions to an aircraft that was on an IFR flight plan which resulted in the aircraft flying below the Minimum Vectoring Altitude.

Narrative: Aircraft X was inbound to the airport from the southeast. Apparently the aircraft was on an IFR flight plan and I completely overlooked that information. It took the aircraft traveling about 10 miles inside my airspace before the pilot called and made first contact with me. When the pilot finally called me and told me he had the current ATIS I had asked the pilot which route he wanted to take inbound to North Las Vegas airport. Again; I failed to look at all the information in the data block and treated him as if he was VFR. When I asked the pilot which route he wanted and he was open to either route; I gave the aircraft a clearance through the Class Bravo airspace and assigned a heading of 270 with no altitude assigned. A minute or so later I asked the pilot if he was familiar with the local flying area and the surrounding terrain; and after he replied in the affirmative; I instructed the pilot to resume own navigation then fly heading 360.After I got that read back; I instructed the pilot to cross the airport at and maintain 5;000 feet. A few minutes later as he approached the airport from the southeast and was approximately 6 miles to the southeast and over a 6;300 Minimum Vectoring Altitude. I had noticed there were numerous VFR departures departing southbound; so I assigned a heading of 320 to stay away from the targets I saw departing. At this time the pilot had already begun his descent to comply with the VFR instructions that I had issued; and never mentioned that he was IFR. As stated before I didn't realize he was IFR. I had made a couple traffic calls regarding the departing aircraft who were not Radar identified; and at that time a Controller a few positions over mentioned the altitude of Aircraft X and that was the first time I noticed the data block and all the information that I initially missed indicating that he was in fact IFR. At that point The aircraft was already at 5;500 feet heading northwest bound; and it was at this point that I and the Supervisor talked about the aircraft and the situation at hand.I don't know that there are any recommendations or changes that can or should be made to prevent this from happening again in the future. I simply missed the information in the data block indicating that this aircraft was IFR. When I issued a Class Bravo clearance and all appropriate navigation and altitude instructions for a VFR aircraft; I had the expectation bias that the aircraft was indeed VFR when he accepted all the instructions and never questioned the clearance. I missed the indicators that he was on an IFR flight plan and there is nothing more to it and completely my fault and no one else's.

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.