-
Hi Guest! Forum rules have been updated. All users please read here.
Tornado ADV (F2/F3) Avionics
- Thread starter overscan
- Start date
- Joined
- Dec 27, 2005
- Messages
- 11,534
- Reaction score
- 942
Foxhunter Radar
AI24 Foxhunter Radar
Development
In the early 1960s, RRE (Radar Research Establishment) Great Malvern and Elliott began research into a new type of radar they called FMICW (Frequency Modulated Interrupted Continuous Wave), with possible application in two areas; AI (airborne interception) and AEW (airborne early warning). In a frequency modulated continuous wave (FMCW) radar a continuous wave is smoothly varied in frequency over time. The frequency of received radar signals is then compared with that being currently emitted in the receiver. The combination of the two waveforms gives frequency-triplets which can be decoded to give target range and range rate. However, as radar energy emission is continuous, it needs separate transmit and receive antennas which is not practical in airborne applications.
FMICW complicates this by periodically interrupting the waveform to allow a single antenna to both transmit and receive. This introduces additional complexities to the design over FMCW via PRF intervals and harmonics. However it seemed a method to allow good lookdown detection capability and be a promising alternative to the US AMTI solution used in the E-2C Hawkeye.
In 1963 studies started for a naval AEW aircraft which became the Blackburn P.139. By 1965, FMICW radar technology was looking very promising and the P.139 had settled on an FASS (fore-and-aft scanner system) radar with inverse-cassegrain antennas using FMICW. However, in 1965 the UK carrier fleet was axed and the P.139 consigned to history.
Work continued in Britain on FMICW despite these setbacks. In 1967 a prototype radar flew in a Canberra. A prototype of an FMICW AEW radar was under construction in 1971 but was cancelled on cost grounds, and also because the US was building its new E-3 AWACS with a High PRF Pulse Doppler radar, which worked on slightly different principles to the UK FMICW approach.
By 1967 Britain was formulating the Operation Requirement for the MRCA, and hit upon the idea of an air intercept variant to replace the Phantom in the air defence role. The Tornado ADV (Air Defence Variant) requirement was formulated as long ago as 1969. However, the ADV version was not considered a high priority in the early stages, as the RAF was only just receiving brand new F-4M Phantoms, and a replacement wouldn’t be needed until the early 1980s. Indeed, the contract for AI24 wasn’t signed until 1976, though Marconi had flown test hardware prior to this.
Marconi-Elliott were given responsibility for developing the AI24 radar for the ADV (incidently, the “Foxhunter” name was never official; the designation for the radar was just AI24) with Ferranti supplying some components. Requirements for AI24 were ambitious. ADV was expected to intercept Soviet bombers and cruise missiles at extended distances, at high and low altitudes. Detection range for a typical bomber was to exceed 100 nautical miles (185km) and the radar was expected to track multiple targets simultaneously. Emphasis was placed on ECCM capabilities as the intended targets were assumed to use powerful ECM systems. Lookdown detection ranges were expected to be as great as possible.
In order to meet these tough requirements, Marconi-Elliott decided to base AI 24 on their longstanding work on FMICW radars, which had seemed to offer strong lookdown performance and long range detection, and, crucially, was thought to offer good resistance to ECM.
The US meanwhile had moved on from AMTI to modern pulse-Doppler radars. The F-14’s AWG-9 was a High PRF pulse Doppler radar with FM ranging for long range target detection. Marconi’s own FMICW concept was largely a version of the same concept, the distinguishing features of FMICW being extremely high PRFs, very high duty cycle (near 50%), and the use of a single range gate; that is, rather than dividing the interpulse receiving period into individual range cells corresponding to targets at different ranges and analysing them separately, a single sample was taken of the whole interpulse region. This integrated the returns (and hence clutter) from many range cells into a single range gate. The magnitude of the ground clutter is therefore typically high, 80-90dB above thermal noise, requiring an exceptionally good dynamic range signal processing chain, extremely low sidelobe levels and a very pure transmitted signal to allow successful target detection. However, it simplified the processing as only a single set of Doppler filters needed to be formed, rather than multiple filters for each range gate. Early FMICW radars used analogue processing; for AI24 Marconi used digital signal processing.
A fibreglass based, twist-cassegrain antenna was selected, for two main reasons. Firstly, very low sidelobe levels were thought to achievable, which helped in ECM resistance and was also important as outlined above for FMICW performance. Additionally, the resulting antenna was extremely lightweight (just 3lb!), which reduced inertia and allowed rapid scanning, which would be helpful in track-while-scan mode.
Following early trials of test radars in a Canberra from 1975, and from 1976 a Buccaneer (XX897) assigned to RRE, the first flight of a Foxhunter in a Tornado was made on 17 June 1981. The original forecast in-service date for the Foxhunter radar was 1982. By 1983, the “B” version was flying in Tornado ZA283, but production radars were still two years away.
The first batch of 18 Tornado F2s were delivered without radars, and had to be fitted with ballast in the nose to compensate for the weight of the missing radar. This lead to the now famous “Blue Circle radar” joke (Blue Circle being a British manufacturer of cement, and handily following the pattern of British radar designations like Blue Fox, Blue Vixen etc). Foxhunter did not enter service until 1985 and then only an interim standard version that didn’t meet requirements, despite a 63% increase in development costs.
Not all the problems were of Marconi’s making. Part of the problem was the lack of experience in fighter radars in Britain. The last indigenous fighter radar had been the Ferranti AI23 for the Lightning, but while Ferranti had built the US AWG-10 pulse-Doppler radar under license, Marconi had comparable recent experience to draw on. It was still expected to produce radar to roughly equal the AWG-9, the most powerful and expensive fighter radar in the world, at lower cost. Yet the actual contract was an old-fashioned “cost plus” contract where the government agreed to pay all costs plus a percentage profit, rather than a fixed price, which some industry observers feel contributed to the late service entry and problems encountered.
In some respects, the early Foxhunter was actually slightly inferior to the AWG-12 radar on the British F-4 Phantom II. No tail-chase programming was initially requested, and this had to be added later, as did close combat modes. A 20 target TWS capability was required, but was optimised for bomber raid assessment and targeting, not manoeuvring combat. Whilst it worked well in testing against drone targets, in service it proved unable to correctly track multiple targets making turns and moving in less predictable ways. Allegedly, it had problems with detecting lower RCS targets in clutter, and Hawks used in air training with the Tornado F3 were fitted with radar repeater pods.
Marconi and the UK government agreed a multi-year plan to bring Foxhunter up to an acceptable standard. By 1988, “Stage 1” radars were introduced into production which fully met the basic requirements of the RAF. These were to be followed by the definitive “Stage 2” radars, with new programmable digital processors. For the Gulf War in 1991, an emergency “Stage 1+” was introduced, to give some of the “Stage 2” capabilities to the “Stage 1” radar, but crucially this did not include the vital NCTR (Non Cooperative Target Recognition) mode as this feature required the new upgraded processors of "Stage 2”. The lack of NCTR relegated the F3 to a secondary air defence role well behind the front line. This was introduced with the “Stage 2G” in 1996, and further refined since then.
Since Stage 2 there have been continuous programmes of improvement for the Foxhunter, which are detailed later in the “Variants” section. The latest standard of AI24 radar supports the AIM-120 AMRAAM, and finally lives up to the original promise of this troubled radar design.
AI24 Foxhunter Radar
Development
In the early 1960s, RRE (Radar Research Establishment) Great Malvern and Elliott began research into a new type of radar they called FMICW (Frequency Modulated Interrupted Continuous Wave), with possible application in two areas; AI (airborne interception) and AEW (airborne early warning). In a frequency modulated continuous wave (FMCW) radar a continuous wave is smoothly varied in frequency over time. The frequency of received radar signals is then compared with that being currently emitted in the receiver. The combination of the two waveforms gives frequency-triplets which can be decoded to give target range and range rate. However, as radar energy emission is continuous, it needs separate transmit and receive antennas which is not practical in airborne applications.
FMICW complicates this by periodically interrupting the waveform to allow a single antenna to both transmit and receive. This introduces additional complexities to the design over FMCW via PRF intervals and harmonics. However it seemed a method to allow good lookdown detection capability and be a promising alternative to the US AMTI solution used in the E-2C Hawkeye.
In 1963 studies started for a naval AEW aircraft which became the Blackburn P.139. By 1965, FMICW radar technology was looking very promising and the P.139 had settled on an FASS (fore-and-aft scanner system) radar with inverse-cassegrain antennas using FMICW. However, in 1965 the UK carrier fleet was axed and the P.139 consigned to history.
Work continued in Britain on FMICW despite these setbacks. In 1967 a prototype radar flew in a Canberra. A prototype of an FMICW AEW radar was under construction in 1971 but was cancelled on cost grounds, and also because the US was building its new E-3 AWACS with a High PRF Pulse Doppler radar, which worked on slightly different principles to the UK FMICW approach.
By 1967 Britain was formulating the Operation Requirement for the MRCA, and hit upon the idea of an air intercept variant to replace the Phantom in the air defence role. The Tornado ADV (Air Defence Variant) requirement was formulated as long ago as 1969. However, the ADV version was not considered a high priority in the early stages, as the RAF was only just receiving brand new F-4M Phantoms, and a replacement wouldn’t be needed until the early 1980s. Indeed, the contract for AI24 wasn’t signed until 1976, though Marconi had flown test hardware prior to this.
Foxhunter prototype on bench
Marconi-Elliott were given responsibility for developing the AI24 radar for the ADV (incidently, the “Foxhunter” name was never official; the designation for the radar was just AI24) with Ferranti supplying some components. Requirements for AI24 were ambitious. ADV was expected to intercept Soviet bombers and cruise missiles at extended distances, at high and low altitudes. Detection range for a typical bomber was to exceed 100 nautical miles (185km) and the radar was expected to track multiple targets simultaneously. Emphasis was placed on ECCM capabilities as the intended targets were assumed to use powerful ECM systems. Lookdown detection ranges were expected to be as great as possible.
In order to meet these tough requirements, Marconi-Elliott decided to base AI 24 on their longstanding work on FMICW radars, which had seemed to offer strong lookdown performance and long range detection, and, crucially, was thought to offer good resistance to ECM.
The US meanwhile had moved on from AMTI to modern pulse-Doppler radars. The F-14’s AWG-9 was a High PRF pulse Doppler radar with FM ranging for long range target detection. Marconi’s own FMICW concept was largely a version of the same concept, the distinguishing features of FMICW being extremely high PRFs, very high duty cycle (near 50%), and the use of a single range gate; that is, rather than dividing the interpulse receiving period into individual range cells corresponding to targets at different ranges and analysing them separately, a single sample was taken of the whole interpulse region. This integrated the returns (and hence clutter) from many range cells into a single range gate. The magnitude of the ground clutter is therefore typically high, 80-90dB above thermal noise, requiring an exceptionally good dynamic range signal processing chain, extremely low sidelobe levels and a very pure transmitted signal to allow successful target detection. However, it simplified the processing as only a single set of Doppler filters needed to be formed, rather than multiple filters for each range gate. Early FMICW radars used analogue processing; for AI24 Marconi used digital signal processing.
A fibreglass based, twist-cassegrain antenna was selected, for two main reasons. Firstly, very low sidelobe levels were thought to achievable, which helped in ECM resistance and was also important as outlined above for FMICW performance. Additionally, the resulting antenna was extremely lightweight (just 3lb!), which reduced inertia and allowed rapid scanning, which would be helpful in track-while-scan mode.
Buccaneer XX897, used to test Foxhunter
Following early trials of test radars in a Canberra from 1975, and from 1976 a Buccaneer (XX897) assigned to RRE, the first flight of a Foxhunter in a Tornado was made on 17 June 1981. The original forecast in-service date for the Foxhunter radar was 1982. By 1983, the “B” version was flying in Tornado ZA283, but production radars were still two years away.
The first batch of 18 Tornado F2s were delivered without radars, and had to be fitted with ballast in the nose to compensate for the weight of the missing radar. This lead to the now famous “Blue Circle radar” joke (Blue Circle being a British manufacturer of cement, and handily following the pattern of British radar designations like Blue Fox, Blue Vixen etc). Foxhunter did not enter service until 1985 and then only an interim standard version that didn’t meet requirements, despite a 63% increase in development costs.
Not all the problems were of Marconi’s making. Part of the problem was the lack of experience in fighter radars in Britain. The last indigenous fighter radar had been the Ferranti AI23 for the Lightning, but while Ferranti had built the US AWG-10 pulse-Doppler radar under license, Marconi had comparable recent experience to draw on. It was still expected to produce radar to roughly equal the AWG-9, the most powerful and expensive fighter radar in the world, at lower cost. Yet the actual contract was an old-fashioned “cost plus” contract where the government agreed to pay all costs plus a percentage profit, rather than a fixed price, which some industry observers feel contributed to the late service entry and problems encountered.
In some respects, the early Foxhunter was actually slightly inferior to the AWG-12 radar on the British F-4 Phantom II. No tail-chase programming was initially requested, and this had to be added later, as did close combat modes. A 20 target TWS capability was required, but was optimised for bomber raid assessment and targeting, not manoeuvring combat. Whilst it worked well in testing against drone targets, in service it proved unable to correctly track multiple targets making turns and moving in less predictable ways. Allegedly, it had problems with detecting lower RCS targets in clutter, and Hawks used in air training with the Tornado F3 were fitted with radar repeater pods.
Production Foxhunter
Marconi and the UK government agreed a multi-year plan to bring Foxhunter up to an acceptable standard. By 1988, “Stage 1” radars were introduced into production which fully met the basic requirements of the RAF. These were to be followed by the definitive “Stage 2” radars, with new programmable digital processors. For the Gulf War in 1991, an emergency “Stage 1+” was introduced, to give some of the “Stage 2” capabilities to the “Stage 1” radar, but crucially this did not include the vital NCTR (Non Cooperative Target Recognition) mode as this feature required the new upgraded processors of "Stage 2”. The lack of NCTR relegated the F3 to a secondary air defence role well behind the front line. This was introduced with the “Stage 2G” in 1996, and further refined since then.
Since Stage 2 there have been continuous programmes of improvement for the Foxhunter, which are detailed later in the “Variants” section. The latest standard of AI24 radar supports the AIM-120 AMRAAM, and finally lives up to the original promise of this troubled radar design.
Attachments
- Joined
- Dec 27, 2005
- Messages
- 11,534
- Reaction score
- 942
Re: Foxhunter Radar
Detailed Description
Foxhunter weighs about 300kg altogether, slightly more than half the weight of AWG-9 and slightly heavier than the APG-63.
Contrary to other reports, Foxhunter is primarily digital in design. Indeed, its adoption of digital signal processing was perhaps premature given the technology levels available, and was not until Stage 2 replaced the processors that it really lived up to expectations.
It uses two separate IF receivers; one for FMICW modes and one for Pulse modes, as the optimal characteristics of each mode were impossible to accommodate in a single unit. Pulse modes use SAW (Surface Acoustic Wave) compression.
FMICW modes use FM modulation of the waveform for ranging. The received signal is processed using digital signal processing techniques.
Processors are a mixture of hard wired, firmware microprocessor and digital programmable technology. The Frequency Analyser uses hard wired Schottky TTL and LSI circuits.
A high speed, wide dynamic range, A/D Converter takes the analogue signal from the FMICW IF (intermediate frequency) receiver and converts it to digital samples. The digital samples are analysed in the Frequency Analyser using FFT algorithms which vary depending on the period of FM ranging modulation.
A weighting process reduces the spreading caused by the short sampling period, followed by an automatic detection process. The detector uses a constant false alarm (CFAR) process which continually adjusts the detection threshold as a function of the combined clutter and receiver thermal noise levels. Signals exceeding this threshold level are passed to the range correlator which determines range by comparing the outputs from different phases of the FM waveform. The final stage is a plot extractor which produces a well defined and unique output of the range and range rate of each target.
Twist Cassegrain antenna of the type used on Foxhunter. A fixed feed (A) emits polarised radar energy forwards. The radar hits a hyperboloid sub-dish (B), with embedded wires parallel to the plane of polarisation, which reflects the radar signal. It then hits the paraboloid main reflector (C) where the polarisation is twisted by 90 degrees by wires arranged at 45 degrees to the plane of polarisation. The radar signal then bounces forward again, but due to its changed polarity now passes straight through the sub-dish.
Detailed Description
Foxhunter weighs about 300kg altogether, slightly more than half the weight of AWG-9 and slightly heavier than the APG-63.
Contrary to other reports, Foxhunter is primarily digital in design. Indeed, its adoption of digital signal processing was perhaps premature given the technology levels available, and was not until Stage 2 replaced the processors that it really lived up to expectations.
It uses two separate IF receivers; one for FMICW modes and one for Pulse modes, as the optimal characteristics of each mode were impossible to accommodate in a single unit. Pulse modes use SAW (Surface Acoustic Wave) compression.
FMICW modes use FM modulation of the waveform for ranging. The received signal is processed using digital signal processing techniques.
Processors are a mixture of hard wired, firmware microprocessor and digital programmable technology. The Frequency Analyser uses hard wired Schottky TTL and LSI circuits.
A high speed, wide dynamic range, A/D Converter takes the analogue signal from the FMICW IF (intermediate frequency) receiver and converts it to digital samples. The digital samples are analysed in the Frequency Analyser using FFT algorithms which vary depending on the period of FM ranging modulation.
A weighting process reduces the spreading caused by the short sampling period, followed by an automatic detection process. The detector uses a constant false alarm (CFAR) process which continually adjusts the detection threshold as a function of the combined clutter and receiver thermal noise levels. Signals exceeding this threshold level are passed to the range correlator which determines range by comparing the outputs from different phases of the FM waveform. The final stage is a plot extractor which produces a well defined and unique output of the range and range rate of each target.
Twist Cassegrain antenna of the type used on Foxhunter. A fixed feed (A) emits polarised radar energy forwards. The radar hits a hyperboloid sub-dish (B), with embedded wires parallel to the plane of polarisation, which reflects the radar signal. It then hits the paraboloid main reflector (C) where the polarisation is twisted by 90 degrees by wires arranged at 45 degrees to the plane of polarisation. The radar signal then bounces forward again, but due to its changed polarity now passes straight through the sub-dish.
Attachments
- Joined
- Dec 27, 2005
- Messages
- 11,534
- Reaction score
- 942
Re: Foxhunter Radar
Performance and Modes
Detection Ranges
(from Gruszczynski & Rybak, probably represents “Z” standard. Later models are said to have at least 10-15% greater detection ranges.)
185km vs a bomber target, head on engagement
130-140km vs a bomber target, tailchase engagement
120-130km vs a fighter target, head on engagement
75-90km vs a fighter target, tailchase engagement
Modes
Pulse Doppler Search / TWS
Target Search
Track-While-Scan
These are the primary radar modes, used for long range detection, tactical evaluation, and missile fire control. PRFs used are above 100Khz. In Search, contacts are drawn as vertical lines, with IFF friendlies drawn as crosses. The target selection marker is the -| |- shape. In TWS, each target is assigned a letter, and a line (vector) indicating target direction and ground speed. The WSO can get numeric information (including target height) on any tracked target by selecting it with the marker. Friendly targets are assigned numbers rather than letters. Target B is drawn reversed because it is currently outside the scan limits of the radar; the Memory Track feature will keep plotting the predicted path of the target (as a straight line in last known direction) to aid re-acquisition.
TWS mode can track up to 20 targets at once; if an additional track file is initiated, the radar weighs it against the existing targets and either discards it or deletes one of the existing targets.
Pilot and WSO can additionally select a Tactical Evaluation Display, which attempts to correlate all targets from radar, RWR, and datalink on a single display.
Pulse Doppler Angle Lock / CW Illumination
Angle Lock (Single Target Track)
[size=8pt]HUD presentation of the same engagement
Angle Lock is a 4 channel Monopulse single target tracking mode (Sum, Azimuth Difference, Elevation Difference, and Double Difference channels). Single target tracking is necessary to engage a target with Sky Flash; it maintains CW illumination (separately selected) on the target during missile flight. On the CRT display, TRK A LOC indicates that target A is the locked on target. MRM A indicates Sky Flash (Medium Range Missile) is armed. Note that target B remains on the display, using the Memory Track feature, reversed out to indicate it is not currently being tracked by the radar. By plotting the predicted movement of the former TWS targets during the single target lockon phase, reacquisition of the targets after reverting to TWS mode should be made easier. The HUD picture shows the pilot’s HUD presentation of the same engagement; only the locked on target is shown, as a small circle with a vector indicating direction and speed. The solid dot aiming marker must be held inside the outer Allowable Steering Error circle.
Pulse Combat
Described as “rapid target lockon of visually sighted target”.
Pulse Angle Lock
Described as “fire control of gun, very close range angle”
Ground Mapping
Basic ground mapping for navigation, using pulse compression modulation
Performance and Modes
Detection Ranges
(from Gruszczynski & Rybak, probably represents “Z” standard. Later models are said to have at least 10-15% greater detection ranges.)
185km vs a bomber target, head on engagement
130-140km vs a bomber target, tailchase engagement
120-130km vs a fighter target, head on engagement
75-90km vs a fighter target, tailchase engagement
Modes
Pulse Doppler Search / TWS
Target Search
Track-While-Scan
These are the primary radar modes, used for long range detection, tactical evaluation, and missile fire control. PRFs used are above 100Khz. In Search, contacts are drawn as vertical lines, with IFF friendlies drawn as crosses. The target selection marker is the -| |- shape. In TWS, each target is assigned a letter, and a line (vector) indicating target direction and ground speed. The WSO can get numeric information (including target height) on any tracked target by selecting it with the marker. Friendly targets are assigned numbers rather than letters. Target B is drawn reversed because it is currently outside the scan limits of the radar; the Memory Track feature will keep plotting the predicted path of the target (as a straight line in last known direction) to aid re-acquisition.
TWS mode can track up to 20 targets at once; if an additional track file is initiated, the radar weighs it against the existing targets and either discards it or deletes one of the existing targets.
Pilot and WSO can additionally select a Tactical Evaluation Display, which attempts to correlate all targets from radar, RWR, and datalink on a single display.
Pulse Doppler Angle Lock / CW Illumination
Angle Lock (Single Target Track)
[size=8pt]HUD presentation of the same engagement
Angle Lock is a 4 channel Monopulse single target tracking mode (Sum, Azimuth Difference, Elevation Difference, and Double Difference channels). Single target tracking is necessary to engage a target with Sky Flash; it maintains CW illumination (separately selected) on the target during missile flight. On the CRT display, TRK A LOC indicates that target A is the locked on target. MRM A indicates Sky Flash (Medium Range Missile) is armed. Note that target B remains on the display, using the Memory Track feature, reversed out to indicate it is not currently being tracked by the radar. By plotting the predicted movement of the former TWS targets during the single target lockon phase, reacquisition of the targets after reverting to TWS mode should be made easier. The HUD picture shows the pilot’s HUD presentation of the same engagement; only the locked on target is shown, as a small circle with a vector indicating direction and speed. The solid dot aiming marker must be held inside the outer Allowable Steering Error circle.
Pulse Combat
Described as “rapid target lockon of visually sighted target”.
Pulse Angle Lock
Described as “fire control of gun, very close range angle”
Ground Mapping
Basic ground mapping for navigation, using pulse compression modulation
Attachments
- Joined
- Dec 27, 2005
- Messages
- 11,534
- Reaction score
- 942
Variants
Sources
Jane’s Avionics
Jane’s Radar & Electronic Warfare
Jane’s Aircraft Upgrades
Hansard www.publications.parliament.uk
www.tornado-data.com
Flight International
Tornado ADV News Issues 2, 3, 7 (via www.tornado-data.com)
Press releases from Panavia, QinetiQ, BAe Systems
Aeroguide 21: Tornado ADV Linewrights, 1988
Glenn Ashley, Panavia Tornado in Action Squadron/Signal
Andy Evans, Panavia Tornado Crowood Press, 1999
J Gruszczynski, E.F. Rybak, Panavia Tornado, Lotnictwo Wojskowe, 2000 (Polish)
Bill Gunston, Modern Combat Aircraft 6: Panavia Tornado, Ian Allan 1985
Paul Jackson, Aircraft Illustrated Special: RAF Tornado, Ian Allan, 1987
Paul Jackson, ‘Panavia Tornado’ WAPJ Volume 3, Autumn 1990
John Lake, ‘Tornado Variant Briefing’ WAPJ Volume 31, Winter 1997
John Lake, Tornado: Multi-role Combat Aircraft, Midland Publishing, 2000
Doug Richardson, Modern Fighting Aircraft: Tornado, Salamander, 1986
- B initial “complete” version, flew in 1983.
- W First production version, 70 built. Fitted to Batch 4 Blocks 8 + 9, Batch 5 Block 10. 44 “W” later upgraded to “Z” standard from 1988.
- Z 80 built. Fitted to Batch 5 Block 11, Batch 6 Block 12. Broadly met initial requirements, but not the revised requirements.
- Stage 1 76 built from September 1988. Fitted from Batch 6 Block 13 to 15. Improved radar functions related to the aircraft's new F-18 style HOTAS (Hands On Throttle and Stick) controls, improved cooling (for Saudi ADV) and refined TWS and ECCM algorithms. HUD Search mode, activated by a HOTAS switch, scans the 20 deg field of view of the HUD and automatically locks on to any detected target. 124 “Z” radars were upgraded to Stage 1 software.
- Stage 1+ was rushed through in 1991 for the Gulf War. Radar designation is AA, with revised software.
- Stage 2 was intended to be the definitive Foxhunter, fully meeting the revised requirements of the RAF.
- Stage 2G was introduced from 1996; includes NCTR (Non-Cooperative Target Recognition) technology. Radar designation is AB.
- Stage 2G* upgraded the radar processors and software.
- Stage 2H upgraded the radar processor and optimised software.
- CSP (Capability Sustainment Programme) was signed 5 March 1996, providing for upgrades to 100 Tornado F3s to allow use of AIM-120 AMRAAM and ASRAAM missiles. Radar upgrades would allow multi-target engagement capability, and attempt to unify the fleet on a common radar standard. Other targets included reducing susceptibility to ECM and improved serviceability. CSP was implemented in two stages in order to deliver some operational advantages as soon as possible. First delivery was made in 1998, and both phases were scheduled to be completed by 2002. It did not include a mid-course update facility for the AIM-120 AMRAAM, due to technical difficulties.
- AOP (AMRAAM Optimisation Programme) was signed on 8 June 2001, for the provision of a mid-course guidance capability for AMRAAM on Tornado F3 aircraft, initial IOC was end 2002, and the upgrade program was concluded by late 2004.
- FSP (F3 Sustainment Programme) Signed in December 2004, FSP sets out to address a number of issues identified at the end of the AOP (AMRAAM Optimisation Programme). It includes integration of AIM-120C-5 and ASRAAM FOC2 and enhancement of the weapons systems capability, particularly the displays, through a number of radar computer and main computer software changes. In December 2005, a Tornado F3 fired two AIM-120C-5s at subsonic targets.
Sources
Jane’s Avionics
Jane’s Radar & Electronic Warfare
Jane’s Aircraft Upgrades
Hansard www.publications.parliament.uk
www.tornado-data.com
Flight International
Tornado ADV News Issues 2, 3, 7 (via www.tornado-data.com)
Press releases from Panavia, QinetiQ, BAe Systems
Aeroguide 21: Tornado ADV Linewrights, 1988
Glenn Ashley, Panavia Tornado in Action Squadron/Signal
Andy Evans, Panavia Tornado Crowood Press, 1999
J Gruszczynski, E.F. Rybak, Panavia Tornado, Lotnictwo Wojskowe, 2000 (Polish)
Bill Gunston, Modern Combat Aircraft 6: Panavia Tornado, Ian Allan 1985
Paul Jackson, Aircraft Illustrated Special: RAF Tornado, Ian Allan, 1987
Paul Jackson, ‘Panavia Tornado’ WAPJ Volume 3, Autumn 1990
John Lake, ‘Tornado Variant Briefing’ WAPJ Volume 31, Winter 1997
John Lake, Tornado: Multi-role Combat Aircraft, Midland Publishing, 2000
Doug Richardson, Modern Fighting Aircraft: Tornado, Salamander, 1986
crossiathh
CLEARANCE: Confidential
- Joined
- Jan 17, 2006
- Messages
- 54
- Reaction score
- 1
Really great. When will your new website go online?
- Joined
- Dec 27, 2005
- Messages
- 11,534
- Reaction score
- 942
A printable version
http://www.secretprojects.co.uk/ebooks/Foxhunter.pdf
http://www.secretprojects.co.uk/ebooks/Foxhunter.pdf
flogger-23
CLEARANCE: Restricted
- Joined
- Feb 9, 2006
- Messages
- 2
- Reaction score
- 0
does the audi tornado have the same foxhounter radar and avionics as the UK, or are the saudi one downgraded??
flogger-23
CLEARANCE: Restricted
- Joined
- Feb 9, 2006
- Messages
- 2
- Reaction score
- 0
does the IDS tornado use a CW/pulse radar or only a pulse radar??
JFC Fuller
CLEARANCE: Top Secret
- Joined
- Apr 22, 2012
- Messages
- 3,211
- Reaction score
- 91
Paul,
I just found this article and its fantastic, thank you for posting it! Prior to Options for Change it had been planned to MLU you the Tornado F3 in the early/mid 90s, it probably would have included JTIDS for the entire fleet (as opposed to just two squadrons as actually happened) and a multitude of radar upgrades that would have provided the type with virtually all the weapons capability that it was eventually given to it in a piecemeal fashion anyway to sustain the type until Typhoon arrived. It was referred to as a weapons system enhancement and the feasibility study was undertaken in 1990 but the project was dead by 1991.
I just found this article and its fantastic, thank you for posting it! Prior to Options for Change it had been planned to MLU you the Tornado F3 in the early/mid 90s, it probably would have included JTIDS for the entire fleet (as opposed to just two squadrons as actually happened) and a multitude of radar upgrades that would have provided the type with virtually all the weapons capability that it was eventually given to it in a piecemeal fashion anyway to sustain the type until Typhoon arrived. It was referred to as a weapons system enhancement and the feasibility study was undertaken in 1990 but the project was dead by 1991.
pathology_doc
CLEARANCE: Top Secret
- Joined
- Jun 7, 2008
- Messages
- 851
- Reaction score
- 47
flogger-23 said:
I read this as "Italian-built Tornado ADV" at first, until I got to "Saudi" and realised it was a typo! ;D