I used to think of the circle-to-land maneuver following an instrument approach as a necessary evil. We had a lot of airports to go to, in good weather and bad, but not enough straight-in instrument approaches. The cost of installing an instrument approach left us with few options, so we learned to deal with it. Dealing with it, meant training and checking in actual aircraft while flying as high as possible (up to traffic pattern altitude) and as wide as possible (up to normal traffic pattern width). I no longer think of circling as a necessary evil. Now I think of it as an unnecessary and unsafe evil which has been made worse by the way we train and check. I can hear about half of you cheering me on and the other half wondering what all the fuss is about. Allow me to explain.

— James Albright





Before I go any further, let me define “unsafe” for those of you in the business of training and checking in simulators. I believe a safe approach requires the aircraft be stable no later than 500 feet above the landing surface. An approach isn’t stable unless the aircraft is wings level, fully configured to land, on speed, on the runway’s extended centerline, and on the specified glide path (usually 3°). Furthermore, you cannot have exceeded 30° of bank on the way to getting there. If you haven’t got all that accomplished by the time you pass 500 feet above the landing surface, you are unstable. And unsafe

1 — Circling before simulators became clever

2 — The classic (and dumb) simulator circling check

3 — Learning to distrust the simulator

4 — If "they" know it is wrong, why do "they" insist on it?

5 — Learning the wrong lessons in the simulator sets you up to fail in the real world

6 — Creatively extending your vision

7 — Solving the circling conundrum

8 — Two possible solutions



Circling before simulators became clever

Early simulators did a poor job of presenting the airport environment with enough cues to make circling approaches possible, so examiners granted pilots wide latitude. It was almost understood that the turn to the landing runway would be a near-aerobatic maneuver, but so long as we ended on the runway all was forgiven. As simulators got better, the forgiveness became rarer. Lost on those administering the check was the fact it is impossible to fly a stable approach off a circling approach at most published visibility minimums. I’ll illustrate that with several examples, but first let me explain how it is that many pilots somehow make it all work out. There are various techniques, but the earliest was with a stopwatch and what many aviators call “the gouge.”

A classic definition of “gouge” is to extort, and I suppose that is apropos here. We pilots would take copious notes after each failed and successful simulator circle and the word spread throughout: when to turn, what angle to use, how long to time, and so on. “Do you see the runway?” “Absolutely!” As simulators got better, so did cockpit avionics. So the gouge has been replaced with wonderful Situational Awareness (SA) tools, such as airport moving maps and geographically referenced approach charts with accurately placed aircraft symbols.

So we are learning to improve our SA, a good thing. But we are learning the wrong lessons about how to circle. Moreover, we are growing a false sense of confidence that we will be able to circle in the real world as safely as we do in the simulator. There is no better example than the classic simulator circle exercise: The approach to Memphis International Airport (KMEM), Tennessee, Runway 27, circle to Runway 18 Right.


The classic (and dumb) simulator circling check


Circling north of Memphis is theoretically easy because there is a huge ramp that offers visual cues, the approach runway displaced a half mile from the landing runway, giving you more distance to displace yourself, and there are two other runways leading up to the runway you want to land on. But even with all these advantages, pilots struggle with it until they memorize the gouge or learn creative ways to extend their vision. (More on that later.)

I last accomplished this in a simulator for a Gulfstream GVII-G500, a Category C aircraft. A typical approach speed for us at normal weights, no wind, would be 130 KTAS. Our turn radius would be 0.53 nautical miles (nm). The Category C visibility minimum for that approach is 1-1/2 statute miles (sm). A sm is 15% less than an nm, and that difference is critical. My technique is to turn 45° north once I spot the runway and then turn to base once I have the correct offset. I am fortunate that my aircraft’s avionics help me out with this. In earlier aircraft, the check airman would light up the ramp to give me the cues I needed.

I was rarely able to do this and roll wings level on final before 500 feet. But the various check airmen almost always ignored stable approach rules, I suppose because they had no choice. I diagrammed the approach and discovered that if flown perfectly, you would roll out 1.5 nm from the touchdown zone. Good job? Almost. A 3° glide path takes 318 ft/nm, so you would roll out at (1.5)(318) = 477 feet, just shy of a stable approach. But that required perfection on your part. How many flight maneuvers require perfection?

Several years ago, I was flying into Memphis on a moonless night, just after midnight. (Note: this was in an actual aircraft, not a simulator.) The normally busy FedEx arrival traffic was already on the ground, and we had the night sky to ourselves. We were cleared for the ILS Runway 27 and the tower reported the winds were 090 / 5 knots, which wasn’t optimal. By the time we got to the glide slope, the winds picked up to 090 / 15. We told tower, “we can’t land with more than ten knots on the tail.” Tower said, “You have the airport to yourselves, circle to the runway of your choice.”

I looked at the right seat pilot and said, “we’ve never been better prepared to circle, anywhere.” But it wasn’t like the simulator at all, we didn’t see any of the ground references or the approach lights to the other runways. We had to beg tower to light everything up before we were able to circle.

Of course, this example, and those to follow, are in a jet flying at 130 KTAS. You may have better luck in a slower aircraft, especially in a lower circling category. But I’ve found these results to be typical of Category C, D, and E aircraft.

Just as I was learning to distrust the Memphis circling procedure in the simulator, our training vendor discovered a way to make it even worse: New York-John F. Kennedy International Airport (KJFK), New York. The approach is to Runway 4L, circle to Runway 31 Right.


Learning to distrust the simulator


The simulator circling at KJFK is just like KMEM, only less. While you are given ¼ sm more visibility, you have less offset to the landing runway and fewer visual cues. You end up rolling out 1.25 nm from the end of the runway and that means you will be at (1.25)(318) = 398 feet. Once again, the exercise leaves you unstable at 500 feet.

Most simulator instructors and examiners will grant you a lot of leeway when looking for a stable approach during this maneuver. I am usually left to self-critique. “Another unstable approach into Kennedy,” I typically say after landing. “Why don’t you fly a stable approach, then?” I am asked. I admit that my answer is meant to provoke: “I can fly that maneuver at minimums, or I can fly it stable. But I can’t do both.”

Of course, that sparks a heated debate because it is me accusing the examiner of doing something wrong. (I am doing exactly that.) These debates usually end with the examiner saying his or her hands are tied, because the Federal Aviation Administration (FAA) mandates this kind of training of all Part 142 training centers. I know this is true, but it doesn’t take the training centers off the hook. The FAA gets things wrong all the time and the only way they get them right is if someone like a very large Part 142 training center pushes back.


If "they" know it is wrong, why do "they" insist on it?

My company operations manuals doesn't allow our pilots to circle at weather below 1,000' ceiling and 3 miles visibility. But at the simulator we are told we have to demonstrate the circle at published minimums. "Why?" I ask. Most simulator instructors eventually retreat to their catchall excuse: "It's a 142 requirement, there is nothing we can do about it."

That, of course, begs the questions "What is 142" and who are the "we" they are talking about?

14 CFR 142

This is the FAR that "prescribes the requirements governing the certification and operation of training centers." It is the rules telling our training providers how to do their jobs. But it doesn't get into the details about how to conduct a simulator check ride. For that, you need to look into the FAA Order 8900.1 series, specifically, Volume 3, Chapter 54. So that's where we find out how "they" are told how do to a circling approach check. Right? Not exactly. It tells the training centers that the Training Center Examiner (TCE) — the person giving you the check — that the TCE must be evaluated at published minimums if that TCE will be evaluating circling approaches at published minimums. Specifically:

In order for the TCE to remain qualified to instruct/evaluate circling approaches, at published minimums, the TCE must be evaluated accomplishing the circling maneuver at published minimums during his/her proficiency check.

Source: [FAA Order 8900.1, Volume 3, Chapter 54,¶3-4355.C.3)a)3.

So the TCE has to be checked at published minimums. What about we, their customers, the pilots the regulations call "the applicant," what about us?

Airline Transport Pilot (ATP) and Type Rating for Airplane Airman Certification Standards (ACS)

The ATP ACS provides the standards we as pilots at our level must demonstrate to pass a check ride. Among the standards listed in Section VI.G., Circling Approach:

  • "Execute a circling approach at night or with marginal visibility."

The next section provides many of the things we cannot do:

  • "Attempting to land from an unstable approach."

The ACS does not define "marginal" or "stable approach."


The TCEs at the training centers assume Part 142 mandates circling at visibility minimums. It could be that the Principle Operations Inspectors at the FAA have insisted on that, also assuming the requirement. Regardless of who it getting this wrong, the fact we are teaching pilots to land at visibility minimums that make a stable approach impossible risks teaching the wrong lessons. Contrary to popular opinion, circling at a small airport is harder than the large multi-runway operations chosen at our training centers.


Learning the wrong lessons in the simulator sets you up to fail in the real world


You might think the odds are stacked against us at a major international airport with multiple runways, but they are actually improved. These airports have full approach lighting systems that make keeping sight of the airport easier. Ironically, you will almost never have to circle at one of these airports, since they tend to have approaches to each runway. Where things become really hazardous is where you have just one, short runway.

I used to be based at Boire Field (KASH), New Hampshire, where the choices for the single runway were the ILS Runway 14 or the VOR Runway 32. If the ILS was down, our best option was said to be the VOR Runway 32, circle to Runway 14 with 2 sm minimum visibility. After flying simulated circling approaches with less visibility, I thought this would be easy. It was not: it left us rolling out just 1.2 nm from the touch down zone. That comes to (1.2)(318) = 382 feet. The runway has since been lengthened, but back then it was 5,500 feet long. We learned that given the choice of circling at minimums and landing someplace else, the someplace else was always a better option.


Creatively extending your vision


Is this problem going to get better anytime soon? I doubt it. As disingenuous as the system is, we pilots are even more ingenious at finding ways to “creatively” extend our vision and our success in flying the unflyable.

Many aircraft, like mine, offer very good map displays of the runway environment with the aircraft’s position drawn in real time. We can size the display to draw a 2 nm circle around the aircraft as well as 2 nm “feathers” which depict localizer beams off any runways with an ILS approach. We are encouraged to do this as a way of improving our SA.

I’ve seen more than a few pilots struggle with the KMEM Runway 27 circle to Runway 18 Right and then be given helpful hints on how to use this technology to improve their odds. We are told to place that circle over the ILS Feather to Runway 27. Yes, that keeps you within 2 nm of the airport environment. But 2 nm converts to 2.3 sm and our visibility minimum is 1.5 sm. Somebody is cheating: either the pilot doesn’t really see the airport, or the examiner has fudged with the visibility. No matter who is fudging, we pilots are taught we can safely circle at our visibility minimums. I contend that we cannot.


Solving the circling conundrum


Example circling maneuver with 2 nm (not sm) visibility

I often wonder about the fact we use statute miles for visibility and nautical miles for everything else. Let’s say in our small airport example we insisted on our visibility minimums using the same numerical value, but in nautical miles. Would that extra 15% solve things? Yes, it appears it would. Being able to begin our offset earlier and fly a wide base turn allows us to roll out 1.58 nm from touchdown. That means we will be at (1.58)(318) = 502 feet. Again, that requires perfection from imperfect pilots. So this is hardly the solution to what ails us. But there are two solutions available.


Two possible solutions

Solution one . . .

. . . raise the visibility minimums. We are told repeatedly that “Circling is a VFR maneuver.” In my flight department, we require at least 1,000 feet ceiling and 3 sm visibility for circling. If we don’t have that, we look for another place to land.

Solution two . . .

. . . technology. We often fly to Dekalb-Peachtree Airport (KPDK), Georgia, where there are several instrument approaches available for landing on Runway 21 Left. As of the day I am writing this, we do not have our Letter of Authorization (LOA) to use the only approach available for the opposite runway, the RNAV(RNP) Runway 3 Right. (We applied more than six months ago.) We are fully trained and our aircraft is fully capable. The RNAV(RNP) has turned circling, a very unsafe maneuver, into one of the easiest in the book. And easy means safe.


The RNAV(RNP) Rwy 3R at Dekalb-Peachtree (KPDK)

If the dangers of circling are as I’ve outlined them here . . .

. . . why do they persist? I believe they continue at many airports because they are an easy way of offloading the problems of air traffic control onto the pilot. ATC will continue to use circling approaches if we pilots continue to accept them. We pilots will continue to accept them because our training tells us it is safe to do so. The approach visibility minimums have the FAA’s stamp of approval, after all! But keep in mind you can say the same thing about the once ubiquitous NDB approach.

Most of the airports I use have long ago decommissioned their Non-Directional Beacon (NDB) approaches and to that I long ago said, “Good Riddance.” I think few will argue that an NDB approach can be deadly. Now that we’ve slayed that dragon, it is time to aim for the next. I am hoping for the day circling approaches will be as rare as those awful NDB approaches. And on that day, I will say good riddance.


(Source material)

FAA Order 8900.1