Narrative:

I was conducting OJT on the satellite sector. We had approximately 5 planes. A C172 was on a planned missed approach from olympia airport (olm). He was requesting an ILS at tacoma narrows (tiw). My developmental cleared the C172 to tiw via radar vectors and in the same clearance issued incorrect missed approach instructions. The C172 did not read back the clearance. The developmental then went back and 'chunked' the clearance and only issued 'cleared to tiw via heading 360 maintain 2;000 ft.' the C172 read back the clearance correctly. The developmental then gave the appropriate missed approach instructions for tiw; 'after completion of your ILS; fly heading 250; maintain 2;000 ft.' the C172 then read back 'roger; 250 to 2;000 ft.' meanwhile; we had an overflight enroute to pae and a clearance request off the ground to pae. I moved over to the fdio and was printing a full route on the pae overflight to check that stars had labeled the data block correctly. When pae is in the data block; it is often overlooked that the aircraft is actually landing elsewhere. I then turned my attention to the clearance and read back from the aircraft departing from the ground at bremerton (pwt). During this time frame; the C172 had turned westbound at 2;000 and entered a 4;000 MVA. I took action as soon as I realized the situation. I turned him north towards lower MVA's and issued a climb to 4;000 and included the word 'immediately'. I had the developmental drop the MVA map and bring up the eovm (emergency obstruction vector map) and scanned for any obstructions on the new vector. I asked the C172 his flight conditions and he responded that he was IMC. The C172 flew north and re-entered the 2;000 MVA. I reviewed the falcon replay and listened to the audio play back. I believe that my attention was diverted from the situation for a few reasons. I was focused on making sure that my developmental did not issue the same incorrect missed approach on the second clearance. He got it right and I didn't recognize how the pilot read back the clearance. I was also distracted with the 2 pae arrivals. The pilot took the 250 heading immediately instead of on the missed approach. I got distracted and let the C172 enter the area of higher terrain. I don't know what recommendations would prevent this situation from re-occurring except remaining vigilant in the future about clear communication with the pilots. Although; after resolving the situation I was discussing with the developmental and we agreed that neither of us saw any low altitude alerting and thought that was very odd.

Google
 

Original NASA ASRS Text

Title: S46 Controller providing OJT described a below MVA event listing multiple distractions as contributing factors.

Narrative: I was conducting OJT on the Satellite sector. We had approximately 5 planes. A C172 was on a planned missed approach from Olympia Airport (OLM). He was requesting an ILS at Tacoma Narrows (TIW). My Developmental cleared the C172 to TIW via RADAR vectors and in the same clearance issued incorrect missed approach instructions. The C172 did not read back the clearance. The Developmental then went back and 'chunked' the clearance and only issued 'Cleared to TIW via heading 360 maintain 2;000 FT.' The C172 read back the clearance correctly. The Developmental then gave the appropriate missed approach instructions for TIW; 'After completion of your ILS; fly heading 250; maintain 2;000 FT.' The C172 then read back 'Roger; 250 to 2;000 FT.' Meanwhile; we had an overflight enroute to PAE and a clearance request off the ground to PAE. I moved over to the FDIO and was printing a full route on the PAE overflight to check that STARS had labeled the Data Block correctly. When PAE is in the Data Block; it is often overlooked that the aircraft is actually landing elsewhere. I then turned my attention to the clearance and read back from the aircraft departing from the ground at Bremerton (PWT). During this time frame; the C172 had turned westbound at 2;000 and entered a 4;000 MVA. I took action as soon as I realized the situation. I turned him north towards lower MVA's and issued a climb to 4;000 and included the word 'Immediately'. I had the Developmental drop the MVA map and bring up the EOVM (Emergency Obstruction Vector Map) and scanned for any obstructions on the new vector. I asked the C172 his flight conditions and he responded that he was IMC. The C172 flew north and re-entered the 2;000 MVA. I reviewed the Falcon Replay and listened to the audio play back. I believe that my attention was diverted from the situation for a few reasons. I was focused on making sure that my Developmental did not issue the same incorrect missed approach on the second clearance. He got it right and I didn't recognize how the pilot read back the clearance. I was also distracted with the 2 PAE arrivals. The pilot took the 250 heading immediately instead of on the missed approach. I got distracted and let the C172 enter the area of higher terrain. I don't know what recommendations would prevent this situation from re-occurring except remaining vigilant in the future about clear communication with the pilots. Although; after resolving the situation I was discussing with the developmental and we agreed that neither of us saw any Low Altitude Alerting and thought that was very odd.

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