special instructions (spins) georgian airspaceserver.3rd-wing.net/public/maraudeur/pour rom/special...

Special Instructions

(SPINS)

GEORGIAN AIRSPACE

COMPLIANCE WITH THIS INSTRUCTION IS MANDATORY

Distribution: 132nd

Virtual Wing, and cooperating organizations

Version:1.2 - 10th

FEBRUARY 2015

Classification: This document is UNCLASSIFIED, for Digital Combat Simulator only

SPINS - GEORGIAN AIRSPACE

Version 1.2 - 10th

February 2015

2 FOR DCS USE ONLY

Summary of changes:

Version 1.1:

5.4.2: Added Risk Estimate Distances

5.4.3: Added Target Location Error categories

7.3.4 Entry into Killbox

7.3.5 Egress from Killbox

8.6.1: Changed standing RAMROD words

Version 1.2:

8.5: Added information about CSAR freqeuncy and its use.

7.1: Removed information about Kobuleti restricted zones. Added information about ranges in

Tblisi area

7.2: Removed MOA information

7.3: Added information about Tblisi TMA

10: Updated Group ID's and Lasercodes, added more squadrons

Appendix B: Changed airspace information from Kobuleti to Tblisi area

1. Introduction 1.1. Scope. These SPINS outlines those procedures applicable to the safe operations of

DCS aircrafts during all 132nd Virtual Wing hosted events. NOTE: These SPINS will not

replace each participating squadron own SOP’s but will make sure that all participating

pilots have a common understanding on how to operate during 132nd Virtual Wing hosted

events

1.2. Deviations. Deviations from these procedures require specific approval from

participating squadrons/organizations and should be discussed in the 132nd

Virtual Wing

forum.

1.3. Precedence. These SPINS take precedence over unit SOP’s. This to ensure a safe

environment for all aircrew participating in 132nd Virtual Wing hosted events.

1.4. Recommended changes. Recommendations for changes to these SPINS should be

addressed at the 132nd

Virtual Wing forums.

1.5. Changes. Changes made in this document will be made visible in the following

format:

Added text and deleted text

Only changes from one version to the next will have these markings.


Version 1.2 - 10th

February 2015

3 FOR DCS USE ONLY

2. General Information 2.1. Timezone. Timezone for all timings will be UTC+4 Hours (local Georgian time). The

reference time will be provided by the military global positioning systems or hacks

received from C2 agency (AWACS/GCI) for all assets.

2.2. Standard Units.

2.2.1. Positions will be given in the following format: LAT/LONG. DD°MM.MMM'

2.2.2. Distance will be given in nautical miles.

2.2.3. Elevation will be given in feet AMSL unless otherwise stated

2.3. ATO publication. ATO will be published at:

http://132virtualwing.org/index.php/page/ato

3. Command and Control (C2) 3.1. During operations flightleads will be responsible for their flights.

3.2. During operations package commanders will be in charge of a package of flights

3.3. All flights shall follow ATC and Controller instructions. All flights are to monitor

ATC frequencies when within an airfields airspace control zone.

3.4. All flights shall remain on a C2 frequency at all times, unless approved by a C2

agency to do something else. (C2 frequency: ATC/Tower/AWACS)

3.5. SADL information. 132nd Virtual Wing will use group ID in the 3X series. (30, 31,

32, 33 etc). MASTERARMS is given 4X series. See also section 10.

4. Rules of Engagement 4.1. Rules of engagement will be given in each mission brief.

4.2. Positive Identification (PID). PID is defined as the reasonable certainty that a

functionally and geographicly defined object of attack is a legitimate military target in

accordance with the Law of War and applicable Rules of Engagement.

5. Offensive Operations 5.1. Risk analysis. Aircrew should consider the acceptable mission risk level (AMRL)

when planning the mission

5.2. Acceptable Mission Risk Level

5.2.1. Extreme. The mission is vitally important to the survival of own or coalition

nation. Potential losses are not to preclude the execution of the task.

http://132virtualwing.org/index.php/page/ato


Version 1.2 - 10th

February 2015

4 FOR DCS USE ONLY

Mission/element cancellation cannot be authorized once strike package pushed

into enemy airspace.

5.2.2. High. The mission is vitally important to the overall success of the campaign.

Potential losses are not to preclude the execution of the task. ATO tasking

cannot be changed without permission from a higher authority.

Mission/element cancellation may only be authorized by higher authority.

5.2.3. Medium. The mission is important to the overall success of the campaign.

Every attempt to minimize losses should be made. The Mission Commander

may request permission from higher authority to reassign within the package

by role to optimize successful prosecution of assigned task. The minimum go-

criteria per element is to have self-protection capability of at least 2 of the

following: electronic self-protection(jammer), Chaff/Flare, Threat warning.

Overall mission cancellation may only be authorized by higher authority.

5.2.4. Low. The mission is only important within the context of the short term

situation. Losses are not acceptable. Forces will not enter surface weapons

engagement zones without dedicated SEAD. The mission commander has

authority to cancel mission based on loss of OCA/SEAD or force composition

falling below the minimum force required to achieve the tasked level of

destruction.

5.3. Target Priority Grade

5.3.1. Priority 1. The target is a critical factor in the overall outcome of the conflict or

a critical enabling objective for the other elements of the mission or will cause an

immediate and permanent reduction in the effectiveness of the enemy.

5.3.2. Priority 2. The target is an important factor in the overall outcome of the

conflict or will cause a long term reduction in the effectiveness of the enemy.

5.3.3. Priority 3. The target is an enabling factor for later missions or will cause a

temporary reduction in the effectiveness of the enemy.

5.4. Close Air Support (CAS). Close Air Support (CAS) is air action by fixed-wing and

rotary-wing aircraft against hostile targets that are in close proximity to friendly

forces, and requires detailed integration of each air mission with the fire and

movement of those forces.

5.4.1. CAS formats

5.4.1.1. CAS check-in Briefing

CAS Check-in briefing

Mission number:

Number and type of aircraft:

Position and altitude:

Ordnance:


Version 1.2 - 10th

February 2015

5 FOR DCS USE ONLY

Time on station

Capabilities

Abort code:

5.4.1.2. Area Operation Update (AO-update)

AO update

Threat:

Target:

Friendly situation:

Artillery activity:

Clearance authority:

Ordnance:

Restrictions:

Hazards:

Remarks:

5.4.1.3. CAS brief

CAS brief

Type of control:

Bomb-on-target/Bomb-on-Coordinate

Ordnance:

Method of engagement:

IP:

Heading:

Distance:

Target elevation:

Target description

Target loacation:

Type Mark: Laser code:

Egress:

Remarks:

Restrictions:


Version 1.2 - 10th

February 2015

6 FOR DCS USE ONLY

5.4.2. Risk Estimate Distances

Fixed Wing Risk Estimate Distances Table

Weapon Description

0,1 %

PI

MK-82 contact 500 Ib bomb 310m

MK82 HD contact 500 Ib bomb/ high-drag 310m

MK84 contact 2000 Ib 355m

CBU-87 Cluster 300m

CBU-103 Cluster 270m

GBU-12 500 Ib Laser Guided 280m

GBU-10 2000 Ib Laser Guided 315m

GBU-38 500 Ib JDAM 210m

GBU-31 2000 Ib JDAM 335m

AGM-65 Maverick 125 Ib warhead 175m

M151, M229, M261 2.75" Rockets medium altitude 265m

M151, M229, M261 2.75" Rockets low altitude 290m

GAU-8 30mm Gatling gun 95m

5.4.3. Target Location Error Categories

TLE CAT 1: 0-6m

TLE CAT 2: 7-15m


Version 1.2 - 10th

February 2015

7 FOR DCS USE ONLY

TLE CAT 3: 16-30m

TLE CAT 4: 31-91m

TLE CAT 5: 92-305m

TLE CAT 6: Above 305m

5.4.4.

5.5. Strike Coordination And Reconnaissance (SCAR)

SCAR is a mission flown for the purpose of detecting targets and coordinating or

performing attack or reconnaissance on those targets. SCAR missions are flown in a

specific geographic area and are an element of the C2 interface to coordinate

multiple Air Interdiction flights, detect and attack targets, neutralize enemy air

defenses, and provide BDA. The area may be defined by a box or grid where

potential targets are known or suspected to exist, or where mobile enemy surface

units have relocated because of surface fighting. SCAR coordinators perform a

similar function for Air Interdiction missions that forward air controller (airborne)

(FAC[A]) provides for CAS aircraft. Typical SCAR tasks include cycling multiple

attacking flights through the target area and providing prioritized targeting guidance

and enemy air defense updates to maximize the effect of each sortie.

5.5.1. SCAR Commander. A SCAR Commander (SCAR-C) will be used in order to

coordinate several flights conducting SCAR in the same area (The same killbox).

If only one flight is tasked in a single area, the flightlead will normally take the

duty as SCAR commander.

5.5.1.1. Duties. SCAR-C is not a formal qualifications such as FAC(A), and

everyone flying combat missions can assume the role as SCAR-C.

Duties of a SCAR-C is to deconflict any air assets operating within his

airspace, provide an AO-update to SCAR assets, clear SCAR assets into

the killbox., provide attack briefs to SCAR assets when necessary

5.5.2. SCAR formats

5.5.2.1. C2 Agency SCAR briefing. (For retasking to immediate SCAR

missions)

C2 Agency SCAR briefing

Killbox name and status:

Targets:

Threats:

Friendlies:

SCAR-C:

Ordnance restrictions or requests:

Remarks:


Version 1.2 - 10th

February 2015

8 FOR DCS USE ONLY

5.5.2.2. SCAR check-in briefing

SCAR check-in briefing

Mission number:

Number and type of aircraft:

Position and altitude:

Ordnance:

Time on station

5.5.2.3. SCAR AO-update

SCAR AO-update

Threat:

Target:

Friendly situation:

Restrictions:

5.5.2.4. SCAR Attack brief

SCAR Attack briefing

Deconfliction instructions:

Target description:

Target location:

Target elevation:

Remarks:

6. Airfield information 6.1. KOBULETI(UG5X)

RWY 07-25, 2400x60(m) 7870x197(ft) TWR:133.100 MHZ ATIS: 133.200 MHZ

6.2. TBILISI-SOGANLUG(UG24)

RWY 13-31, 2475x80(m) 8120x262(ft) TWR: 130.100 MHZ ATIS:130.200 MHZ

6.3. VAZIANI(UG27)

RWY 13-31, 2485x62(m) 8150x203(ft) TWR: 140.100 MHZ 140.200 MHZ

6.4. BATUMI(UGSB)

RWY 13-31, 2455x60(m) 8050x197f(t) TWR: 131.000 MHZ ATIS: 131.200 MHZ

6.5. SENAKI KOLKHI(UGKS)

RWY 09-07, 2375x50(m) 7790x164(ft) TWR: 132.100 MHZ ATIS: 132.200 MHZ

6.6. KUTAISI(UGKO)


Version 1.2 - 10th

February 2015

9 FOR DCS USE ONLY

RWY 08-26, 2500x60(m) 8200x197(ft) TWR: 134.100 MHZ ATIS: 134.200 MHZ

6.7. TBLISI-LOCHINI(UGTB)

RWY 13R-13L, 2920x45(m) 9580x150(ft) TWR: 138.100 MHZ ATIS: 138.200 MHZ

7. Airspace information 7.1. Restricted Areas. See appendix BRAVO for graphic overlay over Restricted areas.

All current restricted areas are ranges surrounding the Tblisi area. All ranges have their

own range order with detailed information.

Dusheti Range. Active from GROUND and up to Flightlevel 200.

Dusheti Range For basic range

Name (navpoint name) Latitude Longitude Description

DR1 N41°59.755 E044°24.735 Bridge

DR2 N42°10.619 E044°28.930 River split

DR3 N42°08.230 E044°46.230 Road junction

DR4 N41°59.945 E044°45.320 River outlet

DR5 N41°57.635 E044°36.060 Bridge

Dusheti Range Expanded For tactical range


DR1 N41°59.755 E044°24.735 Bridge

DR6 N42°11.600 E044°21.440 Bend in river

DR7 N42°15.000 E044°40.690 Powerline crossing river

DR8 N42°13.380 E044°50.260 Bridge



DR5 N41°57.635 E044°36.060 Bridge

Tianeti Range. Active from GROUND and up to Flightlevel 200.

Tianeti Range


TR1 N41°59.950 E044°45.300 River outlet

TR2 N42°04.360 E044°50.545 Bend in river

TR3 N42°13.380 E044°50.260 Bridge

TR4 N42°19.070 E044°53.010 Bridge

TR5 N42°19.100 E045°19.700 Mountain top

TR6 N41°46.917 E045°10.631 River outlet


Version 1.2 - 10th

February 2015

10 FOR DCS USE ONLY

Marnueli Range. Active from GROUND and up to Flightlevel 200.

Marneuli range


MR1 N41°19.800 E045°09.346 Bend in river

MR2 N41°13.331 E044°53.454 Bend in river

MR3 N41°17.958 E044°40.577 Highest peak

MR4 N41°28.026 E044°50.457 Powerline crossing river

Tetra Range. Active from GROUND and up to Flightlevel 200.

Tianeti Range


TE1 N41°27.330 E014°14.745 Split in river


TE3 N41°39.350 E044°42.570 Start of river



7.1.1. SPARE

7.2. Military Operating Areas (MOA's). Currently no defined MOA's. Can be created on

a case-by-case basis by coordinating with AWACS or ATC.

7.3. Tblisi Terminal Maneuver Area.

In the Tblisi area there are 3 airports close together(Lochini, Vaziani and Soganlung).

Each airport have its own controlzone, as shown by the Aries charts. This zone is fairly

small, and tower is in charge of everything within this zone. Outside these three airports,

there is established a TMA(Terminal Manouever Area) that handles all traffic in and out of

the three airports. Callsign "Approach" is for the controller in charge of the TMA.

Name(navpoint name) Latitude Longitude

UGTB1 N41°54.370 E044°25.358

UGTB2 N41°59.945 E044°45.320

UGTB3 N41°33.075 E045°37.180

UGTB4 N41°28.758 E045°32.013

UGTB5 N41°28.025 E045°12.970

UGTB6 N41°23.200 E045°02.910

UGTB7 N41°39.350 E044°42.570

UGTB8 N41°43.790 E044°25.650


Version 1.2 - 10th

February 2015

11 FOR DCS USE ONLY

7.4. Killbox. Killbox is a three-dimensional target area, defined to facilitate the integration

of coordinated weapons fire.

It is a coordination measure enabling air assets to engage surface targets without

needing further coordination with commanders and without terminal attack control.

A killbox can be under the control of a FAC(A) or a SCAR commander. The space is

defined by an area reference system. Each killbox is divided into 20x20 minute

squares.

A Killbox can be either active or closed.

7.4.1. Active Killbox. This is a killbox in use by someone. Killboxes can be

requested by flightplan request or through a C2 agency (AWACS/GCI).

7.4.2. Closed Killbox. This is a killbox currently not in use by anyone, and impose

no restrictions on air operations. This is the default value for killboxes.

7.4.3. Airspace. A active killbox is active from GND and up to 15000ft AGL.

7.4.4. Entry. Entry into killbox. Entry into killboxes are done from either of the two

western corners. Check in with FAC(A) or SCAR commander prior to entering

the killbox. Entry can be done from eastern corners if the situation dictates it

(threat etc)

7.4.5. Egress. Egress from the killbox is done from either of the two eastern corners.

Egress can be done from western corners if the situation dictates it (threat etc)

7.4.6. Quadrants. The Killbox can be further divided into 4 quadrants named A, B,

C and D. The NORTH-WESTERN corner of the killbox is named A, and the

SOUTH EASTERN corner is named D. See Appendix C for graphical overlay.

7.5. Georgian airspace. Georgian airspace is under allied control and can be used at all

times. This does not include the airspace over ABKHAZIA which for the time being is

considered contested airspace.

7.6. Russian airspace. All allied flights are to stay outside 2nm of the Russian border at all

times in order to prevent an unwanted escalation of the situation. NOTE: This is not valid

when tasking is to enter Russian airspace to conduct attacks.

7.7. International waters. International waters are considered 12nm outside the coast of a

country. All flights are thus approved to operate outside 12nm off the ABKHAZIAN coast,

and outside the Russian coast.


Version 1.2 - 10th

February 2015

12 FOR DCS USE ONLY

7.8. Zone around ships. In order to prevent an unwanted escalation, all flights are to

remain 4nm away from any Russian ship.

7.9. Altimeter settings. QNH is the altimeter pressure setting to be used by all aircrafts.

7.10. Standard Pressure Settings (SPS). For operations in 132nd Virtual Wing

hosted events we use standard pressure setting at altitudes above 5000ft AMSL. When

climbing above 5000ft, switch to standard pressure setting (29.92). Altitudes will be given

as flightlevels(FL) when operating on SPS. When descending below FL050, switch back to

local QNH as given by TWR.

7.11. Force QNH. Any C2 agency (including FAC(A) and SCAR-C can establish a force

QNH within his area of responsibility. This in-order to avoid unneccessary QNH changes.

When operating on force QNH, the C2 agency need to make sure all assets are briefed on

the QNH in use prior to entering the area.

8. Combat Search and Rescue 8.1. Combat Search and Rescue (CSAR) can be conducted in two ways:

8.1.1. Pre-planned CSAR. If the purpose of the mission is to conduct a rescue

operation of a downed pilot

8.1.2. Immediate CSAR. Occurs if a pilot is shot down during a mission, and

AWACS or Air Mission Commander order a CSAR operation to rescue the

downed pilot.

8.2. CSAR Task force. CSAR Task force can consist of the following assets:

8.2.1. Recovery asset. Normally a UH-1 Huey. If possible one primary and one

secondary helicopter.

8.2.2. Fixed wing rescue escort (RESCORT). Normally A-10s flying overhead

pattern to stay close to recovery veichles.

8.2.3. Rotary Wing RESCORT. Normally KA-50's flying in formation to the

extraction point and will provide fire support at the extraction site.

8.2.4. Support assets. Tanker and AWACS

8.2.5. Rescue Combat Air Patrol. Air-to air capable fixed wing aircrafts securing the

airspace above the CSAR Area of Operations (AO).

8.3. Duties.

8.3.1. Air Mission Commander (AMC). Coordinates the mission as it progresses.

Preferably AMC is the AWACS controller. If AWACS is unavaileble, AMC

will be filled by the role of the most senior flightlead.


Version 1.2 - 10th

February 2015

13 FOR DCS USE ONLY

8.3.2. On-Scene Commander(OSC). Coordinates the rescue efforts at the rescue site.

Initially this will be the wingman of the downed pilot.

8.4. Callsigns.

8.4.1. Rescue Helicopter: PEDRO

8.4.2. Rescue Escort: SANDY. SANDY 1 will be the On-Scene Commander. If no

AWACS is present. SANDY 1 will be both OSC and AMC

8.5. Frequencies.

8.5.1. MAYDAY call. MAYDAY calls are to be broadcasted at GUARD frequency

(243.000). Include Bullseye position (direction and distance from the Bullseye)

8.5.2. If time permits, coordinate with AWACS on flights designated frequency

8.5.3. CSAR Frequency. All CSAR operations are to be conducted on dedicated

CSAR freqeuency: 241.000 (MAROON 8). All assets involved in a CSAR

operation should monitor this frequency. If several CSAR operations are

conducted at the same time, AWACS will designated other frequencies for

CSAR.

8.6. RAMROD. Ramrod is an authentication code. RAMROD is a 10 letter word

where none of the letters appear twice. To authenticate the challenger selects two

letters in the authentication code, one of each side of the desired response. The

correct response is the letter bracketed by the challenge. For example using the

word COMPLEXIFY, you challenge by saying: Authenticate "PAPA-ECHO"

and the reply should be: "I authenticate LIMA"

8.6.1. Standing RAMROD

8.6.1.1. Even days (2,4,6,8 etc): LUMBERJACK

8.6.1.2. Odd days (1,3,5,7 etc): COMPLEXITY

9. Deconfliction 9.1. Standard Deconfliction.Between flights. 1000ft is standard deconfliction separation

between two flights.

9.2. Coordinating altitude. Standard deconfliction between FW and RW aircraft is at

1500ft AGL. FW are free to operate above 1500ft AGL and RW are free to operate below

1500ft AGL.

10. Air Assets

Unit Platform Callsign Group ID Lasercodes Base

617th

vSquadron A-10C 3-series 1511-1600 Lochini

696th

vSquadron Ka-50 BLADE N/A Lochini

121st vAviation Company UH-1 HUSKY Lochini

MasterArms A-10C 4-series 1600-1620 Lochini


Version 1.2 - 10th

February 2015

14 FOR DCS USE ONLY

MasterArms Ka-50 N/A Lochini

RAF Air UK - 74th Squadron A-10C 21-25 1620-1640 Lochini

RAF Air UK - 97th Squadron A-10C 26-29 1640-1660 Lochini

11. Appendixes

Appendix A - SPARE

Appendix B - Restricted airspace and TMA


Version 1.2 - 10th

February 2015

15 FOR DCS USE ONLY

Appendix C - Killbox graphical overlay

Corners for area A:

N46 00.000 E037 00.000

N46 00.000 E038 00.000

N45 00.000 E037 00.000

N45 00.000 E037 00.000

special instructions (spins) georgian airspaceserver.3rd-wing.net/public/maraudeur/pour rom/special...

Documents