Updated: 2023-05-15 --- # Additional Group Additional Group is a call made when either a new group is detected or a previous non-factor group becomes a factor for a commit. In order for it to be an additional group, the group must show up outside meld range. Additional groups are named, “Additional Group, 2nd additional group, 3rd additional group” and so on. Make the additional group call as soon as it becomes clear that the group will be a factor. >[!example] Additional group >“`[AIC Callsign]`, `[#]` additional group, `[anchor]` `[alt+trk+dec+fill]`” >>[!quote] >>==AIC==: “Closeout, 2nd additional group, rock 245/45 22k, track south, hostile foxhound” # New Picture If the picture changes outside meld range, the AIC has the option of calling “new picture”. Think of new picture as wiping the slate clean and starting again, all group names and targeting are removed, and new group names and/or labels are assigned to all groups. The AIC is not required to call new picture, and cannot call it inside meld range. The new picture call is identical to the post commit call, except “new picture” is added at the front. E.g. “Closeout, new picture, 6 groups…..” # Pop-up Group A pop-up group is a group that appears inside of meld range but outside of threat range. A pop-up group is communicated in the same way as an additional group and if more than one appears, they are named in the same way. (pop-up group, 2nd pop up group, 3rd…) A pop-up group is one of the situations where the AIC is expected to communicate post meld. The pop-up group is usually communicated via BRAA format. >[!Example] > “Victory-1, Pop-up group BRAA….” # Threat Group If a new group shows up at or inside of threat range, or a previously targeted group becomes untargeted while within threat range of a friendly, that group is a threat group. If the group was previously identified, add ‘threat’ to the beginning of the group name, otherwise the group name is just “threat group”. Make a BRAA call to the threat group, provide directive targeting or a recommendation >[!Example] >==AIC==: “Camelot-1, East Group, Threat BRAA …. … recommend flow 270” By default a threat group is implied to be untargeted, if a group is targeted but still a threat to a friendly, add “targeted by” to the fill ins with the targeting friendly >[!Example] >==AIC==: “Camelot-1, West Group, Threat BRAA 120/30, 22k, hot, hostile, flanker, targeted by Victory-1, recommend flow 300” # Bogey Dope Bogey dope is a request for a BRAA call to the closest group to the calling fighter. Respond to bogey dope with a BRAA call to the closest factor group. If multiple groups are within meld range, prioritize threat, then un-targeted groups, then targeted factor groups then finally non-factor groups. Remember to add “targeted by” in the fill-ins when referencing targeted groups. If there are no groups in the picture, respond “clean” >[!example] >`A/C`: “Victory-1 Bogey Dope” >==AIC==: “Victory-1, West Group, BRAA….” # Spike/Mudspike Calls If an aircraft has an RWR indication indicating a radar lock or potential missile launch, they should call “SPIKE” with a bearing to the spike. If it is a ground based system, they should call “MUDSPIKE”. If the system type is known, it may be added. The AIC will respond with an abbreviated BRAA call indicating the range, altitude, and aspect (as applicable) of the first matching contact along the given bearing. If no contacts are along that bearing, they will respond “clean” with the bearing. E.g. “Closeout, clean 330” >[!example] Spike, Mudspike, Clean >`A/C`: “`[Callsign]`, (Mud)Spike `[bearing]` (`[type]`)” >>[!quote] >>`A/C`: “Winder-3-1 Spike 330, 29” > >==AIC==: “`[Callsign]`, (Mud)Spike Range `[range]`, `[altitude]`, `[aspect]`, `[declaration]`, `[tipper]`, `[group name]`” >>[!quote] >>==AIC==: “Winder-3-1, Spike Range 21, 16k, hot, hostile, fulcrum, east group” > >==AIC==: “`[AIC Callsign]`, clean `[bearing]`” >>[!quote] >>AIC “Closeout, Clean 330” # Strobe/Metallica If an aircraft encounters a jamming strobe and is unable to resolve the contact or there is ambiguity about contacts along the strobe line, they should make a strobe call to the AIC. The AIC will respond with a similar format to the spike call. >[!example] Strobe >`A/C`: “`[Callsign]`, Strobe `[bearing]`” >>[!quote] >>`A/C`: “Bengal-1-1 Strobe 120” > >==AIC==: “`[Callsign]`, Strobe Range `[range]`, `[altitude]`, `[aspect]`, `[declaration]`, `[tipper]`, `[group name]`” >>[!quote] >>==AIC==: “Bengal-1-1 Strobe range 35, 34k, hot, hostile, Flanker-H, north group” If a friendly aircraft is targeting a group, but then loses targeting due to jamming, the friendly fighters should make a “Metallica” call, indicating they are unable to employ due to jamming. They should state their intent (Either “Press” or “Flow cold”) and the AIC will respond with either a strobe call or a flow direction as appropriate. >[!example] Metallica >`A/C`: “`[Callsign]`, Metallica `[group name]`, intend `[intentions]`” >>[!quote] >>`A/C`: “Bengal-1 Metallica west group, intend press” # Separation If friendly fighters desire a callout of the distance between the group they have currently targeted and another group or the next closest group, they can make a separation call. The AIC replies with the distance between the currently targeted group and the indicated group or next closest group. The separation is assumed to be in the same direction as was last called in the picture (ie either range or azimuth), if the type of separation needs to be specified due to a changing picture, it can be added to the AIC call. >[!example] Seperation > `A/C`: “`[Callsign]`, Separation (group name)” > >[!quote] > >A/C “Winder-3, separation north group” > >==AIC==: “`[AIC Callsign]`, `[Group name]` `[range/azimuth]` Separation `[distance]` `[altitude]` `[track]` `[declaration]` `[tipper]`” >>[!quote] >>AIC “Closeout, North Group Separation 25, 34, track south, hostile, flanker” # Flow/Cold Flow is a brevity term indicating maneuver in a specified direction. It can be used in a directive, informative, or inquisitive manner. Unlike giving an aircraft vectors, flow allows for dynamic maneuvering in the general direction of the flow, it can be a specific heading or a cardinal or sub cardinal direction. When used with the aircrafts own callsign and a direction, it is an informative call stating intentions e.g. >[!Example] >`A/C`: “Victory-1 flow south” > When used with another aircrafts callsign and a direction, it is a directive call giving instructions to turn that direction. E.g. >[!Example] >==AIC==: “Camelot-2, flow 240” When used without a direction, it is an inquisitive call asking for a good flow direction, it should be responded to with a directive flow call. E.g. >[!Example] >`A/C`: “Winder-2 defensive, flow” >==AIC==: “Winder-2 flow 330” Cold is a descriptive term for the opposite direction of the enemy, when added to a flow call its specifies the flow towards the safe axis. E. g. >[!Example] >`A/C`: “Victory-3, flow cold” >==AIC==: “Victory-3 flow 210”