Narrative:

The PA46 was being vectored from the south to sff for an ILS approach. When given a 040 heading and descent to 070 he read back; 'fly heading 140 and descend 070.' he was corrected to fly heading 040; a forty heading; he read back 'heading 140 and 070.' I believe I had two others check on during his second readback and did not hear the 140 heading a second time. The aircraft turned to a southerly heading and descended through the altitude of 070. My MVA's in the area were 065; 060; and 056. I did not receive a low altitude alert. I started advising the pilot to climb immediately to higher altitude due to higher terrain. I advised him what my MVA's were. He sounded very unfamiliar; confused; and nervous. I asked if he needed any assistance or if he just got confused. He never asked for assistance except to be vectored for the approach. He made comments such as; 'I'm doing better now.' I assumed he either got disoriented or did not understand his autopilot. I considered icing but did not have any reports.the pilot continued to deviate from instructions. When assigned a climb to 065 he was observed at 070. I gave him block altitudes. Before turning him base for the approach; I asked if he was ready for the turn. He did not start his descent after cleared for the approach; I instructed him to start to descend. I advised he was slightly high on glideslope and that I would keep him on my frequency until he could verify that he was in fact established on final and glideslope. He got a low altitude alert with tower on a 2 mile final. I later heard he departed approximately 2 hours later on the SFF3 departure with another controller and flew the SID incorrectly. I was busy with numerous other aircraft; so in the end I never issued the brasher warning. I did call sff tower and advised them to watch the aircraft closely as they were having trouble following instructions. I also asked them to give the pilot the TRACON number. The pilot left a message and I passed the information to my supervisor. Ensure proper readback; no matter how many times it takes. Issue low altitude alert along with cautions; if high terrain. Issue the brasher phraseology. Talk to the pilot more; ask them what is happening in more detail to try and offer better help or instructions.

Google
 

Original NASA ASRS Text

Title: GEG Approach Controller describes poor altitude control and incorrect heading read back of a PA46 pilot being vectored to the ILS 22R at SFF.

Narrative: The PA46 was being vectored from the south to SFF for an ILS approach. When given a 040 heading and descent to 070 he read back; 'fly heading 140 and descend 070.' He was corrected to fly heading 040; a forty heading; he read back 'heading 140 and 070.' I believe I had two others check on during his second readback and did not hear the 140 heading a second time. The aircraft turned to a southerly heading and descended through the altitude of 070. My MVA's in the area were 065; 060; and 056. I did not receive a Low Altitude alert. I started advising the pilot to climb immediately to higher altitude due to higher terrain. I advised him what my MVA's were. He sounded very unfamiliar; confused; and nervous. I asked if he needed any assistance or if he just got confused. He never asked for assistance except to be vectored for the approach. He made comments such as; 'I'm doing better now.' I assumed he either got disoriented or did not understand his autopilot. I considered icing but did not have any reports.The pilot continued to deviate from instructions. When assigned a climb to 065 he was observed at 070. I gave him block altitudes. Before turning him base for the approach; I asked if he was ready for the turn. He did not start his descent after cleared for the approach; I instructed him to start to descend. I advised he was slightly high on glideslope and that I would keep him on my frequency until he could verify that he was in fact established on final and glideslope. He got a Low Altitude alert with Tower on a 2 mile final. I later heard he departed approximately 2 hours later on the SFF3 departure with another controller and flew the SID incorrectly. I was busy with numerous other aircraft; so in the end I never issued the Brasher Warning. I did call SFF Tower and advised them to watch the aircraft closely as they were having trouble following instructions. I also asked them to give the pilot the TRACON number. The pilot left a message and I passed the information to my Supervisor. Ensure proper readback; no matter how many times it takes. Issue Low Altitude Alert along with cautions; if high terrain. Issue the Brasher phraseology. Talk to the pilot more; ask them what is happening in more detail to try and offer better help or instructions.

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.