ML17312B553

From kanterella
Revision as of 07:48, 29 October 2019 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 97-002-00:on 970528,SR for Core Protection Was Not Performed Due to Inadequate Procedures.Revised Procedures
ML17312B553
Person / Time
Site: Palo Verde Arizona Public Service icon.png
Issue date: 07/07/1997
From: Marks D
ARIZONA PUBLIC SERVICE CO. (FORMERLY ARIZONA NUCLEAR
To:
Shared Package
ML17312B552 List:
References
LER-97-002-02, LER-97-2-2, NUDOCS 9707150361
Download: ML17312B553 (8)


Text

LICENSEE EVENT REPORT (LER)

DOCKET NUMBER (2) PAGE (3)

ACILITYNAME (1)

Palo Verde Unit 1 050005'2 81oF04 TLE (4)

Surveillance Re uirement for Core Protection Calculators not Performed due to Inade uate Proced ures EVENT DATE 6 LER NUMBER 6 REPORT DATE OTHER FACIUTIES INVOLVED 6 MONTH SEQUENTIAL REVISCN FACILITY NAMES NUMSERS 46 NUMBER NUMBER 0 5 0 0 0 0 5 2 8 9797 0 0 2 0 0 0 7 0.7 9 7 REPORT IS SUBMITTEDPURSUANT TO THE REQUIREMENTS OF 10 CFR C (Chactt one or mora oI the following) (11) 05000 MODE (9) 20.402(b) 20.405(c) 50.73(a)(2)(iv) 73.71(b) 3 20.405(a)(t)Oi SL38(c)(1) 5073(a)(2)(v) 73,71(c)

LEVEL(tO) 20.405(a)(1)(ii) QL38(c)(2) 50.73(a)(2)(vir) OTHER (Spacity in Abstract P P P 20.405(a)(1) xiii) SL73(a)(2)(i) 50.73(a)(2)(vis)(A) bebw and in Text, NRC Form 20.405(a)(1)(iv) 5073(a)(2)rs) 50.73(a)(2)(vs)(B) 20.405(a)(t)(V) 50.73(a)(2)(iii) 5073(a)(2)(x)

UCENSEE CONTACT FOR THIS LER (1 2)

HONE NUMBER EA CODE Daniel G. Marks, Section Leader, Nuclear Regulatory Affairs 6 0 2 3 9 3 - 6 4 9 2 COMPLETE ONE UNE FOR EACH COMPONENT FAILURE DESCRIBED IN THIS REPORT (I 3)

CAUSE SYSTEM COMPONENT MANUFAC. REPORTABLE P"';:"; 'I'v'Iji,"~~~vg'AUSE SYSTEM COMPONENT MANUFAC REPORTABLE TURER TURER TO NPRDS SUPPLEMENTAL REPOR'T EXPECTED (14) EXPECTED MONTH DAY YEAR SUBMISSON YES 0I yas. complete EXPECTED SUBMISSON DATE) DATE (I 5)

TRACT (Limitto 1400 spaces, Le., approximately fdtaen single space aWwritten lines) (16)

On June 11 at approximately 1500 MST, Palo Verde Unit 1 was in Mode 1 (POWER OPERATION) operating at approximately 100 percent: power when APS personnel identified that a Technical Specification (TS) Surveillance Requirement (SR) for Core Protection Calculators (CPC) (TS SR 4.3.1.5) was not performed during the unit restart on May 28, 1997. The TS violation was identified during a Nuclear Assurance Audit of Unit Operations, Technical Specificat:ions, and License Conditions. A backend review of the SRs indicated that the CPCs were OPERATIONAL prior to and immediately following the event.

A preliminary evaluation has determined that the apparent cause of the missed surveillance test was attributed to inadequate procedures. As correct:ive action, procedures have been revised to properly reflect the TS SR. No previous similar events have been reported pursuant: to 10CFR50.73 in the last three years.

't)707150361 970707 PDR ADOCK 05000528 S PDR

P j

LICENSEE EVENT REPORT (LER) TEXT CONTINUATION ACLBYNAME DOCKET NUMBER LER NUMBER PAGE YEAR REWSO NUMBER NUMBER Palo Verde Unit 1 <,'.N.

0 5 0 0 0 5 2 8 9 7 0 0 2 0 0 0 2 of04

1. REPORTING REQUIREMENT:

This LER 528/97-002-00 is being written to report an event that resulted in the plant being operated in a condition prohibited by the Technical Specifications as specified by, 10CFR50.73.(a)(2)(i)(B).

Specifically, on June 11, 1997 at appzoximately 1500 MST, Palo Verde Unit 1 was in Mode 1 (POWER OPERATION) operating at approximately 100 percent power when APS personnel (other utility personnel) identified that a Technical Specification (TS) Surveillance Requirement (SR) for Core Protection Calculators (CPC) (JC) (TS SR 4.3.1.5) was not performed during the unit restart on May 28, 1997. On May 28, 1997, Palo Verde Unit 1 was in Mode 3 (HOT STANDBY). The TS violation was identified during a Nuclear Assurance, Audit of Unit Operations, TS, and License Conditions.

2. EVENT DESCRIPTION:

On May 28, 1997, Control Room personnel (utility-licensed operator) were preparing to perform a reactor (AC) startup following a reactor trip event which occurred on May 27, 1997 (LER 528/97-001-00). At 'approximately 1347 MST on May 28, 1997, a Mode change procedure was being impl'emented to ensure all applicable TS and administrative requirements were met prior to closing the reactor trip breakers (AA) in Mode 3. However, the procedure did not identify the performance of TS SR for checking CPC auto restarts as being required prior to closing the reactor trip breakers. The reactor trip breakers were closed at approximately 1351 on May 28, 1997.

TS Limiting Condition for Operation (LCO) 3.3.1, Reactor Protection Instrumentation, identifies the CPC APPLICABLE MODE in Table 3.3-1 as 1, 2 (STARTUP), 3*, 4* (HOT SHUTDOWN), 5* (COLD SHUTDOWN) with a note that indicates that the "*" denotes with the "protective system trip breakers in the, closed position, the CEA [control element assembly] [AA] drive system capable of CEA withdrawal, and fuel in the reactor vessel." TS SR 4.3.1'.5 states that the CPCs shall be determined OPERABLE at 1'east once per 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> by verifying that less than three auto restarts have occurred on each calculator during the past 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />.

At approximately 2230 MST on May 28, 1997, Control Room personnel completed shiftly surveillance procedures for Mode 3 which also did not include the CPC auto restart check following closure of the reactor trip breakers. On May 29, 1997 at approximately 0856 MST, Control Room personnel completed shiftly surveillance procedures in preparation for entering Mode 2. The Mode 2 surveillance log procedure did include the TS SR to check the CPC auto restart indication.

/

LICENSEE EVENT REPORT (LER) TEXT CONTINUATION ACQIVNAME DOCKET NUMBER LER NUMBER PAGE YEAR SEQUENIIAI. REVISIO NUMBER NUMBER Palo Verde Unit 1 0'5 0 0 0 5 2 8 9 7 0 0 2 0 0 0 3 of 0 4 At approximately 1500 MST on June 11, 1997, during an Operations and TS audit, Nuclear Assurance personnel identified that for a nineteen (approximate) hour period, the performance of TS SR 4.3.1.5 had not been performed during the unit restart, prior to and following the closure of the reactor trip breakers. This event resulted in a TS violation. There were no safety system actuations and none were required.

3. ASSESSMENT'F THE SAFETY CONSEQUENCES AND IMPLICATIONS OF THZS'VENT:

The function of the CPCs in Mode 3 with the reactor trip breakers closed is to generate a trip s'ignal in the event of a CEA withdrawal transient if less than four reactor coolant pumps (RCP), (AB) are operating and the Logarithmic Power High trip setpoint is greater than 10E-4 percent power.

TS allows the CPCs to be inoperable in this specified condition if the Logarithmic Power Level High Trip is OPERABLE with the trip setpoint lowered to less than, or equal to 10E-4 percent power. The safety analysis for a CEA withdrawal event with four RCPs operating assumes a .Logarithmic Power High trip setpoint of 10E-2 percent power. For the time period the reactor trip breakers were closed, all four RCPs remained in operation and the Logarithmic Power High trip setpoint was at approximately 10E-3 percent power.

A backend review of the SRs to check for CPC'uto restarts that were completed prior to the reactor trip on May 27, 1997 and prior to Mode 2 entry on May 29, 1997, indicated that there were no CPC auto restarts and that the CPCs were OPERATIONAL.

The event,did not result in any challenges to the fission product barriers or result in any release of radioactive materials. Therefore, there were no adverse safety consequences or implications as a result of this event.

This event did not adversely affect the safe'operation of the plant or health and safety of the public.

CAUSE OF THE EVENT:

An independent investigation of this event is being conducted, in accordance with the APS Corrective Action Program. As part of the investigation,, a determination of the cause of the event will be performed. A preliminary evaluation has determined that the apparent root cause is attributed to inadequate procedures (SALP Cause: Code D: Defective Procedures). The requirement to have CPCs OPERABLE in Mode 3*, 4+,, 5* was implemented as a result of a TS amendment, (numbered 98, 86, and 69 respectively for Units 1, 2, and 3) issued on September 1, 1995 and effective:on December 14, 1995. This change was in response to a concern

41 LICENSEE EVENT REPORT,(LER) TEXT CONTINUATION AGILITYNAME DOCKET NUMBER LER NUMBER PAGE YEAR SEQUENTIAL ~, REIASIO NUMBER ca~ NUMBER Palo Verde Unit 1 0 5 0 0 0 5 2 8 9 7 0 0 2 0 0 04of04 related to a CEA withdrawal event from subcritical conditions with less than four RCPs operating and the Logarithmic Power High trip setpoint greater than 10E-4 percent power. In this scenario the CPCs are required to protect the core by automatically generating a reactor trip at 10E-4 percent power. For conditions with four RCPs in operation the Logarithmic Power High trip setpoint of 10E-2 percent power is adequate to protect the core. The investigation will evaluate the apparent procedural deficiencies in properly implementing the TS amendment as well as the transportability issues related to Units 2 and 3. If the evaluation results differ from this determination or the results would significantly alter the readers'nderstanding of the significance of the event, a supplement will be submitted.

No unusual characteristics of .the work location (e.g., noise, heat, poor lighting) directly contributed to this event. Personnel error did not contribute to this event.

5. STRUCTURES'YSTEMS I OR COMPONENTS INFORMATION There are no indications that any structures, systems, or components weze inoperable at the start of the event which contributed to this event.

No component or system failures were involved. No failures of components with multiple functions were involved. No failures that rendered a train of a safety system inoperable were involved.

6. CORRECTIVE ACTIONS TO PREVENT RECURRENCE:

An independent investigation of this event is being conducted in accordance with the APS Corrective Action Program. Actions to prevent recurrence aze being developed based upon the results of the investigation and will be tracked under the APS Corrective Action Tracking System.

Immediate corrective action was taken to revise the Mode change and the surveillance test procedures to require a check of the CPC auto restart indication when in Modes 3, 4, or 5 with reactor trip breakers closed and Logarithmic Power High trip setpoint greater than 10E-4 percent power.

7. PREVIOUS SIMILAR EVENTS:

Although previous events have been reported pursuant to 10CFR50.73 in the past three years for missing TS surveillance requirements, the causes discussed in the previous events have not been similar to this event.

Therefore, the corrective actions of the previous events would not have prevented this event.

41