 |
| A side-by-side visual comparison of India’s Tejas, Pakistan’s JF-17 Thunder, and China’s J-10 fighter jets. The infographic highlights aircraft in service numbers and development timelines to illustrate how production speed influences air power balance in South Asia and East Asia. |
The loudest argument in South Asian airpower right now is not “whose jet turns tighter”. It is “whose factories and supply chains can keep squadrons alive”. The recent run of Tejas headlines—crashes in 2024 and 2025, followed by a February 2026 runway-overshoot and a reported precautionary fleet pause—lands on an already sore point: India needs combat aircraft at scale, fast, because Indian Air Force is operating far below a long-stated squadron requirement.
Against that, Pakistan has built its force structure around steady JF-17 production and has added J-10C fighters in meaningful numbers, while China has already done what “Make it here” dreams of: moved from dependence on foreign aircraft engines toward operational domestic powerplants, and produced fighter fleets at volumes India has not matched for its light-fighter programme.
This report uses (and cross-checks) official contract announcements and capacity claims from Press Information Bureau and Ministry of Defence, audit findings from Comptroller and Auditor General of India, fleet counts from FlightGlobal based on Cirium datasets, transfer-dependence statistics from Stockholm International Peace Research Institute, export/inventory context from the United States Department of Defense, and engine-supply reporting from Janes.
A key conclusion emerges: capability matters, but tempo is what converts capability into deterrence. A jet programme that cannot reliably deliver 15–25 aircraft a year (and keep them serviceable) becomes a strategic vulnerability—especially for an air force trying to climb from 29 fighter squadrons back toward 42.
Timelines and fleet scale
Comparative milestones and outputs
The table below is structured for investigative writing: it emphasises not just “when it flew”, but “when it started to matter” (induction + numbers in units + exports).
Milestone timeline chart
The timeline below is deliberately “production-centric”: it foregrounds induction, supply, and losses alongside first flights.
Key dates are drawn from government and audit records for Tejas, credible defence analysis for J‑10 milestones, and multiple reporting streams for JF‑17 production/induction.
Production tempo and industrial models
The tempo problem in numbers
There is a trap in many fighter-jet debates: counting “orders” instead of “aircraft in squadrons”. Orders are promises; open squadrons are power. Using the same independent fleet dataset for in-service counts, we can estimate how quickly each system translated into squadron mass after induction:
These are not “factory throughput” measures; they are force-structure outcomes that include basing, training pipelines, acceptance, and (sometimes) attrition. Still, even as rough indicators, they show the central thesis: production systems that consistently output high single digits to low double digits annually will reshape regional fleets; those that output 3–4 a year will not.
Industrial model differences that drive tempo
India’s Tejas is manufactured by Hindustan Aeronautics Limited, a state-run defence manufacturer. Government statements describe a deliberate ramp plan—8 aircraft per year, then 16, then 24—plus wider vendor participation, and higher indigenous content in the 2025 contract. Yet the same programme’s history in audit shows repeated schedule slippage and mismatches between planned and realised production capability (for example, plans for building facilities for eight aircraft per year but only four being created at that point in the programme).
China’s model is not “private-sector competition”; it is state-led scale with a maturing domestic industrial base. One clean indicator is from SIPRI: China’s arms imports have fallen as it builds its ability to design and produce major systems, and it increasingly supplies others (with Pakistan as a major recipient of Chinese exports). For the J‑10 line specifically, credible defence analysis frames series production beginning after flight testing completion and a rapid (relative) transition to service readiness by 2004.
Pakistan’s model is hybrid: co-development and local assembly/production around a Chinese spine. The JF‑17 story, even in sympathetic write-ups, reads like a production-first programme (deliver aircraft, then upgrade through blocks), with early deliveries from China, an eventual start of series production at home, and a long-run goal of replacing multiple legacy fleets. But there is also a ceiling: recent reporting describes capacity constraints—“fewer than 20 per year”—and uncertainty about whether the line can expand quickly enough to meet new export interest.
Squadron impact and force structure
India’s fighter shortfall is no longer a quiet, technical concern—it is now described in mainstream reporting as a strategic risk. By early 2026, reporting tied to Indian defence approvals described the air force as down to 29 fighter squadrons, far short of a long-stated requirement of 42.
That gap matters because it changes how deterrence is perceived. A force sitting at 29 squadrons has less surge capacity for simultaneous contingencies (for India, read: western and northern theatres) and less resilience to maintenance cycles, accidents, and retirements. It is also why an Indian defence committee explicitly pushed for broader private-sector involvement, and why the air force leadership has been quoted arguing India needs 35–40 new fighters annually to rebuild strength—numbers that are an order of magnitude higher than Tejas’ realised historical induction rate and still above HAL’s near-term capacity claims.
This is where Tejas vs JF‑17 vs J‑10 stops being a fan-war and becomes procurement math. If Tejas output stabilises at 16–24 aircraft per year as planned, it becomes a genuine force-structure repair tool. If it does not—because engines arrive late, subassemblies bottleneck, trials slip, or acceptance slows—India will keep living in a stopgap ecosystem (life extensions, imports, and mixed fleets).
Capability and supply-chain dependencies
Capability snapshots that matter for “production-speed airpower”
A rigorous capability comparison could run 10,000 words; for this feature’s thesis, the most relevant capability question is simpler: can the platform be produced and sustained with predictable inputs? The table below focuses on the parts of capability that most strongly intersect with supply chains (engines, radars, and weapons integration).
Supply-chain dependency as a strategic constraint
For Tejas, supply-chain dependency is not theoretical: it has been publicly tied to U.S.-origin engine delivery schedules. Reporting tracked how a supplier disruption (including a South Korean supplier issue) slowed F404 deliveries, with revised delivery rhythms (for example, “two engines a month”) effectively becoming a gating factor on aircraft deliveries. Government messaging tries to close that loop through negotiated technology transfer and rising indigenous content claims.
Pakistan’s dependency pattern is different. SIPRI’s data shows Pakistan’s arms imports becoming even more China-dominant over time—82% of Pakistan’s arms imports came from China in 2019–23—which is less a vulnerability if Beijing is your strategic partner, and more a structural choice that prioritises assured supply over supplier diversity. The JF‑17 itself sits inside this logic: a Chinese avionics and weapons ecosystem with a Russian engine dependency that Pakistan has historically managed through the China channel.
China’s J‑10 story is the “endgame” of this arc: start with a foreign engine, then transition to domestic engines on an operational platform, reducing exposure as industrial maturity rises.
Safety record and transparency
What is clearly documented
Two Tejas crashes are clearly documented in high-reliability reporting: a March 2024 crash in Rajasthan with pilot ejection, and a November 2025 crash during a Dubai Airshow demonstration flight that killed the pilot. In February 2026, reporting described a runway overshoot/ground incident followed by precautionary fleet checks; the manufacturer disputed “crash” framing and described a minor ground technical incident.
What cannot be cleanly computed (and why)
The user request asks for “incidents vs platform flight hours”. Here is the uncomfortable truth: public sources do not provide a stable, official, up-to-date Tejas fleet flying-hours total in the same way some Western programmes do. Without a verified numerator (total hours), accident-rate arithmetic becomes guesswork—especially when “fleet grounded” reporting mixes airborne crashes with ground incidents and with “written off” vs “repaired” ambiguity.
For JF‑17, at least one widely cited figure exists: reporting in 2016 claimed the fleet had logged “more than 19,000 operational flight hours” (at that time) and connected that claim to an aviation journalist who tracks PAF. But that number is both old and not an official running total; it is useful context, not a definitive denominator.
The investigative way to handle this in a feature is to be explicit: the trend is observable (Tejas’ safety narrative is under pressure), but precise per-hour comparisons are not currently defensible from open official data. That transparency is part of the “hard-hitting” tone: if governments want credibility, they publish the maintenance and flying-hour baselines that let citizens judge risk honestly.
One: The Tejas did not just overshoot a runway; it overshot India’s production reality. Thirty jets grounded is not an engineering headline—it is a force-structure headline, because India is sitting at 29 squadrons when it says it needs 42.
Two: South Asia keeps arguing about “4.5 generation”. Meanwhile, China is quietly winning the only category that pays dividends in war: how many aircraft you can field, fix, and replace every year.
Three: The Tejas is not “bad”. The problem is crueller: India built a jet; Pakistan built a production rhythm; China built an industrial system. Those are three different achievements, and only one of them scales deterrence.
In February, the Tejas story stopped being about a single aircraft and became about an entire air force. Reports said a Tejas overshot the runway and the fleet went into precautionary checks; the manufacturer pushed back, calling it a minor ground incident. Either way, the message was the same: when you only have around a few dozen jets of a type in frontline use, any pause is loud. It is loud because the Indian Air Force is down to 29 fighter squadrons—far below the 42 it says it needs. That is not a gap you patch with speeches. You patch it with deliveries.
This is the part most debates dodge: airpower is not a beauty contest between platforms; it is an industrial contest between calendars. Tejas exists—it is inducted, it is flying, it has two operational squadrons, and it is positioned as a centrepiece of India’s modernisation story. The government has also sold the public a ramp plan: HAL at 8 aircraft a year, then 16, then 24. Two major contracts—83 aircraft in 2021 and 97 more signed in 2025—are meant to turn Tejas into a fleet, not a symbol.
But production is where symbolism dies. The Tejas programme’s own audited history reads like a warning label: milestones that slipped by years, planned production facilities that did not match intended throughput, and cascading delays from early design and systems integration decisions. That audit is old (2015), but its logic is timeless: complex weapons programmes fail when governance, integration discipline, and user involvement are weak. And when you combine that with an external engine supply chain, it gets sharper. Recent reporting has tied Tejas Mk1A delays directly to F404 engine delivery schedules—down to the cadence of engines arriving per month.
Now look across the border and the contrast is not subtle. Pakistan’s JF‑17 is not marketed as mystical; it is marketed as available. Its origin story is blunt: a China-backed programme offered in the mid‑1990s, prototypes flying by 2003, early production arriving by 2007, and series production beginning by 2009. By 2025 fleet datasets list more than a hundred JF‑17 fighters in service plus a meaningful trainer fleet. Pakistan is also signing export deals, including a contract with Azerbaijan, and discussing possible sales with Bangladesh. This is not proof that JF‑17 is “better”; it is proof that a repeatable production pipeline can be built in the region—and that pipeline itself becomes a strategic asset.
China’s J‑10 takes the argument further: it is what scale looks like when a state decides a fighter is going to become the backbone of a force, not a boutique programme. Analysts describe the J‑10 moving into series production by the end of 2003 and being ready for service in 2004, then evolving through radar and weapons upgrades into the J‑10C era of AESA and long-range missiles. Fleet data lists hundreds in Chinese service. And while China began with foreign engines—prototype J‑10s flew with Russian AL‑31FN—later reporting highlighted operational J‑10Cs with domestically made engines. That arc matters: it is the difference between a programme whose output is hostage to foreign bottlenecks and one whose output can be planned politically and executed industrially.
The supply-chain picture exposes why Pakistan’s “success” is not simply a story of genius; it is a story of alignment. SIPRI reports that 82% of Pakistan’s arms imports came from China in 2019–23. That is dependency, yes—but it is dependency aligned to a strategic patron that also supplies aircraft, missiles, radars, and the broader technology spine. Pakistan’s J‑10C story reflects that: the U.S. DoD assessed 20 J‑10Cs delivered to Pakistan as of May 2025, with total orders since 2020 of 36, and it described Pakistan as the only export customer. When supply, finance, and geopolitics pull in the same direction, production moves.
Tejas still has a path to being a real “numbers fighter”, but it requires an uncomfortable shift in what India treats as victory. Winning is not signing a contract; it is delivering aircraft into squadrons at the tempo the air force chief says is required—35 to 40 fighters a year across programmes. Winning is cutting engine and subsystem uncertainty, so acceptance schedules stop being a hostage to someone else’s factory. Winning is publishing credible fleet flying-hour baselines so safety debates are about verified rates, not viral jokes and “flying coffin” memes. And winning, ultimately, is admitting the real contest: not Tejas versus JF‑17 versus J‑10 in the sky—but HAL versus time.
