ML18194A413: Difference between revisions
StriderTol (talk | contribs) (Created page by program invented by StriderTol) |
StriderTol (talk | contribs) (StriderTol Bot change) |
||
| Line 17: | Line 17: | ||
=Text= | =Text= | ||
{{#Wiki_filter:July 18, 2018 | {{#Wiki_filter:July 18, 2018 | ||
Mr. William F. Maguire, Site Vice President | |||
Entergy Operations, Inc. | |||
River Bend Station | |||
5485 U.S. Highway 61N | Mr. William F. Maguire, Site Vice President | ||
St. Francisville, LA 70775 | Entergy Operations, Inc. | ||
SUBJECT: | River Bend Station | ||
5485 U.S. Highway 61N | |||
Dear Mr. Maguire: | St. Francisville, LA 70775 | ||
On July 16, 2018, the U.S. Nuclear Regulatory Commission (NRC) completed a baseline | |||
inspection at your River Bend Station, Unit 1. On May 31 and July 16, 2018, the NRC | SUBJECT: | ||
inspection team discussed the results of this inspection with you and other members of your | RIVER BEND STATION - NRC BASELINE INSPECTION REPORT | ||
staff. The results of this inspection are documented in the enclosed report. | 05000458/2018012 | ||
NRC inspectors documented five findings of very low safety significance (Green) in this report. | |||
Four of these findings involved violations of NRC requirements. Additionally, NRC inspectors | Dear Mr. Maguire: | ||
documented two violations that were determined to be Severity Level IV under the traditional | |||
enforcement process. The NRC is treating these violations as non-cited violations (NCVs) | On July 16, 2018, the U.S. Nuclear Regulatory Commission (NRC) completed a baseline | ||
consistent with Section 2.3.2.a of the NRC Enforcement Policy. | inspection at your River Bend Station, Unit 1. On May 31 and July 16, 2018, the NRC | ||
If you contest the violations or significance of these NCVs, you should provide a response within | inspection team discussed the results of this inspection with you and other members of your | ||
30 days of the date of this inspection report, with the basis for your denial, to the U.S. Nuclear | staff. The results of this inspection are documented in the enclosed report. | ||
Regulatory Commission, ATTN: Document Control Desk, Washington, DC 20555-0001; with | |||
copies to the Regional Administrator, Region IV; the Director, Office of Enforcement; and the | NRC inspectors documented five findings of very low safety significance (Green) in this report. | ||
NRC resident inspector at the River Bend Station. | Four of these findings involved violations of NRC requirements. Additionally, NRC inspectors | ||
If you disagree with a cross-cutting aspect assignment in this report, you should provide a | documented two violations that were determined to be Severity Level IV under the traditional | ||
response within 30 days of the date of this inspection report, with the basis for your | enforcement process. The NRC is treating these violations as non-cited violations (NCVs) | ||
disagreement, to the U.S. Nuclear Regulatory Commission, ATTN: Document Control Desk, | consistent with Section 2.3.2.a of the NRC Enforcement Policy. | ||
Washington, DC 20555-0001; with copies to the Regional Administrator, Region IV; and the | |||
NRC resident inspector at the River Bend Station. | If you contest the violations or significance of these NCVs, you should provide a response within | ||
30 days of the date of this inspection report, with the basis for your denial, to the U.S. Nuclear | |||
Regulatory Commission, ATTN: Document Control Desk, Washington, DC 20555-0001; with | |||
copies to the Regional Administrator, Region IV; the Director, Office of Enforcement; and the | |||
NRC resident inspector at the River Bend Station. | |||
If you disagree with a cross-cutting aspect assignment in this report, you should provide a | |||
response within 30 days of the date of this inspection report, with the basis for your | |||
disagreement, to the U.S. Nuclear Regulatory Commission, ATTN: Document Control Desk, | |||
Washington, DC 20555-0001; with copies to the Regional Administrator, Region IV; and the | |||
NRC resident inspector at the River Bend Station. | |||
W. Maguire | W. Maguire | ||
This letter, its enclosure, and your response (if any) will be made available for public inspection | 2 | ||
and copying at http://www.nrc.gov/reading-rm/adams.html and at the NRC Public Document | This letter, its enclosure, and your response (if any) will be made available for public inspection | ||
Room in accordance with 10 CFR 2.390, Public Inspections, Exemptions, Requests for | and copying at http://www.nrc.gov/reading-rm/adams.html and at the NRC Public Document | ||
Withholding. | Room in accordance with 10 CFR 2.390, Public Inspections, Exemptions, Requests for | ||
Withholding. | |||
Sincerely, | |||
Docket No. 50-458 | /RA/ | ||
License No. NPF-47 | |||
Enclosure: | Jason W. Kozal, Chief | ||
Inspection Report 05000458/2018012 | Project Branch C | ||
w/ Attachment: Documents Reviewed | Division of Reactor Projects | ||
Docket No. 50-458 | |||
License No. NPF-47 | |||
Enclosure: | |||
Inspection Report 05000458/2018012 | |||
w/ Attachment: Documents Reviewed | |||
Docket Number: | |||
License Number: | Enclosure | ||
Report Number: | U.S. NUCLEAR REGULATORY COMMISSION | ||
Enterprise Identifier: I-2018-012-0015 | Inspection Report | ||
Licensee: | |||
Facility: | |||
Location: | Docket Number: | ||
Inspection Dates: | 05000458 | ||
Inspectors: | |||
License Number: | |||
NPF-47 | |||
Approved By: | |||
Report Number: | |||
05000458/2018012 | |||
Enterprise Identifier: I-2018-012-0015 | |||
Licensee: | |||
Entergy Operations, Inc. | |||
Facility: | |||
River Bend Station | |||
Location: | |||
Saint Francisville, Louisiana | |||
Inspection Dates: | |||
February 1, 2018 to July 16, 2018. | |||
Inspectors: | |||
J. Sowa, Senior Resident Inspector | |||
J. Drake, Senior Reactor Inspector | |||
C. Young, Senior Project Engineer | |||
M. OBanion, Resident Inspector (Acting) | |||
B. Parks, Resident Inspector | |||
Approved By: | |||
J. Kozal, Chief, Branch C | |||
Division of Reactor Projects | |||
The U.S. Nuclear Regulatory Commission (NRC) continued monitoring the licensees | |||
performance by conducting a baseline inspection at River Bend Station in accordance with the | 2 | ||
Reactor Oversight Process. The Reactor Oversight Process is the NRCs program for | |||
overseeing the safe operation of commercial nuclear power reactors. Refer to | SUMMARY | ||
https://www.nrc.gov/reactors/operating/oversight.html for more information. Findings and | The U.S. Nuclear Regulatory Commission (NRC) continued monitoring the licensees | ||
violations being considered in the NRCs assessment are summarized in the tables below. | performance by conducting a baseline inspection at River Bend Station in accordance with the | ||
Reactor Oversight Process. The Reactor Oversight Process is the NRCs program for | |||
overseeing the safe operation of commercial nuclear power reactors. Refer to | |||
https://www.nrc.gov/reactors/operating/oversight.html for more information. Findings and | |||
violations being considered in the NRCs assessment are summarized in the tables below. | |||
List of Findings and Violations | |||
Failure to Identify and Correct a Broken Feedwater Chemistry Probe | |||
Cornerstone | |||
Significance | |||
Cross-cutting | |||
Aspect | |||
Report | |||
Section | |||
Barrier | |||
Integrity | |||
Green | |||
NCV 05000458/2018012-02 | |||
Closed | |||
None | |||
71152 - | |||
Problem | |||
Identification | |||
and | |||
Resolution | |||
Two examples of a self-revealed non-cited violation (NCV) of 10 CFR Part 50, Appendix B, | |||
Criterion XVI, Corrective Action, were identified for the licensees failure to identify that a | |||
broken chemistry probe in the feedwater system had the potential to cause an adverse impact | |||
on plant safety, and promptly implement appropriate measures to address that condition. | |||
Failure to Provide Adequate Procedures for Post-Scram Recovery | |||
Cornerstone | |||
Significance | |||
Cross-cutting | |||
Aspect | |||
Report | |||
Section | |||
Mitigating | |||
Systems | |||
Green | |||
NCV 05000458/2018012-06 | |||
Closed | |||
None | |||
71111.18 - | |||
Plant | |||
Modifications | |||
The inspectors reviewed a self-revealed, non-cited violation of Technical Specification 5.4.1.a for | |||
the licensees failure to establish, implement and maintain a procedure required by Regulatory | |||
Guide 1.33, Revision 2, Appendix A, dated February 1978. Specifically, Procedure OSP-0053, | |||
Emergency and Transient Response Support Procedure, Revision 22, which is required by | |||
Regulatory Guide 1.33, inappropriately directed operations personnel to establish feedwater flow | |||
to the reactor pressure vessel using the main feedwater regulating valve as part of the post- | |||
scram actions. This resulted in the main feedwater regulating valves being operated outside | |||
their design limits. This resulted in catastrophic failure of the main feedwater regulating valve | |||
variseals and subsequent damage to multiple fuel assemblies. | |||
Failure to Develop an Adequate Operational Decision-Making Issue for Compensatory Measures | |||
Related to a Degraded Condition of the Feedwater System Sparger Nozzles | |||
Cornerstone | 3 | ||
Failure to Develop an Adequate Operational Decision-Making Issue for Compensatory Measures | |||
Related to a Degraded Condition of the Feedwater System Sparger Nozzles | |||
Cornerstone | |||
Significance | |||
Cross-cutting | |||
Aspect | |||
The inspectors identified a Green non-cited violation of 10 CFR Part 50, Appendix B, Criterion V, | Report Section | ||
Instructions, Procedures, and Drawings, for the failure to develop an adequate Operational | Mitigating | ||
Systems | |||
Green | |||
NCV 05000458/2018012-05 | |||
Closed | |||
[H.9] - | |||
Human | |||
Performance, | |||
Training | |||
71111.15 - | |||
Operability | |||
Determinations | |||
and | |||
Functionality | |||
Assessment | |||
The inspectors identified a Green non-cited violation of 10 CFR Part 50, Appendix B, Criterion V, | |||
Instructions, Procedures, and Drawings, for the failure to develop an adequate Operational | |||
Decision-Making Issue (ODMI) document per Procedure EN-OP-111, Operational Decision- | Decision-Making Issue (ODMI) document per Procedure EN-OP-111, Operational Decision- | ||
Making Issue Process. Specifically, the licensee failed to develop an ODMI that provided | Making Issue Process. Specifically, the licensee failed to develop an ODMI that provided | ||
adequate guidance to the operators for safely operating the plant with degraded feedwater | adequate guidance to the operators for safely operating the plant with degraded feedwater | ||
sparger nozzles. | sparger nozzles. | ||
Failure to Establish Procedural Guidance for Determining Core Flow During Unanticipated | |||
Single Loop Operations | Failure to Establish Procedural Guidance for Determining Core Flow During Unanticipated | ||
Cornerstone | Single Loop Operations | ||
Cornerstone | |||
Initiating | Significance | ||
Cross-cutting | |||
Aspect | |||
Report | |||
Section | |||
Initiating | |||
The inspectors reviewed a self-revealed, non-cited violation of 10 CFR Part 50 Appendix B, | Events | ||
Criterion V, Instructions, Procedures, and Drawings, for the licensees failure to establish | Green | ||
appropriate instructions in the abnormal operating procedure for thermal hydraulic instabilities. | NCV 05000458/2018012-03 | ||
Specifically, the procedural step for determining core flow when in single loop operations at low | Closed | ||
power did not provide appropriate instructions to operators. As a result, station personnel could | [P.3] - | ||
not conclusively determine core flow and inserted a manual reactor scram. | Problem | ||
Failure to Perform 10 CFR 50.59 Evaluation for Main Feedwater System Sparger Nozzle | Identification | ||
Damage | and | ||
Cornerstone | Resolution, | ||
Resolution | |||
None | 71153 - | ||
Follow-up of | |||
Events and | |||
The inspectors identified a Severity Level IV non-cited violation of 10 CFR 50.59, Changes, | Notices of | ||
Tests, and Experiments, for the licensees failure to provide a written safety evaluation for the | Enforcement | ||
determination that operation with compensatory measures for damaged feedwater sparger | Discretion | ||
nozzles did not require a license amendment pursuant to 10 CFR 50.90, Application for | The inspectors reviewed a self-revealed, non-cited violation of 10 CFR Part 50 Appendix B, | ||
amendment of license, construction permit, or early site permit. Specifically, the licensee failed | Criterion V, Instructions, Procedures, and Drawings, for the licensees failure to establish | ||
to recognize that compensatory measures prohibiting operation in single loop conditions | appropriate instructions in the abnormal operating procedure for thermal hydraulic instabilities. | ||
required technical specification changes, and as such required prior NRC approval. | Specifically, the procedural step for determining core flow when in single loop operations at low | ||
power did not provide appropriate instructions to operators. As a result, station personnel could | |||
not conclusively determine core flow and inserted a manual reactor scram. | |||
Failure to Perform 10 CFR 50.59 Evaluation for Main Feedwater System Sparger Nozzle | |||
Damage | |||
Cornerstone | |||
Significance | |||
Cross-cutting | |||
Aspect | |||
Report | |||
Section | |||
None | |||
SL-IV | |||
NCV 05000458/2018012-07 | |||
Closed | |||
None | |||
71111.18 - | |||
Plant | |||
Modifications | |||
The inspectors identified a Severity Level IV non-cited violation of 10 CFR 50.59, Changes, | |||
Tests, and Experiments, for the licensees failure to provide a written safety evaluation for the | |||
determination that operation with compensatory measures for damaged feedwater sparger | |||
nozzles did not require a license amendment pursuant to 10 CFR 50.90, Application for | |||
amendment of license, construction permit, or early site permit. Specifically, the licensee failed | |||
to recognize that compensatory measures prohibiting operation in single loop conditions | |||
required technical specification changes, and as such required prior NRC approval. | |||
Failure to Conduct Adequate Transient Snap Shot Assessment Following Recirculation Pump | |||
Trip | |||
Cornerstone | 4 | ||
Initiating | Failure to Conduct Adequate Transient Snap Shot Assessment Following Recirculation Pump | ||
Trip | |||
Cornerstone | |||
Significance | |||
Cross-cutting | |||
The inspectors identified a finding for the licensees failure to adequately validate simulator | Aspect | ||
response during a transient snap shot assessment following an unexpected trip of reactor | Report | ||
recirculation pump A on December 19, 2012. | Section | ||
Failure to Submit a Licensee Event Report for a Manual Scram | Initiating | ||
Cornerstone | Events | ||
Green | |||
None | FIN 05000458/2018012-01 | ||
Closed | |||
None | |||
71152 - | |||
Problem | |||
Identification | |||
The inspectors identified a Severity Level IV non-cited violation of 10 CFR 50.73, Licensee | and | ||
Event Report System, for the licensees failure to submit a required licensee event report (LER). | Resolution | ||
Specifically, on February 1, 2018, after an unexpected trip of the recirculation pump B, the | The inspectors identified a finding for the licensees failure to adequately validate simulator | ||
licensee initiated a manual scram of the reactor that was not part of a preplanned sequence and | response during a transient snap shot assessment following an unexpected trip of reactor | ||
failed to submit an LER within 60 days. | recirculation pump A on December 19, 2012. | ||
Failure to Submit a Licensee Event Report for a Manual Scram | |||
Cornerstone | |||
Significance | |||
Cross-cutting | |||
Aspect | |||
Report | |||
Section | |||
None | |||
SL-IV | |||
NCV 05000458/2018012-04 | |||
Closed | |||
None | |||
71153 - | |||
Follow-up of | |||
Events and | |||
Notices of | |||
Enforcement | |||
Discretion | |||
The inspectors identified a Severity Level IV non-cited violation of 10 CFR 50.73, Licensee | |||
Event Report System, for the licensees failure to submit a required licensee event report (LER). | |||
Specifically, on February 1, 2018, after an unexpected trip of the recirculation pump B, the | |||
licensee initiated a manual scram of the reactor that was not part of a preplanned sequence and | |||
failed to submit an LER within 60 days. | |||
INSPECTION SCOPES | |||
Inspections were conducted using the appropriate portions of the inspection procedures (IPs) in | |||
effect at the beginning of the inspection unless otherwise noted. Currently approved IPs with | 5 | ||
INSPECTION SCOPES | |||
Inspections were conducted using the appropriate portions of the inspection procedures (IPs) in | |||
effect at the beginning of the inspection unless otherwise noted. Currently approved IPs with | |||
their attached revision histories are located on the public website at http://www.nrc.gov/reading- | their attached revision histories are located on the public website at http://www.nrc.gov/reading- | ||
rm/doc-collections/insp-manual/inspection-procedure/index.html. Samples were declared | rm/doc-collections/insp-manual/inspection-procedure/index.html. Samples were declared | ||
complete when the IP requirements most appropriate to the inspection activity were met | complete when the IP requirements most appropriate to the inspection activity were met | ||
consistent with Inspection Manual Chapter (IMC) 2515, Light-Water Reactor Inspection | consistent with Inspection Manual Chapter (IMC) 2515, Light-Water Reactor Inspection | ||
Program - Operations Phase. The inspectors reviewed selected procedures and records, | Program - Operations Phase. The inspectors reviewed selected procedures and records, | ||
observed activities, and interviewed personnel to assess licensee performance and compliance | observed activities, and interviewed personnel to assess licensee performance and compliance | ||
with Commission rules and regulations, license conditions, site procedures, and standards. | with Commission rules and regulations, license conditions, site procedures, and standards. | ||
REACTOR SAFETY | |||
71111.15Operability Determinations and Functionality Assessments (1 Sample) | REACTOR SAFETY | ||
71111.15Operability Determinations and Functionality Assessments (1 Sample) | |||
The inspectors evaluated the following operability determinations and functionality | |||
assessments: | |||
71111.18Plant Modifications (2 Samples) | (1) Review of Operational Decision-Making Issue (ODMI) associated with damaged | ||
feedwater sparger on February 8, 2018 | |||
71111.18Plant Modifications (2 Samples) | |||
The inspectors evaluated the following temporary or permanent modifications: | |||
OTHER ACTIVITIES - BASELINE | (1) OSP-0053, Emergency And Transient Response Support Procedure, following | ||
71152Problem Identification and Resolution | decision to control reactor vessel level with main feedwater regulating valves during | ||
post-scram operations | |||
(2) Review of plant operation following modification to feedwater sparger nozzles 7 and 8 | |||
OTHER ACTIVITIES - BASELINE | |||
71152Problem Identification and Resolution | |||
Annual Follow-up of Selected Issues (3 Samples) | |||
The inspectors reviewed the licensees implementation of its corrective action program | |||
related to the following issues: | |||
(1) Review of 1) simulator modelling of core parameters during a recirculation pump trip at | |||
low power and 2) licensed operator training associated with single loop operations at low | |||
power | |||
(2) Actions to address a broken isokinetic chemistry sampling probe in the feedwater | |||
system | |||
(3) Actions to address fuel failures caused by debris material in the reactor vessel | |||
71153Follow-up of Events and Notices of Enforcement Discretion | |||
6 | |||
INSPECTION RESULTS | 71153Follow-up of Events and Notices of Enforcement Discretion | ||
Personnel Performance (1 Sample) | |||
(1) The inspectors evaluated operator response to the unexpected trip of the reactor | |||
recirculation pump B on February 1, 2018. | |||
INSPECTION RESULTS | |||
Failure to Identify and Correct a Broken Feedwater System Chemistry Probe | |||
Cornerstone | |||
Significance | |||
Cross-cutting | |||
Aspect | |||
Report | |||
Section | |||
Barrier | |||
In 1999, the licensee initiated Condition Report CR-RBS-1999-1011 to document that an | Integrity | ||
Green | |||
NCV 05000458/2018012-02 | |||
Closed | |||
None | |||
71152 - | |||
Problem | |||
Identification | |||
and | |||
Resolution | |||
Two examples of a self-revealed Green finding and associated NCV of 10 CFR Part 50, | |||
Appendix B, Criterion XVI, were identified for the licensees failure to identify that a broken | |||
chemistry probe in the feedwater system had the potential to cause an adverse impact on | |||
In March 2004, the NRC issued Information Notice (IN) 2004-06, Loss of Feedwater | plant safety, and promptly implement appropriate measures to address that condition. | ||
Description: | |||
In 1999, the licensee initiated Condition Report CR-RBS-1999-1011 to document that an | |||
isokinetic chemistry sample probe was found to be missing from its installed location in the | |||
feedwater system, having broken off in the system. Following unsuccessful attempts to | |||
locate and remove the missing probe, the licensee performed evaluation ER-99-0539 to | |||
evaluate the potential impact of the missing probe on the continued operation and function of | |||
feedwater system components. This evaluation concluded that the missing probe remaining | |||
in the system would not present any hazard to any feedwater system components, and would | |||
have no adverse effect on continued operation. This conclusion was based, in part, on a | |||
calculation showing that feedwater flow would not have enough energy to levitate the probe | |||
past a 20-foot vertical riser portion of the system, and therefore would not have the potential | |||
to enter a feedwater sparger in the reactor vessel downstream of the vertical riser. Another | |||
calculation showed that the impact energy of the loose probe on any feedwater components | |||
would be negligible. | |||
In March 2004, the NRC issued Information Notice (IN) 2004-06, Loss of Feedwater | |||
Isokinetic Sampling Probes at Dresden Units 2 and 3 (ADAMS Accession No. | |||
ML040711214). The IN discussed that broken probes had been discovered at five other | |||
stations from 1990 to 2001, and further described the conditions discovered at Dresden | |||
Nuclear Power Station (Dresden), Units 2 and 3. In 2003, three holes in a feedwater sparger | |||
at Dresden Unit 2 were discovered, along with the missing feedwater probe in the sparger, | |||
which had apparently caused the damage. Two probes were discovered to be in a feedwater | |||
sparger in Dresden Unit 3, with no damage to the sparger having occurred yet. These | |||
conditions demonstrated that not only could the probes be transported to the feedwater | |||
spargers in the reactor vessel, but that they could potentially damage the spargers. The | |||
licensees evaluation of this operating experience concluded that, since the broken probe at | |||
River Bend had been replaced with a probe of a design not susceptible to the same failure, | |||
no further action was needed. The licensee failed to address the potential impacts of the | |||
adverse condition of the broken probe that remained loose in the feedwater system. | |||
In 2011, the licensee documented an evaluation of a similar condition that had been | |||
discovered at Brunswick Steam Electric Plant, Unit 2, where a feedwater sample probe was | |||
discovered inside a feedwater sparger. The licensees evaluation of this operating | 7 | ||
experience concluded that the current design (i.e. the probe that replaced the previous | |||
broken probe) was not susceptible to this kind of failure. The licensee again failed to address | In 2011, the licensee documented an evaluation of a similar condition that had been | ||
the impact of the previous broken probe that remained in the system, given that its potential | discovered at Brunswick Steam Electric Plant, Unit 2, where a feedwater sample probe was | ||
to be transported into a feedwater sparger in the reactor vessel had been shown. | discovered inside a feedwater sparger. The licensees evaluation of this operating | ||
In January 2018, the licensee discovered damage in the form of two holes in feedwater | experience concluded that the current design (i.e. the probe that replaced the previous | ||
sparger nozzles in the reactor vessel, with the broken probe protruding from one of the holes | broken probe) was not susceptible to this kind of failure. The licensee again failed to address | ||
in the direction of the other. The broken probe remaining in the feedwater system resulted in | the impact of the previous broken probe that remained in the system, given that its potential | ||
potential adverse impacts on the reactor vessel wall due to impingement of feedwater flow | to be transported into a feedwater sparger in the reactor vessel had been shown. | ||
through the holes in the damaged sparger, as well as potential adverse impacts on the | |||
integrity of fuel cladding due to the introduction of foreign material (pieces of the feedwater | In January 2018, the licensee discovered damage in the form of two holes in feedwater | ||
sparger and chemistry probe) in the reactor vessel. | sparger nozzles in the reactor vessel, with the broken probe protruding from one of the holes | ||
Corrective Actions: The broken probe was removed from the system. The licensee | in the direction of the other. The broken probe remaining in the feedwater system resulted in | ||
performed evaluations to identify plant operational limitations to ensure that adverse impacts | potential adverse impacts on the reactor vessel wall due to impingement of feedwater flow | ||
to reactor pressure vessel wall integrity from additional holes in a feedwater sparger are | through the holes in the damaged sparger, as well as potential adverse impacts on the | ||
minimized. The licensee also issued an action to perform a review of historical loose parts | integrity of fuel cladding due to the introduction of foreign material (pieces of the feedwater | ||
evaluations to add to tracking mechanisms and ensure adequacy of previous evaluations. | sparger and chemistry probe) in the reactor vessel. | ||
Corrective Action Reference: CR-RBS-2018-0294, CR-RBS-2018-0613, and | |||
CR-RBS-2017-2828. | Corrective Actions: The broken probe was removed from the system. The licensee | ||
Performance Assessment: | performed evaluations to identify plant operational limitations to ensure that adverse impacts | ||
Performance Deficiency: The licensees failure on two occasions to identify a broken | to reactor pressure vessel wall integrity from additional holes in a feedwater sparger are | ||
chemistry probe in the feedwater system had the potential to cause an adverse impact on | minimized. The licensee also issued an action to perform a review of historical loose parts | ||
plant safety and to promptly implement appropriate measures to address that condition was a | evaluations to add to tracking mechanisms and ensure adequacy of previous evaluations. | ||
performance deficiency. | |||
Screening: The inspectors determined the performance deficiency was more than minor | Corrective Action Reference: CR-RBS-2018-0294, CR-RBS-2018-0613, and | ||
because it was associated with the Cladding Performance, as well as the RCS Equipment | CR-RBS-2017-2828. | ||
and Barrier Performance, attributes of the Barrier Integrity Cornerstone, and adversely | Performance Assessment: | ||
impacted the cornerstone objective to provide reasonable assurance that physical design | |||
barriers (fuel cladding, reactor coolant system, and containment) protect the public from | Performance Deficiency: The licensees failure on two occasions to identify a broken | ||
radionuclide releases caused by accidents or events. Specifically, the unaddressed condition | chemistry probe in the feedwater system had the potential to cause an adverse impact on | ||
of the broken probe remaining in the feedwater system resulted in damage to the feedwater | plant safety and to promptly implement appropriate measures to address that condition was a | ||
sparger, which resulted in thermal stresses to the reactor pressure vessel due to feedwater | performance deficiency. | ||
impingement on the inner reactor pressure vessel wall, as well as the introduction of foreign | |||
material inside the reactor vessel having the potential to result in damaged fuel. The licensee | Screening: The inspectors determined the performance deficiency was more than minor | ||
performed an evaluation to determine what plant operational limitations were necessary in | because it was associated with the Cladding Performance, as well as the RCS Equipment | ||
order to ensure that additional thermal stresses on the reactor pressure vessel inner wall | and Barrier Performance, attributes of the Barrier Integrity Cornerstone, and adversely | ||
remained below a threshold that would challenge the structural integrity of the vessel. | impacted the cornerstone objective to provide reasonable assurance that physical design | ||
Significance: In accordance with Inspection Manual Chapter 0609, Appendix A, Section 5.0, | barriers (fuel cladding, reactor coolant system, and containment) protect the public from | ||
RCS boundary issues other than pressurized thermal shock are evaluated under the Initiating | radionuclide releases caused by accidents or events. Specifically, the unaddressed condition | ||
Events Cornerstone. Using Inspection Manual Chapter 0609, Appendix A, The Significance | of the broken probe remaining in the feedwater system resulted in damage to the feedwater | ||
Determination Process for Findings At-Power, Exhibit 1, Initiating Events Screening | sparger, which resulted in thermal stresses to the reactor pressure vessel due to feedwater | ||
Questions, the finding was screened, as a potential loss of coolant accident (LOCA) initiator, | impingement on the inner reactor pressure vessel wall, as well as the introduction of foreign | ||
as having very low safety significance (Green) because, after a reasonable assessment of | material inside the reactor vessel having the potential to result in damaged fuel. The licensee | ||
performed an evaluation to determine what plant operational limitations were necessary in | |||
order to ensure that additional thermal stresses on the reactor pressure vessel inner wall | |||
remained below a threshold that would challenge the structural integrity of the vessel. | |||
Significance: In accordance with Inspection Manual Chapter 0609, Appendix A, Section 5.0, | |||
RCS boundary issues other than pressurized thermal shock are evaluated under the Initiating | |||
Events Cornerstone. Using Inspection Manual Chapter 0609, Appendix A, The Significance | |||
Determination Process for Findings At-Power, Exhibit 1, Initiating Events Screening | |||
Questions, the finding was screened, as a potential loss of coolant accident (LOCA) initiator, | |||
as having very low safety significance (Green) because, after a reasonable assessment of | |||
degradation, the finding could not result in exceeding the RCS leak rate for a small LOCA and | |||
could not have likely affected other systems used to mitigate a LOCA. | |||
Cross-cutting Aspect: A cross-cutting aspect of P.5, Operating Experience, was determined | 8 | ||
to be applicable to the performance deficiencies; however, no cross-cutting aspect was | |||
assigned since the performance deficiencies occurred in 2004 and 2011, and are not | degradation, the finding could not result in exceeding the RCS leak rate for a small LOCA and | ||
indicative of current licensee performance. | could not have likely affected other systems used to mitigate a LOCA. | ||
Enforcement: | |||
Violation: Title 10 CFR Part 50, Appendix B, Criterion XVI, requires, in part, that measures | Cross-cutting Aspect: A cross-cutting aspect of P.5, Operating Experience, was determined | ||
shall be established to assure that conditions adverse to quality, such as failures, | to be applicable to the performance deficiencies; however, no cross-cutting aspect was | ||
malfunctions, deficiencies, deviations, defective material and equipment, and | assigned since the performance deficiencies occurred in 2004 and 2011, and are not | ||
nonconformances are promptly identified and corrected. Contrary to the above, from | indicative of current licensee performance. | ||
June 2004 to January 2018, the licensee failed to establish measures to assure that a | Enforcement: | ||
condition adverse to quality was promptly identified and corrected. Specifically, the licensee | |||
failed to identify and correct a condition involving a broken sampling probe inside the | Violation: Title 10 CFR Part 50, Appendix B, Criterion XVI, requires, in part, that measures | ||
feedwater system. The uncorrected condition resulted in damage to a feedwater sparger, | shall be established to assure that conditions adverse to quality, such as failures, | ||
with the potential to impact the available margin for integrity of the reactor vessel. | malfunctions, deficiencies, deviations, defective material and equipment, and | ||
Disposition: This violation is being treated as a non-cited violation, consistent with | nonconformances are promptly identified and corrected. Contrary to the above, from | ||
Section 2.3.2.a of the Enforcement Policy. | June 2004 to January 2018, the licensee failed to establish measures to assure that a | ||
Failure to Provide Adequate Procedures for Post-Scram Recovery | condition adverse to quality was promptly identified and corrected. Specifically, the licensee | ||
Cornerstone | failed to identify and correct a condition involving a broken sampling probe inside the | ||
feedwater system. The uncorrected condition resulted in damage to a feedwater sparger, | |||
Mitigating | with the potential to impact the available margin for integrity of the reactor vessel. | ||
Disposition: This violation is being treated as a non-cited violation, consistent with | |||
The inspectors reviewed a self-revealing, non-cited violation of Technical Specification 5.4.1.a | Section 2.3.2.a of the Enforcement Policy. | ||
for the licensees failure to establish, implement and maintain a procedure required by | |||
Regulatory Guide 1.33, Revision 2, Appendix A, dated February 1978. Specifically, | Failure to Provide Adequate Procedures for Post-Scram Recovery | ||
Procedure OSP-0053, Emergency and Transient Response Support Procedure, | Cornerstone | ||
Revision 22, which is required by Regulatory Guide 1.33, inappropriately directed operations | Significance | ||
personnel to establish feedwater flow to the reactor pressure vessel using the main feedwater | Cross-cutting | ||
regulating valve (MFRV) as part of the post-scram actions. This resulted in the MFRVs being | Aspect | ||
operated outside their design limits. This resulted in catastrophic failure of the MFRV | Report | ||
variseals and subsequent damage to multiple fuel assemblies. | Section | ||
Description: | Mitigating | ||
In January 2015, the licensee revised Procedure OSP-0053, Emergency And Transient | Systems | ||
Response Support Procedure, to use one of the three MFRVs to control reactor water level | Green | ||
following a scram event, and not use C33-LVF002, Start-Up FRV, which is designed to be | NCV 05000458/2018012-06 | ||
used for this application. This resulted in proceduralizing the use of a MFRV in circumstances | Closed | ||
below the minimum controllable flow for the MFRV of 209,000 lbs/hr that the Main FRV | None | ||
Copes Vulcan sizing datasheet provides as the a minimum controllable flow condition. As a | 71111.18 - | ||
result of this change to the procedure to use a MFRV, the valves cycled numerous times in | Plant | ||
the process of controlling level at low flow post-scram when feedwater flow demand was | Modifications | ||
below the MFRV minimum controllable flow volume. This repeated cycling of the valve led to | The inspectors reviewed a self-revealing, non-cited violation of Technical Specification 5.4.1.a | ||
excessive open/close cycling of the MFRVs and caused the catastrophic failure of the | for the licensees failure to establish, implement and maintain a procedure required by | ||
variseals. | Regulatory Guide 1.33, Revision 2, Appendix A, dated February 1978. Specifically, | ||
Procedure OSP-0053, Emergency and Transient Response Support Procedure, | |||
Revision 22, which is required by Regulatory Guide 1.33, inappropriately directed operations | |||
personnel to establish feedwater flow to the reactor pressure vessel using the main feedwater | |||
regulating valve (MFRV) as part of the post-scram actions. This resulted in the MFRVs being | |||
operated outside their design limits. This resulted in catastrophic failure of the MFRV | |||
variseals and subsequent damage to multiple fuel assemblies. | |||
Description: | |||
In January 2015, the licensee revised Procedure OSP-0053, Emergency And Transient | |||
Response Support Procedure, to use one of the three MFRVs to control reactor water level | |||
following a scram event, and not use C33-LVF002, Start-Up FRV, which is designed to be | |||
used for this application. This resulted in proceduralizing the use of a MFRV in circumstances | |||
below the minimum controllable flow for the MFRV of 209,000 lbs/hr that the Main FRV | |||
Copes Vulcan sizing datasheet provides as the a minimum controllable flow condition. As a | |||
result of this change to the procedure to use a MFRV, the valves cycled numerous times in | |||
the process of controlling level at low flow post-scram when feedwater flow demand was | |||
below the MFRV minimum controllable flow volume. This repeated cycling of the valve led to | |||
excessive open/close cycling of the MFRVs and caused the catastrophic failure of the | |||
variseals. | |||
As a result, foreign material parts of the variseal were introduced into the core. It is | |||
suspected that this material resulted in six nuclear fuel cladding failures caused by debris | |||
fretting. | 9 | ||
Corrective Actions: The licensee revised Procedure OSP-0053, Emergency and Transient | |||
Response Support Procedure, to control reactor vessel level post scram using a startup | As a result, foreign material parts of the variseal were introduced into the core. It is | ||
feedwater regulating valve and modified the design of the MFRV variseal. | suspected that this material resulted in six nuclear fuel cladding failures caused by debris | ||
Corrective Action Reference: CR-RBS-2016-00893 | fretting. | ||
Performance Assessment: | |||
Performance Deficiency: The failure to establish adequate procedural guidance for operation | Corrective Actions: The licensee revised Procedure OSP-0053, Emergency and Transient | ||
of the main feedwater system was a performance deficiency. | Response Support Procedure, to control reactor vessel level post scram using a startup | ||
Screening: The performance deficiency was more than minor, and therefore a finding, | feedwater regulating valve and modified the design of the MFRV variseal. | ||
because it was associated with the procedure quality attribute of the Mitigating Systems | |||
Cornerstone and adversely affected the cornerstone objective to ensure the availability, | Corrective Action Reference: CR-RBS-2016-00893 | ||
reliability, and capability of systems that respond to initiating events to prevent undesirable | Performance Assessment: | ||
consequences. Specifically, Procedure OSP-0053, Emergency and Transient Response | |||
Support Procedure, Revision 22, inappropriately directed operations personnel to establish | Performance Deficiency: The failure to establish adequate procedural guidance for operation | ||
feedwater flow to the reactor pressure vessel using the MFRV as part of the post-scram | of the main feedwater system was a performance deficiency. | ||
actions. This resulted in the MFRVs being operated outside their design limits. | |||
Significance: The inspectors screened the finding in accordance with Inspection Manual | Screening: The performance deficiency was more than minor, and therefore a finding, | ||
Chapter 0609, Appendix A, The Significance Determination Process for (SDP) for Findings | because it was associated with the procedure quality attribute of the Mitigating Systems | ||
At-Power. Using Inspection Manual Chapter 0609, Appendix A, Exhibit 2, Mitigating | Cornerstone and adversely affected the cornerstone objective to ensure the availability, | ||
Systems Screening Questions, the inspectors determined this finding was of very low safety | reliability, and capability of systems that respond to initiating events to prevent undesirable | ||
significance (Green) because the finding: (1) was not a deficiency affecting the design or | consequences. Specifically, Procedure OSP-0053, Emergency and Transient Response | ||
qualification of a mitigating structure, system, or component, and did not result in a loss of | Support Procedure, Revision 22, inappropriately directed operations personnel to establish | ||
operability or functionality; (2) did not represent a loss of system and/or function; (3) did not | feedwater flow to the reactor pressure vessel using the MFRV as part of the post-scram | ||
represent an actual loss of function of at least a single train for longer than its technical | actions. This resulted in the MFRVs being operated outside their design limits. | ||
specification allowed outage time, or two separate safety systems out-of-service for longer | |||
than their technical specification allowed outage time; and (4) did not represent an actual loss | Significance: The inspectors screened the finding in accordance with Inspection Manual | ||
of function of one or more nontechnical specification trains of equipment designated as high | Chapter 0609, Appendix A, The Significance Determination Process for (SDP) for Findings | ||
safety-significant in accordance with the licensees maintenance rule program. | At-Power. Using Inspection Manual Chapter 0609, Appendix A, Exhibit 2, Mitigating | ||
Cross-cutting Aspect: No cross-cutting aspect was assigned since the performance | Systems Screening Questions, the inspectors determined this finding was of very low safety | ||
deficiency occurred in January 2015 and is not indicative of current licensee performance. | significance (Green) because the finding: (1) was not a deficiency affecting the design or | ||
Enforcement: | qualification of a mitigating structure, system, or component, and did not result in a loss of | ||
Violation: Technical Specification 5.4.1.a requires in part, that written procedures shall be | operability or functionality; (2) did not represent a loss of system and/or function; (3) did not | ||
established, implemented, and maintained covering the applicable procedures recommended | represent an actual loss of function of at least a single train for longer than its technical | ||
in Regulatory Guide 1.33, Revision 2, Appendix A, dated February 1978. Regulatory | specification allowed outage time, or two separate safety systems out-of-service for longer | ||
Guide 1.33, Appendix A, Section 6.u., identifies procedures for responding to a reactor trip as | than their technical specification allowed outage time; and (4) did not represent an actual loss | ||
required procedures. Procedure OSP-0053, Attachment 16, Post Scram | of function of one or more nontechnical specification trains of equipment designated as high | ||
Feedwater/Condensate Manipulations Below 5% Reactor Power, was a procedure | safety-significant in accordance with the licensees maintenance rule program. | ||
established by the licensee for responding to a reactor trip. | |||
Contrary to the above, from January 30, 2015, until April 13, 2017, the licensee failed to | Cross-cutting Aspect: No cross-cutting aspect was assigned since the performance | ||
maintain adequate written procedures for responding to a reactor trip. Specifically, | deficiency occurred in January 2015 and is not indicative of current licensee performance. | ||
Procedure OSP-0053 inappropriately directed operations personnel to establish feedwater | Enforcement: | ||
Violation: Technical Specification 5.4.1.a requires in part, that written procedures shall be | |||
established, implemented, and maintained covering the applicable procedures recommended | |||
in Regulatory Guide 1.33, Revision 2, Appendix A, dated February 1978. Regulatory | |||
Guide 1.33, Appendix A, Section 6.u., identifies procedures for responding to a reactor trip as | |||
required procedures. Procedure OSP-0053, Attachment 16, Post Scram | |||
Feedwater/Condensate Manipulations Below 5% Reactor Power, was a procedure | |||
established by the licensee for responding to a reactor trip. | |||
Contrary to the above, from January 30, 2015, until April 13, 2017, the licensee failed to | |||
maintain adequate written procedures for responding to a reactor trip. Specifically, | |||
Procedure OSP-0053 inappropriately directed operations personnel to establish feedwater | |||
flow to the reactor pressure vessel using the MFRV as part of the post-scram actions. The | |||
MFRV operator characteristics are not designed to operate at the low flow conditions | |||
immediately following a reactor scram from high power. As a result, the MFRV variseals | 10 | ||
degraded and resulted in damage to multiple fuel assemblies. Subsequent to the event, the | |||
licensee changed the procedure, directing operations personnel to utilize one of the startup | flow to the reactor pressure vessel using the MFRV as part of the post-scram actions. The | ||
feedwater regulating valves. | MFRV operator characteristics are not designed to operate at the low flow conditions | ||
Disposition: This violation is being treated as an non-cited violation consistent with | immediately following a reactor scram from high power. As a result, the MFRV variseals | ||
Section 2.3.2.a of the NRC Enforcement Policy. | degraded and resulted in damage to multiple fuel assemblies. Subsequent to the event, the | ||
Failure to Develop an Adequate Operational Decision-Making Issue for Compensatory | licensee changed the procedure, directing operations personnel to utilize one of the startup | ||
Measures Related to a Degraded Condition of the Feedwater System Sparger Nozzles | feedwater regulating valves. | ||
Cornerstone | |||
Disposition: This violation is being treated as an non-cited violation consistent with | |||
Section 2.3.2.a of the NRC Enforcement Policy. | |||
Failure to Develop an Adequate Operational Decision-Making Issue for Compensatory | |||
Measures Related to a Degraded Condition of the Feedwater System Sparger Nozzles | |||
Cornerstone | |||
Significance | |||
The inspectors identified a Green non-cited violation of 10 CFR Part 50, Appendix B, | Cross-cutting | ||
Criterion V, Instructions, Procedures, and Drawings, for the failure to develop an adequate | Aspect | ||
operational decision-making issue (ODMI) document per Procedure EN-OP-111, Operational | Report Section | ||
Decision-Making Issue Process. Specifically, the licensee failed to develop an ODMI that | Mitigating | ||
provided adequate guidance to the operators for safely operating the plant with degraded | Systems | ||
feedwater sparger nozzles. | Green | ||
Description: | NCV 05000458/2018012-05 | ||
During a reactor startup on February 1, 2018, reactor recirculation pump B unexpectedly | Closed | ||
tripped during an attempted upshift to fast speed. As a result, the plant was operating with | [H.9] - | ||
recirculation pump A in fast speed and recirculation pump B not running. Prior to this startup, | Human | ||
during an outage that was being conducted to replace failed fuel assemblies, damage to | Performance, | ||
feedwater sparger nozzles was identified. | Training | ||
Example 1: The evaluation of the damaged feedwater sparger nozzles 7 and 8 on | 71111.15 - | ||
sparger N4C identified that the damaged sections of the feedwater sparger nozzles had the | Operability | ||
potential to adversely affect the vessel cladding by allowing relatively colder water to directly | Determinations | ||
flow into the relatively hotter vessel wall, thus inducing thermal fatigue. All components of the | and | ||
reactor coolant system (RCS) are designed to withstand effects of cyclic loads due to system | Functionality | ||
pressure and temperature changes. These loads are introduced by startup (heatup) and | Assessments | ||
shutdown (cooldown) operations, power transients, and reactor trips. Limits are established | The inspectors identified a Green non-cited violation of 10 CFR Part 50, Appendix B, | ||
for pressure and temperature changes during RCS heatup and cooldown, such that plant | Criterion V, Instructions, Procedures, and Drawings, for the failure to develop an adequate | ||
systems remain within the design assumptions and the stress limits for cyclic operation. | operational decision-making issue (ODMI) document per Procedure EN-OP-111, Operational | ||
Limits on RCS pressure, temperature, heatup rate, and cooldown rate define allowable | Decision-Making Issue Process. Specifically, the licensee failed to develop an ODMI that | ||
operating regions and operating cycles to prevent nonductile failure of system components. | provided adequate guidance to the operators for safely operating the plant with degraded | ||
Because operation with the sparger nozzle damage was outside the limits originally analyzed, | feedwater sparger nozzles. | ||
the licensee requested General Electric-Hitachi (GEH) to provide an operability analysis of | Description: | ||
the degraded condition. GEH Report 004N6557, Revision 0, dated January 26, 2018, | |||
Operability Assessment of the River Bend Station Feedwater Sparger Assembly in the | During a reactor startup on February 1, 2018, reactor recirculation pump B unexpectedly | ||
January 2018 As-found Condition, stated, in part, this evaluation does not account for Final | tripped during an attempted upshift to fast speed. As a result, the plant was operating with | ||
recirculation pump A in fast speed and recirculation pump B not running. Prior to this startup, | |||
during an outage that was being conducted to replace failed fuel assemblies, damage to | |||
feedwater sparger nozzles was identified. | |||
Example 1: The evaluation of the damaged feedwater sparger nozzles 7 and 8 on | |||
sparger N4C identified that the damaged sections of the feedwater sparger nozzles had the | |||
potential to adversely affect the vessel cladding by allowing relatively colder water to directly | |||
flow into the relatively hotter vessel wall, thus inducing thermal fatigue. All components of the | |||
reactor coolant system (RCS) are designed to withstand effects of cyclic loads due to system | |||
pressure and temperature changes. These loads are introduced by startup (heatup) and | |||
shutdown (cooldown) operations, power transients, and reactor trips. Limits are established | |||
for pressure and temperature changes during RCS heatup and cooldown, such that plant | |||
systems remain within the design assumptions and the stress limits for cyclic operation. | |||
Limits on RCS pressure, temperature, heatup rate, and cooldown rate define allowable | |||
operating regions and operating cycles to prevent nonductile failure of system components. | |||
Because operation with the sparger nozzle damage was outside the limits originally analyzed, | |||
the licensee requested General Electric-Hitachi (GEH) to provide an operability analysis of | |||
the degraded condition. GEH Report 004N6557, Revision 0, dated January 26, 2018, | |||
Operability Assessment of the River Bend Station Feedwater Sparger Assembly in the | |||
January 2018 As-found Condition, stated, in part, this evaluation does not account for Final | |||
Feedwater Temperature Reduction (FFWTR), Feedwater Heater Out-of-Service (FWH OOS) | |||
conditions, nor Single Loop Operation (SLO) operating conditions. Based on this analysis, | |||
the licensees engineering department concluded that the recommended classification of this | 11 | ||
condition was OPERABLE-COMP MEAS (operable with compensatory measures), with the | |||
degraded/nonconforming condition being the holes in the feedwater sparger nozzles. Based | Feedwater Temperature Reduction (FFWTR), Feedwater Heater Out-of-Service (FWH OOS) | ||
on the results of this analysis, one of the operational restrictions/limitations stipulated in the | conditions, nor Single Loop Operation (SLO) operating conditions. Based on this analysis, | ||
licensees ODMI was that, RBS will not operate in Single Loop Operation (SLO). | the licensees engineering department concluded that the recommended classification of this | ||
The ODMI developed by the licensee included two trigger points: | condition was OPERABLE-COMP MEAS (operable with compensatory measures), with the | ||
Trigger Point 1: | degraded/nonconforming condition being the holes in the feedwater sparger nozzles. Based | ||
An unexpected operational state below approximately 85 percent power in which the vessel | on the results of this analysis, one of the operational restrictions/limitations stipulated in the | ||
wall-to-feedwater delta-T stabilizes at less than or equal to 154 degrees Fahrenheit (F), as | licensees ODMI was that, RBS will not operate in Single Loop Operation (SLO). | ||
detected by periodic monitoring during normal operations, OR due to a transient as defined | |||
above. | The ODMI developed by the licensee included two trigger points: | ||
Trigger Point 2: | |||
An unexpected operational state in which the vessel wall-to-feedwater delta-T stabilizes at | Trigger Point 1: | ||
greater than 154 degrees F, as detected by periodic monitoring during normal operations, OR | |||
due to a transient as defined above. | An unexpected operational state below approximately 85 percent power in which the vessel | ||
The ODMI failed to provide adequate guidance to the operators if they found themselves in | wall-to-feedwater delta-T stabilizes at less than or equal to 154 degrees Fahrenheit (F), as | ||
any of the conditions that GEH had listed as not being evaluated for continued operation with | detected by periodic monitoring during normal operations, OR due to a transient as defined | ||
the degraded condition. When reactor recirculation pump B failed to shift to fast speed at | above. | ||
9:46 a.m., the operators logged entry into Procedure GOP-004, Single Loop Operations. | |||
The plant was in single loop operating conditions, and remained there until 10:57 a.m. when | Trigger Point 2: | ||
the Mode switch was placed in shutdown. The ODMI failed to provide adequate guidance on | |||
the actions required if the plant entered any of the conditions that were not evaluated for the | An unexpected operational state in which the vessel wall-to-feedwater delta-T stabilizes at | ||
degraded sparger condition. In addition, the Just In Time Training given to the operators | greater than 154 degrees F, as detected by periodic monitoring during normal operations, OR | ||
prior to taking the watch to commence power operations with the degraded condition did not | due to a transient as defined above. | ||
address these issues either. As a result, rather than take prompt actions to place the plant in | |||
a known safe condition upon entry into single loop operations, the control room supervisor | The ODMI failed to provide adequate guidance to the operators if they found themselves in | ||
requested that GEH be contacted to determine if it was acceptable to remain in single loop | any of the conditions that GEH had listed as not being evaluated for continued operation with | ||
operations. | the degraded condition. When reactor recirculation pump B failed to shift to fast speed at | ||
Example 2: The evaluation of the damaged feedwater sparger nozzles 7 and 8 on | 9:46 a.m., the operators logged entry into Procedure GOP-004, Single Loop Operations. | ||
sparger N4C identified that the damaged sections of the feedwater sparger nozzles had the | The plant was in single loop operating conditions, and remained there until 10:57 a.m. when | ||
potential to adversely affect the B narrow range level instrument. The damage on feedwater | the Mode switch was placed in shutdown. The ODMI failed to provide adequate guidance on | ||
sparger N4C created unexpected feedwater flow paths in the reactor vessel during plant | the actions required if the plant entered any of the conditions that were not evaluated for the | ||
operation that had the potential to adversely affect the "B" variable leg reactor water level | degraded sparger condition. In addition, the Just In Time Training given to the operators | ||
instruments. There were two potential impacts of this condition on indicated level from | prior to taking the watch to commence power operations with the degraded condition did not | ||
narrow range level instruments that tap off of the B variable leg. Flow from the holes in the | address these issues either. As a result, rather than take prompt actions to place the plant in | ||
feedwater sparger nozzle elbows could flow across the variable leg nozzle opening at AZ | a known safe condition upon entry into single loop operations, the control room supervisor | ||
200 degrees (B Leg), lowering the pressure on the variable leg side of the differential | requested that GEH be contacted to determine if it was acceptable to remain in single loop | ||
pressure measurements, or the flow from the sparger nozzle damage could directly impact | operations. | ||
the B variable leg, increasing the pressure on the variable leg side of the differential pressure | |||
measurements. | Example 2: The evaluation of the damaged feedwater sparger nozzles 7 and 8 on | ||
sparger N4C identified that the damaged sections of the feedwater sparger nozzles had the | |||
potential to adversely affect the B narrow range level instrument. The damage on feedwater | |||
sparger N4C created unexpected feedwater flow paths in the reactor vessel during plant | |||
operation that had the potential to adversely affect the "B" variable leg reactor water level | |||
instruments. There were two potential impacts of this condition on indicated level from | |||
narrow range level instruments that tap off of the B variable leg. Flow from the holes in the | |||
feedwater sparger nozzle elbows could flow across the variable leg nozzle opening at AZ | |||
200 degrees (B Leg), lowering the pressure on the variable leg side of the differential | |||
pressure measurements, or the flow from the sparger nozzle damage could directly impact | |||
the B variable leg, increasing the pressure on the variable leg side of the differential pressure | |||
measurements. | |||
The narrow range RPV level instrumentation supports two reactor water level trips: low level | |||
(Level 3) and high level (Level 8). During a transient or accident event where the RPV water | |||
level is changing, the trip signal from the B narrow range instrument could be affected. | 12 | ||
Based on the GE report, during a transient or accident event where the RPV water level is | |||
increasing, the high level (Level 8) trips (RPS trip and Feedwater Pump trip) in the affected | The narrow range RPV level instrumentation supports two reactor water level trips: low level | ||
channel may occur later than the trips in the unaffected channels. This may delay the overall | (Level 3) and high level (Level 8). During a transient or accident event where the RPV water | ||
Level 8 trips. For the Level 8 RPS trip, the margin between the calculated nominal trip | level is changing, the trip signal from the B narrow range instrument could be affected. | ||
setpoint and the technical specification allowable value is 0.77 inches. For the Level 3 RPS | |||
trip, the margin between the calculated nominal trip setpoint and the technical specification | Based on the GE report, during a transient or accident event where the RPV water level is | ||
allowable value is 0.67 inches. An operability determination of the narrow range level | increasing, the high level (Level 8) trips (RPS trip and Feedwater Pump trip) in the affected | ||
instruments was performed under CR-RBS-2018-00633 CA-01. | channel may occur later than the trips in the unaffected channels. This may delay the overall | ||
The ODMI developed by the licensee included two trigger points: | Level 8 trips. For the Level 8 RPS trip, the margin between the calculated nominal trip | ||
Trigger Point 1: | setpoint and the technical specification allowable value is 0.77 inches. For the Level 3 RPS | ||
Action: Refer to applicable SRs as specified by STP-000-0001, Att. 9.2 | trip, the margin between the calculated nominal trip setpoint and the technical specification | ||
allowable value is 0.67 inches. An operability determination of the narrow range level | |||
instruments was performed under CR-RBS-2018-00633 CA-01. | |||
Notify the Duty Manager and the Ops Duty Manager | |||
Trigger Point 2: | The ODMI developed by the licensee included two trigger points: | ||
The magnitude of the B channel deviation is 1.5 inches in either direction from the average | |||
of the A, C and D channel average + 1.1 inches. | Trigger Point 1: | ||
Notify the Duty Manager and the Engineering Duty Manager. | Action: Refer to applicable SRs as specified by STP-000-0001, Att. 9.2 | ||
The ODMI implemented by the licensee allowed level indication deviation in the affected | Step 30 in STP-000-0001 not within 4 inches | ||
channel for the B21-LTN080 instruments to be monitored to ensure it remained within the | Step 71 in STP-000-0001 not within 6 inches | ||
allowable margin to ensure the technical specification trip limit is not exceeded. It stated in | Notify the Duty Manager and the Ops Duty Manager | ||
part that, If the deviation exceeds a change of 1.5 inches from historical deviation of | |||
1.1 inches above the average of the A, C, and D channels in either an increasing or | Trigger Point 2: | ||
decreasing direction, then condition will be evaluated by engineering. The monitored trigger | The magnitude of the B channel deviation is 1.5 inches in either direction from the average | ||
point of +1.5 inches will provide adequate margin for both the Level 3 and Level 8 trips. | of the A, C and D channel average + 1.1 inches. | ||
However, if a 1.5-inch bias in the low direction would have been reached, two Technical | Notify the Duty Manager and the Engineering Duty Manager. | ||
Specification (TS) Allowable Values could have been exceeded (by 0.5 inches for TS | |||
Table 3.3.5.2-1, Function 2, Reactor Core Isolation Cooling System Instrumentation, and by | The ODMI implemented by the licensee allowed level indication deviation in the affected | ||
0.49 inches for TS Table 3.3.5.2-1, Function 5, Reactor Protection System Instrumentation). | channel for the B21-LTN080 instruments to be monitored to ensure it remained within the | ||
The 1.5-inch bias in the low direction would have rendered the instrument inoperable based | allowable margin to ensure the technical specification trip limit is not exceeded. It stated in | ||
on 10 CFR 50.36(c)(2)(i), which states, Limiting conditions for operation are the lowest | part that, If the deviation exceeds a change of 1.5 inches from historical deviation of | ||
functional capability or performance levels of equipment required for safe operation of the | 1.1 inches above the average of the A, C, and D channels in either an increasing or | ||
facility. Since the limiting conditions for operations (LCOs) include Allowable Values (e.g., | decreasing direction, then condition will be evaluated by engineering. The monitored trigger | ||
LCO 3.3.5.2 includes Table 3.3.5.2-1 which has Allowable Values for Functions 2 and 5), the | point of +1.5 inches will provide adequate margin for both the Level 3 and Level 8 trips. | ||
Allowable Values are understood to be the lowest functional capability or performance levels | However, if a 1.5-inch bias in the low direction would have been reached, two Technical | ||
of equipment required for safe operation of the facility. | Specification (TS) Allowable Values could have been exceeded (by 0.5 inches for TS | ||
The licensees technical specifications provide the following guidance: Surveillance | Table 3.3.5.2-1, Function 2, Reactor Core Isolation Cooling System Instrumentation, and by | ||
Requirement 3.0.1, Failure to meet a Surveillance, whether such failure is experienced | 0.49 inches for TS Table 3.3.5.2-1, Function 5, Reactor Protection System Instrumentation). | ||
during the performance of the Surveillance or between performances of the Surveillance, | The 1.5-inch bias in the low direction would have rendered the instrument inoperable based | ||
shall be failure to meet the LCO. | on 10 CFR 50.36(c)(2)(i), which states, Limiting conditions for operation are the lowest | ||
functional capability or performance levels of equipment required for safe operation of the | |||
facility. Since the limiting conditions for operations (LCOs) include Allowable Values (e.g., | |||
LCO 3.3.5.2 includes Table 3.3.5.2-1 which has Allowable Values for Functions 2 and 5), the | |||
Allowable Values are understood to be the lowest functional capability or performance levels | |||
of equipment required for safe operation of the facility. | |||
The licensees technical specifications provide the following guidance: Surveillance | |||
Requirement 3.0.1, Failure to meet a Surveillance, whether such failure is experienced | |||
during the performance of the Surveillance or between performances of the Surveillance, | |||
shall be failure to meet the LCO. | |||
1.1 Definitions: A CHANNEL CALIBRATION shall be the adjustment, as necessary, of the | |||
channel output such that it responds within the necessary range and accuracy to known | |||
values of the parameter that the channel monitors | 13 | ||
In addition, the TS Bases state, SR 3.0.1 through SR 3.0.4 establish the general | |||
requirements applicable to all Specifications and apply at all times, unless otherwise stated. | 1.1 Definitions: A CHANNEL CALIBRATION shall be the adjustment, as necessary, of the | ||
The OPERABILITY of the RPS (Reactor Protection System) is dependent on the | channel output such that it responds within the necessary range and accuracy to known | ||
OPERABILITY of the individual instrumentation channel Functions specified in | values of the parameter that the channel monitors | ||
Table 3.3.1.1-1. Each Function must have a required number of OPERABLE channels [2 per | |||
RPS trip system for the vessel level function] per RPS trip system, with their setpoints within | In addition, the TS Bases state, SR 3.0.1 through SR 3.0.4 establish the general | ||
the specified Allowable Value, where appropriate. The actual setpoint is calibrated consistent | requirements applicable to all Specifications and apply at all times, unless otherwise stated. | ||
with applicable setpoint methodology assumptions. Each channel must also respond within | The OPERABILITY of the RPS (Reactor Protection System) is dependent on the | ||
its assumed response time. Allowable Values are specified for each RPS Function specified | OPERABILITY of the individual instrumentation channel Functions specified in | ||
in the Table. Nominal trip setpoints are specified in the setpoint calculations. The nominal | Table 3.3.1.1-1. Each Function must have a required number of OPERABLE channels [2 per | ||
setpoints are selected to ensure that the actual setpoints do not exceed the Allowable Value | RPS trip system for the vessel level function] per RPS trip system, with their setpoints within | ||
between successive channel calibrations. Operation with a trip setpoint less conservative | the specified Allowable Value, where appropriate. The actual setpoint is calibrated consistent | ||
than the nominal trip setpoint, but within its Allowable Value, is acceptable. A channel is | with applicable setpoint methodology assumptions. Each channel must also respond within | ||
inoperable if its actual trip setpoint is not within its required Allowable Value. | its assumed response time. Allowable Values are specified for each RPS Function specified | ||
Process effects impact the establishment of the appropriate Nominal Trip Setpoint, which is | in the Table. Nominal trip setpoints are specified in the setpoint calculations. The nominal | ||
determined by addressing all instrument channel uncertainties (including biases) and | setpoints are selected to ensure that the actual setpoints do not exceed the Allowable Value | ||
offsetting them from the Analytical Limit. The currently licensed Allowable Values are fixed | between successive channel calibrations. Operation with a trip setpoint less conservative | ||
within the technical specification tables. Nominal Trip Setpoints are established on the basis | than the nominal trip setpoint, but within its Allowable Value, is acceptable. A channel is | ||
of a calculation that identifies all known uncertainties between the Analytical Limit and the | inoperable if its actual trip setpoint is not within its required Allowable Value. | ||
Nominal Trip Setpoint. If a new, unaccounted-for process effect bias in the nonconservative | |||
direction is discovered, this effect needs to be reflected in the calculation of a new Nominal | Process effects impact the establishment of the appropriate Nominal Trip Setpoint, which is | ||
Trip Setpoint and a corresponding new Allowable Value. However, in this case, the licensee | determined by addressing all instrument channel uncertainties (including biases) and | ||
did not elect to pursue a license amendment or other process to change its currently licensed | offsetting them from the Analytical Limit. The currently licensed Allowable Values are fixed | ||
Allowable Value, nor did it ask for a temporary enforcement discretion. Therefore, with the | within the technical specification tables. Nominal Trip Setpoints are established on the basis | ||
new (unaccounted for) postulated process effect present, this has the effect of making the | of a calculation that identifies all known uncertainties between the Analytical Limit and the | ||
existing Nominal Trip Setpoint (calibrated value) offset in the nonconservative direction by the | Nominal Trip Setpoint. If a new, unaccounted-for process effect bias in the nonconservative | ||
amount of the new postulated process effect (i.e., up to 1.5 inches), which reduces the margin | direction is discovered, this effect needs to be reflected in the calculation of a new Nominal | ||
between the actual trip setpoint and the existing licensed Allowable Value. | Trip Setpoint and a corresponding new Allowable Value. However, in this case, the licensee | ||
Therefore, to meet the River Bend technical specification requirement that a channel be | did not elect to pursue a license amendment or other process to change its currently licensed | ||
considered inoperable if its actual trip setpoint is not within its required Allowable Value | Allowable Value, nor did it ask for a temporary enforcement discretion. Therefore, with the | ||
without changing the currently licensed Allowable Value, only approximately a 1/2-inch of the | new (unaccounted for) postulated process effect present, this has the effect of making the | ||
1.5 inches of new postulated process effect can be accommodated between the existing | existing Nominal Trip Setpoint (calibrated value) offset in the nonconservative direction by the | ||
calibrated setpoint and the (existing) licensed Allowable Value. Thus, the direction to notify | amount of the new postulated process effect (i.e., up to 1.5 inches), which reduces the margin | ||
engineering only if the Rx vessel level indication bias had reached a value of 1.5 inches in | between the actual trip setpoint and the existing licensed Allowable Value. | ||
either direction was inadequate direction for the operating staff in order to ensure that the | |||
instruments remained operable. | Therefore, to meet the River Bend technical specification requirement that a channel be | ||
Corrective Actions: The licensee corrected the condition by revising the ODMI to include | considered inoperable if its actual trip setpoint is not within its required Allowable Value | ||
adequate operator guidance and trigger points. | without changing the currently licensed Allowable Value, only approximately a 1/2-inch of the | ||
Corrective Action Reference: CR-RBS-2018-03148 | 1.5 inches of new postulated process effect can be accommodated between the existing | ||
calibrated setpoint and the (existing) licensed Allowable Value. Thus, the direction to notify | |||
engineering only if the Rx vessel level indication bias had reached a value of 1.5 inches in | |||
either direction was inadequate direction for the operating staff in order to ensure that the | |||
instruments remained operable. | |||
Corrective Actions: The licensee corrected the condition by revising the ODMI to include | |||
adequate operator guidance and trigger points. | |||
Corrective Action Reference: CR-RBS-2018-03148 | |||
Performance Assessment: | |||
Performance Deficiency: The failure to establish ODMI guidance per Procedure EN-OP-111 | |||
to address the compensatory measures implemented to maintain operability of the plant with | 14 | ||
degraded feedwater sparger nozzles was a performance deficiency. | |||
Screening: For Example 1, the performance deficiency was more than minor, and therefore a | Performance Assessment: | ||
finding, because it was associated with the equipment reliability attribute of the Mitigating | |||
Systems Cornerstone and adversely affected the cornerstone objective to ensure the | Performance Deficiency: The failure to establish ODMI guidance per Procedure EN-OP-111 | ||
availability, reliability, and capability of systems that respond to initiating events to prevent | to address the compensatory measures implemented to maintain operability of the plant with | ||
undesirable consequences. Specifically, the licensee failed to provide adequate guidance to | degraded feedwater sparger nozzles was a performance deficiency. | ||
the operators for actions required if the plant inadvertently entered any of the unanalyzed | |||
conditions for continued operation with the degraded sparger. For Example 2, the | Screening: For Example 1, the performance deficiency was more than minor, and therefore a | ||
performance deficiency was more than minor, and therefore a finding, because if left | finding, because it was associated with the equipment reliability attribute of the Mitigating | ||
uncorrected it would have the potential to lead to a more significant safety concern. | Systems Cornerstone and adversely affected the cornerstone objective to ensure the | ||
Specifically, the use of less conservative calculated values than the Allowable Values stated | availability, reliability, and capability of systems that respond to initiating events to prevent | ||
in the facility TS as a basis for establishing a threshold for operability of TS equipment could | undesirable consequences. Specifically, the licensee failed to provide adequate guidance to | ||
result in the inappropriate evaluation of actual degraded conditions that impact the ability of | the operators for actions required if the plant inadvertently entered any of the unanalyzed | ||
components to perform their required safety functions. | conditions for continued operation with the degraded sparger. For Example 2, the | ||
Significance: The inspectors screened the finding in accordance with Inspection Manual | performance deficiency was more than minor, and therefore a finding, because if left | ||
Chapter 0609, Appendix A, The Significance Determination Process for (SDP) for Findings | uncorrected it would have the potential to lead to a more significant safety concern. | ||
At-Power. Using Inspection Manual Chapter 0609, Appendix A, Exhibit 1, Initiating Events | Specifically, the use of less conservative calculated values than the Allowable Values stated | ||
Screening Questions, the inspectors determined this finding was of very low safety | in the facility TS as a basis for establishing a threshold for operability of TS equipment could | ||
significance (Green) because for Example 1, the finding would not result in exceeding the | result in the inappropriate evaluation of actual degraded conditions that impact the ability of | ||
RCS leak rate for a small LOCA and could not have likely affected other systems used to | components to perform their required safety functions. | ||
mitigate a LOCA. For Example 2, it was not a design/qualification deficiency, did not | |||
represent a loss of system safety function, did not result in a loss of function of a single train | Significance: The inspectors screened the finding in accordance with Inspection Manual | ||
Chapter 0609, Appendix A, The Significance Determination Process for (SDP) for Findings | |||
At-Power. Using Inspection Manual Chapter 0609, Appendix A, Exhibit 1, Initiating Events | |||
Screening Questions, the inspectors determined this finding was of very low safety | |||
significance (Green) because for Example 1, the finding would not result in exceeding the | |||
RCS leak rate for a small LOCA and could not have likely affected other systems used to | |||
mitigate a LOCA. For Example 2, it was not a design/qualification deficiency, did not | |||
represent a loss of system safety function, did not result in a loss of function of a single train | |||
for greater than its TS-allowable outage time, did not result in a loss of function of nonsafety- | for greater than its TS-allowable outage time, did not result in a loss of function of nonsafety- | ||
related risk-significant equipment and was not risk significant due to external events. In | related risk-significant equipment and was not risk significant due to external events. In | ||
addition, no actual deviation of the B narrow range level instrument was observed during | addition, no actual deviation of the B narrow range level instrument was observed during | ||
plant startup on February 9, 2018. | plant startup on February 9, 2018. | ||
Cross-cutting Aspect: This finding had a cross-cutting aspect of human performance, change | |||
management H.3: Leaders use a systematic process for evaluating and implementing | Cross-cutting Aspect: This finding had a cross-cutting aspect of human performance, change | ||
change so that nuclear safety remains the overriding priority. Specifically, the licensee did | management H.3: Leaders use a systematic process for evaluating and implementing | ||
not use a systematic process to develop and verify the adequacy of the ODMIs associated | change so that nuclear safety remains the overriding priority. Specifically, the licensee did | ||
with the compensatory measures implemented for the degraded sparger. | not use a systematic process to develop and verify the adequacy of the ODMIs associated | ||
Enforcement: | with the compensatory measures implemented for the degraded sparger. | ||
Violation: Title 10 CFR Part 50, Appendix B, Criterion V, requires in part that, activities | Enforcement: | ||
affecting quality shall be prescribed by documented instructions, procedures, or drawings, of | |||
a type appropriate to the circumstances. Licensee Procedure EN-OP-111, Operational | Violation: Title 10 CFR Part 50, Appendix B, Criterion V, requires in part that, activities | ||
Decision-Making Issue (ODMI) Process, Revision 16, an Appendix B quality-related | affecting quality shall be prescribed by documented instructions, procedures, or drawings, of | ||
procedure, provides instructions for developing guidance for plant operation with | a type appropriate to the circumstances. Licensee Procedure EN-OP-111, Operational | ||
compensatory measures in place to maintain plant system operable with degraded | Decision-Making Issue (ODMI) Process, Revision 16, an Appendix B quality-related | ||
conditions. Procedure EN-OP-111, step 5.2.4, states that Operational Decision-Making | procedure, provides instructions for developing guidance for plant operation with | ||
Considerations should ensure that a course of action is selected based upon a critical | compensatory measures in place to maintain plant system operable with degraded | ||
consideration of risks and potential consequences, as well as a thorough understanding of | conditions. Procedure EN-OP-111, step 5.2.4, states that Operational Decision-Making | ||
alternate solutions. The final decision should be a deliberate act, providing clear direction, | Considerations should ensure that a course of action is selected based upon a critical | ||
trigger points, contingencies, and abort criteria. The Action Plans should provide clear | consideration of risks and potential consequences, as well as a thorough understanding of | ||
alternate solutions. The final decision should be a deliberate act, providing clear direction, | |||
trigger points, contingencies, and abort criteria. The Action Plans should provide clear | |||
guidance in each ODMI which delineate actions to be taken when conditions escalate | |||
unexpectedly, conditions are outside the scope of the ODMI analysis, or actions are not able | |||
to be implemented. Actions that contain recommendations to "consider or evaluate" in | 15 | ||
response to triggers should be avoided. When such actions are used, a definite period to | |||
finish the evaluation or consideration should be provided. | guidance in each ODMI which delineate actions to be taken when conditions escalate | ||
Contrary to the above, prior to February 1, 2018, the licensee failed to ensure that the ODMIs | unexpectedly, conditions are outside the scope of the ODMI analysis, or actions are not able | ||
provided a course of action based upon a critical consideration of risks and potential | to be implemented. Actions that contain recommendations to "consider or evaluate" in | ||
consequences, as well as a thorough understanding of alternate solutions; and that the final | response to triggers should be avoided. When such actions are used, a definite period to | ||
decision was a deliberate act providing clear direction, trigger points, contingencies, and abort | finish the evaluation or consideration should be provided. | ||
criteria. Specifically, the licensee failed to develop adequate guidance for the operators to | |||
maintain safe operation of the plant with compensatory measures in place for degraded | Contrary to the above, prior to February 1, 2018, the licensee failed to ensure that the ODMIs | ||
feedwater sparger nozzles. The action plans failed to provide clear guidance in each ODMI | provided a course of action based upon a critical consideration of risks and potential | ||
to delineate actions to be taken when conditions escalate unexpectedly; instead, the actions | consequences, as well as a thorough understanding of alternate solutions; and that the final | ||
specified directed the operators to consult with offsite contractors regarding the acceptability | decision was a deliberate act providing clear direction, trigger points, contingencies, and abort | ||
of allowing the plant to remain in operation with given conditions. | criteria. Specifically, the licensee failed to develop adequate guidance for the operators to | ||
Disposition: This violation is being treated as a non-cited violation, consistent with | maintain safe operation of the plant with compensatory measures in place for degraded | ||
Section 2.3.2.a of the NRC Enforcement Policy. | feedwater sparger nozzles. The action plans failed to provide clear guidance in each ODMI | ||
Failure to Establish Procedural Guidance for Determining Core Flow During Unanticipated | to delineate actions to be taken when conditions escalate unexpectedly; instead, the actions | ||
Single Loop Operations | specified directed the operators to consult with offsite contractors regarding the acceptability | ||
Cornerstone | of allowing the plant to remain in operation with given conditions. | ||
Initiating | Disposition: This violation is being treated as a non-cited violation, consistent with | ||
Section 2.3.2.a of the NRC Enforcement Policy. | |||
Failure to Establish Procedural Guidance for Determining Core Flow During Unanticipated | |||
Single Loop Operations | |||
Cornerstone | |||
The inspectors reviewed a self-revealed, non-cited violation of 10 CFR Part 50, Appendix B, | Significance | ||
Criterion V, Instructions, Procedures and Drawings, for the licensees failure to establish | Cross-cutting | ||
appropriate instructions in the abnormal operating procedure for thermal hydraulic | Aspect | ||
instabilities. Specifically, the procedural step for determining core flow when in single loop | Report | ||
operations at low power did not provide appropriate instructions to operators. As a result, | Section | ||
station personnel could not conclusively determine core flow and inserted a manual reactor | Initiating | ||
scram. | Events | ||
Description: | Green | ||
On February 1, 2018, with the unit in Mode 1 at approximately 27 percent power, reactor | NCV 05000458/2018012-03 | ||
recirculation pump B unexpectedly tripped during an upshift in the speed of the pump. As a | Closed | ||
result, the reactor was in a single loop configuration with the recirculation pump A running in | [P.3] - | ||
fast speed and the recirculation pump B not running. Operators entered Abnormal Operating | Problem | ||
Procedure AOP-0024, Thermal Hydraulic Instability Controls, Revision 30, as a result of the | Identification | ||
unplanned entry into single loop operations. Step 5.8 of this procedure directed operators to | and | ||
determine core flow and enter the General Operating Procedure GOP-004, for single loop | Resolution, | ||
operations. Step 5.8 also instructed operators to determine core flow using process computer | Resolution | ||
point B33NA01V when in a configuration with one recirculation pump in fast speed and one | 71153 - | ||
recirculation pump off. Control room operators observed the value of this data point as | Follow-up of | ||
13.9 Mlbm/hr. The operators concluded that this value was not valid since the indicated flow | Events and | ||
Notices of | |||
Enforcement | |||
Discretion | |||
The inspectors reviewed a self-revealed, non-cited violation of 10 CFR Part 50, Appendix B, | |||
Criterion V, Instructions, Procedures and Drawings, for the licensees failure to establish | |||
appropriate instructions in the abnormal operating procedure for thermal hydraulic | |||
instabilities. Specifically, the procedural step for determining core flow when in single loop | |||
operations at low power did not provide appropriate instructions to operators. As a result, | |||
station personnel could not conclusively determine core flow and inserted a manual reactor | |||
scram. | |||
Description: | |||
On February 1, 2018, with the unit in Mode 1 at approximately 27 percent power, reactor | |||
recirculation pump B unexpectedly tripped during an upshift in the speed of the pump. As a | |||
result, the reactor was in a single loop configuration with the recirculation pump A running in | |||
fast speed and the recirculation pump B not running. Operators entered Abnormal Operating | |||
Procedure AOP-0024, Thermal Hydraulic Instability Controls, Revision 30, as a result of the | |||
unplanned entry into single loop operations. Step 5.8 of this procedure directed operators to | |||
determine core flow and enter the General Operating Procedure GOP-004, for single loop | |||
operations. Step 5.8 also instructed operators to determine core flow using process computer | |||
point B33NA01V when in a configuration with one recirculation pump in fast speed and one | |||
recirculation pump off. Control room operators observed the value of this data point as | |||
13.9 Mlbm/hr. The operators concluded that this value was not valid since the indicated flow | |||
was much lower than expected with one recirculation pump running in fast speed. The | |||
operators then observed a value of 27.3 Mlbm/hr core flow using the ERIS data point for | |||
B33NA01V. This value appeared to be a valid number based on the single loop operation | 16 | ||
power/flow map contained in AOP-0024, Attachment 2. Normal data points are displayed in | |||
ERIS with a white text, but control room operators observed the ERIS data point displayed in | was much lower than expected with one recirculation pump running in fast speed. The | ||
a magenta color. Additionally, the word suspect appeared adjacent to the data point for | operators then observed a value of 27.3 Mlbm/hr core flow using the ERIS data point for | ||
core flow. Control room operators contacted information technology personnel and attempted | B33NA01V. This value appeared to be a valid number based on the single loop operation | ||
to understand the magenta color and suspect information associated with the core flow data | power/flow map contained in AOP-0024, Attachment 2. Normal data points are displayed in | ||
point. Concurrently, operators attempted to validate core flow using alternate means but | ERIS with a white text, but control room operators observed the ERIS data point displayed in | ||
were unsuccessful as the alternate indications did not provide accurate core flow readings at | a magenta color. Additionally, the word suspect appeared adjacent to the data point for | ||
low reactor power when in a single loop configuration. After approximately one hour spent | core flow. Control room operators contacted information technology personnel and attempted | ||
seeking to understand the unfamiliar indication associated with B33NA01V, control room | to understand the magenta color and suspect information associated with the core flow data | ||
operators conducted a brief and made the decision to shut down the unit due to the | point. Concurrently, operators attempted to validate core flow using alternate means but | ||
uncertainties associated with the core flow data point. Following plant shutdown and | were unsuccessful as the alternate indications did not provide accurate core flow readings at | ||
subsequent troubleshooting and investigation, licensee personnel concluded that the | low reactor power when in a single loop configuration. After approximately one hour spent | ||
magenta text and suspect note associated with ERIS B33NA01V was an expected system | seeking to understand the unfamiliar indication associated with B33NA01V, control room | ||
response. Below approximately 40 percent core flow, the plant process computer shifts the | operators conducted a brief and made the decision to shut down the unit due to the | ||
calculation method from the primary means of calculating core flow using the sum of jet pump | uncertainties associated with the core flow data point. Following plant shutdown and | ||
flows to an alternate process that uses core plate differential pressure. As a result of shifting | subsequent troubleshooting and investigation, licensee personnel concluded that the | ||
to the alternate calculation of core flow, data point ERIS B33NA01V was programmed to turn | magenta text and suspect note associated with ERIS B33NA01V was an expected system | ||
magenta in color and display suspect to alert operators that the method of calculating core | response. Below approximately 40 percent core flow, the plant process computer shifts the | ||
flow had changed. | calculation method from the primary means of calculating core flow using the sum of jet pump | ||
The inspectors reviewed Condition Report CR-RBS-2012-07759. This condition report was | flows to an alternate process that uses core plate differential pressure. As a result of shifting | ||
generated by operations department personnel on December 19, 2012, and identified that | to the alternate calculation of core flow, data point ERIS B33NA01V was programmed to turn | ||
ERIS point B33NA01V indicated suspect and was not available for use. The condition | magenta in color and display suspect to alert operators that the method of calculating core | ||
report also stated that this data point was needed for determining core flow when the plant | flow had changed. | ||
configuration consisted of one recirculation pump running in fast speed and another | The inspectors reviewed Condition Report CR-RBS-2012-07759. This condition report was | ||
recirculation pump was off. The inspectors confirmed that this condition report was generated | generated by operations department personnel on December 19, 2012, and identified that | ||
during a single loop plant configuration that was the result of an unanticipated reactor | ERIS point B33NA01V indicated suspect and was not available for use. The condition | ||
recirculation pump A trip on December 19, 2012. The condition report corrective actions | report also stated that this data point was needed for determining core flow when the plant | ||
explained the reason for the suspect reading of ERIS point B33NA01V. No corrective | configuration consisted of one recirculation pump running in fast speed and another | ||
actions were generated to address AOP-0024, which directs licensed operators to validate | recirculation pump was off. The inspectors confirmed that this condition report was generated | ||
core flow in single loop operations. Additionally, no corrective actions were generated to | during a single loop plant configuration that was the result of an unanticipated reactor | ||
validate plant simulator response to unanticipated single loop operations. | recirculation pump A trip on December 19, 2012. The condition report corrective actions | ||
Corrective Actions: After this information was disseminated to licensed operators, the | explained the reason for the suspect reading of ERIS point B33NA01V. No corrective | ||
licensee implemented procedural changes to AOP-0024 that provided amplifying information | actions were generated to address AOP-0024, which directs licensed operators to validate | ||
regarding B33NA01V validated core flow. Specifically, the licensee revised the procedure on | core flow in single loop operations. Additionally, no corrective actions were generated to | ||
February 7, 2018, in order to 1) direct operators to determine core flow using ERIS data point | validate plant simulator response to unanticipated single loop operations. | ||
B33NA01V during single loop operations when core flow is below 40 percent and 2) provide | |||
clear guidance regarding expected system response of the process computer data points | Corrective Actions: After this information was disseminated to licensed operators, the | ||
during abnormal flow configurations. | licensee implemented procedural changes to AOP-0024 that provided amplifying information | ||
Corrective Action Reference: CR-RBS-2018-00776 | regarding B33NA01V validated core flow. Specifically, the licensee revised the procedure on | ||
Performance Assessment: | February 7, 2018, in order to 1) direct operators to determine core flow using ERIS data point | ||
Performance Deficiency: The failure to establish appropriate guidance to determine core flow | B33NA01V during single loop operations when core flow is below 40 percent and 2) provide | ||
during single loop operations in quality-related abnormal operating procedure AOP-0024, | clear guidance regarding expected system response of the process computer data points | ||
Thermal Hydraulic Instability Controls, Revision 30, was a performance deficiency. | during abnormal flow configurations. | ||
Corrective Action Reference: CR-RBS-2018-00776 | |||
Performance Assessment: | |||
Performance Deficiency: The failure to establish appropriate guidance to determine core flow | |||
during single loop operations in quality-related abnormal operating procedure AOP-0024, | |||
Thermal Hydraulic Instability Controls, Revision 30, was a performance deficiency. | |||
Screening: The performance deficiency was more than minor, and therefore a finding, | |||
because it was associated with the procedure quality attribute of the Initiating Events | |||
Cornerstone and adversely affected the cornerstone objective to limit the likelihood of events | 17 | ||
that upset plant stability. Specifically, the failure to understand core flow data indicated by | |||
plant process computer point B33NA01V and ERIS data point B33NA01V resulted in | Screening: The performance deficiency was more than minor, and therefore a finding, | ||
confusion and the ultimate decision to insert a manual reactor scram. | because it was associated with the procedure quality attribute of the Initiating Events | ||
Significance: The inspectors screened the finding in accordance with Inspection Manual | Cornerstone and adversely affected the cornerstone objective to limit the likelihood of events | ||
Chapter 0609, Appendix A, The Significance Determination Process for (SDP) for Findings | that upset plant stability. Specifically, the failure to understand core flow data indicated by | ||
At-Power. Using Inspection Manual Chapter 0609, Appendix A, Exhibit 1, Initiating Events | plant process computer point B33NA01V and ERIS data point B33NA01V resulted in | ||
Screening Questions, the inspectors determined this finding is of very low safety significance | confusion and the ultimate decision to insert a manual reactor scram. | ||
(Green) because the finding did not cause a reactor trip and the loss of mitigation equipment | |||
relied upon to transition the plant from the onset of the trip to a stable shutdown condition. | Significance: The inspectors screened the finding in accordance with Inspection Manual | ||
Cross-cutting Aspect: This finding has a cross-cutting aspect in the area of problem | Chapter 0609, Appendix A, The Significance Determination Process for (SDP) for Findings | ||
identification and resolution, resolution, because the licensee failed to take effective | At-Power. Using Inspection Manual Chapter 0609, Appendix A, Exhibit 1, Initiating Events | ||
corrective actions to address issues in a timely manner commensurate with their safety | Screening Questions, the inspectors determined this finding is of very low safety significance | ||
significance. Specifically, the station failed to implement procedure changes to AOP-0024 | (Green) because the finding did not cause a reactor trip and the loss of mitigation equipment | ||
after discovering similar confusing indications associated with B33NA01V on | relied upon to transition the plant from the onset of the trip to a stable shutdown condition. | ||
December 19, 2012. | |||
Enforcement: | Cross-cutting Aspect: This finding has a cross-cutting aspect in the area of problem | ||
Violation: Title 10 CFR Part 50, Appendix B, Criterion V, requires in part that, activities | identification and resolution, resolution, because the licensee failed to take effective | ||
affecting quality shall be prescribed by documented instructions, procedures, or drawings, of | corrective actions to address issues in a timely manner commensurate with their safety | ||
a type appropriate to the circumstances. | significance. Specifically, the station failed to implement procedure changes to AOP-0024 | ||
Contrary to the above, prior to February 7, 2018, the licensee failed to provide a procedure of | after discovering similar confusing indications associated with B33NA01V on | ||
a type appropriate to the circumstances for an activity affecting quality. Specifically, | December 19, 2012. | ||
AOP-0024, Thermal Hydraulic Stability Controls, a quality-related procedure, was not | Enforcement: | ||
appropriate to the circumstances. AOP-0024 did not provide accurate and adequate | |||
instruction to operators to determine core flow during single loop operations. The licensee | Violation: Title 10 CFR Part 50, Appendix B, Criterion V, requires in part that, activities | ||
restored compliance by revising AOP-0024 to include accurate and adequate guidance to | affecting quality shall be prescribed by documented instructions, procedures, or drawings, of | ||
determine core flow during unanticipated single loop operations. | a type appropriate to the circumstances. | ||
Disposition: This violation is being treated as an non-cited violation consistent with | |||
Section 2.3.2.a of the NRC Enforcement Policy. | Contrary to the above, prior to February 7, 2018, the licensee failed to provide a procedure of | ||
Failure to Perform 10 CFR 50.59 Evaluation for Main Feedwater System Sparger Nozzle | a type appropriate to the circumstances for an activity affecting quality. Specifically, | ||
Damage | AOP-0024, Thermal Hydraulic Stability Controls, a quality-related procedure, was not | ||
Cornerstone | appropriate to the circumstances. AOP-0024 did not provide accurate and adequate | ||
instruction to operators to determine core flow during single loop operations. The licensee | |||
None | restored compliance by revising AOP-0024 to include accurate and adequate guidance to | ||
determine core flow during unanticipated single loop operations. | |||
The inspectors identified a Severity Level IV NCV of 10 CFR 50.59, Changes, Tests, and | Disposition: This violation is being treated as an non-cited violation consistent with | ||
Experiments, for the licensees failure to provide a written safety evaluation for the | Section 2.3.2.a of the NRC Enforcement Policy. | ||
determination that operation with compensatory measures for damaged feedwater sparger | |||
nozzles did not require a license amendment pursuant to 10 CFR 50.90, Application for | Failure to Perform 10 CFR 50.59 Evaluation for Main Feedwater System Sparger Nozzle | ||
amendment of license, construction permit, or early site permit. Specifically, the licensee | Damage | ||
Cornerstone | |||
Significance | |||
Cross-cutting | |||
Aspect | |||
Report | |||
Section | |||
None | |||
SL-IV | |||
NCV 05000458/2018012-07 | |||
Closed | |||
None | |||
71111.18 - | |||
Plant | |||
Modifications | |||
The inspectors identified a Severity Level IV NCV of 10 CFR 50.59, Changes, Tests, and | |||
Experiments, for the licensees failure to provide a written safety evaluation for the | |||
determination that operation with compensatory measures for damaged feedwater sparger | |||
nozzles did not require a license amendment pursuant to 10 CFR 50.90, Application for | |||
amendment of license, construction permit, or early site permit. Specifically, the licensee | |||
failed to recognize that compensatory measures prohibiting operation in single loop | |||
conditions were technical specification changes, and as such required prior NRC approval. | |||
Description: | 18 | ||
During an outage that was conducted to replace failed fuel assemblies in January 2018, | |||
damage to feedwater sparger nozzles was identified. The evaluation of the damaged | failed to recognize that compensatory measures prohibiting operation in single loop | ||
feedwater sparger nozzles #7 and #8 on sparger N4C identified that the damaged sections of | conditions were technical specification changes, and as such required prior NRC approval. | ||
the feedwater sparger nozzles had the potential to adversely affect the vessel cladding by | Description: | ||
allowing relatively colder water to directly flow into the relatively hotter vessel wall, thus | |||
inducing thermal fatigue. All components of the RCS are designed to withstand effects of | During an outage that was conducted to replace failed fuel assemblies in January 2018, | ||
cyclic loads due to system pressure and temperature changes. These loads are introduced | damage to feedwater sparger nozzles was identified. The evaluation of the damaged | ||
by startup (heatup) and shutdown (cooldown) operations, power transients, and reactor trips. | feedwater sparger nozzles #7 and #8 on sparger N4C identified that the damaged sections of | ||
Limits are established for pressure and temperature changes during RCS heatup and | the feedwater sparger nozzles had the potential to adversely affect the vessel cladding by | ||
cooldown, such that plant systems remain within the design assumptions and the stress limits | allowing relatively colder water to directly flow into the relatively hotter vessel wall, thus | ||
for cyclic operation. Limits on RCS pressure, temperature, heatup rate, and cooldown rate | inducing thermal fatigue. All components of the RCS are designed to withstand effects of | ||
define allowable operating regions and operating cycles to prevent nonductile failure of | cyclic loads due to system pressure and temperature changes. These loads are introduced | ||
system components. Because operation with the sparger nozzle damage was outside the | by startup (heatup) and shutdown (cooldown) operations, power transients, and reactor trips. | ||
limits originally analyzed, the licensee requested General Electric-Hitachi (GEH) to provide an | Limits are established for pressure and temperature changes during RCS heatup and | ||
operability analysis of the degraded condition. GEH Report #004N6557 Revision 0, dated | cooldown, such that plant systems remain within the design assumptions and the stress limits | ||
January 26, 2018, Operability Assessment of the River Bend Station Feedwater Sparger | for cyclic operation. Limits on RCS pressure, temperature, heatup rate, and cooldown rate | ||
Assembly in the January 2018 As-found Condition, stated in part, this evaluation does not | define allowable operating regions and operating cycles to prevent nonductile failure of | ||
system components. Because operation with the sparger nozzle damage was outside the | |||
limits originally analyzed, the licensee requested General Electric-Hitachi (GEH) to provide an | |||
operability analysis of the degraded condition. GEH Report #004N6557 Revision 0, dated | |||
January 26, 2018, Operability Assessment of the River Bend Station Feedwater Sparger | |||
Assembly in the January 2018 As-found Condition, stated in part, this evaluation does not | |||
account for Final Feedwater Temperature Reduction (FFWTR), Feedwater Heater Out-of- | account for Final Feedwater Temperature Reduction (FFWTR), Feedwater Heater Out-of- | ||
Service (FWH OOS) conditions, nor Single Loop Operation (SLO) operating conditions. | Service (FWH OOS) conditions, nor Single Loop Operation (SLO) operating conditions. | ||
Based on this analysis, the licensees engineering department concluded that the | |||
recommended classification of this condition was OPERABLE-COMP MEAS (operable with | Based on this analysis, the licensees engineering department concluded that the | ||
compensatory measures), with the degraded/nonconforming condition being the holes in the | recommended classification of this condition was OPERABLE-COMP MEAS (operable with | ||
feedwater sparger nozzles. One of the operational restrictions/limitations was that, RBS will | compensatory measures), with the degraded/nonconforming condition being the holes in the | ||
not operate in Single Loop Operation (SLO). These compensatory measures directly | feedwater sparger nozzles. One of the operational restrictions/limitations was that, RBS will | ||
affected Technical Specification (TS) 3.4.1, Recirculation Loops Operating. The TS limiting | not operate in Single Loop Operation (SLO). These compensatory measures directly | ||
condition for operation (LCO) B, One recirculation loop shall be in operation, which is | affected Technical Specification (TS) 3.4.1, Recirculation Loops Operating. The TS limiting | ||
applicable when operating in Modes 1 and 2, had the following limitations: | condition for operation (LCO) B, One recirculation loop shall be in operation, which is | ||
1. | applicable when operating in Modes 1 and 2, had the following limitations: | ||
2. | |||
3. | 1. | ||
single loop operation limits specified in the Core Operating Limits Reports (COLR); | THERMAL POWER 77.6% rated thermal power (RTP); | ||
4. | 2. | ||
limits specified in the COLR; and | Total core flow within limits; | ||
5. | 3. | ||
(Average Power Range Monitors Flow Biased Simulated Thermal Power- High), Allowable | LCO 3.2.1,"AVERAGE PLANAR LINEAR HEAT GENERATION RATE (APLHGR)," | ||
Value for single loop operation as specified in the COLR. | single loop operation limits specified in the Core Operating Limits Reports (COLR); | ||
The licensees compensatory measures established a more restrictive LCO whereby Single | 4. | ||
Loop Operations are limited by more restrictive criteria than those stated in the existing LCO. | LCO 3.2.2,"MINIMUM CRITICAL POWER RATIO (MCPR)," single loop operation | ||
Specifically, the licensees compensatory measures stated that the station would not operate | limits specified in the COLR; and | ||
in Single Loop Operation. | 5. | ||
NRC Administrative Letter 98-10: Dispositioning of Technical Specifications That Are | LCO 3.3.1.1, "Reactor Protection System (RPS) Instrumentation," Function 2.b | ||
Insufficient To Assure Plant Safety, dated December 29, 1988, provides the following | (Average Power Range Monitors Flow Biased Simulated Thermal Power- High), Allowable | ||
guidance: | Value for single loop operation as specified in the COLR. | ||
The licensees compensatory measures established a more restrictive LCO whereby Single | |||
Loop Operations are limited by more restrictive criteria than those stated in the existing LCO. | |||
Specifically, the licensees compensatory measures stated that the station would not operate | |||
in Single Loop Operation. | |||
NRC Administrative Letter 98-10: Dispositioning of Technical Specifications That Are | |||
Insufficient To Assure Plant Safety, dated December 29, 1988, provides the following | |||
guidance: | |||
Title 10 of the Code of Federal Regulations, Section 50.36, Technical Specifications | |||
requires that each TS limiting condition for operation (LCO) specify, at a minimum, the lowest | |||
functional capability or performance level of equipment required for the safe operation of the | 19 | ||
facility. | |||
IMC0326 states, in part: Additionally, if a compensatory measure involves a temporary facility | Title 10 of the Code of Federal Regulations, Section 50.36, Technical Specifications | ||
or procedure change, 10 CFR 50.59 should be applied to the temporary change with the | requires that each TS limiting condition for operation (LCO) specify, at a minimum, the lowest | ||
intent to determine whether the temporary change/compensatory measure itself (not the | functional capability or performance level of equipment required for the safe operation of the | ||
degraded or nonconforming condition) impacts other aspects of the facility or procedures | facility. | ||
described in the UFSAR. In considering whether a temporary facility or procedure change | |||
impacts other aspects of the facility, a licensee should apply 10 CFR 50.59, paying particular | IMC0326 states, in part: Additionally, if a compensatory measure involves a temporary facility | ||
attention to ancillary aspects of the temporary change that result from actions taken to directly | or procedure change, 10 CFR 50.59 should be applied to the temporary change with the | ||
compensate for the degraded condition. Whenever degraded or nonconforming conditions | intent to determine whether the temporary change/compensatory measure itself (not the | ||
are discovered, 10 CFR Part 50, Appendix B, requires prompt corrective action to correct or | degraded or nonconforming condition) impacts other aspects of the facility or procedures | ||
resolve the condition. | described in the UFSAR. In considering whether a temporary facility or procedure change | ||
In summary, the discovery of an improper or inadequate TS value or required action is | impacts other aspects of the facility, a licensee should apply 10 CFR 50.59, paying particular | ||
considered a degraded or nonconforming condition as defined in IMC0326. Imposing | attention to ancillary aspects of the temporary change that result from actions taken to directly | ||
administrative controls in response to an improper or inadequate TS is considered an | compensate for the degraded condition. Whenever degraded or nonconforming conditions | ||
acceptable short-term corrective action. The NRC staff expects that, following the imposition | are discovered, 10 CFR Part 50, Appendix B, requires prompt corrective action to correct or | ||
of administrative controls, an amendment to the TS, with appropriate justification and | resolve the condition. | ||
schedule, will be submitted in a timely fashion. Once any amendment correcting the TS is | |||
approved, the licensee must update the final safety analysis report, as necessary, to comply | In summary, the discovery of an improper or inadequate TS value or required action is | ||
with 10 CFR 50.71(e). | considered a degraded or nonconforming condition as defined in IMC0326. Imposing | ||
Because the licensee did not perform a 50.59 screening for the compensatory measures | administrative controls in response to an improper or inadequate TS is considered an | ||
associated with the restricted operating conditions, the licensee failed to recognize that the | acceptable short-term corrective action. The NRC staff expects that, following the imposition | ||
TSs were now non-conservative and that NRC approval was required. | of administrative controls, an amendment to the TS, with appropriate justification and | ||
Corrective Actions: The licensee documented the violation in the corrective action program | schedule, will be submitted in a timely fashion. Once any amendment correcting the TS is | ||
and created actions to review 50.59 screening requirements. | approved, the licensee must update the final safety analysis report, as necessary, to comply | ||
Corrective Action Reference: CR-RBS-2018-03147 | with 10 CFR 50.71(e). | ||
Performance Assessment: | |||
Performance Deficiency: The failure to perform a written safety evaluation for the effect of | Because the licensee did not perform a 50.59 screening for the compensatory measures | ||
compensatory measures implemented due to degraded feedwater sparger nozzles was a | associated with the restricted operating conditions, the licensee failed to recognize that the | ||
performance deficiency. | TSs were now non-conservative and that NRC approval was required. | ||
Screening: The performance deficiency was evaluated in accordance with the traditional | |||
enforcement process because it impacted the ability of the NRC to perform its regulatory | Corrective Actions: The licensee documented the violation in the corrective action program | ||
oversight function. | and created actions to review 50.59 screening requirements. | ||
Significance: Using example 6.1.d.2 from the NRC Enforcement Policy, the violation was | |||
determined to be a Severity Level IV violation. | Corrective Action Reference: CR-RBS-2018-03147 | ||
Cross-cutting Aspect: Because the violation was dispositioned using the traditional | Performance Assessment: | ||
enforcement process, no cross cutting aspect was assigned. | |||
Performance Deficiency: The failure to perform a written safety evaluation for the effect of | |||
compensatory measures implemented due to degraded feedwater sparger nozzles was a | |||
performance deficiency. | |||
Screening: The performance deficiency was evaluated in accordance with the traditional | |||
enforcement process because it impacted the ability of the NRC to perform its regulatory | |||
oversight function. | |||
Significance: Using example 6.1.d.2 from the NRC Enforcement Policy, the violation was | |||
determined to be a Severity Level IV violation. | |||
Cross-cutting Aspect: Because the violation was dispositioned using the traditional | |||
enforcement process, no cross cutting aspect was assigned. | |||
Enforcement: | |||
Violation: Title 10 CFR 50.59(d)(1) requires, in part, that the licensee shall maintain records | |||
of changes in the facility, of changes in procedures, and of tests and experiments as | 20 | ||
described in the updated final safety analysis report (UFSAR). These records must include a | |||
written evaluation which provides a basis for the determination that the change, test, or | Enforcement: | ||
experiment does not require a license amendment. | |||
Contrary to the above, since January 29, 2018, the licensee failed to maintain records of a | Violation: Title 10 CFR 50.59(d)(1) requires, in part, that the licensee shall maintain records | ||
change to the facility, as described in the UFSAR, that include a written evaluation which | of changes in the facility, of changes in procedures, and of tests and experiments as | ||
provides a basis for the determination that the change did not require a license amendment. | described in the updated final safety analysis report (UFSAR). These records must include a | ||
Specifically, the licensee made changes pursuant to 10 CFR 50.59(c) to the plant as | written evaluation which provides a basis for the determination that the change, test, or | ||
described in the UFSAR and did not provide a written evaluation for the determination that | experiment does not require a license amendment. | ||
compensatory measures prohibiting operation in single loop condition were technical | |||
specification changes, and as such required prior NRC approval. | Contrary to the above, since January 29, 2018, the licensee failed to maintain records of a | ||
Disposition: This violation is being treated as an non-cited violation consistent with | change to the facility, as described in the UFSAR, that include a written evaluation which | ||
Section 2.3.2.a of the NRC Enforcement Policy. | provides a basis for the determination that the change did not require a license amendment. | ||
Failure to Conduct Adequate Transient Snap Shot Assessment Following Recirculation Pump | Specifically, the licensee made changes pursuant to 10 CFR 50.59(c) to the plant as | ||
Trip | described in the UFSAR and did not provide a written evaluation for the determination that | ||
Cornerstone | compensatory measures prohibiting operation in single loop condition were technical | ||
specification changes, and as such required prior NRC approval. | |||
Initiating Events | |||
Disposition: This violation is being treated as an non-cited violation consistent with | |||
Section 2.3.2.a of the NRC Enforcement Policy. | |||
Failure to Conduct Adequate Transient Snap Shot Assessment Following Recirculation Pump | |||
The inspectors identified a Green finding for the licensees failure to adequately validate | Trip | ||
simulator response during a transient snap shot assessment following an unexpected trip of | Cornerstone | ||
reactor recirculation pump A on December 19, 2012. | Significance | ||
Description: | Cross-cutting | ||
On December 19, 2012, with the plant operating at 100 percent power, reactor recirculation | Aspect | ||
pump A unexpectedly tripped off. As a result, the plant configuration consisted of one | Report | ||
recirculation pump running in fast speed and the other recirculation pump secured. During | Section | ||
this single loop configuration, station personnel identified that emergency response | Initiating Events | ||
information system (ERIS) point B33NA01V indicated suspect and was not available for | Green | ||
use. The station documented this condition in Condition Report CR-RBS-2012-07759. | FIN 05000458/2018012-01 | ||
On February 1, 2018, with the unit in Mode 1 at approximately 27 percent power, reactor | Closed | ||
recirculation pump B unexpectedly tripped during an upshift in the speed of the pump. As a | None | ||
result, the reactor was in a single loop configuration with the recirculation pump A running in | 71152 - | ||
fast speed and the recirculation pump B not running. Operators entered abnormal operating | Problem | ||
procedure AOP-0024, Thermal Hydraulic Instability Controls, Revision 30, as a result of the | Identification | ||
unplanned entry into single loop operations. Step 5.8 of this procedure directed operators to | and | ||
determine core flow and enter general operating procedure GOP-004, Single Loop | Resolution | ||
Operations. Step 5.8 also instructed operators to determine core flow using process | The inspectors identified a Green finding for the licensees failure to adequately validate | ||
computer point B33NA01V (which can be observed in both ERIS and the plant process | simulator response during a transient snap shot assessment following an unexpected trip of | ||
computer) when in a configuration with one recirculation pump in fast speed and one | reactor recirculation pump A on December 19, 2012. | ||
Description: | |||
On December 19, 2012, with the plant operating at 100 percent power, reactor recirculation | |||
pump A unexpectedly tripped off. As a result, the plant configuration consisted of one | |||
recirculation pump running in fast speed and the other recirculation pump secured. During | |||
this single loop configuration, station personnel identified that emergency response | |||
information system (ERIS) point B33NA01V indicated suspect and was not available for | |||
use. The station documented this condition in Condition Report CR-RBS-2012-07759. | |||
On February 1, 2018, with the unit in Mode 1 at approximately 27 percent power, reactor | |||
recirculation pump B unexpectedly tripped during an upshift in the speed of the pump. As a | |||
result, the reactor was in a single loop configuration with the recirculation pump A running in | |||
fast speed and the recirculation pump B not running. Operators entered abnormal operating | |||
procedure AOP-0024, Thermal Hydraulic Instability Controls, Revision 30, as a result of the | |||
unplanned entry into single loop operations. Step 5.8 of this procedure directed operators to | |||
determine core flow and enter general operating procedure GOP-004, Single Loop | |||
Operations. Step 5.8 also instructed operators to determine core flow using process | |||
computer point B33NA01V (which can be observed in both ERIS and the plant process | |||
computer) when in a configuration with one recirculation pump in fast speed and one | |||
recirculation pump off. Control room operators observed the value of this data point as | |||
13.9 million pounds mass per hour (Mlbm/hr) of flow through the reactor core. The operators | |||
concluded that this value was not valid since the indicated flow was much lower than | 21 | ||
expected with one recirculation pump running in fast speed. The operators then observed a | |||
value of 27.3Mlbm/hr core flow using the ERIS data point for B33NA01V. This value | recirculation pump off. Control room operators observed the value of this data point as | ||
appeared to be a valid number based on the single loop operation power/flow map contained | 13.9 million pounds mass per hour (Mlbm/hr) of flow through the reactor core. The operators | ||
in AOP-0024, Attachment 2. Normal data points on ERIS are displayed with a white text, but | concluded that this value was not valid since the indicated flow was much lower than | ||
control room operators observed the ERIS data point displayed in a magenta color. | expected with one recirculation pump running in fast speed. The operators then observed a | ||
Additionally, the word suspect appeared adjacent to the data point for core flow. Control | value of 27.3Mlbm/hr core flow using the ERIS data point for B33NA01V. This value | ||
room operators contacted information technology personnel and attempted to understand the | appeared to be a valid number based on the single loop operation power/flow map contained | ||
magenta color and suspect information associated with the core flow data point. | in AOP-0024, Attachment 2. Normal data points on ERIS are displayed with a white text, but | ||
Concurrently, operators attempted to validate core flow using alternate means but were | control room operators observed the ERIS data point displayed in a magenta color. | ||
unsuccessful, as the alternate indications did not provide accurate core flow readings at low | Additionally, the word suspect appeared adjacent to the data point for core flow. Control | ||
reactor power when in a single loop configuration. After approximately one hour spent | room operators contacted information technology personnel and attempted to understand the | ||
seeking to understand the unfamiliar indication associated with B33NA01V, control room | magenta color and suspect information associated with the core flow data point. | ||
operators conducted a brief and made the decision to shut down the unit due to the | Concurrently, operators attempted to validate core flow using alternate means but were | ||
uncertainties associated with the core flow data point. Following plant shutdown and | unsuccessful, as the alternate indications did not provide accurate core flow readings at low | ||
subsequent troubleshooting and investigation, licensee personnel concluded that the | reactor power when in a single loop configuration. After approximately one hour spent | ||
magenta text and suspect note associated with ERIS B33NA01V was an expected system | seeking to understand the unfamiliar indication associated with B33NA01V, control room | ||
response. Below approximately 40 percent core flow, the plant process computer shifts the | operators conducted a brief and made the decision to shut down the unit due to the | ||
calculation method from the primary means of calculating core flow using the sum of jet pump | uncertainties associated with the core flow data point. Following plant shutdown and | ||
flows to an alternate process that uses core plate differential pressure. As a result of shifting | subsequent troubleshooting and investigation, licensee personnel concluded that the | ||
to the alternate calculation of core flow, data point ERIS B33NA01V was programmed to turn | magenta text and suspect note associated with ERIS B33NA01V was an expected system | ||
magenta in color and display suspect to alert operators that the method of calculating core | response. Below approximately 40 percent core flow, the plant process computer shifts the | ||
flow had changed. After this information was disseminated to licensed operators, the | calculation method from the primary means of calculating core flow using the sum of jet pump | ||
licensee implemented procedural changes to AOP-0024 that provided amplifying information | flows to an alternate process that uses core plate differential pressure. As a result of shifting | ||
regarding B33NA01V validated core flow. Specifically, the licensee revised the procedure on | to the alternate calculation of core flow, data point ERIS B33NA01V was programmed to turn | ||
February 7, 2018, in order to provide clear guidance regarding expected system response of | magenta in color and display suspect to alert operators that the method of calculating core | ||
the process computer data points during abnormal flow configurations. | flow had changed. After this information was disseminated to licensed operators, the | ||
The inspectors compared the actual plant response to the simulator response for the trip of a | licensee implemented procedural changes to AOP-0024 that provided amplifying information | ||
recirculation pump while at low power. The actual conditions in the main control room during | regarding B33NA01V validated core flow. Specifically, the licensee revised the procedure on | ||
the event on February 1, 2018, resulted in ERIS point B33NA01V indicating the correct flow | February 7, 2018, in order to provide clear guidance regarding expected system response of | ||
(27.3Mlbm/hr), but the data point turned magenta in color and displayed the warning label | the process computer data points during abnormal flow configurations. | ||
suspect. This was later determined by information technology personnel to be the correct | |||
response and data display, and was the result of the core flow calculation methodology | The inspectors compared the actual plant response to the simulator response for the trip of a | ||
swapping from the primary method (jet pump flow) to the alternate method (core plate | recirculation pump while at low power. The actual conditions in the main control room during | ||
differential pressure). | the event on February 1, 2018, resulted in ERIS point B33NA01V indicating the correct flow | ||
In the simulator, the inspectors determined that ERIS point B33NA01V provided erratic | (27.3Mlbm/hr), but the data point turned magenta in color and displayed the warning label | ||
indications of core flow following a simulated trip of the recirculation pump B from an initial | suspect. This was later determined by information technology personnel to be the correct | ||
condition of approximately 25 percent. The indicated flow varied, and ultimately stabilized at | response and data display, and was the result of the core flow calculation methodology | ||
approximately 10Mlbm/hr, which is less than half of the expected indication. Additionally, | swapping from the primary method (jet pump flow) to the alternate method (core plate | ||
B33NA01V did not change to a magenta color, and it did not display the word suspect. The | differential pressure). | ||
inspectors determined that ERIS B33NA01V was programmed to calculate core flow using | |||
the sum of jet pump flows at all power levels. As a result, the displayed value was inaccurate | In the simulator, the inspectors determined that ERIS point B33NA01V provided erratic | ||
below 40 percent core flow, and the data point was not programmed to turn magenta or | indications of core flow following a simulated trip of the recirculation pump B from an initial | ||
indicate suspect since no swap to a backup means of calculation below 40 percent core | condition of approximately 25 percent. The indicated flow varied, and ultimately stabilized at | ||
flow was modelled. | approximately 10Mlbm/hr, which is less than half of the expected indication. Additionally, | ||
B33NA01V did not change to a magenta color, and it did not display the word suspect. The | |||
inspectors determined that ERIS B33NA01V was programmed to calculate core flow using | |||
the sum of jet pump flows at all power levels. As a result, the displayed value was inaccurate | |||
below 40 percent core flow, and the data point was not programmed to turn magenta or | |||
indicate suspect since no swap to a backup means of calculation below 40 percent core | |||
flow was modelled. | |||
The inspectors reviewed procedure EN-OP-117, Operations Assessments, Version 4, | |||
Section 5.4, which states that transient snap-shot assessments are performed whenever a | |||
plant transient occurs. A plant transient is defined in section 5.4[2] as including any turbine | 22 | ||
generator power change in excess of 10 percent of rated power in less than one minute other | |||
than a momentary spike due to a grid disturbance or a manually initiated runback. The | The inspectors reviewed procedure EN-OP-117, Operations Assessments, Version 4, | ||
inspectors concluded that the recirculation pump A trip on December 19, 2012, met the | Section 5.4, which states that transient snap-shot assessments are performed whenever a | ||
definition of a transient. EN-OP-117, Attachment 9.2, Transient Snap Shot Assessment | plant transient occurs. A plant transient is defined in section 5.4[2] as including any turbine | ||
Documentation Form, Objective 7, discusses the training preparation aspect of the | generator power change in excess of 10 percent of rated power in less than one minute other | ||
assessment. Specifically, the transient snap-shot assessment is performed in order to | than a momentary spike due to a grid disturbance or a manually initiated runback. The | ||
validate that the simulator accurately represented the plant characteristics of the transient. | inspectors concluded that the recirculation pump A trip on December 19, 2012, met the | ||
The licensee provided a Post-Event Simulator Test report that was run on February 14, 2013. | definition of a transient. EN-OP-117, Attachment 9.2, Transient Snap Shot Assessment | ||
The report concluded that the simulator response matched the parameters observed in the | Documentation Form, Objective 7, discusses the training preparation aspect of the | ||
plant. The inspectors determined that although the snap-shot assessment was performed, | assessment. Specifically, the transient snap-shot assessment is performed in order to | ||
station personnel did not validate that ERIS B33NA01V (validated core flow) provided | validate that the simulator accurately represented the plant characteristics of the transient. | ||
operators with the same indications seen by operators in the plant during a recirculation | The licensee provided a Post-Event Simulator Test report that was run on February 14, 2013. | ||
pump trip. | The report concluded that the simulator response matched the parameters observed in the | ||
The inspectors determined that no condition report or simulator deficiency report was | plant. The inspectors determined that although the snap-shot assessment was performed, | ||
generated to document the discrepancy between the plant and the simulator for displaying | station personnel did not validate that ERIS B33NA01V (validated core flow) provided | ||
ERIS B33NA01V. The simulator ERIS B33NA01V core flow indication did not display the | operators with the same indications seen by operators in the plant during a recirculation | ||
correct value for core flow and also did not indicate suspect or turn magenta. The | pump trip. | ||
inspectors reviewed training documentation to determine why this discrepancy was not | |||
observed during continuing simulator training scenarios. The inspectors concluded that this | The inspectors determined that no condition report or simulator deficiency report was | ||
discrepancy was not documented because the station did not conduct training on abnormal | generated to document the discrepancy between the plant and the simulator for displaying | ||
single loop operations during low power operations. The inspectors reviewed industry | ERIS B33NA01V. The simulator ERIS B33NA01V core flow indication did not display the | ||
standards and guidelines for simulator training and determined that the station is required to | correct value for core flow and also did not indicate suspect or turn magenta. The | ||
periodically conduct training on abnormal events that occur during low power operations. | inspectors reviewed training documentation to determine why this discrepancy was not | ||
Corrective Actions: The station documented the core flow indication simulator deficiency in a | observed during continuing simulator training scenarios. The inspectors concluded that this | ||
deficiency report and generated actions to incorporate the discrepancy into future licensed | discrepancy was not documented because the station did not conduct training on abnormal | ||
operator training sessions. | single loop operations during low power operations. The inspectors reviewed industry | ||
Corrective Action Reference: CR-RBS-2018-03145 | standards and guidelines for simulator training and determined that the station is required to | ||
Performance Assessment: | periodically conduct training on abnormal events that occur during low power operations. | ||
Performance Deficiency: The licensees failure to validate core flow in the simulator during a | |||
transient snap shot assessment following the trip of the reactor recirculation pump A on | Corrective Actions: The station documented the core flow indication simulator deficiency in a | ||
December 19, 2012, was a performance deficiency. | deficiency report and generated actions to incorporate the discrepancy into future licensed | ||
Screening: The performance deficiency was more than minor, and therefore a finding, | operator training sessions. | ||
because it was associated with the human performance attribute of the Initiating Events | |||
Cornerstone and adversely affected the cornerstone objective to limit the likelihood of events | Corrective Action Reference: CR-RBS-2018-03145 | ||
that upset plant stability and challenge critical safety functions during shutdown as well as | Performance Assessment: | ||
power operations. Specifically, the failure to validate simulator fidelity following a plant | |||
transient prevented the licensee from identifying simulator model discrepancies when | Performance Deficiency: The licensees failure to validate core flow in the simulator during a | ||
determining core flow during low power, single loop operations. | transient snap shot assessment following the trip of the reactor recirculation pump A on | ||
December 19, 2012, was a performance deficiency. | |||
Screening: The performance deficiency was more than minor, and therefore a finding, | |||
because it was associated with the human performance attribute of the Initiating Events | |||
Cornerstone and adversely affected the cornerstone objective to limit the likelihood of events | |||
that upset plant stability and challenge critical safety functions during shutdown as well as | |||
power operations. Specifically, the failure to validate simulator fidelity following a plant | |||
transient prevented the licensee from identifying simulator model discrepancies when | |||
determining core flow during low power, single loop operations. | |||
Significance: The inspectors screened the finding in accordance with Inspection Manual | |||
Chapter 0609, Appendix A, The Significance Determination Process for Findings At-Power. | |||
The finding was determined to be of very low safety significance (Green) because the finding | 23 | ||
did not contribute to both the likelihood of a reactor trip and the likelihood that mitigating | |||
equipment would not be available. | Significance: The inspectors screened the finding in accordance with Inspection Manual | ||
Cross-cutting Aspect: No cross cutting aspect was assigned because the performance | Chapter 0609, Appendix A, The Significance Determination Process for Findings At-Power. | ||
deficiency is not indicative of current licensee performance. | The finding was determined to be of very low safety significance (Green) because the finding | ||
Enforcement: Inspectors did not identify a violation of regulatory requirements associated | did not contribute to both the likelihood of a reactor trip and the likelihood that mitigating | ||
with this finding. | equipment would not be available. | ||
Failure to Submit a Licensee Event Report for a Manual Scram | |||
Cornerstone | Cross-cutting Aspect: No cross cutting aspect was assigned because the performance | ||
deficiency is not indicative of current licensee performance. | |||
None | Enforcement: Inspectors did not identify a violation of regulatory requirements associated | ||
with this finding. | |||
Failure to Submit a Licensee Event Report for a Manual Scram | |||
Cornerstone | |||
Significance | |||
The inspectors identified a Severity Level IV non-cited violation of 10 CFR 50.73, Licensee | Cross-cutting | ||
Event Report System, for the licensees failure to submit a required licensee event report | Aspect | ||
(LER). Specifically, on February 1, 2018, after an unexpected trip of the recirculation pump | Report | ||
B, the licensee initiated a manual scram of the reactor that was not part of a preplanned | Section | ||
sequence and failed to submit an LER within 60 days. | None | ||
Description: At approximately 9:46 a.m. on February 1, 2018, with the unit operating at | SLIV | ||
approximately 27 percent power, the recirculation pump B unexpectedly tripped during an | NCV 05000458/2018012-04 | ||
attempted transfer from slow to fast speed. The licensee promptly entered AOP-0024, | Closed | ||
Thermal Hydraulic Instability, and GOP-0004, Single Loop Operation. Note 5.8 of AOP- | None | ||
0024 and Precaution 3.6 of GOP-0004 instruct the licensee to use process computer point | 71153 - | ||
B33NA01V to determine core flow while in single loop operation. The plant process computer | Follow-up of | ||
(PPC) and emergency response information system (ERIS) readouts showed conflicting | Events and | ||
indications for this computer point, with the PPC showing approximately 13,900 Mlbm/hr of | Notices of | ||
flow and ERIS showing approximately 26,000 Mlbm/hr of flow. | Enforcement | ||
Step 5.1 of AOP-0024 instructs the licensee to determine where on the power-to-flow map the | Discretion | ||
plant is operating. If the plant is operating in the restricted region, the procedure states to exit | The inspectors identified a Severity Level IV non-cited violation of 10 CFR 50.73, Licensee | ||
that region by lowering power or raising flow. If the plant is operating in the exclusion region, | Event Report System, for the licensees failure to submit a required licensee event report | ||
the procedure states to verify that a scram has occurred. The indicated PPC value for core | (LER). Specifically, on February 1, 2018, after an unexpected trip of the recirculation pump | ||
flow put the plant in an unanalyzed region of the power-to-flow map, with less flow than the | B, the licensee initiated a manual scram of the reactor that was not part of a preplanned | ||
minimum amount of flow that defines any region, including the exclusion region. The | sequence and failed to submit an LER within 60 days. | ||
indicated ERIS value put the plant in the restricted region, just above the boundary that | Description: At approximately 9:46 a.m. on February 1, 2018, with the unit operating at | ||
delineates the restricted region from the monitoring region. | approximately 27 percent power, the recirculation pump B unexpectedly tripped during an | ||
The licensee initially believed the ERIS value to be the correct value; however, this value was | attempted transfer from slow to fast speed. The licensee promptly entered AOP-0024, | ||
accompanied by a magenta suspect note on the ERIS screen, which caused the licensee to | Thermal Hydraulic Instability, and GOP-0004, Single Loop Operation. Note 5.8 of AOP- | ||
question its validity. In an effort to determine the true value of core flow, the licensee | 0024 and Precaution 3.6 of GOP-0004 instruct the licensee to use process computer point | ||
performed a manual calculation using other known inputs. The licensee performed this | B33NA01V to determine core flow while in single loop operation. The plant process computer | ||
calculation incorrectly and wrongly corroborated the PPC value as the correct value. Given | (PPC) and emergency response information system (ERIS) readouts showed conflicting | ||
indications for this computer point, with the PPC showing approximately 13,900 Mlbm/hr of | |||
flow and ERIS showing approximately 26,000 Mlbm/hr of flow. | |||
Step 5.1 of AOP-0024 instructs the licensee to determine where on the power-to-flow map the | |||
plant is operating. If the plant is operating in the restricted region, the procedure states to exit | |||
that region by lowering power or raising flow. If the plant is operating in the exclusion region, | |||
the procedure states to verify that a scram has occurred. The indicated PPC value for core | |||
flow put the plant in an unanalyzed region of the power-to-flow map, with less flow than the | |||
minimum amount of flow that defines any region, including the exclusion region. The | |||
indicated ERIS value put the plant in the restricted region, just above the boundary that | |||
delineates the restricted region from the monitoring region. | |||
The licensee initially believed the ERIS value to be the correct value; however, this value was | |||
accompanied by a magenta suspect note on the ERIS screen, which caused the licensee to | |||
question its validity. In an effort to determine the true value of core flow, the licensee | |||
performed a manual calculation using other known inputs. The licensee performed this | |||
calculation incorrectly and wrongly corroborated the PPC value as the correct value. Given | |||
the inability to establish that the plant was operating in any allowed region of the power-to- | the inability to establish that the plant was operating in any allowed region of the power-to- | ||
flow map, the licensee made the decision to manually actuate the reactor protection system | |||
(RPS) by taking the reactor mode switch to shutdown. | |||
During the investigation after the scram, the licensee determined that the ERIS value was, in | 24 | ||
fact, a valid indication of core flow at the time of the event. Operators had not been | |||
adequately trained on the meaning of the magenta suspect indication, and were therefore | flow map, the licensee made the decision to manually actuate the reactor protection system | ||
unable to determine the implications of the indications on the validity of the data point. | (RPS) by taking the reactor mode switch to shutdown. | ||
Pursuant to the requirements of 10 CFR 50.72(b)(3)(iv), the licensee reported the scram | |||
event to the NRC at 1:23 p.m. as an event that resulted in an actuation of the RPS. On | During the investigation after the scram, the licensee determined that the ERIS value was, in | ||
March 23, 2018, the licensee retracted the report on the grounds that the actuation was part | fact, a valid indication of core flow at the time of the event. Operators had not been | ||
of a pre-planned sequence during testing or reactor operation. The inspectors concluded that | adequately trained on the meaning of the magenta suspect indication, and were therefore | ||
this retraction was inappropriate and that the event was reportable for the reasons provided | unable to determine the implications of the indications on the validity of the data point. | ||
below. | |||
The inspectors reviewed NUREG-1022, Event Report Guidelines 10 CFR 50.72 and 50.73, | Pursuant to the requirements of 10 CFR 50.72(b)(3)(iv), the licensee reported the scram | ||
revision 3, which provides the following guidance: Actuations that need not be reported are | event to the NRC at 1:23 p.m. as an event that resulted in an actuation of the RPS. On | ||
those initiated for reasons other than to mitigate the consequences of an event (e.g., at the | March 23, 2018, the licensee retracted the report on the grounds that the actuation was part | ||
discretion of the licensee as part of a preplanned procedure). In the case of the February 1, | of a pre-planned sequence during testing or reactor operation. The inspectors concluded that | ||
2018, River Bend scram event, the inspectors determined that the manual RPS actuation was | this retraction was inappropriate and that the event was reportable for the reasons provided | ||
initiated in order to mitigate the consequences (i.e., uncertainty as to the condition of the plant | below. | ||
with respect to core flow and power-to-flow considerations) of an event (i.e., the unexpected | The inspectors reviewed NUREG-1022, Event Report Guidelines 10 CFR 50.72 and 50.73, | ||
loss of a reactor recirculation pump). | revision 3, which provides the following guidance: Actuations that need not be reported are | ||
NUREG-1022 also provides an example of a reportable manual scram that was event driven | those initiated for reasons other than to mitigate the consequences of an event (e.g., at the | ||
and not part of a preplanned sequence during testing or reactor operation: | discretion of the licensee as part of a preplanned procedure). In the case of the February 1, | ||
2018, River Bend scram event, the inspectors determined that the manual RPS actuation was | |||
initiated in order to mitigate the consequences (i.e., uncertainty as to the condition of the plant | |||
with respect to core flow and power-to-flow considerations) of an event (i.e., the unexpected | |||
loss of a reactor recirculation pump). | |||
NUREG-1022 also provides an example of a reportable manual scram that was event driven | |||
and not part of a preplanned sequence during testing or reactor operation: | |||
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 | |||
As with the scram in the above example, the scram that occurred at River Bend Station was | performed a reactor scram, which was uncomplicated. This event is reportable as a | ||
not part of a preplanned sequence during testing or reactor operation, but was instead an | manual RPS actuation. Even though the reactor scram was in response to an existing | ||
event driven response to a series of unplanned and unexpected adverse occurrences in the | written procedure, this event does not involve a preplanned sequence because the | ||
plant. These occurrences included: a trip of the recirculation pump B, entry into an abnormal | loss of recirculation pumps and the resultant off-normal procedure entry were event | ||
operating procedure for thermal hydraulic instability, an inability to determine core flow and | driven, not preplanned. Both an ENS notification and an LER are required. In this | ||
location on the power-to-flow map in accordance with that procedure, a realization that the | case, the licensee initially retracted the ENS notification, believing that the event was | ||
PPC indication of core flow put the plant outside of any allowed operating region of the | not reportable. After staff review and further discussion, it was agreed that the event | ||
power-to-flow map, an incorrect manual calculation that wrongly corroborated the accuracy of | is reportable for the reasons discussed above. | ||
the PPC indication, and the presence of a poorly understood suspect indication that | |||
appeared to undermine the validity of the ERIS flow indication. These adverse occurrences | As with the scram in the above example, the scram that occurred at River Bend Station was | ||
generated uncertainty as to the status of reactor safety. The subsequent decision to perform | not part of a preplanned sequence during testing or reactor operation, but was instead an | ||
event driven response to a series of unplanned and unexpected adverse occurrences in the | |||
plant. These occurrences included: a trip of the recirculation pump B, entry into an abnormal | |||
operating procedure for thermal hydraulic instability, an inability to determine core flow and | |||
location on the power-to-flow map in accordance with that procedure, a realization that the | |||
PPC indication of core flow put the plant outside of any allowed operating region of the | |||
power-to-flow map, an incorrect manual calculation that wrongly corroborated the accuracy of | |||
the PPC indication, and the presence of a poorly understood suspect indication that | |||
appeared to undermine the validity of the ERIS flow indication. These adverse occurrences | |||
generated uncertainty as to the status of reactor safety. The subsequent decision to perform | |||
a manual reactor scram was consistent with general instruction provided in EN-OP-115, | |||
Conduct of Operations, which states: do not hesitate to reduce power or perform an | |||
immediate reactor shutdown when reactor safety is uncertain. As with the scram in the | 25 | ||
a manual reactor scram was consistent with general instruction provided in EN-OP-115, | |||
Conduct of Operations, which states: do not hesitate to reduce power or perform an | |||
immediate reactor shutdown when reactor safety is uncertain. As with the scram in the | |||
above example, the February 1, 2018, River Bend scram also involved entry into an off- | above example, the February 1, 2018, River Bend scram also involved entry into an off- | ||
normal procedure due to an unexpected plant equipment malfunction that resulted in the | normal procedure due to an unexpected plant equipment malfunction that resulted in the | ||
potential for the plant to be in an undesired condition with respect to power-to-flow | potential for the plant to be in an undesired condition with respect to power-to-flow | ||
considerations. | considerations. | ||
The senior resident inspector was present in the control room during the events and was able | |||
to confirm that the shutdown was event driven rather than preplanned. At 10:55 a.m., the | The senior resident inspector was present in the control room during the events and was able | ||
control room briefed that because PPC and ERIS showed conflicting indications of core flow | to confirm that the shutdown was event driven rather than preplanned. At 10:55 a.m., the | ||
with ERIS indicating suspect, the mode switch was going to be placed in shutdown. At | control room briefed that because PPC and ERIS showed conflicting indications of core flow | ||
10:57 a.m., roughly two minutes after the brief was completed, the reactor operator | with ERIS indicating suspect, the mode switch was going to be placed in shutdown. At | ||
scrammed the reactor, and the following station log entry was made: MCR [main control | 10:57 a.m., roughly two minutes after the brief was completed, the reactor operator | ||
room] announces placing plant in shut down due to inability to regulate recirculation flow. If | scrammed the reactor, and the following station log entry was made: MCR [main control | ||
the reactor shutdown had been preplanned, it would not have proceeded at this accelerated | room] announces placing plant in shut down due to inability to regulate recirculation flow. If | ||
pace. Rather, the licensee would have worked through the relevant steps of the applicable | the reactor shutdown had been preplanned, it would not have proceeded at this accelerated | ||
shutdown procedure, GOP-0004, Single Loop Operation, scramming the reactor only after | pace. Rather, the licensee would have worked through the relevant steps of the applicable | ||
those steps had been completed and signed for. Upon review of the copy of GOP-0004 that | shutdown procedure, GOP-0004, Single Loop Operation, scramming the reactor only after | ||
was in use by the operators on February 1, 2018, the inspectors noted that no steps of | those steps had been completed and signed for. Upon review of the copy of GOP-0004 that | ||
Attachment 3, Shutdown from Single Loop Operation, were marked as completed, and the | was in use by the operators on February 1, 2018, the inspectors noted that no steps of | ||
attachment was not signed off as being initiated or completed. The deviation from normal | Attachment 3, Shutdown from Single Loop Operation, were marked as completed, and the | ||
practice was appropriate because the scram was not being initiated as part of a preplanned | attachment was not signed off as being initiated or completed. The deviation from normal | ||
sequence. It was instead being initiated in response to the unanticipated emergence of a | practice was appropriate because the scram was not being initiated as part of a preplanned | ||
safety concern. | sequence. It was instead being initiated in response to the unanticipated emergence of a | ||
Corrective Actions: The licensee documented the violation in the corrective action program | safety concern. | ||
and generated corrective actions to review reportability requirements. | |||
Corrective Action Reference(s): CR-RBS-2018-03953 | Corrective Actions: The licensee documented the violation in the corrective action program | ||
Performance Assessment: | and generated corrective actions to review reportability requirements. | ||
Performance Deficiency: The failure to submit a required licensee event report was a | |||
performance deficiency. | Corrective Action Reference(s): CR-RBS-2018-03953 | ||
Screening: The performance deficiency was evaluated in accordance with the reactor | Performance Assessment: | ||
oversight process and was determined to be minor because it could not be reasonably | |||
viewed as a precursor to a significant event, would not have the potential to lead to a more | Performance Deficiency: The failure to submit a required licensee event report was a | ||
significant safety concern, does not relate to a performance indicator that would have caused | performance deficiency. | ||
the performance indicator to exceed a threshold, and did not adversely affect a cornerstone | |||
objective. The performance deficiency was evaluated in accordance with the traditional | Screening: The performance deficiency was evaluated in accordance with the reactor | ||
enforcement process because it impacted the ability of the NRC to perform its regulatory | oversight process and was determined to be minor because it could not be reasonably | ||
oversight function. | viewed as a precursor to a significant event, would not have the potential to lead to a more | ||
Significance: Using example 6.9.d.9 from the NRC Enforcement Policy, the violation was | significant safety concern, does not relate to a performance indicator that would have caused | ||
determined to be a Severity Level IV violation. | the performance indicator to exceed a threshold, and did not adversely affect a cornerstone | ||
Cross-cutting Aspect: Because the violation was dispositioned using the traditional | objective. The performance deficiency was evaluated in accordance with the traditional | ||
enforcement process, no cross-cutting aspect was assigned. | enforcement process because it impacted the ability of the NRC to perform its regulatory | ||
oversight function. | |||
Significance: Using example 6.9.d.9 from the NRC Enforcement Policy, the violation was | |||
determined to be a Severity Level IV violation. | |||
Cross-cutting Aspect: Because the violation was dispositioned using the traditional | |||
enforcement process, no cross-cutting aspect was assigned. | |||
Enforcement: | |||
Violation: 10 CFR 50.73(a)(1) requires, in part, that the licensee shall submit a Licensee | |||
26 | |||
Enforcement: | |||
Violation: 10 CFR 50.73(a)(1) requires, in part, that the licensee shall submit a Licensee | |||
Event Report (LER) for any event of the type described in this paragraph within 60 days after | |||
the discovery of the event. 10 CFR 50.73(a)(2)(iv)(A) requires, in part, that the licensee shall | |||
report any event or condition that resulted in manual actuation of the reactor protection | |||
system (RPS) except when the actuation resulted from and was part of a pre-planned | |||
sequence during testing or reactor operation. Contrary to the above, on April 2, 2018, the | |||
licensee failed to submit an LER within 60 days after the discovery of an event or condition | |||
that resulted in manual actuation of the RPS that did not result from and that was not a part of | |||
a pre-planned sequence during testing or reactor operation. Specifically, the licensee failed | |||
to submit an LER within 60 days of a manual reactor scram that occurred on February 1, | |||
EXIT MEETINGS AND DEBRIEFS | 2018. | ||
The inspectors verified no proprietary information was retained or documented in this report. | Disposition: Because this SLIV violation was neither repetitive nor willful, and because it was | ||
On May 31, 2018, and on July 16, 2018, the inspectors presented the inspection results to | entered into the licensees corrective action program as Condition Report | ||
Mr. W. Maguire, Site Vice President, and other members of the licensee staff. | CR-RBS-2018-03953, it is being treated as a non-cited violation consistent with | ||
Section 2.3.2.a of the NRC Enforcement Policy. | |||
EXIT MEETINGS AND DEBRIEFS | |||
The inspectors verified no proprietary information was retained or documented in this report. | |||
On May 31, 2018, and on July 16, 2018, the inspectors presented the inspection results to | |||
Mr. W. Maguire, Site Vice President, and other members of the licensee staff. | |||
DOCUMENTS REVIEWED | |||
71111.15Operability Determinations and Functionality Assessments | |||
Attachment | |||
DOCUMENTS REVIEWED | |||
71111.15Operability Determinations and Functionality Assessments | |||
Procedures | |||
Number | |||
Title | |||
Revision | |||
EN-OE-100 | |||
Operating Experience Program | |||
12 & 13 | |||
STP-051-4206 | |||
(RPS Bypassed) RPS/RHR Reactor Vessel Level-Low, | |||
Level 3, High, Level 8, Channel Calibration and Logic | |||
G13.18.6.1.B21 | System Functional Test (B21-N680B, B21-N683B, B21- | ||
N080B) | |||
305 | |||
STP-051-4227 | |||
ECCS/RCIC Actuation Ads Trip System B Reactor | |||
Vessel Water Level Low, Level 3/High, Level 8 Channel | |||
Calibration, and Logic System Functional Test (B21- | |||
71111.18Plant Modifications | N095B, B21-N695B, B21-N693B) | ||
20 | |||
STP-501-4202 | |||
FWS/MAIN Turbine Trip System - Reactor Vessel Water | |||
Level - High Level 8, Channel Calibration and LSFT | |||
(C33-N004B, C33-K624B, C33-R606B, C33-K650-3) | |||
15 | |||
Engineering Changes | |||
G13.18.6.1.B21 | |||
Reactor Vessel Water Level - Low, Level 3 Trip Function | |||
3 | |||
G13.18.6.1.B21*003 Reactor Vessel Water Level - Low, Level 3 Trip Function | |||
3 | |||
G13.18.6.1.B21*010 Reactor Vessel Water Level - Low, Level 8 Narrow | |||
Range | |||
0, 1, 2, & 3 | |||
MCP-IC-501-4202 | |||
FWS/FEED Pump Trip System (MSO) - Reactor Vessel | |||
Water Level - High Level 8, Loop Calibration (C33- | |||
LTN006B, C33-ESN606B) | |||
0 | |||
71111.18Plant Modifications | |||
Condition Reports (CR-RBS-) | |||
CR-RBS-2014-05194 | |||
CR-RBS-2014-06685 | |||
CR-RBS-2014-06691 | |||
CR-RBS-2015-03253 | |||
CR-RBS-2015-03983 | |||
CR-RBS-2015-04065 | |||
CR-RBS-2015-04117 | |||
CR-RBS-2015-08476 | |||
CR-RBS-2015-08515 | |||
CR-RBS-2016-00791 | |||
CR-RBS-2016-00893 | |||
CR-RBS-2016-00893 | |||
CR-RBS-2016-04351 | |||
CR-RBS-2016-04353 | |||
CR-RBS-2017-02828 | |||
OE-NOE-2004-00008 | |||
OE-NOE-2004-00084 | |||
Engineering Changes | |||
Number | |||
Title | |||
Revision | |||
EC-75588 | |||
Accept As-Is Evaluation for Remainder of Cycle 20: Sparger | |||
N4C Nozzles 7 and 8 Damaged | |||
0 & 1 | |||
Procedures | |||
A-2 | |||
Procedures | |||
Number | |||
Title | |||
71152 - Problem Identification and Resolution | Revision | ||
OSP-0053 | |||
Emergency and Transient Response Support Procedure | |||
20-25 | |||
Engineering Changes | STP-000-0001 | ||
Daily Operating Logs | |||
EC-75663 | 082 | ||
DBR-0035279 | |||
GEH Comment Resolution Form | |||
Miscellaneous Documents | 0 | ||
4221.110-000- | |||
043 | |||
Operability Assessment of the River Bend Station | |||
Feedwater Sparger Assembly in the January 2018 As- | |||
CNR RBS PO-18-01-01 Foreign Material Customer Notification Report | Found Condition | ||
0 | |||
71152 - Problem Identification and Resolution | |||
Condition Reports (CR-RBS-) | |||
CR-RBS-2018-00358 | |||
CR-RBS-2018-00613 | |||
CR-RBS-2018-00633 | |||
CR-RBS-2018-00733 | |||
CR-RBS-2018-00895 | |||
CR-RBS-2018-00294 | |||
OE-NOE-2004-00008 | |||
OE-NOE-2004-00084 | |||
Engineering Changes | |||
Number | |||
Title | |||
Revision | |||
EC-75663 | |||
Loose Parts Evaluation for Material Lost From | |||
Feedwater Spargers Identified During PO-18-01 | |||
Foreign Material FME LPA-000 | |||
0 | |||
Miscellaneous Documents | |||
Number | |||
Title | |||
Revision/Date | |||
OSRC Meeting 2018-0001 Minutes | |||
OSRC Meeting 2018-0002 Minutes | |||
Action Item OE33308-20110507-A2-RBS-001 | |||
CNR RBS PO-18-01-01 Foreign Material Customer Notification Report | |||
0 | |||
ECH-NE-17-00039 | |||
River Bend MOC-20a Fuel Inspection Plan | |||
0 | |||
NEDC-31336P-A | |||
General Electric Instrument Setpoint | |||
Methodology | |||
0 | |||
NEDE-21821-A | |||
Boiling Water Reactor Feedwater | |||
Nozzle/Sparger Final Report | |||
0 | |||
NEI 96-07 | |||
Guidelines for 10 CFR 50.59 Implementation | |||
1 | |||
OE33308-20110507 | |||
Sampling Probe Found in Feedwater Sparger | |||
August 17, 2011 | |||
Miscellaneous Documents | |||
A-3 | |||
RBS-ER-99-0539 | |||
Miscellaneous Documents | |||
Procedures | Number | ||
Title | |||
Revision/Date | |||
PO 18-01 | |||
BOP Foreign Material Inspection Report | |||
RBS-ER-99-0539 | |||
Engineering Response Associated with Loose | |||
Part in the Feedwater System | |||
0 | |||
Procedures | |||
Number | |||
Title | |||
Revision | |||
AOP-0001 | |||
Work Order | Reactor Scram | ||
37 | |||
71153Follow-up of Events and Notices of Enforcement Discretion | AOP-0024 | ||
Thermal Hydraulic Stability Controls | |||
30, 31, & 32 | |||
EN-NF-102 | |||
Corporate Fuel Reliability | |||
Condition Reports (CR-RBS-) | 6 | ||
EN-OP-104 | |||
Operability Determination Process | |||
14 | |||
EN-OP-111 | |||
Operational Decision Making Issue Process | |||
15 | |||
EN-OP-117 | |||
Operations Assessments | |||
4 | |||
EOP-0001 | |||
Emergency Operating Procedure - RPV Control | |||
28 | |||
GOP-0001 | |||
Plant Startup | |||
99 | |||
GOP-0002 | |||
Power Decrease/Plant Shutdown | |||
78 | |||
GOP-0003 | |||
Scram Recovery | |||
31 | |||
GOP-0004 | |||
Single Loop Operation | |||
25 | |||
OE-100 | |||
Operating Experience Program | |||
1 | |||
R-PL-012 | |||
Corrective Action Program | |||
1 | |||
STP-000-0001 | |||
Daily Operating Logs | |||
082 | |||
Work Order | |||
52599498 | |||
71153Follow-up of Events and Notices of Enforcement Discretion | |||
Procedures | |||
Number | |||
Title | |||
Revision | |||
EN-OP-115 | |||
Conduct of Operations | |||
23 | |||
GOP-0004 | |||
Single Loop Operation | |||
23 | |||
Condition Reports (CR-RBS-) | |||
2018-03149 | |||
2018-03953 | |||
ML18194A413 | |||
SUNSI Review: | SUNSI Review: | ||
ADAMS: | |||
Non-Publicly Available | |||
Non-Sensitive | |||
Keyword: | |||
By: CHY/RDR | |||
Yes No | |||
NAME | Publicly Available | ||
SIGNATURE | Sensitive | ||
DATE | NRC-002 | ||
OFFICE | |||
SRI:DRP/C | |||
RI:DRP/C | |||
SPE:DRP/C | |||
ARI:DRP/C | |||
C:DRS/EB2 | |||
D:DRP | |||
NAME | |||
JSowa | |||
BParks | |||
CYoung | |||
MOBanion | |||
JDrake | |||
AVegel | |||
SIGNATURE | |||
/RA/ | |||
/RA/ | |||
/RA/ | |||
/RA/ | |||
/RA/ | |||
/RA/ | |||
DATE | |||
6/22/2018 | |||
6/21/2018 | |||
6/21/2018 | |||
6/25/2018 | |||
7/10/2018 | |||
7/18/18 | |||
OFFICE | |||
BC:DRP/C | |||
NAME | |||
JKozal | |||
SIGNATURE | |||
/RA/ | |||
DATE | |||
7/18/18 | |||
}} | }} | ||
Latest revision as of 17:37, 5 January 2025
| ML18194A413 | |
| Person / Time | |
|---|---|
| Site: | River Bend |
| Issue date: | 07/18/2018 |
| From: | Jason Kozal NRC/RGN-IV/DRP/RPB-C |
| To: | Maguire W Entergy Operations |
| Kozal J | |
| References | |
| IR 2018012 | |
| Download: ML18194A413 (32) | |
See also: IR 05000458/2018012
Text
July 18, 2018
Mr. William F. Maguire, Site Vice President
Entergy Operations, Inc.
River Bend Station
5485 U.S. Highway 61N
St. Francisville, LA 70775
SUBJECT:
RIVER BEND STATION - NRC BASELINE INSPECTION REPORT
Dear Mr. Maguire:
On July 16, 2018, the U.S. Nuclear Regulatory Commission (NRC) completed a baseline
inspection at your River Bend Station, Unit 1. On May 31 and July 16, 2018, the NRC
inspection team discussed the results of this inspection with you and other members of your
staff. The results of this inspection are documented in the enclosed report.
NRC inspectors documented five findings of very low safety significance (Green) in this report.
Four of these findings involved violations of NRC requirements. Additionally, NRC inspectors
documented two violations that were determined to be Severity Level IV under the traditional
enforcement process. The NRC is treating these violations as non-cited violations (NCVs)
consistent with Section 2.3.2.a of the NRC Enforcement Policy.
If you contest the violations or significance of these NCVs, you should provide a response within
30 days of the date of this inspection report, with the basis for your denial, to the U.S. Nuclear
Regulatory Commission, ATTN: Document Control Desk, Washington, DC 20555-0001; with
copies to the Regional Administrator, Region IV; the Director, Office of Enforcement; and the
NRC resident inspector at the River Bend Station.
If you disagree with a cross-cutting aspect assignment in this report, you should provide a
response within 30 days of the date of this inspection report, with the basis for your
disagreement, to the U.S. Nuclear Regulatory Commission, ATTN: Document Control Desk,
Washington, DC 20555-0001; with copies to the Regional Administrator, Region IV; and the
NRC resident inspector at the River Bend Station.
W. Maguire
2
This letter, its enclosure, and your response (if any) will be made available for public inspection
and copying at http://www.nrc.gov/reading-rm/adams.html and at the NRC Public Document
Room in accordance with 10 CFR 2.390, Public Inspections, Exemptions, Requests for
Withholding.
Sincerely,
/RA/
Jason W. Kozal, Chief
Project Branch C
Division of Reactor Projects
Docket No. 50-458
License No. NPF-47
Enclosure:
Inspection Report 05000458/2018012
w/ Attachment: Documents Reviewed
Enclosure
U.S. NUCLEAR REGULATORY COMMISSION
Inspection Report
Docket Number:
05000458
License Number:
Report Number:
Enterprise Identifier: I-2018-012-0015
Licensee:
Entergy Operations, Inc.
Facility:
River Bend Station
Location:
Saint Francisville, Louisiana
Inspection Dates:
February 1, 2018 to July 16, 2018.
Inspectors:
J. Sowa, Senior Resident Inspector
J. Drake, Senior Reactor Inspector
C. Young, Senior Project Engineer
M. OBanion, Resident Inspector (Acting)
B. Parks, Resident Inspector
Approved By:
J. Kozal, Chief, Branch C
Division of Reactor Projects
2
SUMMARY
The U.S. Nuclear Regulatory Commission (NRC) continued monitoring the licensees
performance by conducting a baseline inspection at River Bend Station in accordance with the
Reactor Oversight Process. The Reactor Oversight Process is the NRCs program for
overseeing the safe operation of commercial nuclear power reactors. Refer to
https://www.nrc.gov/reactors/operating/oversight.html for more information. Findings and
violations being considered in the NRCs assessment are summarized in the tables below.
List of Findings and Violations
Failure to Identify and Correct a Broken Feedwater Chemistry Probe
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
Barrier
Integrity
Green
Closed
None
71152 -
Problem
Identification
and
Resolution
Two examples of a self-revealed non-cited violation (NCV) of 10 CFR Part 50, Appendix B,
Criterion XVI, Corrective Action, were identified for the licensees failure to identify that a
broken chemistry probe in the feedwater system had the potential to cause an adverse impact
on plant safety, and promptly implement appropriate measures to address that condition.
Failure to Provide Adequate Procedures for Post-Scram Recovery
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
Mitigating
Systems
Green
Closed
None
71111.18 -
Plant
Modifications
The inspectors reviewed a self-revealed, non-cited violation of Technical Specification 5.4.1.a for
the licensees failure to establish, implement and maintain a procedure required by Regulatory
Guide 1.33, Revision 2, Appendix A, dated February 1978. Specifically, Procedure OSP-0053,
Emergency and Transient Response Support Procedure, Revision 22, which is required by
Regulatory Guide 1.33, inappropriately directed operations personnel to establish feedwater flow
to the reactor pressure vessel using the main feedwater regulating valve as part of the post-
scram actions. This resulted in the main feedwater regulating valves being operated outside
their design limits. This resulted in catastrophic failure of the main feedwater regulating valve
variseals and subsequent damage to multiple fuel assemblies.
3
Failure to Develop an Adequate Operational Decision-Making Issue for Compensatory Measures
Related to a Degraded Condition of the Feedwater System Sparger Nozzles
Cornerstone
Significance
Cross-cutting
Aspect
Report Section
Mitigating
Systems
Green
Closed
[H.9] -
Human
Performance,
Training
71111.15 -
Operability
Determinations
and
Functionality
Assessment
The inspectors identified a Green non-cited violation of 10 CFR Part 50, Appendix B, Criterion V,
Instructions, Procedures, and Drawings, for the failure to develop an adequate Operational
Decision-Making Issue (ODMI) document per Procedure EN-OP-111, Operational Decision-
Making Issue Process. Specifically, the licensee failed to develop an ODMI that provided
adequate guidance to the operators for safely operating the plant with degraded feedwater
sparger nozzles.
Failure to Establish Procedural Guidance for Determining Core Flow During Unanticipated
Single Loop Operations
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
Initiating
Events
Green
Closed
[P.3] -
Problem
Identification
and
Resolution,
Resolution
71153 -
Follow-up of
Events and
Notices of
Enforcement
Discretion
The inspectors reviewed a self-revealed, non-cited violation of 10 CFR Part 50 Appendix B,
Criterion V, Instructions, Procedures, and Drawings, for the licensees failure to establish
appropriate instructions in the abnormal operating procedure for thermal hydraulic instabilities.
Specifically, the procedural step for determining core flow when in single loop operations at low
power did not provide appropriate instructions to operators. As a result, station personnel could
not conclusively determine core flow and inserted a manual reactor scram.
Failure to Perform 10 CFR 50.59 Evaluation for Main Feedwater System Sparger Nozzle
Damage
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
None
SL-IV
Closed
None
71111.18 -
Plant
Modifications
The inspectors identified a Severity Level IV non-cited violation of 10 CFR 50.59, Changes,
Tests, and Experiments, for the licensees failure to provide a written safety evaluation for the
determination that operation with compensatory measures for damaged feedwater sparger
nozzles did not require a license amendment pursuant to 10 CFR 50.90, Application for
amendment of license, construction permit, or early site permit. Specifically, the licensee failed
to recognize that compensatory measures prohibiting operation in single loop conditions
required technical specification changes, and as such required prior NRC approval.
4
Failure to Conduct Adequate Transient Snap Shot Assessment Following Recirculation Pump
Trip
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
Initiating
Events
Green
Closed
None
71152 -
Problem
Identification
and
Resolution
The inspectors identified a finding for the licensees failure to adequately validate simulator
response during a transient snap shot assessment following an unexpected trip of reactor
recirculation pump A on December 19, 2012.
Failure to Submit a Licensee Event Report for a Manual Scram
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
None
SL-IV
Closed
None
71153 -
Follow-up of
Events and
Notices of
Enforcement
Discretion
The inspectors identified a Severity Level IV non-cited violation of 10 CFR 50.73, Licensee
Event Report System, for the licensees failure to submit a required licensee event report (LER).
Specifically, on February 1, 2018, after an unexpected trip of the recirculation pump B, the
licensee initiated a manual scram of the reactor that was not part of a preplanned sequence and
failed to submit an LER within 60 days.
5
INSPECTION SCOPES
Inspections were conducted using the appropriate portions of the inspection procedures (IPs) in
effect at the beginning of the inspection unless otherwise noted. Currently approved IPs with
their attached revision histories are located on the public website at http://www.nrc.gov/reading-
rm/doc-collections/insp-manual/inspection-procedure/index.html. Samples were declared
complete when the IP requirements most appropriate to the inspection activity were met
consistent with Inspection Manual Chapter (IMC) 2515, Light-Water Reactor Inspection
Program - Operations Phase. The inspectors reviewed selected procedures and records,
observed activities, and interviewed personnel to assess licensee performance and compliance
with Commission rules and regulations, license conditions, site procedures, and standards.
REACTOR SAFETY
71111.15Operability Determinations and Functionality Assessments (1 Sample)
The inspectors evaluated the following operability determinations and functionality
assessments:
(1) Review of Operational Decision-Making Issue (ODMI) associated with damaged
feedwater sparger on February 8, 2018
71111.18Plant Modifications (2 Samples)
The inspectors evaluated the following temporary or permanent modifications:
(1) OSP-0053, Emergency And Transient Response Support Procedure, following
decision to control reactor vessel level with main feedwater regulating valves during
post-scram operations
(2) Review of plant operation following modification to feedwater sparger nozzles 7 and 8
OTHER ACTIVITIES - BASELINE
71152Problem Identification and Resolution
Annual Follow-up of Selected Issues (3 Samples)
The inspectors reviewed the licensees implementation of its corrective action program
related to the following issues:
(1) Review of 1) simulator modelling of core parameters during a recirculation pump trip at
low power and 2) licensed operator training associated with single loop operations at low
power
(2) Actions to address a broken isokinetic chemistry sampling probe in the feedwater
system
(3) Actions to address fuel failures caused by debris material in the reactor vessel
6
71153Follow-up of Events and Notices of Enforcement Discretion
Personnel Performance (1 Sample)
(1) The inspectors evaluated operator response to the unexpected trip of the reactor
recirculation pump B on February 1, 2018.
INSPECTION RESULTS
Failure to Identify and Correct a Broken Feedwater System Chemistry Probe
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
Barrier
Integrity
Green
Closed
None
71152 -
Problem
Identification
and
Resolution
Two examples of a self-revealed Green finding and associated NCV of 10 CFR Part 50,
Appendix B, Criterion XVI, were identified for the licensees failure to identify that a broken
chemistry probe in the feedwater system had the potential to cause an adverse impact on
plant safety, and promptly implement appropriate measures to address that condition.
Description:
In 1999, the licensee initiated Condition Report CR-RBS-1999-1011 to document that an
isokinetic chemistry sample probe was found to be missing from its installed location in the
feedwater system, having broken off in the system. Following unsuccessful attempts to
locate and remove the missing probe, the licensee performed evaluation ER-99-0539 to
evaluate the potential impact of the missing probe on the continued operation and function of
feedwater system components. This evaluation concluded that the missing probe remaining
in the system would not present any hazard to any feedwater system components, and would
have no adverse effect on continued operation. This conclusion was based, in part, on a
calculation showing that feedwater flow would not have enough energy to levitate the probe
past a 20-foot vertical riser portion of the system, and therefore would not have the potential
to enter a feedwater sparger in the reactor vessel downstream of the vertical riser. Another
calculation showed that the impact energy of the loose probe on any feedwater components
would be negligible.
In March 2004, the NRC issued Information Notice (IN) 2004-06, Loss of Feedwater
Isokinetic Sampling Probes at Dresden Units 2 and 3 (ADAMS Accession No.
ML040711214). The IN discussed that broken probes had been discovered at five other
stations from 1990 to 2001, and further described the conditions discovered at Dresden
Nuclear Power Station (Dresden), Units 2 and 3. In 2003, three holes in a feedwater sparger
at Dresden Unit 2 were discovered, along with the missing feedwater probe in the sparger,
which had apparently caused the damage. Two probes were discovered to be in a feedwater
sparger in Dresden Unit 3, with no damage to the sparger having occurred yet. These
conditions demonstrated that not only could the probes be transported to the feedwater
spargers in the reactor vessel, but that they could potentially damage the spargers. The
licensees evaluation of this operating experience concluded that, since the broken probe at
River Bend had been replaced with a probe of a design not susceptible to the same failure,
no further action was needed. The licensee failed to address the potential impacts of the
adverse condition of the broken probe that remained loose in the feedwater system.
7
In 2011, the licensee documented an evaluation of a similar condition that had been
discovered at Brunswick Steam Electric Plant, Unit 2, where a feedwater sample probe was
discovered inside a feedwater sparger. The licensees evaluation of this operating
experience concluded that the current design (i.e. the probe that replaced the previous
broken probe) was not susceptible to this kind of failure. The licensee again failed to address
the impact of the previous broken probe that remained in the system, given that its potential
to be transported into a feedwater sparger in the reactor vessel had been shown.
In January 2018, the licensee discovered damage in the form of two holes in feedwater
sparger nozzles in the reactor vessel, with the broken probe protruding from one of the holes
in the direction of the other. The broken probe remaining in the feedwater system resulted in
potential adverse impacts on the reactor vessel wall due to impingement of feedwater flow
through the holes in the damaged sparger, as well as potential adverse impacts on the
integrity of fuel cladding due to the introduction of foreign material (pieces of the feedwater
sparger and chemistry probe) in the reactor vessel.
Corrective Actions: The broken probe was removed from the system. The licensee
performed evaluations to identify plant operational limitations to ensure that adverse impacts
to reactor pressure vessel wall integrity from additional holes in a feedwater sparger are
minimized. The licensee also issued an action to perform a review of historical loose parts
evaluations to add to tracking mechanisms and ensure adequacy of previous evaluations.
Corrective Action Reference: CR-RBS-2018-0294, CR-RBS-2018-0613, and
Performance Assessment:
Performance Deficiency: The licensees failure on two occasions to identify a broken
chemistry probe in the feedwater system had the potential to cause an adverse impact on
plant safety and to promptly implement appropriate measures to address that condition was a
performance deficiency.
Screening: The inspectors determined the performance deficiency was more than minor
because it was associated with the Cladding Performance, as well as the RCS Equipment
and Barrier Performance, attributes of the Barrier Integrity Cornerstone, and adversely
impacted the cornerstone objective to provide reasonable assurance that physical design
barriers (fuel cladding, reactor coolant system, and containment) protect the public from
radionuclide releases caused by accidents or events. Specifically, the unaddressed condition
of the broken probe remaining in the feedwater system resulted in damage to the feedwater
sparger, which resulted in thermal stresses to the reactor pressure vessel due to feedwater
impingement on the inner reactor pressure vessel wall, as well as the introduction of foreign
material inside the reactor vessel having the potential to result in damaged fuel. The licensee
performed an evaluation to determine what plant operational limitations were necessary in
order to ensure that additional thermal stresses on the reactor pressure vessel inner wall
remained below a threshold that would challenge the structural integrity of the vessel.
Significance: In accordance with Inspection Manual Chapter 0609, Appendix A, Section 5.0,
RCS boundary issues other than pressurized thermal shock are evaluated under the Initiating
Events Cornerstone. Using Inspection Manual Chapter 0609, Appendix A, The Significance
Determination Process for Findings At-Power, Exhibit 1, Initiating Events Screening
Questions, the finding was screened, as a potential loss of coolant accident (LOCA) initiator,
as having very low safety significance (Green) because, after a reasonable assessment of
8
degradation, the finding could not result in exceeding the RCS leak rate for a small LOCA and
could not have likely affected other systems used to mitigate a LOCA.
Cross-cutting Aspect: A cross-cutting aspect of P.5, Operating Experience, was determined
to be applicable to the performance deficiencies; however, no cross-cutting aspect was
assigned since the performance deficiencies occurred in 2004 and 2011, and are not
indicative of current licensee performance.
Enforcement:
Violation: Title 10 CFR Part 50, Appendix B, Criterion XVI, requires, in part, that measures
shall be established to assure that conditions adverse to quality, such as failures,
malfunctions, deficiencies, deviations, defective material and equipment, and
nonconformances are promptly identified and corrected. Contrary to the above, from
June 2004 to January 2018, the licensee failed to establish measures to assure that a
condition adverse to quality was promptly identified and corrected. Specifically, the licensee
failed to identify and correct a condition involving a broken sampling probe inside the
feedwater system. The uncorrected condition resulted in damage to a feedwater sparger,
with the potential to impact the available margin for integrity of the reactor vessel.
Disposition: This violation is being treated as a non-cited violation, consistent with
Section 2.3.2.a of the Enforcement Policy.
Failure to Provide Adequate Procedures for Post-Scram Recovery
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
Mitigating
Systems
Green
Closed
None
71111.18 -
Plant
Modifications
The inspectors reviewed a self-revealing, non-cited violation of Technical Specification 5.4.1.a
for the licensees failure to establish, implement and maintain a procedure required by
Regulatory Guide 1.33, Revision 2, Appendix A, dated February 1978. Specifically,
Procedure OSP-0053, Emergency and Transient Response Support Procedure,
Revision 22, which is required by Regulatory Guide 1.33, inappropriately directed operations
personnel to establish feedwater flow to the reactor pressure vessel using the main feedwater
regulating valve (MFRV) as part of the post-scram actions. This resulted in the MFRVs being
operated outside their design limits. This resulted in catastrophic failure of the MFRV
variseals and subsequent damage to multiple fuel assemblies.
Description:
In January 2015, the licensee revised Procedure OSP-0053, Emergency And Transient
Response Support Procedure, to use one of the three MFRVs to control reactor water level
following a scram event, and not use C33-LVF002, Start-Up FRV, which is designed to be
used for this application. This resulted in proceduralizing the use of a MFRV in circumstances
below the minimum controllable flow for the MFRV of 209,000 lbs/hr that the Main FRV
Copes Vulcan sizing datasheet provides as the a minimum controllable flow condition. As a
result of this change to the procedure to use a MFRV, the valves cycled numerous times in
the process of controlling level at low flow post-scram when feedwater flow demand was
below the MFRV minimum controllable flow volume. This repeated cycling of the valve led to
excessive open/close cycling of the MFRVs and caused the catastrophic failure of the
variseals.
9
As a result, foreign material parts of the variseal were introduced into the core. It is
suspected that this material resulted in six nuclear fuel cladding failures caused by debris
fretting.
Corrective Actions: The licensee revised Procedure OSP-0053, Emergency and Transient
Response Support Procedure, to control reactor vessel level post scram using a startup
feedwater regulating valve and modified the design of the MFRV variseal.
Corrective Action Reference: CR-RBS-2016-00893
Performance Assessment:
Performance Deficiency: The failure to establish adequate procedural guidance for operation
of the main feedwater system was a performance deficiency.
Screening: The performance deficiency was more than minor, and therefore a finding,
because it was associated with the procedure quality attribute of the Mitigating Systems
Cornerstone and adversely affected the cornerstone objective to ensure the availability,
reliability, and capability of systems that respond to initiating events to prevent undesirable
consequences. Specifically, Procedure OSP-0053, Emergency and Transient Response
Support Procedure, Revision 22, inappropriately directed operations personnel to establish
feedwater flow to the reactor pressure vessel using the MFRV as part of the post-scram
actions. This resulted in the MFRVs being operated outside their design limits.
Significance: The inspectors screened the finding in accordance with Inspection Manual
Chapter 0609, Appendix A, The Significance Determination Process for (SDP) for Findings
At-Power. Using Inspection Manual Chapter 0609, Appendix A, Exhibit 2, Mitigating
Systems Screening Questions, the inspectors determined this finding was of very low safety
significance (Green) because the finding: (1) was not a deficiency affecting the design or
qualification of a mitigating structure, system, or component, and did not result in a loss of
operability or functionality; (2) did not represent a loss of system and/or function; (3) did not
represent an actual loss of function of at least a single train for longer than its technical
specification allowed outage time, or two separate safety systems out-of-service for longer
than their technical specification allowed outage time; and (4) did not represent an actual loss
of function of one or more nontechnical specification trains of equipment designated as high
safety-significant in accordance with the licensees maintenance rule program.
Cross-cutting Aspect: No cross-cutting aspect was assigned since the performance
deficiency occurred in January 2015 and is not indicative of current licensee performance.
Enforcement:
Violation: Technical Specification 5.4.1.a requires in part, that written procedures shall be
established, implemented, and maintained covering the applicable procedures recommended
in Regulatory Guide 1.33, Revision 2, Appendix A, dated February 1978. Regulatory
Guide 1.33, Appendix A, Section 6.u., identifies procedures for responding to a reactor trip as
required procedures. Procedure OSP-0053, Attachment 16, Post Scram
Feedwater/Condensate Manipulations Below 5% Reactor Power, was a procedure
established by the licensee for responding to a reactor trip.
Contrary to the above, from January 30, 2015, until April 13, 2017, the licensee failed to
maintain adequate written procedures for responding to a reactor trip. Specifically,
Procedure OSP-0053 inappropriately directed operations personnel to establish feedwater
10
flow to the reactor pressure vessel using the MFRV as part of the post-scram actions. The
MFRV operator characteristics are not designed to operate at the low flow conditions
immediately following a reactor scram from high power. As a result, the MFRV variseals
degraded and resulted in damage to multiple fuel assemblies. Subsequent to the event, the
licensee changed the procedure, directing operations personnel to utilize one of the startup
feedwater regulating valves.
Disposition: This violation is being treated as an non-cited violation consistent with
Section 2.3.2.a of the NRC Enforcement Policy.
Failure to Develop an Adequate Operational Decision-Making Issue for Compensatory
Measures Related to a Degraded Condition of the Feedwater System Sparger Nozzles
Cornerstone
Significance
Cross-cutting
Aspect
Report Section
Mitigating
Systems
Green
Closed
[H.9] -
Human
Performance,
Training
71111.15 -
Operability
Determinations
and
Functionality
Assessments
The inspectors identified a Green non-cited violation of 10 CFR Part 50, Appendix B,
Criterion V, Instructions, Procedures, and Drawings, for the failure to develop an adequate
operational decision-making issue (ODMI) document per Procedure EN-OP-111, Operational
Decision-Making Issue Process. Specifically, the licensee failed to develop an ODMI that
provided adequate guidance to the operators for safely operating the plant with degraded
feedwater sparger nozzles.
Description:
During a reactor startup on February 1, 2018, reactor recirculation pump B unexpectedly
tripped during an attempted upshift to fast speed. As a result, the plant was operating with
recirculation pump A in fast speed and recirculation pump B not running. Prior to this startup,
during an outage that was being conducted to replace failed fuel assemblies, damage to
feedwater sparger nozzles was identified.
Example 1: The evaluation of the damaged feedwater sparger nozzles 7 and 8 on
sparger N4C identified that the damaged sections of the feedwater sparger nozzles had the
potential to adversely affect the vessel cladding by allowing relatively colder water to directly
flow into the relatively hotter vessel wall, thus inducing thermal fatigue. All components of the
reactor coolant system (RCS) are designed to withstand effects of cyclic loads due to system
pressure and temperature changes. These loads are introduced by startup (heatup) and
shutdown (cooldown) operations, power transients, and reactor trips. Limits are established
for pressure and temperature changes during RCS heatup and cooldown, such that plant
systems remain within the design assumptions and the stress limits for cyclic operation.
Limits on RCS pressure, temperature, heatup rate, and cooldown rate define allowable
operating regions and operating cycles to prevent nonductile failure of system components.
Because operation with the sparger nozzle damage was outside the limits originally analyzed,
the licensee requested General Electric-Hitachi (GEH) to provide an operability analysis of
the degraded condition. GEH Report 004N6557, Revision 0, dated January 26, 2018,
Operability Assessment of the River Bend Station Feedwater Sparger Assembly in the
January 2018 As-found Condition, stated, in part, this evaluation does not account for Final
11
Feedwater Temperature Reduction (FFWTR), Feedwater Heater Out-of-Service (FWH OOS)
conditions, nor Single Loop Operation (SLO) operating conditions. Based on this analysis,
the licensees engineering department concluded that the recommended classification of this
condition was OPERABLE-COMP MEAS (operable with compensatory measures), with the
degraded/nonconforming condition being the holes in the feedwater sparger nozzles. Based
on the results of this analysis, one of the operational restrictions/limitations stipulated in the
licensees ODMI was that, RBS will not operate in Single Loop Operation (SLO).
The ODMI developed by the licensee included two trigger points:
Trigger Point 1:
An unexpected operational state below approximately 85 percent power in which the vessel
wall-to-feedwater delta-T stabilizes at less than or equal to 154 degrees Fahrenheit (F), as
detected by periodic monitoring during normal operations, OR due to a transient as defined
above.
Trigger Point 2:
An unexpected operational state in which the vessel wall-to-feedwater delta-T stabilizes at
greater than 154 degrees F, as detected by periodic monitoring during normal operations, OR
due to a transient as defined above.
The ODMI failed to provide adequate guidance to the operators if they found themselves in
any of the conditions that GEH had listed as not being evaluated for continued operation with
the degraded condition. When reactor recirculation pump B failed to shift to fast speed at
9:46 a.m., the operators logged entry into Procedure GOP-004, Single Loop Operations.
The plant was in single loop operating conditions, and remained there until 10:57 a.m. when
the Mode switch was placed in shutdown. The ODMI failed to provide adequate guidance on
the actions required if the plant entered any of the conditions that were not evaluated for the
degraded sparger condition. In addition, the Just In Time Training given to the operators
prior to taking the watch to commence power operations with the degraded condition did not
address these issues either. As a result, rather than take prompt actions to place the plant in
a known safe condition upon entry into single loop operations, the control room supervisor
requested that GEH be contacted to determine if it was acceptable to remain in single loop
operations.
Example 2: The evaluation of the damaged feedwater sparger nozzles 7 and 8 on
sparger N4C identified that the damaged sections of the feedwater sparger nozzles had the
potential to adversely affect the B narrow range level instrument. The damage on feedwater
sparger N4C created unexpected feedwater flow paths in the reactor vessel during plant
operation that had the potential to adversely affect the "B" variable leg reactor water level
instruments. There were two potential impacts of this condition on indicated level from
narrow range level instruments that tap off of the B variable leg. Flow from the holes in the
feedwater sparger nozzle elbows could flow across the variable leg nozzle opening at AZ
200 degrees (B Leg), lowering the pressure on the variable leg side of the differential
pressure measurements, or the flow from the sparger nozzle damage could directly impact
the B variable leg, increasing the pressure on the variable leg side of the differential pressure
measurements.
12
The narrow range RPV level instrumentation supports two reactor water level trips: low level
(Level 3) and high level (Level 8). During a transient or accident event where the RPV water
level is changing, the trip signal from the B narrow range instrument could be affected.
Based on the GE report, during a transient or accident event where the RPV water level is
increasing, the high level (Level 8) trips (RPS trip and Feedwater Pump trip) in the affected
channel may occur later than the trips in the unaffected channels. This may delay the overall
Level 8 trips. For the Level 8 RPS trip, the margin between the calculated nominal trip
setpoint and the technical specification allowable value is 0.77 inches. For the Level 3 RPS
trip, the margin between the calculated nominal trip setpoint and the technical specification
allowable value is 0.67 inches. An operability determination of the narrow range level
instruments was performed under CR-RBS-2018-00633 CA-01.
The ODMI developed by the licensee included two trigger points:
Trigger Point 1:
Action: Refer to applicable SRs as specified by STP-000-0001, Att. 9.2
Step 30 in STP-000-0001 not within 4 inches
Step 71 in STP-000-0001 not within 6 inches
Notify the Duty Manager and the Ops Duty Manager
Trigger Point 2:
The magnitude of the B channel deviation is 1.5 inches in either direction from the average
of the A, C and D channel average + 1.1 inches.
Notify the Duty Manager and the Engineering Duty Manager.
The ODMI implemented by the licensee allowed level indication deviation in the affected
channel for the B21-LTN080 instruments to be monitored to ensure it remained within the
allowable margin to ensure the technical specification trip limit is not exceeded. It stated in
part that, If the deviation exceeds a change of 1.5 inches from historical deviation of
1.1 inches above the average of the A, C, and D channels in either an increasing or
decreasing direction, then condition will be evaluated by engineering. The monitored trigger
point of +1.5 inches will provide adequate margin for both the Level 3 and Level 8 trips.
However, if a 1.5-inch bias in the low direction would have been reached, two Technical
Specification (TS) Allowable Values could have been exceeded (by 0.5 inches for TS
Table 3.3.5.2-1, Function 2, Reactor Core Isolation Cooling System Instrumentation, and by
0.49 inches for TS Table 3.3.5.2-1, Function 5, Reactor Protection System Instrumentation).
The 1.5-inch bias in the low direction would have rendered the instrument inoperable based
on 10 CFR 50.36(c)(2)(i), which states, Limiting conditions for operation are the lowest
functional capability or performance levels of equipment required for safe operation of the
facility. Since the limiting conditions for operations (LCOs) include Allowable Values (e.g.,
LCO 3.3.5.2 includes Table 3.3.5.2-1 which has Allowable Values for Functions 2 and 5), the
Allowable Values are understood to be the lowest functional capability or performance levels
of equipment required for safe operation of the facility.
The licensees technical specifications provide the following guidance: Surveillance
Requirement 3.0.1, Failure to meet a Surveillance, whether such failure is experienced
during the performance of the Surveillance or between performances of the Surveillance,
shall be failure to meet the LCO.
13
1.1 Definitions: A CHANNEL CALIBRATION shall be the adjustment, as necessary, of the
channel output such that it responds within the necessary range and accuracy to known
values of the parameter that the channel monitors
In addition, the TS Bases state, SR 3.0.1 through SR 3.0.4 establish the general
requirements applicable to all Specifications and apply at all times, unless otherwise stated.
The OPERABILITY of the RPS (Reactor Protection System) is dependent on the
OPERABILITY of the individual instrumentation channel Functions specified in
Table 3.3.1.1-1. Each Function must have a required number of OPERABLE channels [2 per
RPS trip system for the vessel level function] per RPS trip system, with their setpoints within
the specified Allowable Value, where appropriate. The actual setpoint is calibrated consistent
with applicable setpoint methodology assumptions. Each channel must also respond within
its assumed response time. Allowable Values are specified for each RPS Function specified
in the Table. Nominal trip setpoints are specified in the setpoint calculations. The nominal
setpoints are selected to ensure that the actual setpoints do not exceed the Allowable Value
between successive channel calibrations. Operation with a trip setpoint less conservative
than the nominal trip setpoint, but within its Allowable Value, is acceptable. A channel is
inoperable if its actual trip setpoint is not within its required Allowable Value.
Process effects impact the establishment of the appropriate Nominal Trip Setpoint, which is
determined by addressing all instrument channel uncertainties (including biases) and
offsetting them from the Analytical Limit. The currently licensed Allowable Values are fixed
within the technical specification tables. Nominal Trip Setpoints are established on the basis
of a calculation that identifies all known uncertainties between the Analytical Limit and the
Nominal Trip Setpoint. If a new, unaccounted-for process effect bias in the nonconservative
direction is discovered, this effect needs to be reflected in the calculation of a new Nominal
Trip Setpoint and a corresponding new Allowable Value. However, in this case, the licensee
did not elect to pursue a license amendment or other process to change its currently licensed
Allowable Value, nor did it ask for a temporary enforcement discretion. Therefore, with the
new (unaccounted for) postulated process effect present, this has the effect of making the
existing Nominal Trip Setpoint (calibrated value) offset in the nonconservative direction by the
amount of the new postulated process effect (i.e., up to 1.5 inches), which reduces the margin
between the actual trip setpoint and the existing licensed Allowable Value.
Therefore, to meet the River Bend technical specification requirement that a channel be
considered inoperable if its actual trip setpoint is not within its required Allowable Value
without changing the currently licensed Allowable Value, only approximately a 1/2-inch of the
1.5 inches of new postulated process effect can be accommodated between the existing
calibrated setpoint and the (existing) licensed Allowable Value. Thus, the direction to notify
engineering only if the Rx vessel level indication bias had reached a value of 1.5 inches in
either direction was inadequate direction for the operating staff in order to ensure that the
instruments remained operable.
Corrective Actions: The licensee corrected the condition by revising the ODMI to include
adequate operator guidance and trigger points.
Corrective Action Reference: CR-RBS-2018-03148
14
Performance Assessment:
Performance Deficiency: The failure to establish ODMI guidance per Procedure EN-OP-111
to address the compensatory measures implemented to maintain operability of the plant with
degraded feedwater sparger nozzles was a performance deficiency.
Screening: For Example 1, the performance deficiency was more than minor, and therefore a
finding, because it was associated with the equipment reliability attribute of the Mitigating
Systems Cornerstone and adversely affected the cornerstone objective to ensure the
availability, reliability, and capability of systems that respond to initiating events to prevent
undesirable consequences. Specifically, the licensee failed to provide adequate guidance to
the operators for actions required if the plant inadvertently entered any of the unanalyzed
conditions for continued operation with the degraded sparger. For Example 2, the
performance deficiency was more than minor, and therefore a finding, because if left
uncorrected it would have the potential to lead to a more significant safety concern.
Specifically, the use of less conservative calculated values than the Allowable Values stated
in the facility TS as a basis for establishing a threshold for operability of TS equipment could
result in the inappropriate evaluation of actual degraded conditions that impact the ability of
components to perform their required safety functions.
Significance: The inspectors screened the finding in accordance with Inspection Manual
Chapter 0609, Appendix A, The Significance Determination Process for (SDP) for Findings
At-Power. Using Inspection Manual Chapter 0609, Appendix A, Exhibit 1, Initiating Events
Screening Questions, the inspectors determined this finding was of very low safety
significance (Green) because for Example 1, the finding would not result in exceeding the
RCS leak rate for a small LOCA and could not have likely affected other systems used to
mitigate a LOCA. For Example 2, it was not a design/qualification deficiency, did not
represent a loss of system safety function, did not result in a loss of function of a single train
for greater than its TS-allowable outage time, did not result in a loss of function of nonsafety-
related risk-significant equipment and was not risk significant due to external events. In
addition, no actual deviation of the B narrow range level instrument was observed during
plant startup on February 9, 2018.
Cross-cutting Aspect: This finding had a cross-cutting aspect of human performance, change
management H.3: Leaders use a systematic process for evaluating and implementing
change so that nuclear safety remains the overriding priority. Specifically, the licensee did
not use a systematic process to develop and verify the adequacy of the ODMIs associated
with the compensatory measures implemented for the degraded sparger.
Enforcement:
Violation: Title 10 CFR Part 50, Appendix B, Criterion V, requires in part that, activities
affecting quality shall be prescribed by documented instructions, procedures, or drawings, of
a type appropriate to the circumstances. Licensee Procedure EN-OP-111, Operational
Decision-Making Issue (ODMI) Process, Revision 16, an Appendix B quality-related
procedure, provides instructions for developing guidance for plant operation with
compensatory measures in place to maintain plant system operable with degraded
conditions. Procedure EN-OP-111, step 5.2.4, states that Operational Decision-Making
Considerations should ensure that a course of action is selected based upon a critical
consideration of risks and potential consequences, as well as a thorough understanding of
alternate solutions. The final decision should be a deliberate act, providing clear direction,
trigger points, contingencies, and abort criteria. The Action Plans should provide clear
15
guidance in each ODMI which delineate actions to be taken when conditions escalate
unexpectedly, conditions are outside the scope of the ODMI analysis, or actions are not able
to be implemented. Actions that contain recommendations to "consider or evaluate" in
response to triggers should be avoided. When such actions are used, a definite period to
finish the evaluation or consideration should be provided.
Contrary to the above, prior to February 1, 2018, the licensee failed to ensure that the ODMIs
provided a course of action based upon a critical consideration of risks and potential
consequences, as well as a thorough understanding of alternate solutions; and that the final
decision was a deliberate act providing clear direction, trigger points, contingencies, and abort
criteria. Specifically, the licensee failed to develop adequate guidance for the operators to
maintain safe operation of the plant with compensatory measures in place for degraded
feedwater sparger nozzles. The action plans failed to provide clear guidance in each ODMI
to delineate actions to be taken when conditions escalate unexpectedly; instead, the actions
specified directed the operators to consult with offsite contractors regarding the acceptability
of allowing the plant to remain in operation with given conditions.
Disposition: This violation is being treated as a non-cited violation, consistent with
Section 2.3.2.a of the NRC Enforcement Policy.
Failure to Establish Procedural Guidance for Determining Core Flow During Unanticipated
Single Loop Operations
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
Initiating
Events
Green
Closed
[P.3] -
Problem
Identification
and
Resolution,
Resolution
71153 -
Follow-up of
Events and
Notices of
Enforcement
Discretion
The inspectors reviewed a self-revealed, non-cited violation of 10 CFR Part 50, Appendix B,
Criterion V, Instructions, Procedures and Drawings, for the licensees failure to establish
appropriate instructions in the abnormal operating procedure for thermal hydraulic
instabilities. Specifically, the procedural step for determining core flow when in single loop
operations at low power did not provide appropriate instructions to operators. As a result,
station personnel could not conclusively determine core flow and inserted a manual reactor scram.
Description:
On February 1, 2018, with the unit in Mode 1 at approximately 27 percent power, reactor
recirculation pump B unexpectedly tripped during an upshift in the speed of the pump. As a
result, the reactor was in a single loop configuration with the recirculation pump A running in
fast speed and the recirculation pump B not running. Operators entered Abnormal Operating
Procedure AOP-0024, Thermal Hydraulic Instability Controls, Revision 30, as a result of the
unplanned entry into single loop operations. Step 5.8 of this procedure directed operators to
determine core flow and enter the General Operating Procedure GOP-004, for single loop
operations. Step 5.8 also instructed operators to determine core flow using process computer
point B33NA01V when in a configuration with one recirculation pump in fast speed and one
recirculation pump off. Control room operators observed the value of this data point as
13.9 Mlbm/hr. The operators concluded that this value was not valid since the indicated flow
16
was much lower than expected with one recirculation pump running in fast speed. The
operators then observed a value of 27.3 Mlbm/hr core flow using the ERIS data point for
B33NA01V. This value appeared to be a valid number based on the single loop operation
power/flow map contained in AOP-0024, Attachment 2. Normal data points are displayed in
ERIS with a white text, but control room operators observed the ERIS data point displayed in
a magenta color. Additionally, the word suspect appeared adjacent to the data point for
core flow. Control room operators contacted information technology personnel and attempted
to understand the magenta color and suspect information associated with the core flow data
point. Concurrently, operators attempted to validate core flow using alternate means but
were unsuccessful as the alternate indications did not provide accurate core flow readings at
low reactor power when in a single loop configuration. After approximately one hour spent
seeking to understand the unfamiliar indication associated with B33NA01V, control room
operators conducted a brief and made the decision to shut down the unit due to the
uncertainties associated with the core flow data point. Following plant shutdown and
subsequent troubleshooting and investigation, licensee personnel concluded that the
magenta text and suspect note associated with ERIS B33NA01V was an expected system
response. Below approximately 40 percent core flow, the plant process computer shifts the
calculation method from the primary means of calculating core flow using the sum of jet pump
flows to an alternate process that uses core plate differential pressure. As a result of shifting
to the alternate calculation of core flow, data point ERIS B33NA01V was programmed to turn
magenta in color and display suspect to alert operators that the method of calculating core
flow had changed.
The inspectors reviewed Condition Report CR-RBS-2012-07759. This condition report was
generated by operations department personnel on December 19, 2012, and identified that
ERIS point B33NA01V indicated suspect and was not available for use. The condition
report also stated that this data point was needed for determining core flow when the plant
configuration consisted of one recirculation pump running in fast speed and another
recirculation pump was off. The inspectors confirmed that this condition report was generated
during a single loop plant configuration that was the result of an unanticipated reactor
recirculation pump A trip on December 19, 2012. The condition report corrective actions
explained the reason for the suspect reading of ERIS point B33NA01V. No corrective
actions were generated to address AOP-0024, which directs licensed operators to validate
core flow in single loop operations. Additionally, no corrective actions were generated to
validate plant simulator response to unanticipated single loop operations.
Corrective Actions: After this information was disseminated to licensed operators, the
licensee implemented procedural changes to AOP-0024 that provided amplifying information
regarding B33NA01V validated core flow. Specifically, the licensee revised the procedure on
February 7, 2018, in order to 1) direct operators to determine core flow using ERIS data point
B33NA01V during single loop operations when core flow is below 40 percent and 2) provide
clear guidance regarding expected system response of the process computer data points
during abnormal flow configurations.
Corrective Action Reference: CR-RBS-2018-00776
Performance Assessment:
Performance Deficiency: The failure to establish appropriate guidance to determine core flow
during single loop operations in quality-related abnormal operating procedure AOP-0024,
Thermal Hydraulic Instability Controls, Revision 30, was a performance deficiency.
17
Screening: The performance deficiency was more than minor, and therefore a finding,
because it was associated with the procedure quality attribute of the Initiating Events
Cornerstone and adversely affected the cornerstone objective to limit the likelihood of events
that upset plant stability. Specifically, the failure to understand core flow data indicated by
plant process computer point B33NA01V and ERIS data point B33NA01V resulted in
confusion and the ultimate decision to insert a manual reactor scram.
Significance: The inspectors screened the finding in accordance with Inspection Manual
Chapter 0609, Appendix A, The Significance Determination Process for (SDP) for Findings
At-Power. Using Inspection Manual Chapter 0609, Appendix A, Exhibit 1, Initiating Events
Screening Questions, the inspectors determined this finding is of very low safety significance
(Green) because the finding did not cause a reactor trip and the loss of mitigation equipment
relied upon to transition the plant from the onset of the trip to a stable shutdown condition.
Cross-cutting Aspect: This finding has a cross-cutting aspect in the area of problem
identification and resolution, resolution, because the licensee failed to take effective
corrective actions to address issues in a timely manner commensurate with their safety
significance. Specifically, the station failed to implement procedure changes to AOP-0024
after discovering similar confusing indications associated with B33NA01V on
December 19, 2012.
Enforcement:
Violation: Title 10 CFR Part 50, Appendix B, Criterion V, requires in part that, activities
affecting quality shall be prescribed by documented instructions, procedures, or drawings, of
a type appropriate to the circumstances.
Contrary to the above, prior to February 7, 2018, the licensee failed to provide a procedure of
a type appropriate to the circumstances for an activity affecting quality. Specifically,
AOP-0024, Thermal Hydraulic Stability Controls, a quality-related procedure, was not
appropriate to the circumstances. AOP-0024 did not provide accurate and adequate
instruction to operators to determine core flow during single loop operations. The licensee
restored compliance by revising AOP-0024 to include accurate and adequate guidance to
determine core flow during unanticipated single loop operations.
Disposition: This violation is being treated as an non-cited violation consistent with
Section 2.3.2.a of the NRC Enforcement Policy.
Failure to Perform 10 CFR 50.59 Evaluation for Main Feedwater System Sparger Nozzle
Damage
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
None
SL-IV
Closed
None
71111.18 -
Plant
Modifications
The inspectors identified a Severity Level IV NCV of 10 CFR 50.59, Changes, Tests, and
Experiments, for the licensees failure to provide a written safety evaluation for the
determination that operation with compensatory measures for damaged feedwater sparger
nozzles did not require a license amendment pursuant to 10 CFR 50.90, Application for
amendment of license, construction permit, or early site permit. Specifically, the licensee
18
failed to recognize that compensatory measures prohibiting operation in single loop
conditions were technical specification changes, and as such required prior NRC approval.
Description:
During an outage that was conducted to replace failed fuel assemblies in January 2018,
damage to feedwater sparger nozzles was identified. The evaluation of the damaged
feedwater sparger nozzles #7 and #8 on sparger N4C identified that the damaged sections of
the feedwater sparger nozzles had the potential to adversely affect the vessel cladding by
allowing relatively colder water to directly flow into the relatively hotter vessel wall, thus
inducing thermal fatigue. All components of the RCS are designed to withstand effects of
cyclic loads due to system pressure and temperature changes. These loads are introduced
by startup (heatup) and shutdown (cooldown) operations, power transients, and reactor trips.
Limits are established for pressure and temperature changes during RCS heatup and
cooldown, such that plant systems remain within the design assumptions and the stress limits
for cyclic operation. Limits on RCS pressure, temperature, heatup rate, and cooldown rate
define allowable operating regions and operating cycles to prevent nonductile failure of
system components. Because operation with the sparger nozzle damage was outside the
limits originally analyzed, the licensee requested General Electric-Hitachi (GEH) to provide an
operability analysis of the degraded condition. GEH Report #004N6557 Revision 0, dated
January 26, 2018, Operability Assessment of the River Bend Station Feedwater Sparger
Assembly in the January 2018 As-found Condition, stated in part, this evaluation does not
account for Final Feedwater Temperature Reduction (FFWTR), Feedwater Heater Out-of-
Service (FWH OOS) conditions, nor Single Loop Operation (SLO) operating conditions.
Based on this analysis, the licensees engineering department concluded that the
recommended classification of this condition was OPERABLE-COMP MEAS (operable with
compensatory measures), with the degraded/nonconforming condition being the holes in the
feedwater sparger nozzles. One of the operational restrictions/limitations was that, RBS will
not operate in Single Loop Operation (SLO). These compensatory measures directly
affected Technical Specification (TS) 3.4.1, Recirculation Loops Operating. The TS limiting
condition for operation (LCO) B, One recirculation loop shall be in operation, which is
applicable when operating in Modes 1 and 2, had the following limitations:
1.
THERMAL POWER 77.6% rated thermal power (RTP);
2.
Total core flow within limits;
3.
LCO 3.2.1,"AVERAGE PLANAR LINEAR HEAT GENERATION RATE (APLHGR),"
single loop operation limits specified in the Core Operating Limits Reports (COLR);
4.
LCO 3.2.2,"MINIMUM CRITICAL POWER RATIO (MCPR)," single loop operation
limits specified in the COLR; and
5.
LCO 3.3.1.1, "Reactor Protection System (RPS) Instrumentation," Function 2.b
(Average Power Range Monitors Flow Biased Simulated Thermal Power- High), Allowable
Value for single loop operation as specified in the COLR.
The licensees compensatory measures established a more restrictive LCO whereby Single
Loop Operations are limited by more restrictive criteria than those stated in the existing LCO.
Specifically, the licensees compensatory measures stated that the station would not operate
in Single Loop Operation.
NRC Administrative Letter 98-10: Dispositioning of Technical Specifications That Are
Insufficient To Assure Plant Safety, dated December 29, 1988, provides the following
guidance:
19
Title 10 of the Code of Federal Regulations, Section 50.36, Technical Specifications
requires that each TS limiting condition for operation (LCO) specify, at a minimum, the lowest
functional capability or performance level of equipment required for the safe operation of the
facility.
IMC0326 states, in part: Additionally, if a compensatory measure involves a temporary facility
or procedure change, 10 CFR 50.59 should be applied to the temporary change with the
intent to determine whether the temporary change/compensatory measure itself (not the
degraded or nonconforming condition) impacts other aspects of the facility or procedures
described in the UFSAR. In considering whether a temporary facility or procedure change
impacts other aspects of the facility, a licensee should apply 10 CFR 50.59, paying particular
attention to ancillary aspects of the temporary change that result from actions taken to directly
compensate for the degraded condition. Whenever degraded or nonconforming conditions
are discovered, 10 CFR Part 50, Appendix B, requires prompt corrective action to correct or
resolve the condition.
In summary, the discovery of an improper or inadequate TS value or required action is
considered a degraded or nonconforming condition as defined in IMC0326. Imposing
administrative controls in response to an improper or inadequate TS is considered an
acceptable short-term corrective action. The NRC staff expects that, following the imposition
of administrative controls, an amendment to the TS, with appropriate justification and
schedule, will be submitted in a timely fashion. Once any amendment correcting the TS is
approved, the licensee must update the final safety analysis report, as necessary, to comply
with 10 CFR 50.71(e).
Because the licensee did not perform a 50.59 screening for the compensatory measures
associated with the restricted operating conditions, the licensee failed to recognize that the
TSs were now non-conservative and that NRC approval was required.
Corrective Actions: The licensee documented the violation in the corrective action program
and created actions to review 50.59 screening requirements.
Corrective Action Reference: CR-RBS-2018-03147
Performance Assessment:
Performance Deficiency: The failure to perform a written safety evaluation for the effect of
compensatory measures implemented due to degraded feedwater sparger nozzles was a
performance deficiency.
Screening: The performance deficiency was evaluated in accordance with the traditional
enforcement process because it impacted the ability of the NRC to perform its regulatory
oversight function.
Significance: Using example 6.1.d.2 from the NRC Enforcement Policy, the violation was
determined to be a Severity Level IV violation.
Cross-cutting Aspect: Because the violation was dispositioned using the traditional
enforcement process, no cross cutting aspect was assigned.
20
Enforcement:
Violation: Title 10 CFR 50.59(d)(1) requires, in part, that the licensee shall maintain records
of changes in the facility, of changes in procedures, and of tests and experiments as
described in the updated final safety analysis report (UFSAR). These records must include a
written evaluation which provides a basis for the determination that the change, test, or
experiment does not require a license amendment.
Contrary to the above, since January 29, 2018, the licensee failed to maintain records of a
change to the facility, as described in the UFSAR, that include a written evaluation which
provides a basis for the determination that the change did not require a license amendment.
Specifically, the licensee made changes pursuant to 10 CFR 50.59(c) to the plant as
described in the UFSAR and did not provide a written evaluation for the determination that
compensatory measures prohibiting operation in single loop condition were technical
specification changes, and as such required prior NRC approval.
Disposition: This violation is being treated as an non-cited violation consistent with
Section 2.3.2.a of the NRC Enforcement Policy.
Failure to Conduct Adequate Transient Snap Shot Assessment Following Recirculation Pump
Trip
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
Green
Closed
None
71152 -
Problem
Identification
and
Resolution
The inspectors identified a Green finding for the licensees failure to adequately validate
simulator response during a transient snap shot assessment following an unexpected trip of
reactor recirculation pump A on December 19, 2012.
Description:
On December 19, 2012, with the plant operating at 100 percent power, reactor recirculation
pump A unexpectedly tripped off. As a result, the plant configuration consisted of one
recirculation pump running in fast speed and the other recirculation pump secured. During
this single loop configuration, station personnel identified that emergency response
information system (ERIS) point B33NA01V indicated suspect and was not available for
use. The station documented this condition in Condition Report CR-RBS-2012-07759.
On February 1, 2018, with the unit in Mode 1 at approximately 27 percent power, reactor
recirculation pump B unexpectedly tripped during an upshift in the speed of the pump. As a
result, the reactor was in a single loop configuration with the recirculation pump A running in
fast speed and the recirculation pump B not running. Operators entered abnormal operating
procedure AOP-0024, Thermal Hydraulic Instability Controls, Revision 30, as a result of the
unplanned entry into single loop operations. Step 5.8 of this procedure directed operators to
determine core flow and enter general operating procedure GOP-004, Single Loop
Operations. Step 5.8 also instructed operators to determine core flow using process
computer point B33NA01V (which can be observed in both ERIS and the plant process
computer) when in a configuration with one recirculation pump in fast speed and one
21
recirculation pump off. Control room operators observed the value of this data point as
13.9 million pounds mass per hour (Mlbm/hr) of flow through the reactor core. The operators
concluded that this value was not valid since the indicated flow was much lower than
expected with one recirculation pump running in fast speed. The operators then observed a
value of 27.3Mlbm/hr core flow using the ERIS data point for B33NA01V. This value
appeared to be a valid number based on the single loop operation power/flow map contained
in AOP-0024, Attachment 2. Normal data points on ERIS are displayed with a white text, but
control room operators observed the ERIS data point displayed in a magenta color.
Additionally, the word suspect appeared adjacent to the data point for core flow. Control
room operators contacted information technology personnel and attempted to understand the
magenta color and suspect information associated with the core flow data point.
Concurrently, operators attempted to validate core flow using alternate means but were
unsuccessful, as the alternate indications did not provide accurate core flow readings at low
reactor power when in a single loop configuration. After approximately one hour spent
seeking to understand the unfamiliar indication associated with B33NA01V, control room
operators conducted a brief and made the decision to shut down the unit due to the
uncertainties associated with the core flow data point. Following plant shutdown and
subsequent troubleshooting and investigation, licensee personnel concluded that the
magenta text and suspect note associated with ERIS B33NA01V was an expected system
response. Below approximately 40 percent core flow, the plant process computer shifts the
calculation method from the primary means of calculating core flow using the sum of jet pump
flows to an alternate process that uses core plate differential pressure. As a result of shifting
to the alternate calculation of core flow, data point ERIS B33NA01V was programmed to turn
magenta in color and display suspect to alert operators that the method of calculating core
flow had changed. After this information was disseminated to licensed operators, the
licensee implemented procedural changes to AOP-0024 that provided amplifying information
regarding B33NA01V validated core flow. Specifically, the licensee revised the procedure on
February 7, 2018, in order to provide clear guidance regarding expected system response of
the process computer data points during abnormal flow configurations.
The inspectors compared the actual plant response to the simulator response for the trip of a
recirculation pump while at low power. The actual conditions in the main control room during
the event on February 1, 2018, resulted in ERIS point B33NA01V indicating the correct flow
(27.3Mlbm/hr), but the data point turned magenta in color and displayed the warning label
suspect. This was later determined by information technology personnel to be the correct
response and data display, and was the result of the core flow calculation methodology
swapping from the primary method (jet pump flow) to the alternate method (core plate
differential pressure).
In the simulator, the inspectors determined that ERIS point B33NA01V provided erratic
indications of core flow following a simulated trip of the recirculation pump B from an initial
condition of approximately 25 percent. The indicated flow varied, and ultimately stabilized at
approximately 10Mlbm/hr, which is less than half of the expected indication. Additionally,
B33NA01V did not change to a magenta color, and it did not display the word suspect. The
inspectors determined that ERIS B33NA01V was programmed to calculate core flow using
the sum of jet pump flows at all power levels. As a result, the displayed value was inaccurate
below 40 percent core flow, and the data point was not programmed to turn magenta or
indicate suspect since no swap to a backup means of calculation below 40 percent core
flow was modelled.
22
The inspectors reviewed procedure EN-OP-117, Operations Assessments, Version 4,
Section 5.4, which states that transient snap-shot assessments are performed whenever a
plant transient occurs. A plant transient is defined in section 5.4[2] as including any turbine
generator power change in excess of 10 percent of rated power in less than one minute other
than a momentary spike due to a grid disturbance or a manually initiated runback. The
inspectors concluded that the recirculation pump A trip on December 19, 2012, met the
definition of a transient. EN-OP-117, Attachment 9.2, Transient Snap Shot Assessment
Documentation Form, Objective 7, discusses the training preparation aspect of the
assessment. Specifically, the transient snap-shot assessment is performed in order to
validate that the simulator accurately represented the plant characteristics of the transient.
The licensee provided a Post-Event Simulator Test report that was run on February 14, 2013.
The report concluded that the simulator response matched the parameters observed in the
plant. The inspectors determined that although the snap-shot assessment was performed,
station personnel did not validate that ERIS B33NA01V (validated core flow) provided
operators with the same indications seen by operators in the plant during a recirculation
pump trip.
The inspectors determined that no condition report or simulator deficiency report was
generated to document the discrepancy between the plant and the simulator for displaying
ERIS B33NA01V. The simulator ERIS B33NA01V core flow indication did not display the
correct value for core flow and also did not indicate suspect or turn magenta. The
inspectors reviewed training documentation to determine why this discrepancy was not
observed during continuing simulator training scenarios. The inspectors concluded that this
discrepancy was not documented because the station did not conduct training on abnormal
single loop operations during low power operations. The inspectors reviewed industry
standards and guidelines for simulator training and determined that the station is required to
periodically conduct training on abnormal events that occur during low power operations.
Corrective Actions: The station documented the core flow indication simulator deficiency in a
deficiency report and generated actions to incorporate the discrepancy into future licensed
operator training sessions.
Corrective Action Reference: CR-RBS-2018-03145
Performance Assessment:
Performance Deficiency: The licensees failure to validate core flow in the simulator during a
transient snap shot assessment following the trip of the reactor recirculation pump A on
December 19, 2012, was a performance deficiency.
Screening: The performance deficiency was more than minor, and therefore a finding,
because it was associated with the human performance attribute of the Initiating Events
Cornerstone and adversely affected the cornerstone objective to limit the likelihood of events
that upset plant stability and challenge critical safety functions during shutdown as well as
power operations. Specifically, the failure to validate simulator fidelity following a plant
transient prevented the licensee from identifying simulator model discrepancies when
determining core flow during low power, single loop operations.
23
Significance: The inspectors screened the finding in accordance with Inspection Manual
Chapter 0609, Appendix A, The Significance Determination Process for Findings At-Power.
The finding was determined to be of very low safety significance (Green) because the finding
did not contribute to both the likelihood of a reactor trip and the likelihood that mitigating
equipment would not be available.
Cross-cutting Aspect: No cross cutting aspect was assigned because the performance
deficiency is not indicative of current licensee performance.
Enforcement: Inspectors did not identify a violation of regulatory requirements associated
with this finding.
Failure to Submit a Licensee Event Report for a Manual Scram
Cornerstone
Significance
Cross-cutting
Aspect
Report
Section
None
SLIV
Closed
None
71153 -
Follow-up of
Events and
Notices of
Enforcement
Discretion
The inspectors identified a Severity Level IV non-cited violation of 10 CFR 50.73, Licensee
Event Report System, for the licensees failure to submit a required licensee event report
(LER). Specifically, on February 1, 2018, after an unexpected trip of the recirculation pump
B, the licensee initiated a manual scram of the reactor that was not part of a preplanned
sequence and failed to submit an LER within 60 days.
Description: At approximately 9:46 a.m. on February 1, 2018, with the unit operating at
approximately 27 percent power, the recirculation pump B unexpectedly tripped during an
attempted transfer from slow to fast speed. The licensee promptly entered AOP-0024,
Thermal Hydraulic Instability, and GOP-0004, Single Loop Operation. Note 5.8 of AOP-
0024 and Precaution 3.6 of GOP-0004 instruct the licensee to use process computer point
B33NA01V to determine core flow while in single loop operation. The plant process computer
(PPC) and emergency response information system (ERIS) readouts showed conflicting
indications for this computer point, with the PPC showing approximately 13,900 Mlbm/hr of
flow and ERIS showing approximately 26,000 Mlbm/hr of flow.
Step 5.1 of AOP-0024 instructs the licensee to determine where on the power-to-flow map the
plant is operating. If the plant is operating in the restricted region, the procedure states to exit
that region by lowering power or raising flow. If the plant is operating in the exclusion region,
the procedure states to verify that a scram has occurred. The indicated PPC value for core
flow put the plant in an unanalyzed region of the power-to-flow map, with less flow than the
minimum amount of flow that defines any region, including the exclusion region. The
indicated ERIS value put the plant in the restricted region, just above the boundary that
delineates the restricted region from the monitoring region.
The licensee initially believed the ERIS value to be the correct value; however, this value was
accompanied by a magenta suspect note on the ERIS screen, which caused the licensee to
question its validity. In an effort to determine the true value of core flow, the licensee
performed a manual calculation using other known inputs. The licensee performed this
calculation incorrectly and wrongly corroborated the PPC value as the correct value. Given
the inability to establish that the plant was operating in any allowed region of the power-to-
24
flow map, the licensee made the decision to manually actuate the reactor protection system
(RPS) by taking the reactor mode switch to shutdown.
During the investigation after the scram, the licensee determined that the ERIS value was, in
fact, a valid indication of core flow at the time of the event. Operators had not been
adequately trained on the meaning of the magenta suspect indication, and were therefore
unable to determine the implications of the indications on the validity of the data point.
Pursuant to the requirements of 10 CFR 50.72(b)(3)(iv), the licensee reported the scram
event to the NRC at 1:23 p.m. as an event that resulted in an actuation of the RPS. On
March 23, 2018, the licensee retracted the report on the grounds that the actuation was part
of a pre-planned sequence during testing or reactor operation. The inspectors concluded that
this retraction was inappropriate and that the event was reportable for the reasons provided
below.
The inspectors reviewed NUREG-1022, Event Report Guidelines 10 CFR 50.72 and 50.73,
revision 3, which provides the following guidance: 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). In the case of the February 1,
2018, River Bend scram event, the inspectors determined that the manual RPS actuation was
initiated in order to mitigate the consequences (i.e., uncertainty as to the condition of the plant
with respect to core flow and power-to-flow considerations) of an event (i.e., the unexpected
loss of a reactor recirculation pump).
NUREG-1022 also provides an example of a reportable manual scram that was event driven
and not part of a preplanned sequence during testing or reactor operation:
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.
As with the scram in the above example, the scram that occurred at River Bend Station was
not part of a preplanned sequence during testing or reactor operation, but was instead an
event driven response to a series of unplanned and unexpected adverse occurrences in the
plant. These occurrences included: a trip of the recirculation pump B, entry into an abnormal
operating procedure for thermal hydraulic instability, an inability to determine core flow and
location on the power-to-flow map in accordance with that procedure, a realization that the
PPC indication of core flow put the plant outside of any allowed operating region of the
power-to-flow map, an incorrect manual calculation that wrongly corroborated the accuracy of
the PPC indication, and the presence of a poorly understood suspect indication that
appeared to undermine the validity of the ERIS flow indication. These adverse occurrences
generated uncertainty as to the status of reactor safety. The subsequent decision to perform
25
a manual reactor scram was consistent with general instruction provided in EN-OP-115,
Conduct of Operations, which states: do not hesitate to reduce power or perform an
immediate reactor shutdown when reactor safety is uncertain. As with the scram in the
above example, the February 1, 2018, River Bend scram also involved entry into an off-
normal procedure due to an unexpected plant equipment malfunction that resulted in the
potential for the plant to be in an undesired condition with respect to power-to-flow
considerations.
The senior resident inspector was present in the control room during the events and was able
to confirm that the shutdown was event driven rather than preplanned. At 10:55 a.m., the
control room briefed that because PPC and ERIS showed conflicting indications of core flow
with ERIS indicating suspect, the mode switch was going to be placed in shutdown. At
10:57 a.m., roughly two minutes after the brief was completed, the reactor operator
scrammed the reactor, and the following station log entry was made: MCR [main control
room] announces placing plant in shut down due to inability to regulate recirculation flow. If
the reactor shutdown had been preplanned, it would not have proceeded at this accelerated
pace. Rather, the licensee would have worked through the relevant steps of the applicable
shutdown procedure, GOP-0004, Single Loop Operation, scramming the reactor only after
those steps had been completed and signed for. Upon review of the copy of GOP-0004 that
was in use by the operators on February 1, 2018, the inspectors noted that no steps of
Attachment 3, Shutdown from Single Loop Operation, were marked as completed, and the
attachment was not signed off as being initiated or completed. The deviation from normal
practice was appropriate because the scram was not being initiated as part of a preplanned
sequence. It was instead being initiated in response to the unanticipated emergence of a
safety concern.
Corrective Actions: The licensee documented the violation in the corrective action program
and generated corrective actions to review reportability requirements.
Corrective Action Reference(s): CR-RBS-2018-03953
Performance Assessment:
Performance Deficiency: The failure to submit a required licensee event report was a
performance deficiency.
Screening: The performance deficiency was evaluated in accordance with the reactor
oversight process and was determined to be minor because it could not be reasonably
viewed as a precursor to a significant event, would not have the potential to lead to a more
significant safety concern, does not relate to a performance indicator that would have caused
the performance indicator to exceed a threshold, and did not adversely affect a cornerstone
objective. The performance deficiency was evaluated in accordance with the traditional
enforcement process because it impacted the ability of the NRC to perform its regulatory
oversight function.
Significance: Using example 6.9.d.9 from the NRC Enforcement Policy, the violation was
determined to be a Severity Level IV violation.
Cross-cutting Aspect: Because the violation was dispositioned using the traditional
enforcement process, no cross-cutting aspect was assigned.
26
Enforcement:
Violation: 10 CFR 50.73(a)(1) requires, in part, that the licensee shall submit a Licensee
Event Report (LER) for any event of the type described in this paragraph within 60 days after
the discovery of the event. 10 CFR 50.73(a)(2)(iv)(A) requires, in part, that the licensee shall
report any event or condition that resulted in manual actuation of the reactor protection
system (RPS) except when the actuation resulted from and was part of a pre-planned
sequence during testing or reactor operation. Contrary to the above, on April 2, 2018, the
licensee failed to submit an LER within 60 days after the discovery of an event or condition
that resulted in manual actuation of the RPS that did not result from and that was not a part of
a pre-planned sequence during testing or reactor operation. Specifically, the licensee failed
to submit an LER within 60 days of a manual reactor scram that occurred on February 1,
2018.
Disposition: Because this SLIV violation was neither repetitive nor willful, and because it was
entered into the licensees corrective action program as Condition Report
CR-RBS-2018-03953, it is being treated as a non-cited violation consistent with
Section 2.3.2.a of the NRC Enforcement Policy.
EXIT MEETINGS AND DEBRIEFS
The inspectors verified no proprietary information was retained or documented in this report.
On May 31, 2018, and on July 16, 2018, the inspectors presented the inspection results to
Mr. W. Maguire, Site Vice President, and other members of the licensee staff.
Attachment
DOCUMENTS REVIEWED
71111.15Operability Determinations and Functionality Assessments
Procedures
Number
Title
Revision
Operating Experience Program
12 & 13
STP-051-4206
(RPS Bypassed) RPS/RHR Reactor Vessel Level-Low,
Level 3, High, Level 8, Channel Calibration and Logic
System Functional Test (B21-N680B, B21-N683B, B21-
N080B)
305
STP-051-4227
ECCS/RCIC Actuation Ads Trip System B Reactor
Vessel Water Level Low, Level 3/High, Level 8 Channel
Calibration, and Logic System Functional Test (B21-
N095B, B21-N695B, B21-N693B)
20
STP-501-4202
FWS/MAIN Turbine Trip System - Reactor Vessel Water
Level - High Level 8, Channel Calibration and LSFT
(C33-N004B, C33-K624B, C33-R606B, C33-K650-3)
15
G13.18.6.1.B21
Reactor Vessel Water Level - Low, Level 3 Trip Function
3
G13.18.6.1.B21*003 Reactor Vessel Water Level - Low, Level 3 Trip Function
3
G13.18.6.1.B21*010 Reactor Vessel Water Level - Low, Level 8 Narrow
Range
0, 1, 2, & 3
MCP-IC-501-4202
FWS/FEED Pump Trip System (MSO) - Reactor Vessel
Water Level - High Level 8, Loop Calibration (C33-
LTN006B, C33-ESN606B)
0
71111.18Plant Modifications
Condition Reports (CR-RBS-)
OE-NOE-2004-00008
OE-NOE-2004-00084
Engineering Changes
Number
Title
Revision
Accept As-Is Evaluation for Remainder of Cycle 20: Sparger
N4C Nozzles 7 and 8 Damaged
0 & 1
A-2
Procedures
Number
Title
Revision
Emergency and Transient Response Support Procedure
20-25
STP-000-0001
Daily Operating Logs
082
DBR-0035279
GEH Comment Resolution Form
0
4221.110-000-
043
Operability Assessment of the River Bend Station
Feedwater Sparger Assembly in the January 2018 As-
Found Condition
0
71152 - Problem Identification and Resolution
Condition Reports (CR-RBS-)
OE-NOE-2004-00008
OE-NOE-2004-00084
Engineering Changes
Number
Title
Revision
Loose Parts Evaluation for Material Lost From
Feedwater Spargers Identified During PO-18-01
Foreign Material FME LPA-000
0
Miscellaneous Documents
Number
Title
Revision/Date
OSRC Meeting 2018-0001 Minutes
OSRC Meeting 2018-0002 Minutes
Action Item OE33308-20110507-A2-RBS-001
CNR RBS PO-18-01-01 Foreign Material Customer Notification Report
0
ECH-NE-17-00039
River Bend MOC-20a Fuel Inspection Plan
0
General Electric Instrument Setpoint
Methodology
0
Boiling Water Reactor Feedwater
Nozzle/Sparger Final Report
0
Guidelines for 10 CFR 50.59 Implementation
1
OE33308-20110507
Sampling Probe Found in Feedwater Sparger
August 17, 2011
A-3
Miscellaneous Documents
Number
Title
Revision/Date
PO 18-01
BOP Foreign Material Inspection Report
RBS-ER-99-0539
Engineering Response Associated with Loose
Part in the Feedwater System
0
Procedures
Number
Title
Revision
Reactor Scram
37
Thermal Hydraulic Stability Controls
30, 31, & 32
Corporate Fuel Reliability
6
Operability Determination Process
14
Operational Decision Making Issue Process
15
Operations Assessments
4
Emergency Operating Procedure - RPV Control
28
GOP-0001
Plant Startup
99
GOP-0002
Power Decrease/Plant Shutdown
78
GOP-0003
Scram Recovery
31
GOP-0004
Single Loop Operation
25
OE-100
Operating Experience Program
1
R-PL-012
Corrective Action Program
1
STP-000-0001
Daily Operating Logs
082
71153Follow-up of Events and Notices of Enforcement Discretion
Procedures
Number
Title
Revision
Conduct of Operations
23
GOP-0004
Single Loop Operation
23
Condition Reports (CR-RBS-)
2018-03149
2018-03953
SUNSI Review:
ADAMS:
Non-Publicly Available
Non-Sensitive
Keyword:
By: CHY/RDR
Yes No
Publicly Available
Sensitive
OFFICE
SRI:DRP/C
RI:DRP/C
SPE:DRP/C
ARI:DRP/C
C:DRS/EB2
D:DRP
NAME
JSowa
BParks
CYoung
MOBanion
JDrake
AVegel
SIGNATURE
/RA/
/RA/
/RA/
/RA/
/RA/
/RA/
DATE
6/22/2018
6/21/2018
6/21/2018
6/25/2018
7/10/2018
7/18/18
OFFICE
BC:DRP/C
NAME
JKozal
SIGNATURE
/RA/
DATE
7/18/18