securitylab_n•July 12, 2026•🇷🇺Translated from Russian

Europe Unveils RLV C5 Reusable Rocket Concept as a Potential Competitor to SpaceX Starship

The first full-scale launch of Starship in April 2023 ended in an explosion, yet it successfully demonstrated that the massive integrated vehicle could lift off. Eighteen months later, SpaceX returned the Super Heavy booster to the launch site and caught it with the mechanical arms of the launch tower. After the fifth test flight, discussions about a fully reusable super-heavy launch system no longer seemed like distant engineering fantasy.

Starship is designed to deliver more than 100 tons to low Earth orbit while returning both stages for rapid reuse. Although SpaceX has not yet reached the advertised performance figures and continues iterative development, the sheer scale of the project is forcing other nations to reassess their own rocket programs. The question is shifting from whether Starship will transform the space industry to what the appropriate competitive response should be.

An independent assessment of the American rocket’s capabilities was conducted by the German Aerospace Center (DLR). Researchers avoided relying solely on published SpaceX specifications and instead reconstructed flight parameters from publicly available video footage of the first four integrated flight tests.

Specialists extracted telemetry data from the broadcasts and analyzed the vehicle’s motion on a second-by-second basis. Velocity, altitude, acceleration, and other available parameters formed the foundation of a dedicated simulation model. The results were then compared against actual flights to validate how accurately the model represented booster and ship performance.

The calculations showed that the current fully reusable version of Starship could theoretically deliver approximately 59 tons to low Earth orbit. This figure is close to the capability of Falcon Heavy in expendable mode when side boosters and the center core are not recovered.

The number is noticeably lower than the frequently cited 100-ton target, but it applies to an early configuration that has already flown. SpaceX is progressively increasing propellant capacity, upgrading to Raptor 3 engines, and refining the heat shield. Consequently, future variants are expected to deliver substantially higher performance than the initial prototypes.

The next-generation Starship will feature enlarged propellant tanks and higher-thrust Raptor 3 engines. According to the DLR model, a fully reusable system could lift around 115 tons to low Earth orbit, while an expendable configuration could reach 188 tons.

In expendable mode, the new Starship would surpass Saturn V, which sent American crews to the Moon. However, such comparisons reveal only one aspect of the design. SpaceX’s primary bet lies not in a single massive payload but in rapid reuse of both booster and ship.

Full reusability makes Starship extremely heavy. The vehicle requires heat-shield tiles, extra propellant for landing burns, a reinforced structure, and systems rated for multiple flights. Each of these elements reduces the mass available for payload compared with an expendable architecture.

In the same DLR study, researchers proposed a European alternative named RLV C5. The concept also belongs to the super-heavy class but does not attempt to recover the entire vehicle. Only the winged booster is designed for reuse; the upper stage remains expendable.

The booster design draws on work from the SpaceLiner program, which has studied hypersonic passenger vehicles in Europe for many years. RLV C5 inherits the winged shape and horizontal atmospheric return, although the vehicle will not perform a conventional runway landing.

After atmospheric entry, the booster will transition to gliding flight and rendezvous with a large subsonic aircraft. The aircraft will capture the booster in flight and tow it to a landing site. While this recovery method exists only in simulations, it eliminates the need for landing engines and reserve propellant.

Starship solves the same problem differently. Super Heavy flips after stage separation, reignites engines, returns to the launch site, and is caught by tower arms. The ship also performs a vertical landing after re-entry.

The European concept uses liquid hydrogen and liquid oxygen, whereas Starship burns methane and oxygen. Hydrogen provides higher specific impulse, allowing more efficient use of propellant mass. Methane is easier to store and its higher density reduces tank size; SpaceX also plans to produce methane on Mars from local resources.

These differing choices become evident when comparing vehicle mass. Starship will weigh more than three times as much as RLV C5 at liftoff. The American system carries equipment to recover both stages and is sized for significantly heavier payloads. The European rocket sacrifices the upper stage but achieves better mass efficiency as a result.

According to DLR calculations, payload constitutes roughly 40 percent of the total mass Starship delivers to orbit; the remainder is structure, return propellant, and reusability hardware. For RLV C5, the payload fraction could reach 74 percent because the expendable upper stage requires no heat shield or landing systems.

These percentages do not imply that the European rocket will exceed Starship in absolute payload capacity. The American vehicle is far larger and will lift many more tons per launch. RLV C5 offers a more economical payload-to-structure ratio rather than maximum throw mass.

The two vehicles target different missions. Starship is being developed for large-scale lunar expeditions, Mars flights, delivery of oversized modules, and rapid satellite constellation deployment. Its enormous internal volume can accommodate payloads that exceed the fairing dimensions of current launchers.

RLV C5 aims to give Europe independent access to super-heavy lift without immediately developing a fully reusable system. The concept leverages existing SpaceLiner research and could serve as an intermediate step toward a future European vehicle with full reusability.

Nevertheless, the comparison remains unequal. Starship is already undergoing flight testing, with engineers validating engines, heat shields, stage separation, and booster recovery on actual hardware. RLV C5 exists only as a paper design. Realizing a prototype would require a dedicated European program, substantial funding, and years of development to master mid-air capture of a heavy booster.

Starship itself is still far from routine operations. During the fourth flight, the ship sustained significant heat-shield damage, particularly near the forward flap. The vehicle survived re-entry and achieved a controlled splashdown, yet SpaceX had to redesign the thermal protection system.

The economics of the project depend not only on recovering stages but on reusing them without lengthy repairs or extensive post-flight inspections. If refurbishment proves costly and slow, the promised reduction in launch cost will be far more modest.

SpaceX currently holds an advantage not only in vehicle performance but also in accumulated real-world flight experience. The European concept illustrates an alternative technical path, yet only a completed rocket can validate the calculations. Until then, RLV C5 will remain on paper while American engineers continue testing their solutions in flight and advancing at an accelerated pace.

Related articles

Securitylab•Other

Inside the Fortress: Why Perimeter Security Tools Fall Short and How Microsegmentation Protects Networks Internally

Companies invest heavily in perimeter defenses such as firewalls and intrusion detection systems, yet these measures no longer guarantee safety as attackers increasingly operate from within networks. Traditional L2 domains leave virtual machines unisolated, enabling traffic interception, lateral movement, and malware spread similar to an apartment building with poor soundproofing. Microsegmentation powered by SDN divides VLANs into isolated microsegments down to individual VM ports, enforcing granular policies based on ports, IP addresses, and protocols. This approach implements Zero Trust by placing virtual packet filters directly at VM network interfaces on the hypervisor, independent of guest OS actions. Performance remains high because filtering runs on powerful virtualization servers, and scaling occurs naturally as additional hypervisors absorb new workloads without extra configuration. A real-world case from the oil and gas sector shows one customer creating up to 5,000 new microsegmentation rules per week via open REST API. The technology complements rather than replaces perimeter firewalls, delivering both strict internal controls and operational agility.

Habr•Other

Good Bear 1.0 Released: Firefox-Based Browser with Isolated Russian PKI Trust Container

Good Bear 1.0 is a Russian-language browser built on Firefox 156.0 that provides an isolated container for handling Russian PKI certificates without mixing trust contexts or user data with the standard browsing session. The release includes .deb packages for Ubuntu 24.04 LTS amd64 and Windows x64 installers, using Mozilla Public License 2.0 and reproducible build processes from pinned Firefox sources. Instead of globally importing root certificates, the browser performs secondary chain validation only inside a dedicated userContextId container with strict OriginAttributes isolation for caches, storage, and connections. Password autofill and sensitive session data are disabled in the container when separation cannot be guaranteed, and POST requests trigger explicit user choice before reopening in the isolated context. The interface shows both a persistent container marker and a separate RU indicator only when Russian PKI is actively used, along with detailed security panels explaining the trust source. Updates, crash reporting, and automatic MAR mechanisms are intentionally omitted to avoid creating unverified trust chains for the distribution itself.

Habr•Other

Survey of 254 Russian Domains Shows 89% DMARC Adoption but Highlights Gaps in Reporting and Subdomain Policies

A manual review of public DNS records across 254 prominent Russian domains from 17 sectors found strong baseline adoption of email authentication mechanisms. MX records appeared in 96.1% of domains, SPF in 93.7%, DMARC in 89.0%, and DKIM records via common selectors in 62.2%. Among domains with DMARC, 40.7% published a reject policy and 42.9% used quarantine, while 16.4% remained at none. Notably, 19% of DMARC-enabled domains lacked any rua address for aggregate reports, including 33 domains enforcing reject or quarantine. The study also identified cases of inconsistent policies between parent domains and subdomains, as well as SPF records ending in ~all paired with strict DMARC settings. Researchers emphasized that DNS data alone cannot confirm actual mail flow alignment or report consumption.

AntiMalware•Other

Server Outage Halts Vehicle Registration Across Smolensk Region

A technical failure on a unified server has temporarily suspended vehicle registration services in the Smolensk region of Russia. The outage affects the interdistrict traffic police department No.1 located on Lavochkina street, preventing new registrations from being processed. Regional UMVD officials confirmed that the problem impacts the single server used for the entire oblast's registration system. According to department head Maxim Zykov, the disruption is considered temporary, though no precise restoration timeline was provided. Applicants who submitted requests through the Gosuslugi portal will receive services in the first working days after the system is restored. The UMVD plans to issue an additional announcement once operations resume.