A mechanical radar like the Captor needs around 2 whole seconds to go from 9 O ‘clock to 3 O ‘clock , then the scan rate during the plate rotation is way slower than a simple Pesa radar since the beam is not electronically steered . I am not even talking about the time needed to scan the vertical plane as the radar is rotating , but I should 😉
As an example , the fixed RBE2-AA scans the entire field of view in about 100 nanoseconds . You can multiply this by 50 for the Pesa RBE2 (one beam) . Now , do the math 😉
Captor has quoted ranges of 370 km vs transport a/c (Boeing 747) and 185 km for fighters. It can track something like 20-30+ targets and uses interleaved RWS, TWS and VS – quoted tracking range is 160 km vs a 5m2 target. It can TWS in its entire 120° arc due to high mechanical speed. It has automatic IFF and NCTR. The display shows own missiles a 2-D plan and elevation view. ECCM is high – it has dedicated ECCM data processing..
Where does the 2 seconds come from? Assuming its correct Captor could go from initial detection to tracking inside of 10 seconds.
Are you sure on the 100 nanoseconds? This doesn’t appear to make sense.
A radar (even PESA and AESA) needs to pause whilst a radar pulse travels to and from a target.
Transposing R = cDt/2
R = Range
Dt = Detection time
c = speed of light or approx 300,000 km/second
/2 = radar needs to head out and come back
Assuming say R=100 km
Dt = 2R/c
Dt = 200/300,000
Dt = 0.006666 seconds (say 7 milliseconds or 7000 nano seconds)
That is for one pulse…..
For the 100 nanoseconds above, R= 15 meters.
March 2006 Combat Aircraft mentions RBE 2 can detect new targets in ‘seconds’ – ISTR it gives a suggested kill list and can launch a Mica every two seconds against up to 8 targets, whilst tracking a further 32 a/c.
Sign In
