Narrative:

Aircraft X inbound to boise from the northwest down to 8;000 on the STAR. Aircraft X turned to downwind for vectors to an RNAV Y runway 28L approach. I descended him to 7;100 (the lowest MVA to the northeast of boise). Had training on the other radar position. Casual jokes and talking going on between the controllers. I didn't like the way some of my brightness settings for my maps on my radar display looked so I went into the [scope configuration] and started to adjust some settings for weather and maps. Totally forgot about aircraft X on the downwind vector and he entered another MVA of 8;000 to the east of boise at 7;100. No low altitude alert tone since he was in level flight. I issued a low altitude alert; climbed him to 8;000 and turned him to nesle (FAF) for the RNAV approach and cleared him for the approach.I was thinking 'how could I've done that?' there were only two airplanes in my airspace at the time! I can't blame it on any one thing. Sure; I had a quick turn from the prior shift; I worked my whole shift and was winding down with 25 minutes to go; there was joking and humorous banter between the control positions when it happened; I decided at that exact time to start tinkering with my radar map settings. This was my fault; I need to pay attention to the aircraft that I have; not be sidetracked by joking around with other controllers or screwing around with my radar settings when I have traffic. This could've all been avoided if I was just watching my airplanes!there is not and 'black and white' fix for this. Just need to pay attention and not get sidetracked by other things. Keeping airplanes safe is our main job.

Related reports:

Google
 

Original NASA ASRS Text

Title: BOI TRACON Controller was distracted by peer jokes; discussions and fixing the setting on the RADAR scope and forgot about an aircraft that went below a Minimum Vectoring Altitude.

Narrative: Aircraft X inbound to Boise from the northwest down to 8;000 on the STAR. Aircraft X turned to downwind for vectors to an RNAV Y Runway 28L approach. I descended him to 7;100 (the lowest MVA to the northeast of Boise). Had training on the other radar position. Casual jokes and talking going on between the controllers. I didn't like the way some of my brightness settings for my maps on my radar display looked so I went into the [scope configuration] and started to adjust some settings for weather and maps. Totally forgot about Aircraft X on the downwind vector and he entered another MVA of 8;000 to the east of Boise at 7;100. No low altitude alert tone since he was in level flight. I issued a low altitude alert; climbed him to 8;000 and turned him to NESLE (FAF) for the RNAV Approach and cleared him for the approach.I was thinking 'how could I've done that?' There were only two airplanes in my airspace at the time! I can't blame it on any one thing. Sure; I had a quick turn from the prior shift; I worked my whole shift and was winding down with 25 minutes to go; there was joking and humorous banter between the control positions when it happened; I decided at that exact time to start tinkering with my radar map settings. This was my fault; I need to pay attention to the aircraft that I have; not be sidetracked by joking around with other controllers or screwing around with my radar settings when I have traffic. This could've all been avoided if I was just watching my airplanes!There is not and 'black and white' fix for this. Just need to pay attention and not get sidetracked by other things. Keeping airplanes safe is our main job.

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.