Need help for the design of an "ESCORT" script

[FlightControl]

Hi all;

 

I am developing an ESCORT script.

 

http://forums.eagle.ru/showthread.php?t=164696

 

I need help how the communication would go when an escort (which is accompanying the flight of a player in the role of an AFAC) would coordinate or report a potential target and asks assistance from a ground unit or a ship to attack the target.

 

How would this communication go in real life???

 

Are there people in the community who can advise on:

- What parties are involved in the communication? Would there be a coordination centre, or would the pilot contact the ship directly?

- What standard sentences are exchanged?

- Are there any important terminology that i need to reflect in the communication?

- Are there any verification steps? f.e. if the target is hit or not?

...

 

Maybe have a look at the video to understand what the escort is all about first :-)

 

Thanks in advance,

Sven

[Eddie]

A FAC(A) wouldn't do either of those things, it's not their role. FAC(A) provide control of CAS/Air Interdiction aircraft within their assigned airspace in a similar way to a JTAC. A ground TACP may call in naval fire just as they would land based artillery, but that isn't typically the job of the JTAC, FAC(A)s would not do that.

 

Besides that can you be more clear on what you're seeking, Escort is an Air-Air role, and a very diverse one with several variations which operate quite differently.

 

You should find much of what you may need to know for FAC(A) and JTAC related things in the J-FIRE manual.

 

[ame]http://www.dtic.mil/doctrine/new_pubs/jp3_09.pdf[/ame]

Edited April 15, 2016 by Eddie

[FlightControl]

A FAC(A) wouldn't do either of those things, it's not their role. FAC(A) provide control of CAS/Air Interdiction aircraft within their assigned airspace in a similar way to a JTAC. A ground TACP may call in naval fire just as they would land based artillery, but that isn't typically the job of the JTAC, FAC(A)s would not do that.

 

Besides that can you be more clear on what you're seeking, Escort is an Air-Air role, and a very diverse one with several variations which operate quite differently.

 

You should find much of what you may need to know for FAC(A) and JTAC related things in the J-FIRE manual.

 

http://www.dtic.mil/doctrine/new_pubs/jp3_09.pdf

 

So, imagine a friendly airplane doing a CAP, spotting targets. He is on a mission to report target locations so that he can acquire help from ground artillery or ship vessels to engage that target from safe distance.

 

Are you saying that these kind of scenarios are not handled in a real battle field?

 

FC

[Eddie]

Again CAP is an air to air mission, anything on the ground is irrelevant unless it's shooting at you, in which case you evade it.

 

It sounds like you're talking about a recon mission, in which case they generally aren't real time and when hey are (such as with UAVs the pilots would not talk with the naval or ground assets directly it would be routed via one of more C2 agencies. The kind of thing you're talking about doesn't happen with just one aircraft in real time it takes several aircraft and/or ground assets and happens over hours, or days.

[FlightControl]

Aha. So these C2 agencies, are these like coordination centers? And how are they connected with the plane?

[Sryan]

Aha. So these C2 agencies, are these like coordination centers? And how are they connected with the plane?

 

Yeah C2 agencies stand for Command and Control. It depends on how they are connected to the plane. Some monitor the radio communications, some don't communicate with the plane directly but by example observe radar. Some others can directly observe Satellite and datalink information.

 

At the lower to moderate levels, each branche handles his own C2. An example for the Airforce would be the E-3 Sentry (technically a C3I. The third C standing for communications meaning it acts as a link between the tactical and strategic level, and the I standing for Intelligence, meaning the device is capable of gathering most of its own intelligence in the field). For the navy an example would be an aircraft carrier or one of the specialized Command ships ( USS Blue Ridge or USS Mount Whitney).

 

The different branches don't merge untill fairly high up. At the regional or theater level by using something like DJC2. Or at the national or international level based in the continental United States (USJFCOM, although I heard it is now defunct but I don't know how they replaced it ) or Europe ( NATO Allied Joint Force Command. Several bases, I live fairly close to the one in Brunssum, Netherlands wich we still know by its cold war era name AFCENT :) )

 

In short, these lines are way to long for directing artillery strikes. I can imagine the airforce using their Lockheed U-2, RQ4 or formerly their SR-71 to gather intelligence wich makes it's way to other branches for them to use cruise weapons, but even that would presumably take hours to reach from one end to the other.

 

I believe aircraft used for artillery spotting are called AOP's. They belong to the Army Aviation. This means they are all helicopters. I know the OH58 Kiowa carried out this role since atleast the vietnam era. A few where lost performing exactly that role. The Kiowa was supposed to be replaced by the commance or the Bell ARH-70 but with both helicopters canceled the Kiowa is still doing the job today.

 

 

Hope it was helpful or informative :)

[FlightControl]

Thanks. The info is very informative. So if we would implement a game scenario where an assisted attack would be executed of a plane identifying targets, communicating them to these c2 centers and artillery aiming at these locations, well, even if it would be only half real, I am already satisfied... What sentences would these guys say to each other in the communication?

Edited April 16, 2016 by FlightControl

[DUSTY]

Thanks. The info is very informative. So if we would implement a game scenario where an assisted attack would be executed of a plane identifying targets, communicating them to these c2 centers and artillery aiming at these locations, well, even if it would be only half real, I am already satisfied... What sentences would these guys say to each other in the communication?

 

Sounds like you're trying to simulate some form of fixed wing strike coordination and reconnaissance (SCAR) mission.

 

It sounds like you're talking about a recon mission, in which case they generally aren't real time and when hey are (such as with UAVs the pilots would not talk with the naval or ground assets directly it would be routed via one of more C2 agencies.

I think perhaps the SCAR mission could be an exception to this rule. Although SCAR mission and their associated assets are usually planned/fragged well in advance, the SCAR aircraft will pass real-time targeting data to their assets.

 

I've taken the below info from a mission briefing that we did a little while ago. Basically we had some aircraft working as SCAR assets who owned a piece of airspace and searched, located and coordinated attacks on targets within that area. Note that this isn't FAC(A)/CAS work because it was occurring beyond the FSCL, away from friendly ground forces.

 

You'll notice a lot of reference to kill boxes which are a Fire Support Coordination Measure and simply added to the realism of the scenario. You could adapt the below communications to suit your project without using the kill box references if you wish. If you're interested to learn more you can check out this link: https://publicintelligence.net/fm-3-09-34-kill-box-tactics-and-multiservice-procedures/ but it probably goes beyond the scope of what you're trying to achieve:

 

Anyway, here are some examples of how strike coordination and recon aircraft will work with other strikers to employ weapons against targets in their assigned kill box.

 

Example: "Savage 11, this is Cutlass 41, mission number 302, flight of two F18s. 20 miles to the south angels 22, 2 GBU-12s, one GBU-31 per jet. Playtime 30 mikes."

 

Example: "Cutlass 41, Savage 11, proceed to kill box 621GE keypad 9, operate in the block angels 20-22. Target priorities are tanks and artillery, possible SA13 in 622GF keypad9. 621GE is active blue kill box. Be advised Sonic 31 flight of two F18s is operating in the block angels 23-25, Savage 11 at angels 31. Advise when ready to copy attack brief."

 

 

Example: "Cutlass 41 ready to copy."

"Cutlass 41, your target is a column of 4 tanks oriented north to south, location S19 34.2356 E153 25.3493 elevation 1204ft. For

deconfliction, make your attacks south to north with right turns off target back to keypad 9. Advise when engagement complete or

when sensors are on target area for visual talk on."

Here's how an overall scenario might play out:

 

Commanders have established a kill box in an area where multiple OPFOR armoured vehicles are believed to be operating.

Commanders intent is to have air assets attrit forces in this location to prepare the battlefield for an upcoming ground offensive.

 

Kill Box status: BLUE

Establishing Commander's Targeting Guidance:

a) Priorities: Tanks, armoured vehicles, troop/vehicle concentrations and ammunition dumps.

b) Effects: Destroy targets. Do not destroy bridges or road networks. No scatterable munitions near bridges, roads or civilian buildings.

Remarks: No friendlies within the proposed kill box. No Fire Areas (NFA) have been established 10nm south of the kill box where friendly

SOF teams are operating.

 

The first set of assets to arrive on scene is a two ship F/A-18 flight assigned the SCAR mission (callsign Savage 11/12).

SAVG11/12 are the kill box coordinators for the established kill box. The flight have briefed to perform 'yo-yo' tanker ops so as to have

one aircraft on station providing KBC duties for the duration of their briefed time-on-station (TOS).

 

SAVG11 flight control the kill box vertical limits from 10,000ft to FL450 and establish themselves with an altitude split so they can freely

search for targets. By the time SAVG11 flight have found and noted the location of some targets, a section of F/A-18s (MPIE81/82) check

in - SAVG11 performs the kill box brief. Meanwhile, SAVG12 expends its ordnance against a group of revetted tanks in keypad 6 (eastern

side). SAVG11 tasks MPIE81 to also hit this set of targets and passes the coordinates. SAVG11 gives restrictions for MPIE81 to remain in

the eastern keypads (3, 6 and 9) with north/south attack runs for deconfliction. The burning vehicles from SAVG12s hits make a perfect

mark for MPIE81 to continue prosecuting an attack against that target.

 

During MPIE81s attacks, both aircraft in the formation make radio calls on the designated kill box frequency: "Magpie 81 in from the south

GBU12", "Magpie 81 off hot to the east, 1 away", etc.

 

SAVG12 returns to searching for targets while SAVG11 provides the check-in brief to another section of F18s (SWRD51/52).

SWRD flight is sent to keypad 1 to work a target there and is advised of all other aircraft working the kill box.

 

SAVG12 hits joker state early and proceeds to the tanker for AAR. Upon returning to the kill box, SAVG11 hands off to 12 for KBC duties

and heads to the tanker themselves.

 

Over the course of the next few hours, SAVG11 expends their ordnance and the flight continue to work other assets that are assigned to

their kill box.

 

By the time SAVG11/12s TOS is complete, ground forces have advanced to the boundary of the kill box and the Joint Forces Commander

closes the kill box to further air to surface fires. SAVG11/12 are advised of this through the Air Operations frequency and RTB.

 

-----------------------------------------------------------------------------------------------------------------------------------

Sorry for the whole essay but I had the info ready and thought it might help.

 

Cheers

Edited April 17, 2016 by |DUSTY|

[Eddie]

SCAR/SCAR-C is similar to FAC(A) in practice, with the exception that no specific qualification is required. It's still about coordinating other aircraft, there wouldn't be any coordination with ground/naval assets.

 

C2 message are generally passed via AWACS, secure datalink messages, or in suitably equipped aircraft via sat comm radios linking to ground based C2 such as "K-mart" (call sign for the Middle East CAOC during OIF/Op Telic). They would then relay any further tasking on to other assets under their control as needed.

[FlightControl]

e

Edited April 19, 2016 by FlightControl