Skip to content

Special VFR: When It's Legal and When It's Smart

What 14 CFR 91.157 actually allows, why Special VFR is request-only, where it is prohibited outright, and what 1 mile of visibility buys you.

SkyFeed Team 8 min read

Special VFR is a clearance that lets you operate inside a surface area on 1 statute mile of visibility and clear of clouds, when the weather there is below what basic VFR requires. It exists for the case where a 900 ft overcast sitting over an airport, with 10 miles of visibility underneath it, otherwise locks a VFR pilot out of the surface area completely. 14 CFR 91.157 is the whole authority, and it is short.

The important part is what it doesn’t do. It doesn’t give you an altitude, it doesn’t give you terrain clearance, it doesn’t extend past the boundary of the surface area, and nobody offers it to you. A controller can tell you the field is IFR and that a clearance is required to enter. The word “special” has to come from the pilot, every time. That single fact is the difference between using Special VFR as a tool and stumbling into it as an accident sequence.

Special VFR minimums, next to basic VFR

Special VFR substitutes for the VFR weather minimums in 91.155 inside a surface area, below 10,000 ft MSL. Everything else about the flight is unchanged.

Basic VFR in a surface areaSpecial VFR
Flight visibility3 SM1 SM
Ground visibility to take off or land3 SM1 SM
Cloud clearance500 below, 1,000 above, 2,000 horizontal in Class C, D, and E; clear of clouds in Class BClear of clouds
CeilingMay not operate beneath a ceiling less than 1,000 ftNo ceiling requirement
AltitudePer airspaceBelow 10,000 ft MSL
ClearanceNone requiredRequired, and the pilot must request it
Time of dayAnySunrise to sunset, unless part 61 instrument requirements are met and the aircraft is IFR-equipped
WhereAnywhereClass B, C, D, and E surface areas only

Two visibility numbers, not one. Operating inside the surface area needs 1 SM flight visibility, which is your judgment from the cockpit. Taking off or landing needs 1 SM ground visibility as reported, and if the field has no weather reporting, your flight visibility stands in. The regulation adds that a pilot’s own visibility call under that provision is not an official weather report, which matters if anyone reconstructs the flight afterwards.

When you actually need it

Two paragraphs of 91.155 do the work. Paragraph (c) says no VFR flight beneath the ceiling inside a surface area when that ceiling is less than 1,000 ft. Paragraph (d) says no takeoff, landing, or traffic pattern entry unless ground visibility is at least 3 SM.

So either number alone triggers it. A 900 ft overcast with 10 SM underneath needs Special VFR. A 4,000 ft ceiling with 2 SM in mist needs Special VFR. Which one is biting changes what you’re accepting, so read the METAR rather than the flight category badge. Our METAR decoder splits the ceiling out of the layer stack. Only a broken or overcast layer, or a vertical visibility, counts as a ceiling; a SCT layer at 700 ft triggers nothing.

One consequence pilots find surprising: the (c) restriction applies beneath the ceiling. Operating above a ceiling reported below 1,000 ft, inside the surface area, on basic VFR minimums, is permitted, and the FAA’s controller handbook says so explicitly. Getting up there legally is the problem.

Nobody is going to offer it to you

FAA Order JO 7110.65, paragraph 7-5-1 lists the conditions under which Special VFR may be authorized. One of them is “Only when requested by the pilot.”

That is not a formality. It keeps a controller from ever being the one who talks a VFR pilot into weather. What you get instead, if you call up in conditions below VFR, is the current weather, a note that an ATC clearance is required, and “advise intentions.” If you want Special VFR, you ask for Special VFR.

Expect to wait. Paragraph 7-5-2 says Special VFR may be approved only if arriving and departing IFR aircraft are not delayed, and controllers are told to give you an anticipated delay but explicitly not an EFC or an expected departure time. At a busy Class D under a 700 ft ceiling, “expect 15 minutes” is a normal answer.

Special VFR at night needs an instrument rating, and the cutoff is sunset

Except for helicopters, 91.157(b)(4) permits Special VFR only between sunrise and sunset, unless two conditions are both met: the person being granted the clearance “meets the applicable requirements for instrument flight under part 61,” and the aircraft is equipped as required by 91.205(d), the IFR instrument and equipment list. The AIM puts it plainly as instrument rated and equipped for IFR flight. The regulation itself says “meets the applicable requirements,” which is a wider phrase than the shorthand, and it does not say in so many words where holding the rating stops and staying current begins.

Sunrise and sunset are also not the same thing as night. Night in Part 1 starts at the end of evening civil twilight, about 30 minutes after sunset in the mid-latitudes and longer in high summer. So Special VFR closes to a non-instrument pilot on the same trigger that turns your position lights on, and both of those happen before it is legally night. Check the actual times for the field and date on our twilight calculator rather than eyeballing it. Alaska gets its own window in the same paragraph: the sun 6 degrees or less below the horizon, rather than sunrise to sunset.

Where it’s prohibited outright

Appendix D, Section 3 to Part 91 lists 33 airports where the Special VFR weather minimums do not apply to fixed-wing aircraft at all. Mostly the big Class B and Class C fields: O’Hare, JFK, LaGuardia, Newark, Boston, Atlanta, DFW, LAX, San Francisco, Seattle, Denver, Miami, Reagan National, and twenty more. The AIM gives the reason as IFR volume, and the controller handbook gives the mechanism at paragraph 7-5-3. Radar separation is not authorized for a fixed-wing aircraft on a Special VFR clearance, because that aircraft is holding 1 mile and staying clear of clouds on its own judgment.

The list is depicted on sectional charts as well as printed in the regulation, per AIM 4-4-6, so you don’t have to carry it in your head. Don’t infer it from airspace class either. The list has not kept up with the map: it still says Greater Buffalo International and Port Columbus, and it leaves out Charlotte, Phoenix, and Las Vegas, which are all busy Class B fields where Special VFR remains available. Match by location, not by current airport name. The prohibition is fixed-wing only; Part 91 does not prohibit Special VFR helicopter operations at these fields. One more boundary catches people: the controller handbook does not authorize Special VFR in Class E extension areas, only in the surface area itself.

How to request Special VFR

If there’s a tower in the surface area, the request goes to the tower. In a Class E surface area with no tower, AIM 4-4-6 sends you to the nearest tower, an FSS, or the center. You do not need to file a flight plan; the AIM asks only that you state your intentions in enough detail for ATC to fit you into the traffic flow.

There is no published script for the pilot side. Build the request from what the controller needs: who you are, where you are, what you want, and the words “Special VFR.”

Springfield Tower, Skyhawk Three Four Five Alpha Bravo, one zero miles south, one thousand five hundred, request Special VFR for landing.

What comes back is scripted. The controller handbook phraseology is “CLEARED TO ENTER/OUT OF/THROUGH (name) SURFACE AREA,” then “MAINTAIN SPECIAL V-F-R CONDITIONS,” and if traffic requires it, “AT OR BELOW (altitude).” You are never assigned a fixed altitude, because you have to stay clear of clouds and only you can see where the clouds are. Two variants are worth knowing: a climb to VFR, available if visibility is the only limitation, and local Special VFR operations, authorized for a stated period if you want a series of takeoffs and landings.

What 1 mile actually buys you

Run the geometry before you accept it. At 90 knots, 1 statute mile of forward visibility is about 35 seconds of air. A standard-rate 180-degree turn takes a full 60 seconds at any speed, and at 90 knots it moves you roughly 1.1 statute miles sideways by the time you roll out. The turn you would use to get out of trouble is wider than everything you can see.

Now stack the vertical. Clear of clouds above you is the only cloud requirement, so the base can be right there. Below you, 91.119 has not gone anywhere: 500 ft above the surface away from congested areas, 1,000 ft above the highest obstacle within 2,000 ft horizontally over one. Under a 700 ft ceiling on the edge of a built-up area, the legal band you are maneuvering in is thin enough to measure in hundreds of feet, at pattern altitude, in an aircraft that is turning.

The clearance also stops at the boundary. ATC provides no separation once you leave the surface area on a Special VFR clearance, and terrain and obstacle clearance are yours the entire time. AC 61-134, the FAA’s advisory circular on general aviation controlled flight into terrain, describes the failure mode in one sentence: the CFIT accident comes when “the pilot tries to continue flying or maneuvering beneath a lowering ceiling and hits an obstacle or terrain or impacts water.” Special VFR changes only whether the attempt is legal. The way it goes wrong is the mechanism in VFR into IMC, with paperwork.

Watch what’s causing the restriction, too. When it is fog rather than a stratus deck, the number you were briefed can be gone by the time you’re on the runway; some fog types close from 3 miles to zero faster than a runup takes. Below 1 SM reported ground visibility the answer is no anyway. Paragraph 7-5-7 tells the controller to inform a departing fixed-wing aircraft that visibility is less than 1 mile and a clearance cannot be issued.

When it’s the defensible call

Special VFR earns its place in a narrow set of conditions. The restriction is a ceiling rather than visibility, so you can actually see. A nearby report, not a hope, tells you what the weather is doing outside the surface area. You’re going somewhere with better numbers. And there’s a way out that doesn’t depend on the weather improving.

Departing a coastal field under a 900 ft marine layer with 10 miles underneath, bound for a field 40 miles inland reporting clear, fits. Arriving at your home field at last light in 1 mile of mist, because the alternative is a hotel, does not. The regulation permits both. Only one of them is a plan.

Common questions

Can I get Special VFR at a non-towered airport?
Yes, if the field sits under a Class E surface area, which includes a Class D that reverts to Class E when the tower closes. With no tower on the field you request the clearance from the nearest tower, an FSS, or the center, per AIM 4-4-6. If the airport sits in Class G airspace there is no Special VFR available, because there is no controlled airspace down to the surface to need a clearance for. Class G has its own lower VFR minimums instead.
Does Special VFR let me fly lower than normal?
No. Special VFR relieves you of the visibility and cloud-clearance numbers in 14 CFR 91.155, and nothing else. The minimum safe altitudes in 91.119 still apply in full: 500 ft above the surface outside congested areas, and 1,000 ft above the highest obstacle within a 2,000 ft radius over one. ATC does not assign you a fixed altitude on a Special VFR clearance, only an at-or-below when traffic requires it, and terrain and obstacle clearance stay entirely with you.
What happens if the visibility drops below 1 mile after I am already inside?
The controller tells you the field is reporting less than 1 statute mile and asks your intentions. If you report the airport in sight, a tower can still clear you to land, traffic permitting. The FAA writes it this way deliberately, because flight visibility from the cockpit and reported ground visibility are not the same number and you are the one who can see. Your options are to land or to leave the surface area.

The app

Your next brief, already decoded.

SkyFeed reads METARs, TAFs, and the rest of your weather picture back in plain English, per station, on iPhone and iPad.