Jak/Sandbox

IDEAS

HOTAS

In addition to interfacing with the avionics using the pushbuttons (PBs) around the DDIs and MPCD, the F/A-18 features a hands on throttle and stick (HOTAS) control setup. These controls allow the pilot to manipulate various important functions without taking the hands off the throttle or the control stick. There are also some functions only available through the HOTAS.

This section will describe general HOTAS usage. Refer to the appropriate sections for detailed descriptions of individual HOTAS functions.

The Throttle Designator Controller (TDC) and Sensor Control switch (aka the "Castle" switch) are the primary HOTAS controls. The Sensor Control switch is used to assign the TDC to the format on the LDDI, RDDI, or MPCD in all master modes by pressing left, right, or aft. Once the TDC is assigned to a format, the TDC switch can be used to manipulate that format. On the Radar/Attack format, for example, it slews the cursor which is used for a variety of functions such as target selection and scan centering. On the FLIR format, the TDC slews the FLIR line of sight.

In A/G and NAV master mode, the TDC can be assigned to the HUD by Castling forward. The TDC can then be used to create and/or slew an A/G target designation.

In A/A master mode, the forward position of the Sensor Control switch instead enters the Air Combat Maneuvering (ACM) condition and commands the Radar into Helmet Acquisition mode. Once in the ACM condition the Sensor Control switch can then be used to select the other ACM modes: Long Helmet Acq, Wide Acq, and Vertical Acq. The Undesignate button will exit the ACM condition and return to "top level" Sensor Control switch functionality.

When the TDC is already assigned to a format, bumping the Sensor Control switch in that direction again will often perform additional functionality. For example, on the Attack format, when the cursor is over a trackfile, bumping the Sensor Control switch toward the format commands the Radar into acquisition on the target.

When the format on a display cannot accept TDC assignment, such as the Tactical or Support Menu formats, the Sensor Control switch will perform automatic format selection. When pressed right in this scenario, the Radar/Attack format is invoked on the RDDI. Aft will invoke the HSI format on the AMPCD. Left, only in A/A master mode, will invoke the Az/El format on the LDDI.

When the HSI or SA format is on any display, bumping the Sensor Control switch toward it with the TDC already assigned to the format will cycle between the two formats (HSI, SA, HSI, etc).

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 basic generalized description of functions and modes to better understand the overall system.

The first phase of an engagement is often search. In the search phase, 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) and it provides a mostly clean view of only raw Radar Return data, termed "hits" (green brick symbols).

Although the RWS Attack format provides a mostly decluttered view of raw hits, it also maintains Radar trackfiles even if they are not always displayed on the Attack format. In RWS, the pilot can view trackfiles in a few ways. A trackfile is almost always represented as a HAFU symbol. First, the Undesignate button can be used to create then cycle the Launch & Steering target designation (L&S) through all trackfiles. This displays the HAFU symbol on top of the associated raw hits. Second, the Latent TWS (LTWS) option on the DATA sublevel, which is by default selected, allows the pilot to view the trackfile associated with any raw hit by placing the cursor over it. The HAFU is displayed until the cursor is taken off. Third, the MSI option on the DATA sublevel (also default-selected) causes all trackfiles with Datalink contribution to be displayed constantly. The reason for this logic is that the RWS format would not otherwise display Datalink-only trackfiles with no Radar contribution, since they have no raw hits associated.

By using the Undesignate button as described or depressing the TDC with the cursor over a HAFU symbols, trackfiles can be designated as the Launch & Steering target (L&S) or Secondary Designated Target (DT2). or for any HAFU under the cursor if no DT2 exists, weapon launch zones are displayed in RWS. This cues the pilot as to the weapon potential against any target.

The other mode primarily intended for surveillance is Velocity Search (VS). VS does not create trackfiles and 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).

Once the target or targets of an attack are detected and identified, it is desired to more closely track them. This is generally done by way of the Track While Scan (TWS) mode or Single Target Track (STT). TWS can be entered via the mode option at PB5 using the pushbutton or slewing cursor. STT can be entered from RWS or TWS. 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.

In TWS mode, the scan volume is limited to maintain a scan frame time of 3 seconds or less, resulting in a high trackfile refresh rate. Note that there is no difference in trackfile processing between RWS and TWS, but TWS provides better tools for attack. In TWS, 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.

One TWS tool is AUTO scan centering, where the L&S and DT2 trackfiles are automatically maintained in the scan volume. The pilot retains the ability to "bias" the scan volume as desired while maintaining the L&S/DT2, or use MAN scan centering. TWS first defaults to MAN if entered from RWS or VS. AUTO is default when entering TWS from STT. A toggle is available at PB13.

STT is highly straightforward. The Radar is fully dedicated to tracking a single target. This results in the highest trackfile quality, especially important for weapon guidance, at the cost of the Radar not scanning any volume of space at all.

The main beyond visual range weapons available are the AIM-7 Sparrow and AIM-120 AMRAAM missiles. The AIM-7 uses pulse Doppler illumination (PDI) guidance, where the Radar physically "paints" a target with a particular waveform. This guidance requires STT so the Sparrow can only be employed at one target at once and only in STT. The AMRAAM uses datalink guidance from the Radar for the majority of the missile's flight to the he target, which can be supplied in RWS, TWS, or STT. RWS is usually not used for AMRAAM guidance due to the previously mentioned advantages of TWS or STT, but it remains available. Note that an AMRAAM launch from RWS automatically commands TWS but RWS could be reselected if ultimately desired.

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).