Section 20.19(l)(1)(i-iii) and 20.18(l)(2)(i-iii), 911 Callback Capability; Non-initialized Handsets

Forms and Documents

Document	Type	Status	Availability
0987_ss_092011.doc	Supporting Statement A	Uploaded 2011-09-28	Available

IC Document Collections

IC ID	Collection	Type	Status	Form
31532	911 Callback Capability; Non-initialized Handsets		Modified
198595	added state, local or tribal government as a respondent		New

ICR Details

OMB Control No: 3060-0987	ICR Reference No: 201107-3060-026
Status: Historical Active	Previous ICR Reference No: 200810-3060-001
Agency/Subagency: FCC	Agency Tracking No: PSHSB
Title: Section 20.19(l)(1)(i-iii) and 20.18(l)(2)(i-iii), 911 Callback Capability; Non-initialized Handsets
Type of Information Collection: Extension without change of a currently approved collection	Common Form ICR:  No
Type of Review Request: Delegated
OIRA Conclusion Action: Approved without change	Conclusion Date: 09/28/2011
	Date Received in OIRA: 09/28/2011
Terms of Clearance:

	Inventory as of this Action	Requested	Previously Approved
Expiration Date	09/30/2014	36 Months From Approved	10/31/2011
Responses	226,384	0	226,398
Time Burden (Hours)	3,259	0	3,273
Cost Burden (Dollars)	0	0	0

---

Abstract: In 2003, the Commission modified 47 C.F.R. Section 20.18(l) to further improve the ability of public safety answering points (PSAPs) to respond quickly and efficiently to calls for emergency assistance made from non-service initialized wireless mobile handsets. Non-service-initialized wireless mobile handsets (non-initialized handsets) are not registered for service with any Commercial Mobile Radio Service (CMRS) licensee. A non-initialized handset lacks a dialable number, but is programmed to make outgoing 911 calls. The Commission addressed issues arising from the inability of a PSAP operator to call back a 911 caller who becomes disconnected when using a non-service-initialized wireless handset. These requirements also apply to manufacturers of 911-only handsets that are manufactured after May 3, 2004.

---

Authorizing Statute(s): US Code: 47 USC 332 Name of Law: Communications Act of 1934, as amended
   US Code: 47 USC 154 Name of Law: Communications Act of 1934, as amended
   US Code: 47 USC 160 Name of Law: Communications Act of 1934, as amended
   US Code: 47 USC 201 Name of Law: Communications Act of 1934, as amended
   US Code: 47 USC 251-254 Name of Law: Communications Act of 1934, as amended
   US Code: 47 USC 303 Name of Law: Communications Act of 1934, as amended
  

Citations for New Statutory Requirements: None

---

Associated Rulemaking Information
RIN:	Stage of Rulemaking:	Federal Register Citation:	Date:
	Not associated with rulemaking

---

Federal Register Notices & Comments
60-day Notice:	Federal Register Citation:	Citation Date:
	76 FR 45569	07/29/2011
30-day Notice:	Federal Register Citation:	Citation Date:
	76 FR 45569	07/29/2011
Did the Agency receive public comments on this ICR? No

---

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

IC Title	Form No.	Form Name
911 Callback Capability; Non-initialized Handsets
added state, local or tribal government as a respondent

---

ICR Summary of Burden

	Total Approved	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	226,384	226,398	0	0	-14	0
Annual Time Burden (Hours)	3,259	3,273	0	0	-14	0
Annual Cost Burden (Dollars)	0	0	0	0	0	0

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

Burden Increase Due to:

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

Burden Reduction Due to:

Short Statement: The Commission is adding state, local or tribal government as a respondent pool which was inadvertently omitted in ROCIS in the previous submission. The Commission is seeking an extension under delegated authority for this IC. We are reporting a decrease of 14 respondents/responses and hours.

---

Annual Cost to Federal Government: $0

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: 09/28/2011

---