On two different occasions Radar Contact has vectors me to intercept the localizer at an unusually high altitude. At SPIM runway 15 the altitude to intercept the localizer was 8,000 with the IAF at 4,000. Next I tried UAAA's runway 5. RC4 left me at 12,000 with the intercept final at 4,800.I guess the MSA is the culprit? At the above altitude no way do I capture the localizer. What to do?

Looking at the SPIM plate, I'll tell you what I'd do...First, by the looks of those mountains I'd certainly enable NOTAMs. RC calls the MSA to be 7600ft. In this sort of terrain, I'd not use that rather 3300ft (the western half). IOW, I'd change the MSA on the Controller Info Tab prior to Start. With NOTAMs enabled, RC would "...when able..." me down. Inflight, I'd pay close attention to what quad or half I was in and use the published MSAs.Be creative with RC's MSA fields. That's why we put them there, for situations like this. You've every option ;)

>Looking at the SPIM plate, I'll tell you what I'd do...>>First, by the looks of those mountains I'd certainly enable>NOTAMs. RC calls the MSA to be 7600ft. In this sort of>terrain, I'd not use that rather 3300ft (the western half).>IOW, I'd change the MSA on the Controller Info Tab prior to>Start. With NOTAMs enabled, RC would "...when able..." me>down. Inflight, I'd pay close attention to what quad or half I>was in and use the published MSAs.>>Be creative with RC's MSA fields. That's why we put them>there, for situations like this. You've every option >>;) I did the approach with NOTAMS but did not take advantage of the published MSA. Also, I forget to enable NOTAMS into UAAA and faced multiple altitude busts and headings warnings.Thanks,