elevation delta between TPOD and RDR induced by UFC selected waypoint

[nickos86]

An interesting feature. If you designate a target via the RDR while the waypoint selected in the UFC is in the target area, the TPOD cues automatically to the designation and the elevation is quite close to the actual one (comparing to the F10 map). If you des a target via the RDR while the waypoint selected in the UFC is FAR from the target area- the delta between the RDR des and a TPOD will drastically vary.

Attached two pictures. The target area is at waypoint 2. The target coordinated from the F10 map are: N 30°21.066'   E 34°50.382' and alt of 1385ft

For the first picture ,I've entered waypoint 2.A into the UFC and designated a TGT . The coordinates are very accurate. Same for elevation - 1380 vs 1385 ft.

As for the second picture, I've entered waypoint 1A to the UFC and designated the target. Note that now the elev is 1900 ft!

Something to consider and take into account when designating targets using the radar.

 

After seeing the following thread:

KlarSnow important input: "The Air to ground radar pulls the elevation from the steerpoint you have input at PB 17 in the upper right of the radar display. If you do not have a steerpoint up there, it pulls from the closest steerpoint. This is why your targetting pod is pointing in the air. It has no way to generate elevation off of an HRM map, only coordinates." 

So it's a good habit to set the steerpoint closest to target into PB17. But, seems like the "if you don't have a steerpoint up there, it pulls from the closest steerpoint" - doesn't work as intended. Rather, it pull data from the waypoint set in the UFC.

Edited July 14, 2023 by nickos86