System Actuation
System Actuation Reporting Summary
|
Valid |
Invalid
|
Moved
|
ENS + LER
|
LER (as 60 day ENS)
|
Not moved
|
ENS + LER
|
None
|
4-hour (ENS)
While Critical or RPS (ie Scram)
8-hour (ENS)
60-day (LER)
60-day (ENS)
Allowance for invalid signals which actuated a system
System actuation list
System Actuation Reporting contains a list of applicable systems
Both list include:
- (1) Reactor protection system (RPS) including: Reactor scram and reactor trip.
- (2) General containment isolation signals affecting containment isolation valves in more than one system or multiple main steam isolation valves (MSIVs).
- (3) Emergency core cooling systems (ECCS) for pressurized water reactors (PWRs) including: High-head, intermediate-head, and low-head injection systems and the low pressure injection function of residual (decay) heat removal systems.
- (4) ECCS for boiling water reactors (BWRs) including: High-pressure and low-pressure core spray systems; high-pressure coolant injection system; low pressure injection function of the residual heat removal system.
- (5) BWR reactor core isolation cooling system; isolation condenser system; and feedwater coolant injection system.
- (6) PWR feedwater system or emergency feedwater system.
- (7) Containment heat removal and depressurization systems, including containment spray and fan cooler systems.
- (8) Emergency ac electrical power systems, including: Emergency diesel generators (EDGs); hydroelectric facilities used in lieu of EDGs at the Oconee Station; and BWR dedicated Division 3 EDGs.
Only 50.73: (9) Emergency service water systems that do not normally run and that serve as ultimate heat sinks.
Discussion
An event that results or should have resulted in a discharge of the ECCS into the RCS as a result of a valid signal, or an event involving a critical scram, is reportable under 10 CFR 50.72(b)(2)(iv) (a 4-hour report) unless the actuation resulted from and was part of a preplanned sequence.
A valid actuation of any of the systems named in 10 CFR 50.72(b)(3)(iv)(B) is reportable under 10 CFR 50.72(b)(3)(iv)(A) (an 8-hour report) unless the actuation resulted from and was part of a preplanned sequence during testing or reactor operation.
A system actuation should be apparent at the time of occurrence. Therefore, if all events are reported properly, it is expected that all reports under 10 CFR 50.72 are as a result of an ongoing condition.
An actuation of any of the systems named in 10 CFR 50.73(a)(2)(iv)(B) is reportable under 10 CFR 50.73(a)(2)(iv)(A) (a 60-day report) unless the actuation resulted from and was part of a preplanned sequence during testing or reactor operation or the actuation was invalid and occurred while the system was properly removed from service or occurred after the safety function had been already completed. As indicated in 10 CFR 50.73(a)(1), in the case of an invalid actuation reported under 10 CFR 50.73(a)(2)(iv)(A) other than actuation of the RPS when the reactor is critical, the licensee may, at its option, provide a telephone notification to the NRC Operations Center within 60 days after discovery of the event instead of submitting a written LER. In these cases, the telephone report—
- (1) Is not considered an LER.
- (2) Should identify that the report is being made under 10 CFR 50.73(a)(2)(iv)(A).
- (3) Should provide the following information:
- (a) the specific train(s) and system(s) that were actuated
- (b) whether each train actuation was complete or partial
- (c) whether or not the system started and functioned successfully
These paragraphs require events to be reported whenever one of the specified systems actuates either manually or automatically. They are based on the premise that these systems are provided to mitigate the consequences of a significant event and, therefore, (1) they should work properly when called upon, and (2) they should not be challenged frequently or unnecessarily. The Commission is interested in both events in which a system was needed to mitigate the consequences of an event (whether or not the equipment performed properly) and events in which a system actuated unnecessarily.
Events involving ECCS discharge to the vessel are generally more serious than actuations without discharge to the vessel. Therefore, this reporting criterion is a 4-hour report. Valid signals that should have resulted in a discharge of the ECCS into the RCS but did not due to some component that had failed or an operator action that was taken are reportable under 10 CFR 50.72(b)(2)(iv). For example, if a valid ECCS signal was generated by plant conditions and the operator put all ECCS pumps in pull-to-lock position, although no ECCS discharge occurred, the event is reportable under 10 CFR 50.72(b)(2)(iv).
Actuations that need not be reported are those initiated for reasons other than to mitigate the consequences of an event (e.g., at the discretion of the licensee as part of a preplanned procedure).
The intent is to require reporting of the actuation of systems that mitigate the consequences of significant events. Usually, the staff would not consider this to include single-component actuations because single components of complex systems, by themselves, usually do not mitigate the consequences of significant events. However, in some cases a component would be sufficient to mitigate the event (i.e., perform the safety function) and its actuation would, therefore, be reportable. This position is consistent with the statement that the reporting requirement is based on the premise that these systems are provided to mitigate the consequences of a significant event.
Single trains do mitigate the consequences of events, and, thus, train level actuations are reportable.
In this regard, the staff considers actuation of an EDG to be actuation of a train—not actuation of a single component—because an EDG mitigates the event (performs the safety function). (See Example 3 below.) The staff also considers intentional manual actions, in which one or more system components are actuated in response to actual plant conditions resulting from equipment failure or human error, to be reportable because such actions would usually mitigate the consequences of a significant event. This position is consistent with the statement that the Commission is interested in events in which a system was needed to mitigate the consequences of the event.
For example, starting a safety injection (SI) pump in response to a rapidly decreasing pressurizer level or starting high-pressure coolant injection (HPCI) in response to a loss of feedwater would be reportable. However, shifting alignment of makeup pumps or closing a containment isolation valve for normal operational purposes would not be reportable.
Actuation of multichannel actuation systems is defined as actuation of enough channels to complete the minimum actuation logic. Therefore, single-channel actuations, whether caused by failures or otherwise, are not reportable if they do not complete the minimum actuation logic.
Note, however, that if only a single logic channel actuates when, in fact, the system should have actuated in response to plant parameters, this would be reportable under these paragraphs as well as under 10 CFR 50.72(b)(3)(v) and 10 CFR 50.73(a)(2)(v) (“event or condition that could have prevented the fulfillment of the safety function of....”).
With regard to preplanned actuations, operation of a system as part of a planned test or operational evolution need not be reported. Preplanned actuations are those that are expected to actually occur due to preplanned activities covered by procedures. Such actuations are those for which a procedural step or other appropriate documentation indicates that the specific actuation is actually expected to occur. Control room personnel are aware of the specific signal generation before its occurrence or indication in the control room. However, if, during the test or evolution, the system actuates in a way that is not part of the planned evolution, that actuation should be reported. For example, if the normal reactor shutdown procedure requires that the control rods be inserted by a manual reactor scram, the reactor scram need not be reported.
However, if unanticipated conditions develop during the shutdown that cause an automatic reactor scram, such a reactor scram should be reported. The fact that the safety analysis assumes that a system will actuate automatically during an event does not eliminate the need to report that actuation. Actuations that need not be reported are those initiated for reasons other than to mitigate the consequences of an event (e.g., at the discretion of the licensee as part of a planned evolution).
Note that, if an operator were to manually scram the reactor in anticipation of receiving an automatic reactor scram, this would be reportable just as the automatic scram would be reportable.
Valid actuations are those actuations that result from valid signals or from intentional manual initiation, unless it is part of a preplanned test. Valid signals are those signals that are initiated in response to actual plant conditions or parameters satisfying the requirements for initiation of the system. They do not include those that are the result of other signals. Invalid actuations are, by definition, those that do not meet the criteria for being valid. Thus, invalid actuations include actuations that are not the result of valid signals and are not intentional manual actuations.
Except for critical scrams, invalid actuations are not reportable by telephone under 10 CFR 50.72. In addition, invalid actuations are not reportable under 10 CFR 50.73 in any of the following circumstances:
- (1) The invalid actuation occurred when the system was already properly removed from service. This means that all requirements of plant procedures for removing equipment from service have been met. It includes required clearance documentation, equipment and control board tagging, and properly positioned valves and power supply breakers.
- (2) The invalid actuation occurred after the safety function had already been completed. An example would be RPS actuation after the control rods have already been inserted into the core.
If an invalid actuation reveals a defect in the system so that the system failed or would fail to perform its intended function, the event continues to be reportable under other requirements of 10 CFR 50.72 and 50.73. When invalid actuations excluded by the conditions described above occur as part of a reportable event, they should be described as part of the reportable event in order to provide a complete, accurate, and thorough description of the event.
Examples
(1) Reactor Protection System Actuation
- The licensee was placing the RHR system in its shutdown cooling mode while the plant was in hot shutdown. The BWR vessel level decreased for unknown reasons, causing RPS scram and Group III primary containment isolation signals, as designed. All control rods had been previously inserted and all Group III isolation valves had been manually isolated. The licensee isolated RHR to stop the decrease in reactor vessel level.
An ENS notification and an LER are both required because, although the systems’ safety functions had already been completed, the RPS scram and primary containment isolation signals were valid and the actuations were not part of the planned procedure. The automatic signals were valid because they were generated from the sensor by measurement of an actual physical system parameter that was at its setpoint.
With the BWR defueled, an invalid signal actuated the RPS. There was no component operation because the control rod drive system had been properly removed from service. This event is not reportable because (1) the RPS signal was invalid, and (2) the system had been properly removed from service.
- At a BWR, both recirculation pumps tripped as a result of a breaker problem.
This placed the plant in a condition in which BWRs are typically scrammed to avoid potential power/flow oscillations. At this plant, for this condition, a written off-normal procedure required the plant operations staff to scram the reactor.
The plant staff performed a reactor scram, which was uncomplicated.
This event is reportable as a manual RPS actuation. Even though the reactor scram was in response to an existing written procedure, this event does not involve a preplanned sequence because the loss of recirculation pumps and the resultant off-normal procedure entry were event driven, not preplanned. Both an ENS notification and an LER are required. In this case, the licensee initially retracted the ENS notification, believing that the event was not reportable. After staff review and further discussion, it was agreed that the event is reportable for the reasons discussed above.
(2) Boiling Water Reactor Control Rod Block Monitor Actuation
A rod block that was part of the planned startup procedure occurred from the rod block monitor, which, at this plant, is classified as a portion of the RPS.
This event is not reportable because it occurred as a part of a preplanned startup procedure that specified that certain rod blocks were expected to occur.
(3) Emergency Diesel Generator Starts
- An EDG automatically started when a technician inadvertently caused a short circuit that de-energized an essential bus during a calibration. The actuation was valid because an essential bus was de-energized. The event is reportable because the EDG autostart was not identified at the step in the calibration procedure being used.
- After an automatic EDG start, and for unknown reasons, the emergency bus feeder breaker from the EDG did not close when power was lost on the bus. The event is reportable because the actuation logic for the EDG start was completed, even though the EDG did not power the safety buses.
(4) Preplanned Manual Scram
During a normal reactor shutdown, the reactor shutdown procedure required that reactor power be reduced to a low power, at which point the control rods were to be inserted by a manual reactor scram. The rods were manually scrammed.
This event is not reportable because the manual scram resulted from and was, by procedure, part of a preplanned sequence of reactor operation. However, if conditions develop during the process of shutting down that require an unplanned reactor scram, the RPS actuation (whether manually or automatically produced) is reportable.
(5) Actuation of Wrong Component during Testing
During surveillance testing of the MSIVs, an operator incorrectly closed MSIV D when the procedure specified closing MSIV C.
This event is not reportable because the event is an inadvertent actuation of a single component rather than a train-level actuation (and the purpose of the actuation was not to mitigate the consequences of an event).
(6) Reactor Water Cleanup Isolation
A Reactor Water Cleanup (RWCU) primary containment isolation occurred on pressurization between the RWCU suction containment isolation valves, as designed to isolate a pipe break. It is a valid signal because this is the safety function of the containment isolation system. Regardless, the event is not reportable because the signal did not affect containment isolation valves in multiple systems.
(7) Manual Actuation of Component in Response to Actual Plant Condition
At a PWR, maintenance personnel inadvertently pulled an instrument line out of a compression fitting connection at a pressure transmitter. The resultant RCS leak was estimated at between 70 and 80 gallons per minute. Charging flow increased due to automatic control system action. The operations staff recognized the symptoms of an RCS leak and entered the appropriate off-normal procedure. The procedure directed the operations staff to start a second charging pump, and flow was manually increased to raise pressurizer level. Based on the response of the pressurizer level, the operations staff determined that a reactor scram and SI were not necessary. Maintenance personnel still at the transmitter closed the instrument block and root valves, terminating the event.
The staff considers the manual start of the charging pump (which also serves as an ECCS pump, but with a different valve lineup) in response to dropping pressurizer level to be an intentional manual actuation in response to equipment failure or human error and reportable because it constitutes deliberate manual actuation of a single component, in response to plant conditions, to mitigate the consequences of an event. As discussed previously in this section, actuations that need not be reported are those that are initiated for reasons other than to mitigate the consequences of an event (e.g., at the discretion of the licensee as part of a planned procedure or evolution).
(8) Actuation during Maintenance Activity
At a BWR, a maintenance activity was underway involving placement of a jumper to avoid unintended actuations. The maintenance staff recognized that there was a high potential for a loss of contact with the jumper and consequent actuation. This potential was explicitly stated in the maintenance work request and on a risk evaluation sheet.
The operating staff was briefed on the potential actuations prior to start of work. During the event, a loss of continuity did occur and the actuations occurred, involving isolation, standby gas treatment start, closing of some valves in the primary containment isolation system (recirculation pump seal mini purge valve, nitrogen supply to drywell valve, and containment atmospheric monitoring valve).
The event is not reportable under 10 CFR 50.72(b)(2)(iv) or (b)(3)(iv) because the actuations were not valid. It is reportable under 10 CFR 50.73(a)(2)(iv) because the actuations were not listed as (and were not) definitely expected to occur.
Reporting criterion |
---|
|
|
WEEKMONTHYEARENS 574312024-11-19T18:50:000Start date: 19 November 2024 18:50:00 Site: Seabrook Reporting criterion: 10 CFR 50.72(b)(2)(xi), Notification to Government Agency or News Release, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 574322024-11-19T18:50:000Start date: 19 November 2024 18:50:00 Site: Seabrook Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 574182024-11-10T09:37:000Start date: 10 November 2024 09:37:00 Site: Grand Gulf Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 574042024-10-29T15:23:000Start date: 29 October 2024 15:23:00 Site: Prairie Island Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 573512024-09-29T09:56:000Start date: 29 September 2024 09:56:00 Site: Sequoyah Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 573442024-09-27T11:46:000Start date: 27 September 2024 11:46:00 Site: Catawba Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(v)(B), Loss of Safety Function - Remove Residual Heat, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 573432024-09-27T07:46:000Start date: 27 September 2024 07:46:00 Site: Hatch Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 573332024-09-23T11:20:000Start date: 23 September 2024 11:20:00 Site: FitzPatrick Reporting criterion: 10 CFR 50.72(b)(2)(xi), Notification to Government Agency or News Release, 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 573342024-09-23T11:20:000Start date: 23 September 2024 11:20:00 Site: Nine Mile Point Reporting criterion: 10 CFR 50.72(b)(2)(xi), Notification to Government Agency or News Release, 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation, 10 CFR 50.72(b)(2)(iv)(A), System Actuation - ECCS Discharge ENS 573262024-09-17T05:27:000Start date: 17 September 2024 05:27:00 Site: Vogtle Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation, 10 CFR 50.72(b)(2)(iv)(A), System Actuation - ECCS Discharge ENS 572982024-08-30T15:51:000Start date: 30 August 2024 15:51:00 Site: Browns Ferry Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 572852024-08-23T16:19:000Start date: 23 August 2024 16:19:00 Site: Sequoyah Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 572532024-07-30T20:41:000Start date: 30 July 2024 20:41:00 Site: Sequoyah Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 572492024-07-28T22:37:000Start date: 28 July 2024 22:37:00 Site: Saint Lucie Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 572372024-07-24T12:02:000Start date: 24 July 2024 12:02:00 Site: South Texas Reporting criterion: 10 CFR 50.72(b)(2)(xi), Notification to Government Agency or News Release, 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(a)(1)(i), Emergency Class Declaration, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 572212024-07-10T11:28:000Start date: 10 July 2024 11:28:00 Site: Peach Bottom Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 572152024-07-09T01:25:000Start date: 9 July 2024 01:25:00 Site: Vogtle Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation, 10 CFR 50.72(b)(2)(iv)(A), System Actuation - ECCS Discharge ENS 572142024-07-08T19:21:000Start date: 8 July 2024 19:21:00 Site: Watts Bar Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 571952024-06-27T12:04:000Start date: 27 June 2024 12:04:00 Site: Cook Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 571872024-06-22T11:28:000Start date: 22 June 2024 11:28:00 Site: Vogtle Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 571752024-06-16T17:33:000Start date: 16 June 2024 17:33:00 Site: Waterford Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 571592024-06-03T04:51:000Start date: 3 June 2024 04:51:00 Site: Oconee Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 571482024-05-29T10:24:000Start date: 29 May 2024 10:24:00 Site: North Anna Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 571412024-05-23T16:46:000Start date: 23 May 2024 16:46:00 Site: Quad Cities Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 571322024-05-19T04:30:000Start date: 19 May 2024 04:30:00 Site: Beaver Valley Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 571282024-05-15T08:27:000Start date: 15 May 2024 08:27:00 Site: Cook Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 571242024-05-12T21:41:000Start date: 12 May 2024 21:41:00 Site: South Texas Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 571222024-05-11T21:55:000Start date: 11 May 2024 21:55:00 Site: Waterford Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 571072024-05-05T08:38:000Start date: 5 May 2024 08:38:00 Site: Braidwood Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570902024-04-25T03:15:000Start date: 25 April 2024 03:15:00 Site: Browns Ferry Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation, 10 CFR 50.72(b)(2)(iv)(A), System Actuation - ECCS Discharge ENS 570832024-04-20T12:04:000Start date: 20 April 2024 12:04:00 Site: LaSalle Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570752024-04-13T04:35:000Start date: 13 April 2024 04:35:00 Site: Beaver Valley Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570582024-03-28T01:46:000Start date: 28 March 2024 01:46:00 Site: Quad Cities Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570532024-03-26T16:15:000Start date: 26 March 2024 16:15:00 Site: Grand Gulf Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570472024-03-24T23:34:000Start date: 24 March 2024 23:34:00 Site: Palo Verde Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570462024-03-23T04:04:000Start date: 23 March 2024 04:04:00 Site: Fermi Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(v)(D), Loss of Safety Function - Mitigate the Consequences of an Accident, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570422024-03-22T04:37:000Start date: 22 March 2024 04:37:00 Site: Waterford Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(a)(1)(i), Emergency Class Declaration, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570432024-03-22T01:56:000Start date: 22 March 2024 01:56:00 Site: Callaway Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570332024-03-17T20:15:000Start date: 17 March 2024 20:15:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570322024-03-16T19:49:000Start date: 16 March 2024 19:49:00 Site: Waterford Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570262024-03-13T01:11:000Start date: 13 March 2024 01:11:00 Site: Catawba Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570242024-03-12T13:16:000Start date: 12 March 2024 13:16:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570212024-03-11T17:37:000Start date: 11 March 2024 17:37:00 Site: Hatch Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation, 10 CFR 50.72(b)(2)(iv)(A), System Actuation - ECCS Discharge ENS 570062024-03-05T06:32:000Start date: 5 March 2024 06:32:00 Site: Watts Bar Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570042024-03-04T00:42:000Start date: 4 March 2024 00:42:00 Site: Nine Mile Point Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 570032024-03-03T17:42:000Start date: 3 March 2024 17:42:00 Site: Prairie Island Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 569972024-02-28T18:50:000Start date: 28 February 2024 18:50:00 Site: Calvert Cliffs Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 569952024-02-28T14:39:000Start date: 28 February 2024 14:39:00 Site: Monticello Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 569912024-02-24T20:46:000Start date: 24 February 2024 20:46:00 Site: Calvert Cliffs Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 569902024-02-24T08:19:000Start date: 24 February 2024 08:19:00 Site: Browns Ferry Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 569782024-02-19T07:36:000Start date: 19 February 2024 07:36:00 Site: Summer Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 569772024-02-19T04:25:000Start date: 19 February 2024 04:25:00 Site: Brunswick Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 569712024-02-16T11:34:000Start date: 16 February 2024 11:34:00 Site: Farley Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 569702024-02-16T03:24:000Start date: 16 February 2024 03:24:00 Site: Watts Bar Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 569682024-02-15T08:47:000Start date: 15 February 2024 08:47:00 Site: Callaway Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 569362024-01-29T17:02:000Start date: 29 January 2024 17:02:00 Site: Peach Bottom Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 569352024-01-28T02:41:000Start date: 28 January 2024 02:41:00 Site: Watts Bar Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568942023-12-16T09:50:000Start date: 16 December 2023 09:50:00 Site: Grand Gulf Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568872023-12-13T07:02:000Start date: 13 December 2023 07:02:00 Site: River Bend Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568772023-12-02T12:10:000Start date: 2 December 2023 12:10:00 Site: South Texas Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568632023-11-18T05:55:000Start date: 18 November 2023 05:55:00 Site: River Bend Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568562023-11-16T07:27:000Start date: 16 November 2023 07:27:00 Site: Calvert Cliffs Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568522023-11-14T16:41:000Start date: 14 November 2023 16:41:00 Site: Farley Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568462023-11-10T08:14:000Start date: 10 November 2023 08:14:00 Site: Susquehanna Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568412023-11-08T11:45:000Start date: 8 November 2023 11:45:00 Site: Calvert Cliffs Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568392023-11-07T21:17:000Start date: 7 November 2023 21:17:00 Site: Calvert Cliffs Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568262023-11-01T10:48:000Start date: 1 November 2023 10:48:00 Site: Hatch Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation, 10 CFR 50.72(b)(2)(iv)(A), System Actuation - ECCS Discharge ENS 568132023-10-25T01:59:000Start date: 25 October 2023 01:59:00 Site: Turkey Point Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568032023-10-19T16:10:000Start date: 19 October 2023 16:10:00 Site: Prairie Island Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 568022023-10-18T15:16:000Start date: 18 October 2023 15:16:00 Site: McGuire Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 567902023-10-13T01:27:000Start date: 13 October 2023 01:27:00 Site: Ginna Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 567692023-10-01T03:14:000Start date: 1 October 2023 03:14:00 Site: Diablo Canyon Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 567592023-09-27T15:41:000Start date: 27 September 2023 15:41:00 Site: Monticello Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 567552023-09-22T22:19:000Start date: 22 September 2023 22:19:00 Site: Turkey Point Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 567312023-09-09T15:43:000Start date: 9 September 2023 15:43:00 Site: Ginna Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 567102023-09-02T10:32:000Start date: 2 September 2023 10:32:00 Site: Nine Mile Point Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation, 10 CFR 50.72(b)(2)(iv)(A), System Actuation - ECCS Discharge ENS 566922023-08-22T21:24:000Start date: 22 August 2023 21:24:00 Site: Vogtle Reporting criterion: 10 CFR 50.72(b)(2)(xi), Notification to Government Agency or News Release, 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 566762023-08-11T08:29:000Start date: 11 August 2023 08:29:00 Site: Quad Cities Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 566732023-08-10T04:39:000Start date: 10 August 2023 04:39:00 Site: Perry Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation, 10 CFR 50.72(b)(2)(iv)(A), System Actuation - ECCS Discharge ENS 566602023-08-04T21:46:000Start date: 4 August 2023 21:46:00 Site: Watts Bar Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 566582023-08-04T17:20:000Start date: 4 August 2023 17:20:00 Site: Turkey Point Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 566452023-07-30T19:26:000Start date: 30 July 2023 19:26:00 Site: Seabrook Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 565932023-06-27T20:26:000Start date: 27 June 2023 20:26:00 Site: Watts Bar Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 565852023-06-22T14:35:000Start date: 22 June 2023 14:35:00 Site: Robinson Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 565802023-06-16T23:32:000Start date: 16 June 2023 23:32:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 565512023-06-02T11:05:000Start date: 2 June 2023 11:05:00 Site: Palo Verde Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 565442023-05-30T08:46:000Start date: 30 May 2023 08:46:00 Site: Millstone Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 565432023-05-27T23:34:000Start date: 27 May 2023 23:34:00 Site: Prairie Island Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(a)(1)(i), Emergency Class Declaration, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 565312023-05-20T08:15:000Start date: 20 May 2023 08:15:00 Site: Browns Ferry Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 565272023-05-19T12:52:000Start date: 19 May 2023 12:52:00 Site: Beaver Valley Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 565652023-05-06T19:52:000Start date: 6 May 2023 19:52:00 Site: Seabrook Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 564782023-04-20T05:48:000Start date: 20 April 2023 05:48:00 Site: Brunswick Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 565642023-04-12T15:07:000Start date: 12 April 2023 15:07:00 Site: Seabrook Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 564592023-04-09T04:44:000Start date: 9 April 2023 04:44:00 Site: Palo Verde Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 564532023-04-05T10:51:000Start date: 5 April 2023 10:51:00 Site: Summer Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 564512023-04-02T07:52:000Start date: 2 April 2023 07:52:00 Site: McGuire Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 564462023-03-31T18:32:000Start date: 31 March 2023 18:32:00 Site: Hatch Reporting criterion: 10 CFR 50.72(b)(2)(iv)(B), RPS System Actuation, 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 564302023-03-23T21:36:000Start date: 23 March 2023 21:36:00 Site: Susquehanna Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 563892023-03-04T15:10:000Start date: 4 March 2023 15:10:00 Site: LaSalle Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation ENS 563732023-02-19T06:05:000Start date: 19 February 2023 06:05:00 Site: FitzPatrick Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation
[Table view] |
|