Loss of Emergency Preparedness
If not reported under 10 CFR 50.72(a), (b)(1), or (b)(2), an ENS notification is required under 10 CFR 50.72(b)(3) (an 8-hour report) for a major loss of emergency assessment, offsite response, or offsite communications capability. The loss of emergency preparedness capabilities should be apparent at the time of occurrence or discovery. 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.
Discussion
This reporting requirement pertains to events that would result in a major loss of emergency assessment capability, offsite response capability, or offsite communications capabilities. The loss of these capabilities could substantially impair a licensee’s, or offsite officials’, ability to respond to an emergency if one were to occur or has occurred. The focus of this reporting requirement is in the loss of capabilities to perform functions identified in the respective
emergency plan. Failures of individual systems or facilities that comprise these capabilities are reportable only to the extent that these failures meet the above threshold.
Notifying the NRC of these events permits the NRC to consider implementing compensatory measures and to more completely assess the consequences of such a loss should it occur during an accident or emergency. The following are examples of equipment or facilities that may be encompassed by this reporting requirement:
- Emergency Assessment Capabilities
- – safety parameter display system (SPDS)
- – primary emergency response facilities (ERFs)
- – plant monitors necessary for accident assessment
- Offsite Response Capabilities
- – public prompt notification system(s) including sirens (primary system)
- Offsite Communication Capabilities
- – ENS
- – other emergency communications facilities and equipment used between the licensee’s onsite and offsite ERFs, and between the licensee and offsite officials
Losses of the above equipment and other situations should be evaluated for reportability as discussed below.
Loss of Emergency Assessment Capability
A major loss of emergency assessment capability includes those events that would significantly impair the licensee’s emergency assessment capability if an emergency were to occur. Some engineering judgment is needed to determine the significance of the loss of particular equipment. For example, the loss of the SPDS alone may not need to be reported, but a loss of the SPDS concurrent with other plant indicators or annunciators being unavailable is reportable if the licensee would be unable to assess or monitor an accident or transient in progress. Examples of events that should be evaluated against this threshold for reportability include, but are not limited to:
- A loss of a significant portion of control room indication, including annunciators or monitors, or the loss of all plant vent stack radiation monitors, should be evaluated for reportability. In evaluating the reportability of such events, only those display systems, indicators, and annunciators that are relied upon in the emergency plan and the emergency plan implementing procedures addressing classification, assessment, or protective actions; or relied upon in other station procedures that provide input to these activities need to be considered. The indication remaining available should be considered in determining if a major loss of emergency assessment capability has occurred.
- A significant degradation in the licensee’s ability to perform accident assessment functions assigned to a licensee primary ERF by the emergency plan. Typically, these functions would be the technical support center (TSC) but may include the emergency operations facility (EOF). Degradations would not be reportable if the ERF’s assessment capabilities were restored to service within the facility activation times specified in the emergency plan. Planned maintenance which impacts the accident assessment functions of the ERF, or its supporting systems, need not be reported if (1) the ERF’s assessment capabilities could be restored to service within the facility acitivation time specified in the emergency plan in the event of an accident or the
licensee had implemented viable compensatory actions, [1] and (2) the planned outage is not expected to, and subsequently did not, exceed 72 hours.
Loss of Offsite Response Capability
A major loss of offsite response capability includes those events that would significantly impair the ability of the licensee or offsite officials to implement the functions of their respective emergency plans if an emergency were to occur. Examples of events that should be evaluated against this threshold for reportability include, but are not limited to:
- The occurrence of a significant natural hazard (e.g., earthquake, hurricane, tornado, flood, major winter storms) or other event that would do one or both of the following:
- - Prevent State and local jurisdictions from maintaining evacuation routes passable, or from maintaining other parts of the response infrastructure available, to the extent that these jurisdictions would be unable to implement the public protective measures called for in their emergency plan, if known by the licensee, or,
- – Restrict access to the licensee’s site, or its offsite primary EOFs, such that the licensee would not be able to augment its on-shift staff or activate its ERFs as required by the emergency plan. Offsite response support relied upon in the emergency plan, such as fire departments, local law enforcement, and ambulance services, would not be able to access the site.
Traffic impediments, such as fog, snow, and ice, should generally not be reported if they are within the respective capabilities of the licensee, State, or local officials to resolve or mitigate. Rather, the reporting requirement is intended to apply to more significant cases, such as the conditions around the Turkey Point plant after Hurricane Andrew struck in 1992 or the conditions around the Cooper station during the Midwest floods of 1993.
- Failures in the primary public alerting systems (e.g., sirens, tone alert radios), for whatever reason, that result in the loss of the capability to alert a large segment of the population in the emergency planning zone (EPZ) for more than 1 hour. The licensee should take reasonable measures to remain informed of the status of the primary public alerting system, regardless of who maintains the system, and must notify the NRC if the established thresholds are exceeded. A planned outage of the primary public alerting system need not be reported if (1) the licensee had arranged for the implementation of Federal Emergency Management Agency (FEMA)-approved backup alerting methods should public alerting become necessary, and (2) the planned outage is not expected to, and subsequently did not, exceed 24 hours.
Loss of Communications Capability
A major loss of communications capability include those events that would significantly impair the ability of the licensee to implement the functions of its emergency plans if an emergency were to occur. Failures of individual communications systems are reportable only to the extent that these failures meet this threshold. The failure of a single communication system need not be reported if there are viable alternative methods[2] of communicating information about the emergency.
This reporting requirement only addresses those communication systems that enable a licensee to make notifications and provide followup information to Federal, State, and local officials located offsite. It also includes communication capabilities between the site and licensee ERO personnel assigned offsite. Examples of communication systems whose failures should be evaluated against the above threshold for reportability include, but are not limited to, the
following:
- ERDS
- ENS
- health physics network (HPN)
- other offsite communication systems, including the following:
- – dedicated telephone communication link to State or local officials
- – dedicated voice and data links between the site and emergency offsite response facilities
- – licensee radio system for communicating with offsite field monitoring teams
- – commercial telephone lines that are relied upon for use in emergency response
Each site’s communications system will be different, and the significance of the loss of any one communication system may differ from site to site. This reporting requirement is intended to apply to serious conditions during which the telecommunications system can no longer fulfill the communications requirements of the emergency plan.
Planned maintenance that impacts the emergency communications capability need not be reported if (1) the communication system could be restored to service promptly in the event of an accident or the licensee had implemented viable compensatory actions, 13 and (2) the planned outage is not expected to, and subsequently did not, exceed 72 hours.
Although a notification may not be required under 10 CFR 50.72(b)(3(xiii) in the event of a loss of the ENS, HPN, or ERDS because of the availability of viable alternative communication means, the licensee should inform the NRC Operations Center of any failure of these systems so that the NRC may arrange for repair of NRC-supplied communications equipment. When informing the NRC Operations Center, licensees should use the commercial telephone number 301-816-5100. If the Operations Center (or the ERDS Data Center) notifies the licensee that an ENS, HPN, or ERDS line is out of service, there is no need for an additional call. At the time the failure is reported, the licensee should be prepared to supply the following information to expedite repair: (1) name of contact at location of failure, (2) commercial phone number of contact, (3) location of contact (i.e., street address, building number, room number, etc., and (4) any other information that would expedite repair.
Examples
(1) Loss of Public Prompt Notification System
The NRC has not established a numerical threshold (e.g., number, percentage, or area of failed sirens) for this reporting requirement because the thresholds need to be specific to the particular EPZ. The NRC expects its licensees to establish thresholds that reflect the EPZ-specific population density and distribution, the locations of the sirens or other alerting devices, and the overlap in coverage of adjacent sirens. For example, a loss of 10 percent of the sirens in a high-density population area may have greater impact than 13 “Promptly” means within the emergency plan requirements specified for the communication system. A loss of the ability to make initial notifications would need to be restored within 15 minutes, while a loss of the ability to communicate between ERFs would need to be restored within the facility activation time. A “viable” compensatory action is one that (1) can restore the required function in a reasonably comparable manner, and (2) is proceduralized prior to the event.
50 percent of the sirens lost in a low-density area. Similarly, a loss of 10 percent of the sirens dispersed across the entire EPZ may not be as significant as losing the same number of sirens in a single jurisdiction. As such, notifications of the loss of the primary public prompt notification system will vary according to the licensee’s “major loss” threshold. Previous notifications have included the following:
- 12 of 40 county alert sirens were disabled because of loss of power as a result of
severe weather
- 28 of 54 alert sirens were reported out of service as a result of a local ice storm
- all offsite emergency sirens were:
- – found out of service during a monthly test
- – taken out of service for repair
- – out of service because control panel power was lost
- – out of service because the county radio transmitter failed
Failures in the primary public alerting systems (e.g., sirens, tone alert radios), for whatever reason, that result in the loss of the capability to alert a large segment of the population in the EPZ for more than 1 hour should be reported as a major loss of offsite response capability. However, a planned outage need not be reported if (1) the licensee had arranged for the implementation of FEMA-approved backup alerting methods should public alerting become necessary, and (2) the planned outage is not expected to, and subsequently did not, exceed 24 hours. No LER is required because there are no corresponding 10 CFR 50.73 requirements.
(2) Loss of ENS and Commercial Telephone System
The licensee determined that ENS and commercial telecommunications capability was lost to the control room when a fiber optic cable was severed during maintenance. A communications link was established and maintained between the site and the load dispatcher via microwave transmission. Both the ENS and commercial communications capability were restored approximately 90 minutes later.
An ENS notification is required because of the major loss of communications capability.
Although the microwave link to the site was established and maintained during the telephone outage, the link would not allow direct communication between the NRC and the control room, and therefore, this in itself does not fully compensate for the loss of communication that would be required in the event of an emergency at the plant. No LER is required because there are no corresponding 10 CFR 50.73 requirements.
(3) Loss of Direct Communication Line to Police
The licensee determined that the direct telephone line to the State Police had been out of service. In this example, no ENS notification is required because commercial telephone lines to the State Police were available. An ENS notification would be required if the loss of the direct telephone line(s) to various police, local, or State emergency or regulatory agencies is not compensated for by other readily available offsite communications systems. No LER is required because there are no corresponding 10 CFR 50.73 requirements.
(4) Loss of the Emergency Response Data System
The licensee determined that the ERDS was out of service due to a failure of licensee-owned and -maintained equipment. However, the ENS was available.
Because the ERDS is identified as a supplement to the ENS in Appendix E of 10 CFR 50, the failure of the ERDS does not constitute a major loss of offsite communication capability provided that the ENS is available and, as a result, no report under this reporting criterion is required. If, however, the failure is determined to be in NRC-maintained equipment, the licensee should inform the ERDS help desk of the outage so that the NRC can arrange for repair
Reporting criterion |
---|
|
|
WEEKMONTHYEARENS 573612024-10-04T02:35:000Start date: 4 October 2024 02:35:00 Site: Vogtle Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 573252024-09-16T17:29:000Start date: 16 September 2024 17:29:00 Site: Fermi Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 572782024-08-21T00:01:000Start date: 21 August 2024 00:01:00 Site: Summer Reporting criterion: 10 CFR 50.72(b)(3)(v)(D), Loss of Safety Function - Mitigate the Consequences of an Accident, 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 572252024-07-12T17:37:000Start date: 12 July 2024 17:37:00 Site: McGuire Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 572202024-07-09T09:55:000Start date: 9 July 2024 09:55:00 Site: Cooper Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 571632024-06-05T04:41:000Start date: 5 June 2024 04:41:00 Site: Columbia Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 568042023-10-19T16:10:000Start date: 19 October 2023 16:10:00 Site: Prairie Island Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 566982023-08-25T21:00:000Start date: 25 August 2023 21:00:00 Site: Byron Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 566502023-08-01T13:55:000Start date: 1 August 2023 13:55:00 Site: Fermi Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 565132023-05-09T18:55:000Start date: 9 May 2023 18:55:00 Site: Peach Bottom Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 565012023-05-02T19:00:000Start date: 2 May 2023 19:00:00 Site: Palisades Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 564102023-03-15T00:00:000Start date: 15 March 2023 00:00:00 Site: Yankee Rowe Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563642023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: LaSalle Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563632023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: Ginna Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563622023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: FitzPatrick Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563612023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: Dresden Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563602023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: Limerick Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563592023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: Nine Mile Point Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563582023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: Peach Bottom Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563572023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: Quad Cities Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563562023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: Clinton Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563552023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: Calvert Cliffs Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563542023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: Byron Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 563522023-02-06T11:30:000Start date: 6 February 2023 11:30:00 Site: Braidwood Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 559812022-07-07T21:01:000Start date: 7 July 2022 21:01:00 Site: Cooper Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 558672022-04-29T03:38:000Start date: 29 April 2022 03:38:00 Site: Sequoyah Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 557962022-03-19T20:06:000Start date: 19 March 2022 20:06:00 Site: Palo Verde Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 557692022-03-06T03:15:000Start date: 6 March 2022 03:15:00 Site: Byron Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 557582022-02-25T16:33:000Start date: 25 February 2022 16:33:00 Site: McGuire Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 557412022-02-16T16:59:000Start date: 16 February 2022 16:59:00 Site: Watts Bar Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 557422022-02-16T16:28:000Start date: 16 February 2022 16:28:00 Site: Sequoyah Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 557152022-01-27T16:38:000Start date: 27 January 2022 16:38:00 Site: Cooper Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 556942022-01-07T07:20:000Start date: 7 January 2022 07:20:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 556742021-12-22T17:45:000Start date: 22 December 2021 17:45:00 Site: Harris Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 554442021-09-01T03:50:000Start date: 1 September 2021 03:50:00 Site: Palo Verde Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 554432021-08-31T18:40:000Start date: 31 August 2021 18:40:00 Site: Waterford Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 553392021-07-04T13:11:000Start date: 4 July 2021 13:11:00 Site: Catawba Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 553252021-06-24T14:01:000Start date: 24 June 2021 14:01:00 Site: Braidwood Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 553052021-06-13T03:27:000Start date: 13 June 2021 03:27:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 553042021-06-12T22:25:000Start date: 12 June 2021 22:25:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 552132021-04-25T16:00:000Start date: 25 April 2021 16:00:00 Site: Harris Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 550862021-01-29T03:30:000Start date: 29 January 2021 03:30:00 Site: LaSalle Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 550552021-01-03T11:45:000Start date: 3 January 2021 11:45:00 Site: Vogtle Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 550172020-12-01T16:16:000Start date: 1 December 2020 16:16:00 Site: Harris Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 549772020-11-01T09:56:000Start date: 1 November 2020 09:56:00 Site: Sequoyah Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 549682020-10-27T21:08:000Start date: 27 October 2020 21:08:00 Site: Wolf Creek Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 549432020-10-11T07:15:000Start date: 11 October 2020 07:15:00 Site: Catawba Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 549292020-09-30T13:15:000Start date: 30 September 2020 13:15:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 549172020-09-28T09:00:000Start date: 28 September 2020 09:00:00 Site: Peach Bottom Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 548982020-09-12T21:48:000Start date: 12 September 2020 21:48:00 Site: Catawba Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 548872020-09-06T07:45:000Start date: 6 September 2020 07:45:00 Site: Catawba Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 548292020-08-11T17:34:000Start date: 11 August 2020 17:34:00 Site: Peach Bottom Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 548032020-07-29T00:49:000Start date: 29 July 2020 00:49:00 Site: Prairie Island Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 547702020-07-10T13:00:000Start date: 10 July 2020 13:00:00 Site: Catawba Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 547722020-07-10T13:00:000Start date: 10 July 2020 13:00:00 Site: Brunswick Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 547712020-07-10T13:00:000Start date: 10 July 2020 13:00:00 Site: Oconee Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 547732020-07-10T13:00:000Start date: 10 July 2020 13:00:00 Site: Harris Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 547692020-07-10T13:00:000Start date: 10 July 2020 13:00:00 Site: McGuire Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 547682020-07-10T13:00:000Start date: 10 July 2020 13:00:00 Site: Robinson Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 547522020-06-22T01:00:000Start date: 22 June 2020 01:00:00 Site: Catawba Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 547102020-05-13T15:00:000Start date: 13 May 2020 15:00:00 Site: Byron Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 546512020-04-08T13:45:000Start date: 8 April 2020 13:45:00 Site: Harris Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 545692020-03-06T02:00:000Start date: 6 March 2020 02:00:00 Site: Seabrook Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 545092020-02-03T14:15:000Start date: 3 February 2020 14:15:00 Site: Oconee Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 544722020-01-13T14:10:000Start date: 13 January 2020 14:10:00 Site: McGuire Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 544662020-01-08T02:55:000Start date: 8 January 2020 02:55:00 Site: Columbia Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 544332019-12-10T15:20:000Start date: 10 December 2019 15:20:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 544302019-12-10T03:26:000Start date: 10 December 2019 03:26:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 544092019-11-25T16:54:000Start date: 25 November 2019 16:54:00 Site: Columbia Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 543822019-11-12T12:00:000Start date: 12 November 2019 12:00:00 Site: Browns Ferry Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 543802019-11-12T12:00:000Start date: 12 November 2019 12:00:00 Site: Sequoyah Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 543792019-11-12T12:00:000Start date: 12 November 2019 12:00:00 Site: Watts Bar Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 543672019-11-03T14:00:000Start date: 3 November 2019 14:00:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 543292019-10-14T14:11:000Start date: 14 October 2019 14:11:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 542842019-09-18T12:50:000Start date: 18 September 2019 12:50:00 Site: South Texas Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 542782019-09-13T09:27:000Start date: 13 September 2019 09:27:00 Site: Browns Ferry Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 542772019-09-13T09:27:000Start date: 13 September 2019 09:27:00 Site: Watts Bar Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 542762019-09-13T09:27:000Start date: 13 September 2019 09:27:00 Site: Sequoyah Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 542722019-09-12T01:24:000Start date: 12 September 2019 01:24:00 Site: Palo Verde Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 542322019-08-19T14:39:000Start date: 19 August 2019 14:39:00 Site: Cooper Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 541452019-07-03T15:26:000Start date: 3 July 2019 15:26: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)(3)(xiii), Loss of Emergency Preparedness ENS 540902019-05-26T00:30:000Start date: 26 May 2019 00:30:00 Site: Braidwood Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 540732019-05-19T23:09:000Start date: 19 May 2019 23:09:00 Site: Arkansas Nuclear Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 542562019-04-29T02:00:000Start date: 29 April 2019 02:00:00 Site: Catawba Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 539772019-04-04T15:55:000Start date: 4 April 2019 15:55:00 Site: Oyster Creek Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 539412019-03-16T16:00:000Start date: 16 March 2019 16:00:00 Site: Cooper Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 539242019-03-11T12:51:000Start date: 11 March 2019 12:51:00 Site: Beaver Valley Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 538252019-01-14T05:00:000Start date: 14 January 2019 05:00:00 Site: Fermi Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 537752018-12-04T08:00:000Start date: 4 December 2018 08:00:00 Site: Columbia Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 537002018-10-28T05:00:000Start date: 28 October 2018 05:00:00 Site: Prairie Island Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 536962018-10-26T04:00:000Start date: 26 October 2018 04:00:00 Site: Ginna Reporting criterion: 10 CFR 50.72(b)(3)(iv)(A), System Actuation, 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 536562018-10-09T05:00:000Start date: 9 October 2018 05:00:00 Site: South Texas Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 536472018-10-05T05:00:000Start date: 5 October 2018 05:00:00 Site: Wolf Creek Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 535942018-09-11T04:00:000Start date: 11 September 2018 04:00:00 Site: Peach Bottom Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 535752018-08-31T07:00:000Start date: 31 August 2018 07:00:00 Site: Palo Verde Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 535622018-08-24T04:00:000Start date: 24 August 2018 04:00:00 Site: Fermi Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 535222018-07-23T07:00:000Start date: 23 July 2018 07:00:00 Site: Palo Verde Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 535002018-07-11T05:00:000Start date: 11 July 2018 05:00:00 Site: Duane Arnold Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 534982018-07-09T04:00:000Start date: 9 July 2018 04:00:00 Site: McGuire Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness ENS 534722018-06-26T05:00:000Start date: 26 June 2018 05:00:00 Site: Comanche Peak Reporting criterion: 10 CFR 50.72(b)(3)(xiii), Loss of Emergency Preparedness
[Table view] |
|
- ↑ “Promptly” means within the licensee’s emergency plan requirements for facility activation time. A “viable” compensatory action is one that (1) can restore the required function in a reasonably comparable manner and (2) is proceduralized prior to an event.
- ↑ A “viable” alternative method (or compensatory action) is one that (1) can perform the required function in a reasonably comparable manner and (2) is proceduralized prior to an event.