The Rafale and what you know about it.
- Thread starter Picdelamirand-oil
- Start date
1. Starting point: availability is not a ‘bonus’, it is a prerequisite for operational existence
The Saphir exercise (February 2024) serves as a revealing example here: around Mont-de-Marsan, intense activity is sought not for ‘show’, but to test the ability to maintain a pace: the goal is to have 20 aircraft available, each capable of flying several missions per day, over five days, resulting in nearly 200 sorties. The real objective is a ‘high-intensity’ ramp-up, where the value of a weapons system is measured as much by its tactical effectiveness as by its ability to remain operational.
With this in mind, the central argument is clear: the best aircraft in the world is useless if it does not fly when needed. However, modern aircraft are becoming increasingly complex: availability is becoming a challenge, and it depends less on slogans than on a support architecture that is designed, contracted, managed and constantly adjusted.
The Rafale stands out, including through feedback from abroad (India, Greece) citing up to 90% technical availability. The question therefore becomes: what is it about the initial design and support organisation that makes these levels achievable, and what do they really mean?
2. Role of the DMAé: ‘project management’ of in-service support
The DMAé is defined, in programme vocabulary, as a project manager: it enters into the necessary contracts to enable the forces to fly, and organises the industrial ecosystem (engineers, technicians, workers) to ensure availability.
The financial order of magnitude is given at the joint level (Air and Space Force, Navy, ALAT): approximately €4 billion in payments (by 2025) for more than 45 fleets and approximately 1,200 aircraft. The scope is clarified: it covers support and maintenance (not fuel), as well as minor developments and ‘support’ innovation. The major armament standards (development/production/delivery) remain the responsibility of the DGA; the DMAé is mainly involved in the utilisation phase.
This separation of roles is essential: it structures the interface between capability trajectories, activity trajectories and industrial reality.
3. How an annual availability target is set: from policy to execution
The diagram is presented as a chain:
The discussion is not a one-off event: it is held annually and then monitored during implementation, with adjustments made as necessary.
4. Availability: the industrial commitment covers the fleet, and maintenance work ‘pulls down’ the average
One major point, which is often misunderstood, needs to be clarified: contractual availability is calculated for the fleet as a whole (not on a per-aircraft basis) and includes downtime due to maintenance work (modernisation, repairs, corrosion, etc.). Each aircraft does have its own ‘specific’ availability, but the contract commits the manufacturer to an average value for the entire fleet.
The fleet is heterogeneous: some aircraft are older, have undergone more wear and tear, or are in ‘better shape’. Manufacturers must organise themselves: for example, a maximum simultaneous unavailability linked to a type of work (1, 2 or 3 aircraft out of 100) is set, then schedules are negotiated in line with user requirements.
The key idea is that of ongoing dialogue between the DMAé, the armed forces and industry to minimise the impact of work while maintaining activity.
5. Continuous modernisation: F4 standards and long projects, managed through optimisation
Modernisation is described as structural: F4.1, then F4.2, then F4.2 block 2+; in the longer term, discussions on F4.3 / block 3 and on tranche 5T carrying F5. For F4.1, the key point is the duration: we are talking about a project lasting several months, with an order of magnitude given as five months per aircraft (from memory, indicated as such), which necessarily implies a gradual transformation over several years.
The text emphasises two mechanisms:
The philosophy can be summarised as follows: an aircraft that no longer evolves is often an aircraft at the end of its life. The Rafale, designed in the 1980s and entered service in the 2000s, is designed to last; therefore, it must evolve, which requires work. The cost of a renovation (even one that immobilises the aircraft) remains, according to them, much lower than a new acquisition: this is a rational approach to the life cycle.
6. Small size, high efficiency, ‘rustic’ projection: a coherent system
The fleet figures are outlined in broad terms: approximately 100+ Rafales for the Air and Space Force, 41 for the Navy, i.e. less than 150 aircraft (excluding the Mirage 2000). The argument put forward is that multi-role efficiency and the ability to withstand intensive exercises (leaving early, returning late, carrying out ‘all missions’) allow for a smaller format than some of its counterparts.
Projection is described as a marker: the ability to project three Rafales, with an A400M and an MRTT, quickly and far, with a limited footprint. This robustness is understood here in the sense of ‘easily deployable’ rather than ‘technologically simple’.
In the background, industry is explicitly recognised as a component of success (Dassault, Safran, Thales), with a relationship structured by contractual incentives: we are not in an ideal world, but in a controlled world.
The Saphir exercise (February 2024) serves as a revealing example here: around Mont-de-Marsan, intense activity is sought not for ‘show’, but to test the ability to maintain a pace: the goal is to have 20 aircraft available, each capable of flying several missions per day, over five days, resulting in nearly 200 sorties. The real objective is a ‘high-intensity’ ramp-up, where the value of a weapons system is measured as much by its tactical effectiveness as by its ability to remain operational.
With this in mind, the central argument is clear: the best aircraft in the world is useless if it does not fly when needed. However, modern aircraft are becoming increasingly complex: availability is becoming a challenge, and it depends less on slogans than on a support architecture that is designed, contracted, managed and constantly adjusted.
The Rafale stands out, including through feedback from abroad (India, Greece) citing up to 90% technical availability. The question therefore becomes: what is it about the initial design and support organisation that makes these levels achievable, and what do they really mean?
2. Role of the DMAé: ‘project management’ of in-service support
The DMAé is defined, in programme vocabulary, as a project manager: it enters into the necessary contracts to enable the forces to fly, and organises the industrial ecosystem (engineers, technicians, workers) to ensure availability.
The financial order of magnitude is given at the joint level (Air and Space Force, Navy, ALAT): approximately €4 billion in payments (by 2025) for more than 45 fleets and approximately 1,200 aircraft. The scope is clarified: it covers support and maintenance (not fuel), as well as minor developments and ‘support’ innovation. The major armament standards (development/production/delivery) remain the responsibility of the DGA; the DMAé is mainly involved in the utilisation phase.
This separation of roles is essential: it structures the interface between capability trajectories, activity trajectories and industrial reality.
3. How an annual availability target is set: from policy to execution
The diagram is presented as a chain:
- Political intention (white papers)
- Budgets and trajectories (LPM): capability trajectories and activity trajectories
- Annual breakdown: discussion/negotiation between the DMAé and the armed forces to translate missions, exercises, contingencies and economic conditions into activity targets and therefore availability targets.
The discussion is not a one-off event: it is held annually and then monitored during implementation, with adjustments made as necessary.
4. Availability: the industrial commitment covers the fleet, and maintenance work ‘pulls down’ the average
One major point, which is often misunderstood, needs to be clarified: contractual availability is calculated for the fleet as a whole (not on a per-aircraft basis) and includes downtime due to maintenance work (modernisation, repairs, corrosion, etc.). Each aircraft does have its own ‘specific’ availability, but the contract commits the manufacturer to an average value for the entire fleet.
The fleet is heterogeneous: some aircraft are older, have undergone more wear and tear, or are in ‘better shape’. Manufacturers must organise themselves: for example, a maximum simultaneous unavailability linked to a type of work (1, 2 or 3 aircraft out of 100) is set, then schedules are negotiated in line with user requirements.
The key idea is that of ongoing dialogue between the DMAé, the armed forces and industry to minimise the impact of work while maintaining activity.
5. Continuous modernisation: F4 standards and long projects, managed through optimisation
Modernisation is described as structural: F4.1, then F4.2, then F4.2 block 2+; in the longer term, discussions on F4.3 / block 3 and on tranche 5T carrying F5. For F4.1, the key point is the duration: we are talking about a project lasting several months, with an order of magnitude given as five months per aircraft (from memory, indicated as such), which necessarily implies a gradual transformation over several years.
The text emphasises two mechanisms:
- the initial intention (mainly software standard) can be loaded over time as opportunities arise (helmet visor, canopy/tiles modifications, etc.);
- optimisation is carried out through combined projects (retrofit + maintenance visits) to avoid sequential accumulation of downtime.
The philosophy can be summarised as follows: an aircraft that no longer evolves is often an aircraft at the end of its life. The Rafale, designed in the 1980s and entered service in the 2000s, is designed to last; therefore, it must evolve, which requires work. The cost of a renovation (even one that immobilises the aircraft) remains, according to them, much lower than a new acquisition: this is a rational approach to the life cycle.
6. Small size, high efficiency, ‘rustic’ projection: a coherent system
The fleet figures are outlined in broad terms: approximately 100+ Rafales for the Air and Space Force, 41 for the Navy, i.e. less than 150 aircraft (excluding the Mirage 2000). The argument put forward is that multi-role efficiency and the ability to withstand intensive exercises (leaving early, returning late, carrying out ‘all missions’) allow for a smaller format than some of its counterparts.
Projection is described as a marker: the ability to project three Rafales, with an A400M and an MRTT, quickly and far, with a limited footprint. This robustness is understood here in the sense of ‘easily deployable’ rather than ‘technologically simple’.
In the background, industry is explicitly recognised as a component of success (Dassault, Safran, Thales), with a relationship structured by contractual incentives: we are not in an ideal world, but in a controlled world.
7. Contingencies and accidents: repair, arbitration, and management of ‘potential hours’
A case of a serious incident (collision, structural damage) is used to describe the mechanics: securing, technical report, dialogue between DMAé–DGA–industry, costing and repair plan (technical expertise), technical and financial proposal, negotiation, launch of work, then return to airworthiness (authorities involved cited: technical authority, DGA, employment authority, DSAé).
Two key ideas:
8. Interface tools: support management centres (PCS)
PCSs are presented as a practical local interface that enables direct dialogue between the armed forces, industry and the DMAé, particularly when unexpected events occur: accidents, serious technical incidents (severity 1), airworthiness issues, quarantine decisions, risk assessments.
The PCS also serves as a mechanism for transparency on industrial constraints (e.g. supply chain tension) and operational needs (e.g. increased activity), so that everyone can anticipate and propose solutions.
9. ‘Cocooned aircraft’: past logic, different present context
The text indicates that in the mid-2010s, it may have been appropriate to put certain Rafale aircraft ‘in storage’ (potential regeneration), partly because not all aircraft were at the same level of equipment (e.g. AESA) and because the fleet structure (Mirage 2000 still numerous) offered margins.
Today, the diagnosis is clear:
10. The conceptual key: condition-based maintenance (testability + localisation + accessibility)
This is the doctrinal core of maintenance.
10.1 Principle
Condition-based maintenance aims to base maintenance on the actual condition observed, via sensors and integrated testability, rather than on a scheduled plan of periodic visits.
10.2 Requirements
The system imposes stringent requirements:
sensors and measurements everywhere (from the design stage);
software to operate these measurements (drift detection, predictive, fault detection);
above all: very high fault localisation rate, to avoid removing several pieces of equipment ‘for safety reasons’.
10.3 Operational execution
Consequences:
10.4 Physical accessibility
Condition-based maintenance is reinforced by a highly advanced accessibility design: ‘hatches everywhere’, logical routing, avoiding the need to remove one piece of equipment to reach another. The absence of hatches on some ‘smooth’ aircraft is presented as a negative factor for maintainability.
10.5 Compromise with stealth
The compromise is accepted: opening hatches complicates electromagnetic stealth; therefore, the desired stealth must remain compatible with maintainability. The Rafale is positioned for ‘reasonable’ stealth (better than the Mirage 2000) so as not to sacrifice access.
10.6 Lesson in methodology
The thesis is explicit: this level of ambition cannot be ‘added’ after the fact. It must be specified from the outset, for all equipment, in a comprehensive manner, because any airworthiness failure counts for the crew.
11. MCO cost: delicate comparisons, but clear life cycle logic
The argument rejects a raw comparison between the Mirage 2000 and the Rafale at a late stage, as the cost depends on the stage of the life cycle: fewer aircraft, obsolescence, fixed costs spread over a smaller base, etc. The Mirage 2000 should be compared ‘at the heart of its life’ with the Rafale ‘at the heart of its life’.
However, two ideas remain:
12. Logistical footprint and projection: maintenance load as a strategic variable
The maintenance load is presented as an initial, contractual requirement, followed standard after standard, including F5: do not increase the load, as this means more mechanics (a scarce resource) and reduced exportability.
Projection benefits from the ‘as-needed’ approach: there is less need to bring along a logistics train corresponding to a scheduled maintenance plan; a backup batch is carried, and the footprint is reduced. Comparative example provided: Mirage 2000 deployment with 16 trucks (cited experience), versus Pégase-type Rafale projection models (three Rafale + MRTT + A400M).
The text also mentions the prospect of sharing parts with partners (subject to agreements and airworthiness constraints) and the arrival of optimisation/predictive tools to reduce tasks and adapt maintenance to constrained environments (Africa vs mainland France).
13. High intensity: five DMAé axes (preparation, expertise, supply chain, innovation, organisation)
The ‘high intensity’ sequence is structured around five axes:
All of this is put into perspective: these approaches must be identified upstream in strategies to support future systems (Rafale F5, drone, SCAF).
14. Conclusion: the Rafale as a sustainable programme and general lesson
The director concludes by presenting the Rafale as a major post-war programme, not only because of its design and export success, but also because of user satisfaction with an aircraft that is efficient, versatile and easy to maintain in operational terms.
The lesson learned is a rule of method:
when essential support requirements are integrated upstream, the programme runs more smoothly because the user is satisfied and long-term development remains possible on a basis accepted by the armed forces.
A case of a serious incident (collision, structural damage) is used to describe the mechanics: securing, technical report, dialogue between DMAé–DGA–industry, costing and repair plan (technical expertise), technical and financial proposal, negotiation, launch of work, then return to airworthiness (authorities involved cited: technical authority, DGA, employment authority, DSAé).
Two key ideas:
- major repairs take time (design office, workshop), but the process is structured;
- the impact on flight hours is handled through fleet management: the fleet is a reservoir of hours. Based on a target of 250 hours/year on average, certain aircraft can be ‘pushed’ more at times (over 1–3 years) and then compensated for by reducing their activity, shifting the load to other aircraft (a logic already seen in targeted retrofits, particularly in the Navy).
8. Interface tools: support management centres (PCS)
PCSs are presented as a practical local interface that enables direct dialogue between the armed forces, industry and the DMAé, particularly when unexpected events occur: accidents, serious technical incidents (severity 1), airworthiness issues, quarantine decisions, risk assessments.
The PCS also serves as a mechanism for transparency on industrial constraints (e.g. supply chain tension) and operational needs (e.g. increased activity), so that everyone can anticipate and propose solutions.
9. ‘Cocooned aircraft’: past logic, different present context
The text indicates that in the mid-2010s, it may have been appropriate to put certain Rafale aircraft ‘in storage’ (potential regeneration), partly because not all aircraft were at the same level of equipment (e.g. AESA) and because the fleet structure (Mirage 2000 still numerous) offered margins.
Today, the diagnosis is clear:
- the minimum standard is high (F3R widespread; old F2/F3.2 aircraft gone ‘from the top’);
- the question is no longer ‘should we use this Rafale?’ but ‘we don't have enough’;
- there is no ‘stock’ of Rafales: no dormant fleet;
- the fleet is at full capacity: ‘every percentage point of availability is a battle’, and the margins are very small; losing a significant number of aircraft in combat would immediately become an issue.
10. The conceptual key: condition-based maintenance (testability + localisation + accessibility)
This is the doctrinal core of maintenance.
10.1 Principle
Condition-based maintenance aims to base maintenance on the actual condition observed, via sensors and integrated testability, rather than on a scheduled plan of periodic visits.
10.2 Requirements
The system imposes stringent requirements:
sensors and measurements everywhere (from the design stage);
software to operate these measurements (drift detection, predictive, fault detection);
above all: very high fault localisation rate, to avoid removing several pieces of equipment ‘for safety reasons’.
10.3 Operational execution
Consequences:
- fault reporting via maintenance pages;
- information available to the crew;
- data collation on return from mission;
- rapid standard exchange before the next flight.
10.4 Physical accessibility
Condition-based maintenance is reinforced by a highly advanced accessibility design: ‘hatches everywhere’, logical routing, avoiding the need to remove one piece of equipment to reach another. The absence of hatches on some ‘smooth’ aircraft is presented as a negative factor for maintainability.
10.5 Compromise with stealth
The compromise is accepted: opening hatches complicates electromagnetic stealth; therefore, the desired stealth must remain compatible with maintainability. The Rafale is positioned for ‘reasonable’ stealth (better than the Mirage 2000) so as not to sacrifice access.
10.6 Lesson in methodology
The thesis is explicit: this level of ambition cannot be ‘added’ after the fact. It must be specified from the outset, for all equipment, in a comprehensive manner, because any airworthiness failure counts for the crew.
11. MCO cost: delicate comparisons, but clear life cycle logic
The argument rejects a raw comparison between the Mirage 2000 and the Rafale at a late stage, as the cost depends on the stage of the life cycle: fewer aircraft, obsolescence, fixed costs spread over a smaller base, etc. The Mirage 2000 should be compared ‘at the heart of its life’ with the Rafale ‘at the heart of its life’.
However, two ideas remain:
- modern aircraft are more densely equipped and integrated (analogy with Motorola vs iPhone);
- competitiveness can be seen in the export market: price and maintainability are attractive enough that Mirage nations have switched to Rafale.
12. Logistical footprint and projection: maintenance load as a strategic variable
The maintenance load is presented as an initial, contractual requirement, followed standard after standard, including F5: do not increase the load, as this means more mechanics (a scarce resource) and reduced exportability.
Projection benefits from the ‘as-needed’ approach: there is less need to bring along a logistics train corresponding to a scheduled maintenance plan; a backup batch is carried, and the footprint is reduced. Comparative example provided: Mirage 2000 deployment with 16 trucks (cited experience), versus Pégase-type Rafale projection models (three Rafale + MRTT + A400M).
The text also mentions the prospect of sharing parts with partners (subject to agreements and airworthiness constraints) and the arrival of optimisation/predictive tools to reduce tasks and adapt maintenance to constrained environments (Africa vs mainland France).
13. High intensity: five DMAé axes (preparation, expertise, supply chain, innovation, organisation)
The ‘high intensity’ sequence is structured around five axes:
- Preparation: increasing exercises, crisis maintenance, aircraft tours, dispersion, remote projection.
- Technical expertise: re-acculturation to combat damage; rapid repair as close as possible; switch to degraded operation; use of degraded modes provided for in the design (redundancies, acceptable partial losses).
- Key concept: ORM (operational risk management); accepting different levels of risk depending on the context (illustrated by the transition from 10-6 to 10-4).
- Supply chain: balance between stocks and flows; impossibility of storing everything everywhere; need for a rear base and ramp-up of spare parts.
- Innovation: use of maintenance and ageing data, optimisation of fleet management (choosing ‘the 30 best’ out of 100 for projection), logistical anticipation; diagnostic tools, NDT, additive manufacturing, decision support, demonstrators.
All of this is put into perspective: these approaches must be identified upstream in strategies to support future systems (Rafale F5, drone, SCAF).
14. Conclusion: the Rafale as a sustainable programme and general lesson
The director concludes by presenting the Rafale as a major post-war programme, not only because of its design and export success, but also because of user satisfaction with an aircraft that is efficient, versatile and easy to maintain in operational terms.
The lesson learned is a rule of method:
when essential support requirements are integrated upstream, the programme runs more smoothly because the user is satisfied and long-term development remains possible on a basis accepted by the armed forces.
Last edited:
Click on the link below to read the article.
To translate the article from French to English, go to the top right hand corner. There is even a Hindi option
The Rafale and Electronic Warfare
https://omnirole-rafale.com/le-rafale-e
28 Feb 2026
To translate the article from French to English, go to the top right hand corner. There is even a Hindi option
The Rafale and Electronic Warfare
https://omnirole-rafale.com/le-rafale-e
28 Feb 2026
The Rafale F5: an opportunity to create a sovereign, real-time cloud.
The war in Ukraine has revealed a profound transformation in modern warfare: operational superiority now depends as much on data infrastructure as on combat platforms themselves. The ability to connect sensors, drones, aircraft, command centers, and ground forces has become the true backbone of operations. In this context, low-orbit satellite constellations have emerged as a decisive element of resilience. Starlink has provided the most visible illustration of this.
But this development raises a fundamental strategic question for Europe: can it continue to depend on private or foreign infrastructure for its military information architecture? The most realistic answer is probably not to replicate the American model, but to gradually build a distributed architecture based on existing capabilities in Europe. The Rafale F5 could serve as a catalyst for this construction.
The planned evolution of the Rafale F5—cooperation with drones, advanced data fusion, extended electronic warfare, and increased sensors—implies a change of scale in the flow of information. Platforms will need to exchange much more data much more quickly. To support this collaborative combat model, it makes sense to rely on an orbital infrastructure capable of providing robust, distributed, and sovereign connectivity.
However, this infrastructure should not be designed as a centralized decision-making center. A truly robust military architecture must remain distributed. Each platform must retain its capacity for autonomous decision-making and action. The network is not a brain, but a backbone that carries information, synchronizes observations, and allows a coherent picture of the situation to be reconstructed.
In this context, Europe already has several essential building blocks. Military satellites such as Syracuse provide the most sensitive strategic communications. Galileo provides an independent navigation and synchronization reference. The OneWeb and IRIS² projects form the basis of a low-orbit constellation capable of transporting operational data flows. By combining these elements, it becomes possible to gradually build a distributed architecture capable of supporting air, naval, and land operations.
But a new element could profoundly transform the scope of this project: the involvement of India.
India currently occupies a unique geopolitical position. It seeks to preserve its strategic autonomy vis-à-vis the major powers while rapidly developing its industrial and technological capabilities. It already has a solid space program, growing experience in satellites, and clear ambitions in the fields of defense and artificial intelligence. It is also already linked to the OneWeb ecosystem, one of whose main shareholders is the Bharti group.
In this context, a European orbital architecture involving India would offer several major advantages.
First, it would offer much greater strategic and geographical depth. A constellation developed jointly by Europe and India would naturally cover the Euro-Mediterranean area, the Indian Ocean, and a large part of the Indo-Pacific. This geographical continuity would considerably strengthen the system's resilience and broaden its military and civilian applications.
Second, it would allow for the sharing of the industrial and financial effort required to set up a large constellation. Modern space infrastructure requires considerable investment. A Franco-Indian partnership extended to Europe would allow these costs to be shared while ensuring shared political control between strategic partners.
Such a partnership would also be clearly consistent with the growing cooperation between France and India in the field of defense. The Rafale is already a pillar of this relationship. Ongoing cooperation on fighter jet engines for the AMCA program is another. From this perspective, the development of a common orbital infrastructure would be a logical extension of this cooperation.
For the Rafale F5 and its successors, the existence of such an architecture would offer new capabilities: distributed sharing of radar observations, coordination with accompanying drones, beyond-line-of-sight communications relays, rapid updating of threat databases, and post-mission exploitation of collected data. Above all, it would ensure that these information flows remain under the control of strategic partners who share the same vision of technological autonomy.
Ultimately, this architecture could evolve into a genuine collaborative combat infrastructure linking European and Indian forces. It could serve as a basis for joint operations, multinational exercises, or maritime security missions in the Indian Ocean. It would also offer a credible alternative to infrastructures dominated by the major technological powers.
Such a development would not necessarily be incompatible with NATO. On the contrary, it could be complementary. The United States would retain its own global architecture, while Europe would have a system capable of supporting its operations autonomously when necessary. In this context, the Euro-Indian infrastructure could constitute a second technological pillar, interoperable with NATO but not dependent on it.
In a world where alliances are becoming more flexible and technological sovereignty is becoming a central issue, such a project would make strong strategic sense. It would link two large democratic areas—Europe and India—around a shared orbital infrastructure capable of supporting their economic ambitions, space programs, and defense capabilities.
From this perspective, the Rafale F5 could be more than just an evolution of a fighter jet. It could become one of the catalysts for a new strategic architecture linking Europe and India in orbital space. A distributed, resilient, and sovereign architecture, adapted to the information warfare that now characterizes the 21st century.
Satellites can be physically shared but logically separate. This is already how several modern space systems operate. Three levels can be imagined:
The war in Ukraine has revealed a profound transformation in modern warfare: operational superiority now depends as much on data infrastructure as on combat platforms themselves. The ability to connect sensors, drones, aircraft, command centers, and ground forces has become the true backbone of operations. In this context, low-orbit satellite constellations have emerged as a decisive element of resilience. Starlink has provided the most visible illustration of this.
But this development raises a fundamental strategic question for Europe: can it continue to depend on private or foreign infrastructure for its military information architecture? The most realistic answer is probably not to replicate the American model, but to gradually build a distributed architecture based on existing capabilities in Europe. The Rafale F5 could serve as a catalyst for this construction.
The planned evolution of the Rafale F5—cooperation with drones, advanced data fusion, extended electronic warfare, and increased sensors—implies a change of scale in the flow of information. Platforms will need to exchange much more data much more quickly. To support this collaborative combat model, it makes sense to rely on an orbital infrastructure capable of providing robust, distributed, and sovereign connectivity.
However, this infrastructure should not be designed as a centralized decision-making center. A truly robust military architecture must remain distributed. Each platform must retain its capacity for autonomous decision-making and action. The network is not a brain, but a backbone that carries information, synchronizes observations, and allows a coherent picture of the situation to be reconstructed.
In this context, Europe already has several essential building blocks. Military satellites such as Syracuse provide the most sensitive strategic communications. Galileo provides an independent navigation and synchronization reference. The OneWeb and IRIS² projects form the basis of a low-orbit constellation capable of transporting operational data flows. By combining these elements, it becomes possible to gradually build a distributed architecture capable of supporting air, naval, and land operations.
But a new element could profoundly transform the scope of this project: the involvement of India.
India currently occupies a unique geopolitical position. It seeks to preserve its strategic autonomy vis-à-vis the major powers while rapidly developing its industrial and technological capabilities. It already has a solid space program, growing experience in satellites, and clear ambitions in the fields of defense and artificial intelligence. It is also already linked to the OneWeb ecosystem, one of whose main shareholders is the Bharti group.
In this context, a European orbital architecture involving India would offer several major advantages.
First, it would offer much greater strategic and geographical depth. A constellation developed jointly by Europe and India would naturally cover the Euro-Mediterranean area, the Indian Ocean, and a large part of the Indo-Pacific. This geographical continuity would considerably strengthen the system's resilience and broaden its military and civilian applications.
Second, it would allow for the sharing of the industrial and financial effort required to set up a large constellation. Modern space infrastructure requires considerable investment. A Franco-Indian partnership extended to Europe would allow these costs to be shared while ensuring shared political control between strategic partners.
Such a partnership would also be clearly consistent with the growing cooperation between France and India in the field of defense. The Rafale is already a pillar of this relationship. Ongoing cooperation on fighter jet engines for the AMCA program is another. From this perspective, the development of a common orbital infrastructure would be a logical extension of this cooperation.
For the Rafale F5 and its successors, the existence of such an architecture would offer new capabilities: distributed sharing of radar observations, coordination with accompanying drones, beyond-line-of-sight communications relays, rapid updating of threat databases, and post-mission exploitation of collected data. Above all, it would ensure that these information flows remain under the control of strategic partners who share the same vision of technological autonomy.
Ultimately, this architecture could evolve into a genuine collaborative combat infrastructure linking European and Indian forces. It could serve as a basis for joint operations, multinational exercises, or maritime security missions in the Indian Ocean. It would also offer a credible alternative to infrastructures dominated by the major technological powers.
Such a development would not necessarily be incompatible with NATO. On the contrary, it could be complementary. The United States would retain its own global architecture, while Europe would have a system capable of supporting its operations autonomously when necessary. In this context, the Euro-Indian infrastructure could constitute a second technological pillar, interoperable with NATO but not dependent on it.
In a world where alliances are becoming more flexible and technological sovereignty is becoming a central issue, such a project would make strong strategic sense. It would link two large democratic areas—Europe and India—around a shared orbital infrastructure capable of supporting their economic ambitions, space programs, and defense capabilities.
From this perspective, the Rafale F5 could be more than just an evolution of a fighter jet. It could become one of the catalysts for a new strategic architecture linking Europe and India in orbital space. A distributed, resilient, and sovereign architecture, adapted to the information warfare that now characterizes the 21st century.
Satellites can be physically shared but logically separate. This is already how several modern space systems operate. Three levels can be imagined:
- sovereign national level
- coalition/partnership level
- civilian or dual level
- the satellites transport the data
- but only users with national keys can read it.
- This amounts to creating several superimposed networks within the same constellation.
We are going for 24 F5 standard Rafale. Maybe, in future we would increase its order to over 50 or 60. But unfortunately most of our Rafales would be of F4+ standard.
"shared political control"
"common orbital infrastructure"
I snorted as soon as I read these lines.
Absolute zero chance of this happening. Joint development is possible, but whatever we create will be entirely distinct from a pan-Indo-European "shared" system.
Strategic autonomy by definition is not shared. India's main goal is neutrality. Which means someday this network will be used to attack a friend of India, like some poor African country, and similarly India will attack a friend of Europe, like China. In both cases either side will object and defeat the purpose of the "shared" network leaving both sides vulnerable. This network will also be taken over the whims and fancies of member states in the EU where a 40 yo childless Karen PM of a country with a population smaller than my neighborhood gets to have a say over the defense needs of a fifth of humanity on the other side of the planet. No, thank you.
And I'm sure this will be a "democratic process," where Europe gets 27 votes and India gets one.
Plus, it's obvious Europe knows it cannot afford to build such a network. So what next? India foots the bill for this, and then gets told how Europe cannot release all source codes 'cause crown jewels or something? And what if India develops the network, will Europe hand over the sources codes to their platforms for integration? Should we hand over our source codes then?
There is a reason why even the US doesn't share its communication systems protocols with Europe and only gets the option to use them.
The whole thing is entirely unfeasible.
Joint development is definitely feasible and is already happening with France to a certain degree on SBS P3; 21 satellites with France and 31 satellites via Indian private companies. From a previous agreement, the initial plan for JV for 8-10 satellites included joint operations for maritime surveillance. But SBS P3 is for the exclusive use of the Indian military, with France potentially gaining contractual access via sharing intelligence, even real-time access, rather than having operational control over the satellites. And this is for France alone.
IMO (not that it changes anything), the 114-jet order should be an even split between F4 and F5, 57 jets each. I say so bcoz by the time the Indian production line comes online and starts churning out jets, France will have certified and cleared F5 for serial production (~2032). So by that year, we could wrap up F4 production and start building F5. Ofc, just my €0.02. Theres still a while before the parties sign the dotted line, the numbers split could change either way.
It will be difficult to streamline production with a small number of F4s, the minimum necessary will be 90. F5 uses a new engine and different internal estate and avionics, so we will have to continue the production line with more numbers later on for F5 too. Plus exports. After spending so much, we are unlikely to stop at 200.