Jak/Sandbox

Basic A/A Systems Operation
The following is a summary of operating the A/A Radar in a generic engagement. It is intended to give a generalized description of functions and modes to better understand using the overall system, which is detailed in depth in the other sections.

Radar/Attack format. The primary Radar interface is the Attack format. In addition to being accessible from the TAC menu, it can be accessed via HOTAS by bumping the Castle switch right. This invokes the format on the right DDI. The same occurs when entering A/A master mode.

Multi-Sensor Integration trackfiles. Most targets displayed to the pilot are MSI trackfiles. The only exception is raw Radar hits which are the raw returns of the Radar, represented by green brick symbols. These hits are not correlated or extrapolated; hence, "raw" hits. An MSI trackfile on the other hand is a single sensor-fuzed target which the Radar may or may not be contributing to. An MSI track may have only Radar, only Datalink, or both Radar and Datalink contribution.

An MSI trackfile is represented by a symbol called a HAFU ("Hostile, Ambiguous, Friendly, or Unknown"). The HAFU is shaped like a triangle for a hostile, a staple for an unknown or ambiguous, or a half circle for a friendly. It is also colored red, yellow, or green accordingly. A Radar MSI track has an "upside up" HAFU symbol along with an upside down one to indicate any type of Datalink contribution, if any. An MSI track with only Datalink contribution will appear differently based on the contributors. If it has Fighter-to-Fighter (F/F) contribution then it appears simply as an upside down only HAFU. A Surveillance (SURV)-only track appears as a 1/2-size HAFU and either a diamond, tall/skinny rectangle, or full circle. A Precise Participant Location and Identification (PPLI) track appears as a full-sized full circle.

Range While Search (RWS). In the search phase of an engagement, the pilot generally desires to surveil a large chunk of space to detect targets for an attack. The Range While Search (RWS) mode is optimized for this purpose. An unlimited scan volume is available (as large as 6 elevation bars / 140° azimuth).

Scan volume/centering. The size of the scan volume is changed on the Attack format using the azimuth width and elevation bar controls at PB20 and PB6. These options can be selected by pushbutton or via the cursor. The scan volume azimuth center can be easily changed on either the Attack or Az/El formats using the cursor. A quick TDC depress sets the scan center. The elevation can be centered in two ways: by using the Antenna Elevation wheel on the throttle or by using the cursor on the Az/El format.

Hits/trackfiles in RWS. In RWS, the Attack format provides a mostly decluttered view of raw hits, displayed as green bricks. However, RWS also processes Radar trackfiles like TWS. The difference is that in RWS, most trackfiles are intentionally hidden. It is important to note they still exist even when they are hidden. There are a few ways these trackfiles are displayed.

If a trackfile is designated as the L&S or DT2 target, it is displayed as a HAFU symbol with its Mach number and altitude to the left/right. In the case of a Radar trackfile, it is displayed ontop of the corresponding hits.

Also, any trackfile in RWS with Datalink contribution is always displayed on the Attack format. This is regardless of whether it also has Radar contribution (i.e. seen by the Radar). Without this feature there would be no way to indicate the existence of Datalink-only trackfiles on the RWS Attack format. It can be toggled under the DATA sublevel at the "MSI" option.

For any trackfile not being displayed, the pilot can 'preview' it by slewing the cursor over its corresponding raw hits. This is the Latent TWS (LTWS) function and can be toggled under the DATA sublevel if desired. With LTWS not selected, cursoring over a raw Radar hit will not display a trackfile; instead it just displays the raw hit's altitude to the right of the cursor. Once a track is cursored over with the LTWS function, it can be designated by depressing the TDC to permanently display it.

Note that neither the LTWS nor MSI selections have any effect on trackfile processing, but just the display on the Attack format in RWS.

Az/El format. On the Az/El format the pilot is provided a forward-looking projection of trackfiles. No raw hits are displayed and the Az/El format is not subject to the complex RWS display logic on the Attack format; rather, all tracks are always displayed regardless of Radar mode.

SA format. The Situation Awareness (SA) format also displays all MSI tracks like the Az/El, but in a "god's eye" view. Unlike the Attack format, however, the SA display is just like the HSI format in that it is a 360° view around the aircraft, not a warped B-scope view like the Attack and Az/El formats which cover only 140° ahead.

Designated trackfiles. The pilot is able to designate any Radar trackfile. The primary designated track is the Launch & Steering target (L&S). If desired a Secondary Designated Target (DT2) can also be made. The L&S points weapons to that target and also shows weapon launch parameter on the HUD and Attack format. The DT2 is simply used to monitor another track more closely as it also displays launch zones. Also, the DT2 and L&S can be quickly swapped with the Undesignate button. Both the L&S and DT2 positions are shown on the HUD and HMD. The L&S is a box and the DT2 is an "X" shape.

Designation methods. To actually designate trackfiles, two methods are available. The quickest way is by pressing the Undesignate button, which assigns the L&S designation to the rank 1 trackfile. Subsequent quick presses step the L&S designation through each trackfile. If the button isn't pressed for more than 4 seconds then the next press reassigns the L&S to the rank 1 track. Note that when a DT2 exists the Undesignate button cannot do this function as it swaps the L&S/DT2 instead. For this reason, it can be detrimental to have a DT2 if engaging three or more targets at once. The second way of designating trackfiles is with the cursor. When placed over any trackfile, depressing the TDC will make it the L&S if none exists. If an L&S does exist ready, the track is instead made the DT2. The DT2 itself can be designated with the cursor to make it the L&S and undesignate the old L&S.

Velocity Search (VS). The other Radar mode primarily intended for surveillance is Velocity Search (VS). A major disadvantage is the that VS does not create trackfiles. It presents hits in a special azimuth over closure rage format. The advantage over VS is it realizes the maximum possible detection range of the Radar at the cost of poor target data (no range, therefore no altitude calculation, etc). Outside this advantage, RWS is far preferred to VS due to its trackfile processing.

Entering Track While Scan (TWS) and Single Target Track (STT). Once the target or targets of an attack are detected and identified, it is usually desired to more closely track them. This is generally done by way of the Track While Scan (TWS) or Single Target Track (STT) modes. The transition is smooth since trackfiles are already being made in RWS. TWS can be entered via the mode option at PB5 using the pushbutton or via cursor. STT can be entered from RWS or TWS in a few ways, all termed methods of "acquisition". The most common method is Fast Acquisition whereby the desired trackfile or hit is placed under the cursor and the Sensor Control switch is bumped toward the Attack format. This also works on the Az/El format.

Track While Scan (TWS). In TWS mode, the scan volume is restricted to maintain a scan frame time of 3 seconds or less which results in a high trackfile refresh rate. Entering TWS from RWS may result in a smaller volume being forced. Note that there is no difference in trackfile processing between RWS and TWS, but TWS simply provides better tools for attacking targets. In TWS, raw hits can be displayed like in RWS, but all trackfile HAFU symbols are also always displayed. Unlike RWS, raw hits can be removed in TWS by unboxing the HITS option at PB8. This makes the display less cluttered.

TWS scan centering. One highly important TWS tool is AUTO scan centering, which automatically adjusts the Radar scan center to keep the L&S and DT2 trackfiles in the scan volume. This allows the pilot to focus less on manipulating the scan while engaging targets. While in AUTO, the pilot retains the ability to manually "bias" the scan center as desired, while still automatically maintaining the L&S/DT2. This biasing is accomplished using the cursor just like with manual centering. Fully manual (MAN) scan centering is also available in TWS which functions identically to RWS. TWS first defaults to MAN if entered from RWS or VS or to AUTO if entered from STT. An AUTO/MAN toggle is available at PB13.

Single Target Track (STT). STT operation is highly straightforward. The Radar is fully dedicated to tracking a single target. This results in the highest trackfile quality, which is especially important for weapon guidance, at the cost of no space being scanned by the Radar. The STT RAID mode is available for toggle via the RAID switch on the throttle. In RAID, the Radar alternates between full track and brief scans where it searches for additional targets in a narrow vicinity of the STT target. In RAID the Attack format is zoomed in to a 5nm x 5nm display centered on the STT target.

Exiting STT. Return to Search (RTS) from STT is most easily done by pressing the Undesignate button. The Radar returns to the mode used to enter STT (which can be RWS, TWS, or an ACM mode). There are a few exceptions. The Radar never returns to VS since this would delete the existing trackfile. Also, the Radar always returns to TWS if an AMRAAM is in flight. The mode that will be commanded upon RTS is indicated at PB5 under the word "RTS". There is also a TWS option at PB10 to go to TWS directly from STT in any scenario.

AMRAAM and Sparrow missiles. The main beyond visual range weapons available are the AIM-7 Sparrow and AIM-120 AMRAAM missiles which are highly integrated with the Radar. The AIM-7 uses pulse Doppler illumination (PDI) guidance, where the Radar physically "paints" a target with a particular illuminating waveform picked up by the Sparrow seeker. This guidance requires STT, so the Sparrow can only be guided at one target at once, and only in STT. The AMRAAM uses one-way datalink transmissions from the Radar for the majority of the its flight to the target, which can be supplied in RWS, TWS, or STT. This means the AMRAAM can be employed at many targets simultaneously. RWS is usually not used for AMRAAM guidance due to the previously mentioned advantages of TWS or STT, but it remains available. An AMRAAM launch from RWS automatically commands TWS, but RWS could be reselected if ultimately desired. Also, if STT is entered from RWS and an AMRAAM is fired, the Return to Search (RTS) mode becomes TWS, even though STT was entered from RWS.

HAFU SYMBOLOGY RADAR upper hos amb frd unk

F/F lower hos amb frd unk

SURV full small hos amb frd unk

RADAR+F/F full small hos amb frd
RADAR+SURV

PPLI full n/a n/a frd n/a

Priority is first given to PPLI HAFU symbology. Any PPLI trackfile is displayed as a full circle regardless of whether there is onboard contribution.

Non-PPLI Radar trackfiles are prioritized after and have an upper HAFU shape. If a Radar trackfile also has F/F and/or SURV contribution, a lower HAFU is displayed as well. Trackfiles with Radar contribution are also characterized by a rank number in the center of the HAFU.

A trackfile with either only F/F contribution or F/F and SURV contribution is displayed as a lower HAFU shape. There is no indication as to whether SURV is a contributor.

Trackfiles with only SURV contribution have the lowest symbology priority. SURV-only trackfiles are displayed as 3/4 size HAFUs with full diamond, circle, or rectangle shapes.

AUTOMATIC FORMAT SELECTION Commonly-used formats can be automatically selected without using the [TAC] or [SUPT] menu to ease pilot workload.

When A/A or A/G master mode is selected, the A/A Radar/Attack format or A/G Radar format is displayed on the RDDI. When either master mode is selected the Stores format is displayed on the LDDI.

Independent of master mode, when the Sensor Control switch is pressed right and the format on the RDDI cannot accept TDC assignment, the A/A Radar/Attack format or A/G Radar format is displayed on the RDDI, depending on which was last selected. However, in A/A master mode, only the A/A Attack format can be displayed.

In A/A master mode, when the Sensor Control switch is pressed left and the format on the LDDI cannot accept TDC assignment, the Azimuth/Elevation (Az/El) format is displayed.

On the Az/El format, the A/A FLIR and A/A Stores format can be displayed by selecting the "STORES DSPLY" or "FLIR DSPLY" label at PB4 with the cursor. When IFF/RDR is the priority Az/El sensor, PB4 invokes the Stores format. When the FLIR is the priority Az/El sensor, it invokes the FLIR format. The priority sensor is cycled when the Sensor Control switch is bumped toward the Az/El with the cursor outside the tactical region. Note that the cursor is initialized over the STORES/FLIR DSPLY label, which is also outside the tactical region, allowing for immediate selection of the Stores or FLIR format and/or sensor cycling between IFF/RDR and FLIR.

Independent of master mode, when the Sensor Control switch is pressed aft and the format currently on the MPCD cannot accept TDC assignment, the HSI format is displayed on the MPCD. On any display, when the Sensor Control switch is bumped toward the HSI or SA formats after the TDC is already assigned to the format, the HSI and SA formats are cycled (e.g. HSI, SA, HSI).