05000482/LER-2010-008, Regarding Personnel Error Results in Missing High Security Key

Regarding Personnel Error Results in Missing High Security Key

ML102590360
Person / Time
Site:	Wolf Creek
Issue date:	09/09/2010
From:	Matthew Sunseri Wolf Creek
To:	Document Control Desk, Office of Nuclear Reactor Regulation
References
WM 10-0025 LER 10-008-00
Download: ML102590360 (4)

LER-2010-008, Regarding Personnel Error Results in Missing High Security Key

Event date:
Report date:
Reporting criterion:	10 CFR 50.73(a)(2)(i) 10 CFR 50.73(a)(2)(vii), Common Cause Inoperability 10 CFR 50.73(a)(2)(ii)(A), Seriously Degraded 10 CFR 50.73(a)(2)(viii)(A) 10 CFR 50.73(a)(2)(ii)(B), Unanalyzed Condition 10 CFR 50.73(a)(2)(viii)(B) 10 CFR 50.73(a)(2)(iii) 10 CFR 50.73(a)(2)(ix)(A) 10 CFR 50.73(a)(2)(iv)(A), System Actuation 10 CFR 50.73(a)(2)(x) 10 CFR 50.73(a)(2)(v)(A), Loss of Safety Function - Shutdown the Reactor 10 CFR 50.73(a)(2)(v)(B), Loss of Safety Function - Remove Residual Heat 10 CFR 50.73(a)(2)(i)(A), Completion of TS Shutdown 10 CFR 50.73(a)(2)(v), Loss of Safety Function 10 CFR 50.73(a)(2)(i)(B), Prohibited by Technical Specifications
4822010008R00 - NRC Website

text

W0LF CREEK

'NUCLEAR OPERATING CORPORATION Matthew W. Sunseri President and Chief Executive Officer September 9, 2010 WM 10-0025 U. S. Nuclear Regulatory Commission ATTN: Document Control Desk Washington, DC 20555

Subject:

Docket No. 50-482: Licensee Event Report 2010-008-00, "Personnel Error Results in Missing High Security Key" Gentlemen:

The enclosed Licensee Event Report (LER) is being submitted pursuant to 10 CFR 73.71 regarding a high security key being misplaced at Wolf Creek Generating Station.

Commitments made by Wolf Creek Nuclear Operating Corporation in the enclosed LER are identified in the Attachment to this letter.

If you have any questions concerning this matter, please contact me at (620) 364-4008, or Mr.

Richard D. Flannigan at (620) 364-4117.

Sincerely, Matthew W. Sunseri MWS/rlt Attachment - List of Regulatory Commitments Enclosure

- Licensee Event Report 2010-008-00 cc:

E. E. Collins (NRC), w/a, w/e R. P. Correia (NRC), w/a, w/e G. B. Miller (NRC), w/a, w/e B. K. Singal (NRC), w/a, w/e Senior Resident Inspector (NRC), w/a, w/e 3

P.O. Box 411 / Burlington, KS 66839 / Phone: (620) 364-8831 An Equal Opportunity Employer M/F/HC/VET r4L

Attachment to WM 10-0025 Page 1 of 1 LIST OF REGULATORY COMMITMENTS The following table identifies those actions committed to by Wolf Creek Nuclear Operating Corporation (WCNOC) in this document. Any other statements in this submittal are provided for information purposes and are not considered to be regulatory commitments.

Please direct questions regarding these commitments to Mr. Richard Flannigan at (620) 364-4117.

REGULATORY COMMITMENT DUE DATE/EVENT A robust device/method will be used to attach the high December 23, 2010 security key to the lanyard of the operations personnel.

NRC FORM 366 U.S. NUCLEAR REGULATORY APPROVED BY OMB: NO. 3150-0104

'EXPIRES: 08/31/2010

, the NRC may not conduct or sponsor, and a person is not required to respond to, the P. as r

zworc ia f

rr nri iirarl niimh ar nf information collection.

I. FACILITY NAME

2. DOCKET NUMBER

13. PAGE WOLF CREEK GENERATING STATION 05000 482 1 OF 2

4. TITLE Personnel Error Results in Missinq Hicih Security Key

5. EVENT DATE

6. LER NUMBER

7. REPORT DATE

8. OTHER FACILITIES INVOLVED MONTH DAY YEAR YEAR SEQUENTIAL REV MONTH DAY YEAR FACILYNAME DOCKET NUMBER NUMBER NO. 1 05000 FACILITY NAME DOCKET NUMBER 07 12 2010 2010

- 008 -

00 09 09 2010 05000

9. OPERATING MODE

11. THIS REPORT IS SUBMITTED PURSUANT TO THE REQUIREMENTS OF 10 CFR§: (Check all that apply)

El 20.2201(b)

El 20.2203(a)(3)(i)

El 50.73(a)(2)(i)(C).

El 50.73(a)(2)(vii)

Mode 1 [E

20.2201(d)

El 20.2203(a)(3)(ii)

El 50.73(a)(2)(ii)(A)

[3 50.73(a)(2)(viii)(A)

El 20.2203(a)(1)

El 20.2203(a)(4)

El 50.73(a)(2)(ii)(B)

El 50.73(a)(2)(viii)(B)

El 20.2203(a)(2)(i)

[I 50.36(c)(1)(i)(A)

El 50.73(a)(2)(iii)

[I 50.73(a)(2)(ix)(A)

10. POWER LEVEL El 20.2203(a)(2)(ii)

El 50.36(c)(1)(ii)(A)

[I 50.73(a)(2)(iv)(A)

El 50.73(a)(2)(x)

El 20.2203(a)(2)(iii)

El 50.36(c)(2)

El 50.73(a)(2)(v)(A)

[

73.71(a)(4)

El 20.2203(a)(2)(iv)

El 50.46(a)(3)(ii)

El 50.73(a)(2)(v)(B)

El 73.71(a)(5) 100%

El 20.2203(a)(2)(v)

El 50.73(a)(2)(i)(A)

[I 50.73(a)(2)(v)(C)

El OTHER El 20.2203(a)(2)(vi)

El 50.73(a)(2)(i)(B)

El 50.73(a)(2)(v)(D)

Specify in Abstract below or in NRC Form 366A

12. LICENSEE CONTACT FOR THIS LER FACILITY NAME TELEPHONE NUMBER (Include Area Code)

Richard D. Flannigan, Manager Regulatory Affairs 1(62o) 364-4117MANU-REPORTABLE C

SYSTEM COMPONENT MANU-REPORTABLE

CAUSE

SYSTEM COMPONENT FACTURER TO EPIX CAUSEFSYSTEM CMO FACTURER TO EPIX

14. SUPPLEMENTAL REPORT EXPECTED

15. EXPECTED MONTH DAY YEAR SUBMISSION [E YES (If yes, complete 15. EXPECTED SUBMISSION DATE)

E NO DATE

,BSTRACT (Limit to 1400 spaces, i.e., approximately 15 single-spaced typewritten lines)

On July 12, 2010, at 1925 CST, an operations person notified Security that they could not locate their high security key. The last time they could account for the key was approximately 1200 CST. An extensive search was conducted of all the areas that the operator had been. In accordance with Regulatory Guide 5.62, Section C.2.2.16, and 10 CFR 73.71(b), a one-hour notification was made to the NRC. On 7/13/2010 at 0510 CST, the high security key was found in the Control Room on top of a cabinet.

The cause of the event was personnel error.

NRC FORM 366 (9-2007)

PLANT CONDITIONS PRIOR TO EVENT Mode 1 100% power

EVENT DESCRIPTION

On July 12, 2010, at 1925 CST an operations person notified Security that they could not locate their high security key. The last time they could account for the key was approximately 1200 CST when they went to lunch. An extensive search was conducted by Operations and Security personnel of all the areas that the operator had been. An alarm report was run to account for all unknown alarms, which showed that all.intrusion alarms were known or had been responded to. Security implemented a High Security corelock rotation of all areas compromised by the lost key as required by 10 CFR 73.55(g)6.D. On 7/13/2010 at 0510 CST, the high security key was found in the Control Room on top of a cabinet.

BASIS FOR REPORTABILITY A one-hour notification to the NRC was made per Regulatory Guide 5.62, Section C.2.2.16, for a lost key and per 10 CFR 73.71(b). A written report is required in 60 days per 10 CFR 73.71(a)4.

ROOT CAUSE The cause of the missing key was personnel error, inattention to detail.

CORRECTIVE ACTIONS

A robust device/method will be used to attach the high security key to the lanyard of the operations personnel. This action will be completed by December 23, 2010.

SAFETY SIGNIFICANCE

The event was determined not to be risk significant because the key was always in the Control Room.

There were no systems affected or threatened, directly or indirectly during this event.

OPERATING EXPERIENCE/PREVIOUS EVENTS A review of the past three years found seven incidents were high security keys were misplaced. None of these events were reportable because the keys were found within one hour of being misplaced.I