Browse wiki
Jump to navigation
Jump to search
At 0813 CDT on 04/12/2006, the Plant Shift … At 0813 CDT on 04/12/2006, the Plant Shift Superintendent (PSS) was notified that immediately following routine test firing of the C-333 Unit 4 cell 7 UF6 Release Detection System (TSR surveillance requirement 2.4.4.1-1), smoke and sparks were observed coming from the UF6 Release Detection System control module and the system ready light was extinguished. The Area Control Room alarm locked in and the system was declared inoperable by the PSS. The cell and associated piping were above atmospheric pressure (Cascade Mode 2) at the time of the failure. </br>The UF6 Release Detection System is a TSR system that is required to be operable per TSR 2.4.4.1, when a cascade cell and associated piping are in Cascade Mode 2. After discovery of failed system condition, a continuous UF6 smoke watch was initiated on the areas affected by the loss of detection capability in accordance with LCO Required Actions 2.4.4.1.B.1 and 2.4.4.C.1.</br>This event is reportable as a 24 hour event in accordance with 10CFR 76.120(c)(2)(i). This is an event in which equipment is disabled or fails to function as designed when: </br>a.) the equipment is required by a TSR to prevent releases, prevent exposures to radiation and radioactive materials exceeding specified limits, mitigate the consequences of an accident, or restore this facility to a pre-established safe condition after an accident; </br>b.) the equipment is required by a TSR to be available and operable and either should have been operating or should have operated on demand, and </br>c.) no redundant equipment is available and operable to perform the required safety function.</br>The NRC Senior Resident Inspector has been notified of this event.</br>PGDP Problem Report No. ATRC-06-1197; PGDP Event Report No. PAD-2006-03.</br>There was no release from this event. The failure was shorted contacts in the alarm reset relay.</br>* * * UPDATE FROM WALLACE TO KNOKE AT 19:04 EDT on 04/18/06 * * * </br>This report is being retracted. Subsequent to the event, Maintenance and System Engineering determined that the alarm disable switch control module faulted when the operator attempted to reset the ACR PGLD alarm. This fault caused the system power supply to fail. Resetting the alarms is the last step in the test procedure being performed when the failure occurred. Only after the alarms are cleared is the PGLD system returned to normal operating condition and testing complete. In this case, the evidence clearly indicated that the failure occurred during the conduct of the surveillance and the successful firing of the detectors and the start of the test provides positive evidence that the failure did not exist prior to the surveillance. Therefore, the in-service safety system failure reporting criteria of 10CFR 76.120(c)(2)(i) is not applicable. </br>The Senior Resident Inspector has been notified of this retraction.</br>Notified R2DO(Lesser) and NMSS (Janosko).
Notified R2DO(Lesser) and NMSS (Janosko).
13:13:00, 12 April 2006 +
42,494 +
17:30:00, 12 April 2006 +
13:13:00, 12 April 2006 +
At 0813 CDT on 04/12/2006, the Plant Shift … At 0813 CDT on 04/12/2006, the Plant Shift Superintendent (PSS) was notified that immediately following routine test firing of the C-333 Unit 4 cell 7 UF6 Release Detection System (TSR surveillance requirement 2.4.4.1-1), smoke and sparks were observed coming from the UF6 Release Detection System control module and the system ready light was extinguished. The Area Control Room alarm locked in and the system was declared inoperable by the PSS. The cell and associated piping were above atmospheric pressure (Cascade Mode 2) at the time of the failure. </br>The UF6 Release Detection System is a TSR system that is required to be operable per TSR 2.4.4.1, when a cascade cell and associated piping are in Cascade Mode 2. After discovery of failed system condition, a continuous UF6 smoke watch was initiated on the areas affected by the loss of detection capability in accordance with LCO Required Actions 2.4.4.1.B.1 and 2.4.4.C.1.</br>This event is reportable as a 24 hour event in accordance with 10CFR 76.120(c)(2)(i). This is an event in which equipment is disabled or fails to function as designed when: </br>a.) the equipment is required by a TSR to prevent releases, prevent exposures to radiation and radioactive materials exceeding specified limits, mitigate the consequences of an accident, or restore this facility to a pre-established safe condition after an accident; </br>b.) the equipment is required by a TSR to be available and operable and either should have been operating or should have operated on demand, and </br>c.) no redundant equipment is available and operable to perform the required safety function.</br>The NRC Senior Resident Inspector has been notified of this event.</br>PGDP Problem Report No. ATRC-06-1197; PGDP Event Report No. PAD-2006-03.</br>There was no release from this event. The failure was shorted contacts in the alarm reset relay.</br>* * * UPDATE FROM WALLACE TO KNOKE AT 19:04 EDT on 04/18/06 * * * </br>This report is being retracted. Subsequent to the event, Maintenance and System Engineering determined that the alarm disable switch control module faulted when the operator attempted to reset the ACR PGLD alarm. This fault caused the system power supply to fail. Resetting the alarms is the last step in the test procedure being performed when the failure occurred. Only after the alarms are cleared is the PGLD system returned to normal operating condition and testing complete. In this case, the evidence clearly indicated that the failure occurred during the conduct of the surveillance and the successful firing of the detectors and the start of the test provides positive evidence that the failure did not exist prior to the surveillance. Therefore, the in-service safety system failure reporting criteria of 10CFR 76.120(c)(2)(i) is not applicable. </br>The Senior Resident Inspector has been notified of this retraction.</br>Notified R2DO(Lesser) and NMSS (Janosko).
Notified R2DO(Lesser) and NMSS (Janosko).
Has query"Has query" is a predefined property that represents meta information (in form of a <a rel="nofollow" class="external text" href="https://www.semantic-mediawiki.org/wiki/Subobject">subobject</a>) about individual queries and is provided by <a rel="nofollow" class="external text" href="https://www.semantic-mediawiki.org/wiki/Help:Special_properties">Semantic MediaWiki</a>.
00:00:00, 18 April 2006 +
GDP-1 +
Modification date"Modification date" is a predefined property that corresponds to the date of the last modification of a subject and is provided by <a rel="nofollow" class="external text" href="https://www.semantic-mediawiki.org/wiki/Help:Special_properties">Semantic MediaWiki</a>.
23:35:29, 24 November 2018 +
17:30:00, 12 April 2006 +
0.178 d (4.28 hours, 0.0255 weeks, 0.00586 months) +
13:13:00, 12 April 2006 +
URL"URL" is a <a href="/Special:Types/URL" title="Special:Types/URL">type</a> and predefined property provided by <a rel="nofollow" class="external text" href="https://www.semantic-mediawiki.org/wiki/Help:Special_properties">Semantic MediaWiki</a> to represent URI/URL values.