A) A bigger payload competes with both structural strengthening and range requirements for weight. This is a tough balance to strike.Because of:
A: the "compromises" on one platform (carrier based manned fighter) I believe may not be substantial
B: the purpose of a stealthy strike UCAV and a 5th generation manned fighter capable of carrying JSM class weapons do not fill the same niche and can be very complementary to one another.
B) Perhaps. But if a stealthy strike UCAV can handle the same payload, that is an overlap of niches. It can simply take over the role. Ferrying a standoff weapon into range is a waste of a fighter frame. It makes more sense for the fighter to play complement to the UCAV carrying the stand off weapon rather than vice versa. Putting a stand off payload in the UCAV doesn't compromise it and it lets you maximize the mission flexibility of the fighter.
The kinematic and RCS impact is only temporary on the second proposal.I would prefer the former to be honest, because for the strike role I believe the RCS, and the adverse effects on kinematics will be worst for your second proposal rather than the first.
I don't think it makes much sense, doctrinally, for the PLAN to prioritize strike at the cost of some degree of A2A capability if they are also developing a dedicated strike UCAV. If the intention is to develop such a UCAV, then you won't need a manned stealth fighter to have larger payloads to conduct deep penetration strikes because the UCAV would be a better fit for such a role, and deep penetration strikes on a clean stealth configuration would be the primary reason you'd want a bigger weapons bay.The first option will obviously limit the kinematics of the aircraft in A2A domains to a degree, and will result in a worse RCS compared to a "clean" second option, but I expect the naval stealth fighter to have strike as one of its primary missions rather than a secondary mission.
Furthermore, I'm not sure having a manned stealth fighter that compromises A2A capabilities for strike capabilities fits with what we can guess about China's intended carrier doctrine going forth. A2A, I'd argue, is more important for the PLAN's carrier doctrine, given their likely mission profiles and lack of PLAAF mission support when projecting power to distant geographies, than it is for the USN's carrier doctrine.
The first option forces you to live with a compromise between strike and A2A kinematics in perpetuity. The second option lets you convert between strike and A2A kinematics, and recover your A2A kinematic abilities the moment you've unloaded your strike package. Kinematic penalties aren't a big deal for strike missions, but they adversely affect A2A capabilities. Stealth may be a trickier consideration for the second option, but if we're talking about a design with a cleaner exterior than the first option the penalty from carrying an external package that's been shaped to minimize RCS contributions may not be much worse than a chunkier airframe.Meaning in terms of overall adverse effect on stealth and kinematics over the primary missions which the naval fighter will be expected to conduct, I expect the first option to have overall less adverse effect than the second option, simply because I expect the fighter to conduct strike missions fairly frequently as part of its mission requirements.
Even if a future manned naval stealth fighter conducted strike missions fairly frequently, not all or even most of those missions will require larger payload capacity in combination with a clean stealthy exterior, especially if there will be other dedicated platforms that perform strike roles.
Of course, this is also assuming that we are comparing the "adverse" stealth and kinematic effect on the first option to be similar in degree to the transition between X-35 and F-35. That is to say, it won't suddenly mean that a naval large belly variant of J-20 will suddenly be incapable of supercruise if the land based version is capable of it.
As I said, I think we differ in terms of our opinion of how much the adverse effect on stealth and kinematics are.
I think maybe you're underestimating the weight and airframe penalties involved with trying to fit in a larger weapons bay in a design that will already be weight challenged by range and carrier TOL requirements. These requirements are all competing for very limited real estate. If T:W suffers too much, it could very well mean a supercruise capable A2A design loses the ability to supercruise. Remember, again, China's current design bottleneck is the engines, which will put more pressure on keeping weight down, since adding thrust is not likely to be the viable get out of jail card it has proven to be for the JSF.
Again, that's assuming F-35's development troubles are due to the modifications of F-35's performance requirements from X-35, rather than other program management factors.
think if they had not forced a B variant into the F-35 so early, and if they had modified the procurement policy and if they had not porkbarrel'd the F-35, then I think the program would be much more successful.
I think the F-35's capabilities even on an individual aircraft basis are very great and couple that with all the variants they have and the overall number they will produce and couple that with the multiplicative effect of datalinking F-35s together with shared upgrades... I feel like the F-35 won't just be a "capable fighter" but will likely be THE most capable fighter type of its time, moreso than F-22, J-20 or Su-57 or others.
The X-35 that flew was optimized for an A2A role. The program delays and cost overruns that followed weren't a consequence of bad procurement, but a consequence of trying to engineer too many requirements into a single airframe. Sure, if you take out the B variant those problems may have been less severe, but even then with the F-35C we're talking about a product that the USN seems to tacitly consider a compromised solution. It's telling that the USN has already decided it won't be teaming up with the USAF again for a 6th gen fighter, and I think that speaks volumes about what they feel like they got from the JSF.
Last edited: