Jian's vs F-22/F-35??

Status
Not open for further replies.

tphuang

Lieutenant General
Staff member
Super Moderator
VIP Professional
Registered Member
I can't. It's obviously not displayed as visible as su-27. I just figure it's there from the articles that JF-17 has IRST (Remember the article that I translated recently on JF-17, it said that JF-17 has FLIR and its MFDs can display the ground/target imagery + a JDW article)
and also this picture.
Please, Log in or Register to view URLs content!

I mean the one in the picture is clearly a J-10, but you can't really tell that it has an IRST from just looking at the fighter. Unfortunately, ChangHong doesn't really say where it is actually installed.
Please, Log in or Register to view URLs content!

Also, this big picture shows that J-10, J-8II and JH-7 all can use it. Anyway, I'm still a little confused over this entire thing.
 

Sea Dog

Junior Member
VIP Professional
Perhaps they're able to mount an IRST externally rather than it being included as an internal piece of equipment. Maybe it's not something that is part of the design, but rather as something that can be attached per mission needs necessitate. :confused: Just a guess.
 

crobato

Colonel
VIP Professional
cabbageman said:
Unless you think all PLAAF pilots must be great, there is nothing to argue.

PLA still have regiment changes and merges. In 2004, 31st Division was merged into the 12th Division.

Which is irrelevant to the discussion.

You're foolish to think that PLAAF pilots are random and varied in their skills. They do have a high selective process because they always have far more people wanting to join them than the seats they could supply. By the time you are able to be assigned even to a J-7E regiment, that is still quite an honor and a privelege.

Who told you these former J-7 regiments have third grade pilots? Who told you no pilot or regiment changes in these divisions?

And who told you there were? There were no merges recorded with any of the J-7 regiments that converted to the J-10 and J-11.

Military products have stronger survivability, repairability, availability, reliability and security requirements.

But they don't have superior bandwidth. Military electronics are generations behind commercial products thanks to Moore's Law. By the time a military spec'ed product manages to pass all the tests, the commercial cycles have gone two or three generations, even more. And don't think commercial systems are not 'mission critical'---far from it. A lot of the innovations for redudancy and system toughening just happen to be developed first in the commercial sector. 'Mission critical' is a phrase IBM uses to market all its products by the way. Commercial (large scale corporate) applications is every bit as demanding of survivability, repairability, availability, reliability and security as military applications.

Longer reach means greater flexibility. When technology matures, people always choose the longer range weapons first. Your doubt is equivalent of saying no rifle could be used at a distance when your friend is in a close knife fight, therefore rifle is overrated and knife is better. It’s a correct description, but ultimately the wrong question to ask.

What you are describing here is a rifle vs. a machine gun. Rifle has its advantages, but big disadvantages when the fighting comes close. Unfortunately the J-8II isn't very survivable once you get fired upon. Between a J-7 and a J-8II, the J-8II is more detectable and less likely to be able to evade a missile. Considering that China's BVR capabilities remain highly unproven and not well documented, there is no guarantee a J-8II is going to succeed with a lot of its BVR attacks.

The difference of flight qualities between a J-8II and a J-7E/G isn't pretty. The J-7E/G has superior low speed flight characteristics, excellent flight behavior at high alpha, and even less loss of drag and lift at increased alpha approaching transonic speeds. The J-8II's classic delta wing suffers all the disadvantages of the design despite a low wing loading. It lacks variable camber and front slats unlike the J-7E/G. It quickly bleeds speed and lift when you start increasing alpha on it, so it really isn't a very pointable craft. The wing design is prone to bleeding air flow running down the edge, unlike a double delta, and the result is tip stalling. The plane therefore can suddenly stall or lose control when it turns. They partly corrected this problem by adding a second wing fence.

Despite the PLA's ability to propagandize, I hardly ever see any instance the PLAAF or any pilot interview or article that talks glowingly of the J-8II's flight qualities, while heaps abound for the J-7E. And therei s no doubt how flight qualities will eventually cement pilot flight styles and habits. If your plane is crap, you will develop habits trying compensate for its failings. If your plane gives you the utmost confidence in the way it flies, it will reflect on the pilot's own attitudes and flight skills. You can clearly see which of the two are more popular with the PLAAF. I do think that Shenyang AC somehow has more clout with the government to give reason for their assembly lines running but Chengdu AC has by far the better engineers.

The J-8II's advantages in range and payload does make it a superior multirole fighter compared to the J-7, something to consider if both planes are recruited to do A2G missions.
 
Last edited:

cabbageman

New Member
There is nothing random about different levels of skills. Trainings take money and resources, and modernization requires time and organizational changes. Different divisions have different tasks, Wulumuqi AFB wouldn't have same objectives as Quzhou AFB. Concept of "Rapid Reaction Units" says it all. Almost all air forces have highly selective process for pilot recruitment, that doesn't mean trainings results are always universally great.

Already used Yang Liwei for pilot reassignment example. For division merge, see 6th Division.

crobato said:
But they don't have superior bandwidth. Military electronics are generations behind commercial products thanks to Moore's Law. By the time a military spec'ed product manages to pass all the tests, the commercial cycles have gone two or three generations, even more. And don't think commercial systems are not 'mission critical'---far from it. A lot of the innovations for redudancy and system toughening just happen to be developed first in the commercial sector. 'Mission critical' is a phrase IBM uses to market all its products by the way. Commercial (large scale corporate) applications is every bit as demanding of survivability, repairability, availability, reliability and security as military applications.
If you get a blue screen of death on your PC, that means re-boot. The consequence is not so trivial when your fighter flight control or mission computer breakdown during air to air combats. Certainly the commercial real-time systems and selective industries such as critical medical systems and flight traffic towers have very strict requirements. But even those rare commercial systems aren't the same as military ones.

Commercial jets do not need situation awareness of E-3. Corporate Network doesn't have to worry about competitors using electronic warfare to jam its systems. No commercial datalink needs to worry about volume, power, and coolant requirement of F-16. Commercial systems are driven by ROI, military systems are driven by reliable combat power.

Military datalink are not cheap in general. If you want to put them on J-7s, then you have to spend the money on it.

crobato said:
The difference of flight qualities between a J-8II and a J-7E/G isn't pretty.
J-8F is not that bad. Other than better avionics and missiles, J-8F also has a better engine and structural changes. J-7 is ideal for obstructing the enemy and single aircraft engagement. But for contesting air superiority in China airspace and conducting interception with multiple aircrafts on all sides, I still pick J-8F over J-7G. Even if PLA's BVR missiles are unproven, they still complicate enemy air situation, decrease enemy attack envelope, and reduce enemy BVR kills by disrupting enemy tracking.

The real problem with PLAAF's BVR engagement effectiveness isn't BVR technology maturity, but tactics development. Even the Flanker pilots are still learning, I do not think J-8 pilots are that proficient.
 

Roger604

Senior Member
It is well reported that Chinese advances in information warfare were made possible by a burgeoning information technology industry. China is now on the very cutting edge of commercial IT.

[The Chinese IT industry didn't materialize out of thin air. Ethic Chinese engineers (along with Indians) constitute the majority of Silicon Valley engineers. They just went to China and set up shop to get rich.]
 

tphuang

Lieutenant General
Staff member
Super Moderator
VIP Professional
Registered Member
cabbageman said:
If you get a blue screen of death on your PC, that means re-boot. The consequence is not so trivial when your fighter flight control or mission computer breakdown during air to air combats. Certainly the commercial real-time systems and selective industries such as critical medical systems and flight traffic towers have very strict requirements. But even those rare commercial systems aren't the same as military ones.
Alright, I have to get into this now. Do you have any idea of the kind of redundancy put into commercial systems. Do you have any idea of the disastrous consequences of system downtimes in certain commercial enterprises. Seriously, what industry are you in? If you are not working in the Software industry, I suggest that you stop arguing on this.
Commercial jets do not need situation awareness of E-3. Corporate Network doesn't have to worry about competitors using electronic warfare to jam its systems. No commercial datalink needs to worry about volume, power, and coolant requirement of F-16. Commercial systems are driven by ROI, military systems are driven by reliable combat power.
Every datalink is driven by its own set of requirements. Just because the requirement are different, that doesn't mean one is more strict than the other. You really have to ask the programmer themselves to find out which one is more strict.
Military datalink are not cheap in general. If you want to put them on J-7s, then you have to spend the money on it.
B.s: this is another thing you don't seem to understand. datalink and FBW software generally is overpriced for the American planes. The companies that develop software for F-16s and F-22s charge astronomical amount for those software. I know, because a friend of my worked in this company that developed the OS for one control system in F-16. All he said was that there is no way the software itself is worth that much money. Defense contractors for American military hardware can jack up prices like there is no tomorrow.

Then you shift it to the Chinese side, everything gets cheaper. Think about it this way, JF-17 has all the avionics built in and it still cost less than $10 million per jet.

Before we continue, just answer one question. What language do you think most systems in pla are written in? If you can answer this question, then you are at least qualified for this argument.
 

cabbageman

New Member
Do you think all companies have great IT systems like Procter & Gamble or WalMart? The notion of reliability extends beyond the simple "down time”. In commercial world, if you fail you could file for bankruptcy and restart by restructuring. There are plenty of corporation with horrible IT Department and projects. "Certain commercial enterprises" and "commercial real-time systems and selective industries" are the same.

Some military systems use older technology. Part of the reason is that military are sometimes inefficient, but more importantly military tends to use very mature systems because they usually cannot afford to take the same risks as some of the major corporations.

If you think software is the only thing that matters in military equipments, I suggest that you stop arguing on this.

tphuang said:
Every datalink is driven by its own set of requirements. Just because the requirement are different, that doesn't mean one is more strict than the other. You really have to ask the programmer themselves to find out which one is more strict.
Not programmers, but system engineers. Different requirements don’t mean one is more strict than the other, but I already list some of the situations. What's the difference between home PC and IS that handles nuclear missile warning system? The consequence. In military, the majority of systems have life threatening consequences. By comparison commercial systems do not have as many.

tphuang said:
B.s: this is another thing you don't seem to understand. datalink and FBW software generally is overpriced for the American planes.
We are not comparing absolute costs for US and China. It is the resource allocation within each military. FC-1 and SU-27 are cheaper than F-16 and F-15, that doesn't change resource allocation problem for lightweight and heavyweight fighter.

If you believe only US datalink are expensive look at other nations. Link 16 is a NATO standard.

Credential is a legitimate concern. But the programming language is the worst question to ask. It has nothing to do with high level decision making. That is the typical wrong attitude from the technical community. If a CEO ask you about IT strategic planning and resource allocation, and you start talking about using Java or C, guess how far your career will go.
 
Last edited:

MIGleader

Banned Idiot
Sea Dog said:
Perhaps they're able to mount an IRST externally rather than it being included as an internal piece of equipment. Maybe it's not something that is part of the design, but rather as something that can be attached per mission needs necessitate. :confused: Just a guess.

I was thinking that too, but why? An IRST is helpful in Air combat all the time, and if you dont need it, dont use it.

My hypothesis: J-10 completed airframe development before the IRST was considered. when the IRST finished development, it was too late and too hard to make internal changes to the j-10. so they made a hack to mount it externally.
 

tphuang

Lieutenant General
Staff member
Super Moderator
VIP Professional
Registered Member
cabbageman said:
Do you think all companies have great IT systems like Procter & Gamble or WalMart? The notion of reliability extends beyond the simple "down time”. In commercial world, if you fail you could file for bankruptcy and restart by restructuring. There are plenty of corporation with horrible IT Department and projects. "Certain commercial enterprises" and "commercial real-time systems and selective industries" are the same.
again, please show your credentials. The matter of system uptime is the most important part of reliability. There are a lot of other factors, but if your system can't start up or your IT people can't provide support in time, then you are in a whole host of trouble. It's not a matter of bankruptcy, there is also lawsuits and such. Do you think bankruptcy is the only thing awaiting a company like Research In Motion if it's network goes down for like a week? My last job was with a company of around 60 people. Even there, we had backup servers and databases running. If the primary server/db fail, the secondary takes up the load and so forth. If our redundancy measures fail, most of the major ISPs in North America would not be able to offer internet service. This kind of stuff faces every software company with any kind of bright future. IT companies need to prepare for the most unlikely types of disasters. That includes having the electric power going down, getting hit by a earthquake, having your datacenter flooded and a bunch of other extremely unlikely scenarios. We set up hot/cold site and remote data centers that are in different locations, so even if the main company building gets blown up, the operation can still keep on going. Now, do you know how seriously this kind of stuff is taken? Any decent CS program in North America would spend more time teaching you on the principles behind reliability through different methods than coding itself.

Oh yeah, every corporations have the occassional bad IT projects. Nothing different from the military.
Some military systems use older technology. Part of the reason is that military are sometimes inefficient, but more importantly military tends to use very mature systems because they usually cannot afford to take the same risks as some of the major corporations.
Right, all major corporations (most notably banks) have legacy issues. Once you get up in the millions of lines of code, nobody is going to replace those systems as long as they work. Again, there are plenty of theories developed on dealing with legacy systems, I don't think I need to get into it.
If you think software is the only thing that matters in military equipments, I suggest that you stop arguing on this.

Not programmers, but system engineers. Different requirements don’t mean one is more strict than the other, but I already list some of the situations. What's the difference between home PC and IS that handles nuclear missile warning system? The consequence. In military, the majority of systems have life threatening consequences. By comparison commercial systems do not have as many.
Software is not the only thing that matters, but it's a huge part of it.

It's interesting that you used IS that handles nuclear missile warning system, because the most famous software breakdown involves PAC-2 in Operation Desert Storm. And yes, that breakdown caused the most American casualties in ODS. There are similar software breakdown cases in the medicine industry, where the software controlling the machines were causing deaths.

Meaning? reliability is something that all systems have to deal with. It doesn't matter whether you are military or commercial. It doesn't matter whether the system has life threatening consequences, the developers will still make sure that it has enough reliability. The standards set by hospitals, banks and other organizations are not any less strict than that of the military.
We are not comparing absolute costs for US and China. It is the resource allocation within each military. FC-1 and SU-27 are cheaper than F-16 and F-15, that doesn't change resource allocation problem for lightweight and heavyweight fighter.

If you believe only US datalink are expensive look at other nations. Link 16 is a NATO standard.

Credential is a legitimate concern. But the programming language is the worst question to ask. It has nothing to do with high level decision making. That is the typical wrong attitude from the technical community. If a CEO ask you about IT strategic planning and resource allocation, and you start talking about using Java or C, guess how far your career will go.
My career is doing fine. I asked that question with the intention of seeing how much you really know about IT in Chinese military.

Again, you can assess Chinese datalink HW/SW the same as western HW/SW. Do you any idea how much cheaper the computers are in China as compared to the Western world? Do you realize that China doesn't care about this thing called IPR? After the initial development cost, if you only need to pay minimal cost for each copy of the software handling the datalink, the cost of the datalink goes down big time. Everything can be done cheaper in China.

As for the cost, you just need to look at JF-17 to comprehend how expensive datalink and FBW system cost for Chinese planes:
1. flyaway cost of less than 10 million (plaaf is paying $10 million per JF-17)
2. includes around 3 million for RD-93
3. includes airframe
4. includes the modern avionics shown in the JF-17 thread

How expensive do you think datalink can cost for Chinese planes? Let's see, if we assess the airframe + FBW system to be 3 million and the radar to be 1.5 million, the other avionics to 1.5 million, the datalink would still cost no more than a million.
 

crobato

Colonel
VIP Professional
cabbageman said:
There is nothing random about different levels of skills. Trainings take money and resources, and modernization requires time and organizational changes. Different divisions have different tasks, Wulumuqi AFB wouldn't have same objectives as Quzhou AFB. Concept of "Rapid Reaction Units" says it all. Almost all air forces have highly selective process for pilot recruitment, that doesn't mean trainings results are always universally great.

Already used Yang Liwei for pilot reassignment example. For division merge, see 6th Division.

Your example has not proven any merger at all with all known J-7 regiments that converted to the J-10 or J-11.

Mergers also do not prove that the cream of the crop pilots are being selected for J-10 or J-11 either.



If you get a blue screen of death on your PC, that means re-boot. The consequence is not so trivial when your fighter flight control or mission computer breakdown during air to air combats. Certainly the commercial real-time systems and selective industries such as critical medical systems and flight traffic towers have very strict requirements. But even those rare commercial systems aren't the same as military ones.

You really don't know how mission critical a bank's system is, do you? Or the telephone system of a city. Or the systems of a jet liner.

Commercial jets do not need situation awareness of E-3. Corporate Network doesn't have to worry about competitors using electronic warfare to jam its systems. No commercial datalink needs to worry about volume, power, and coolant requirement of F-16. Commercial systems are driven by ROI, military systems are driven by reliable combat power.

Commercial systems are driven by the fact that catastrophic failure can have extremely wide ranging consequences. Another thing is that military systems do not have the same volume of transactions or the same level of bandwidth that large scale mission critical commercial systems does.

The fact that military systems are radiation hardened don't mean jack shit when it comes to technology. It is not difficult to radiation or EMF harden electronics---the main principles of these are very well known since the fifties.

Military datalink are not cheap in general. If you want to put them on J-7s, then you have to spend the money on it.

And I don't believe that it is hard or as expensive as you think. The US defense industry is like Hollywood or many US corporations; a lot of money isn't spent on the actual item itself, but on bloat, corporate salaries, lawyers and lobbyists.

J-8F is not that bad. Other than better avionics and missiles, J-8F also has a better engine and structural changes. J-7 is ideal for obstructing the enemy and single aircraft engagement. But for contesting air superiority in China airspace and conducting interception with multiple aircrafts on all sides, I still pick J-8F over J-7G. Even if PLA's BVR missiles are unproven, they still complicate enemy air situation, decrease enemy attack envelope, and reduce enemy BVR kills by disrupting enemy tracking.

Which is true in a way. But generally BVR is overrated. I remember in AFM, someone pulled a list of "BVR" kills by using the number of AIM-7 and AIM-120 misisle kills in the last 20 years or so. I forgot to ask them just how many are actually done in truly medium to maximum ranges.

The structural changes on the J-8F dont' mean anything. The plane lacks the much more modern wing design of the J-7G which I already mentioned the advantages above. The J-8F still lacks basic niceties like variable camber which every jet in the last 30 years have.

The J-8II has the advantages of range, payload, and a structural airframe that makes it more suited for multirole such as air to ground attacks.


The real problem with PLAAF's BVR engagement effectiveness isn't BVR technology maturity, but tactics development. Even the Flanker pilots are still learning, I do not think J-8 pilots are that proficient.

Everyone had problems with BVR tactics, because mainly BVR isn't that proven outside of scripted exercises and totally unequal situations. Let us ask ourselves how effective a 'wall' of fighters coming into enemy air territory with their radars lighted hunting for targets. Their very presence would already have alerted the enemy, which would actually detect them first before they could on their intended targets. The enemy could approach them in radar silence, flying low for terrain masking, directed by ground countrol or AWACs, and mount passive IR attacks.

One of the problems of BVR is that technology is also working hard to degrade it as much as technology is trying to improve it. ECM, countermeasures, RCS reduction measures.

But the worst thing about BVR is that it sacrifices the element of surprise. The best anti BVR tactic is once you are detected, is to turn tail and away from the shooter. The key to beating BVR is to extend the flight time and distance of the missile. By moving away, this would force missiles to expend the fuel.

Some of the so called BVR tactics aren't as BVR as one would think. Guided by AWACS, a fighter would come within missile NEZ of the target without his radars on, suddenly light his radars up, try to get a fast lock and shoot the missile. There isn't much difference in doing that with an IR missile.

In my opinion, let's assume China tangles a regional power (not the US), the J-7s would probably get more kills than the J-8II, and the J-8II would also resort to passive attacks. I think for outdated planes, the J-7G is more cost effective than the J-8F. But because of "conventional wisdom" about BVR, along with the range, payload and radar advantages, the J-8II will last longer in PLAAF service than the J-7.
 
Status
Not open for further replies.
Top