It is funny to see you defending a stance that you were so fiercely fighting against just few years ago in F-22 vs Su-xx threads. π
Looks like your logic is pretty adaptable to boundary conditions. When your favorite aircraft doesn’t have IRST, then IRST is useless. When it does have some advanced IR sensor, then suddenly the IRST becomes The Magical Solution. πAnyway, what kind of weapon will you use on those 30+nm miles distance? Your AIM-9X makes some 8-9 nm in typical situation.
I try never to state things in absolutes, so I am sorry if I did .
That being said, fighting against a VLO airframe will make BVR combat more difficult but not impossible. Besides IRST, ESM hits will also contribute to target detection. If your datalinks are uni-directional, circuits are leaky, etc then you are making it a lot easier for my ESM to find you (and my IRST to track you).
As far as a weapon goes, just because you are a VLO airframe does not mean that an active seeker cannot get you at BVR ranges. I requires a good seeker, proximity fuse, INS, datalink, and sensors on a supporting aircraft to back it up. The F-35 / AIM-120D combo should not have too much of a problem doing a 30 mile head on VLO shot in clear conditions.
btw, public documents from the SU’s manufacturer claim effective ranges that are a LOT shorter than what the F-35 carries so I do not expect parity using IRST.
That’s a F-111 wheels up landing
http://www.defence.gov.au/media/download/2006/jul/20060720.cfm
Quite on the contrary, if both opponents are LO/VLO and use correct tactics, then BVR is a no-go. The only option left is WVR.
Did you forget BVR using sensors other than radar?
IRST anyone?
LM has shown that EOTS should be able to get a solution out to 30+nm in clear weather.
It’s basically AESA for datalinks. It the beam is not pointed in your direction then there is no way that you will detect it, period.
The ESM of the F-22 is so good about detecting datalinks that it can fire an AMRAAM just on that information. The F-35 will be no different.
IIRC, Rafale’s Spectra & Eurofighter’s DASS should also be able to.
Can we please take this to the F-35 Discussion thread?
@Scooter:
I have no doubt that the new hook & damper will solve the technical issues.
I was just [sarcasm] hoping [/sarcasm] that we won’t be hearing for years how the F-35 has problems landing on the deck as some will continually forget that the issue was solved.
I don’t know at what point in the last few years you think that happened.
The 2010 re-baseline and every slide to the right since then.
EODAS takes a lot of coding to implement. Even the new F-18 “International variant” only add basic IR MAWS capability (no video or tracking).
I think one of the biggest errors in planning during SDD was the decision on how to address increased test & development demands. The DoD decided to delay IOC (in order to maintain year-to-year SDD funding) rather than increase year-to-year funding with an eye towards keeping to the schedule.
While this would have increased short-term SDD costs, it would have saved on concurrency, SLEP, and LRIP costs. It would also have gone a long way to stabilizing the Partner buys and to more FMS contracts (as the buyer would have a better idea on costs and would be buying FRP jets rather than LRIP ones).
@ obligatory:
How is MALD integration coming along on F-35 ?
While itβs in the works, details are not known. Block 4 plans should be finalized this fall, but I do not expect MALD till Blk5 at the earliest.
@Tu22m:
Riiβs original thought in post 1314 was that delaying EODAS would get to IOC sooner. While you might save some time, EODAS is an small player in the overall timeframe of F-35 development so not much time would be saved. He was postulating that the delay would save some money by not having to SLEP 4th gen airframes. However, he did not look at the increased concurrency costs with his plan.
Remember that one of the greatest lessons learned from the F-22 program is that if you do not make sure that all the hardware is part of IOC then odds are you will never get it (F-22 IRST, HMD, Cheek Arrays, etc).
All 6 EODAS sensors (not EOTS) take up less than a TOTAL of 5 cubic ft (less than 1 cf each).
Without being irrespective, only point 7 sounds right to me.
1 & 2 Current certification is based on a known set of variables. If you change those variables, some of the testing has to be redone.
3. How do you figure IR MAWS will happen without EODAS? HOw will it know that a SAM is on the way or a passive AAM is inbound?
4. The only way to do self-BDA without EODAS is to use EOTS. However, that means flying straight & level in order to keep the EOTS in view of the drop site. The EODAS’s 360 FOV means that it always has the drop site in view regardless of the F-35’s movement.
5. How else will the rear-visibility issues be corrected without EODAS?
6. Without EODAS, then it cannot correct HOBS shots if they are outside the FOV of the radar. It also cannot track WVR objects so the whole “where did he go” issue comes into play.
Exit question:
Why pick on EODAS as the one thing to leave out of IOC? Overall, it is not the part that is giving the program the most issues and is not the part that requires the most code.
IMHO there is no long term cost savings to going with SH-ish avionics at F-35 IOC and then developing more later.
The only thing that is saved is initial development funds and time.
Actually, it would cost a lot more in the long run.
1. Any new avionics will have to go through recertification again.
2. Any new hardware will have to go through a lot of physical testing.
3. Lack of EODAS at IOC means that the F-35 has no IR MAWS.
4. Lack of EODAS means a lack of self-BDA.
5. Lack of EODAS means the rear-limited cockpit visibility has no way of being corrected.
6. Lack of EODAS also means that the WVR survivability is greatly diminished since it will not be able to do significant HOBS shots.
7. Lastly, many are crying about, and have made significant cuts in order to reduce, concurrency. By not including the full hardware suite at IOC then you are increasing concurrency costs considerably.
I don’t think EO DAS is a waste of time/money. I do question whether it should’ve been part of the base F-35 program.
I don’t want to spend too much time & space on this, since it is the Gripen thread. Suffice it to say that not having EODAS as a Blk3 item but including it later would have ended up costing a lot more.
Feel free to ask this in the F-35 debate thread so the Gripen one does not get hijacked.
Iirc, LMA hinted that the F-35 Electronic attack variant would not be needed, because the NGJ could be plugged into the F-35 without serious modifications….Any more on this?
There are several contributing factors in this.
1. Dedicated Fiber Optics: Every A2G station (even the belly one) have a dedicated fiber optic connection to the ICP (Central Computer) . This alleviates the need to “re-wire” the F-35 for the NGJ, or any other future pod. The beauty of Fiber is that to upgrade it, you only need to upgrade the transceivers at each end. Currently the F-35’s fiber is single channel, but they are already working on a multi-channel over a single fiber version.
2. An extra ICP: When the F-35 underwent TR-1 (Tech Refresh) during Block upgrade 0.5 the rear ICP (about 1/3 the size of the Primary ICP) was removed. However, the space was left alone for future upgrades. What this means is that if the NGJ needs more ICP space than the Primary ICP can provide, the rear ICP can be used without the need for airframe changes, rewiring, etc.
3. Middleware: The avionics of the F-35 are designed so that changes in hardware do not require a complete redo every time hardware changes. A layer of software called Middleware interacts with the hardware and only the middleware needs to be changed when the hardware changes.
4. UAI: While the first 4 versions of UAI deal with munitions, talk has arisen that UAI would also start to cover pods.
5. Power & Cooling: The NGJ handles its own power & cooling needs so nothing from the F-35 (or any other fighter) is needed in those areas.