Mid-Air Corridors Nobody Talks About
I spent three years working as a VFR flight planner for a small charter operation based out of a regional field that sits roughly equidistant between two major hub airports. The airspace between those two hubs has some quirks that aren't in any of the standard study materials. People who fly regularly between those airports tend to just climb into the controlled flow and follow the published routes. But there's a strip of air sitting between the two Terminal Control Areas that most pilots completely overlook. The basic situation is straightforward. When two Class B or Class C airspace boundaries approach each other without overlapping, they leave a wedge of lower-class airspace in the gap. In my case we were talking about a roughly 40-nautical-mile wide corridor of Class E surface-to-7,000 feet MSL that ran parallel to the arrivals but outside any ARTCC radar vectoring priority. If you stayed under 5,000 feet and kept your airspeed below 200 knots, you could transit that corridor without ever talking to approach control. The IFR flows above you were busy, but the VFR layer underneath was relatively empty most of the day. The trick that nobody mentions is the wind shadow. That corridor sits in the lee of the approach corridors from both airports, which means the prevailing winds get disrupted by the traffic patterns themselves. Turbulence reports from nearby enroute centers almost never mention that gap because nobody files through it at altitude. On a typical afternoon in the summer I'd see thermals bouncing off the industrial parks along the eastern boundary, but the core of the corridor stayed smooth. It's not perfect flying, but it's consistent enough that it became my default routing when the hubs were saturated.
I ran into a real problem one winter morning when a sudden inversion dropped the ceiling to 800 feet over the entire region. Both hub approach controls were running low-visibility procedures, which meant their radar vectors extended much farther out than normal. The gap I'd been using was now inside the Class B shelf on both sides. I couldn't hold altitude without popping into controlled airspace, and I couldn't turn back without crossing active instrument approaches. I solved it by dropping to 1,200 feet AGL and hugging the valley floor that ran perpendicular to the airspace boundary. It added about twelve minutes to the flight, but it kept me clear of every IFR corridor and the tower on the north side didn't even call me because they were running precision approaches and had zero bandwidth for unregistered VFR traffic. Here's what the charts don't make obvious: that corridor isn't actually uncontrolled in the way most pilots think. It's Class E, which means you still need the transponder with Mode C if you're within 30 nautical miles of a Class B primary airport. The boundary distances shift seasonally too, sometimes by as much as six miles, depending on whether the airport is operating under visual or instrument procedures. If you're flying there, you need the current chart supplement open, not just your GPS, because the GPS won't always reflect the live airspace geometry. Another thing beginners miss is that ATC separation standards change the moment you enter controlled airspace. If you drift into a Class C shelf while climbing through 3,000 feet and an IFR departure is pushing hard out of the adjacent hub, you could find yourself 3,000 feet and two miles from a heavy jet with no warning. The transponder will pick you up, but radar coverage in that wedge is spotty because both centers point their primary surveillance arrays at their own runways, not at the space between them. You are technically visible on secondary radar, but you won't get traffic advisories from either facility unless you actively check in. And neither facility is going to offer you separation from the other center's traffic because you're outside their active control zone.
There are downsides to this whole setup that deserve equal weight. The corridor is narrow. A crosswind of more than 20 knots from the north or south can push you into the adjacent terminal airspace before you even realize it. The terrain on the western side rises to over 2,200 feet MSL in places, which eats into your minimum safe altitude quickly. Fuel planning has to account for headwinds in that valley because the wind shadow effect reverses in winter when the Arctic fronts come through and funnel straight down the gap at 40 knots. And the radio situation is annoying. You'll pick up the regional ATIS on a good day, but there's no dedicated frequency for that airspace. You're on your own for situation awareness. For anyone who wants to fly this route regularly, the best tool I found is a combination of the FAA's SPINS database for real-time airspace changes and a portable GPS that can display live TFRs and temporary restricted areas. The Garmin Pilot app works fine if you keep the subscription current, but the offline data goes stale. I switched to ForeFlight once I started relying on this corridor regularly because the airspace layer updates more frequently and the synthetic vision helps when the valley terrain gets confusing in marginal weather. The cost is about $200 a year, which is nothing compared to what a controlled airspace violation would cost you. The corridor also has a seasonal limitation that most people don't account for. From late spring through early fall, the military starts running low-level training routes in the broader region, and the lateral boundaries of those routes sometimes intrude into the eastern edge of the gap. The NOTAM cycle is 28 days, but actual start times shift. If you're planning a flight during those months, you need to check the current LFR posting at least twice in the week before you go. Last summer I nearly flew into an active LFR because the online chart update was three days old and the NOTAM text was buried under a pile of routine military scheduling notices. I caught it by calling the local FSS, which took four minutes but saved me from losing my insurance coverage on a technicality.
Get the Full Details
If you're looking for alternatives, the standard IFR routing through either hub is obviously the safer bet. It takes longer, burns more fuel, and requires a flight plan, but you get radar service and separation from everything else in the sky. For short VFR hops where you're just trying to get from point A to point B without the hub traffic headaches, the mid-air corridor works. For anything carrying passengers who might get anxious in marginal conditions, or for flights that depend on arriving within a specific time window, stick to the published approach corridors. This route is a convenience tool, not a primary navigation strategy. One final note about fuel reserves. The standard 45-minute reserve calculation doesn't apply cleanly here because the corridor has no diversion airports within a reasonable radius. The nearest appropriate field for an unexpected landing is about 18 miles off the northern end, and it's a private strip that may not be open to the public. You should plan your fuel with at least an hour of reserve for this particular route, and you should have a backup landing field preselected at the southern end too. I keep a printed airport diagram for both fields in the glovebox because cell service drops out completely once you're in the valley between the two terminal areas.
