Shield AI targets Poland for autonomous X-BAT fighter jet production and NATO F-16 engine hub
{loadposition bannertop}
{loadposition sidebarpub}
Polish Prime Minister Donald Tusk announced that U.S. defense firm Shield AI has offered Poland an industrial role in its X-BAT autonomous uncrewed combat aircraft program and proposed the establishment of a regional F-16 engine sustainment hub in the country. This dual-track proposal aims to integrate Polish aerospace manufacturers into the early production cycle of runway-independent, next-generation combat assets before serial manufacturing begins. Simultaneously, the initiative seeks to establish a centralized European maintenance facility for the General Electric F110 engine family to support distributed NATO air operations on the eastern flank.
The X-BAT is an autonomous tail-sitter vertical takeoff and landing aircraft powered by a single F110-GE-129 engine with a thrust-vectoring nozzle, offering a maximum range exceeding 2,000 nautical miles and an operational ceiling above 50,000 feet. Developed around Shield AI’s Hivemind software stack to ensure mission execution in GNSS-denied environments, the platform is tracking a compressed schedule that aims for prototype demonstrations in 2028 and initial production planning by 2029.
Related topic: Poland Targets GCAP Sixth-Generation Fighter Program to Secure Future NATO Airpower Role
During Eurosatory 2026, Shield AI displayed a redesigned 45% scale model of the X-BAT, which abandoned the original cranked-kite planform and adopted a straight leading edge with greater sweep, producing a sharper arrowhead-shaped flying wing configuration. (Picture source: Army Recognition)
On June 16, 2026, Polish Prime Minister Donald Tusk announced that the U.S. company Shield AI wants Poland to take part in the X-BAT autonomous combat aircraft program and establish a regional F-16 engine support center in Poland intended to serve NATO operators in Europe. The proposal links two separate but mutually reinforcing areas: an industrial role in a new unmanned combat aircraft before serial production begins, and a sustainment role for the F110 engine already used across several NATO fighter fleets. The timing matters because the X-BAT was publicly unveiled only in October 2025, after approximately 18 months of preliminary development work, and Shield AI is already looking beyond a purely U.S.-based industrial model.
For Warsaw, the offer intersects with several parallel decisions: the future size and composition of the Polish fighter fleet, Poland’s possible participation in the Global Combat Air Programme (GCAP), the introduction of the F-35A, the continued operation of F-16C/D Block 52+ fighters, and the government’s effort to move the national aerospace sector beyond licensed production, repair activity, and subcontracting. The X-BAT program is notable because its published schedule is compressed by the standards of combat aircraft development. Shield AI has already completed wind tunnel testing, radar cross-section testing, engine integration work, and structural pathfinder construction, with first vertical takeoff and landing flight tests planned for 2026.
Mission-capable prototype demonstrations are targeted for 2028, and initial production planning is expected for 2029. That sequence would move the aircraft from public unveiling to production planning in four years, whereas many Western fighter jet programs take more than ten years to move from early design to initial operational use. The reason the schedule is possible is that Shield AI is not trying to develop every major subsystem from scratch. The X-BAT uses an existing fighter engine, applies an autonomy stack already demonstrated on the F-16 and unmanned aircraft, and uses a tail-sitter airframe that avoids the mechanical complexity of tiltrotors, rotating nacelles, or lift-fan propulsion.
The X-BAT is configured as a tail-sitter vertical takeoff and landing aircraft, meaning it launches vertically on the thrust of a single afterburning turbofan, then transitions into wing-borne forward flight once clear of the launch area. The X-BAT has a wingspan of 39 ft (equal to 11.9 m), a length of 26 ft (7.9 m), a maximum range of more than 2,000 nautical miles (3,700 km), with a service ceiling above 50,000 ft and a maneuver load factor greater than 4g. These figures place it well above small tactical UAVs in range, altitude, propulsion class, and intended mission set, while keeping it below manned fighter aircraft in size and maneuver requirements. The airframe design is therefore a compromise between combat maneuvering, endurance, structural mass, and vertical recovery requirements.
The propulsion arrangement is one of the key differentiators of the X-BAT. It uses an F110-GE-129 engine with the Axisymmetric Vectoring Exhaust Nozzle, or AVEN, which gives the aircraft the thrust-vectoring authority required for vertical launch, transition, and tail-first recovery. The F110 engine family already powers multiple F-16 and F-15 variants, making it a mature propulsion base rather than an experimental engine. The X-BAT does not use an F-35B-style lift-fan, which would add weight, volume, shafting, doors, and maintenance burden. It also does not use the V-22 Osprey’s tiltrotor arrangement, which requires rotating nacelles and large proprotors. Instead, it uses a single central propulsion line and a thrust-vectoring exhaust approach rooted in technologies explored through the F-15 ACTIVE and related U.S. flight-control programs.
This choice reduces the number of moving propulsion assemblies, but it also places higher demands on inlet design, flight-control software, thrust management, and recovery precision. The propulsion choice also explains why the proposed Polish engine center may be more achievable in the near term than an X-BAT manufacturing in the country. Poland already operates F-16C/D Block 52+ fighters and is receiving its first F-35A stealth fighters, giving it a growing combat aircraft sustainment requirement regardless of the X-BAT’s eventual production outcome. A Polish F110 maintenance hub would be relevant to existing European F-16 operators and to any future X-BAT fleet using the same engine family.
Sustainment work also tends to produce longer industrial continuity than final assembly, because engines require inspection, repair, overhaul, component replacement, testing, and life-cycle management across decades of service. A regional F110 support center in Poland could therefore become a practical industrial anchor even if the X-BAT manufacturing starts later, remains limited at first, or is divided among several countries. For NATO, such a center would also reduce dependence on longer supply chains and could shorten maintenance cycles for F110-powered aircraft based in Europe. The autonomy architecture is also central to X-BAT’s military relevance. The unmanned aircraft is built around Shield AI’s Hivemind software stack, which has already demonstrated an autonomous control capability on the F-16 and multiple unmanned systems.
Hivemind is designed for operation without continuous GPS access and for mission continuation during communications disruption. That matters because modern air operations increasingly occur under GNSS denial, datalink interference, electronic attack, and cyber-electromagnetic pressure. The war in Ukraine, Poland’s neighbour, has shown that navigation and communications cannot be assumed even for relatively short-range unmanned aircraft, and the problem is more severe for systems expected to penetrate defended airspace. The X-BAT is therefore not built around the assumption that a remote operator or manned aircraft will constantly control it by datalink. It can work with manned aircraft, but it is also intended to execute assigned missions independently when connectivity is interrupted.
This makes the X-BAT different from earlier UAV concepts that depended on continuous command links. In a permissive environment, a datalink allows retasking, human supervision, target updates, and coordination with manned aircraft. In a contested environment, that same dependency can become a vulnerability if jamming, terrain masking, emissions control, or cyber-electromagnetic activity interrupts the link. The X-BAT’s autonomy model is consequently intended to reduce that vulnerability by allowing the aircraft to continue under preloaded mission parameters and established rules when external control is degraded. This does not remove the requirement for mission planning, data loading, target validation, communications management, or human decision-making at the operational level.
It changes where those functions occur and reduces the assumption that constant pilot-like control must be maintained throughout the mission. On June 15, 2026, at Eurosatory, Shield AI also displayed a 45% scale model of a redesigned X-BAT configuration that had been unveiled at Sea-Air-Space 2026. The redesigned airframe abandoned the original cranked-kite planform and adopted a straight leading edge with greater sweep, producing a sharper arrowhead-shaped flying-wing configuration. This change is not cosmetic. A more swept, arrowhead-like flying-wing layout can support higher-speed flight regimes, cleaner aerodynamic efficiency, internal volume management, and radar-signature control more effectively than some less-refined planforms.
The revised shape moves the X-BAT closer in visual and aerodynamic logic to aircraft such as Boeing’s X-45C Phantom Ray and China’s GJ-11 Sharp Sword. It also suggests that the program is being shaped not only around vertical takeoff and landing, but also around range, survivability, internal carriage, and high-subsonic transit performance. The X-BAT also differs from the main Western Collaborative Combat Aircraft designs now racing for future fighter operations. Boeing’s MQ-28 Ghost Bat relies on conventional runway operations, which means it still depends on usable airfields, taxiways, maintenance aprons, fuel points, and base defense. General Atomics’ YFQ-42A also requires traditional airfield infrastructure, and Anduril’s YFQ-44A follows the same runway-dependent operating model.
Airbus’ U760 Ravenstorm remains in the concept phase and is expected to enter service in the early 2030s, while Helsing’s CA-1 Europa focuses heavily on electronic warfare and collaborative operations. Shield AI’s X-BAT is currently the only announced Western CCA-type aircraft combining jet propulsion, internal weapons bays, fighter-sized engine power, and runway independence. Its closest conceptual ancestor is therefore not another current CCA but the Ryan X-13 Vertijet, a Cold War tail-sitter experiment now being revisited through modern autonomy, flight-control computing, inlet modeling, and stealth shaping.
The rather unique launch and recovery concept is one of the most important parts of the aircraft because it determines whether runway independence is operationally useful or only a technical feature. The X-BAT is built around a mobile Launch and Recovery Vehicle, or LRV, rather than a runway-based operating model. The aircraft is transported folded or stowed on the vehicle, which acts as the ground handling system, launch point, recovery point, and storage interface. For launch, the vehicle raises the aircraft into a vertical attitude, after which the single F110-GE-129 afterburning turbofan lifts it from the vehicle. The X-BAT then climbs vertically, clears the launch area, and transitions into forward wing-borne flight.
This sequence removes the need for a runway, but it still requires a launch area with sufficient clearance, fuel supply, weapons handling capacity, communications access, maintenance support, and security. Recovery is more demanding than launch, as the X-BAT returns in conventional forward flight and approaches the LRV before executing a high-angle-of-attack transition comparable to a cobra maneuver. It rotates from horizontal flight into a near-vertical attitude, stabilizes under thrust-vector control, descends tail-first, and lands on the recovery vehicle. The maneuver requires the inlet to keep feeding the engine while the aircraft moves from 0° to 90° angle of attack, a condition that can disrupt airflow if the inlet is not shaped and positioned correctly.
Shield AI’s work on this phase required extensive computational fluid dynamics analysis, wind-tunnel testing, and inlet design work. Unlike the Ryan X-13 Vertijet, where the pilot had to conduct a difficult tail-first recovery, the X-BAT performs the maneuver autonomously using flight control algorithms derived partly from the company’s V-BAT vertical takeoff and landing experience. The aircraft, therefore, does not require a runway, arresting cable, catapult, or conventional landing gear sequence for recovery. The storage and deployment metrics further show how Shield AI intends the X-BAT to be used in distributed operations. The storage figure is 40 ft × 14 ft × 6 ft, and the stated expeditionary footprint is 3:1, meaning that three X-BATs can fit in roughly the deck space of one legacy fighter. That matters for land and maritime deployment.
On land, the aircraft could be dispersed across roads, port areas, logistics compounds, remote islands, and austere operating locations. At sea, the same concept could apply to ship decks with sufficient clearance and support equipment. The aircraft’s vertical launch and recovery profile expands the number of possible operating locations, but it does not eliminate the logistical chain. Fuel trucks, weapons loading equipment, engine support, mission-data loading, recovery alignment, vehicle concealment, spare parts, and personnel protection become the critical limiting factors. Like the Gripen, the target set shifts from fixed runways and hardened shelters to mobile launch points and their support nodes. For NATO’s eastern flank, this operational logic is directly tied to survivability. A runway-independent aircraft like the X-BAT does not make air operations immune to attack, but it complicates adversary targeting by increasing the number of possible launch locations and reducing dependence on a small number of known air bases.
Moreover, the X-BAT’s range of more than 2,000 nautical miles also allows launch sites to be moved deeper into friendly territory or farther from immediate missile threat areas. This aligns with NATO’s Agile Combat Employment logic, which emphasizes dispersal, mobility, rapid relocation, and the ability to continue air operations after attacks on main operating bases. For Poland, the relevance is particularly high because its geography places key military infrastructure within reach of Russian and Belarusian missile systems, as well as long-range air-launched weapons. A mobile LRV-based fighter aircraft could support operations from a larger number of sites, including road networks, coastal areas, temporary operating locations, logistics hubs, and potentially maritime decks.
Poland’s potential gains from the dual proposal from Shield AI are therefore industrial, operational, and technological. Early access to the X-BAT and the GCAP would give Poland involvement in two next-generation combat aircraft programs before serial production begins, rather than after the design is already fixed and the industrial roles have already been allocated. Manufacturing participation would be more significant than a maintenance-only role, especially if Polish companies gain workshare in airframe structures, ground vehicles, support equipment, engine-related sustainment, mission systems integration, or component production.
Involvement in a software-intensive combat aircraft program like the X-BAT would also expose Poland’s aerospace and defense sector to autonomy, mission planning, human-machine teaming, electronic warfare resilience, and distributed operations. These areas are increasingly relevant to sixth-generation combat aircraft development, including the GCAP, which Poland is evaluating as part of its future combat aviation policy. For now, the engine center component may be the most concrete part of the proposal because it is based on an existing need. European F-16 fleets will continue to require F110 sustainment, and Poland’s own F-16C/D Block 52+ fleet already provides a domestic foundation for such work. A regional facility would create skilled maintenance activity, test-cell requirements, parts flows, inspection capacity, and engineering work that can remain active regardless of the pace of the X-BAT development.
Written by Jérôme Brahy
Jérôme Brahy is a defense analyst and documentalist at Army Recognition. He specializes in naval modernization, aviation, drones, armored vehicles, and artillery, with a focus on strategic developments in the United States, China, Ukraine, Russia, Türkiye, and Belgium. His analyses go beyond the facts, providing context, identifying key actors, and explaining why defense news matters on a global scale.
Explore More Defense News
• Land Defense News• Naval Defense News• Defense Aerospace News
{loadposition bannertop}
{loadposition sidebarpub}
Polish Prime Minister Donald Tusk announced that U.S. defense firm Shield AI has offered Poland an industrial role in its X-BAT autonomous uncrewed combat aircraft program and proposed the establishment of a regional F-16 engine sustainment hub in the country. This dual-track proposal aims to integrate Polish aerospace manufacturers into the early production cycle of runway-independent, next-generation combat assets before serial manufacturing begins. Simultaneously, the initiative seeks to establish a centralized European maintenance facility for the General Electric F110 engine family to support distributed NATO air operations on the eastern flank.
The X-BAT is an autonomous tail-sitter vertical takeoff and landing aircraft powered by a single F110-GE-129 engine with a thrust-vectoring nozzle, offering a maximum range exceeding 2,000 nautical miles and an operational ceiling above 50,000 feet. Developed around Shield AI’s Hivemind software stack to ensure mission execution in GNSS-denied environments, the platform is tracking a compressed schedule that aims for prototype demonstrations in 2028 and initial production planning by 2029.
Related topic: Poland Targets GCAP Sixth-Generation Fighter Program to Secure Future NATO Airpower Role
During Eurosatory 2026, Shield AI displayed a redesigned 45% scale model of the X-BAT, which abandoned the original cranked-kite planform and adopted a straight leading edge with greater sweep, producing a sharper arrowhead-shaped flying wing configuration. (Picture source: Army Recognition)
On June 16, 2026, Polish Prime Minister Donald Tusk announced that the U.S. company Shield AI wants Poland to take part in the X-BAT autonomous combat aircraft program and establish a regional F-16 engine support center in Poland intended to serve NATO operators in Europe. The proposal links two separate but mutually reinforcing areas: an industrial role in a new unmanned combat aircraft before serial production begins, and a sustainment role for the F110 engine already used across several NATO fighter fleets. The timing matters because the X-BAT was publicly unveiled only in October 2025, after approximately 18 months of preliminary development work, and Shield AI is already looking beyond a purely U.S.-based industrial model.
For Warsaw, the offer intersects with several parallel decisions: the future size and composition of the Polish fighter fleet, Poland’s possible participation in the Global Combat Air Programme (GCAP), the introduction of the F-35A, the continued operation of F-16C/D Block 52+ fighters, and the government’s effort to move the national aerospace sector beyond licensed production, repair activity, and subcontracting. The X-BAT program is notable because its published schedule is compressed by the standards of combat aircraft development. Shield AI has already completed wind tunnel testing, radar cross-section testing, engine integration work, and structural pathfinder construction, with first vertical takeoff and landing flight tests planned for 2026.
Mission-capable prototype demonstrations are targeted for 2028, and initial production planning is expected for 2029. That sequence would move the aircraft from public unveiling to production planning in four years, whereas many Western fighter jet programs take more than ten years to move from early design to initial operational use. The reason the schedule is possible is that Shield AI is not trying to develop every major subsystem from scratch. The X-BAT uses an existing fighter engine, applies an autonomy stack already demonstrated on the F-16 and unmanned aircraft, and uses a tail-sitter airframe that avoids the mechanical complexity of tiltrotors, rotating nacelles, or lift-fan propulsion.
The X-BAT is configured as a tail-sitter vertical takeoff and landing aircraft, meaning it launches vertically on the thrust of a single afterburning turbofan, then transitions into wing-borne forward flight once clear of the launch area. The X-BAT has a wingspan of 39 ft (equal to 11.9 m), a length of 26 ft (7.9 m), a maximum range of more than 2,000 nautical miles (3,700 km), with a service ceiling above 50,000 ft and a maneuver load factor greater than 4g. These figures place it well above small tactical UAVs in range, altitude, propulsion class, and intended mission set, while keeping it below manned fighter aircraft in size and maneuver requirements. The airframe design is therefore a compromise between combat maneuvering, endurance, structural mass, and vertical recovery requirements.
The propulsion arrangement is one of the key differentiators of the X-BAT. It uses an F110-GE-129 engine with the Axisymmetric Vectoring Exhaust Nozzle, or AVEN, which gives the aircraft the thrust-vectoring authority required for vertical launch, transition, and tail-first recovery. The F110 engine family already powers multiple F-16 and F-15 variants, making it a mature propulsion base rather than an experimental engine. The X-BAT does not use an F-35B-style lift-fan, which would add weight, volume, shafting, doors, and maintenance burden. It also does not use the V-22 Osprey’s tiltrotor arrangement, which requires rotating nacelles and large proprotors. Instead, it uses a single central propulsion line and a thrust-vectoring exhaust approach rooted in technologies explored through the F-15 ACTIVE and related U.S. flight-control programs.
This choice reduces the number of moving propulsion assemblies, but it also places higher demands on inlet design, flight-control software, thrust management, and recovery precision. The propulsion choice also explains why the proposed Polish engine center may be more achievable in the near term than an X-BAT manufacturing in the country. Poland already operates F-16C/D Block 52+ fighters and is receiving its first F-35A stealth fighters, giving it a growing combat aircraft sustainment requirement regardless of the X-BAT’s eventual production outcome. A Polish F110 maintenance hub would be relevant to existing European F-16 operators and to any future X-BAT fleet using the same engine family.
Sustainment work also tends to produce longer industrial continuity than final assembly, because engines require inspection, repair, overhaul, component replacement, testing, and life-cycle management across decades of service. A regional F110 support center in Poland could therefore become a practical industrial anchor even if the X-BAT manufacturing starts later, remains limited at first, or is divided among several countries. For NATO, such a center would also reduce dependence on longer supply chains and could shorten maintenance cycles for F110-powered aircraft based in Europe. The autonomy architecture is also central to X-BAT’s military relevance. The unmanned aircraft is built around Shield AI’s Hivemind software stack, which has already demonstrated an autonomous control capability on the F-16 and multiple unmanned systems.
Hivemind is designed for operation without continuous GPS access and for mission continuation during communications disruption. That matters because modern air operations increasingly occur under GNSS denial, datalink interference, electronic attack, and cyber-electromagnetic pressure. The war in Ukraine, Poland’s neighbour, has shown that navigation and communications cannot be assumed even for relatively short-range unmanned aircraft, and the problem is more severe for systems expected to penetrate defended airspace. The X-BAT is therefore not built around the assumption that a remote operator or manned aircraft will constantly control it by datalink. It can work with manned aircraft, but it is also intended to execute assigned missions independently when connectivity is interrupted.
This makes the X-BAT different from earlier UAV concepts that depended on continuous command links. In a permissive environment, a datalink allows retasking, human supervision, target updates, and coordination with manned aircraft. In a contested environment, that same dependency can become a vulnerability if jamming, terrain masking, emissions control, or cyber-electromagnetic activity interrupts the link. The X-BAT’s autonomy model is consequently intended to reduce that vulnerability by allowing the aircraft to continue under preloaded mission parameters and established rules when external control is degraded. This does not remove the requirement for mission planning, data loading, target validation, communications management, or human decision-making at the operational level.
It changes where those functions occur and reduces the assumption that constant pilot-like control must be maintained throughout the mission. On June 15, 2026, at Eurosatory, Shield AI also displayed a 45% scale model of a redesigned X-BAT configuration that had been unveiled at Sea-Air-Space 2026. The redesigned airframe abandoned the original cranked-kite planform and adopted a straight leading edge with greater sweep, producing a sharper arrowhead-shaped flying-wing configuration. This change is not cosmetic. A more swept, arrowhead-like flying-wing layout can support higher-speed flight regimes, cleaner aerodynamic efficiency, internal volume management, and radar-signature control more effectively than some less-refined planforms.
The revised shape moves the X-BAT closer in visual and aerodynamic logic to aircraft such as Boeing’s X-45C Phantom Ray and China’s GJ-11 Sharp Sword. It also suggests that the program is being shaped not only around vertical takeoff and landing, but also around range, survivability, internal carriage, and high-subsonic transit performance. The X-BAT also differs from the main Western Collaborative Combat Aircraft designs now racing for future fighter operations. Boeing’s MQ-28 Ghost Bat relies on conventional runway operations, which means it still depends on usable airfields, taxiways, maintenance aprons, fuel points, and base defense. General Atomics’ YFQ-42A also requires traditional airfield infrastructure, and Anduril’s YFQ-44A follows the same runway-dependent operating model.
Airbus’ U760 Ravenstorm remains in the concept phase and is expected to enter service in the early 2030s, while Helsing’s CA-1 Europa focuses heavily on electronic warfare and collaborative operations. Shield AI’s X-BAT is currently the only announced Western CCA-type aircraft combining jet propulsion, internal weapons bays, fighter-sized engine power, and runway independence. Its closest conceptual ancestor is therefore not another current CCA but the Ryan X-13 Vertijet, a Cold War tail-sitter experiment now being revisited through modern autonomy, flight-control computing, inlet modeling, and stealth shaping.
The rather unique launch and recovery concept is one of the most important parts of the aircraft because it determines whether runway independence is operationally useful or only a technical feature. The X-BAT is built around a mobile Launch and Recovery Vehicle, or LRV, rather than a runway-based operating model. The aircraft is transported folded or stowed on the vehicle, which acts as the ground handling system, launch point, recovery point, and storage interface. For launch, the vehicle raises the aircraft into a vertical attitude, after which the single F110-GE-129 afterburning turbofan lifts it from the vehicle. The X-BAT then climbs vertically, clears the launch area, and transitions into forward wing-borne flight.
This sequence removes the need for a runway, but it still requires a launch area with sufficient clearance, fuel supply, weapons handling capacity, communications access, maintenance support, and security. Recovery is more demanding than launch, as the X-BAT returns in conventional forward flight and approaches the LRV before executing a high-angle-of-attack transition comparable to a cobra maneuver. It rotates from horizontal flight into a near-vertical attitude, stabilizes under thrust-vector control, descends tail-first, and lands on the recovery vehicle. The maneuver requires the inlet to keep feeding the engine while the aircraft moves from 0° to 90° angle of attack, a condition that can disrupt airflow if the inlet is not shaped and positioned correctly.
Shield AI’s work on this phase required extensive computational fluid dynamics analysis, wind-tunnel testing, and inlet design work. Unlike the Ryan X-13 Vertijet, where the pilot had to conduct a difficult tail-first recovery, the X-BAT performs the maneuver autonomously using flight control algorithms derived partly from the company’s V-BAT vertical takeoff and landing experience. The aircraft, therefore, does not require a runway, arresting cable, catapult, or conventional landing gear sequence for recovery. The storage and deployment metrics further show how Shield AI intends the X-BAT to be used in distributed operations. The storage figure is 40 ft × 14 ft × 6 ft, and the stated expeditionary footprint is 3:1, meaning that three X-BATs can fit in roughly the deck space of one legacy fighter. That matters for land and maritime deployment.
On land, the aircraft could be dispersed across roads, port areas, logistics compounds, remote islands, and austere operating locations. At sea, the same concept could apply to ship decks with sufficient clearance and support equipment. The aircraft’s vertical launch and recovery profile expands the number of possible operating locations, but it does not eliminate the logistical chain. Fuel trucks, weapons loading equipment, engine support, mission-data loading, recovery alignment, vehicle concealment, spare parts, and personnel protection become the critical limiting factors. Like the Gripen, the target set shifts from fixed runways and hardened shelters to mobile launch points and their support nodes. For NATO’s eastern flank, this operational logic is directly tied to survivability. A runway-independent aircraft like the X-BAT does not make air operations immune to attack, but it complicates adversary targeting by increasing the number of possible launch locations and reducing dependence on a small number of known air bases.
Moreover, the X-BAT’s range of more than 2,000 nautical miles also allows launch sites to be moved deeper into friendly territory or farther from immediate missile threat areas. This aligns with NATO’s Agile Combat Employment logic, which emphasizes dispersal, mobility, rapid relocation, and the ability to continue air operations after attacks on main operating bases. For Poland, the relevance is particularly high because its geography places key military infrastructure within reach of Russian and Belarusian missile systems, as well as long-range air-launched weapons. A mobile LRV-based fighter aircraft could support operations from a larger number of sites, including road networks, coastal areas, temporary operating locations, logistics hubs, and potentially maritime decks.
Poland’s potential gains from the dual proposal from Shield AI are therefore industrial, operational, and technological. Early access to the X-BAT and the GCAP would give Poland involvement in two next-generation combat aircraft programs before serial production begins, rather than after the design is already fixed and the industrial roles have already been allocated. Manufacturing participation would be more significant than a maintenance-only role, especially if Polish companies gain workshare in airframe structures, ground vehicles, support equipment, engine-related sustainment, mission systems integration, or component production.
Involvement in a software-intensive combat aircraft program like the X-BAT would also expose Poland’s aerospace and defense sector to autonomy, mission planning, human-machine teaming, electronic warfare resilience, and distributed operations. These areas are increasingly relevant to sixth-generation combat aircraft development, including the GCAP, which Poland is evaluating as part of its future combat aviation policy. For now, the engine center component may be the most concrete part of the proposal because it is based on an existing need. European F-16 fleets will continue to require F110 sustainment, and Poland’s own F-16C/D Block 52+ fleet already provides a domestic foundation for such work. A regional facility would create skilled maintenance activity, test-cell requirements, parts flows, inspection capacity, and engineering work that can remain active regardless of the pace of the X-BAT development.
Written by Jérôme Brahy
Jérôme Brahy is a defense analyst and documentalist at Army Recognition. He specializes in naval modernization, aviation, drones, armored vehicles, and artillery, with a focus on strategic developments in the United States, China, Ukraine, Russia, Türkiye, and Belgium. His analyses go beyond the facts, providing context, identifying key actors, and explaining why defense news matters on a global scale.
Explore More Defense News
• Land Defense News
• Naval Defense News
• Defense Aerospace News
