VALAR WATCH
Key findingsTheir claims, annotatedEvidenceTake action
374 facts · 512 sources · updated 2026-09-30

Fact plan-009

newrecordreported Valar's dates clash: 'full power June 21' in the state's lease memo, yet on June 22 it announced 10 kWt of 100
2026-09-17 · plan-009 · Valar Atomics, Utah Trust Lands Administration, American Nuclear Society, Harry Hansen

The Trust Lands staff memo for the 17 September 2026 board meeting, in its 'Applicant' background section, states that Ward 250 'reached full power operations on June 21, 2026' and generated electricity on 1 July. The memo does not say who supplied the date; the next paragraph says 'The applicant represents' what its DOE approvals show. ANS reported on 22 June 2026 that Valar 'is now proceeding with a planned power ascension' and announced that day an output of 10 kWt, a tenth of the reactor's 100 kWt rating. If the reactor was at full power on 21 June, a 22 June announcement of 10 kWt with power ascension still under way does not fit: either the 21 June date is wrong or the 22 June announcement described an earlier step, and no public record says which. On 24 June Valar's Harry Hansen told Price's council the reactor had gone to full power 'shortly after' going critical (plan-006). The memo also says Valar holds a DOE 'Certificate of Readiness' and has 'brought and sustained that reactor through an initial testing campaign'; no such certificate has been published (safe-007, gov-037). The board had these statements in its packet when it approved the lease on 17 September (mine-011, mine-016).

In plain termsTwo things Valar has said, a day apart, do not line up. The state's lease memo says the reactor hit full power on June 21. But on June 22 Valar announced the reactor had reached 10 kilowatts, one tenth of full power, and a nuclear trade journal reported it was still stepping the power up. This does not show that anything unsafe happened. It shows that a date the state had in front of it when it voted cannot be squared with the company's own announcement, and there is no public logbook to settle it.
verified 2026-09-29: Verify pass 2026-09-29: memo (packet pp. 18-19) and ANS re-read. Fixed: the memo does not attribute the June 21 date to Valar; 'first step' is not ANS's wording. Downgraded to 'reported': the June 22 side rests on one report (ANS) of a Valar post we could not read (x.com answered 402). Vote reference corrected to mine-011 (the approval) as well as mine-016.

In tabs: operations, timeline, carbon_site, process · file plans_ops