You're ten miles behind the carrier, fuel state is getting interesting, and you hear "99, Mother's weather is 200 scattered, visibility 2 miles, expect Case III recovery."
Do you know what that means? More importantly, do you know how to fly it?
Get the ball wired. Book a Carrier Recovery lesson — a tutor calls your power corrections live through Case I, II, and III approaches until the scan becomes automatic.
US Navy carrier aviation uses three standardised recovery procedures—Case I, II, and III—depending on weather conditions and time of day. Each dictates a completely different approach pattern, level of ATC control, and set of procedures. If you've been flying carrier ops in DCS by just "eyeballing it," you're missing a fundamental part of how naval aviation actually works.
Let's fix that.
An F/A-18C lined up on the catapult — carrier operations demand precise adherence to procedures from launch to recovery
Affiliate disclosure: This guide contains affiliate links. If you purchase through these links, SimTuts earns a small commission at no extra cost to you. We only recommend products we genuinely believe improve the flight sim experience.
Why Three Cases?
The core problem is simple: how do you get 20+ aircraft back aboard a ship that's moving at 25 knots, has a landing area the size of a tennis court, and might be surrounded by clouds, rain, or complete darkness?
The Navy's answer is to scale the recovery procedure to match the conditions:
- Case I - When you can see everything, keep it simple and fast
- Case II - When visibility is reduced but not gone, add some structure
- Case III - When you can't see anything, control everything
Each Case balances two competing needs: getting aircraft aboard quickly (the ship has limited time on a recovery course) and doing so safely (mid-air collisions are bad for everyone).
Case I: The Good Weather Pattern
Conditions: Ceiling at or above 3,000 feet, visibility 5 nautical miles or greater, daytime operations.
Case I is the "nice day" recovery. Pilots can see the ship, see each other, and handle their own separation. It's fast, efficient, and relies heavily on pilot skill and judgement rather than ATC control.
The Pattern
Here's how a Case I recovery flows:
-
The Marshal Stack - Returning aircraft hold overhead the carrier at or above 2,000 feet, orbiting in a left-hand pattern. This is the "holding pattern" while waiting for your turn.
-
The Break - When cleared (or at your assigned time), you descend and enter the break at 800 feet, up to 350 knots. The break is a hard left turn to bleed speed and enter the landing pattern.
-
The Downwind - After the break, you fly parallel to the ship's course on the left side, configuring the aircraft (gear, flaps, hook).
-
The Turn to Final - A continuous descending turn that rolls you out behind the ship, lined up with the angled deck.
-
The Groove - The final 15-18 seconds of flight, from "the start" to touchdown. This is where the LSO is talking to you.
Key Numbers (F/A-18C)
- Break entry: 800 feet, up to 350 knots
- Downwind: 600 feet, landing configuration, on-speed AOA
- The Start: 3/4 mile behind the ship, on glideslope
- On-speed AOA: 8.1 units (the "E" bracket on your HUD)
The Beauty of Case I
What makes Case I elegant is its simplicity. There's minimal radio chatter. Pilots maintain their own separation visually. The pattern flows continuously—aircraft enter the overhead, break, land, and clear the deck in a smooth stream.
In DCS multiplayer with multiple aircraft, a properly run Case I recovery is genuinely satisfying to watch and participate in. Aircraft stacked in the overhead, sequential breaks, everyone flowing through the pattern like clockwork.
The flip side: Case I requires good weather and good visibility. When conditions deteriorate, the whole system breaks down. Enter Case II.
Multiple aircraft on the flight deck — managing this traffic is why standardised recovery procedures exist
Case II: The Transition
Conditions: Ceiling at or above 1,000 feet and visibility 5 nautical miles or greater, but with possible IMC during the descent. May also be used during the day-to-night transition period.
Case II is the "we can still kind of see" procedure. It adds an instrument approach phase to get you close to the ship, then transitions to a visual pattern for landing.
The Pattern
-
Marshal - Aircraft hold at assigned altitudes along the final bearing (the extended centreline behind the ship), typically starting at 15+ miles and descending inbound.
-
Approach - You fly a controlled descent along the final bearing, following altitude restrictions at specific distances.
-
Platform - At approximately 5,000 feet and 10 miles, you level off and continue inbound.
-
Transition - When you break out visually (can see the ship), you enter a modified Case I pattern—either joining the overhead or proceeding directly to the downwind.
Why Case II Exists
Case II bridges the gap between "fly it yourself" and "we'll talk you all the way in." It gives you the structure of an instrument approach to get close, then lets you fly the visual pattern once you can see what you're doing.
Think of it as "instrument approach to visual landing." You might enter clouds during the descent but should break out in time to fly the pattern visually.
In DCS, Case II is often used during marginal weather scenarios or late afternoon missions when visibility is good but clouds are present.
Case III: The Full Instrument Recovery
Conditions: Ceiling below 1,000 feet, visibility less than 5nm, OR any night operations.
Case III is the "I can't see anything and I'm trusting the system to get me aboard" procedure. It's a full instrument approach from marshal to touchdown, with continuous ATC control.
This is what naval aviators train for years to master. Landing on a carrier at night in bad weather is considered one of the most demanding tasks in aviation.
The Pattern
-
Marshal - Aircraft hold at assigned altitudes in a stack behind the ship. Each aircraft is assigned a specific altitude and time to begin the approach (push time).
-
Descent - At your push time, you begin a controlled descent along the final bearing, following precise altitude/distance restrictions.
-
Platform and Dirty-Up - Level at 5,000 feet, approximately 10 miles out. Configure for landing.
-
Final Approach - Continue descent, following the approach procedure. In the F/A-18C, you're using the ICLS (Instrument Carrier Landing System) needles.
-
The Groove - Same as Case I/II, but you may not see the ship until very late. The ICLS and ACLS (Automatic Carrier Landing System) guide you down.
The Marshal Stack
In Case III, the marshal stack is carefully orchestrated. Aircraft are stacked at 1,000-foot intervals, with the lowest aircraft closest to the ship. Each aircraft has an assigned push time.
When you push, you descend at a prescribed rate. The aircraft that was above you pushes one minute later. This creates a stream of aircraft, each separated by one minute and 1,000 feet, flowing toward the ship.
ICLS and ACLS
ICLS (Instrument Carrier Landing System) provides needles on your HUD—similar to an ILS approach to a runway. A glideslope needle tells you if you're high or low; a localiser needle tells you if you're left or right.
ACLS (Automatic Carrier Landing System) can actually fly the aircraft to touchdown automatically (Mode I) or provide cockpit display guidance via crossbar/needle that the pilot hand-flies (Mode II). In Mode I, you're essentially a passenger—the system flies the jet onto the deck.
Most pilots hand-fly using ICLS needles, with ACLS as backup. But on the darkest, worst-weather nights, Mode I ACLS approaches happen.
The Night Trap
Landing on a carrier at night is famously disorienting. There's no horizon. The ship's lights are the only reference, and they can create optical illusions. Pilots report that the deck seems to move unpredictably, that closure rates are impossible to judge, that every instinct screams "this is wrong."
The only way through is to trust your instruments, trust the LSO, and fly the needles. The moment you start chasing visual references you can't really see, you're in trouble.
In DCS, night Case III approaches are genuinely challenging. Turn up your gamma and you're cheating yourself of the experience. Fly it properly dark and you'll understand why naval aviators consider night traps a unique skill.
Quick Reference Summary
| Condition | Case | Pattern Type |
|---|---|---|
| Day, ceiling 3,000+, visibility 5nm+ | Case I | Visual overhead pattern |
| Day, ceiling 1,000+, vis 5nm+, possible IMC in descent | Case II | Instrument to visual transition |
| Night OR ceiling <1,000 OR vis <5nm | Case III | Full instrument approach |
Deck crew coordinate aircraft movements — the organised chaos of carrier operations in DCS
Setting Up Cases in DCS
For Case I practice:
- Set weather to clear, time to midday
- Start 10nm behind the carrier at 2,000+ feet
- Practice the overhead pattern and break
For Case II practice:
- Set weather with a ceiling around 2,000 feet
- Start at marshal (15nm behind, 5,000+ feet)
- Practice the instrument portion, transition to visual
For Case III practice:
- Set time to night, weather as desired
- Start at marshal stack altitude
- Practice full instrument approach using ICLS needles
The Supercarrier module adds significant realism to all of this, including proper ATC communications, IFLOLS (the "meatball"), and enhanced deck operations.
Common Mistakes
Case I:
- Breaking too early or too late (should be at the bow)
- Getting slow on downwind before configuring
- Flying a square pattern instead of a continuous turn to final
- Descending below pattern altitude before the turn
Case II:
- Not knowing the altitude restrictions at each distance
- Trying to go visual too early (before breaking out)
- Forgetting to dirty-up at platform
Case III:
- Chasing the needles instead of making small corrections
- Looking for the ship too early (fly the instruments until you're in close)
- Not trusting ICLS—your eyes will lie to you at night
- Poor power management in the groove
The Discipline of Procedures
Naval aviation has procedures for everything because procedures save lives. The Case system exists because controlled chaos is better than uncontrolled chaos, and because instrument procedures let you operate when visual procedures can't.
When you fly Case III in DCS and catch the wire on a pitch-black night, you've done something that real naval aviators spend entire careers perfecting. It's not the most glamorous part of carrier aviation—nobody makes movies about the instrument approach phase—but it's where the professionals separate themselves.
Master all three Cases, and you're not just landing on carriers. You're operating like the Navy does.
A note on hardware: Flying the ball lives and dies on precise throttle and seeing the lens. A Thrustmaster T16000M FCS HOTAS gives you the smooth throttle micro-corrections that holding on-speed AoA in the groove demands, and head-tracking — TrackIR 5, the Tobii Eye Tracker 5, or a VR headset like the Meta Quest 3 — keeps the meatball and lineup in view through the groove. Rudder pedals make lineup corrections far easier.
Carrier operations are complex, and there's no substitute for practice with feedback. If you're struggling with carrier landings—especially night traps—consider booking a session with one of our experienced naval aviation tutors. Real-time LSO calls and pattern coaching can compress weeks of solo practice into a single session.
