NRC Form 366, 366A, and 366B, "Licensee Event Report"

Forms and Documents

Forms and supporting documents for this ICR

Document	Type	Status	Availability

No forms / supporting documents in this ICR. Check IC Document Collections.

IC Document Collections

Information collection document groups

IC ID	Collection	Type	Status	Form
33348	NRC Form 366, Licensee Event Report		Modified

ICR Details

OMB Control No: 3150-0104	ICR Reference No: 201508-3150-003
Status: Historical Inactive	Previous ICR Reference No: 201309-3150-004
Agency/Subagency: NRC	Agency Tracking No:
Title: NRC Form 366, 366A, and 366B, "Licensee Event Report"
Type of Information Collection: Revision of a currently approved collection	Common Form ICR:  No
Type of Review Request: Regular
OIRA Conclusion Action: Preapproved	Conclusion Date: 10/06/2015
	Date Received in OIRA: 08/10/2015
Terms of Clearance: The collection is pre-approved, contingent upon no substantive changes being made to this collection after adoption of the final rule. Otherwise this collection should be re-submitted to OMB for review.

table that charts list comparision

	Inventory as of this Action	Requested	Previously Approved
Expiration Date	10/31/2018	01/31/2017	01/31/2017
Responses	507	0	350
Time Burden (Hours)	35,368	0	28,000
Cost Burden (Dollars)	778	0	614

---

Abstract: FINAL RULE - Cyber Security Event Notifications. The final rule codifies the new requirements under section 73.77, "Cyber Security Event Notifications," and requires licensees subject to the provisions of section 73.54 to report certain cyber security events to the NRC within the timeliness requirements specified. Licensees are required to submit written security follow-up reports to the NRC on NRC Form 366, "Licensee Event Report," for certain notifications made under section 73.77. As a result of this rule, NRC Form 366 is being amended. NRC Forms 366A and 366B are unchanged. NOTE: This final rule affects two separate information collections: NRC Form 366 and 10 CFR Part 73. Burden associated with reporting on NRC Form 366 under the final rule has been submitted under this clearance number (3150-0104). Burden associated with other Part 73 requirements has been submitted under a request for a new clearance number. (At the proposed rule stage, all burden was submitted under 10 CFR Part 73, 3150-0002).

---

Authorizing Statute(s): PL: Pub.L. 83 - 703 1-311 Name of Law: Atomic Energy Act
  

Citations for New Statutory Requirements: None

---

Associated Rulemaking Information
RIN:	Stage of Rulemaking:	Federal Register Citation:	Date:
3150-AJ37	Final or interim final rulemaking

---

Federal Register Notices & Comments

Did the Agency receive public comments on this ICR? Yes

---

Number of Information Collection (IC) in this ICR: 1

table that charts list of burden

IC Title	Form No.	Form Name
NRC Form 366, Licensee Event Report	NRC Form 366A, NRC Form 366B, NRC Form 366

---

ICR Summary of Burden

table that charts list of burden

	Total Request	Previously Approved	Change Due to New Statute	Change Due to Agency Discretion	Change Due to Adjustment in Estimate	Change Due to Potential Violation of the PRA
Annual Number of Responses	507	350	0	157	0	0
Annual Time Burden (Hours)	35,368	28,000	0	7,368	0	0
Annual Cost Burden (Dollars)	778	614	0	164	0	0

Burden increases because of Program Change due to Agency Discretion: Yes

Burden Increase Due to: Changing Regulations

Burden decreases because of Program Change due to Agency Discretion: No

Burden Reduction Due to:

Short Statement: The final rule codifies the new requirements under section 73.77, "Cyber Security Event Notifications," and requires licensees subject to the provisions of section 73.54 to report certain cyber security events to the NRC within the timeliness requirements specified. Licensees are required to submit written security follow-up reports to the NRC on NRC Form 366, "Licensee Event Report," for certain notifications made under section 73.77.

---

Annual Cost to Federal Government: $1,831,600

Does this IC contain surveys, censuses, or employ statistical methods? No

Is the Supporting Statement intended to be a Privacy Impact Assessment required by the E-Government Act of 2002? No

Is this ICR related to the Affordable Care Act [Pub. L. 111-148 & 111-152]? No

Is this ICR related to the Dodd-Frank Wall Street Reform and Consumer Protection Act, [Pub. L. 111-203]? No

Is this ICR related to the American Recovery and Reinvestment Act of 2009 (ARRA)? No

Is this ICR related to the Pandemic Response? Uncollected

---

Common Form ICR:  No

---

On behalf of this Federal agency, I certify that the collection of information encompassed by this request complies with 5 CFR 1320.9 and the related provisions of 5 CFR 1320.8(b)(3).

The following is a summary of the topics, regarding the proposed collection of information, that the certification covers:

(a) It is necessary for the proper performance of agency functions;

(b) It avoids unnecessary duplication;

(c) It reduces burden on small entities;

(d) It uses plain, coherent, and unambiguous language that is understandable to respondents;

(e) Its implementation will be consistent and compatible with current reporting and recordkeeping practices;

(f) It indicates the retention periods for recordkeeping requirements;

(g) It informs respondents of the information called for under 5 CFR 1320.8 (b)(3) about:

(i) Why the information is being collected;

(ii) Use of information;

(iii) Burden estimate;

(iv) Nature of response (voluntary, required for a benefit, or mandatory);

(v) Nature and extent of confidentiality; and

(vi) Need to display currently valid OMB control number;

(h) It was developed by an office that has planned and allocated resources for the efficient and effective management and use of the information to be collected.

(i) It uses effective and efficient statistical survey methodology (if applicable); and

(j) It makes appropriate use of information technology.

If you are unable to certify compliance with any of these provisions, identify the item by leaving the box unchecked and explain the reason in the Supporting Statement.

Certification Date: 08/10/2015

---