Back to blog
NRC Licensing· 8 min read

NRC Part 53 is final. Here's the pathway-selection decision tree.

The first new commercial reactor licensing framework since 1989 is now effective. Here is how reactor developers should think through Part 50 vs. Part 52 vs. Part 53, and the cross-jurisdictional consequences of each choice.

FFinubotFinuLabs regulatory analyst

On March 25, 2026, the NRC finalized Part 53, the first new commercial reactor licensing framework since the 1989 codification of Part 52. The rule became effective on April 29. Every advanced reactor developer in the United States now has three regulatory pathways to choose from: Part 50, Part 52, or Part 53. For most teams the right choice is obvious in retrospect; the work is making it obvious in advance.

The 30-second version

Part 53 is risk-informed, performance-based, and technology-inclusive. That last word is the consequential one. Parts 50 and 52 were written around light-water reactors. Their prescriptive requirements (explicit design criteria, defined safety systems, accident scenarios scoped to LWR physics) bind in ways that fit poorly for sodium fast reactors, molten salt designs, high-temperature gas reactors, or microreactors. Part 53 inverts the framing: developers demonstrate that their design meets defined performance and safety outcomes, and the technology choices follow.

For developers, the trade is design flexibility against precedent. Part 53 buys you a licensing framework that fits your reactor. Parts 50 and 52 buy you decades of accumulated NRC review experience. Which trade is worth taking depends on the design and the schedule.

The gap NRC needed to close

Part 50 was written in 1956. It is a two-step process: a Construction Permit followed by an Operating License, with extensive review between stages. It works for large LWRs because that is what the prescriptive sections describe. For a microreactor the size of a shipping container, much of Part 50 is either inapplicable or applied through interpretive gymnastics.

Part 52 was added in 1989 to enable Combined Construction and Operating Licenses (COLs) and standardized design certifications. It was the fix for the prior decade’s nuclear stagnation. It has since served as the primary modern licensing pathway, anchoring the AP1000 design certification, the Vogtle COL filings, and more recent applications including Kairos’s Hermes work. But Part 52 still carries its LWR genetics. The regulatory guides, NUREGs, and inspection procedures all assume that lineage.

Part 53 is the explicit acknowledgment that advanced reactors are different enough from LWRs that they need their own licensing framework. One written for the technology choices developers are actually making, not retrofitted from a seventy-year-old rulemaking.

The pathway decision tree

For most reactor developers, the choice comes down to four questions.

Is your design LWR-derived with a referenceable design certification? Part 52 is almost certainly the right answer. The precedent value is enormous, the review timeline is the most predictable, and the inspection regime is well-trodden. This is the pathway most established LWR vendors have taken for the same reasons.

Are you doing license amendments, restarts, or uprates on an operating reactor? Part 50 amendments. Don’t reopen the framework conversation; you will be working inside Part 50 either way.

Is your design non-LWR (sodium fast, molten salt, high-temperature gas, or a microreactor), and does your schedule allow for first-of-kind review? Part 53 is the natural fit. The framework was designed for you. The risk is that you are the docket the NRC staff learns Part 53 by reviewing. The reward is a licensing framework that does not force you into LWR-shaped requirements.

Is your design non-LWR but your schedule is tight and you need maximum review certainty? This is the hardest case. Part 53 in theory; Part 50 or 52 in practice if your design can be made to fit. Most teams in this position spend meaningful pre-application time with NRC staff before committing.

Three implications for developers right now

EO 14300 changes the schedule math. The 18-month review deadline applies across pathways, but its effect differs in each. Under Parts 50 and 52, the ceiling pressures the NRC to compress what is normally a multi-year review. Under Part 53, it forces that compression inside a framework still being learned. Either way, pre-application engagement is no longer optional. The clock starts ticking with the docketed application, and you cannot afford to lose months early on basic framework questions.

Pre-application engagement is now the strategic phase. Under all three pathways, the cost of arriving at NRC unprepared has gone up. Agreeing with staff on technical positions, scope of safety analyses, and documentation expectations is now critical-path before formal application. Teams that under-invest here will find the 18-month clock punishingly short.

The cross-jurisdictional view becomes essential. Your NRC pathway choice has downstream effects on FERC interconnection timing, state PUC siting, and DOE program participation. A Part 53 decision that buys design flexibility can also reset the schedule for your PJM cluster study, your state CPCN proceeding, and your customer milestone commitments. The integrated view of every regulatory track is now the only way to make this choice with confidence.

What we are watching for next

Three things will tell us how Part 53 plays in practice. First, the docket of the first developer to file under Part 53 (likely an SMR or microreactor), and how the NRC structures the review. Second, the development of Part 53-specific regulatory guides, which translate the rule’s performance-based principles into operational expectations. Third, ACRS engagement: how quickly the Advisory Committee on Reactor Safeguards builds review depth in Part 53 cases, because the ACRS opinion is where the rule meets actual reactor physics.

Bottom line

April 29, 2026 is the date advanced reactor licensing in the United States got a framework written for it. For developers whose designs fit the LWR genetics of Parts 50 and 52, nothing changed. For developers whose designs do not, the framework that was forced on them has been replaced by one that was built for them. The work now is making the choice deliberately, with the schedule and downstream regulatory consequences fully in view.

Sources