ENS 52748
ENS Event | |
|---|---|
21:00 May 10, 2017 | |
| Title | Research Test Reactor - Technical Specification Violation |
| Event Description | On Wednesday May 10, 2017 at approximately [1700 EDT], the Reactor Operator (RO) that was signed in on the reactor console logbook completed a ['key on'] checklist in preparation for a routine reactor startup. The RO left the control room and brought the log book to the reactor bridge for the Designated Senior Reactor Operator (DSRO) to sign off for the ['key on'] startup. The RO immediately realized his mistake concerning the procedural requirement for a reactor operator to be present in the control room at all times when the reactor is not secured (procedure OP-103), and returned to the control room.
The DSRO followed the RO to the control room and observed that the reactor key was in the on position, the control rods were all fully inserted, and reactor power was at residual levels. The reactor was shutdown, but was not secured. The DSRO determined that this constituted a violation of procedure OP-103 and could be a Reportable Occurrence as defined under Technical Specification 1.2.24 h. The DSRO reviewed Technical Specification (TS) 6.6.2, Action to be Taken in the Event of a Reportable Occurrence. The DSRO determined that under TS 6.6.2a that reactor conditions had been returned to normal by the presence of the licensed operator in the control room. The DSRO then signed the Key On checklist authorization for reactor startup and the reactor was started. The DSRO spoke with the Manager of Engineering and Operations (MEO) by telephone about this matter at approximately 1800 on May 10, 2017. The MEO concurred that procedure OP-103 was violated and would be reportable to the Nuclear Regulatory Commission (NRC). The DSRO and MEO agreed to discuss this matter with the Director, Nuclear Reactor Program and the Reactor Health Physicist on May 11, 2017. The MEO stated on May 11, 2017 that TS 6.1.3a, the specification implemented by procedure OP-103, was not met. It was agreed that required notifications to NRC would be made by [1700] on May 11, 2017 to meet the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> notification requirement. |
| Where | |
|---|---|
| North Carolina State University Raleigh, North Carolina (NRC Region 0) | |
| License number: | R-120 |
| Reporting | |
| Non | |
| Time - Person (Reporting Time:+18.4 h0.767 days <br />0.11 weeks <br />0.0252 months <br />) | |
| Opened: | Gerry Wicks 15:24 May 11, 2017 |
| NRC Officer: | Vince Klco |
| Last Updated: | May 11, 2017 |
| 52748 - NRC Website | |
North Carolina State University with Non | |
WEEKMONTHYEARENS 565532023-06-02T12:18:0002 June 2023 12:18:00
[Table view]Non Unscheduled Shutdown ENS 557472022-02-17T18:46:00017 February 2022 18:46:00 Non Technical Specification Violation ENS 527482017-05-10T21:00:00010 May 2017 21:00:00 Non Research Test Reactor - Technical Specification Violation ENS 464842010-12-13T20:00:00013 December 2010 20:00:00 Non Research Reactor Radiography Incident ENS 449912009-04-10T13:30:00010 April 2009 13:30:00 Non Violation of Limiting Conditions in Technical Specification 3.5B 2023-06-02T12:18:00 | |