Overhead Break Arrival: From Concept to Execution

Warning to the reader:

This publication is intentionally (slightly) provocative. We’re going to point out (once again...) the recurring mistakes and half-truths that circulate in popular DCS tutorials, even in official videos. The aim is not to blame individuals. Instead, we’ll use those examples as a basis to deepen your understanding of fighter aviation, so you can approach the simulator with the mindset of a combat aviator, even if you are “just” an armchair pilot.

As you perfectly know, using observed mistakes as the raw material for improvement is the very foundation of the debrief phase in any fighter-jet mission. Debriefs exist to dissect what was done, what went wrong, and how to do it better next time. If we aren’t willing to call out incorrect technique and trace it back to flawed understanding, we rob ourselves of the single most powerful improvement tool pilots have.

The recent release of the MiG-29 in DCS World brought with it a series of demo and tutorial videos. One in particular, produced by Wags and showcasing the landing procedure, caught my eye. It reminded me a former video about the F-16 Viper landing procedure.

Even if I perfectly understand that it was meant as an instructional piece, I couldn’t help noticing how little it conveyed about what combat aviation is really about. To be frank, the procedure looked lazy: the aircraft was flown slow and gentle, the sequence drawn out, the energy completely missing. At times, it felt like watching a C-17 Globemaster on final (no offense). But this is supposed to be Digital Combat Simulator...

Here lies my main complaint: the overhead break is not just “one way to land.” It is a combat maneuver, designed to expedite the recovery of fighters under tactical conditions. When flown slowly and gently, it loses all of its purpose.

In this post, I intend to examine first the origins and conceptual purpose of the overhead break, then lay out the errors commonly met in online tutorials and explain why those errors matter. Finally, I will give practical guidance on how to execute the maneuver properly in DCS so your flying is informed by reason, not a more or less random youtube video...

I. Conceptual Basis

I.1 - Modern justifications

The overhead break (OHB), or Посадка с (визуального) малого круга in Russian (visual close-circle landing), since the MiG-29 was the triggering factor, is often described in airfields landing procedures. To take just one example, MCAS Miramar describes it in their local procedures as “an expeditious type of arrival using VFR, allowing multiple aircraft flying together to land in quick succession by performing a roughly racetrack-shaped descending loop.” The procedure continues by detailing how the lead aircraft initiates the break overhead the runway, followed in sequence by the rest of the formation, each turning downwind and then onto final with proper spacing.

Even in this straightforward peacetime description, the essence of the OHB is already visible: it is designed to expedite recovery and efficiently sequence multiple aircraft. The logic is economy of time and space: recover a formation quickly, keep traffic predictable, and minimize the need for extended holding or in-trail approaches.

Other justifications for the OHB procedure can also be found:

• Noise-impact mitigation: OHB reduce the time that aircraft spend low and slow over noise-sensitive final-approach corridors.

• Safety: OHB keeps aircraft within a known, recoverable footprint of the airfield and centralizes visual inspection of the field (preceding traffic, runway state) by the flight lead.

• Reduced radio use: for formation flights, overhead approaches allow a lead to make the radio calls and sequence multiple elements with minimal chatter. This reduces controller workload and allows wingmen to maintain station until the last safe moment. This is particularly true in a restrictive EMCON environment.

The Overhead Break as described by FAA ATC procedures in section 3.10.2

But these modern considerations forget the original reasons for the OHB: it was designed as a combat maneuver.

I.2 – Historical Background

The overhead break was never invented to reduce noise complaints or ease radio traffic. Its origins are far older, rooted in the brutal realities of combat aviation.

As early as World War I, airfields themselves were often within range of the front lines. The limited depth of the battlefield meant that enemy forces could stage ambushes or direct fire against aircraft during takeoff and landing. Aviators quickly recognized that returning to base low on fuel and ammunition was a particularly dangerous phase of flight: the aircraft were slow and often committed to a predictable landing path.

Direct evidence from that era is scarce, photography and film were still in their infancy, but by World War II the picture became undeniable. Gun-camera footage shows aircraft on approach turning into easy prey. Aircraft caught in landing configuration,gear down, flaps extended, engines throttled back, had almost no chance to evade strafing. The lesson was brutally clear: the longer you spent lumbering toward the runway in a low-energy state, the greater your chances of being killed before your wheels touched the ground.

Gun-camera footage of a Hawker Hurricane with gear down.

A German bomber (possibly a Heinkel He-111) is being strafed just before landing.

Fast-forward to Vietnam, and the same vulnerabilities reappeared in the jet age. As TAC ATTACK magazine reminds us, there are documented cases of fighters being shot down while on approach to bases in South Vietnam, exposed and slow, just as their WWII predecessors had been.

"Many of us have seen gun camera film of kills during the traffic pattern (even with gear and flaps down"...

For units flying from forward bases within range of small arms and AAA, the landing phase was as dangerous as the mission itself.

The overhead break provided a simple, effective countermeasure. By keeping aircraft at combat speed until the last possible moment, and by converting that speed into spacing and configuration only when abeam the runway, the break minimized the window of exposure.The maxim train as you fight applies directly here. Practicing the OHB in peacetime meant that, in wartime, pilots have the muscle memory to execute recoveries under fire without hesitation. It is not just a way to get home: it was a maneuver with survivability baked into its geometry.

And that relevance is not confined to history. The conflicts of the 21st century prove, again, that the landing phase remains a high-risk portion of flight. The ongoing war in Ukraine highlights this reality in stark terms: the widespread use of drones shows how even supposedly secure airfields can be subject to constant surveillance and attack. A slow, extended approach is no longer just inefficient: it can be fatal. The OHB, with its compressed profile and reduced exposure time, remains a tactically sound answer to an enduring problem.

Fighter Bomber telegram channel acknowledged the threat that UAVs cause to aircraft during take-off and landing.

With that reality in mind, you finally understand why the overhead break is flown the way it is, and why so many YouTube tutorials get it wrong. If you truly accept the maxim “train as you fight”, you will never fly the break the same way again. The maneuver stops being a neat pattern and becomes a tactical tool: fast, purposeful, and survivability-driven.

II. Common mistakes

Let's break down the full landing procedure in chronological order in order to identify the most common mistakes.

II.1 - IP to Overhead

• Don't be too slow: keep your combat speed as long as possible.

We all perfectly know that many manuals quote 300–350 kt as the beginning-of-break speed, but treat those figures as minimums, not targets. If noise abatement and traffic management aren’t constraining you, ask for a higher recovery speed. In training 450 kt is perfectly reasonable, and in wartime you may deliberately arrive even faster (540 kt or more). The whole point of the OHB is to delay the low-energy, predictable phase of flight until the last practical moment.

• Don't fly directly over the runway: you should be offset to the "cold" or "dead" side, that is to say opposite to the break side.

That offset gives you a clear visual of the runway surface and lets you spot preceding traffic without having to shove the jet into awkward bank angles. It’s the same logic used in carrier recoveries. It will be particularly important when EMCON procedures are in use.

• Look around: don't keep your eyes in front of you, focused on the runway.

Your earliest duty after the IP is visual acquisition. Don’t tunnel on the runway or the HUD. First clear the outside sector for traffic and threats, then check the inside sector (the area you’ll be turning into). Expect mixed performance traffic: transports, helicopters, or even aircraft with radio failures, and scan accordingly.

Slow, lined up on runway, and head locked forward... Bingo!

II.2 - The Break

• Decision point: 1st third of downwind.

Don't turn too late, especially if you are a 4-ship flight (or even more...). The idea is to be quickly settled for the final turn, and every second on the cold leg will delay that turn. Just as for a Navy "shit hot break", you can even turn abeam the runway threshold and make it a continuous turn to land.

• Last visual scan before you break: first, look outside, then look inside.

Give a last look toward the cold side to clear for threats, you don’t want to offer your belly to someone you didn’t see. Then look inside to confirm spacing with preceding traffic. Once clear, start the turn.

• Pull hard: that is to say as hard as you are stupid (or clever).

Pull hard, go idle, extend the speed brakes, in that order. The goal is to be established downwind 1 to 2 NM abeam the runway at pattern altitude. A shallow break simply won’t get you there. If you have a wingman, don't touch your throttle before you frankly pulled away, or he'll get very surprised!

For the bank angle itself, let's take the time to do the math: a 30° AoB turn at 180 kt already places you 1.8 NM off the runway, and that’s at your exit speed. At 300 kt, a 30° turn produces a turn radius of 13,800 ft (≈2.1 NM): much too wide. If you want to be abeam in the right place, you need to pull significantly harder: at 300 kt you can take ~70° of bank and then slowly reduce. If you’re arriving hotter than that, expect to pull near max G, and that’s totally normal!

The rule of thumb known as G ~ speed (kt) /100 is quite efficient.

This Turn Performance Chart will give you a turn radius for a given TAS and bank angle.

• About ordnance.

A persistent sim myth is that pulling hard with bombs onboard risks “losing them.” That's total nonsense. If your loadout is cleared in the flight manual, it has been structurally tested across the authorized flight envelope. The only requirement is to respect the published restrictions. Within the approved domain, you can (and should) break at maximum performance.

• Look outside: again...

During the turn, your eyes belong inside the turn, looking where you’re flying to. The HUD deserves only quick glances. This is a visual pattern, not an IMC instrument approach. Note that in real life, staring down (eg at your kneeboard page) during a high-G break is a reliable way to induce Coriolis disorientation. So scan outside, fly the jet.

Midfield is too late, this break is too lazy, and more importantly, it is flown as an IFR procedure...

II.3 - Downwind

The downwind leg exists for one purpose: to give you enough time to configure the jet for landing. Think of it as the transition between the slick, “out of the break” configuration and the dirty, “ready to land” state.

• Configuration:

Each aircraft has its own checklist, but a few universal rules apply:

• power before configuration: you came out of the break at idle. Before touching gear or flaps, make sure the engine responds to throttle input. You'll gain a few precious seconds in case of an unresponsive engine.

• hydraulics check: hydraulic failures almost always have a consequence during the configuration phase (gear, flaps, brakes). Know your pressures before moving anything.

• gear before flaps: if something fails, it is far easier to land with gear down and no flaps than the opposite.

• Distance to runway: spacing by picture, not numbers.

The correct abeam distance is driven by pattern altitude. Trust your visual cues, not a TACAN/DME readout. A properly flown break should place you roughly 1.5 NM abeam at ~1,500 ft AGL. If pattern altitude changes (eg higher for noise, lower for weather), adjust spacing accordingly.

Correct abeam distance as described in the T-38C training manual. It can serve as a reference in most aircraft.

• Wind correction: correct for cross wind.

Crosswind is often forgotten but makes all the difference. Nose slightly into the wind on downwind to preserve spacing, and anticipate how it will affect your base-to-final. With a strong crosswind, you may need either more or less bank in the final turn to keep ground track correct. Ignoring it guarantees a sloppy approach.

Some people are taught not to correct the bank angle during the final turn, but correct the distance to the runway instead: the rule is 0.1 Nm for each 10 kt of crosswind (closer or farther depending on direction).

• Look outside: again and again...

Once again, it is not the time to admire your HUD. Keep your eyes outside: preceding traffic on final, runway state, spacing. On familiar fields, use ground references (buildings, roads, landmarks) to cue your base turn. They make spacing corrections and wind compensation much easier than trying to only fly by numbers.

The abeam distance is checked only once, just before final turn. We can see that we are so far away that the runway is barely visible...

II.4 - Final Turn

• Better start early than late:

The infamous “45° cue” (waiting until the runway threshold is 45° behind your shoulder) is widely quoted, but it only works if you are relatively close (≈1.0–1.5 NM abeam). If you are farther out, that same cue will push you into an overshoot and an extended base leg that looks more like an airline circuit than a fighter recovery.

Civilian visual patterns use that geometry because they are designed for safety, stability, and wide spacing. Fighters are different: the turn can begin much earlier, sometimes almost abeam the threshold, especially in light, maneuverable aircraft. Waiting for 45° may be acceptable in legacy jets without FBW or in heavy configurations, but if you want to fly the overhead break fast, tactical, and efficient, start early.

• Nose down: push on the stick.

Rolling into final is one of the rare times in a fighter when you push on the stick. If your nose simply “settles” below the horizon, you are too far out. A proper final turn requires an immediate −8° to −10° nose-low attitude. Flying it flat is the unmistakable sign of a poor setup: you waited too long to turn.

• Throttle: keep some juice.

A well-flown final turn trades altitude for energy, keeping you on-speed naturally. But don’t fly it at idle. Ideally, you should need to carry a touch of power to sustain the turn. That keeps your RPM up, which is exactly where you want it: jet engines spool slowly from idle, and if you need to wave off, a live throttle response is priceless. High, hot, or heavy conditions make this even more critical. Idle should be reserved for the moment you are absolutely certain you can reach the runway, even if the motor coughs.

-1,500 to -2,000 ft/min represent a -5° to -6° slope at 180 kt: it's very flat for a modern jet, that should aim around -10°.

If this is how you see the runway on final, you started your final turn too late: you are very far on final, it's nearly a straight-in...

II.5 - Landing

This is how you should see the runway at the end of the final turn.

• Short final: this is not sightseeing...

The “final” phase of an overhead break is never meant to be long. Navy aircraft typically fly a 15–18 second groove to a moving deck. On a fixed runway, anything more than about 15 seconds is already excessive. If your final looks like an airliner approach, you’ve missed the point.

Even if here the aiming point is long, you'll notice that the final phase is very short: that's totally normal in most case.

• Aiming point: the runway threshold, and even before...

What is certainly the most common and most important error in DCS tutorials is the aim point selection. You have to understand that if a "standard" runway length by NATO standards (2,400 m or around 8,000 ft) is sufficient in normal circumstances, it can quickly become too short when hardship start to add up: take a wet runway a drag chute that refuses to open, and suddenly your runway is too short for comfort...

Standard civilian markings: the aiming point if far from threshold, and the touchdown zone even farther.

That's why you want to maximize the runway length available for braking action, by aiming a touchdown point as close as possible to the threshold. In order to achieve an early touchdown, the secret is to place your aiming point slightly early before the runway threshold. Obviously, you have to take into account the potential obstacles situated before the runway, and the runway lights in particular: aiming too short might result into a collision, broken lights, and in the worse case, broken gear...

You can see on this performance chart that if a 8,000ft runway is perfectly nice with a drag chute, it can quickly become short without...

When the runway has a displaced threshold, this limitation is no more a factor, and you can aim well before the threshold. Accidentally touching down before the threshold will have no consequences in this case.

Runway with a displaced threshold. There's absolutely no obstacle preventing you from aiming "short".

As a result, you will easily understand that your height over the threshold should be minimal, and not the 50 ft AGL taught in civil aviation.

• Touchdown: it's not that fragile...

If we all agree that a beautiful "kiss landing" is satisfactory, we should also keep in mind that we want to slow down the jet as early as possible. If you correctly managed your speed until short final, you should be able to completely chop power when passing the threshold, if you did not touch down yet. This should counter the ground effect due to runway proximity. Extending the air-brakes just before touch down can also help.

The two extremes: you must find the sweet spot in between...

• Aerodynamic braking: it's not a question of choice.

Unless you’re carrying a drag chute, aerodynamic braking is advised on many aircraft. It is especially true with delta-wing airframes, that are acting like a giant airbrake. Holding the nose up after touchdown allows the aircraft to decelerate efficiently and reduces overall brake demand. With an heavy aircraft, it is even possible that a full stop is not possible without aerodynamic braking without drag chute. Slamming the nose down right after main gear touchdown, is only advised when using the drag chute that is most efficient at higher speed.

Most tutorials will tell you to aim behind the threshold, while in reality you should aim just before.

As a result, all these pilots will end up VERY high above the threshold, loosing hundred meters of usable runway.

A real pilot will initially aim BEFORE the threshold...

... and he will put his flight path marker on the threshold during the "flare" only.

III. Even more tactical approaches ?

What you read above should be considered as a baseline, that is to say the peacetime overhead that every wingman should master. If you think that stops there, you’re only halfway home. In wartime the options multiply, and the OHB can be adapted into more tactical variants designed to minimize the time an enemy has to react. Those variants go by many names: tactical break, battle break, or “Afghan-style” recoveries in Russia (we discussed it already in the tactical landing procedures during EOF). These methods are purpose-built responses to real threats.

III.1 - The "tactical break" (or "battle break")

First of all, we must admit that an arrival at 1,500 ft gives an adversary time: to hear and see you, to cue a MANPAD, to launch or vector several small UAS. The tactical break seeks to deny that lead time. It compresses the detection to engagement windows for the adversary by changing the approach altitude: very low, very fast, and executed so the aircraft are effectively over the field for the shortest possible interval.

WWII Tactical break arrival.

Without going further in details, the main characteristics of the tactical break are:

• Low-level ingress: the formation approaches low (often a few hundred feet AGL or lower, depending on the environment), fast (as fast as permissible), and with minimal radio transmission to limit detection.

• Perch/climb pull: during the break, jets perform a climbing pull into a “perch” point. It's a short apex designed to place the aircraft in the final turn with minimal predictable exposure.

• Final turn: from the perch the final turn is standard: that's where the peacetime training pays off. The last part of the landing procedures brings you back to familiar territory that you perfectly master, so as to land safely and efficiently.

Formation: line-abreast & mutual support

Since mutual support is the priority, the line-abreast formation should be preferred for tactical arrivals. Unlike in-trail recoveries, line-abreast presents a simultaneous, distributed target and allows overlapping fields of view. Wingmen can scan laterally, and small UAS or AAA must re-aim quickly to engage multiple, separated aircraft. In short: low, fast, and in battle formation reduces the ability of an adversary to engage all aircraft.

The supremacy of the line-abreast formation in the jet age is one of the hard "lessons learned" of Vietnam that remains relevant today. The pictures below (TAC ATTACK, 1977) provide clear visual references for how a two-ship and a four-ship line-abreast arrival can be flown in practice and make an excellent illustration for a tactical-arrival brief.

Note that if the line-abreast formation remains tactically sound, modern survivability thinking changes one key parameter: spacing. The previous publication recommend very tight lateral separations (1,000 ft or ≈ 0.16 NM) between elements. I would not recommend that today. For contemporary jet operations, I would increase spacing by an order of magnitude. A lateral spacing of 10,000 ft (≈1.6 NM) is a far more useful baseline: it preserves mutual support and overlapping fields of observation while keeping elements outside the short-range, minimum-engagement envelopes of many IR systems and giving crews room to maneuver if engagement occurs.

2-ship line abreast tactical break.

4-ship line abreast tactical break.

Conclusion

It’s worth recognizing why so many DCS tutorials present the overhead break as a slow, gentle maneuver: it gives the narrator time to explain each step, and it makes the sequence easier for viewers to follow. That has value in a learning context, but it must be understood for what it is: a pedagogical simplification, not an authentic representation of fighter aviation. Treat it as a learning aid only, not as the end-state of your training.

Because flying a fighter jet, even in a simulator, requires a mindset.

“Because I was inverted.” Few lines capture the fighter pilot mindset better...

First, a fighter is a high-performance machine, and its procedures are meant to be flown as such. There is no place for lazy two-G turns or hesitant stick inputs. A maximum-performance turn flown at 80° of bank, or an aggressive inverted pull to achieve the proper nose-low attitude, is not “reckless,” it’s simply using the aircraft the way it was designed. No one is spilling coffee in the backseat, and nobody should gasp because the jet went momentarily inverted: that’s normal in this world.

Second, there is no “pause” in combat. The enemy will always look to strike when you are most vulnerable, and takeoff and landing are definitely the most exposed phases of flight. These truths were recognized in the 20th century, but they are in danger of being forgotten today. The ongoing war in Ukraine is a stark reminder: in an era of pervasive drones and standoff strikes, there is no such thing as a safe rear area. Airfield operations are once again high-risk events, and training must adapt to that reality.

If you embrace this mindset in your sim flying, you’ll not only fly overhead breaks more authentically: you’ll start to think like a combat aviator. And that is ultimately the whole point of Digital Combat Simulator!