--end content-->

India Could Build Rafales, but Critical M88 Engine Parts Stay in France

Safran’s offer would bring M88 engine assembly to India while keeping the most critical parts in France, making French spares supply a factor in Indian Air Force readiness.

(DEFENCE SECURITY ASIA) — France would keep manufacturing the most critical M88 engine parts at home under the industrial offer for India’s proposed 114 Rafale fighters, a limit that could leave Indian squadron readiness exposed to French supply even with domestic engine assembly.

The November report on the French production plans puts a specific limit on Make in India under scrutiny, as New Delhi weighs how far local assembly and repair can reduce its dependence on imported components across a much larger Rafale fleet.

Safran chief executive Olivier Andriès said the company would “establish an assembly line in India” but make the M88’s “most critical parts” only in France, potentially leaving Indian engine maintenance dependent on French replacement components.

The signed Tata agreements cover major fuselage sections in Hyderabad, while the proposed M88 assembly line would bring different work to India, leaving the availability of French-made critical parts relevant to both engine production and long-term fleet support.

Dassault Aviation chief executive Éric Trappier called the Tata partnership “a decisive step in strengthening our supply chain in India,” linking the Hyderabad fuselage agreements to a production ramp-up serving international customers as well as India’s fighter requirements.

M88 Engine
M88 Engine

Reported plans envisage around 90 to 96 aircraft built or assembled in India, with initial deliveries from France, although the final split will determine when New Delhi begins receiving aircraft and how much work the local production line sustains.

India’s Defence Acquisition Council, chaired by Defence Minister Rajnath Singh, cleared the Rafale requirement on 12 February 2026, opening a government-to-government procurement process whose terms will determine how much of the production and sustainment burden India can absorb domestically.

The reported US$34 billion to US$39 billion estimate covers aircraft, weapons, training, simulators, support and industrial infrastructure, with that spending likely to shape how quickly the Indian Air Force can convert deliveries into deployable squadrons.

India already operates 36 Rafales and ordered 26 naval Rafale M aircraft in April 2025, so delivery of the proposed 114 fighters would bring its combined inventory to 176 and deepen the two services’ reliance on Rafale support arrangements.

That expansion would come as the service operates an estimated 29 to 30 fighter squadrons against a sanctioned strength of 42, a gap that gives delivery schedules and sustainment capacity immediate weight in South Asian airpower assessments.

The software talks carry an operational consequence because controlled interfaces could give India access to its own weapons on the Rafale while leaving the radar, mission computer and electronic warfare software under French industrial control throughout the fleet’s service life.

The question for New Delhi is how much fleet readiness it can secure through domestic repair capacity and assured access to French parts, while Paris can expand production with India and keep the most sensitive manufacturing work at home.

(READ) Rafale M Makes First INS Vikrant Landing, Advancing India’s Carrier Strike Plans

Why France Is Keeping Critical M88 Parts

Keeping the most critical M88 components in France means an Indian final assembly line would still rely on cross-border supply for parts outside the local manufacturing allocation, with interruptions potentially affecting engine output even when assembly capacity is available.

The proposed assembly line and the Hyderabad maintenance, repair and overhaul facility address different points in the logistics chain, with assembly supporting engine production and the repair shop intended to return worn or damaged modules to service closer to the fleet.

Hyderabad’s planned capacity of more than 600 M88 modules a year describes the volume of components the facility could handle, with any readiness gain depending on the mix of modules requiring repair, their turnaround times and the availability of approved spares.

Local sourcing of selected M88 components would widen the supplier base and move some work nearer to Indian operators, while the engine’s support chain would still depend on Safran’s ability to provide France-made parts for the most sensitive repairs.

Andriès singled out Le Creusot in explaining Safran’s plans to invest in France, anchoring the production decision in French capacity for complex components whose availability could still govern how quickly some M88 modules return from maintenance to operational use.

The precise list of parts reserved for France remains undisclosed, making the treatment of individual hot-section components uncertain and limiting any assessment of how much repair activity Hyderabad could complete when a critical item is unavailable from the French supply chain.

Domestic overhaul could shorten the repair cycle by reducing the need to send eligible modules overseas, but the benefit would vary with the condition of each module and whether local inventories hold the parts required to complete the work.

As the Indian Rafale fleet expands, demand for engine support will grow across deliveries and routine flying, giving the programme an incentive to align repair capacity, spare holdings and access to French-made parts with the pace of aircraft induction.

The separate Safran proposal for India’s Advanced Medium Combat Aircraft envisages a new engine developed with Indian partners and substantially broader technology rights, illustrating how clean-sheet development creates different bargaining terms from localising production of an existing M88 design.

The competing Rolls-Royce offer for the Advanced Medium Combat Aircraft provides another route for New Delhi to pursue engine design rights, while the Rafale talks address the nearer-term requirement to keep a growing fleet supplied with serviceable propulsion modules.

(READ) India’s 26-Jet Rafale-M Deal Opens Weapons Integration, Keeps French Software Limits

Rafale
Rafale

What Hyderabad Will Manufacture for the Rafale

Four production transfer agreements signed on 5 June 2025 cover the forward, central and complete rear fuselage sections plus rear lateral shells, giving Tata Advanced Systems a role in producing the airframe structures on which Dassault’s expansion plans depend.

The Hyderabad facility is expected to begin turning out sections in fiscal 2028 and eventually reach capacity for up to two complete fuselages per month, a planned structural output that must be matched by downstream work to yield finished aircraft.

Running Indian and French production in parallel would give Dassault a second source for major structures, which could ease pressure on the wider Rafale supply chain as orders for India and other international customers compete for manufacturing capacity.

Producing the fuselage in Hyderabad exposes local suppliers and workers to the quality and acceptance requirements for major combat aircraft structures, building industrial capabilities that can carry value across production runs even while Dassault retains control of the aircraft definition.

Tata will work to Dassault’s drawings, so the public agreements place authority over the master technical definition with the French prime, leaving the scope for Indian changes to dimensions, materials or manufacturing processes dependent on permissions beyond the published terms.

That distinction matters during a long service life because a domestic producer can build a structure to an approved specification while decisions about changes affecting aircraft configuration and acceptance remain with the company responsible for the Rafale’s overall design.

Dassault is studying an industrial arrangement extending through final assembly and first flight in India, a step that would bring more production responsibility to Hyderabad if agreed and would require corresponding arrangements for acceptance and delivery of complete aircraft.

Hical’s work on Rafale flight-control system components points to localisation beyond fuselage fabrication, with Indian suppliers gaining production work while responsibility for the qualification and configuration of their components remains embedded in Dassault’s wider programme.

Reported local-content targets range from 40 to 50 percent initially to 55 to 60 percent in later batches, although percentages alone reveal little about which imported systems would still set the pace of final assembly or aircraft repairs.

Supplying fuselages to the wider Rafale programme could give Hyderabad demand beyond the Indian order, while continued French production preserves capacity at home and makes the partnership an instrument of French export policy as well as India’s Make in India programme.

What 114 Rafales Could Add to India’s Airpower

The procurement moved from requirement approval to evaluation of a French offer in 2026, placing the immediate decision on commercial terms, manufacturing arrangements and long-term industrial commitments before any final contract can be cleared by India’s Cabinet Committee on Security.

The Indian Air Force’s squadron deficit gives the proposal urgency following the MiG-21’s retirement, as the service must replenish combat aircraft while sustaining personnel, training and maintenance capacity for the units already responsible for India’s standing air defence commitments.

Early flyaway aircraft from France could start the induction process while Hyderabad builds up production, although the operational value of that first tranche would still depend on the availability of trained crews, ground personnel, weapons and maintenance support at delivery.

The proposed mix of single-seat and twin-seat Rafales also affects the force-generation timetable, since the reported balance of roughly 88 single-seat and 26 twin-seat aircraft would influence how the service assigns aircraft to conversion training and operational units during expansion.

The proposed fleet is expected to centre on the Rafale F4, while discussion of later F5 aircraft or upgrades introduces a configuration question that could affect training continuity, software support and the cost of managing successive standards within the same force.

With 36 Rafales already in service, the Air Force has a foundation for training and maintenance, but absorbing a much larger fleet would require support capacity to expand alongside deliveries if the programme is to improve sustained aircraft availability.

The 26 Rafale M aircraft ordered by the Indian Navy add potential scale to the wider support relationship, with common elements offering scope for coordination while naval and land-based operations continue to impose distinct requirements on each service’s logistics footprint.

Reported inclusion of Meteor, SCALP and MICA alongside prospective Indian weapons makes the package a broader force investment, because the utility of a growing fighter fleet depends in part on the weapons cleared and available when its squadrons enter service.

Defence Secretary Rajesh Kumar Singh’s stated aim of concluding the procurement by March 2027 provides a negotiating timetable, while approval and implementation still depend on agreement over pricing, aircraft configuration, local production volumes and the rights attached to weapons integration.

The regional effect will emerge as squadrons become operational, with aircraft deliveries, trained crews and support availability determining how much additional airpower India can sustain over time and how quickly neighbouring militaries need to account for the change in force posture.

Rafale Source Code and Indian Weapons

Access to Rafale source code is a separate negotiation from industrial localisation because the software controlling the Thales RBE2 AESA radar, Modular Data Processing Unit and SPECTRA electronic warfare suite governs functions that remain central to the aircraft’s operational configuration.

The RBE2 radar supports detection and tracking, the mission computer brings sensor information and weapons functions together, and SPECTRA manages electronic self-protection, making authority over software changes relevant whenever a future upgrade touches several systems at the same time.

At a July 2026 French Senate hearing, Trappier described the Rafale F5 architecture as “archifermée,” or tightly closed, citing the integrity of France’s nuclear mission while leaving room for a more open layer for some functions outside that protected core.

Those comments establish the French manufacturer’s position on F5 architecture, while the contractual scope of India’s access under a predominantly F4 procurement will turn on the negotiated export configuration and on the permissions attached to any interfaces Dassault makes available.

Interface Control Documents could give Indian engineers defined points of access for approved weapons integration while preserving French control of core software, making the scope of those documents more consequential than a general promise to accommodate domestic weapons.

Astra, Rudram and the Smart Anti-Airfield Weapon feature in reported integration discussions, but the terms that matter for fleet planning include which variants are covered, who performs certification and whether approvals extend to future changes after the aircraft enter service.

Manufacturer-assisted integration could get specific Indian weapons onto the fleet while leaving Dassault involved in subsequent upgrades, with broader interface rights potentially shifting more of that work to India as new weapons enter development over the Rafale’s expected service life.

The naval Rafale M agreement provides a precedent through its weapons integration provisions, giving negotiators an existing model to examine while leaving the Air Force programme’s permissions, responsibilities and technical scope subject to its own contract and aircraft configuration.

Potential integration of BrahMos-NG remains less certain, with the missile’s Indo-Russian origins raising questions about the handling of sensitive interface data and adding a third-country dimension to decisions otherwise centred on bilateral technology and industrial cooperation between India and France.

Restrictions on core software can also affect how quickly Indian requirements translate into certified fleet changes, because the authority to approve alterations to combat systems can influence upgrade schedules even where India has secured permission to integrate selected weapons.

What the Deal Signals Beyond India

A signed agreement would give France a larger role in India’s long-term combat aviation support and draw New Delhi more deeply into the Rafale supply chain, tying the relationship to production, spares and upgrades well beyond the initial aircraft deliveries.

For other Rafale operators, the outcome will show how far Dassault and its partners are prepared to extend industrial participation and software access to a major customer, with India’s prospective order giving the negotiations greater significance for future export terms.

France’s decision to keep sensitive M88 manufacturing and core combat system authority at home preserves control over technologies that underpin its own operational requirements, while the Hyderabad agreements allow production of major structures to grow through a partner outside France.

India’s prospective gains are equally tangible where the agreements transfer recurring work, because domestic fuselage manufacture and engine repair can build a permanent workforce and reduce reliance on overseas turnaround for some tasks that directly affect day-to-day fleet availability.

The two countries would share some production risks while retaining different sources of leverage, with France depending on Hyderabad for part of its expanded structural output and India relying on French suppliers for critical engine components and combat system support.

For South Asian defence planners, the earliest measurable indicators will be delivery schedules, induction capacity and support commitments, because those factors determine when India can sustain more Rafales in service and whether the procurement alters expectations about its available airpower.

In the wider Indo-Pacific, the precedent reaches beyond India’s eventual fighter numbers because it tests whether a major European supplier can build production capacity in the region while retaining authority over technologies it regards as central to national defence.

Comparing the M88 proposal with the Advanced Medium Combat Aircraft engine talks also shows why India can accept different forms of industrial partnership for different procurement needs, pursuing near-term fighter readiness alongside a longer-term effort to acquire engine design rights.

The final negotiating text will determine whether India secures a combination of domestic assembly, repair throughput, access to critical spares and authority over weapons integration, with each element affecting the fleet at a different point in its operational life.

The clearest near-term measures of Indian control will be which repairs Hyderabad can finish with parts on hand and what supply commitments cover the rest, because those terms will shape Rafale availability after the first aircraft are delivered.

Leave A Reply

Your email address will not be published.