Maryland-3 Airports: Enahnced Security Procedures at Certain Airports in the Washington, DC Area

Forms and Documents

Forms and supporting documents for this ICR

Document	Type	Status	Availability
Form TSA FORM 418 PIN Application Process	Form	New	Available
Maryland-3 30 Day Notice.pdf	Supplementary Document	Uploaded 2008-11-28	Available
MD3 PRA Supporting Statement1.doc	Supporting Statement A	Uploaded 2008-11-28	Available
OMB 1652-0029 Maryland3 Airports PRA 60DY RenewNotice 20080902 Publ (73 FR 51313).pdf	Supplementary Document	Uploaded 2008-11-13	Available
49 Part 1562.doc	Supplementary Document	Uploaded 2008-11-13	Available

IC Document Collections

Information collection document groups

IC ID	Collection	Type	Status	Form
20956	Maryland-3 Airports: Enahnced Security Procedures at Certain Airports in the Washington, DC Area		Removed
187318	PIN Application Process	Form	New

ICR Details

OMB Control No: 1652-0029	ICR Reference No: 200811-1652-001
Status: Historical Active	Previous ICR Reference No: 200509-1652-001
Agency/Subagency: DHS/TSA	Agency Tracking No:
Title: Maryland-3 Airports: Enahnced Security Procedures at Certain Airports in the Washington, DC Area
Type of Information Collection: Revision of a currently approved collection	Common Form ICR:  No
Type of Review Request: Regular
OIRA Conclusion Action: Approved without change	Conclusion Date: 03/06/2009
	Date Received in OIRA: 11/28/2008
Terms of Clearance:

table that charts list comparision

	Inventory as of this Action	Requested	Previously Approved
Expiration Date	03/31/2012	36 Months From Approved	03/31/2009
Responses	400	0	400
Time Burden (Hours)	1,166	0	1,172
Cost Burden (Dollars)	41,200	0	41,200,000

---

Abstract: The rule establishing this collection requires the establishment of security measures that permit normal flight operations to resume at the Maryland-3 airports (College Park Airport (CGS), Potomac Airfield (VKX), and Washington Executive/Hyde Field (W32)). To that end, TSA requires applicants seeking to fly to or from one of the Maryland-3 airports to submit personal information and fingerprints so that TSA can issue a personal identification number (PIN) and the FBI can conduct security threat assessments.

---

Authorizing Statute(s): US Code: 49 USC 49 Name of Law: Transportation
  

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:
	73 FR 51313	09/02/2008
30-day Notice:	Federal Register Citation:	Citation Date:
	73 FR 72499	11/28/2008
Did the Agency receive public comments on this ICR? No

---

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

table that charts list of burden

IC Title	Form No.	Form Name
Maryland-3 Airports: Enahnced Security Procedures at Certain Airports in the Washington, DC Area
PIN Application Process	TSA FORM 418	MD-3 PIN APPLICATION

---

ICR Summary of Burden

table that charts list 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	400	400	0	0	0	0
Annual Time Burden (Hours)	1,166	1,172	0	-6	0	0
Annual Cost Burden (Dollars)	41,200	41,200,000	0	-41,158,800	0	0

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

Burden Increase Due to: Miscellaneous Actions

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

Burden Reduction Due to: Using Information Technology

Short Statement: There is a slight decrease in burden hours due to the availability of the form electronically. A correction has also been posted in regards to the Annual Burden Cost from the previous submission, which shows there has been adjustment, not a correction. The previously approved Annual Burden Cost is incorrect

---

Annual Cost to Federal Government: $33,469

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]? Uncollected

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

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

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: 11/28/2008

---