marmor

Yeah, and they released a whole document too which holds multiple documents regarding the seeker itself from early development stages(why they chose this and that) to late production(tests). Along with meetings with americans throughout these, from comparing to the sparrow E and to the F in clutter, noise, MLC rejections, seeker ranges etc and mentions of the M but sadly nothing as the M was still in early development but they knew it was a slotted array antenna with 4channels for monopulse tracking.

You can use it, it was released by them. Though I dont know if there are more pages, I'm sorry. British were well aware of issues and limitations on the SPO15-RADAR-JAMMER interference and bunch of other stuff well before the fall of the USSR. They really knew the opponent once you read the whole section, how the spo15 looked and showed, radar worked, frequencies, jammer, IRSTS etc. To quote the very nicely detailed 1987 F3 TACMAN which has been declassified

I remembered this thread 4 years ago by the pilot. SPO doing its SPO things and a technician showing it could be fixed if it helps clear things out And there you have the RWR being blinded by the radars, and the N019 itself too...

Eh, I've read/heard cases where it isnt the case. If not, just locking would put the enemy on the defensive. Its not that simple

With the only difference between PDI before and after launch is the use of burst ranging while the missile is off? How often would it need to do burst ranging to improve accuracy? I wouldn't say it does it in intervals <1sec. The RWR would've to fulfill, 2 conditions. STT and nonRG HPRF (if no burst rangine after x amount if time). Imo, it is pushing it on hypotheticals. Not even more advanced and complex RWRs of western were able to know if there's launch as you can read on the Tornado F3 Tacman.

I forgot about the burst ranging part. However, the burst ranging is not for PDI. It's also used during normal STT coming from RGHPRF, VS acq and even MPRF to improve range accuracy. On the best case scenario. IF you could detect the difference between PDI and normal RGHPRF Track, you wouldn't get a warning when a missile is launched. You would get a warning that he is under the missile guidance waveform(PDI), meaning you simply don't know if there's a missile in the air. Had west germany erupted, warsaw bloc pilots would've taken nasty surpises straight up their cockpits. Like my PFP shows, straight into the hud.(IF the umbilical had been properly connected to the F15)

Logically no(bc there's no other signal other than the STT HPRF and if it changes, the change occurs when missile is selected and target is under 1.2Rmax) and everything points towards it. No clue at all

On the apg-65, the Hi PRF of RWS/STT/TWS is Range Gated. It's at a lower duty cycle(~33% according to the case study)and lower PRF(if I'm not mistaken?). So mprf like processing and (FM rangine used too?). On that manual it states For VS I just think a high PRF and high duty cycle. The PDI (Hi PRF) is commanded by the apg 65 if the sparrow is selected and the target is under 1.2Rmax They shouldn't detect F14s/15/18s. Tornado F3 tacman states that a locks from planes that guide SAHR through HPRF should be taken as a missile in the air and be defensive. And THAT RWR was quite advanced for its time and showed ALOT of information. If you look at the emitter list, you have the fighter(lets say mirage) and under it a different signal, IM, for mraam. F14 has one, as it used both PD and CW. But no extra signal for F18/15. Why not? The CW section is considerably large in time to tell the difference between a pulse and a continuous wave. As you know it switches back and forth between CW and Pulse. ~30ms cw and ~20ms for pulse. The pulse is 1.25-1.5 microsec and HPRF is 160-220kHz. You can fit 4800-6600pulses. Mathematically, you can consider the CW part as a cw infront of the pulse.

It's just the transition from either Radio Correction or INS to SAHR during missile flight. Yeah the process is automatic, but it WON'T switch at a range when it sees the target. It will switch when it reaches (just under so it sees the target)either 40km, 25km, 12km, by a command given by the radar to do it after x amount of time after launch. Those ranges depend on the what the pilot selected here. Should be this switch on the weapons console As for Altitude. If H/M PRF and target is above 1km alt, the missile will transition to SAHR at the distances above. If target is under 1 km, and MPRF the previous transition ranges are reduced to 5km, 3.125km, 1.5km respectively. 1/8ths of the previous ranges

It should, if its able to detect it and lock it. For a 3m2 target. On HPRF detection range is ~70km in a high alt-look up geometry. If its flying at lower altitudes (sub 3km) and its still a look up scenario, ~64km If its flying at low altitudes and its a look down scenario, it falls down to ~40km. MPRF( much lower ranges so ill not put them) Tracking ranges are stated to be achieved at 70% of the maximum detection range. If a lock is achieved the pilot can select the time( thus range to target) the R27R/ER switches from Radio Correction to SAHR. The seeker head must be able to see the target if you don't want it wasted. The seeker head detects the 3m2 target at 25km, this is "your average fighter" sized target. If you do the math RCS corresponds to 20m2 for bombers( which corresponds for a bomber size target on the Mig 25 manual), 25m2 for fighters and 0.16m2 cruise missiles So yes it can, you just need to detect it and lock it.

It's from the Tornado F3 tactics Manual. Those are ACMI flyouts. Dunno if someone can test them null YES its declasssified

@Chizh I want to know if F-18s, F-15s, F-14s(with PD selected) still give the enemy indication on the RWR when they launch sparrows? Because how can they know when exactly launch if there's no signal change when it's done nor an additional one. STT warning should be the most unless the RWR starts screaming missile launch if the signal strength is strong enough( short range). Compared to a phantom which will start illuminating the area with CW energy once a missile launches or the N001/N019 which will interleave between pulsed for tracking and CW for missile guidance

If I'm correct, antenna nutation for tracking is modelled. Will the AIM7E's as well have this detail?

Nice to know! That would require to know the content of dipoles in the cloud but could be simplified. But still, at 10N.M the mainlobe would be looking almost half a N.M behind of a beaming target.

How will the interaction with chaff be? Will RCS modeling be improved? This would be an issue for the phantom's apq120. Especially with chaffing targets. Target RCS is constant right now, independent of aspect. Lets say the target is 7m² and chaff cloud for example 310m²( following ada151928, the RCS of a mature cloud would be N(0.155A²), where N is amount of dipoles- ex. 1.8million- and A the wavelength of radar-ex9Ghz radar-) . For track to switch to the chaff, the power centroid should be closer to the chaff cloud thus the target will leave the resolution cell. So a small chaff cloud should be able to decoy the radar easily. But on a beaming target, the RCS increases considerably. For example the tornado f3 side aspect can get close to 1500m². Same as the mig 21s rcs(1000m²) With a higher rcs, the power centroid should be closer to the target, therefore keeping lock better and not having just a single chaff transfering the lock away. And the typically when you turn while defending you show your belly and whole wing area.... Same way that a 1000m² rcs will show up longer range and brighter than a 10m² rcs target on the radar scope. Would like to hear about this since it's something that will really suck using the phantom (having 1 (ONE) chaff pull the lock away) This is something that can easily be worked on ED's side. Make RCS increase side aspect, nothing hard and complex. A simple function f depending on angle off nose and initial rcs, f(θ, σ). May not be the most accurate but 7.3 gorillion miles better that what currently is in use.

You don't need a suite with MSIP 1000000LM 2K20 ENHANCED LIMITED GOLD EDITION to notice CW( within the frequency it looks at) in your direction. Knowing that CW was typically used solely for missile guidance, you can just declare there's a missile in the air. Now, to identify the frequency hops for guidance, frequency used, modulation and say that's X plane guiding a missile instead of Y is another thing. To detect it would be a matter of frequency bands that it sees. Like the MiG29 vs a phantom guiding a SAHR. Phantom will guide with a nonstop CW between 10.050-10.250 GHz with 350KHz modulation/85 Hz FM. A MiG29 will send for 20ms a HPRF/MPRF waveform then for 30ms will send CW in X band frequency with 2 subcarrier frequencies at 208 and 228K Hz depending on guidance instructions. Old rusty RWR which can only tell if its CW or pulsed will see and show 2 emitters(AI-CW) from the phantom(LPRF/HPRF waveform and CW), for the Mig 29 it'll see 2(MPRF/HPRF and CW) switching between each other. Here it probably show both. Probably it will not be able to tell the difference between a phantom or Mig29 radar. MSIP 1000000LM 2K20 ENHANCED LIMITED GOLD EDITION will know the modulation and frequency from the phantom and if they come from same direction, declare that the F4 is firing a missile at you. Showing 1 emitter. With the MiG29, it will recognize the switching pattern and/or frequency modulation from the CW and therefore declare that a specific Mig29 is guiding a missile. Showing you 1 emitter.

From what I know, there isn't a 9.13 manual available online like the 9.12s. Especially one which contains detailed information on systems such as the бортовой комплекс САМОЛЕТОВОЖДЕНИЯ, ПРИЦЕЛИВАНИЯ И УПРАВЛЕНИЯ ВООРУЖЕНИЕМ САМОЛЕТА МиГ-29Б (СУВ-29Э и сопрягаемые системы) which has detailed information regarding the systems. And I don't think stuff like the guidance method(CW) would've been changed, perhaps on the coding and frequencies to reduce jamming. But I've never read about CW dropped. Which is what gives a launch warning