Risks & Potentials

Risks and potentials

This Learn page is part of an engineering-hypothesis discussion — not a safety case or a claim that residual risk is zero. Design intent is outlined under Why?. Component maturity is on the technology TRL tables.

Comparing reactor safety: thermal vs fast

It is useful to distinguish risks typical of pressurized light-water fleets from those of a sodium fast reactor of the kind ReCore explores.

Risk factor	Typical large LWR	ReCore-class SFR concept (intent)
Coolant pressure	High (~150 bar class)	Near atmospheric (~1 bar)
Coolant state	Pressurized water (can flash to steam)	Liquid metal (large margin to boil)
Boiling / LOCA character	Pressure-driven flash, complex emergency cooling	Different; Na stays liquid over a large ΔT if inventory is retained
Zr–water H₂ production	Relevant in severe accidents with water + hot Zr	No primary water; no that specific H₂ path
Decay heat removal	Active systems important historically	Passive natural circulation is a design intent

Understanding the differences

Loss of coolant (LWR vs low-pressure Na): In a high-pressure LWR, a break can flash coolant and challenge core cooling. In a near-atmospheric sodium vessel, liquid Na does not flash the same way; cooling still depends on inventory, natural circulation, and engineered barriers — not “automatic safety.”
Hydrogen from Zr–water: LWRs can produce H₂ from zirconium–steam reactions. A sodium primary system without water removes that particular mechanism; other hydrogen or chemical hazards (e.g. Na fires) can still exist.
Sodium chemistry: Sodium reacts with air and water. ReCore uses a nitrogen power cycle so that Na–H₂O at the steam generator is not the design driver. That does not eliminate all sodium chemical risk. Isolation of high-pressure N₂ from the primary is intended via single-wall Alloy 709 tubes plus acoustic leak detection, fast module isolation / blowdown, and cover-gas relief, not by deleting every intermediate function. A circulating secondary-Na loop remains a licensing fallback. See ReCore-Reactor and ReCore-Power.

Potentials: closed cycle and firm power

Once-through LWR fuel leaves actinides that dominate radiotoxicity for on the order of 300000 years, while using only a small fraction of uranium’s energy potential. Multi-recycle of transuranics in a fast reactor aims to reduce the long-term radiotoxic inventory requiring isolation, leaving residual waste more dominated by fission products (literature often discusses order-of 500 years in simplified comparisons) — a fuel-cycle goal, not a guaranteed single-plant outcome.

Civilian plutonium and depleted uranium can become start-up and fertile feed after processing, rather than pure storage liabilities. Burning actinides and using fertile U-238 can multiply energy extracted per tonne of natural uranium relative to once-through LWR use — over a multi-recycle fleet path, not from one burnup cycle alone.

On the grid, a modular SFR with a closed Brayton plant is potentially well suited to dispatchable low-carbon power and flexible operation with high renewable shares — if control, economics, and coupling are demonstrated.

Global SFR foundation

Sodium fast reactors are not speculative physics. Industrial and experimental heritage includes:

Russia (BN-600 & BN-800): multi-decade grid-connected SFR operation
USA (EBR-II): metal fuel and inherent-safety demonstrations
France (Phénix & Superphénix): extensive SFR operating and R&D history
China & India: active SFR programmes

Risks and intended mitigations

Historical risks are real; mitigations below are design intents, not completed proofs.

Risk	Intended mitigation direction
Proliferation	Process co-recovery of Pu with other actinides (e.g. LCC); still requires formal safeguards and accountancy
Core damage / overpower	Metallic fuel negative temperature feedbacks assist safety; engineered shutdown and DHR remain essential — not “impossible to melt”
Sodium fires	Compact inventory order of 60 m³ (~62.6 m³ analytical — not “below 50”); inert cover gas; explore removing Na–water at the power island; fire/leak design still required
Emergency planning zone	EPZ size is a regulatory outcome, not a design deliverable; “site-boundary EPZ” is not claimed as achieved
Waste legacy	Multi-recycle of TRU is intended to cut long-term actinide burden; no hard burnup fraction or automatic century-horizon guarantee

Comparison with past designs

Historical accidents inform design intent. ReCore does not claim those failure modes are “engineered out forever.”

Chernobyl

The RBMK design combined graphite moderation with a positive void coefficient that increased power as coolant boiled.

Concept direction: sodium coolant (no graphite moderator of that type), design intent for negative void coefficient and strong negative temperature feedbacks, plus engineered systems and containment appropriate to licensing.

Fukushima

Station blackout challenged active decay-heat removal; zirconium–steam reactions produced hydrogen.

Concept direction: passive DHR as design intent (natural circulation without AC power); no primary water → no that Zr–steam H₂ path. Passive systems still need analysis, testing, and regulatory acceptance.

Sodium accidents (Monju & Fermi 1)

Monju (secondary Na leak / fire): A leak in a secondary sodium system was a major event.
- Concept direction: Na→N₂ on external single-wall Alloy 709 heaters. An 80 bar tube break is intended to be caught by acoustic leak detection, isolated at the module headers, and vented through a directional shroud into the argon cover-gas plenum (burst discs + cyclone), not absorbed by a helium-watched second wall. A circulating intermediate-Na loop is a fallback, not the FOAK baseline. Primary Na still needs leak detection, inventory control (order of 60 m³ class, ~62.6 m³ analytical), cover gas, and fire mitigation.
Fermi 1 (flow blockage): Loose debris contributed to local cooling failure.
- Concept direction: minimise unnecessary in-vessel debris sources; rely on metallic fuel conductivity and negative feedback for localized anomalies — still requires thermal-hydraulics design and QA.

On this page