If you are trying to decide whether local Rafale production would make Bharat strategically autonomous, do not begin with the number of aircraft assembled here. Begin with a harder question: what could Bharat still operate, repair, modify, and produce if French support were delayed or withheld?
That test separates industrial participation from sovereign capability. A factory in Hyderabad can create valuable skills and supply-chain depth. But if a mission-critical component, software change, or engineering decision remains under foreign control, the dependency has moved rather than disappeared.
A factory is valuable, but it is not design authority
Technology transfer is often discussed as if it were a package that a supplier either hands over or retains. In practice, it is a ladder of distinct capabilities. Bharat must know which rung each contractual commitment reaches.
- Assembly: Indian workers join imported or locally produced parts according to an approved process.
- Component manufacture: Indian facilities make specified parts using transferred tooling, process instructions, quality controls, and materials.
- Sustainment: Indian personnel can inspect, diagnose, repair, overhaul, and replace equipment without routinely returning it to the foreign supplier.
- Modification and integration: Bharat can incorporate approved weapons, sensors, software changes, and mission requirements without depending on discretionary foreign permission for every change.
- Design authority: Indian institutions possess the engineering data, tools, test capability, trained personnel, and legal rights needed to understand and alter the system itself.
Each rung has value, but they are not interchangeable. An assembly line can create employment, production discipline, supplier experience, and familiarity with a complex aircraft. It does not automatically confer the ability to redesign an engine part, rebuild mission software, or certify a modified combat configuration.
Source-code access requires the same precision. Receiving a copy of code is not the same as receiving the right and practical ability to change it. A usable transfer may also require the build environment, interface information, configuration history, test procedures, documentation, trained engineers, and authority to deploy the resulting software. Conversely, source code alone is not the only possible way to reduce dependence. Clearly defined interfaces, domestic integration rights, controlled access arrangements, and binding response obligations can matter as well. The contract must identify the actual capability, not rely on the phrase “technology transfer.”
Read the proposed Rafale package one dependency at a time
The proposed 114-aircraft arrangement remains under negotiation. The publicly described industrial plan would give Bharat meaningful manufacturing work, but it would also preserve important French controls. Tata Advanced Systems is expected to build most of the fuselage in Hyderabad, while Safran is expected to establish an M88 engine assembly line in Bharat.
| Capability area | Publicly described position | What Bharat still needs to establish |
|---|---|---|
| Airframe production | Most of the Rafale fuselage would be built by Tata Advanced Systems in Hyderabad. | Which engineering data, repair rights, process controls, and change authorities accompany that work. |
| M88 engine | An engine assembly line would be established in Bharat, but the most critical M88 parts would continue to be made only in France. | Which imported parts can ground an aircraft, how they will be stocked and replenished, and whether Bharat can repair or eventually manufacture them. |
| Combat system | No published commitment gives Bharat the Rafale source code or an independent right to modify the combat system. | The exact rights to integrate Indian requirements, test changes, manage configurations, and deploy upgrades. |
| Future AMCA engine | A full technology transfer for an engine intended for Bharat’s AMCA has reportedly been offered. | What “full” means in enforceable deliverables, intellectual-property permissions, design work, testing responsibility, and control of critical manufacturing processes. |
Do not collapse these rows into one localization percentage. A fuselage made in Hyderabad can deepen Bharat’s aerospace base while leaving engine availability dependent on French production. An M88 assembled in Bharat can improve manufacturing competence while leaving the most consequential component knowledge abroad. Both gains are real, and both limits are real.
The negotiations are not finished, and unpublished contractual terms could alter the picture. That uncertainty should prevent an absolute verdict, but it should not justify an inflated claim. The evidence presently supports a narrower description: substantial local manufacturing is proposed, while independent design and modification authority has not been demonstrated.
Apply five sovereignty tests before accepting the label
Strategic autonomy does not mean that every nut, circuit, and material must originate in Bharat. Modern aircraft depend on international supply networks. Autonomy means that another state should not hold a practical veto over decisions essential to Bharat’s defence. You can assess a Rafale agreement by applying five tests.
- The disruption test: Can Bharat keep the fleet operational if deliveries from France are interrupted? The answer requires an itemized map of imported mission-critical parts, their replacement pathways, domestic repair coverage, inventory policy, and replenishment obligations. Counting locally made parts is less useful than identifying the few imported items whose absence can stop operations.
- The repair test: Can Indian facilities diagnose and correct serious failures? A credible package should specify depot-level work, test benches, diagnostic tools, calibration capability, repair data, approved materials, inspection standards, and the authority to return repaired equipment to service. “Maintenance in India” is too vague unless the permitted depth of maintenance is defined.
- The modification test: Can Bharat respond to a new operational requirement without waiting indefinitely for the original supplier? Examine access to controlled interfaces, software tools, configuration data, integration laboratories, flight-test information, certification procedures, and approvals. The relevant question is not merely whether Bharat receives source code; it is whether Indian teams can make, validate, and field the changes the Indian Air Force needs.
- The learning test: Are Indian engineers performing work that builds reusable capability, or only following a fixed production sequence? A useful transfer assigns Indian teams responsibility for design analysis, problem-solving, testing, failure investigation, manufacturing-process development, and certification. Training should be tied to work that Indian institutions will later perform independently.
- The decision-rights test: Who can approve, delay, price, or refuse a repair, integration, software release, or component substitution? The agreement should state the procedure, evidence required, responsibility for testing, costs, response obligations, and conditions under which approval may be withheld. If these decisions remain discretionary, the dependency remains political as well as technical.
These tests also expose a common negotiating mistake: treating jobs or production value as a substitute for control over critical nodes. A large amount of low-risk manufacturing cannot compensate for foreign control of a small number of parts or permissions that determine whether the aircraft can fly, fight, or evolve.
Run separate scorecards for Rafale readiness and AMCA mastery
Bharat has two legitimate objectives, but they operate on different timelines. The Rafale workstream concerns the readiness and sovereign use of an existing foreign-designed aircraft. The AMCA engine workstream concerns the creation of an indigenous design capability. Mixing the two makes it easy for progress in one to conceal weakness in the other.
The Rafale scorecard should track operational dependence:
- which parts and assemblies are produced in Bharat, weighted by their operational criticality rather than only their price or quantity;
- which inspection, repair, overhaul, and testing tasks Indian facilities can perform;
- which failures still require equipment, data, personnel, or replacement parts from France;
- which weapons, sensors, and software changes Bharat can integrate, and whose approval is required;
- which configuration, certification, and release decisions remain with the foreign suppliers; and
- what binding arrangements protect fleet availability during a supply or political disruption.
The AMCA engine scorecard should track the accumulation of design authority:
- the engineering models, design data, process knowledge, test methods, and failure information delivered to Indian institutions;
- the design and validation tasks actually performed by Indian engineers;
- the right and practical ability to modify, test, certify, manufacture, and support future versions;
- Indian control over suppliers and production processes for critical components;
- the tools, facilities, and trained teams retained after foreign assistance ends; and
- any licence restrictions affecting reuse, future variants, exports, or collaboration with another partner.
A promise of “full transfer” should therefore be converted into a schedule of named data packages, software tools, equipment, training, work assignments, intellectual-property permissions, decision rights, and acceptance tests. Payment and milestone acceptance should follow demonstrable capability. A ceremonial handover or a training course is not evidence that Indian teams can reproduce the work unaided.
The reported AMCA offer should not be used as credit against missing M88 rights unless the commitments are enforceable and connected. An offer concerning a future Indian engine does not by itself remove a present dependency in the Rafale fleet. If the workstreams sit under different agreements, each needs its own milestones, remedies, and accountability.
This does not mean a Rafale agreement is useful only if France transfers every protected technology. A foreign-designed aircraft can meet an urgent operational requirement while Indian programmes develop deeper capabilities. The honest question is whether the price, readiness benefit, retained dependencies, and learning value form an acceptable bargain. A sound procurement need not be mislabelled as complete technological sovereignty.
Key takeaways
- Local assembly and fuselage production are valuable industrial gains, but they do not establish control over the engine or combat system.
- Criticality matters more than localization volume. One unavailable engine component or one withheld software permission can outweigh thousands of locally made items.
- Source code is important only within a larger package of modification rights, tools, documentation, testing capability, trained personnel, and deployment authority.
- Rafale fleet readiness and AMCA engine mastery require separate scorecards; success in one cannot erase dependence in the other.
- Every claim of “full transfer” should be translated into enforceable deliverables and tested capabilities before it is counted as strategic autonomy.
When you next encounter a localization announcement, put four questions beside it: What will be made here? What can be repaired here? What can be changed here? What remains controlled abroad? If the final column contains items that can stop operations or block an essential upgrade, describe the arrangement accurately as industrial participation with retained dependencies.
Bharat should negotiate for the strongest Rafale package available, but measure the result without slogans. The durable objective is a chain of Indian capability that runs from production to diagnosis, from diagnosis to modification, and from modification to original design. That is the point at which technology transfer begins to support strategic autonomy rather than merely resemble it.
References

Leave a Reply
You must be logged in to post a comment.