It does raise the interesting question as to why RVL, rather than VL, was not made the basis for the requirement. Particularly since HGI was one of the main problems with the Boeing design.
Aussie/Swerve – So if RVL/STOL will be the norm on austere surfaces (defined as what? Anything other than US air base concrete protected by an AM-2 heat/blast-shield?) does anyone know when it will be tested and practiced? And what kind of landing guidance will be used in adverse conditions?
It would also be ironic, given the amount of trouble taken to avoid hot-gas ingestion in VL, if the standard recovery mode were to be RVL or VL on a moving ship.
MrMalaya – Your answer will be found on Pprune, but basically the UK has a “Persian Gulf hot day” standard that is hotter than the KPP spec.
Swerve – Sure, you can do an RVL. But if it is a slow-roller, there are still ground impact issues, and the faster it is, the more other issues (like getting weight on wheels for braking and steering, and TD point scatter) become important. And VL allows you to recover off your primary runway, which is useful if you have only one RW.
You are forgetting about EODAS. If you are close enough to be in a turning fight, then you are likely within the NEZ of the Aim-120D regardless of the launch angle.
So are the other members of the shooter’s formation.
Neither AIM-120D nor EO-DAS are magic. The former requires more time to turn off-boresight than a thrust-vectoring HOBS missile and I believe the seeker gimbal is +-45 degrees. The latter is trying to maintain a dynamic 3D situational picture with only Az-El position and rate data. Plus the standard missile datalink functions only within the fighter radar FOV, as far as I know.
Re: Austere landings – 2 free internetz awarded to anyone producing a pic of an F-35B doing an ashore VL on anything other than concrete protected by AM-2.
MD – The byline says it all. Thompson is a consultant to P&W and advocated the termination of the F136, promoting the completely false notion that the F135 had been selected for the JSF SSD phase through competition. (Both CDA teams used P&W’s F119-based X-engines for the X-32 and X-35, but the timing precluded any real competition.)
It’s interesting that PW is now trying to squash Advent, which is needed for the new bomber but would (if it works) be a big improvement for the F-35, and could arrive in time to power a lot of the A-models.
The helo operator will get a bigger shock when MoD sends them the bill.
It’s also an architecture issue.
The F-35 inherited the F-22 architecture, with peripherals (remember them?) controlled by an integrated central processor (ICP). Through the mid-1990s, that was how you could put all the horsepower needed for EMCON and sensor fusion on a fighter – through shared processing.
The drawback is that everything is related and integrated, so changing things involves tons of regression testing.
Today, you can (and prefer to) stick all the processing, and indeed all the memory, you could ever want right behind all the sensors and feeds, and you make them talk to one another. If you notice, the Super H has quite a high degree of sensor fusion, but it runs through the display processor.
The engine is not “hobbled”. Performance calculations include a normal margin for deterioration between overhauls, which LM hopes can be whittled away.
Aurcov – AESA development has been continuing in a healthy manner outside the JSF program, as witness APG-63, RACR and the Selex range.
And the F-15 DEWS may share some technology with the JSF fit, but will have an active mode and different antennas.
Spud – You done gone lost me on that chart.
On TR-2 I see onboard S/W in the red and offboard not started.
Spud – Since the AG report apparently schwacks the DND, I’d wait to read it before jumping to conclusions.
And the avionics are not “mostly done” because prototypes have been through some exercises on the FTB. That’s some serious wandering into the Baghdad Bob zone.
Spud – Surely the slip in IOT&E completion reflects a slip in IOT&E start, which in turn reflects a slip in completion of DT? Or are you suggesting that the JSFPO and the Pentagon are imposing some random delay?
And IOT&E is, one accepts, not about developing the system. It’s about confirming that the system conforms to requirements under operational conditions.
Also, the slip shows the extent to which the Japanese “competition” was an exercise in politics. Boeing and EF were offering combat-ready aircraft in 2016, according to the requirement, but this was apparently waived for the JSF.
Loke – That may be true, insofar as the only way to make the F-35 win a contest is to tailor the rules to it, while making up estimates for the cost of other aircraft. Watch for emerging news…
Spud – You might care to reconsider your “the majority of the avionics work is done” in the light of the fact that IOT&E completion has just slipped another three years, to 2019.
Breaking News:
Canada to withdraw from F-35 programme. Will consider F-18F and F-15 variants as an alternative.
Might be a little less of the old poisson d’avril to this by tomorrow. Sounds like the auditor-general’s ready to put the boot in.
Midwave was originally chosen because it had better, more photo-quality resolution at range. I believe that LW is slightly better for atmospheric transmission, in theory, and some IRSTs* either stayed in LW or went dual-band. I think the LockMart IRST may still be LWIR but Selex Galileo has now gone MWIR-only. And all the unclass missile-defense work with airborne IR tracking has used standard Reaper MWIR hardware.
* Real IRSTs. Not the “I’m not an IRST but I play one on TV” excuses on certain aircraft.
xxxx Disruptive behaviour. xxxx
MSphere – Actually I think the sensors are 1024 x 1024, which is OK but not marvellous over a 60deg x 60deg field of view.