There is a category of aviation knowledge that never appears in any document but gets passed down anyway. An instructor says it. A student writes it in a notebook. That student becomes an instructor and says it with the same confidence, and now it has been said twice as often by twice as many people. Nobody ever looks it up, because nobody ever doubts it. It just sounds like the kind of thing that would be true.
Here is one of them:
"Only one aircraft can operate under Special VFR in the surface area at a time."
I have heard this on flight lines. I have heard it in ground schools. I heard it enough times that at some point I stopped hearing it as a claim and started hearing it as a fact, and then I put it on this website as one of four bullet points describing when SVFR operations may be conducted.
It is not true. There is no such rule, there never was, and the FAA publishes language that actively contradicts it.
A CFI candidate emailed me to point this out. He had sat through a private pilot ground lesson where the instructor stated it flatly, could not find it in the FAR, went looking in the right place, found the opposite, and then went one step further and tried to work out where the misconception came from. That last step is the one worth writing about, so what follows is laid out the way the investigation ran.
The governing rule is 14 CFR 91.157, Special VFR Weather Minimums. It is short. Paragraph (b) is the operative list, and it contains exactly four conditions:
Paragraph (a) limits SVFR to below 10,000 feet MSL inside the lateral boundaries of controlled airspace designated to the surface for an airport, and carves out the locations listed in Part 91 Appendix D, Section 3, where SVFR is prohibited outright. Paragraph (c) prohibits any aircraft other than a helicopter from taking off or landing under SVFR unless ground visibility is at least 1 statute mile, or flight visibility if ground visibility is not reported.
That is the whole regulation. Read it start to finish and count the conditions. There is no fifth condition about being the only SVFR aircraft in the airspace. There is no reference to a traffic count anywhere in the section, and nothing in Appendix D adds one.
So the rule does not exist in the rules. That already settles the legal question, but it does not explain why so many competent people believe otherwise.
If a widely believed idea is not in the CFR, the next place to look is the Aeronautical Information Manual, since a lot of what pilots "know" traces to AIM phrasing rather than regulatory text.
AIM 4-4-6 covers Special VFR Clearances. Subparagraph (f) reads:
"ATC provides separation between Special VFR flights and between these flights and other IFR flights."
Read that carefully, because it does more than fail to support the myth. It refutes it. Separation between Special VFR flights is a meaningless concept if only one Special VFR flight can exist in the surface area at a time. The FAA would not have written a separation standard for a situation it had prohibited.
Two publications in, and the score is one silent and one hostile.
Pilots tend to stop at the FAR/AIM. The question here is not really a pilot question, though. It is a question about what ATC is permitted to do with the airspace, and that lives in FAA Order JO 7110.65, Air Traffic Control, currently at change BB. Chapter 7, Section 5 is dedicated to SVFR.
Paragraph 7-5-3, Separation, opens like this:
a. Apply nonradar or visual separation between:
- SVFR fixed-wing aircraft.
- SVFR fixed-wing aircraft and SVFR helicopters.
- SVFR fixed-wing aircraft and IFR aircraft.
b. Apply nonradar, visual, or IFR radar separation between:
- SVFR helicopters.
- SVFR helicopters and IFR aircraft.
Every one of those pairings is between two aircraft. "SVFR fixed-wing aircraft" as a separation category, plural, describing one SVFR airplane being separated from another SVFR airplane. "SVFR helicopters," plural, same structure. The controller's manual goes well past permitting multiple SVFR aircraft in a surface area. It tells controllers which tools to use when it happens.
Paragraph 7-5-4 adds a second, quieter piece of evidence. Controllers do not assign SVFR aircraft a fixed altitude, because the pilot has to maneuver to stay clear of clouds. Instead they clear the aircraft at or below an altitude that is at least 500 feet below any conflicting IFR traffic, and never below the minimum safe altitude in 91.119. That is a vertical separation technique, and vertical separation is another thing you do not need when there is only ever one airplane.
The answer is not that a bunch of instructors made something up. There are three separate roots, and all three are real.
The most powerful source of tribal knowledge is not a document. It is what you hear on the radio a hundred times during primary training.
There are towered fields where the practice is, in effect, one SVFR aircraft in the surface area at a time. Aurora State in Oregon (KUAO) is a commonly cited example among pilots in the Portland and Salem corridor. You call for SVFR, and if somebody else is already working in there, you get told to hold or to expect a delay. Not sometimes. Consistently, and for years.
A student who trains at a field like that will hear that exchange over and over before anyone ever hands them 91.157. By the time they read the regulation, they are not reading it to learn the rule. They are reading it to confirm something they already believe, and confirmation bias does the rest. Then they become an instructor and teach what they experienced.
A consistent local practice is not a regulation. It is a facility decision, and it lives in a facility directive or a letter of agreement, not in the CFR and not in the 7110.65. Those documents are generally not published for pilots. So the practice is highly visible and its authority is completely invisible, which is exactly the condition under which folklore forms. Pilots see the effect every day and never see the cause, so they invent a cause, and the invented cause gets promoted to "the rule."
If your home field behaves this way, that is worth knowing and worth planning around. It is not worth teaching as a regulation, and it does not generalize to every surface area in the country.
Local practice does not come from nowhere either. Look at what the controller has available and the pattern starts to make sense.
Go to 7-5-3, subparagraph (a), and read the note attached to it:
"Due to the requirements for SVFR fixed-wing aircraft to maintain 1-mile flight visibility and to remain clear of clouds, radar separation is not authorized during SVFR fixed-wing operations."
Radar separation is off the table for SVFR airplanes. That leaves nonradar separation and visual separation. Nonradar separation in a four mile surface area is coarse and workload-intensive. Visual separation is governed by 7-2-1, and the version a tower uses, tower-applied visual separation under 7-2-1(a)(1), requires that the tower visually observe the aircraft and maintain the separation itself. In the weather that made you request SVFR in the first place, a controller may simply not be able to see both aircraft well enough to do that.
So the controller is left doing labor-intensive nonradar work in bad weather while also running the rest of the airport. Running one SVFR aircraft at a time is not a rule they are following. It is the workload decision almost anyone would make.
Now take the tower away.
At a non-towered airport inside a Class E surface area, the SVFR clearance comes from whoever controls that airspace, often an approach control or the ARTCC. That controller is not at the airport. This is the scenario a lot of pilots describe as "Center will only let one SVFR aircraft in there at a time," and the reasoning behind it holds up better than the folk version.
The folk version is that the controller has no eyes on the aircraft. True, but the precise consequence is what matters. Look at 7-2-1 again. Subparagraph (a), covering both tower-applied and pilot-applied visual separation, is labeled TERMINAL. Subparagraph (b) is labeled EN ROUTE, and it authorizes exactly one method: pilot-applied visual separation, where a pilot sees the other aircraft, acknowledges it in sight, and is instructed to maintain visual separation.
Stack that up. For two SVFR airplanes in a Class E surface area worked by Center:
Given that stack, a controller who issues one SVFR clearance and holds everyone else until that aircraft is out is making a defensible call. Which is why it happens so often, and why pilots reasonably conclude it is a rule.
It is still not a rule. The airspace does not impose it, 91.157 does not impose it, and the 7110.65 does not impose it. What imposes it is the intersection of available separation methods, controller workload, and IFR priority under 7-5-2.
The phrase does appear in the 7110.65. Once.
Paragraph 7-5-5, Local Operations, subparagraph (b):
"Control facilities may also authorize an FSS to transmit SVFR clearances so that only one aircraft at a time operates in the Class B, Class C, Class D, or Class E surface areas unless pilots agree that they will maintain visual separation with other aircraft operating in the Class B, Class C, Class D, or Class E surface areas. Such authorization concerning visual separation by pilots must be contained in a LOA between the control facility and the FSS."
There it is. "Only one aircraft at a time." Anyone who has heard the myth and then stumbles across this paragraph will feel like they have found the source and stop reading.
Look at what it actually says, though. This is a provision about a control facility delegating clearance relay authority to a Flight Service Station. It describes the terms of that delegation, not a property of the airspace. It constrains what an FSS may hand out on the control facility's behalf, and even then it includes an explicit escape hatch: the one-at-a-time restriction lifts when pilots agree to maintain visual separation, provided that arrangement is documented in a letter of agreement between the facility and the FSS.
A rule about how an FSS relays clearances at a non-towered field became, through repetition, a rule about the airspace itself. That is a very ordinary way for tribal knowledge to form. Someone reads a real sentence in a real document and generalizes it one level too far, and the generalization is what gets repeated because it is shorter and easier to remember than the original.
Put the three roots together and the myth looks less like ignorance and more like something close to inevitable. Pilots experience a consistent local restriction. The restriction has a sound procedural basis nobody ever showed them. And one real sentence in a real FAA document appears to confirm it. Three things pointing the same direction, none of them saying what everyone thinks they say.
For our purposes at Flight First, the helicopter provisions settle the question beyond argument.
Compare 7-5-3(a) with 7-5-3(b). Fixed-wing SVFR gets nonradar or visual separation. Helicopter SVFR gets nonradar, visual, or IFR radar separation, a strictly wider toolset, because helicopters are not bound by the 1 mile visibility requirement that made radar separation unworkable for airplanes.
Then read 7-5-3(c). When local helicopter volume or complexity warrants it, a facility may establish alternate SVFR helicopter separation minima by letter of agreement with the operator. The LOA has to require SVFR helicopters to maintain visual reference to the surface, and it applies these minima:
Two hundred feet. Simultaneous departures. The FAA does not write a 200 foot separation standard between two SVFR helicopters departing at the same moment unless two SVFR helicopters can depart at the same moment.
This matches what happens in the field. In HEMS operations at a busy surface area, multiple SVFR helicopters working simultaneously is routine, not exotic.
Strip out the myth and this is what limits an SVFR clearance:
What does not appear on that list is a national limit of one.
That distinction has teeth. If you assume the limit is regulatory, you never ask. If you understand it is a facility and workload decision, then asking is reasonable, and so is telling the controller you have the other aircraft in sight and will maintain visual separation. Under 7-2-1 that is a tool the controller can use, and it is the same escape hatch written into 7-5-5(b). The answer may still be no. But "no" from a controller managing workload is a different thing from "no" written into the CFR, and only one of those is worth a radio call.
The technical answer here matters less than the method. Four publications, four different jobs:
That fourth tier is where most aviation folklore is born. Facility-level decisions produce the patterns pilots live inside, day after day, while the documents that authorize them stay out of view. When the visible effect has no visible cause, people supply one, and the supplied explanation gets taught with more confidence than the real one ever would have been.
So the habit worth building is not "look it up" but "look it up in the right book." Ask which tier a claim belongs to. Is this a regulation that binds me, guidance about how the system works, a procedure that binds the controller, or a local arrangement at this one airport? Those four answers have very different scopes, and treating a tier four practice as a tier one rule is the error we started with.
If you are teaching, this makes an excellent ground lesson. Do not tell the student the answer. Hand them 91.157 and AIM 4-4-6, then 7110.65 paragraphs 7-2-1, 7-5-2, 7-5-3, and 7-5-5, and ask them to determine whether more than one aircraft may operate under SVFR in a surface area. Let them find the contradiction themselves. Let them find 7-5-5(b) and work out why it does not mean what it looks like it means. Then ask them the better question: if the rule permits it, why does our home field almost never do it? Working that out from the separation paragraphs is the lesson. They will remember the SVFR rules, and more importantly they will have practiced the skill that actually distinguishes a good instructor, which is knowing which document is authoritative for which question and going to it instead of repeating what they were told.
The SVFR section of our Helicopter VFR Weather Minimums page previously listed "are the only aircraft at the airport operating under SVFR" as a condition for SVFR operations. That was incorrect and has been removed. Two other items on that page have also been corrected: SVFR is available in Class B, C, D, and E surface areas only rather than in all airspace except Class A, and the description of helicopter visibility has been reworded, since the absence of a regulatory minimum in 91.157 is not the same thing as an endorsement of flying with none.
Thanks to the CFI candidate who took the time to research this properly and write in. If you find something else on this site that does not hold up against the source documents, tell us. We would rather be corrected than repeated.
Sources