General/CATC Communications Guide
From SOURCE DCS WIKI
More actions
Carrier Air Traffic Controller (CATC) Communications Guide
Created by 14th VSFS Top Hatters
Information is based on real-world procedures but modified to cater to DCS limitations
Brevity Words / Glossary
- Angels
- Height of an aircraft in thousands of feet MSL (e.g. Angels 2, Angels 21)
- Mom / Mother
- The aircraft carrier
- Signal is Charlie
- Cleared to commence/land
- Signal is Delta
- Do not commence/land
- Ninety-Nine
- A message to be conveyed to all stations on frequency (no acknowledgement required)
- State
- Fuel state expressed in thousands of pounds (e.g. "State 12.4")
- Low State
- Fuel state expressed in thousands of pounds of the member in the flight/formation with the lowest fuel (e.g. "Low State 3.5")
- DME
- Distance Measuring Equipment. Used to indicate distance in nautical miles from a navaid such as TACAN or VOR. (e.g. "...at 12 DME from carrier switch to tower")
- Dirty Up
- Configure aircraft for landing (flaps, gears, etc.)
- Kilo
- Aircraft is in a mission ready state (only applies to CASE III)
- EAT
- Expected Approach Time (push/commence time)
- CCZ / CCA
- Carrier Control Zone / Carrier Control Area
- Commencing
- Continuing with an approach, usually breaking off a marshal stack
- Zip-Lip
- No communications required unless urgent and necessary
General Information
- CCZ is 5nm from mom extending from SFC to 2500ft and is in effect during CASE I and CASE II
- CCZ is controlled by PriFly which consists of:
- Tower — Responsible for pattern traffic, briefing "Up on deck" aircraft with "99" calls (or individually), and giving signal charlie to overhead stack in case 1
- LSO/Paddles — Responsible from final approach to trap/bolter for arriving aircraft, gives audio cues and guides to pilots
- CCZ is controlled by PriFly which consists of:
- CCA is 50nm from mom extending from surface to infinity, subject to change from surrounding airspace which usually take priority
- CCA has multiple manned stations depending on CASE being used and traffic density:
- Marshal — Responsible for issuing marshal stacks and ensuring separation between commencing aircraft is timed correctly. Fuel state should be updated constantly to the stat board especially those with low fuel states.
- Approach 1 — Only exists during Case II and III. Takes control of aircraft between Commence and Platform all the way down until LSO assumes control.
- Approach 2 — Same as Approach 1 but is only used if heavy recovery traffic is expected and/or as a discrete frequency for emergency aircraft.
- Departure — Only exists during Case II and III. Has control from time the aircraft is airborne until "Kilo" is reported, at which point the controller can send the aircraft to appropriate tac freq (in our case, magic). Controller can delay freq switch after "Kilo" if further services are needed, but must be before leaving CCA.
- LSO/Paddles — Monitors frequency and takes over when aircraft is entering groove, at which point LSO has priority on radio until aircraft has either trapped or boltered.
- CCA has multiple manned stations depending on CASE being used and traffic density:
- On initial contact include flight tactical callsign along with side number to ensure aircraft is from the correct fighter wing
- E.g. "Hat 123 checking in…" / "Ripper 123 marking mom's…"
- If unable to make commence time within +/- 15s report to marshal immediately
- "Marshal, 104 is early/late for commence time"
- Side numbers should have the same initial number within the same flight
- For example, Hat = 1xx, Ripper = 2xx, Psycho = 3xx
- Last 30 seconds of time hack should not be interrupted unless necessary
CATCC Specific Information
- DIRTY UP (command from CATC) LIMITS ARE NO EARLIER THAN 13 MILES AND NO LATER THAN 8 MILES
- At 8nm aircraft will dirty up automatically if no dirty up instruction was received within the dirty up window (13nm–8nm)
- Minimums for PAR approaches is 1¼ mile; at this point aircraft has to report BALL/CLARA and LSO takes over. If LSO has no contact visually then aircraft has to waveoff.
- If aircraft reports CLARA but LSO has contact, approach may continue at LSO discretion
- CATCC should have a "Status Board" which is used to monitor flights fuel state and urgency
- LotATC comments on aircraft tag should suffice for now
- Case I departure allows Case I, II, and III recovery. Case II departure allows a Case II or III recovery; a Case III departure mandates a Case III recovery.
- Case II recovery allows for 2-ship in marshal
- This is risky — see 28:45 for explanation
- There are four degrees of control a CATC controller has:
- Positive control — The controlling agency has radar and radio contact with the aircraft being controlled, and published approach or departure procedures are complied with, or where specific assignments regarding heading and altitude are issued by the controller. While the pilot provides altitude separation by maintaining assigned altitudes, the air traffic controller is responsible for lateral and time separation. The air traffic controller may direct speed changes.
- Advisory control — The controlling agency monitors radar and radio contact with the aircraft under its control and provides traffic advisories. The individual pilot is responsible for traffic separation with the assistance from the control agency.
- Monitor control — Must only be used when an aircraft is operating in VMC outside of controlled airspace and separation from other traffic can be safely assumed by the pilot.
- Non-radar control (rare) — When shipboard radar is INOP; very unlikely on DCS.
- The recommended way to create separation between aircraft after commencing is to employ a method called "lagging". To "lag" an aircraft, approach instructs a series of left and right turns, ideally 30 degrees or less. Once desired separation is achieved, aircraft can be instructed to "fly final bearing". This is preferred over the "dirty up" method (depending on the situation) because once an aircraft dirties up, they must remain at approach speed and landing configuration for the rest of the approach.
- In case 1 and 2, aircraft cannot be sent to tower frequency unless aircraft has called visual. Marshal and approach controllers are not obligated to handover aircraft to tower when they are visual with mom but it has to be switched prior to entering the CCZ (5nm).
- For case 2 and 3 departure, the arc and departure radial is only required when aircraft are in IMC. Once aircraft is in VMC and reports "on top", the departure controller is free to allow aircraft to continue own navigation (advisory control) or remain on positive control.
- If giving 99 transmission on check in and controller is not ready for time hack, "standby time hack" can be used.
- Time hack on ground should be given after all aircraft are "up on deck", otherwise this will have to be repeated for any new aircraft that missed the time hack. Ideally, every plane that launches from the carrier has to be time hacked.
- Anytime a major change happens to anything like BRC, weather, departure, etc., use "99" to announce
- 99's don't require acknowledgement from anyone
- "Ninety-Nine, *Lone Warrior*, (insert message)"
- For case 3, controllers maintain positive control until aircraft reports "Kilo"
- Refrain from saying climb or descend; if need to assign altitude say "Take angels 7" or "Take angels 2.5"
- To issue heading changes, do not say "turn", only say left/right followed by a magnetic heading: "Left 290", "Right 050"
- LSO will be on the frequency that aircraft are on when in the last few miles to recover. For CASE I and II this is on tower (PriFly); for CASE III LSO will be on approach freq.
- Once aircraft is on the ball and paddles contact, LSO has complete priority on frequency
Phrases marked with *(message)* are optional and may be used when workload and frequency congestion permit for situational awareness.
CASE I Departure
| Station | Phrase |
|---|---|
| Pilot | Tower, XXX, Up on deck |
| Tower | XXX, Tower, Roger |
| Tower issues "99" transmission once all aircraft has checked in | |
| Tower | Ninety-Nine, Lone Warrior, CASE ___ launch, expected BRC ___, mother's weather ___, altimeter __.__, primary divert as briefed. Time in (at least 40s) seconds __, time in 30 seconds __, time in 15 seconds __, 5, 4, 3, 2, 1, MARK!..... time __ |
| When ready to taxi | |
| *Pilot* | *XXX, Taxiing to CAT __* |
| *Tower* | *XXX* |
| Once hooked on catapult and ready | |
| *Pilot* | *XXX, Salute* |
| Zip-Lip for remainder of CASE I departure | |
| Flights can switch off BTN 1 at their discretion once clear of CCZ | |
Notes
- "99" transmission has to be done after all aircraft has checked in but before the first aircraft launches
- "Up on deck" call should be made as soon as electrical power is established (usually via ground power)
- Minimum 10 second launch interval if aircraft are on same-side cats (e.g. cat 1 + cat 2 launches need a 10 second interval; cat 1 + cat 3 do not)
CASE I Recovery
| Station | Phrase |
|---|---|
| When 60–50nm from Mom | |
| Pilot | (Mom tac callsign) marshal, (tac callsign) XXX (report if holding hands), Marking mother's (radial) for (DME), angels __, (low) state __._ |
| Marshal | (Tac callsign) XXX, (Mom tac callsign) Marshal, CASE 1 recovery, BRC is __, Mother's Weather ___, Altimeter __.__, marshal angels ___, report see me at 10 |
| Pilot | CASE 1 recovery, BRC ___, Altimeter __.__, marshal angels _, XXX |
| When within 10 DME AND visual with Mom | |
| Pilot | XXX, See you at (DME) |
| Marshal | XXX, update state, check in tower button 1 |
| Pilot | Tower, XXX, (low) state __._ |
| Tower | XXX |
| When carrier is ready to accept recoveries | |
| Tower | XXX, signal is charlie |
| Pilot | Signal is charlie, XXX |
| When commencing from stack | |
| *Pilot* | *XXX, commencing* (unrealistic but mandatory) |
| 3NM behind Mom, 800ft, 350kias | |
| *Pilot* | *XXX, at initial* (if in IMC this call is required) |
| When IFLOLS (ball) AND lineup can be CLEARLY seen | |
| Pilot | XXX, (Aircraft name) ball/clara, state __._ |
| LSO | Roger Ball/Clara! |
| If pilot doesn't make ball call before ¾ mile | |
| LSO | XXX, Three quarter mile call the ball |
| Pilot | XXX, (Aircraft name) ball/clara, state __._ |
| LSO | Roger Ball/Clara! |
| CASE I BOLTER / WAVEOFF | |
|---|---|
| LSO | WAVE-OFF! / BOLTER BOLTER BOLTER! |
| Technically bolter/waveoff procedures are completely zip-lip. Aircraft are to visually fly the bolter procedure and are responsible for maintaining visual separation with all aircraft. | |
Notes
- Stack can accommodate 4-ship (in formation) at each angels but not recommended unless flight lead is confident in tight formation skills with all members for extended periods of time (2-ship max is recommended)
CASE III Departure
| Station | Phrase | |
|---|---|---|
| Departure radial and altitude should have been determined in pre-brief | ||
| Pilot | Tower, XXX, Up on Deck | |
| Tower | XXX, Tower, cleared as Fragged. Case 3 departure. *Departure Radial ___ , Angels___* [a] Altimeter __.__ Squawk ____. | |
| Pilot | Case 3, *Departure Radial ___, Angels__*, Altimeter __.__, Squawk ____, XXX | |
| Tower | Readback correct | XXX, negative (repeat clearance) |
| Tower issues "99" transmission once all aircraft has checked in | ||
| Tower | Ninety-Nine, Lone Warrior, CASE ___ launch, expected BRC ___, mother's weather ___, altimeter __.__, primary divert as briefed. Time in (at least 40s) seconds __, time in 30 seconds __, time in 15 seconds __, 5, 4, 3, 2, 1, MARK!.... , time __ | |
| Once Ready for Taxi | ||
| *Pilot* | *XXX, taxiing Cat __* | |
| *Tower* | *XXX* | |
| Once hooked on catapult and ready | ||
| *Pilot* | *XXX, Salute* | |
| Once airborne | ||
| Pilot | Departure, XXX, Airborne | |
| Departure | XXX, Departure, radar contact | |
| When passing Angels 2.5 | ||
| Pilot | Departure, XXX, Passing 2.5 | |
| Departure | XXX | |
| When reaching 7 DME | ||
| Pilot | XXX, Arcing | |
| Departure | XXX | |
| When established on departure radial | ||
| Pilot | XXX, Established outbound | |
| Departure | XXX | |
| If in IMC and now VMC | ||
| Pilot | XXX, On top, angels __ | |
| Departure | XXX | |
| If not VMC at departure angels or by angels 18 | ||
| Pilot | XXX, Popeye | |
| Departure | XXX (refer to notes) | |
| When Aircraft is Mission Ready | ||
| Pilot | XXX, Kilo | |
| Departure | XXX, cleared to switch | XXX, roger |
| Pilot | Cleared to switch, XXX | |
[a] Only issue radial and angels if not previously determined, or if changes have been made
Notes
- 30 second launch interval regardless of cat positions
- If Popeye is reported, ATC should assign aircraft to take angels 19 (or climb above a known cloud ceiling where aircraft can proceed VMC), with each following member taking one angels above. They will proceed as single ships under positive control until in VMC (aircraft reports "on top"), at which point departure will decide the appropriate action.
CASE III Recovery
| Station | Phrase | |
|---|---|---|
| When 60–50nm from mom | ||
| Pilot | (Tac callsign) Marshal, (Tac callsign) XXX checking in (holding hands with), marking mom's (radial) for (DME), (low) state _._ | |
| Marshal | (Tac callsign) XXX, (Tac callsign) Marshal, CASE 3 recovery, CV-1 approach, expected final bearing ___, altimeter __.__ (repeat following clearance for each flight member) XXX, Marshal (Radial), (DME) miles, angels __, Expected approach time __, approach button 15 | |
| Pilot | XXX, Marshal (radial), (DME) miles, angels __, Expected approach time __, approach button 15 | |
| Marshal | XXX, Readback correct | XXX, negative (repeat clearance) |
| Formation splits are at flight lead discretion, unless directed by marshal | ||
| Once established on assigned marshal stack | ||
| Pilot | XXX, Established angels __, state _._ | |
| Marshal | XXX | |
| When commencing on +/- 15 sec of EAT | ||
| Pilot | XXX, Commencing, state _._, altimeter __.__ | |
| Marshal | XXX, radar contact __ miles, final bearing __ | |
| Pilot | XXX | |
| Transfer to Approach (anytime before PLATFORM) | ||
| Marshal | XXX, switch approach, check in button 15 | |
| Pilot | XXX | |
| Pilot | Approach, XXX, checking in (DME) miles, state _._ | |
| Approach | XXX, final bearing ___ | |
| Pilot | XXX | |
| Dirty Up Instruction (between 8–13nm) | ||
| Approach | XXX, dirty up | |
| Pilot | XXX, getting dirty | |
| If no "dirty up" command is given, aircraft will dirty up at 8nm automatically | ||
| Start ICLS approach (between 4–6nm) | ||
| Approach | XXX, fly bullseye | |
| Pilot | XXX (if bullseye not showing say "negative bullseye") | |
| When IFLOLS (ball) AND lineup can be CLEARLY seen | ||
| Pilot | XXX, (Aircraft name) ball/clara, state __._ | |
| LSO | Roger ball/clara! (wind over deck) knots | |
| If pilot doesn't make ball call before ¾ mile | ||
| Approach | XXX, three quarter mile, call the ball | |
| Pilot | XXX, (Aircraft name) ball/clara, state __._ | |
| LSO | Roger ball/clara! (wind over deck) knots | |
| CASE III BOLTER / WAVEOFF | |
|---|---|
| LSO | WAVE-OFF! / BOLTER BOLTER BOLTER! |
| Aircraft will fly 150kt at 1200ft straight out on final bearing | |
| Approach | XXX, turn downwind / turn downwind at (DME) miles |
| Pilot | XXX, (readback instruction) |
| If no instructions are given, aircraft will automatically turn downwind at 4nm | |
| Once aircraft is abeam carrier | |
| Pilot | XXX, abeam, state _._ |
| Approach | XXX, intercept final bearing at (DME) miles (minimum 4nm) |
| Pilot | (DME) miles, XXX |
| If no instructions are given, aircraft will turn to intercept final bearing at 4nm | |
Notes
- The flight lead should identify the member with the lowest fuel state and clearly specify the recovery order, or at minimum, designate who will commence first.
- For controllers: Make sure the aircraft lowest in the stack commences first, set approach times accordingly.
LSO/Paddles Phraseology
- For LSO, if aircraft is seen configured incorrectly such as no hook, no gear, or abnormal/damaged gear, "waveoff, waveoff" command is given immediately, followed by the reason e.g. "waveoff waveoff, nose gear not fully extended"
- LSO will be on the frequency that aircraft are on when in the last few miles to recover. For CASE I and II this is on tower (PriFly); for CASE III LSO will be on approach freq.
- Once aircraft is on the ball and paddles contact, LSO has complete priority on frequency
Appendix: Comm Presets & Reference
Known Comm Presets
| Button | Station |
|---|---|
| 1 | Tower/Paddles (PriFly) |
| 2 | Departure |
| 3 | Strike |
| 4 | Red Crown |
| 5–9 | Various Tactical/Mission/CVW discrete freqs |
| 10 | Squadron Tower/CATCC rep |
| 15 | Approach 1 |
| 16 | Marshal |
| 17 | Approach 2 (if more than one was needed or discrete for emerg. aircraft) |