Nuclear Security & Deterrence Monitor Vol. 27 No. 20
Visit Archives | Return to Issue
PDF
Morning Briefing
Article of 6
March 17, 2014

GAO LAUNCHES INVESTIGATION INTO DOE SUPPORT OF USEC

By ExchangeMonitor

The Government Accountability Office earlier this month launched its investigation into the Department of Energy’s support for USEC in response to a request last June by Reps. Ed Markey (D-Mass.) and Michael Burgess (R-Texas). The GAO is still in the planning phase of the effort and is determining the scope and schedule moving forward, but has had initial meetings with DOE and USEC officials. The Department is currently supporting USEC’s American Centrifuge enrichment technology through a research, development and deployment cost-share program launched last June, using as a justification the need for a domestic source of low enriched uranium for tritium production. 

The same week the cost-share program began, Markey and Burgess sent a detailed letter to the GAO questioning numerous aspects of the Department’s effort and requesting an investigation. “The Department of Energy’s assertion that continuing to bail out USEC is the only way the U.S. can get the tritium needed for America’s nuclear weapons program appears to be untrue,” states a release at the time from Markey’s office. It also raised concern regarding a DOE-brokered uranium tails reenrichment program at the Paducah Gaseous Diffusion Plant operated by USEC. “The Department’s recent uranium transfer announcement may violate the USEC Privatization Act and may additionally not include adequate safeguards,” the release states.

Print
0
46

false
false
false

MicrosoftInternetExplorer4

st1:*{behavior:url(#ieooui) }

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:”Table Normal”;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:””;
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:”Times New Roman”;
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}

Comments are closed.