There's Exactly One Time You Should Fly a Teardrop Traffic Pattern Entry

There's a single moment when the "teardrop" is the safest thing you can do. Every other time you reach for it, you're making the pattern more dangerous, not less.

I'll just say it up front, because dancing around it would be dishonest: I don't trust the "teardrop" traffic pattern entry into the downwind. Not because it's illegitimate. It's in the book, and it has exactly one job it does well. But that one job involves specific circumstances and the rest of the time the teardrop is a maneuver I'd honestly rather never see. I don't trust it because of how it actually gets flown out there in the real world, day after day, at non-towered fields all over the country: as a default, when it should be a last resort. And while we're being honest, I'm convinced we shouldn't be calling it a teardrop at all. More on that shortly.

This isn't a new thought for me. But it came roaring back recently when Juan Browne, "Blancolirio" to most of you, put out a rant on the subject that lit up the comments and turned into the same fight we always seem to have in aviation: old school versus new school. I watched a lot of pilots defend the teardrop with real heat, and I watched a few defend it mostly because defending it felt like keeping up with the times. And the whole thing left me with a frustration I want to work through honestly, in long form, where there's room to actually think instead of just react.

Here's the video that kicked it off, so you can watch the thing I'm responding to before I make my case:

https://www.youtube.com/watch?v=rD4mqkMszyo

Can't see the player? Watch Juan's video on YouTube.

So this isn't a hot take. It's a debrief. Let me walk through it the way I'd want a fellow pilot to walk me through it..

What the teardrop traffic pattern entry is actually for

Here's the scenario the teardrop is built for: you're approaching the airport from the wrong side of the pattern. The downwind is over there, and you're over here. You need a safe, predictable way to get from the wrong side to the right side without surprising anybody.

The FAA's answer, spelled out in the Airplane Flying Handbook and Advisory Circular 90-66C, goes like this: cross over midfield at least 500 feet above pattern altitude. Keep going. Get a good two miles clear of the pattern. Then, clear of everyone and with a moment to scan, descend to pattern altitude and turn to join the 45 to the downwind.

This depicts the correct entry: 2 NM beyond the traffic pattern and then a turn inbound on the 45 degree entry

.

Notice the shape of that maneuver. By the time you're turning toward the pattern, you're already level, already at pattern altitude, and already looking at the traffic you're about to join. You arrive on the 45, the one entry every single pilot is trained to expect and watch for. And here's the narrow problem it actually solves: sometimes you show up and the pattern is simply too busy to cross midfield at pattern altitude without cutting into someone's path. When that happens, climbing above the whole pattern, getting well clear, and coming back around on the 45 is the safe way down through traffic that's too thick to thread. That is the job. That is the entire job.

Flown that way, for that reason, I have no quarrel with it. But notice how specific that reason is. It isn't "I came in from the wrong side." It's "I came in from the wrong side and the pattern was too packed to cross safely." Take that second half away and the teardrop has no job to do.

What the teardrop usually is

Now here's what I actually see, over and over: cross midfield, and immediately start a descending turn back toward the downwind. Tight. Quick. Efficient. It feels like a teardrop. There's a curve and a descent and you end up on downwind, so what's the difference?

All three versions of this maneuver depicted here are wrong!

The difference is everything.

When you start that descending turn right after crossing the field, you spend the whole maneuver descending and turning and with your tail to the pattern. You are blind, physically blind in a high-wing especially, to the exact traffic you are about to merge with, at the exact moment you're merging with it. You're losing altitude into the same airspace where someone is flying a normal downwind, and you can't see them, and they may not see you.

The FAA doesn't mince words about this. AC 90-66C says plainly that entries made while descending create collision hazards and should be avoided. That's not my opinion dressed up as authority. It's the same FAA guidance the teardrop's defenders are quoting when they say "it's in the book."

Same name. Two completely different maneuvers. One is the procedure. The other is the procedure's name stapled onto a shortcut.

The word itself is borrowed, and that may be the whole problem

Here's the part I think actually explains a lot of the bad flying. Go look at the passage describing this entry in the Airplane Flying Handbook, the PHAK, or AC 90-66C. You will not find the word "teardrop" anywhere. The FAA describes a midfield overflight and a 45 entry, and never names it. We named it.

So where did the word come from? Instrument flying, where it means something precise. A teardrop is a recognized course reversal: depart a fix outbound, then turn back and intercept the inbound course. The Instrument Flying Handbook is blunt about its purpose, to let an aircraft "reverse direction and lose considerable altitude within reasonably limited airspace." There's also the teardrop holding-pattern entry, one of the three standard hold entries. Both are real, both are precise, and both live in the instrument world: flown on a charted course, in protected airspace, usually with nobody else in it.

Now read that instrument purpose again. Reverse direction and lose considerable altitude in a small area. Sound familiar? It's a flawless description of the botched VFR entry, the tight descending turn-back into the pattern. I don't think that's a coincidence. When we borrowed the word, we borrowed the picture that comes with it: a maneuver built to turn and descend in tight airspace. The problem is that the VFR pattern isn't empty protected airspace. It's full of other airplanes, and descending and turning with your back to them is the one thing you can't afford to do there.

So maybe the simplest fix is also the most honest: stop calling it a teardrop. Call it what the FAA calls it, a midfield crossing and maneuver for a 45 entry, flown level and well clear before you turn. Leave "teardrop" on the approach plate and in the hold, where it earns its name. The words we use in the cockpit shape the maneuvers we fly, and this is a case where the wrong word has been quietly teaching people the wrong move.

"If it's flown correctly..."

This is where the conversation always stalls, and it's the part that genuinely frustrates me.

When you raise the safety concern, you get one of two replies:

"If it's flown correctly, it's safe." True. But a procedure that's flown incorrectly far more often than it's flown correctly has a problem, and "you're just doing it wrong" isn't a defense of the procedure. It's an indictment of how it's being taught and absorbed.

"It says right there in the AIM that I can." Also true. And I'd never argue you don't have the right to fly it. But "I'm allowed to" and "this is the safest thing I can do right now" are two different questions, and somewhere along the way we started treating the first one as if it answered the second.

That's the heart of what bothers me. Not the teardrop itself. The reasoning.

The question I keep coming back to

When I'm coming in from the wrong side, here's the question I try to actually ask in the moment: what is the safest way to do this, right now, with this traffic?

For me, most of the time, the honest answer is a midfield crosswind at pattern altitude. I stay level, at the same height as everyone already in the pattern, where they can see me and I can see them. Same-altitude traffic is traffic you can actually spot, and that's the whole game at a non-towered field. It's a see-and-be-seen world, and anything that keeps me visible and predictable wins.

And here's the part that struck me when I went back to the book: the FAA agrees with me about when. The Pilot's Handbook of Aeronautical Knowledge lays both entries out side by side. The overflight-and-teardrop is listed first; the midfield crosswind is listed as the "alternate." Don't read a ranking into that word, by the way. "Alternate" means second-listed, not second-rate. What matters is the condition the book bolts onto the crosswind:

"An alternate method is to enter on a midfield crosswind at pattern altitude, carefully scan for traffic, announce your intentions, and then turn downwind. This technique should not be used if the pattern is busy." FAA Pilot's Handbook of Aeronautical Knowledge, Chapter 14

Read that last line slowly, because it carries the whole argument. The FAA tells you to fly the crosswind, then tells you to stop flying it once the pattern gets busy. That is the exact split I'm making. Quiet pattern: cross at altitude, stay level, stay visible. Busy pattern: the book itself retires the crosswind, and that is when the teardrop, flown the right way, becomes the correct tool.

So when should you ever fly the teardrop? Exactly once in a while, and only when: you arrive at your destination airport and observe the pattern is too busy to do it safely. Too many airplanes, too little room, no clean gap to slot into. That is the moment this procedure exists for. You stay above all of it, get well clear, and come back around on the 45, because going over the top of a crowded pattern is safer than forcing your way across the middle of it.

That's it. That's the one time. Not because you came in from the wrong side. Not because it's quicker. Not because the AIM lets you. Only because the pattern was too full to cross at altitude, and overflying was the safest way through. Every other time, there's a better entry, and you already know what it is.

Now the honest part, because someone with the handbook open will raise it if I don't. The book never says "only fly the teardrop when it's busy." Flown correctly, the teardrop is legal any time you're coming from the wrong side. So my position is stricter than the FAA's, and I'd rather own that than dress it up as a rule it isn't.

My reason is the failure mode from a few paragraphs back: done wrong, the teardrop is that descending turn with your tail to the pattern, and it gets botched constantly. So when it's quiet, why reach for the entry with the ugly failure mode when the book hands me a level, visible one built for exactly those conditions? When it's busy, the math flips, and the teardrop earns its keep.

Which means the whole thing comes down to a single word: busy.

What counts as "busy"?

This is the part nobody wants to pin down, because it's a judgment call, and judgment calls are uncomfortable. But if my entire rule turns on the word, I owe you a real definition instead of a shrug.

Busy isn't a head count. Three Cubs doing lazy closed traffic on a calm evening isn't busy. A single jet on a long straight-in while a student drills touch-and-goes can be. So stop counting airplanes and ask the question that actually matters: can I cross midfield at pattern altitude right now, with positive separation, and a clear picture of everyone?

If you can find a clean gap, you know where every airplane is, and you can slide across without forcing anyone to maneuver, it isn't busy. Fly the crosswind. If you can't find that gap, or you can't account for all the traffic, or crossing would put you nose-to-nose with someone on crosswind or downwind, it's busy. Go over the top.

And here's the tiebreaker for when you genuinely can't tell, because you won't always be able to tell: weigh the two ways of being wrong. Call it "not busy" when it was, and you've flown into traffic you couldn't separate from. Call it "busy" when it wasn't, and you've flown a slightly longer entry that was perfectly safe. Those two mistakes are nowhere near equal. So when it feels like a coin flip, it isn't one: treat it as busy and overfly. The cautious call costs you ninety seconds. The other one can cost everything.

This is really about how we decide

Here's the part I want to drive home, because it's bigger than one pattern entry.

You can rationalize almost any decision after the fact. We're smart people; that's exactly the problem. Give a pilot a maneuver he likes and a few minutes, and he'll build you an airtight case for why it was fine. I've done it. You've done it. It's human.

But "I can justify it" is a low bar. The professionals I admire don't ask whether a decision can be defended. They ask whether it was right, and they're willing to find out it wasn't. That's what a debrief is for. You take the thing apart honestly, you let the facts win even when they're inconvenient, and you walk away a slightly better pilot than you walked in.

I'd love for us to have that conversation about the teardrop. Not the comment-section version where everybody arrives already knowing they're right and leaves more sure of it. The other version, the one where the goal is to get better, not to win.

So if the teardrop is your default, here's my ask, and it's a small one: the next time you're set up to fly it, run the honest check first. Is the pattern actually too busy to cross at altitude? If it isn't, you don't need the teardrop, and the safest version of you picks something else. Do that, every time, and the maneuver goes back to being what it was always meant to be: a rare tool for a rare problem.

I'm not trying to beat anyone in the comments. I'd genuinely rather talk it through, get better, and stop relitigating the same argument with the same outcome. But the outcome I actually care about doesn't happen in a comment thread. It happens in the cockpit, the next time you reach for this entry and ask yourself whether you really need it.

That's the only outcome worth flying for. And it makes the pattern safer for every one of us.

-TFS