@dimebag2 I spent the afternoon setting up a parametrized version of the situation in Geogebra that can calculate the camera slew rate with respect to the clouds. The geogebra file is attached to this post, to download and open in Geogebra/geometry. Most parameters can be modified via the algebra view.

The F18 always starts at the origin; as a simplification I'm using a circular flight path with radius

r=3.2 nm; in GIMBAL, the turn radius changes.

F18speed=350/3600, that's 350 knots converted to nm/s. The UAP is initially (

UAP0) placed at

dUAP=29.8 nm with a bearing of 54⁰ from the F18, and it velocity

vUAP is 380 knots heading 69⁰, which corresponds to

@Edward Current 's scenario 5 with straight and level UAP trajectory.

Edit the above values to match a specific scenario, the rest is automatic.

All distances are in nautical miles (nm), times (

t,

arrow) are in seconds, speeds are in nm/s.

You can move both objects

t seconds ahead via the

t slider. This will update the azimuth of the UAP with respect to the F18, corresponding to the GIMBAL video HUD.

The velocity vectors

vF18 and

vUAP are calculated for 1 second; the displayed velocity arrows are scaled by the

arrow slider, which is calibrated in seconds, to make them more visible. The headings of the F18 and the UAP are indicated as blue and red dashed lines.

The thicker dark green line is the sight line from the F18 to the UAP, with dotted lines to each side indicating the 0.35⁰ FOV. The thin green line is the sight line from the tip of the F18 arrow to the tip of the UAP arrow, i.e. it indicates what the sight line would be

arrow seconds in the future if the F18 continued along its current heading. This gives you a way to examine how much the sight lines are going to diverge over time, from any F18 position.

Geogebra actually computes this divergence using a cloud bank at

Clouddistance=120 nm (editable!) from the origin. It determines where the current and future sight lines intersect the clouds, computes the

Slew angle of these points with the F18, and normalizes it by dividing by

arrow to yield the indicated slew rate.

The s/FOV reading is just a simple conversion of the slew rate with a 0.35⁰ FOV. If you set the

arrow time to be half that, you can see the future sightline exactly at the edge of the FOV.

I hope this is clear enough; have fun!