132nd-vwing/atrm_brief

Mission brief and resources

atrm_brief's Issues

Tankers encroach range 9

It looks and feels like two of the tankers in the ATRM mission encroach on the western edge of Range 9. We subsequently have a big chunk of airspace on the western side of the range - maybe a 10nm wide corridor - that's impossible to use. Can we consider either:

• Taking a chunk out of the range and giving it to the tankers
• Moving them

typo in Pages/Presets

heading has "Frequncy" instead of Frequency

Add CV to CF file

Please add CV with 50NM radius area to CF file.

F14 (SPECTRE and KNIGHT) laser code ranges

SPECTRE and KNIGHT currently have two problems with laser codes:

1. They both have the same ranges (1455-1458)
2. Those ranges don't work in the F14; the F14 has the following restrictions for laser code ranges:
   Digit 1: must be 1
   Digit 2: can be 5, 6, or 7
   Digit 3: can be 1-8
   Digit 4: can be 1-8

Thanks for fixing :-)

Range 7 AR scenarios, unclear what they do

from the brief:
Admin
Start AR scenario: “Start Dynamic AR Scenario”
“Activate AR Targets at Range 7” + “Activate Anti Air at Range 7”

its unclear for the user what those do, or what the difference is

Hound documentation

Related to 132nd-vWing/ATRM#134 and 132nd-vWing/ATRM#136. @hbjonsson when able and once the latest build has been tested, please update the documentation as necessary.

Viper presets do not reflect kneeboard pack

Either our kneeboard pack is wrong or the presets are, but the two don't resemble each other!

Adding ACLS, Link4 for CVN-73 & CVN-72

To make ACLS and LINK4 active for both carriers it has to be set up in CVN opions by adding ACLS and LINK 4 (freq 373.0 for CVN-73 and 372.00 for CVN-72

Airspace Control Plan

For reference:
https://www.jcs.mil/Portals/36/Documents/Doctrine/pubs/jp3_52.pdf

Page 64 ->

/Pages/SPINS.html - Hostile Act / Hostile intention - Speed should not be a criteria

I would suggest not having criteria along the lines of "Hot toward friendlies, with a groundspeed of 500kts or higher" as this is not a definite description as something only a hostile would do.

It would in my opinion be better to write something along the lines of "moving tactically towards friendlies" as this is something that AWACS or Pilots monitoring the contact should be able to recognize and assess.

Master Freqs: TCN issues on Recovery Tanker/AR202

Recovery Tanker is 64Y on 2 page summary - but 48Y in mission (as per: https://github.com/132nd-vWing/ATRM/blob/9aeb20c120613915019314dec9049778f2bfee25/l10n/DEFAULT/ATRM_Airboss.lua#L8)

AR202 TCN is 48X (correct) in 2 page summary, but not in Frequencies sheet (says 48Y)

Presets on Mi8

Can we get the Mi8s to have the following presets:

	R-863
1	126.100
2	126.200
3	127.100
4	237.000
5	119.200
6	119.400
7	121.100
8	121.200
9	229.000
10	227.500
11	228.500
12	228.250
13	127.500
14	225.750
15	235.750
16	233.250
17	242.250
18	231.250
19	309.000
20	136.250

	R-828
1	35.60
2	32.90
3	48.50
4	33.80
5	36.30
6	37.80
7	38.20
8	33.50
9	38.50
10	34.25

If I can help, please let me know.

Add reference to RAMROD in Authentication in Standing SPINS

RAMROD is currently in the same link as AET100 (it is on the same document), but there isn't a reference to it so it is hard to find. Can RAMROD also be referenced along with AET100 in the Authentication section so that those who don't know that they are combined can still find it.

very minor issue: FLIPs are linked twice in the brief

very minor issue: FLIPs are linked twice in the brief, once under 'navigation' but also as separate point on the landing page

R15 frequency

R15 has no assigned frequency as per https://132nd-vwing.github.io/ATRM_Brief/Files/ATRM%20freqs%20overview.pdf

from Artur: add CV 50nm radius to CF

132nd-vWing/ATRM#84

Add instructions for Range-14 "preset CAS Scenarios"

I'd like to add the following text to the briefing, describing the new scenarios and how they should be used but can't handle the editor too well hence would appreciate if anyone more competent could support:

CAS pre-set random scenarios, Range-14:
The random pre-set CAS scenarios are aimed to provide the JTAC with practicing a rapid preparation of his situation updates based on details provided by a simulated Ground Force Commander.

How-To-Use:

1. Once in the mission, first take any slot of a USA airframe and then switch to TACTICAL COMMANDER or JTAC (The purpose of this is to allow receiving of messages generated only for specific users. This step is essential!
2. In the F10 menu, select ACTIVATE RANGE-14 PRESET CAS SCENARIO RANDOMLY. This would display the GFC-briefing to you providing you with the situation , priorities, restrictions and other scenario-specific information. It is highly advised to screenshot this screen so that the brief can be read later on as needed.
3. The briefing relates to this map:
   https://cloud.132virtualwing.org/s/RdHNqBNkNNgwWiP
4. After a few minutes, The "regular" JTAC unit of the range will deactivate and only the scenario-specific JTAC would be available (The GFC brief also states the LATLONG of your JTAC position for this scenario).
5. Similarly, the scenarios can also be selected specifically rather than randomly by choosing "CAS Preset scenario 1", CAS Preset scenario2" etc.

add a webhook channel for this repo in discord

Low priority.

Can we get a webhook channel like #atrm_github or #opuf_brief_github for this repo as well?

Some of the stuff here gets copied into kneeboards. Would be nice to see which stuff gets updated, so that we know when we need to update our kneeboard.

two more VFR routes around OMAM

When RWY31 is in use, and the 617th recovers from SW, we need to make a pretty long detour for LUGAL 3, entering at VILLAGE. I would like to propose a new route for both directions, using a new navpoint HIGHWAY. This would establish the new departues MANSA 4 and LUGAL 4, thereby creating more flexibility and shorter ingress when the navigation target is in the direction of the take-off.

Range 12 RW AR scenario needs briefing entry

132nd-vWing/ATRM#109

@132nd-Inigo

Range 15 Secondary (149) conflicts with AR-301

This is referenced in the master frequency file and of course AR-301 in the mission

I'm adding this here so it can be logged and I shall do a sweep to check if others need changing and can then do a single sweep fix