Narrative:

Aircraft X requested the ILS 22R approach at sff opposite direction operations (odo). This was all routine. There is a lot of terrain and high mvas close to the base area for this approach. I was training and asked the developmental to either climb or descend aircraft X and commit to whether he was going to vector for the approach inside of the terrain or climb above it and join the approach farther out. The deviation opted to descend and join the approach inside the terrain. This was a good choice and something that needs to be practiced as it is a standard part of our operation. We turned aircraft X a little late. The aircraft was going very fast and waited a while to start the turn. The deviation gave the aircraft another heading to clear the terrain even further then I overrode and asked the pilot for a good rate of turn for terrain. Finally the aircraft started turning but it was a little late and the bulk of the primary target (not the entire target) was just inside a 060 feet MVA when the aircraft was at 055 feet. We were just a little late and violated the MVA. We debriefed this at length and watched the falcon replay simulating the event if the pilot had started turning when we issued it. While it could have worked another day with another aircraft we needed to start the turn earlier. I changed the deviation's plan and he was unaware of my technique to make that approach work from the lower altitude and I waited too long to intervene. Next time I should help more when I change the deviation's plan and intervene sooner if required and we should prep the pilot and watch out for the fast speed when a tight turn is required for a complicated approach to get established on.

Related reports:

Google
 

Original NASA ASRS Text

Title: GEG TRACON Instructor reported a Developmental Controller turned an aircraft too late and entered an area with a higher Minimum Vectoring Altitude.

Narrative: Aircraft X requested the ILS 22R approach at SFF Opposite Direction Operations (ODO). This was all routine. There is a lot of terrain and high MVAs close to the base area for this approach. I was training and asked the developmental to either climb or descend Aircraft X and commit to whether he was going to vector for the approach inside of the terrain or climb above it and join the approach farther out. The DEV opted to descend and join the approach inside the terrain. This was a good choice and something that needs to be practiced as it is a standard part of our operation. We turned Aircraft X a little late. The aircraft was going very fast and waited a while to start the turn. The DEV gave the aircraft another heading to clear the terrain even further then I overrode and asked the pilot for a good rate of turn for terrain. Finally the aircraft started turning but it was a little late and the bulk of the primary target (not the entire target) was just inside a 060 feet MVA when the aircraft was at 055 feet. We were just a little late and violated the MVA. We debriefed this at length and watched the FALCON replay simulating the event if the pilot had started turning when we issued it. While it could have worked another day with another aircraft we needed to start the turn earlier. I changed the DEV's plan and he was unaware of my technique to make that approach work from the lower altitude and I waited too long to intervene. Next time I should help more when I change the DEV's plan and intervene sooner if required and we should prep the pilot and watch out for the fast speed when a tight turn is required for a complicated approach to get established on.

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.