Secure Flight

ICR 201906-1652-003

OMB: 1652-0046

Federal Form Document

Forms and Documents
Document
Name
Status
Supplementary Document
2019-06-10
Supplementary Document
2019-06-10
Supplementary Document
2019-06-10
Supplementary Document
2019-06-10
Supplementary Document
2016-01-27
Supplementary Document
2016-01-26
Supplementary Document
2016-01-26
Supporting Statement A
2019-06-12
Supplementary Document
2019-06-10
Supplementary Document
2019-06-10
Supplementary Document
2007-06-18
IC Document Collections
IC ID
Document
Title
Status
236389
New
236388
New
236386
New
200232
Modified
200231
Removed
200230
Modified
180751
Removed
ICR Details
1652-0046 201906-1652-003
Active 201601-1652-005
DHS/TSA
Secure Flight
Extension without change of a currently approved collection   No
Regular
Approved without change 04/22/2020
Retrieve Notice of Action (NOA) 07/31/2019
  Inventory as of this Action Requested Previously Approved
04/30/2023 36 Months From Approved 04/30/2020
5,216,893 0 97,668,001
67,125 0 678,295
6,818,957 0 4,592,058

The Transportation Security Administration is proposing to collect information from covered U.S. aircraft operators and foreign air carriers in order to begin implementation of the Secure Flight Program. The collection would cover passenger reservation data for covered domestic and international flights. The collection would also cover the collection from covered aircraft operators of certain identifying information for non-traveling individuals that the aircraft operators seek to authorize to enter a sterile area, i.e. to escort a minor or a passenger with disabilities or for another approved purpose.

PL: Pub.L. 108 - 458 4012 Name of Law: Intelligence Reform and Terrorism Prevention Act
  
US Code: 49 USC 1540 Name of Law: Transportation Security Administration

Not associated with rulemaking

  83 FR 62880 12/06/2018
84 FR 23063 05/21/2019
No

  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 5,216,893 97,668,001 0 -97,667,844 5,216,736 0
Annual Time Burden (Hours) 67,125 678,295 0 -678,249 67,079 0
Annual Cost Burden (Dollars) 6,818,957 4,592,058 0 -4,566,864 6,793,763 0
No
Yes
Miscellaneous Actions
The changes reflect additional aircraft operators that have migrated to Secure Flight as covered carriers. The total number of covered Secure Flight carriers has grown from 211 in 2011 to 262 covered carriers in 2015 and from 262 in 2015 to 323 in 2018. Going forward, TSA also anticipates 15 to 20 new covered aircraft operators to cutover to Secure Flight annually. The changes also cover the transmission of lists of low-risk passengers who are eligible for expedited screening that are received from non-federal entities. The changes also reflect: • In 2018, via a security program amendment, TSA ended the Airport Sterile Area Access Pass Program (ASAAPP). Previously, in 2016, ASAAPP had replaced the Airport Access Authorization to Commercial Establishments (AAACE) Beyond the Screening Checkpoint pilot, which was implemented in 2011. • Increased requests for Gate Passes by covered airlines and aircraft operators for individuals seeking access to the sterile areas. • TSA’s phase out of the use of the Frequent Flier Code Word (FFCW) and the CAPPS Assessment sent by the covered airlines.  

$110,219
No
    Yes
    Yes
No
No
No
Uncollected
Christina Walsh 571 227-2062 christina.walsh@tsa.dhs.gov

  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:
 
 
 
 
 
 
 
    (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;
 
 
 
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.
07/31/2019


© 2024 OMB.report | Privacy Policy