ML062610316
| ML062610316 | |
| Person / Time | |
|---|---|
| Site: | Oyster Creek |
| Issue date: | 09/15/2006 |
| From: | Cowan P AmerGen Energy Co |
| To: | Document Control Desk, Office of Nuclear Reactor Regulation |
| References | |
| 2130-06-20398 | |
| Download: ML062610316 (5) | |
Text
An Exelon Company AverLen Energy Company, LLC www.exeiorcorp.coiTI 10 CFR 50.55a 21 30-06-20398 September 15,2006 U. S. Nuclear Regulatory Commission Attn: Document Control Desk Washington, DC 20555 Oyster Creek Generating Station Facility License No. DPR-16 Docket No. 50-219
Subject:
Response to Request for Additional Information - Proposed Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel
References:
- 1)
- 2)
- 3)
- 4)
AmerGen letter 21 30-00-20300 dated November 10, 2000, Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel AmerGen letter 21 30-00-20304 dated November 14,2000, Modification to Proposed Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel USNRC letter dated November 16,2000, Request to Use an Alternative Repair of the Control Rod Drive Housing Interface with the Reactor Vessel at the Oyster Creek Nuclear Generating Station (TAC NO.
M 6046 1 )
AmerGen letter 21 30-01 -20031 dated January 19, 2001, Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel -
Clarification of Leakage Inspection USNRC letter dated January 8, 2002, Oyster Creek Nuclear Generating Station - Clarification of Leakage Inspection (TAC NO. MB1065)
AmerGen letter 21 30-02-2021 4 dated July 26, 2002, Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel AmerGen letter 21 30-02-20291 dated October 4,2002, Additional Information - Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel (TAC No. MB5700)
USNRC letter dated October 18, 2002, Oyster Creek Nuclear Generating Station - Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel (TAC NO. M65700)
AmerGen letter 21 30-03-20271 dated October 21, 2003, Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel AmerGen letter 21 30-04-201 57 dated July 20,2004, Response to Request for Additional Information Concerning Alternative Repair of Control Rod Drive Housing interface with Reactor Vessel
U.S. Nuclear Regulatory Commission September 15, 2006 Page 2
- 13)
- 14)
AmerGen letter 21 30-04-20201 dated August 23,2004, Response to Request for Additional Information Concerning Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel AmerGen letter 21 30-04-20214 dated September 8,2004, Response to Request for Additional Information Concerning Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel USNRC letter dated November 12,2004, Oyster Creek Nuclear Generating Station - Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel (TAC NO. MC1099)
AmerGen letter 21 30-06-20297 dated March 31,2006, Proposed Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel - Draft Code Case N-730, Roll-Expansion of Class 1 Control Rod Drive Bottom Head Penetrations in BWRs,Section XI, Division 1 AmerGen letter 21 30-06-20355 dated June 23,2006, Response to Request for Additional Information - Proposed Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel I AmerGen letter 21 30-06-20383 dated August 14,2006, Response to Request for Additional Information - Proposed Alternative Repair of Control Rod Drive Housing Interface with Reactor Vessel In the Reference 14 letter, AmerGen Energy Company, LLC (AmerGen) requested a proposed alternative to the requirements of ASME Section XI, 1995 Edition through 1996 Addenda, IWA-4000, Repair/Replacement Activities, for the repair of CRD housing penetrations 42-43 and 46-39 at the Oyster Creek Generating Station. Specifically, AmerGen proposes the use of Draft Code Case N-730, Roll-Expansion of Class 1 Control Rod Drive Bottom Head Penetrations in BWRs,Section XI, Division 1. Additionally, AmerGen requested approval of the code case as an alternative repair for any additional penetrations that may exhibit leakage for the remainder of the Oyster Creek Generating Station Fourth Ten-Year lnservice Inspection Interval.
In the Reference 15 letter, AmerGen provided a response to the NRC staffs request for additional information. In a conference call with the NRC staff on September 13, 2006, additional clarification was requested. Specifically, in the Reference 15 response, we provide information concerning non-destructive examination resulting from the roll repair. The purpose of this letter is to clarify that a plant specific mockup will be available for future inservice inspection of CRD housing penetrations 42-43 and 46-39 and in the event that additional roll repairs are necessary. This will ensure compliance with Appendix I of the draft code case. contains a Summary of Commitments concerning this issue.
If you should have any questions, please contact Mr. Tom Loomis at 61 0-765-551 0.
Very truly yours, Pamela B. Cowan Director - Licensing & Regulatory Affairs AmerGen Energy Company, LLC
U.S. Nuclear Regulatory Commission September 15, 2006 Page 3
Attachment:
Summary of Commitments cc:
S. J. Collins, USNRC, Administrator, Region I G. E. Miller, USNRC, Project Manager, Oyster Creek M. Ferdas, USNRC, Senior Resident Inspector, Oyster Creek File No. 06028
ATTACHMENT 1
SUMMARY
OF COMMITMENTS
SUMMARY
OF COMMITMENTS The following table identifies commitments made in this document. (Any other actions discussed in the submittal represent intended or planned actions. They are described to the NRC for the NRCs information and are not regulatory commitments.)
COMMITMENT OUTAGE The purpose of this letter is to clarify that a plant specific mockup will be available for future inservice inspection of CRD housing penetrations 42-43 and 46-39 and in the event that additional roll repairs are necessary. This will ensure compliance with Appendix I of the draft code case.
COMMITMENT TYPE ONE-TIME ACTION (Yes/No)
No Programmatic (Y es/No)
Yes