Altitude Directives in VFR Flight Following

I use flight following for nearly any long VFR flight, but lately I've been annoyed by controllers giving altitude directives ("Maintain VFR at or below 3000") which would put me at altitudes that are undesirable in terms of aircraft performance or engine-out safety. I think these are sometimes issued to make it easier for ATC to clear the way for arrivals to busy airports.

One pilot friend has suggested I simply cancel flight following instead of complying with the instruction, put IMO this may be at odds with 14 CFR § 91.123 (b): "...no person may operate an aircraft contrary to an ATC instruction in an area in which air traffic control is exercised", since the instruction has already been given. Any thoughts about this?
If you're receiving only flight following, if you're not in airspace where ATC has separation responsibility for VFR aircraft (Class B, Class C/Outer Area, TRSA), you should not be given any altitude directive. There's no reason for it and no authority to issue it. Some people will now point out that FAR 91.159 VFR cruising altitude or flight level includes "...unless otherwise authorized by ATC". That was added when TCAs were created so that ATC could assign altitudes inconsistent with the regulation.
 
That raises a related question: If I request to cancel FF (and change freq), can ATC deny that request?
If you're not in airspace where communications with ATC is required you don't have to request termination of ATC services, just say bye-bye.
 
Ask your friend to point to where 91.123 mentions flight following. It doesn't. You're in controlled airspace, you've received an instruction from ATC, you just follow it.
How do you reconcile FAR 91.123(b) with FAR 91.3(a)?
 
I use flight following for nearly any long VFR flight, but lately I've been annoyed by controllers giving altitude directives ("Maintain VFR at or below 3000") which would put me at altitudes that are undesirable in terms of aircraft performance or engine-out safety.
You can always request a higher altitude. I don't think controllers are in the habit of issuing arbitrary altitudes. If you were told to stay below 3,000, there was probably a reason for it.
 
If you can't see it, you damn sure can't reconcile it.
Must admit, I'm not following you either. Are you thinking that, since 91.3(a) says "The pilot in command of an aircraft is directly responsible for, and is the final authority as to, the operation of that aircraft", they're not subject to ANY following regulations? That seems to be the case, since you're pointing out a "conflict". To me, it means I'm directly responsible for flying the plane in a way that complies with the regs and 91.123(b) sensibly says "Except in an emergency...", which allows me to make the best decision for the circumstances in an emergency. I appreciate a clarification of what you're trying to say.

in airspace where ATC has separation responsibility for VFR aircraft (Class B, Class C/Outer Area, TRSA)
As noted by midlife, this also includes Class E, which is much broader than the few you mentioned. ATC has responsibility for separating IFR traffic from everyone else there, too.

This thread is great discussion - and it kinda illustrates something that came up in a completely unrelated thread (the Chevron deference case): I think most regs come into existence in response to people doing things others thought they didn't think people needed telling not to do. I could easily imagine the FAA says enough is enough and starts expanding controlled airspace boundaries and restrictions because too many people took the "I can do what I want" approach to the point of risking others.
 
Must admit, I'm not following you either. Are you thinking that, since 91.3(a) says "The pilot in command of an aircraft is directly responsible for, and is the final authority as to, the operation of that aircraft", they're not subject to ANY following regulations? That seems to be the case, since you're pointing out a "conflict". To me, it means I'm directly responsible for flying the plane in a way that complies with the regs and 91.123(b) sensibly says "Except in an emergency...", which allows me to make the best decision for the circumstances in an emergency. I appreciate a clarification of what you're trying to say.
There are those who insist pilots must adhere to all ATC instructions while in controlled airspace, even instructions ATC is not authorized to issue.
As noted by midlife, this also includes Class E, which is much broader than the few you mentioned. ATC has responsibility for separating IFR traffic from everyone else there, too.
It includes only that Class E airspace that is also a TRSA or the Outer Area of Class C airspace.
 
I could easily imagine the FAA says enough is enough and starts expanding controlled airspace boundaries and restrictions because too many people took the "I can do what I want" approach to the point of risking others.
The FAA has really been good about that. The regulatory bounds of Class C airspace, for example, are much smaller than the actual arrival and departure routes being used; they don't even encompass all arrival fixes. The same can probably be said of Class B and most definitely about Class D.

And they typically give advance notice and sometimes meet with pilot groups when Class C or B boundaries are modified or established.

There is absolutely nothing regulatory saying a VFR pilot should keep out of the approach corridor protected above 700 AGL by the magenta vignette. But yeah, get enough pilots believing that being reasonably courteous is a violation of their fundamental rights, and things could change.


1720378610715.png
 
Last edited:
This weekend I flew north to south across the departure corridor for charlotte. I did not get flight following as I knew they would make me go way out of my way. I was at 10.5k and I’m totally convinced they held a flight down just to try to teach me a lesson. It climbed like a rocket to 12k and then leveled off until it passed me and then started back up like a rocket again. If they’d kept it climbing it would have passed over me by 5-10k feet.
 
This weekend I flew north to south across the departure corridor for charlotte. I did not get flight following as I knew they would make me go way out of my way. I was at 10.5k and I’m totally convinced they held a flight down just to try to teach me a lesson. It climbed like a rocket to 12k and then leveled off until it passed me and then started back up like a rocket again. If they’d kept it climbing it would have passed over me by 5-10k feet.
You feel they held a flight down to teach you a lesson but climbed it through your altitude?
 
You feel they held a flight down to teach you a lesson but climbed it through your altitude?
Just to give me a bit of wake turbulence. Every other flight went higher sooner. I was watching too see if I would really be in the way and I wasn’t.
 
There are those who insist pilots must adhere to all ATC instructions while in controlled airspace, even instructions ATC is not authorized to issue.
What's an example of an ATC instruction I don't have to follow in controlled airspace? And what's the authority saying I don't have to follow it?
 
Say there is clouds and he gives you a heading straight into it. And you try to negotiate a different course of action and he won't budge. What are you gonna do?
 
What's an example of an ATC instruction I don't have to follow in controlled airspace? And what's the authority saying I don't have to follow it?
ATC is not authorized to assign altitudes or issue altitude restrictions to VFR aircraft outside of Class B, Class C, or TRSA services. The authority for that is FAA Order 7110.65 Air Traffic Control.
 
Say there is clouds and he gives you a heading straight into it. And you try to negotiate a different course of action and he won't budge. What are you gonna do?
Say “unable”. They probably also said “maintain VFR” somewhere in the conversation too. Even if they didn’t you’re VFR and unable.
 
The Finer Points had a podcast on this a few years ago. He did as the OP suggested, cancelled and when they didn’t cancel him he got mad and switched frequencies. He followed up and had a whole discussion why that was against the FAR’s.

I hate it coming back on FF into my airport under the bravo shelf from the north. They always drop me way down low in the bumps. I’ve learned to cancel with center before even getting to approach to avoid it
 
...I hate it coming back on FF into my airport under the bravo shelf from the north. They always drop me way down low in the bumps. I’ve learned to cancel with center before even getting to approach to avoid it
My only complaint in a similar situation was that they held me high for so long that it was a challenge to avoid busting the bravo.
 
Say there is clouds and he gives you a heading straight into it. And you try to negotiate a different course of action and he won't budge. What are you gonna do?
Change altitude. Under most circumstance, when VFR, they won't give you both a heading and attitude. Regardless, it's your responsibility to maintain VFR, so say, "unable," and tell them what you're going to do. Imminent inadvertent IFR is an emergency.
 
ATC is not authorized to assign altitudes or issue altitude restrictions to VFR aircraft outside of Class B, Class C, or TRSA services. The authority for that is FAA Order 7110.65 Air Traffic Control.
You didn't answer the second question, which was not the authority you're relying on for what ATC is instructed to do by the FAA, but rather, the authority that says I only have to follow certain instructions.

Approach control for the Class B nearest to me will absolutely give altitude restrictions to VFRs on FF outside the B.
 
You didn't answer the second question, which was not the authority you're relying on for what ATC is instructed to do by the FAA, but rather, the authority that says I only have to follow certain instructions.
FAR 91.3(a).
Approach control for the Class B nearest to me will absolutely give altitude restrictions to VFRs on FF outside the B.
They are violating FAA Order 7110.65 when they do.
 
NTSB Interviewer: So controller Bob, you were talking to the King Air and watched as he flew into the path of 6 passenger jets? And refused his multiple requests to help him remain clear?

Controller Bob: Yes sir! Really bad outcome, but I followed the rules! Are you here to give me an award?
 
FAR 91.3(a).
That says that as PIC I'm responsible for my decisions. It doesn't say I can do whatever I want. If that's what it meant, then every other regulation would be meaningless, and 91.3(b) would be superfluous.
FAA: Why did you fly through the FRZ?
PIC: Because I'm PIC, you can't tell me what to do!
They are violating FAA Order 7110.65 when they do.
Is there a specific section you're referring to?
 
I guess I'm just of the mindset that believes Flight Following has advantages that far outweigh the disadvantages. One of the disadvantages is ATC will sometimes give me instructions that are inconvenient. I generally comply but sometimes there's a potential safety issue involved. As an example, when I approach Miami from the west, Approach will almost always ask me to be at or below 2000 over the Everglades, which is too low for me in terms of finding dry places to land in an emergency. So I ask for higher and they generally give it. My assumption that they don't have to think about me at 2000 whereas they now have to think about me but they are generally willing to do it.
 
My flight this weekend was vfr for 800 miles or so. I had to change my plan every 5 or 10 minutes for several hours of the flight to stay safe and out of the clouds. It would have made things much more complex for me to try to do that under flight following. I was on 121.5 the whole time.

I had to adjust altitude and direction almost constantly for a couple hundred miles. I think it would have been less safe for those miles if I were trying to coordinate with atc also.

The one time in the past that I had an issue that atc could have helped me with, I was on flight following and they did nothing but give me frequency changes while I’m working the problem making it worse. They refused to help with any of my requests to help find an appropriate airport or get frequencies or weather info for the airport that I found on my own.
 
My flight this weekend was vfr for 800 miles or so. I had to change my plan every 5 or 10 minutes for several hours of the flight to stay safe and out of the clouds. It would have made things much more complex for me to try to do that under flight following. I was on 121.5 the whole time.

I had to adjust altitude and direction almost constantly for a couple hundred miles. I think it would have been less safe for those miles if I were trying to coordinate with atc also.

The one time in the past that I had an issue that atc could have helped me with, I was on flight following and they did nothing but give me frequency changes while I’m working the problem making it worse. They refused to help with any of my requests to help find an appropriate airport or get frequencies or weather info for the airport that I found on my own.
In my experience in similar weather, ATC is very accommodating. They expect you to change headings and altitudes frequently. Sometime they ask the PIC to advise of altitude changes or to stay above or below a level but otherwise "altitude and heading your discretion" or just "maintain vfr." The complications generally come closer to busy airports
 
Ever have someone ask for your help / opinion, and then respond by telling you you're wrong?

Ever ask ATC for Flight Following to help you with your VFR flight, and when they give you advice based on the wider / bigger picture they have, you .................
 
In my experience in similar weather, ATC is very accommodating. They expect you to change headings and altitudes frequently. Sometime they ask the PIC to advise of altitude changes or to stay above or below a level but otherwise "altitude and heading your discretion" or just "maintain vfr." The complications generally come closer to busy airports
I’ve used it plenty of times. I’m very familiar with how it works. Quite frequently they are more trouble than helpful. I’m also ifr rated and have many hours flying in the system. I’m not afraid to talk to atc. But I also have experience that shows me it’s often not worth it.

It also depends on where you are and who you are talking to. In more congested areas, they rarely give you "altitude and heading your discretion" for hundreds of miles.
 
Last edited:
It OFTEN is much easier to just go IFR
IF you're IFR rated and current (edit: and also in an IFR rated plane), I can't think of any reason to fly X Country without filing an IFR plan. If you're not IFR rated/current, then I'd say always get F Following.
 
Last edited:
IF you're IFR rated and current, I can't think of any reason to fly X Country without filing an IFR plan. If you're not IFR rated/current, then I'd say always get F Following.
The aircraft I was flying is not properly equipped to legally file IFR.
 
  • Like
Reactions: WDD
That says that as PIC I'm responsible for my decisions. It doesn't say I can do whatever I want. If that's what it meant, then every other regulation would be meaningless, and 91.3(b) would be superfluous.
FAA: Why did you fly through the FRZ?
PIC: Because I'm PIC, you can't tell me what to do!
As you interpret it it's meaningless.
Is there a specific section you're referring to?
Chapter 7, section 9.
 
I guess I'm just of the mindset that believes Flight Following has advantages that far outweigh the disadvantages. One of the disadvantages is ATC will sometimes give me instructions that are inconvenient. I generally comply but sometimes there's a potential safety issue involved. As an example, when I approach Miami from the west, Approach will almost always ask me to be at or below 2000 over the Everglades, which is too low for me in terms of finding dry places to land in an emergency. So I ask for higher and they generally give it. My assumption that they don't have to think about me at 2000 whereas they now have to think about me but they are generally willing to do it.
Flight following, by itself, is traffic advisories and safety alerts. Controllers can suggest headings or altitudes but they cannot assign them.
 
Flight following, by itself, is traffic advisories and safety alerts. Controllers can suggest headings or altitudes but they cannot assign them.
They can also request you update them if you change altitude or heading, which can be a burden if the system is busy.
 
Deals with Class B operations, and most assuredly contemplates giving vectors and altitudes to VFRs.

View attachment 131119
Yes, that's appropriate in Class B airspace. You said, "Approach control for the Class B nearest to me will absolutely give altitude restrictions to VFRs on FF outside the B."


7-9-7. ALTITUDE ASSIGNMENTS

a.
Altitude information contained in a clearance, instruction, or advisory to VFR aircraft must meet MVA,
MSA, or minimum IFR altitude criteria.

b. Issue altitude assignments, if required, consistent with the provisions of 14 CFR Section 91.119.

NOTE-
The MSAs are:
1. Over congested areas, an altitude at least 1,000 feet above the highest obstacle,
2. Over other than congested areas, an altitude at least 500 feet above the surface.

REFERENCE-
FAA Order JO 7110.65, Para 4-5-2, Flight Direction.
FAA Order JO 7110.65, Para 4-5-3, Exceptions.
FAA Order JO 7110.65, Para 4-5-6, Minimum En Route Altitudes.


c. Aircraft assigned altitudes which are contrary to 14 CFR Section 91.159 must be advised to resume altitudes
appropriate for the direction of flight when the altitude assignment is no longer required or when leaving Class
B airspace.


PHRASEOLOGY-
RESUME APPROPRIATE VFR ALTITUDES.
 
Flight following, by itself, is traffic advisories and safety alerts. Controllers can suggest headings or altitudes but they cannot assign them.
Is this true? I had a controller get angry at me a couple of weeks ago for shifting altitude under VFR FF to avoid entering a cloud, and told me that I had left my "assigned altitude". Was he wrong?
 
Back
Top