Tholozor

Make sure you also include the grid zone designator.

If the indication is for the D model, then it's only applicable to the D model. The beginning of the manual states that anything coded with [D] is only for F-16D aircraft. Anything applicable to both C and D will have no code.

Did you align the HMD?

Using the DTC would only apply to PP targets. You can still designate a waypoint with TOO.

That filter is specific to RWR contacts, not PPLI symbology.

Can only be done via the UFC.

Antenna elevation isn't tied to the bar scan setting. Bar scan only changes the vertical coverage of the scan volume, but doesn't control the elevation of the scan volume center. The attached numbers to the TDC represent the upper and lower altitude the scan volume covers at the range where the TDC is present on the scope. Using the antenna elevation control on the throttle allows the pilot to steer the center of the scan volume up and down relative to the aircraft's horizon. You can use the AZ/EL page in A/A Master Mode (can be invoked on the left DDI with Sensor Control Switch Left if the left DDI doesn't have a page that can have the TDC assigned to it) to have a forward-looking radar scope that shows the scan volume FOV.

The UPDT option is used for correcting INS positional drift, analogous to the FIX options in the F-16 (only available if the position-keeping mode is not POS/AINS).

4-HARM F-16 was squadron-dependent. Some had aircraft with an additional plug in the wiring harness to allow data/video transfer for the inboard stations. Changing laser codes from the cockpit in the Hornet is a stop-gap until the codes can be set on the rearm panel (same could be said for the A-10).

Already reported:

The AN/AAR-50 was the Thermal Imaging Navigation Set, not Nite Hawk. The AN/ASQ-173 was purely a laser spot tracking pod (basically the Navy's version of the Pave Penny pod used the A-10). The baseline AN/AAS-38 was indeed only a FLIR camera for targeting. The -38A added a laser designator, but still had no laser spot detection capability, so Hornets would still use Nite Hawks combined with -173s until the -38B, which added LST. The original idea of ATFLIR was to combine all three pods into one. Fun fact: Nite Hawk and TINS pods that were modified for carriage on the Super Hornet were re-labeled as AN/AAS-46 and AN/AAR-55, respectively.

If the INS is not yet aligned, the map defaults to the terrain's (0,0) coordinates, which for Caucasus is the middle of Crimea.

Already reported (affects the F-16 as well):

Here's the manufacturer's product page for their second version of it: https://electronics.leonardo.com/en/products/loam-v2, you can check the brochure for more details.

You can always use the Base Point (home plate) steerpoint as your selected navigation point by entering 'B' (SHFT -> 3) on the UFC, that'll let you edit any sequenced points.

Waypoint Sequences in the Hornet can have up to 15 waypoints per sequence, with three sequences in total. As far as I've seen reading the NATOPS, no direct waypoint selection is available.

Link16 isn't related to missile guidance in this way. The ownship FCR has its own missile command datalink for AMRAAM guidance, otherwise F-16s wouldn't have been able to guide 120s prior to the addition of the MIDS-LVT (e.g. Desert Storm).

Already reported:

The new fuze options are WIP and currently don't do anything, selection is irrelevant at this time.

New fuze options are WIP and can currently be ignored, but basically: - M904/M905 are old-school mechanical impact fuzes. - FMU-139 is an electro-mechanical fuze installed in the tail. - FMU-152 is the Joint Programmable Fuze (JPF) installed in the tail that permits cockpit programming.

Never named the door gunners, but my copilot is Bob.

Radar manual.

The radar elevation display on the cursor in VS mode is calculated if the range scale were at 80nmi (according to the -742).