05000247/LER-2007-002

From kanterella
Revision as of 11:12, 27 November 2017 by StriderTol (talk | contribs) (Created page by program invented by StriderTol)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
LER-2007-002, Technical Specification Prohibited Condition Due to Exceeding Containment Air Temperature Limit Allowed Outage Time as a Result of Changes in Instrument Uncertainty
Docket Number
Event date: 1-3-2007
Report date: 2-8-2007
Reporting criterion: 10 CFR 50.73(a)(2)(i)(B), Prohibited by Technical Specifications

10 CFR 50.73(a)(2)(v), Loss of Safety Function
2472007002R00 - NRC Website

Note: The Energy Industry Identification System Codes are identified within brackets }

DESCRIPTION OF EVENT

On August 29, 2006, during a review of operator daily surveillance rounds (DSR) by a Nuclear Analysis Engineer, it was noted that the DSR for containment {NH) temperature had a temperature limit of 125 degrees F and referenced Technical Specification (TS) 3.6.5 for actions when the temperature is found to exceed the limit. The TS 3.6.5, "Containment Air Temperature," Limiting Condition of Operation (LCO) requires for Modes 1-4, that the containment average air temperature be between 50 degrees F and less than or equal to 130 degrees F.

The Bases for TS 3.6.5 states the LCO limits for containment temperature are analytical limits therefore, an appropriate allowance for instrument uncertainty must be applied to ensure the limits are met. Review of the calculation (FIX-00117-00), "Containment Temperature Indication Instrument Loop Uncertainty," showed that FIX-00117-00 calculates the loop uncertainty for containment temperature indication using instrument TI-1203 (TI} with an uncertainty of +/-8.4 degrees F, and the plant computer (PICS) (ID} using an uncertainty of +/-7.9 degrees F. Engineering concluded that the calculated instrument uncertainty would result in containment temperature potentially exceeding the TS limit at approximately 122 degrees F and not at the 125 degrees F limit referenced in the DSR. Additional review also discovered that the service water (SW) system {BI} operating procedure (SOP-24.1) for hot weather operations states, "If the containment temperature exceeds 130 degrees F, then containment cooling equipment will be beyond the design basis.

Engineering concluded that instrument uncertainty had also not been accounted for in this SOP statement. The condition was recorded on August 29, 2006, in the IPEC corrective action program (CAP) as condition report CR-IP2-2006- 005177. At the time the condition was identified, the plant was at 100% steady state reactor power with containment air temperature below 120 degrees F.

During the review, the Nuclear Analysis Engineer noted that containment temperature was now recorded in surveillance procedure 2-PT-D001, not DSR-08 and prior to conversion from the custom TS to the Improved TS (ITS), containment temperature was recorded on Operator Log 2-DSR-1. The instrument loop uncertainty calculation for containment temperature (FIX-00117-00) Revision 0, was approved on July 10, 2002, and was performed in response to a condition recorded on December 2, 2000, in CR-IP2-2000-09735. The purpose of the calculation (FIX-00117-00) was to ensure instrument inaccuracy was accounted for in the procedural acceptance criteria for the containment temperature operator log. This action was the result of an extent of condition review for a condition recorded on May 4, 2000, in condition report CR-IP2- 2000-03224 for a safety evaluation deficiency regarding minimum containment temperature.

In 2000, during the condition report (CR) review, corrective actions (CA) were assigned to the Operations Procedure Group for revision of the Control Room Log for containment temperature (CR-IP2-2000-09735 CA-6) and to Design Engineering to perform the analysis necessary to determine suitable criteria for containment temperature (CR-IP2-2000-09735 CA-7). CR-IP2-2000-09735 was assigned to the Setpoint Group, which used the CA system to assign implementation and update actions as part of the setpoint process. The impact calculation review process per procedure ENN-DC-126 did not exist at that time.

The corrective action (CA-6) for revising the operator log (2-DSR-1) was closed six months prior to its due date of December 31, 2000, citing lack of information from Design Engineering. CA-6 requested reassignment of the CA when the input information became available.

The CA for performing an analysis (CA-7) was closed on August 27, 2002, after the calculation (FIX-00117-00) had been issued. A closure review was performed on September 23, 2002, but did not identify that the update to the containment temperature log procedure had not been completed. Calculation FIX-00117-00 Revision 0 did not identify any affected documents, although the need to update the operator log was identified previously in CA-6. During this time period (2002), the calculation impact review process had been implemented per procedure ENN-DC-126, but the operator surveillance requirement error was not identified.

In 2003, the ITS conversion created a daily surveillance requirement for logging containment temperature and the requirement at that time became part of procedure 2-PT-D001. The containment temperature criterion of 125 degrees F contained in procedure 2-PT-D001 was carried over from the operator log procedure 2-DSR-1. At the time CR-IP2-2000-09735 was initiated, the 125 degree F containment temperature criterion established a supplemental log only and the action point to begin shutting down the reactor at 130 degrees F. At a time between the initiation of CR-IP2-2000-09735 in 2000, and the ITS implementation in 2003, the 125 degree F containment temperature criterion became an action point at which operators had to consider shutting down the reactor.

A review of past containment air temperatures for the summers of 2004, 2005, and 2006, based on the plant computer (PICS/PI) data, indicated that the TS limit of 130 degrees was exceeded in 2005 and 2006 considering the revised monitoring uncertainties. At some point each day from July 25 through August 26, 2005, and August 2 through August 19, 2006, the indicated temperature exceeded 122.1 degrees F. The limiting value initially used was 122.1 degrees F (TS limit of 130 degrees F minus 7.9 degrees F for calculated uncertainty). The calculation of uncertainty was reviewed to determine if conservatisms were considered.

Engineering determined that the uncertainty for the five temperature elements was included as if it were one module when these elements are input to an averaging device. ISA Standard 67.04-2000, provides a methodology for propagating uncertainty through a summing device which entails combining the uncertainties for each temperature element using the square root of the sum of the squares (SRSS) and dividing by five (circuit with 5 inputs). After re- evaluating the temperatures using the alternate method, the loop uncertainties were determined to be +/-6.1 degrees F for 2-PT-D001, and +/-5.4 degrees F for the PICS computer. These results would revise the acceptance limits to 123.9 degrees F and 124.6 degrees F. When the remaining past temperatures that exceeded the limit considered the TS Allowed Outage Time (AOT) of 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />, the only period remaining that exceeded 124.6 degrees F for 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> was on August 16-17, 2005. Engineering determined the temperature exceeded 124.6 degrees F at 6:59 AM on August 16 (peak of 125.85 degrees F) and did not return to within limits until 5:46 AM on August 17, 2005, a period of approximately 22 hours2.546296e-4 days <br />0.00611 hours <br />3.637566e-5 weeks <br />8.371e-6 months <br />, 47 minutes. The peak temperature difference during this time was 1.25 degrees F.

A completion of review of past containment temperature documentation on January 3, 2007, confirmed that the TS limit was exceeded on August 16-17, 2005.

CAUSE OF EVENT

The direct cause of the condition was a failure to update surveillance procedure 2-PT-D001 (latest surveillance requirements) to reflect revised criteria from calculation FIX-00117-00 Revision 0, at the time the calculation was created (approved July 10, 2002). The apparent cause was inappropriate closure of a CA.

The initial CA was closed without performing the task and no tracking activity was issued to ensure the document was updated. Contributing causes (CC) included CC1: CR closure review was not thorough enough to identify that the required update of procedure 2-PT-D001 was not implemented, CC2: The ENN-DC-126 impact review process did not identify affected procedures when preparing calculation FIX-00117-00 under CA-7 of CR-IP2-2000-09735.

CORRECTIVE ACTIONS

The following corrective actions have been performed under the Corrective Action Program (CAP) to address the causes of this event.

  • Surveillance procedure 2-PT-D001,"Control Room Operations Surveillance Requirements," was changed to a new containment temperature criteria of 121 degrees F by revision 14 and the revised surveillance distributed. Action completed on November 2, 2006.
  • The apparent and contributing causes associated with CR-IP2-2006-05177 are considered to be historical condition report quality issues. These issues are considered historical because the conditions described occurred prior to conditions recorded in CR-IP2-2003-05886 and CR-IP2-2003-01185. CR-IP2-2003- 05886 was initiated to address the lack of rigor, thoroughness, and standalone quality of CR evaluations. CR-IP2-2003-01185 was initiated to address CR closeout issues. The containment temperature surveillance issues identified by the condition recorded in CR-1P2-2006-05177 are enveloped by the evaluations and corrective actions implemented under CR-IP2-2003-05886 and CR- IP2-2003-01185 for condition report quality issues.
  • An extent of condition review was performed which concluded that the apparent and contributing cause of inadequate CR closure review are CR quality issues that have the potential to affect any plant department and any CR. The issue with CR quality has been addressed previously. The contributing cause for failure to identify impacted documents under the calculation review process is also considered historical as the impact review process was strengthened by its inclusion in the ER response and closeout process under previous CRs. The reason surveillance procedure 2-PT-D001 was not identified during impact review could not be ascertained, but engineering had identified that the impact review process per ENN-DC-126 was weak. Consequently, changes per EN- DC-126 Revision 6, require the use of the EN-DC-115 ER Response process when preparing a calculation and identifying affected documents. The revision also requires use of the EN-DC-118 closeout process to ensure that all required plant documents are updated.

EVENT ANALYSIS

The event is reportable under 10CFR50.73(a)(2)(i)(B). The licensee shall report any operation or condition which was prohibited by the plant TS. This event meets the reporting criteria because the containment temperature exceeded an instrument value of 124.6 degrees F at 6:59 AM on August 16 (124.74 degrees F) and did not return to within limits until 5:46 AM on August 17, 2005 (124.58 degrees F), a period of approximately 22 hours2.546296e-4 days <br />0.00611 hours <br />3.637566e-5 weeks <br />8.371e-6 months <br />, 47 minutes. This error resulted in the monitored containment air temperature potentially exceeding the TS Limiting Condition of Operation (LCO) upper limit of 130 degrees after considering instrument uncertainty. The time in which the condition existed exceeded the 8-hour AOT for TS 3.6.5 and the required actions were not performed.

If the DSR had contained the correct value as recorded by the calculation, operators would have been alerted to the condition and could have taken appropriate steps. The date of the event for reportability is January 3, 2007, because the evaluation of past temperature conditions was not finalized until that date. The date of discovery for an actual occurrence was not known when the condition was recorded in CR-IP2-2006-05177. There was no safety system that could not have performed its safety function as a result of the containment temperature exceeding the TS limit. Therefore, there was no safety system functional failure reportable under 10 CFR 50.73(a)(2)(v).

PAST SIMILAR EVENTS

A review of the past two years of Licensee Event Reports (LERs) for events that involved instrument uncertainty errors that resulted in exceeding TS allowed completion times did not identify any LERs.

SAFETY SIGNIFICANCE

This event had no effect on the health and safety of the public.

There were no actual safety consequences for the event because there were no accidents or transients. The TS required number of containment fan cooler units (FCUs) fBK} were operable and could have provided the required cooling to maintain containment temperature below the TS limit. The 24 FCU was removed from service August 16, 2005, at approximately 5:30 AM for a PM on its supply breaker.

The FCU was returned to service on August 17, 2005, at approximately 5:30 AM.

The remaining four FCUs were available for cooling. In addition, during the TS prohibited condition, the temperature of the river water used for FCU cooling water was well below the design maximum of 95 degrees F, therefore there was margin for cooling. If the containment temperature surveillance procedure had contained the correct value as recorded by the calculation, operators would have been alerted to the condition and could have taken appropriate steps to maintain the proper temperature.

There were no significant potential safety consequences of this event under reasonable and credible alternative conditions. The containment average air temperature limit of 130 degrees F is an initial condition used in the Design Basis Analysis (DBA). The temperature limit is also used to establish the containment environmental qualification operating envelope for both containment pressure and temperature. The temperature limit ensures that operation is maintained within the assumptions used in the DBA analysis for containment. The limiting DBAs relative to containment are the Loss of Coolant Accident (LOCA) and Main Steam Line Break (MSLB). The containment air temperatures which were determined to exceed the TS limits were small (1.25 degrees F) and within the safety margin of the accident analysis evaluation and therefore would not have a significant effect on safety. The containment temperature exceeded the instrument limit of 124.6 degrees F at 6:59 AM on August 16 (maximum of 125.85 degrees F), a difference of 1.25 degrees F, and returned to within limits at 5:46 AM on August 17, 2005 (124.58 degrees F). The 124.6 degrees F instrument limit ensures the actual temperature will not exceed the design limit of 130 degrees F.

FSAR Section 14.3.5 identifies the calculated LOCA peak pressure as 45.71 psig, and the peak LOCA temperature as 266.81 degrees F, assuming an initial containment temperature of 130 degrees F. The LOCA containment response bounds the MSLB. TS Bases 3.6.6 lists the design pressure as 47 psig and the design temperature as 271 degrees F. The pressure/temperature margin envelopes the small exceedance on initial containment temperature assumed in the DBA analysis.