Brien K. Meehan wrote:


This seems to be one of those things that everybody knows, but isn't
really stated authoritatively anywhere. I can't find that rule in
7110.65, but I'm not intimately familiar with it. I'd like to
corrected if possible.

You're essentially asking me to prove a negative. Can't do it. My rule
book tells me what I can do in my airspace. There's no list of what I
can't do.



Even so, that's somebody else's problem. I'd still have to comply with
a controller's directives, even if he's acting outside his authority.

No, you don't. If a controller tries to give you something that the
rules do not allow then say unable. It's as simple as that.


The language of 91.123 doesn't account for appropriate ATC
instructions, it's says "in an area where air traffic control is
exercised."

But you're examples are in areas where ATC is not exercised.



In my silly example, I might be in Peoria's airspace,
which is an area where air traffic control is exercised, so I'm
obligated to follow instructions given by ATC, even if it is SoCal
Approach.

No.



... but this is a good thing. A more prudent example might be
something that happened to me on my student long solo XC. I made a
list of controllers to talk to, and accidently got out of order. I
called Flint Tower when I meant to call Saginaw Tower. Flint Tower
told me to remain clear of Class D and contact "Approach" on 118.80. I
contacted Approach, which turned out to be Flint Approach, and got
everything straightened out quickly. But, in this case, Flint told me
to stay clear of their Class D (well, every Class D, I guess), and I
was obligated to do that, even though I was outside Flint's
jurisdiction.

He's exercising his control within his class D, he didn't do anything in
the class E.