Browse wiki
Jump to navigation
Jump to search
On June 9, 2014, at 5:35 pm, Exelon observ … On June 9, 2014, at 5:35 pm, Exelon observed that the 2A EDG field flash monitoring relay alarmed in the main control room. Initial investigation by Exelon incorrectly concluded that this alarm was caused by an alarm card problem and that the operability of the EDG was not impacted. On June 11, 2014, at 10:35 am, subsequent investigation by Exelon determined that the alarm was caused by a loose fuse clip which would have prevented the flashing of the 2A EDG generator field thus rendering the 2A EDG inoperable. Repairs were made, post-maintenance testing was completed, and the 2A EDG was declared operable on June 11, 2014, at 4:32 pm. An ACE concluded that the operations staff incorrectly determined that the 2A EDG was operable based on the available indications without determining the cause of the alarm. The 2A EDG was inoperable for 46 hours and 57 minutes which is a condition that required entry into TS LCO 3.8.1.B for one EDG inoperable. TS LCO 3.8.1.B requires five actions with required completion times ranging from 1 hour to 14 days. Four of these require</br>actions were not performed within the required completion time thus TS Condition 3.8.1.J should have been entered which required the unit to be placed in Mode 3 within 6 hours and Mode 5 within 36 hours from entry into the condition. Neither action of TS LCO 3.8.1.J was taken within the required time, therefore, the condition existed for a time longer than allowed by TS. The inspectors reviewed Exelons ACE and other related documents and determined that no performance deficiency existed becaus</br>Exelons actions in response to the 2A EDG field flash monitoring relay alarm was not inconsistent with station documents and their action were reasonable based on the information available to the operators at that time. The inspectors reviewed LER 05000318/2014-002-00 and determined that traditional enforcement applies in accordance with IMC 0612, Power Reactor Inspection Reports</br>Section 0612-09 and 0612-13 and the Enforcement Policy, Section 2.2.4.d, because a violation of NRC requirements existed without an associated performance deficiency. This issue was considered to be a Severity Level IV NCV of TS LCO 3.8.1.J, in accordance with the Enforcement Policy, Section 6.1.d. This Severity Level IV licensee identified NCV was entered into Exelons CAP as CR-2014-006670.ntered into Exelons CAP as CR-2014-006670.
23:59:59, 31 December 2014 +
23:59:59, 31 December 2014 +
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>.
05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 +, 05000317/FIN-2014005-02 + and 05000317/FIN-2014005-02 +
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>.
15:50:36, 30 May 2018 +
23:59:59, 31 December 2014 +
TS-3.8.1.B + and TS-3.8.1.J +