ML20058N767

From kanterella
Jump to navigation Jump to search
Application for Amend to License DPR-65,revising Tech Specs Per Generic Ltr 87-09 Re Section 3 on Limiting Conditions for Operation & Section 4 on Surveillance Requirements
ML20058N767
Person / Time
Site: Millstone Dominion icon.png
Issue date: 08/09/1990
From: Mroczka E
NORTHEAST NUCLEAR ENERGY CO., NORTHEAST UTILITIES
To:
NRC OFFICE OF INFORMATION RESOURCES MANAGEMENT (IRM)
Shared Package
ML20058N770 List:
References
B13079, GL-87-09, GL-87-9, NUDOCS 9008150064
Download: ML20058N767 (11)


Text

'

, 4 .-

I O

ll , . ,

l 4 l

General Offices

- km AkTF ONNECTICUT 06141-0270 I.

i_ August 9, 1990 Docket No. 50-336 B13079 Re: 10CFR50.90 U. S. Nuclear Regulatory Commission Attn: Doument Control Desk Washington, DC 20555 Gentlemen:

Millstone Nuclear Power Station Unit No. 2 Pro)osed Revision to Technical Specifications C lanaes Suaaested by Generic letter 87-09 Pursuant to 10CFR50.90, Northeast Nuclear Energy Company '(NNECO). hereby proposes to amend its Operating License, DPR 65,.by incorporating the changes identified in Attachment 1 into the Technical Specifications of Millstone Unit No. 2. The proposed changes involve no significant hazards considerations.

As Staffpart of anGeneric issued initiativeLetter to improve 87-09,(p'dustry technical specifications, the NRC

-which suggested various changes which could be proposed by licensees to improve the clarity of the technical speci-fications in certain, specified, areas. The following is an itemization.of how the suggested changes from Generic Letter 87-09 have been adapted for Millstone Unit No. 2.

The Staff proposed wording for these Technical ' Specification = changes which has,.for the most part, been adopted in the attached proposed changes to the Millstone Unit No. 2 Technical Specifications. NNECO's review of the applica-

.bility of. Generic Letter 87-09 to the Millstone Unit No. 2 Technical Specifi-cations, however, identified several areas where deviations from the guidance provided in Generic letter 87 09 are warranted. Although the proposed changes differ from the Staff guidance, they are consistent with the . intent of Generic Letter 87-09.

General Discussion

- The primary changes ~ suggested in Generic Letter 87-09 are to Technical Speci-fication Sections 3.0 and 4.0. In addition, due to the changes to Sections 3.0 (1) Generic letter 87-09, " Sections of 3.0 and 4.0 of the Standard Technical Specifications (STS) on the Applicability of Limiting Conditions ~of Operation and Surveillance Requirements," dated June 4, 1987.

9008150064 9ooeo9 7 0 W ., 'DR . . ADOCK 05000336 1 (\ g\\ i l

FDC k 5

. - - .. A

.- o ,

U.S. Nuclear Regulatory Commission B13079/Page 2 August 9, 1990 l l

and 4.0, many of the individual Technical Specifications in Section 3 (Limit-  !

ing Conditions for Operation) and Section 4 (Surveillance Requirements) also l recuire revision in order to be consistent with the intent of the revised 3.0 anc 4.0.

In order to implement the recommendations of Generic Letter 87 09, the NRC  ;

Staff provided very specific guidance on what changes were required (e.g., i revised wording for T.S. 3.0.4, deletion of certain existing exemptions from T.S. 3.0.4). As a result of NNECO's review of this guidance, several areas i were identified where application of this guidance would not be consistent t with the intent of Generic letter 87-09. For example, the changes recommended i in Generic Letter 87 09 include revising T.S. 3.0.4 such that entry into an l operational mode is permitted while subject to the provisions of an ACTION statement, provided that the applicable ACTION statement would allow continued l operation for an unlimited period of time and would not require that the plant i be shut down. However, T.S. 3.7.1.2 ACTION statement (c) currently allows '

indefinite continued operation with all three auxiliary feedwater pumps >

inoperable. Although this allowance is understandable for power operation, it  ;

is inappropriate to allow start up in this condition. For example, passing through MODE 4 to MODE 3, shutdown cooling is no longer available for decay  :

heat-removal. In MODE 3, only the steam generators can be used for decay heat  :

removal. With no auxiliary feed pumps operable, entry into this condition should not be permitted since there would be no safety-related system ~ avail-  ;

able for steam generator inventory makeup. This example shows why deviations from Generic Letter 87-09 were required in order to meet the intent of the -

recommended changes. Other deviations are discussed in the following pages.

Proposed Chances to Section 3--Limitina Conditions for Opg.tgliga The changes recommended by the Staff in Generic Letter 87 09 would revise T.S. 3.0.4 such that it would allow entry .into an operational mode with reliance on one or more ACTION statements provided that conformance to the ACTION sta'ements would allow continued operation for an unlimited period of )

time. If ti.e ACTION statements would require a plant shutdown within a spect. ]

fied time interval, then entry into a higher operational mode would not be allowed. ) l A number of Technical Specifications currently contain an exemption from T.S. 3.0.4. The Staff suggested that these specific exemptions be deleted only I where the ACTION statement would permit continued operation for an unlimited period of time. Under the Generic Letter 87-09 guidance, where the ACTION q statements require a plant shutdown, the exemption from T.S. 3.0.4 would be i retained. The concern with retaining exemptions to T.S. 3.0.4 is that in the j case where the exemption is retained (i.e., ACTION statement would require i shutdown, so start-up should not be permitted), there would be u guidance on l weh ther or. not a mode change would be permitted. That is, if T.S. 3.0.4 does i not apply, there would be no other Technical Specification which would either preclude or allow start-up. ,

I

i, '

. 1

. . I

,' . l

- t l

U.S. Nuclear Regulatory Commission B13079/Page 3 l August 9, 1990 '

t Please note that the NRC's (and NNECO's) proposed revised wording for T.S.

3.0.4 already provides the necessary guidance for All situations, and the ,

current exemptions from T.S. 3.0.4 in individual specifications can all be deleted reaardless of the ACTION reautrements. If this is done, T.S. 3.0.4 ,

would always apply. If compliance with the ACTION requirements would allow t unlimited continued operation then mode changes would explicitly be allowed.

On the other hand,. if the ACTION requirements would require a plant shutdown, T.S. 3.0.4 would explicitly prohibit mode changes while still subject to the ,

ACTION- statement. This meets exactly the intent of the Staff's recommended changes and eliminates the potential for confusion that could result if an )

exemption from T.S. 3.0.4 were retained. ,

The specific changes proposed for the Millstone Unit No. 2 Technical Specifi- I cations are summarized below. Note that in several cases due to unique wording of individual specifications, changes other than deletion of the exemption from T.S. 3.0.4 are required to ensure that the intent of the existing ACTION requirement is not affected. Also, various other changes were made to a few

  • affected pages to achieve consistency throughout the Technical Specifications and to correct existing editorial errors.

T.S. 3.0.3 - This specification is proposed to be changed in part to read: .

"Where corrective measures are completed that permit operation under the ACTION requirements, the ACTION may be taken in ,

accordance with the specified time limits as measured from the time it is identified that a Limiting Condition for Operation is not met." This change is being proposed to be consistent with the wording as contained throughout the proposed specifications for Sections 3.0 and 4.0. ,

T.S. 3.0.4 - This specification is proposed to be changed to read: " Entry into an OPERATIONAL MODE or other specified condition shall not be made when the conditions of the limiting Condition for 0)eration are not met and the associated ACTION requires a '

slutdown if they are not met within a specified time interval.

Entry into an OPERATIONAL H0DE or other specified condition may

be made in accordance with ACTION requirements when conformance l to them permits continued operation of the- facility for an l

unlimited period of time. This provision shall not prevent l passage through or to OPERATIONAL MODES as required to comply with ACTION requirements."

T.S. 3.1.3.3 - delete exemption from 3.0.4 T.S. 3.3.3.1 - delete exemption from 3.0.4 I T.S. 3.3.3.2 - delete exemption from 3.0.4 T.S. 3.3.3.3 delete exemption from 3.0.4 l i

J

f. .

l , .

i U.S. Nuclear Regulatory Commission i

813079/Page 4 August 9, 1990 T.S. 3.3.3.4 - delete exemption from 3.0.4 T.S. 3.3.3.7 - delete exemption from 3.0.4 T.S. 3.3.3.8 - delete exemption from 3.0.4 T.S. 3.3.3.9 - delete exemption from 3.0.4 T.S. 3.3.3.10 - . delete exemption from 3.0.4 T.S. 3.4.3 - delete exemption from 3.0.4. This will still permit start-up l

with the PORVs ino serable, block valves closed and power removed, as permittec by the current Technical Specifications.

T.S. 3.4.8 - delete exemption from 3.0.4. Add a statement to the current ACTION statement-(a) that ' Entry into 'an OPERATIONAL MODE or other specified condition is permitted pursuant to Specifica-tion 3.0.4 when subject ~to this ACTION statement." This is

necessary to retain the ability to start-up with the primary coolan+ iodine concentration above the LCO but within the allowable limit, as permitted by the current Technical Specifi-cations,
j. T.S. 3.4.9.3 - delete exemption from 3.0.4 T.S. 3.4.10 - delete exemption from 3.0.4 T.S. 3.4.11 - delete exemption from 3.0.4 T.S. 3.6.1.3 - delete exemption from 3.0.4 and replace with the following statement: "

Entry'into an OPERATIONAL MODE or other s)ecified i condition under the provisions of Specification 3.0.4 siall not be made if the inner air lock door is inoperable." This will retain the intent of the current Technical Specification, which allows. start-up if the outer air lock' door;is. inoperable.

T.S. 3.7.1.1 . delete exemption from 3.0.4 T.S. 3.7.1.2 - add the following to ACTION statement - (c): " Entry into an OPERATIONAL MODE or other specified condition under the provi-sions of Specification 3.0.4 shall not- be made with three auxiliary feedwater pumps inoperable." This is necessary so i that.having three AFW pumps inoperable not requiring a shutdown-l is not interpreted to mean that start-up in this condition is l permitted.  ;

I l T.S. 3.7.7.1 - delete exemption from 3.0.4 T.S. 3.7.9.1 - delete . exemption from 3.0.4 1

> l t ,  ;

.. 4 U.S. Nuclear Regulatory Commission B13079/Page 5 August 9, 1990 i

T.S. 3.7.9.2 - delete exemption from 3.0.4 T.S. 3.7.9.3 - delete exemption from 3.0.4 T.S. 3.7.10 - delete exe.nption from 3.0.4 T.S. 3.11.1.2 - delete exemption from 3.0.4 T.S. 3.11.2.2 - delete exemption from 3.0.4 T.S. 3.11.2.3 - delete exemption from-3.0.4 T.S. 3.11.3 - delete exemption from 3.0.4 Prooosed Chanaes to Section 4--Surveillance Reauirements The first change suggested by the Staff in Generic letter 87-09 would revise Specification 4.0.3 to allow a delay of 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> before implementation of ACTION requirements after it is identified that a surveillance has not been.

performed. This would allow time to perform the surveillance to demonstrate  !

equipment operability and compliance with the LCO when the allowable outage ,

time limits of the ACTION requirements are less than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />. Surveillance I requirements affecting LCOs with ACTION times greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> would not .

be affected by this change. No changes to individual-Technical Specifications  !

are required as a result of this change.

The second change is an addition to T.S. 4.0.4 to permit ~ passage into -lower operational modes when required by ACTION requirements without first having to perform the surveillances applicable in the lower modes. The intent is to not delay shutdown of the facility when it is required by T.S. ACTION require-ments. Again, no changes are required for individual Technical Specifications l

other than 4.0.4.

1 As _a part of the Generic Letter 87-09 changes, the Staff also suggests that l l

the exemptions to T.S. 4.0.4 contained in individual Technical Specifications i

[ be deleted. These exemptions are currently contained in T.S. 4.2.3.1, 4.2.4.1, 4.2.6.2, and 4.7.1.2. Typically, equipment required by an LCO to be operable in a given mode must have the surveillance requirements performed before entry L into that mode is allowed. However, some surveillance requirements cannot:be satisfied (e.g., power distribution limits) until the mode is. entered. These Technical Specifications are currently exempted from the requirements of T.S.

4.0.4.

Generic letter 87-09 states that " allowance of an exception to Specification 4.0.4 can create a conflict with Specification 4.0.3" and that "when surveil-lance requirements can only be completed after entry into a mode or specified condition for.which the Surveillance Requirements apply, an exception to the i recuirements of Specification 4.0.4 is allowed. However, upon entry into this '

moce or condition, the requirements of Specification 4.0.3 may not be. met L

(* ,

. l

. 1 U.S. Nuclear Regulatory Commission B13079/Page 6 August 9, 1990 ,

because the Surveillance Recuirements may not have been performed within the allowed surveillance interval."

NNECO's interpretation of the Technical Specifications is that if an exception is granted to Specification 4.0.4 for an individual surveillance requirement, the normal surveillance interval is applicable. That is, the normal surveil-lance . interval is assumed to start at the time of entry into the mode for which the surveillance is required to be performed. Taking exception .to Specif,1 cation 4.0.4 in a surveillance requirement explicitly permits entry into an operational mode when the applicable surveillances. have rot been performed within the required surveillance interval. If .this is explicitly allowed, we do. not see how this can be interpreted as a violation of the Specification 4.0.3 requirement that surveillances be performed within the allowed surveillance interval. If entry into a mode with the surveillance interval exceeded is acceptable, then that same situation should not. be a violation of a specification that is applicable only when the mcda is entered.

An exception to one specification should not automatically be a violation of a different specification.

For example, the surveillance requirements associated with T.S. 3/4'2.3, Total

! Integrated. Radial Peaking Factor, contains an exemption to 4.0.4. Thus, the  !

l surveillance requirements for this LCO are required to be performed only at the frequency required by 4.2.3.2. Typically this would be once every 31 days ,

of Mode 1 operation or prior to reaching 70% power after refueling. Time spent '

in lower modes of operation where the specification does not apply is not part of the required surveillance interval. Using the Staff's interpretation, only the 24-hour " grace" period allowed by the revised 4.0.3 would be available to complete all required surveillances before determining that the LC0 has not been met and applying the ACTION requirements. Depending on plant conditions during start-up and rate of power ascension, etc., 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> is not adequate to i perform reliable surveillances on power distribution limits. Since we  !

currently do not see any conflict between 4.0.3 and 4.0.4 due to the exceptions granted to 4.0.4, it is requested that these exceptions be retained.

The affected Technical Specifications and the proposed changes are identified below:

T.S. 4.0.3 - revised to read " Failure to perform a Surveillance Requirement within the allowed surveillance interval, defined by Specifica-tion 4.0.2, shall constitute failure to meet the OPERABILITY requirements for a Limiting Condition for Operation. The time ,

limits of the ACTION requirements are applicable at the time it. '

is : identified that a Surveillance Requirement has not been performed. The ACTION require;nents may be delayed for up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> to permit the completion of the surveillance when the allowable outage time limits of the ACTION requirements are  !

less than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />. Surveillance requirements do not have to '

be performed on inoperable equipment." l

?

I

-~ >

l ,

l .

l U.S. Nuclear Regulatory Commission B13079/Page 7 August 9, 1990 l

T.S. 4.0.4 - add the following sentence to the end
"This provision shall l not prevent passage through or to OPERATIONAL MODES as required '

to comply with ACTION requirements."

Pronosed Chances to Bases l

i

' Several deviations are recommended from the bases provided in Generic Letter 87-09. These are:

Specification 3.0.3 - delete sentence which states that "one hour is  !

l allowed to prepare for an orderly shutdown before initiating a change in plant operation." The exact -  :

timing of power reductions, shutdown, etc., should be at the discretion of ' the operator, so long as the l time limits of T.S. 3.0.3 are met. This sentence  :

l could be interpreted as an additional Technical Specification requirement.

revise the next to last sentence at the bottom of page B3/4 02 for consistency with remainder of Sections 3.0 and 4.0.

Specification 4.0.3 - delete the last portion of the first paragraph on page B3/4 0-5 regarding enforcement action and the reporting requirements. This is inconsistent with the  ;

purpose of the. Bases. -

delete the sentence in the middle paragraph of aage '

B3/4 0 5 discussing- the applicability of the. 24 1our

" grace" period for surveillances which are exempted from T.S. 4.0.4, as this is inconsistent with how NNECO interprets these requirements (see earlier discussion).

Sionificant H m nds Contideratiqn l NNECO has reviewed the specific proposed changes to Sections 3.0 and 4.0 of the Technical Specifications in accordance with 10CFR50.92 and has concluded t

that the changes do not involve a significant hazards ansideration. NNECO's analysis pursuant to 10CFR50.92 specifically addressed the changes as t proposed, using current Technical Specifications (rather than the text suggested in Generic Letter 87-09) as the benchmark.

1 NNECO concludes that the proposed changes to Sections 3.0 and 4.0 do not:  ;

1. Involve a significant increase in the probability or consequences of any accident previously analyzed.

)

U.S. Nuclear Regulatory Commission B13079/Page 8

. August 9, 1990

a. Section 3.0: The current Technical Specification 3.0.4 prohibits changing mode of operation unless all Limiting Conditions for Operation (LCOs) are met. Certain Technical Specifications, however, contain an exemption to Technical Specification 3.0.4 that allows start-up with equipment or parameters that are not in com)11ance with an applicable LCO. This exemption typically is proviced for that equipment covered by Technical Specifications that is not necessary to adequately mitigate design basis accidents in these cases, because equipment operability does not impact the design basis, there is no need for a restriction on plant start up. In all of these cases exce)t one (Technical Specification 3.4.8), the ACTION statements allow continued operation for an. indefinite period. (Technical Specification 3.4.8 provides an exemption so that a posttrip iodine spike will not preclude restart.)

The proposed revision to Technical Specification 3.0.4 would speci-fically allow entry into an operational mode while subject to ACTION requirements, provided those requirements allow indefinite continued operation. The revised Technical Specification 3.0.4 is thus consis-tent with the concept and intent of the current Technical Specifica-tions; the numerous exemptions from Technical Specification 3.0.4  :

would no longer be necessary or appropriate. As such, the proposed '

changes will not increase the probability. or consequences of any accident previously analyzed.

1 Several other current Technical Specifications in Section 3.0 (3.4.3. , 3.4.8, 3.6.1.3, and 3.7.1.2) contain limited exemptions 4 from the current Technical Specification 3.0.4 that cannot be simply ,

deleted as a result of the proposed revision to Technical Specifica- 1 tion 3.0.4. NNEC0 has therefore proposed revisions to these that are consistent with the intent of Generic Letter 87-09 and that ensure the intent and function of the Technical Specifications do not change. Therefore, these proposed changes as well as the various '

editorial changes will also not impact the probability or consequences of accidents previously analyzed.

Finally, the proposed changes to Technical Specification 3.0.4 also j impact other individual Technical Specifications which do not  ;

currently contain an exemption from T.S. 3.0.4 (e.g., Technical Specification 3.6.3.1, which permits indefinite continued operation with an inoperable containment isolation valve provided the penetra-tion is isolated by a deactivated valve). In these cases, the proposed revisions to Technical Specification 3.0.4 would allow-start-up because the a)plicable ACTION requirements allow indefinite continued operation. Fowever this minor change is consistent with  !

the objective of Generic Letter 87-09 and the incent of the other proposed revisions, i.e., to allow- mode changes when subject to ACTION requirements that do not impact continued operation. In these  !

cases, the ACTION requirements provide an equivalent level of safety (

)

l

- 1 U.S. Nuclear Regulatory Commission ,

B13079/Page 9  !

August 9, 1990 l l l t

i j without requiring a shutdown. Allowing start up in these situations will therefore have no adverse impact on the probability or conse-quences of any accident previously anal / zed,

b. Section 4.0: The proposed change would revise Technical Specifica-  :

tion 4.0.4 to allow a delay of up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> to implement ACTION recuirements in the event a-required surveillance was not performed anc the allowable outage time limits of the ACTION statement are ,

less than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />. This delay would apply only in the event of a missed surveillance; it would not apply to a failed surveillance.

The proposed delay in implementing the ACTION requirements is ,

intended to allow sufficient time to complete the required surveil- '

lance. The proposal recognizes that a missed surveillance is much less significant than a failed surveillance. Further, given that the vast majority of surveillances performed meet relevant acceptance criteria, in most cases the missed surveillance -- once completed --

will demonstrate the equipment to be operable. The proposed change recognizes that it is overly conservative to assume that equipment ,

is inoperable simply because a surveillance was missed.

This proposed change to Technical Specification 4.0.4 does not impact the integrity of any component or of the reactor coolant pressure boundary. The proposed change does not impact, in a substantive way, the operability or surveillance requirements for any component, nor does it change the way surveillance / testing is ,

performed. NNECO therefore concludes that the change will not increase the probability or consequences of any accident previously analyzed.

The proposed change to Technical Specification 4.0.4 is essentially a clarification of existing Technical Specifications. As such, this-change will also have no effect on the probability or consequences of accidents previously analyzed.

2. Create the possibility of a new or different kind of accident from any previously analyzed.

1 None of the proposed changes to either Section 3.0 or Section 4.0 of  !

the Technical Specifications or the proposed editorial changes will  !

have any impact on plant response. The amendments requested also involve no changes to plant equipment or to either normal or remergency operating procedures. Thus, no new failure modes will be introduced.

In addition, all of the equipment affected by the change to Techni-cal Specification 3.0.4 is either not required for mitigation of a design basis accident or the applicable Technical Specification i

i i

1- -

l' .

U.S. Nuclear Regulatory Commission B13079/Page 10 August 9, 1990 ACTION statement provides an equivalent level of safety. Thus, plant response will be unaffected.

In summary, NNECO concludes that the proposed changes will not create the possibility of any new or different kind of accident from those previously analyzed.

3. Involve a significant reductior in any margin of safety.

As discussed above, none of the proposed changes to either Section 3.0 or Section 4.0 of the Technical Specifications or the editorial changes will impact plant equipment, plant response, or any param-eter related to the integrity of the reactor coolant pressure boundary. Further, the proposed changes will not affect either normal or emergency operating procedures. Therefore, the proposed changes will not impact any safety limit or reduce any margin of safety.

Moreover, the Commission has provided guidance concerning the application of standards in 10CFR50.92 by providing certain examples (March 6,1986, FR7751) of amendments that are considered not likely to involve a significant hazards consideration. The changes proposed herein are not enveloped by a specific example.

The proposed changes were suggested, for the most part, by the NRC Staff via ,

Generic Letter 87-09, to clarify and improve the Technical Specifications; I they affect no parameters or systems directly, are associated with no failure i modes, do not affect operation of the plant, and do not change the intent of ,

the Technical Specifications. Therefore, the proposed changes involve no significant hazards consideration, i

The Millstone Unit No. 2 Nuclear Review Board has reviewed and approved the  !

attached proposed revisions and has concurred with the above determinations, j l

The improvements suggested by the NRC Staff in Generic letter 87-09 have been  !

incorporated into the Technical Specifications of the Haddam Neck Plant. This I was issued as Amendment No. 125, dated April 26, 1990, as part of their conversion to Standard Technical Specifications.

The proposed change is not required to support continued operation.

Therefore, NNEC0 requests the effective date for the proposed change- be .

60 days after issuance by the NRC Staff. This will provide adequate time for I

changes to controlled documents and any applicable training of operational personnel, i

l

/

/

,/ /p /

&p 3 ,

s;/ \,i '

/

+

s y

8

't4 s

4,.

s s

s s

3 N

\

u e r

U.S. Nuclear Regulatory Comission B13079/Page 11 August 9, 1990 In accordance with 10CFR50.91(b), we are providing the State of Connecticut with a copy of this proposed amendment.

Very truly yours, NORTHEAST NUCLEAR ENERGY COMPANY h dt l E. J/Nroczka //

Senior Vice PresTdent cc: T. T. Martin, Region I Administrator G. S. Vissing, NRC Project Manager, Millstone Unit No. 2 W. J. Raymond, Senior Resident. Inspector, Millstone Unit Nos. 1, 2, and 3 P. Habighorst, Resident Inspector, Millstone Unit No. 2 Mr. Kevin McCarthy Director, Radiation Control Unit Department of Environmental Protection Hartford, Connecticut 06116 STATE OF CONNECTICUT)

) ss. Berlin COUNTY OF HARTFORD Then personally appeared before me, E. J. Mroczka, who being duly sworn, did state that he is Senior Vice President of Northeast Nuclear Energy Company, a Licensee herein, that he is authorized to execute and - file the foregoing information in the name and on behalf of the Licensee herein, and that the statements contained in said information are true and correct to the best of his knowledge and belief.

4't/twD tn/ /

Notary Pupc MyComm!:c'oa Exp!ms March 31,1993,

_ _ . . .