ML20151U537

From kanterella
Jump to navigation Jump to search
Application for Amend to License DPR-3,authorizing Listed Tech Spec Changes,Per Generic Ltr 84-43, Reporting Requirements of 10CFR50... & Generic Ltr 85-19, Reporting Requirements on Primary Coolant Iodine Spikes. Fee Paid
ML20151U537
Person / Time
Site: Yankee Rowe
Issue date: 02/05/1986
From: Heider L
YANKEE ATOMIC ELECTRIC CO.
To:
Office of Nuclear Reactor Regulation
Shared Package
ML20151U542 List:
References
FYR-86-012, FYR-86-12, GL-84-43, GL-85-19, PC-192, NUDOCS 8602110045
Download: ML20151U537 (12)
v • d • e


Text

Tpho"" (6 ") 8 ' -" ' oo YANKEE ATOMIC ELECTRIC COMPANY TWX 710-380 7619

,-~f , FYR 86-012

\' 1671 Worcester Road. Framingham, Massachusetts 01701 2.C 15.1 d w. PC - 192 i: 0. n CE -

February 5, 1986 United States Nuclear Regulatory Commission Washington, DC 20555 Attention: Office of' Nuclear Reactor Regulation

References:

(a) License No. DPR-3 (Docket No. 50-29)

(b) USNRC Generic Letter No. 84-43, dated December 19, 1983,

" Reporting Requirements of 10CFR Part 50, Sections 50.72 and 50.73, and Standard Technical Specifications" (c) ^JSNRC Genvele Lettec No. 85-19, dated September 27, 1905,

" Reporting Requirements on Primary Coolant Iodine Spikes" (d) 10CFR 50.73 Licensee Event Report System

Subject:

Proposed Change to the Yankee Atomic Electric Company's Technical Specifications Concerning Licensee Event Reportu and Reporting Requirements on Primary Coolant Iodine Spikes

Dear Sir:

Pursuant to Section 50.59 of the Commission's Rules and Regulations, the Yankee Atomic Electric Company hereby requests the authorization to make the following modification to Appendix A of the Operating License:

PROPOSED CHAJGE Reference it made to the Technical Specifications of License No. DPR-3.

1. de propose to modify Technical Specifications 1.7, 6.5.1.6.f.

6.5.2.8.g, 6.6.1, 6.9.4, 6.9, 6.9.6 and 6.10.1 as indicated in Generic Letter No. 84-43, dated December 19, 1983, " Reporting Requirements of 10CFR Part 50, Sections 50.72 and 50.73, and Standard Technical Specifications."

2. We propose to modify Technical Specifications 3.3.3.6, 3.3.3.7, 3.11.1.1, 3.11.2.1, 3.11.2.5 and 3.11.3 to remove the negation of an LER for the successful completion of the applicable Action Statement.

k 0602110045 860205 PDR ADOCK 00000029 P PDR

>y valMd$ 00

United States Nuclear Regulatory Commission _ February 5, 1986 Attention: Office of Nuclear Reactor Regulation Page 2

3. We propose to modify Technical Specifications 3.11.2.6, 4.4.9.1 and 4.4.10.5, and Tables 4.4-5 and 6.9 to remove the reference to the old LER requirements.
4. We propose to modify Technical Specifications 3.5.2, 3.5.3 and 6.9.6

+-

to remove the requirement for a 90-day special report which would be redundant to a LER requirement.

5. We propose to modify Technical Specifications 3.11.1.2, 3.11.1.3, 3.11.1.4, 3.11.2.2, 3.11.2.3, 3.11.2.4, 3.11.4, 3.12.1, 3.12.2, 3.12.3 and 4.6.1.6 to remove wording that could put_the Technical Specification in conflict with 10CFR 50.73.
6. We propose to modify Technical Specifications 3.4.7 and 6.9.2 as indicated in Generic Letter No. 85-19, dated September 27, 1985,

" Reporting Requirements on Primary Coolant Iodine Spikes "

l Attachment A details each change, and Attachment B contains the revised pages.

. REASON AND BASIS FOR CHANGE i

This change is necessary to make the Technical Specifications consistent with'10CFR 50.73 and will reduce ambiguity and conflict between the i documents. With the incorporation of these changes, the possibility of l failing to submit a required report will be reduced.

I SAFETY CONSIDERATION This change has been evaluated and determined to involve a

, no-significant-hazards consideration. This determination is based on this being a purely administrative change in reporting requirements and does not j effect assumptions or methods used in accident analysis. The proposed change, therefore, does not:

1. Involve a significant increase in the probability or consequences of i an accident previously evaluated; or
2. Create the possibility of a new or different kind of accident from any accident previously evaluated; or
3. Involve a significant reduction in a margin of safety.

Based on the considerations contained herein, it is concluded that there

is reasonable assurance that operation of the Yankee Plant consistent with the
proposed Technical Specification'will not endanger the health or safety of the  ;
public. This proposed change has been reviewed by the Nuclear Safety Audit  !

and Review Committee.

i  !

United States Nuclear Regulatory Convaission February 5, 1986 Attention: Office of Nuclear Reactor Regulation Page 3 FEE DETERMINATION In accordance with 10CFR 170.21, a payment of $150.00 is enclosed for this application.

SCHEDULE OF CHANGE The changes described above will be incorporated into the Yankee Technical Specifications upon receipt of your approval.

We trust that this information is acceptable; however, should you have any questions regarding this matter, please contact me.

Very truly yours,

(' Y

~ L. H. Heider Vice President / Manager of Operations LHH/hja Enclosure COMMONWEALTH OF MASSACHUSETTS)

)ss MIDDLESEK COUNTY )

Then personally appeared before me, L. H. Heider, who, being duly sworn, did state that he is a Vice President of Yankee Atomic Electric Company, that he is duly authorized to execute and file the foregoing document in the name and on the behalf of Yankee Atomic Electric Company and that the statements therein are true to the best of his knowledge and belief, b

Robert H. Croce Notary Public My Commission Expires August 29, 1991

o ATTACHMENT A Reason for Change

1. Page I. INDEX - SECTION 1.0 Change: " Reportable Occurrence" to " Reportable Event."

Reason: To incorporate the recommendation in Generic Letter No. 83-43 that the new term used in 10CFR50.73, Reportable Event, replaces Reportable Occurrence presently used in Licensee Technical Specifications.

2. Page XV INDEX - SECTION 6.6 Change: " REPORTABLE OCCURRENCE ACTION" to " REPORTABLE EVENT ACTION."

Reason: To incorporate the recommendation in Generic Letter No. 83-43 that the new term used in 10CFR50.73, Reportable Event, replaces Reportable Occurrence presently used in Licensee Technical Specifications.

3. Page XV INDEX - SECTION 6.9.4 Change: " REPORTABLE OCCURRENCES" to " DELETE."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications and its requirements are being incorporated into Specification 6.6.

4. Page 1-2 Specification 1.7 Change: " REPORTABLE OCCURRENCE" to " REPORTABLE EVENT."

Reason: To incorporate the recommendation in Generic Letter No. 83-43 that the new term used in 10CFR50.73, Reportable Event, replaces Reportable Occurrence presently used in Licensee Technical Specifications.

5. Page 1-2 Specification 1.7 Change: "as a reportable occurrence in Specification 6.9.4." to "in Section 50.73 to 10CFR, Part 50."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

ATTACHMENT A (Continued)

6. Page 3/4 3-32 Specification 3.3.3.6, ACTION (a).

Change: Delete "With the successful completion of the requirements of the ACTION statement, the provisions of Specification 6.9.4 for the preparation and submittal of License Event Reports are not applicable."

Reason: Specification 6.9.4 is being deleted from the Yankee technical Specifications, and the paragraph is being simplified by removing negation of a Licensee Event Report. Yankee Technical Specification 6.6 shall specify all actions to be taken for REPORTABLE EVENTS.

7. Page 3/4 3-32 Specification 3.3.3.6, ACTION (b)

Change: Delete "in lieu of Licensee Event Report."

Reason: To simplify the paragraph by removing an extraneous phrase. Yankee Technical Specification 6.6 shall specify all actions to be taken for REPORTABLE EVENTS.

8. Page 3/4 3-37 Specification 3.3.3.7, ACTION (a)

Change: "as a reportable occurrence in Specification 6.9.4." to "in Section 50.73 to 10CFR, Part 50."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

9. Page 3/4 3-37 Specification 3.3.3.7, ACTION (b)

Change: Delete "With the successful cor.pletion of the requirements of the ACTION statement, the provisions of Specification 6.9.4 for the preparation and submittal of License Event Reports are not applicable."

Reason: Specification 6.9.4 is being deleted from the Yankeo Technical Specifications, and the paragraph is being simplified by removing negation of a Licensee Event Report. Yankee Technical Specification 6.6 shall specify all actions to be taken for REPORTABLE EVENTS.

10. Page 3/4 4-15 Specification 3.4.7, ACTION and 16
Change
Delete "A REPORTABLE OCCURRENCE shall . . . . information:

0 l- , _ .. _ _ __.. - _ _ _ _ _ . _ _ - _ . . _ _ _ . _ _ -

ATTACHMENT A (Continued)

1. Reactor power . . . was exceeded,
2. Fuel .... region,
3. Clean-up .... exceeded,
4. History .... and
5. The time .... I-131."

Reason: To incorporate into the Yankee Technical Specifications the modified reporting recommendations outlined in Generic Letter 85-19, Reference (c). This report will be described in Specification 6.9.2.

11. ~

e 3/4 4-26 Specification 4.4.9.1 Change: Delete "An initial report ... of this Specification."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and all reporting requirements will be in accordance with 10CFR50.73 as stated in Specification 6.6.

12. Page 3/4 4-36 Specification 4.4.10.5 Change: Delete "c. Results of steam .... to prevent recurrence."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications and its requirements are being incorporated into Specification 6.6.

13. Page 3/4 4-38 Table 4.4-5, 1st and 2nd SAMPLE INSPECTION Change: Delete both statements, " Prompt notification to NRC pursuant to Specification 6.9.4."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the table is being simplified by removing the statement of NRC notification.

Yankee Technical Specification 6.6 shall specify all actions to be taken for Reportable Events.

14. Page 3/4 5-3 Specification 3.5.2 Change: Delete "In the event ... cycles to date."

Reason: To remove from the Yankee Technical Specifications any requirements for a 90-day special report for ECCS actuation. These activities will be addressed in Yankee Technical Specification 6.6.

i

ATTACHMENT A (Continued)

15. Page 3/4 5-10 Specification 3.5.3, ACTION (e)

Change: Delete "e. In the event ... to date."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the table is being simplified by removing the statement of NRC notification.

Yankee Technical Specification 6.6 shall specify all actions to be taken for Reportable Events.

16. Page 3/4 6-7 Specification 4.6.1.6 Change: Delete "An initial report ... this specification."

Reason: To incorporate into the Yankee Technical Specifications ,

the modified reporting recommendations outlined in Generic Letter 85-19, Reference (c). This report will be described in Specification 6.9.2.  ;

17. Page 3/4 11-1 Specification 3.11.1.1 Change: Delete "With the successful ... not applicable."

Reason: Specification 6.9.4 is.being deloted from the Yankee Technical Specifications, and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

18. Page 3/4 11-4 Specification 3.11.1.2 Change: "in lieu of any other report required by Specification 6.9" to "and if not applicable to 10CFR50. 73 ," .

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

19. Page 3/4 11-5 Specification 3.11.1.3 Change: Delete "With the successful ... not applicable."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

20. Page 3/4 11-6 Specification 3.11.1.4 Change: Delete "in lieu of a Licensee Event Report."

Reason: Specification 6.9.4 is being deleted from the Yankee l Technical Specifications, and the paragraph is being

! simplified by removing negation of a Licensee Event' Report. Yankee Technical Specification 6.6 shall specify all actions to be taken for REPORTABLE EVENTS.

ATTACHMENT A (Continued)

21. Page 3/4 11-7 Specification 3.11.2.1 Change: Delete "With the successful ... no applicable."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications.'and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

22. Page 3/4 11-10 Specification 3.11.2.2 Change: "in lieu of any other report required by Specification 6.9" to "and if not applicab'e to 10CFR50.73."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

23. Page 3/4 11-11 Specification 3.11.2.3 Change: "in lieu of any other report required by Specification 6.9" to "and if not applicable to 10CFR50.73."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

24. Page 3/4 11-12 Specification 3.11.2.4 Change: "in lieu of any other report required by Specification 6.9" to "and if not applicable to 10CFR50.73."

deason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

25. Page 3/4 11-13 Specification 3.11.2.5 Change: Delete both statements of "With the successful ... not applicable."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

26. Page 5/4 11-14 Specification 3.11.2.6 Change: Delete "or provide ..... above limit."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and all reporting requirements will be in accordance with 10CFR50.73 as stated in Specification 6.6.

ATTACHMENT A (Continued)

27. Page 3/4 11-15 Specification 3.11.3 Change: Delete "With the successful ... not applicable."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

28. Page 3/4 11-16 Specification 3.11.4 Change: "in lieu of a Licensee Event Report" to "if not applicable to 10CFR50.73."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the definition of a REPORTABLE EVENT will be as specified in 10CFR50.73.

29. Page 3/4 12-1 Specification-3.12.1 Change: Delete both statements of "in lieu of a Licensee Event Report."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the paragraph is being simplified by removing negation of a Licensee Event Report. Yankee Technical Specification 6.6 shall specify all actions to be taken for REPORTABLE EVENTS.

30. Page 3/4 12-2 ACTION (c)

Change: Delete "In lieu of a Licensee Event Report and."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the paragraph is being simplified by removing negation of a Licensee Event Report. Yankee Technical Specification 6.6 shall specify all actions to be taken for REPORTABLE EVENTS.

31. Page 3/4 12-9 Specification 3.12.2 Change: Delete both statements of "in lieu of any other report required by Specification 6.9."

Reason: To simplify the paragraph by removing an extraneous phrase.

32. Page 3/4 12-10 Specification 3.12.3 Change: Delete "in lieu of a Licensee Event Report."

ATTACHMENT A (Continued)

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications, and the paragraph is being simplified by removing negation of a Licensee Event Report. Yankee Technical Specification 6.6 shall specify all actions to be taken for REPORTABLE EVENTS.

33. Page 6-8 Specification 6.5.1.6(f)

Change: " Review of events requiring 24-hour written notification to the Commission." to " Review of all REPORTABLE EVENTS."

Reason: To incorporate the recommendation in Generic Letter No. 83-43 that the new term used in 10CFR50.73, Reportable Event, replaces Reportable Occurrence presently used in Licensee Technical Specifications.

34. Page 6-11 Specification 6.5.2.8(g)

Change: " Events requiring 24-hour written notification to the Commission" to "ALL REPORTABLE EVENTS."

Reason: To incorporate the recommendation in Generic Letter No. 83-43 that the new term used in 10CFR50.73, Reportable Event, replaces Reportable Occurrence presently used in Licensee Technical Specifications.

35. Page 6-13 Specification 6.6 Change: " REPORTABLE OCCURRENCE ACTION" to " REPORTABLE EVENT ACTION."

Reason: To incorporate the recommendation in Generic Letter No. 83-43 that the new term used in 10CFR50.73. Reportable Event, replaces Reportable Occurrence presently used in Licensee Technical Specifications.

36. Page 6-13 Specification 6.6.1 Change: " REPORTABLE OCCURRENCES" to " REPORTABLE EVENTS."

Rearon: To incorporate the recommendation in Generic Letter No. 83-43 that the new term used in 10CFR50.73, Reportable Event, replaces Reportable Occurrence presently used in Licensee Technical Specifications.

37. Page 6-13 Specification 6.6.l(a)

Change: " Specification 6.9" to "Section 50.73 to 10CFR, Part 30 and."

. _= ..= . . . . . - .

ATTACHMENT A (Continued)

Reason: To incorporate into the Yankee Technical Specifications a direct reference to the reporting requirements specified in 10CFR50.73.

38. Page 6-13 Specification 6.6.1(b)

Change: "Each REPORTABLE OCCURRENCE requiring 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> notification to the Commission shall be reviewed by PORC and" to "Esch REPORTABLE EVENT shall be-reviewed by the PORC and the results of this review."

Reason: To incorporate into the Yankee Technical Specifications nomenclature-recommended in Generic Letter 83-43.

39. 'Page 6-14 Specification 6.9 Change: "6.9.3 and 6.9.4" to "and 6.9.3."

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications and its requirements are being incorporated into Specification 6.6.

40. Page 6-15 Specification 6.9.2 Change: Add "d. The results ... limit."

Reason. To incorporate into the Yankee Technical Specifications the modified reporting recommendations outlined in Generic Letter 85-19, Reference (c).

41. Page 6-15a Change: Add new page Reason: Specification 6.9.2(d) added to page 6-15.
42. Pages 6-16, Specification 6.9.4 6-17 and 6-18 Change: Delete Specification 6.9.4.

Reason: Specification 6.9.4 is being deleted from the Yankee Technical Specifications and its requirements are being incorporated into Specification 6.6.

43. Page 6-19 Specification 6.9.4 Change: Delete " Note: Sealed .... Item."

Reason: Specification 6.9.4 is being deleted frem the Yankee Technical Specifications and its requirements are being incorporated into Specification 6.6.

ATTACHMENT A ,

(Continued)

44. Page 6-22 Specification 6.9.6(b)

Change: "ECCS Actuation, Specification 3.4.2 and 3.5.3" to

"(Delete)."

Reason: This reporting requirement is incorporated into Yankee Technical Specification 6.6.

45. -Page 6-22 Specification 6.10.1(c)

Change: " REPORTABLE OCCURRENCE" to " REPORTABLE EVENT."

Reason: To incorporate the recommendation in Generic Letter No. 83-43 that the new term used in 10CFR50.73, Reportable Event, replaces Reportable Occurrence presently used in Licensee Technical Specifications.

Retrieved from "https://kanterella.com/w/index.php?title=ML20151U537&oldid=2963627"