Narrative:

Portland north sector called to tell me that aircraft X was planning to cancel IFR for 4s2 and to [give] approval request direct to 4s2. I approved the approval request. The data block shows the aircraft will be at 7;000 ft. Aircraft X checks in on my frequency level at 6;000 ft. I was startled by this information because the minimum IFR altitude is 6;800 ft. Aircraft X did look like he was still on T276; so I thought maybe that was an acceptable altitude on the t-route. I checked and the t-route was 6;500. So I climbed aircraft X to 7;000 ft. And then coordinated this with portland north. I then asked the pilot if he was still on T276 and he said affirmative. So; that was confusing information.I recommend remedial training to the portland controller on the meas on T276 and the portland/seattle LOA.

Google
 

Original NASA ASRS Text

Title: Seattle Center Controller reported that an aircraft was handed off below the MIA; resulting in CFTT.

Narrative: Portland north Sector called to tell me that Aircraft X was planning to cancel IFR for 4S2 and to [give] Approval Request Direct to 4S2. I approved the Approval Request. The data block shows the aircraft will be at 7;000 ft. Aircraft X checks in on my frequency level at 6;000 ft. I was startled by this information because the minimum IFR altitude is 6;800 ft. Aircraft X did look like he was still on T276; so I thought maybe that was an acceptable altitude on the T-route. I checked and the T-route was 6;500. So I climbed Aircraft X to 7;000 ft. and then coordinated this with Portland North. I then asked the pilot if he was still on T276 and he said affirmative. So; that was confusing information.I recommend remedial training to the Portland controller on the MEAs on T276 and the Portland/Seattle LOA.

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.