2023-09-24T13:29:48Z

Mags: Skapade sidan med '==Basic 2-ship BVR tactics== Motivation: Understand and apply basic 2-ship BVR tactics Components: Formation, MAR/DOR, communication, mutual support, differences from single...'

==Basic 2-ship BVR tactics==

Motivation: Understand and apply basic 2-ship BVR tactics

Components: Formation, MAR/DOR, communication, mutual support, differences from singleton BVR

Not covered: Advanced aircraft performance, advanced weapon efficiency

Prerequisites: Knowledge of your aircraft's performance, basic radar operation, basic A/A missiles employment

Progression: Advanced 2-ship BVR tactics, weapon employment and combat efficiency

===Tactical imperatives===

* Keep weapons and a radar pointed in threat direction at all times.
* Stay out of Minimum Abort Range, as long as possible or until you decide to transition to a WVR engagement.

===Arriving on station===

Fly in chosen formation to station. About 20 NM from station, wingman performs a 360 or a dog-leg to separate roughly 20 NM in a trail. Enter CAP racetrack hold with hot leg in threat direction.

Radials

2023-09-12T17:54:56Z

Mags: /* Suggested exercise */

''[[Home]] >> [[Standard Operating Procedures]] >> [[Radials]]''

==What is a radial?==

A radial is a compass bearing '''from''' a point. Usually from an airfield, TACAN station, VOR station or carrier.

Together with a range and altitude component, it is often used to describe where airplanes are located relative to an airfield, TACAN station, a carrier or bullseye. The first component of a bullseye call - the compass bearing from the bullseye - is a radial.

<div style="clear: both"></div>
[[Fil:Radials.jpg|300px|thumb|left|Radials and locations relative to an airfield]]
<div style="clear: both"></div>

==Important facts to note==

The heading of an airplane has nothing to do with its radial, just like roll and pitch of the aircraft are unrelated to its position. Heading, pitch and roll will affect how the location of an aircraft ''changes over time'', but is not needed to describe its ''current location'' relative to something else.

The heading of a carrier has nothing to do with radials relative to its TACAN station. The radial is a ''compass'' bearing from the carrier's location, regardless of whether the carrier is heading east or west etc.

==To fly on a radial==

When an aircraft is said to be "flying on a radial", it means that it remains on that radial. There are a couple of ways to fly a radial:
* Fly outbound on a radial
* Fly inbound on a radial
* Be anchored on a radial and distance - orbiting a certain point
* To marshal in a racetrack on a radial - meaning you are moving up and down a radial

<div style="clear: both"></div>
[[Fil:Radials on.jpg|300px|thumb|left|Different ways to "fly on a radial"]]
<div style="clear: both"></div>

==When are radials used?==

* During radio communications and navigation around airfields on arrival or departure - both for describing current positions, and for positioning flights
* During radio communications and navigation around carriers - especially CASE 3 operations
* Bullseye calls for describing flight locations relative to a predetermined "bullseye" location in the theatre of operations

==Examples of radial usage in communications==

''Kutaisi, Indy9 marking your 080 (radial) 35 miles angels 20''

The flight Indy9 lets Kutaisi know that they are located 35 miles away in the 080 bearing from the Kutaisi airfield.

''Picture: One group, bulls 350 (radial) for 50, angels 31, heading south''

A group of aircraft is located roughly 50 miles north of the bullseye.

''Indy91, Union Marshal, marshal on the 230 radial, 26 miles angels 11''

The carrier marshal is telling Indy91 to position itself on the 230 radial 26 miles from the carrier.

==Suggested exercise==

The following is an exercise that will test your understanding of radials. Make sure your flight is being recorded by Tacview, then fly the route.

# From Kutaisi, fly outbound on radial 120 until 40 NM, 30 000 ft.
# Position yourself on radial 180, 50 NM. Perform three orbits on that position.
# Position yourself on radial 220, 60 NM. Fly two laps with 6 NM legs.
# Position yourself on radial 270, 60 NM. Then fly inbound on that radial towards Kutaisi until you are overhead Kutaisi (directly above the airfield).
# Send the Tacview file to a mentor or instructor for review+feedback.

==How to read radials in various aircraft==

Generally, you will have a navigation instrument that shows the bearing towards a waypoint or navigation beacon. The radial you are on is simply the reciprocal (opposite) of that bearing. Many navigation instruments (HSIs) will have a marker to help you read this opposite bearing.

===F-16C===

[[Fil:Ehsi tcn out.jpg|360px|thumb|left|Reading your radial in F-16C]]

Mission Design Guide

2023-09-08T07:07:58Z

Mags: /* Bullseye placement */

''[[Home]] >> [[Mission Design Guide]]''

==Goals==

* Make it a smooth process for mission designers to create new missions.
* Establish standard configurations for things such as callsigns, comms and TACAN channels.
* Provide workarounds for common DCS problems, such as loss of TACAN.
* Provide tips for how to design a fun mission.

==Game Options Considerations==

Some settings that you set in the game's options (available through the DCS main menu) are copied into the actual mission. You need to make sure the following is setup in your options:

* Gameplay / Wake Turbulence OFF
* Gameplay / Easy Communication OFF

==Mission Editor Considerations==

===Mission Template===

[[Fil:Flights_THT.png|400px|thumb|Lineup]]

To make things easy, you can download a template .miz file that has all the basic stuff already setup for you. This will most likely save you quite a lot of time.

The template includes:
* Supercarrier with correct frequencies and TACAN.
* Deactivatable backup carrier.
* F10 menu controlled script that lets us reactivate the TACAN and ILS in case it shuts down because of a bug.
* Moose framework.
* Five tankers with patterns and correct frequencies.
* E-3 AWACS.
* 21 flights of F/A-18C, F-14A/B, AJS 37, A-10C, F-16C, Mirage 2000, UH-1H, AH-64D and Ka-50.
* F-14s and A-10s have comms preset synchronized with other aircraft types as per Master Arms standards.
* All aircraft have unique modex/tailnumbers as well as laser codes matching the included kneeboard.
* Enemies that can be spawned through LotAtc.
Download it here:
* [https://wiki.masterarms.se/images/9/9c/MA_MissionTemplate_CA_6_3.miz Caucasus Mission Template 6.3]
* [https://wiki.masterarms.se/images/d/d8/MA_MissionTemplate_PG_6_3.miz Persian Gulf Mission Template 6.3]
* [https://wiki.masterarms.se/images/6/66/MA_MissionTemplate_SY_6_3.miz Syria Mission Template 6.3]
* Written briefing template: [[Mission Briefing Template]]

===Detailed Basic Instructions===

This section covers all the things that should be considered in all missions. If you're using the mission template, most of this stuff is already taken care of.

====Carrier Setup====
''The mission templates already have these things set up.''
* Use ship number for TACAN (72X for CVN-72) and 264.00 for AI comms.
* Use the method showcased in the template .miz to allow for TACAN and ILS reactivation.
* If you have wind, make sure that the carrier route makes the carrier steam ''into'' the wind. No carrier cross-wind.
* The wind-over-deck speed should be around 25 kts. If you have zero wind, set the speed to 25. If you have 10 kts of headwind, set the speed to 15 kts.
** If you change the wind, you may need to tweak the carrier's heading and speed. Use this tool to know what approximate heading and speed is recommended for any given wind setting. https://magwo.github.io/carrier-cruise/
* To calculate the BRC, you need to work some magic because of true vs magnetic heading differances.
** In Caucasus and in Syria, take the course you see in the ME minus 6. Example: Boat is heading 000. BRC is 353.
** In Persian Gulf, take the course you see in the ME minus 2. Example: Boat is heading 000. BRC is 358.

====Flight Callsigns====
''The mission templates have flight names set to Arctic1, Bender2, Crimson3 and so on by default, and you are recommended to keep them. Feel free to be creative and change them, but if you do, a new custom transponder json file will have to be created for your mission, making things more complicated.''

Using the callsigns in the templates make things easier. Here is a spreadsheet with the flights available in the templates:
* [https://docs.google.com/spreadsheets/d/1C_Cu42DHHPnOjoe6QEh-Vef0yCF0RqlnCd3AfM36kDw/edit?usp=sharing Master Arms Mission Template Flights on Google Drive]

Here are a few guidelines:
* Unless there's a good reason for not doing so, use incremental numbers on the flights. If you have three flights and want to use the names Adam, Boxer and Charlie, call them Adam1, Boxer2 and Charlie3.
* Don't use callsigns that are too similar to each other. For instance avoid using two callsigns starting with the same letter (like Viper and Victor).
* Avoid callsigns that are easily associated with a certain aircraft type, if the flight flies something else. For instance, don't have an F-16 flight called Stinger1 or an F/A-18 flight called Viper2 or Falcon3.

''The mission templates have flight names set to Arctic1, Bender2, Crimson3 and so on by default.''

====Tanker Setup====
''The mission templates already have these things set up.''
* Navy aircraft (F/A-18C and F-14B) use "probe-and-drogue" refueling. They can refuel from KC-135 MPRS and KC-130.
* Air Force aircraft (F-16C, F-15C, A-10C) use "flying boom" refuling. They can refuel from KC-135 only (note: NOT the MPRS version).
* We normally never use the S-3 tanker because of various reasons.
* Be advised that the KC-130 carries significantly less fuel than the KC-135 MPRS and as such, can refuel fewer aircraft before it heads home.
* You may want to add a two-ship HAVCAP that escorts the main tankers.
* To setup a tanker pattern, add two waypoints (1 and 2) in addition to the starting waypoint. On WP1, add an action "ORBIT / RACE-TRACK". The tanker will fly in a race-track between WP1 and WP2.
* For tankers at about 15000-17000', a ground speed of 360 kts is good. Don't forget to set this speed in the Orbit Waypoint action as well.
* We recommend setting the tankers' "Reaction to Threat" setting to "Passive Defence".
* In most missions, you should setup three (or more) tankers:
** 1) Navy overhead tanker using Ch 14 (260.00). Could be KC-135 MPRS or a KC-130. Recommended callsign "Arco1" and TCN 101Y.
** 2) Air Force main tanker using Ch 20 (266.00). Always a KC-135. Recommended callsign "Texaco2" and TCN 102Y.
** 3) Navy overhead tanker using Ch 19 (253.00). Could be KC-135 MPRS or a KC-130. Recommended callsign "Shell3" and TCN 103Y.

====AWACS Setup====
''The mission templates already have these things set up.''
* There are two different EW aircraft. E-2D Hawkeye and E-3 Sentry. We recommend using the E-3 because of its superior radar coverage.
* Put the aircraft in a location between the airfield or carrier and the enemy AO, in such a way that it can be protected by friendly forces if needed.
* E-3 normally flies at around 29000' at 0.75M.
* E-2D normally flies at around 22000' at 250 kts indicated airspeed.
* You may want to add a two-ship HAVCAP aircraft that escorts the EW aircraft.
* Set the AWACS frequency to 251.00. Normally we have a human acting AWACS on Ch 3 (265.00). Channel 18 (251.00) is the AI AWACS channel (normally not used).
* We recommend setting the aircraft's "Reaction to Threat" setting to "Passive Defence".

====Bullseye placement====
Pilots and AWACS often need to describe locations relative to a known pre-briefed location, called the bullseye.

* Place the bullseye between friendly airspace and enemy airspace, 20-100 NM from anticipated engagement area.
* If possible, place the bullseye on a geographically well-known, visually spottable location such as a city, village, bridge, mountain or airfield.
* Don't place the bullseye on a target area. It causes impractically large bearing changes when aircraft are moving around the target area.

====Radio Presets====
''The mission templates already have these things set up.''
* As far as it is possible, all aircraft should have the same radio presets for the UHF radio. It should follow the Master Arms standard [[Comms]] plan, which is identical to the DCS standard list for F/A-18C and F-16C (305.00, 264.00, 265.00 and so on).
* Normally, you only have to change F-14 and AJS 37 flights.
* AJS 37 flights should have Special 1: 270.00, Special 2: 257.00, Special 3: 265.00

====Mission Customization====
''To allow for convenient testing, the mission templates don't have F10 View set to "Map Only", so you need to change it manually.''
* Buildings can not be seen in TacView. So if you have buildings as targets, put a Russian Infantry in the roof, and set WP 0 to "Set Option/ROE/Weapon Hold" and "Perform Task/HOLD", to make sure we can evaluate if we hit the targets after a mission.
* When developing the mission, it's nice to have the F10 View Option set to "All", for easy debugging.
* When you are done, before actually playing the mission, change this option to "Map Only" (and enforce it), so people can't use the F10 map as a GPS.
* Enforce the padlock option to "OFF".
* You can enforce Labels to "OFF" if you want. But we recommend leaving it not enforced. The mission needs to allow "Neutral Dot Labels" to allow for pilots to use the Mini Dot Labels mod found under [[Mods]]. Typically, we trust people to not use actual full labels.

==Design Considerations==

* While it's up to you as a mission designer to decide the difficulty level, be advised that it's more common that one accidently makes the mission too hard than too easy. It's tempting to add lots of enemies, but generally it's not needed to provide an interesting challenge.
* Even if the mission turns out to be easy, meaning nobody got shot down or was close to being so, you can count on that the mission will get challenging regardless. Comms, formation flying, keeping SA, aerial refueling and so on are very challenging and fun elements in themselves, even without somebody shooting at you.
* Don't over-complicate things. With lots of players, things will get complicated regardless.
* Always assign a package lead/mission commander. Inform them a couple of days before the flight preferably. If you don't have anybody else, consider taking this responsibility yourself. Don't run the mission without a formal commander.

==Written Briefing Considerations==
This is the recommended format for the written briefing.
Here's a copy-paste friendly briefing template: [[Mission Briefing Template]]

*Event details
**RSVP
**Activity
**Theatre
**Modules
**Prerequisites (State any general or slot-specific prerequisites for participation (i.e CASE 3, BQ, AAR etc))
**Lineup
*1 SITUATION
**1.1 Overview
**1.2 Area of operations
**1.3 Time and weather
**1.4 Air threats
**1.5 Ground threats
**1.6 Friendly forces
**1.7 Civilian/3rd part
*2 MISSION
*3 EXECUTION
**3.1 Commander’s intent
**3.2 Packages
**3.3 Order of events
**3.4 Rules of engagement
**3.5 Acceptable level of risk
**3.6 Flight tasking
*4 ADMINISTRATION AND LOGISTICS
**4.1 Airfield operations
**4.2 Carrier operations
**4.3 Tankers
*5 COMMAND AND CONTROL
**5.1 Commander
**5.2 Frequencies
**5.3 Authentication
**5.4 Freq flow (Airfield flights)
**5.5 Freq flow (Carrier flights)
**5.6 Brevity
**5.7 Bullseye
*6 ANNEXES (maps and so on)

==Step Briefing Considerations==

* Try to start the briefing asap. Don't wait more than a couple of minutes for late-joiners.
* Quickly go through the plan from an overview perspective.
* Let the mission commander, AWACS operator and ATC/Carrier people communicate any additional instructions and potential risks everyone needs to be aware of.
* Allow for questions but avoid long discussions.
* Keep the tempo up! Make sure the briefing doesn't take more than 15 minutes for easier missions and 30 minutes for very advanced missions.
* Allow for a quick restroom break just before starting the server.

Mission Design Guide

2023-09-08T06:57:18Z

Mags: /* Mission Editor Considerations */

''[[Home]] >> [[Mission Design Guide]]''

==Goals==

* Make it a smooth process for mission designers to create new missions.
* Establish standard configurations for things such as callsigns, comms and TACAN channels.
* Provide workarounds for common DCS problems, such as loss of TACAN.
* Provide tips for how to design a fun mission.

==Game Options Considerations==

Some settings that you set in the game's options (available through the DCS main menu) are copied into the actual mission. You need to make sure the following is setup in your options:

* Gameplay / Wake Turbulence OFF
* Gameplay / Easy Communication OFF

==Mission Editor Considerations==

===Mission Template===

[[Fil:Flights_THT.png|400px|thumb|Lineup]]

To make things easy, you can download a template .miz file that has all the basic stuff already setup for you. This will most likely save you quite a lot of time.

The template includes:
* Supercarrier with correct frequencies and TACAN.
* Deactivatable backup carrier.
* F10 menu controlled script that lets us reactivate the TACAN and ILS in case it shuts down because of a bug.
* Moose framework.
* Five tankers with patterns and correct frequencies.
* E-3 AWACS.
* 21 flights of F/A-18C, F-14A/B, AJS 37, A-10C, F-16C, Mirage 2000, UH-1H, AH-64D and Ka-50.
* F-14s and A-10s have comms preset synchronized with other aircraft types as per Master Arms standards.
* All aircraft have unique modex/tailnumbers as well as laser codes matching the included kneeboard.
* Enemies that can be spawned through LotAtc.
Download it here:
* [https://wiki.masterarms.se/images/9/9c/MA_MissionTemplate_CA_6_3.miz Caucasus Mission Template 6.3]
* [https://wiki.masterarms.se/images/d/d8/MA_MissionTemplate_PG_6_3.miz Persian Gulf Mission Template 6.3]
* [https://wiki.masterarms.se/images/6/66/MA_MissionTemplate_SY_6_3.miz Syria Mission Template 6.3]
* Written briefing template: [[Mission Briefing Template]]

===Detailed Basic Instructions===

This section covers all the things that should be considered in all missions. If you're using the mission template, most of this stuff is already taken care of.

====Carrier Setup====
''The mission templates already have these things set up.''
* Use ship number for TACAN (72X for CVN-72) and 264.00 for AI comms.
* Use the method showcased in the template .miz to allow for TACAN and ILS reactivation.
* If you have wind, make sure that the carrier route makes the carrier steam ''into'' the wind. No carrier cross-wind.
* The wind-over-deck speed should be around 25 kts. If you have zero wind, set the speed to 25. If you have 10 kts of headwind, set the speed to 15 kts.
** If you change the wind, you may need to tweak the carrier's heading and speed. Use this tool to know what approximate heading and speed is recommended for any given wind setting. https://magwo.github.io/carrier-cruise/
* To calculate the BRC, you need to work some magic because of true vs magnetic heading differances.
** In Caucasus and in Syria, take the course you see in the ME minus 6. Example: Boat is heading 000. BRC is 353.
** In Persian Gulf, take the course you see in the ME minus 2. Example: Boat is heading 000. BRC is 358.

====Flight Callsigns====
''The mission templates have flight names set to Arctic1, Bender2, Crimson3 and so on by default, and you are recommended to keep them. Feel free to be creative and change them, but if you do, a new custom transponder json file will have to be created for your mission, making things more complicated.''

Using the callsigns in the templates make things easier. Here is a spreadsheet with the flights available in the templates:
* [https://docs.google.com/spreadsheets/d/1C_Cu42DHHPnOjoe6QEh-Vef0yCF0RqlnCd3AfM36kDw/edit?usp=sharing Master Arms Mission Template Flights on Google Drive]

Here are a few guidelines:
* Unless there's a good reason for not doing so, use incremental numbers on the flights. If you have three flights and want to use the names Adam, Boxer and Charlie, call them Adam1, Boxer2 and Charlie3.
* Don't use callsigns that are too similar to each other. For instance avoid using two callsigns starting with the same letter (like Viper and Victor).
* Avoid callsigns that are easily associated with a certain aircraft type, if the flight flies something else. For instance, don't have an F-16 flight called Stinger1 or an F/A-18 flight called Viper2 or Falcon3.

''The mission templates have flight names set to Arctic1, Bender2, Crimson3 and so on by default.''

====Tanker Setup====
''The mission templates already have these things set up.''
* Navy aircraft (F/A-18C and F-14B) use "probe-and-drogue" refueling. They can refuel from KC-135 MPRS and KC-130.
* Air Force aircraft (F-16C, F-15C, A-10C) use "flying boom" refuling. They can refuel from KC-135 only (note: NOT the MPRS version).
* We normally never use the S-3 tanker because of various reasons.
* Be advised that the KC-130 carries significantly less fuel than the KC-135 MPRS and as such, can refuel fewer aircraft before it heads home.
* You may want to add a two-ship HAVCAP that escorts the main tankers.
* To setup a tanker pattern, add two waypoints (1 and 2) in addition to the starting waypoint. On WP1, add an action "ORBIT / RACE-TRACK". The tanker will fly in a race-track between WP1 and WP2.
* For tankers at about 15000-17000', a ground speed of 360 kts is good. Don't forget to set this speed in the Orbit Waypoint action as well.
* We recommend setting the tankers' "Reaction to Threat" setting to "Passive Defence".
* In most missions, you should setup three (or more) tankers:
** 1) Navy overhead tanker using Ch 14 (260.00). Could be KC-135 MPRS or a KC-130. Recommended callsign "Arco1" and TCN 101Y.
** 2) Air Force main tanker using Ch 20 (266.00). Always a KC-135. Recommended callsign "Texaco2" and TCN 102Y.
** 3) Navy overhead tanker using Ch 19 (253.00). Could be KC-135 MPRS or a KC-130. Recommended callsign "Shell3" and TCN 103Y.

====AWACS Setup====
''The mission templates already have these things set up.''
* There are two different EW aircraft. E-2D Hawkeye and E-3 Sentry. We recommend using the E-3 because of its superior radar coverage.
* Put the aircraft in a location between the airfield or carrier and the enemy AO, in such a way that it can be protected by friendly forces if needed.
* E-3 normally flies at around 29000' at 0.75M.
* E-2D normally flies at around 22000' at 250 kts indicated airspeed.
* You may want to add a two-ship HAVCAP aircraft that escorts the EW aircraft.
* Set the AWACS frequency to 251.00. Normally we have a human acting AWACS on Ch 3 (265.00). Channel 18 (251.00) is the AI AWACS channel (normally not used).
* We recommend setting the aircraft's "Reaction to Threat" setting to "Passive Defence".

====Bullseye placement====
Pilots and AWACS often need to describe locations relative to a known pre-briefed location, called the bullseye.

* Place the bullseye between friendly airspace and enemy airspace, 20-100 NM from anticipated engagement area.
* If possible, place the bullseye on a geographically well-known, visually spottable location such as a city, village, bridge, mountain or airfield.
* Don't place the bullseye on a target area. It causes impractically large angular changes when aircraft are moving around the target area.

====Radio Presets====
''The mission templates already have these things set up.''
* As far as it is possible, all aircraft should have the same radio presets for the UHF radio. It should follow the Master Arms standard [[Comms]] plan, which is identical to the DCS standard list for F/A-18C and F-16C (305.00, 264.00, 265.00 and so on).
* Normally, you only have to change F-14 and AJS 37 flights.
* AJS 37 flights should have Special 1: 270.00, Special 2: 257.00, Special 3: 265.00

====Mission Customization====
''To allow for convenient testing, the mission templates don't have F10 View set to "Map Only", so you need to change it manually.''
* Buildings can not be seen in TacView. So if you have buildings as targets, put a Russian Infantry in the roof, and set WP 0 to "Set Option/ROE/Weapon Hold" and "Perform Task/HOLD", to make sure we can evaluate if we hit the targets after a mission.
* When developing the mission, it's nice to have the F10 View Option set to "All", for easy debugging.
* When you are done, before actually playing the mission, change this option to "Map Only" (and enforce it), so people can't use the F10 map as a GPS.
* Enforce the padlock option to "OFF".
* You can enforce Labels to "OFF" if you want. But we recommend leaving it not enforced. The mission needs to allow "Neutral Dot Labels" to allow for pilots to use the Mini Dot Labels mod found under [[Mods]]. Typically, we trust people to not use actual full labels.

==Design Considerations==

* While it's up to you as a mission designer to decide the difficulty level, be advised that it's more common that one accidently makes the mission too hard than too easy. It's tempting to add lots of enemies, but generally it's not needed to provide an interesting challenge.
* Even if the mission turns out to be easy, meaning nobody got shot down or was close to being so, you can count on that the mission will get challenging regardless. Comms, formation flying, keeping SA, aerial refueling and so on are very challenging and fun elements in themselves, even without somebody shooting at you.
* Don't over-complicate things. With lots of players, things will get complicated regardless.
* Always assign a package lead/mission commander. Inform them a couple of days before the flight preferably. If you don't have anybody else, consider taking this responsibility yourself. Don't run the mission without a formal commander.

==Written Briefing Considerations==
This is the recommended format for the written briefing.
Here's a copy-paste friendly briefing template: [[Mission Briefing Template]]

*Event details
**RSVP
**Activity
**Theatre
**Modules
**Prerequisites (State any general or slot-specific prerequisites for participation (i.e CASE 3, BQ, AAR etc))
**Lineup
*1 SITUATION
**1.1 Overview
**1.2 Area of operations
**1.3 Time and weather
**1.4 Air threats
**1.5 Ground threats
**1.6 Friendly forces
**1.7 Civilian/3rd part
*2 MISSION
*3 EXECUTION
**3.1 Commander’s intent
**3.2 Packages
**3.3 Order of events
**3.4 Rules of engagement
**3.5 Acceptable level of risk
**3.6 Flight tasking
*4 ADMINISTRATION AND LOGISTICS
**4.1 Airfield operations
**4.2 Carrier operations
**4.3 Tankers
*5 COMMAND AND CONTROL
**5.1 Commander
**5.2 Frequencies
**5.3 Authentication
**5.4 Freq flow (Airfield flights)
**5.5 Freq flow (Carrier flights)
**5.6 Brevity
**5.7 Bullseye
*6 ANNEXES (maps and so on)

==Step Briefing Considerations==

* Try to start the briefing asap. Don't wait more than a couple of minutes for late-joiners.
* Quickly go through the plan from an overview perspective.
* Let the mission commander, AWACS operator and ATC/Carrier people communicate any additional instructions and potential risks everyone needs to be aware of.
* Allow for questions but avoid long discussions.
* Keep the tempo up! Make sure the briefing doesn't take more than 15 minutes for easier missions and 30 minutes for very advanced missions.
* Allow for a quick restroom break just before starting the server.

Training

2023-07-31T11:50:20Z

Mags:

''[[Home]] >> [[Training]]''

The following is a list of topics that Master Arms intends to train regularly, and when we last trained them. This document helps us ensure that we stay proficient in all aspects of flying virtual multi-role fighters, and do not neglect certain training.

{| class="wikitable" style="text-align: left"
|-
! Topic !! Last trained !! Recommended frequency !! Notes
|-
| CASE 1 || [https://masterarms.se/event/training-tuesday-29/ 2022-11-29] || 2 / year ||
|-
| CASE 3 || [https://masterarms.se/event/training-tuesday-40/ 2023-04-11] || 1 / year || DO NOT combine with IFR training
|-
| Airport procedures / ATC radio || [https://masterarms.se/event/training-tuesday-airport-procedures-mission-procedures-and-communication/ 2022-11-01] || 2 / year ||
|-
| Group & formation flying || [http://masterarms.se/event/training-tuesday-formation-flying/ 2022-04-26] || 1 / year ||
|-
| A/A Refueling || [https://masterarms.se/event/training-tuesday-37/ 2023-03-07] || 1 / year ||
|-
| Dogfighting || n/a || 1 / year ||
|-
| Group BVR with comms || n/a || 1 / year ||
|-
| Group A/G attacks || [https://masterarms.se/event/training-tuesday-37/ 2023-03-07] || 1 / year ||
|-
| Group SEAD/DEAD || [http://masterarms.se/event/training-tuesday-7/ 2022-03-11] || 1 / year || Combine with Group A/G
|-
| Time On Target || [https://masterarms.se/event/training-thursday-23/ 2023-07-27] || 1 / year ||
|-
| Intercepts || [https://masterarms.se/event/training-tuesday-you-have-been-intercepted/ 2023-02-21] || 1 / year ||
|-
| IFR airport procedures || [https://masterarms.se/event/traningstisdag-ifr-2/ 2023-02-27] || 1 / year || DO NOT combine with CASE 3
|}

IFR and CASE 3 should not be combined because they both require tower/ATC and will compete for those resources. Also, it's nice if members who want to practice both IFR and CASE 3 can do so.

2022-10-28T09:25:12Z

Mags:

''[[Home]] >> [[Standard Operating Procedures]] >> [[Mission SPINS]]''

SPINS stands for "Special Instructions". This page contains standard procedures that are valid for all Master Arms missions unless the organizer or mission commander explicitly states something else. The written mission briefings on the Master Arms event page often refers to the instructions on this page.

==Rules of Engagement==
We use three different sets of predefined Rules of Engagement, namely ROE: A, ROE: B and ROE: C.

{| class="wikitable"
|-
! scope="col"| ROE Set
! scope="col"| Intent
! scope="col"| Default Weapon Status
! scope="col"| Enemy Hostile Act
|-
! scope="row"| A
| Low level conflict, weapon usage rare
| HOLD
| Weapon employment
|-
! scope="row"| B
| Medium level conflict, weapon usage restricted
| TIGHT
| Weapon employment, radar lock
|-
! scope="row"| C
| High level conflict, war
| FREE
| Weapon employment, radar lock, maneuvering for tactical advantage
|-
|}

===Weapon status===

AWACS/GCI may change weapon status over the course of a mission.

*HOLD: On commander's formal order ("Cleared to engage")
*TIGHT: On targets declared HOSTILE
*FREE: On targets declared HOSTILE or BANDIT

===Self defence===

Nothing in these ROE negates the right of individual self defence, protecting your own aircraft and wingmen, as a response to a ''hostile act'' (as described in the table above for ROE: A, B, C respectively).

===BANDIT / HOSTILE criteria===

Only important for AWACS/GCI players

Used by AWACS/GCI to determine contact status.

BANDIT: Contact fulfills 2 criterias 
HOSTILE: Contact fulfills 3 criterias

*Lack of IFF
*PPLI indicates enemy (red)
*Enemy territory point of origin
*RWR correlates to known enemy type
*Race track pattern in enemy territory
*Unit accelerating and/or climbing on intercept profile

Or any one (1) ''hostile act'' (as described in the table above for ROE: A, B, C respectively).

==Acceptable Level of Risk==

The Acceptable Level of Risk (ALR) states what the mission commander should be ready to sacrifice in order to accomplish the main mission objective. We use three different variants of predefined ALRs.

===ALR: LOW===

* Accept losses at peacetime rates only
* Accept only favorable engagements
* Withdraw if high level threat manifests
* Aircraft recovery higher priority than mission goal

===ALR: MEDIUM===

* Accept 25% losses
* Accept neutral and disadvantageous engagements
* Withdraw to prevent heavy losses
* Aircraft recovery higher priority than mission goal

===ALR: HIGH===

* Accept 50% losses
* Accept neutral and disadvantageous engagements
* Preserve some future capability if able
* Mission goal higher priority than aircraft recovery

==Carrier Ops==

The procedures are explained in the [[CASE 1]] and [[CASE 3]] sections. The following additions should be followed:

* Regardless of CASE, the lowest amount of fuel when showing up in the groove for the first landing attempt is 3000 lbs.
** CASE 1: Hornet/Tomcat tank 2000, T + 2. Meaning that after bolter/waveoff 1 and bolter/waveoff 2, you may still attempt to land one more time, but if this '''third''' attempt fails, you will need to go to the tanker.
** CASE 3: Hornet/Tomcat tank 2000, T + 1. Meaning that after bolter/waveoff 1, you may still attempt to land one more time, but if this '''second''' attempt fails, you will need to go to the tanker.
* Check in with Marshal around 15-20 minutes before the briefed charlie time.