Frederf

The missile should fly toward the prescribed destination regardless of other emitters of any type or position until a particular point in the trajectory. An EOM shot to completely empty ground must ignore other emitters along the majority of the flight path. Otherwise the HARM is invalidated as a means to suppress a particular threat if it is so easily distracted 2 seconds off the rail.

The maximum possible number of Maverick to launch with one WR press is two. They both must be tracking simultaneously from paired stations (e.g. 3/7) and "RP 2" must be selected. Due to an issue this currently isn't possible if LAU-88 or EO VIS or EO BORE is used. AG master mode SMS OSB 2 (x2) "PRE" SMS OSB 8 then OSB 19 then OSB 2 "RP 2" DMS down WPN SOI Refine crosshairs on first target and TMS forward to track MSL STEP Refine crosshairs on second target and TMS forward to track MSL STEP to confirm both missiles are within firing parameters (optional) Weapons release button hold until both missiles fire (short delay) F16 EO RP2.trk You could use two points to designate two targets. For example if STPT 1 has first target then simply TMS forward to track first missile and INC to STPT 2 and TMS forward to track second missile. You're allowed to change the target point in the middle of the process. Here's an example of two steerpoints which are near two targets with a steerpoint change in the middle. F16 EO RP2 STPT.trk

All situations of external power are indistinguishable from supply by the internal main generator. The only exception is rejection of all ground power supply by the ground power monitor unit in cases of ground power not meeting volt/freq/phase requirements. After the monitor unit the airplane cannot tell the difference.

It should be a short press of IFFCOM hat inboard/outboard (forget) which should wipe DL contacts for a time. IDM takes a while to make an update but L16 can be fast. Wiping data could be repopulated super fast. IFF inboard cycles ALL -> FTR+ -> TGTS or if NONE it selects the last non-NONE selection. IFF outboard alternates X -> NONE where X is the setting as set above.

Sorry, more careful analysis. I set up ISA, 22000lb GW, DI 0, infinite fuel, G effects off. Test run is continuous turn at MIL, sea level, and check Tacview graphs. Max ITR (and STR) is around M0.5 or a little more which is about 325 KCAS for 25 or more dps. At 450 KCAS (M0.85) TR is about 17.5dps. At higher altitudes the max ITR Mach is higher say 15,000' it's M0.75 which is about 405 KCAS. In general KCAS for best TR will get higher at higher altitudes. Expect it in the area 330-440 KCAS with slower speed down low and higher up high.

nah, even full flex it shouldn't go squirrel off the rail. TI is for other types. GS is for trajectory shape.

Real HARMs have trip points. A 40 mile EOM shot shouldn't be forgetting its mission 2 seconds off the rail. It has nothing to do with FOV.

Tested with just plain ACE BORE. The radar just is bad in certain geometries. Steep downlook at even a few miles and it will take a while to lock if at all. I wasn't able to get lock in in some situations until 0.7nm slant. Make sure you're not holding TMS forward with ACM BORE or HMCS as the radar won't radiate until TMS forward is released.

If you fire a POS shot at a location (say without an emitter) ~35nm and there is a threat radar of the assigned type ~30 degrees off axis laterally from the airplane-location line the missile will fly toward the active emitter within 2 seconds after launch. This applies to all POS shots: EOM, RUK, PB.

I have found that all HARMs trip very shortly after launch and will track other than the designated target regardless of mode.

There are charts and it's as you say. Best turning rate is always the slowest speed that you can hit 8-9G (or whatever your limit is at the time). Weight doesn't change the speed at best performance nearly at all. The performance depends on weight a bunch but not so much the speed to attain it. The charts are in Mach for speed. In general the speed is less ~0.6 at low alt climbing to 0.9 or so at higher alts. Almost always max performance instantaneous turn performance is near 450 KCAS. It might be slower at high alt where M.9 happens at lower KCAS. But all max ITR turns are negative Ps which means it's not something you can sustain for more than about 90 degrees of turn. Being at max ITR parameters grants maneuver potential. Potential is spent after the first turn. After potential is spent best turn is STR which is slower. And sometimes you want other performance than turn rate, e.g. radius which is a little slower.

There is only one mode possible with HMCS FCR cueing. I'm guessing this has nothing to do with HMCS and would have the same performance with ACM BORE straight ahead on the HUD. I would compare radar performance between HMCS and BORE before I concluded there is anything special about HMCS.

Radar dishes are not armored.

1xAIM-9M on station 1 is 116 (+-0.5) kg. Adding 1xAIM-9M on station 11 is 231 (+-0.5) kg. Multiplying by two is 232 (+-1.0) kg. In imperial, 256+-0.5 pounds, times two is 512+-1.0 pounds, shows 509+-0.5 pounds. If I remember DCS is doing something silly like rounding/truncating first and then adding for display purpose which can give more variance in addition than the normal method. To the precision DCS chooses to display masses in the native SI I've never found a wrong tallying up.

The stores weight includes both weapons and suspension gear. So a single AIM-9 is the summation of: (1) AIM-9 (1) DRA (2) LAU-105 And a second AIM-9 only adds another weapon weight. Suspension gear is a significant part of the stores weight.

Walleye is a bomb. Maverick is a missile. SAM won't engage the Walleye.

Paveway III is a lot smarter than Paveway II. That would make predicting flight time harder. The timer could be the unguided ballistic prediction. Flashing L is definitely showing active laser.

It's supposed to lase for a little while after the predicted time of impact (~4 sec) to ensure it actually lases throughout the impact which could potentially be longer than predicted. If the moving target was causing the impact to happen sooner than predicted the laser would continue to run for that 4 seconds plus the difference between predicted and actual. Does the laser run forever after the 0:00 timer?

The aiming for CBU-97s specifically has been goofed for a little while. The system thinks that the post-burst high drag part of the trajectory is super super super high drag (basically that it will fall straight down from burst). The actual BLU-108 doesn't experience this drag however and tends to overshoot the aimpoint. But CBUs in general have CCIP solutions which are a lot steeper than slick unitary bombs. It's just due to their burst height and high drag second segment. If you're just slightly above the burst height then the trajectory is steep because it's essentially no slick flight and mostly drag flight and if you're super high altitude the ballistic arc curves down a lot just like slick bombs do. It's basically impossible to get CCIP solutions super flat with CBUs because they don't tend to fly that way.

A ha. I found evidence that L16 correlation is limited to system tracks. Preventing tank tracks from correlating would solve a lot of confusion.

Many users are sloppy when it comes to notation for angles. This makes confusion between formats too common. Angles are always expressed as the numerical portion of a type followed by the identifying symbol of the type. This process is repeated for the next smallest type to be used. Only the smallest type can have decimal component. 14.555555° There is only degrees type, followed by ° (degree) symbol, and since there is only one type it can have decimal part. "Fourteen point five five...degrees." 14°33.3333' There are 14 of the degrees type followed by ° symbol followed by 33.33 of minutes type followed by ' (minutes) symbol. "Fourteen degrees, thirty-three point three three three three minutes." 14°33'19.998'' There are 14 then ° (degrees) then 33 then ' (minutes) then 19.998 then '' (seconds). "Fourteen degrees, thirty-three minutes, and nineteen point nine nine eight seconds." The three examples are all exactly the same angle expressed in different formats. Dots, dashes, spaces, other symbols, repeated symbols, out of order symbols are all non-standard and risk being ambiguous and misinterpreted. N 41.56.017 is such a case. Does it mean N41.5617° or N41°56'17'' or N41°56.017'? The extra zero suggests the latter but who can be sure? For F-16 you never enter any data except N E S W and digits 0 1 2 3 4 5 6 7 8 9. The symbols, format, and place values are fixed by the system. That format is: a xx° yy.yyy' or b xxx° yy.yyy' where is a is north/south, b is east/west, xx is between 00 and 90, xxx is between 000 and 180, yy.yyy is between 00.000 and 59.999. Not that longitudes of less than 100° are expressed as three digits so 1° is 001°. Latitudes always are entered as 7 digits and longitudes as 8 digits. Negative-possible values (like elevation) are preceded by a 0 ICP press to indicate a negative sign.

Same as Bignewy

The foreign manual says that "RDY" shows up after handoff is completed which kinda suggests that launch is inhibited until handed off. The procedure listed makes no mention of launching other than after handoff. But maybe USAF is different.

For AIM-9 or AIM-120 it temporarily alternates the permanent setting to it's alternative as long as enable is held. E.g. SLAVE to BORE or BORE to SLAVE. If you want to change the permanent setting then press the appropriate OSB on SMS. It's for quick selection of the opposite setting. Yes, that's how it works. Enable should change the EO submodes at all* times, not just when WPN is SOI. For some reason DCS is limiting it to WPN SOI. In general Enable is not a SOI-dependent control. *When EO is selected weapon, except RECCE SOI. I noticed it won't change submodes when missile is tracking. That's possibly correct. I don't know. If submode cycling worked when missile tracking I don't know if track would be broken or not. Manual doesn't say that submode cycling by enable is inhibited when missile tracking but it also doesn't say that it's not. Enable also cycles through the HARM submodes in a similar manner to EO, not sure if it steps HAS-POS-DL or only alternates HAS-POS. In that case WPN might have to be SOI. For F-16s with the ability to launch Penguin missile is does a similar submode cycling. I don't know what enable does on RCCE SOI but I guess it can do something. In general enable is not SOI dependent and is used for submode changing of the selected weapon (AA missile, EO, HARM, Penguin, Recce pod).

If no update is performed then the system would work the same as with an update but without the refinement of position. The target would have defined position at BAD however it would be subject to a BUT position which may have drifted some. I agree that PI is a small logical modification or addon. Not much has to change to make PI out of normal CCRP. If I was designing the system I would have the system change from the PI designation phase to the attack on 3/9 passage of any update point (oblique or overfly) or a couple miles passing if no update was made. Target would be BAD regardless of update or not. The last thing you want screaming at 600 knots at 500 over enemy territory is not getting rid of your bombs. Maybe you see the reference point too late for oblique but you could overfly or you don't get a chance to update at all. Probably you would do a normal INS update one point earlier than the attack so drift is minimal anyway. It's preferable to have imperfect aim than to not release at all. You aren't likely to get another chance.