Channels and Frequencies
This is the default comms plan for missions.
Mission specific channels (11 through 13) are used to fit the scenario of a mission. These may include additional tankers, airport towers & ground, specific tasking channels, JTAC etc. If used for a mission, the table will be updated with said channels' functions in the mission event page.
These common channels are called the PRI (primary) channels. They are used on Com1 (i.e the left radio in the Hornet).
|2||Carrier Tower (AI)||264.00|
|4||Carrier Red Crown||256.00|
|9||AWACS Check In||255.00|
|11||Air Force Sec Tanker (AI)||259.00|
|12||Navy Sec Tanker (AI)||268.00|
|14||Navy Main Tanker (AI)||260.00|
|15||Carrier Approach A||263.00|
|17||Carrier Approach B||267.00|
|19||Carrier Overhead Tankers (AI)||253.00|
|20||Air Force Main Tanker (AI)||266.00|
This is the standard comms table for AJS 37. Note that there's no AJS 37 preset for Ground. It has to be manually set to 250.00.
|E||AWACS Check In||255.00|
The AUX frequencies are used by flights for intraflight comms. These are not presets. You have to manually tune your AUX radio to the correct frequency. The frequencies start at 130.10 and increases by .10 for each flight, corresponding to that flight's number.
Com2 (i.e the right radio in the Hornet) is used for this. As a flight lead, you may instead opt to use Teamspeak for intraflight comms. (If you do, the recommendation is to use TS instead of the AUX radio, not using TS as third radio)
Common Radio Procedures
When the flight lead wants its flight to switch to a new channel (or specific frequency), he declares it on the frequency they are currently on. That way, the flight know where to go, and the controller of the frequency knows that you're now leaving. The brevity is "[Flight callsign], [Channel (or freq) to go to], push!].
Example: (Camel3, flight of four Hornets, is on channel 14 after finishing their aerial refueling, and should now go to channel 3 (package channel).
Camel31: "Camel Three, button 3, push!"
Note: The terms "Button" and "Channel" are used interchangeably. "Button" sounds a little more US Navy than "Channel" and we tend to use that, but it doesn't matter.
After a flight enters a new PRI channel, they should "check in". This is done by having the leader say "[Flight name and number]". The wingmen then simply reply (on the channel they are entering) with their numbers in the flight. Note that you should not say the words "check in" or "checking in" at any point.
Example: (Camel3, flight of four Hornets, checks in on Package channel)
Camel31: "Camel Three" Camel32: "Two!" Camel33: "Three!" Camel34: "Four!"
Exception: During CASE 1 carrier procedures, flights do not check in on the tower channel (1) before the recovery. The check in is implicit, and nothing is said on the radio.
Contacting controlling agency
After a flight has checked in for the first time, it is common (and in the case of the Package channel, mandatory) to contact the controlling agency on that channel. The most common situation is that a flight has checked in on the package channel and contacts AWACS. Let the controlling agency know your airframe count, your position and any other relevant information (for instance fuel state on lowest flight member, tasking, any technical issues and so on). If some of these things should already be known by the controlling agency (because they are pre-briefed) and they haven't changed, you don't need to mention them, but instead state "as fragged".
Example: (Camel3, flight of four Hornets on CAP tasking, has just checked in and now contacts AWACS "Stingray" on Package channel)
Camel31: "Stingray, Camel31, marking bullseye 270 for 35 at angels 28, lowest state 10.8, as fragged!" Stingray: "Camel31, Stingray, radar contact, continue as fragged."
This is not always used, but sometimes a controlling agency may ask a flight (or vice-versa) to authenticate themselves to prove that they are friendly. When this happens, we're using a system called "RAMROD". It works by having a certain phrase communicated to all parties in the briefing. The phrase is then used as a key to be able to correctly reply to the querying instance's authentication request. The query consists of two letters from the phrase, with exactly one letter between them. The letter in between is the correct answer. Note that the phrase is assumed to "wrap around", meaning the first letter in the phrase is located between the last and the second letter.
Example 1: (Stingray asks Camel3 for authentication. The prebriefed RAMROD key is "MONKEYSPIT")
Stingray: "Camel3, authenticate October Kilo!" Camel31: "Stingray, Camel31 authenticates November." Stingray: "Camel3, approved."
Example 2: (Same situation)
Stingray: "Camel3, authenticate India Mike!" Camel31: "Stingray, Camel31 authenticates Tango." Stingray: "Camel31, approved."
When flying in events (and preferably during casual flying), you are expected to turn on your transponder and enable Mode 3 using a certain code. The way it's done is different in every aircraft. We use a simple system for knowing what code to use.
- During training events, you should use 0 + your sidenumber. If your sidenumber is 403, you should input 0403.
- During mission events, you should use 1 + your sidenumber. If your sidenumber is 403, you should input 1403.
Following these instructions, your callsign will automatically display for our ATC and AWACS people using the standalone program LotATC, saving them lots of trouble.
Here is a list of brevity that is good to learn! Brevity