FSS and MTRs
 

What is up with FSS not wanting to talk to military guys entering VR routes? Multiple times they have been bothered with me checking in with them. They pretty much tell me to make CTAF calls on 255.4 and not to bother calling them. Everything I have read in FAR/AIM, 3710, and 7610.4 says to call them and that is what I teach guys. I have heard that MTRs were left out of the contract when Lockheed took over. Any truth to that? I'll tell you what though, it really bothers me that these jokers don't want to be bothered.

Great, less people to talk to...make a quick call as you enter, and if there is time, when you leave. Sometimes I'll get a reply with the local alt. setting, most of the time it's nothing. Honestly, I don't want to be bothered by talking to them.

FSS = no value added on MTR anyway -- maybe an altimeter for someplace 100 miles away. It's always been a square filler and would be better if we could get it removed.

Thanks for the responses. I guess I will make the call on entering the route and call it good.

AP1/B used to say call on 255.4. It no longer says that. I think you're just required to monitor. I'll still make in the blind calls when I know there is a crossing route.

Shack! I have always been taught and teach that the call, while required by various entities both civ and mil, is an advisory call for entry/exit especially on high traffic routes. If I had a warm fuzzy that civ traffic was monitoring FSS(VHF) I might monitor that and report points along the way to give them SA, but that's a far fetched wish on my part, so I just squawk 4000 and be on my way!

Could it be a "feel my pain due to sequestration?", or is this a service not normally provided?

I remember a few years back not getting a pop up VFR fright following request through ATL due to "limited staffing". ATC was not busy, just trying to make a point.