ML20209G103
| ML20209G103 | |
| Person / Time | |
|---|---|
| Site: | Fermi  |
| Issue date: | 08/20/1985 |
| From: | Holahan G Office of Nuclear Reactor Regulation |
| To: | Rossi C NRC OFFICE OF INSPECTION & ENFORCEMENT (IE) |
| Shared Package | |
| ML20209B956 | List: |
| References | |
| FOIA-86-729 NUDOCS 8508220387 | |
| Download: ML20209G103 (2) | |
Text
-
o j#"44sg
~9 #
g,
,o, UNITED STATES T ((
,,,s g ', 3 5- ( (,g NUCLEAR REGULATORY COMMISSION
.-\\
C
' t' br? l /:$
WASHINGTON, D. C. 20s55 e
%i.'.O /
/) -t's - n.,,.
AUG 2 01985 7" ?
(bf,.
gL C
MEMORANDUM FOR:
Charles E. Rossi, Chief
(
Events Analysis Branch, DEPER
/. - s.,,
FROM:
Gary M. Holahan, Chief Operating Reactors Assessment Branch, DL i
SUBJECT:
REPORTABILITY OF INADVERTENT CRITICALITY AT FERMI 2 Fermi 2 experienced an inadvertent criticality on July 2, 1985.
The NRC, both Region III and headquarters, was not notified of this event by the licensee until July 15, 1985. Apparently, an inadvertent criticality is not a promptly reportable event under current 10 CFR 50.72 reporting requirements.
The NRC views an inadvertent criticality very seriously. An inadvertent criticality is reportable to Congress as an abnormal occurrence (A0) even if no exposure, injury, or damage occurs.
In addition, 10 CFR 2 Appendix C identifies an inadvertent criticality as a Severity Level I event for enforcement.
Due to the serious nature of the event, I suggest that EAB consider adding inadvertent criticality to the list of prompt reportable events in your forthcoming 10 CFR 50.72 revision effort.
fN Gary H 1'ahan, Chief Operating Reactors Assessment Branch, DL cc:
E. Weiss CONTACT:
W. Swenson, NRR j
X27876 l
f Io g'!
, <[Q j M h' '
l MI tu l