30-Day Notice

79066

Federal Register / Vol. 80, No. 243 / Friday, December 18, 2015 / Notices

critical assets without visitor escorts or
without the background checks listed in
RBPS 12 under exceptional
circumstances (e.g., foreseeable but
unpredictable circumstances)? If so,
who? If so, which exceptional
circumstances would warrant access
without visitor escorts or without the
background checks listed in RBPS 12?
2. With Regard to Option 1
• How will notice be provided to
affected individuals that information is
being provided to the Department?

mstockstill on DSK4VPTVN1PROD with NOTICES

3. With Regard to Option 2
• How will notice be provided to
affected individuals that information is
being provided to the Department?
• What will the facility do if NPPD is
unable to verify an affected individual’s
enrollment in another Department TSDB
vetting program?
• What will be the timeframe for this
follow-on action?
• What will the facility do if NPPD
does verify the credential, but later
during a periodic re-verification, is
unable verify the credential?
• What will be the timeframe for this
follow-on action?
• Does the facility describe how it
will comply with RBPS 12(iv) for
affected individuals without credentials
capable of being verified under Option
2?
4. With Regard to Option 3
• How will the facility identify those
affected individuals who possess
TWICs?
• How will the facility comply with
RBPS 12(iv) for affected individuals
without TWICs?
• How will the facility electronically
verify and validate TWICs of affected
individuals?
• Which reader(s) or Physical Access
Control System (PACS) will the facility
be using? Or, if it is not using readers,
how it will use the CCL or CRL?
• Where will the reader(s) or PAC(s)
be located?
• What mode or modes (i.e., which
setting on the TWIC Reader) will be
used when verifying and validating the
TWIC of an affected individual? 27
• Will the TWIC of an affected
individual be re-verified and revalidated with TWIC readers, and, if so,
how often?
• What will the facility (or
designee(s)) do if an affected
individual’s TWIC cannot be verified or
if the TWIC reader is not functioning
properly?
27 See table 4.1 on page 18 of the TSA reader
specification at (http://www.tsa.gov/sites/default/
files/publications/pdf/twic/twic_reader_card_app_
spec.pdf).

VerDate Sep<11>2014

19:20 Dec 17, 2015

Jkt 238001

5. With Regard to Option 4
• Upon which Federal screening
program(s) does the facility or designee
intend to rely?
• What document(s) or credential(s)
issued by the Federal screening
program(s) will the facility visually
verify?
• What procedures will the facility
use to allow affected individuals to
present document(s) or credential(s)?
• How will the facility verify that the
credential or document presented by
affected individuals is not fraudulent?
• What procedures will the facility
follow to visually verify that a
credential or document is current and
valid (i.e., not expired)?
• Will the visual verification include
the following?
Æ Comparing any picture on a
document or credential to the bearer of
the credential or document;
Æ Comparing any physical
characteristics listed on the credential
or document (e.g., height, hair color, eye
color) with the bearer’s physical
appearance;
Æ Checking for tampering;
Æ Reviewing both sides of the
credential or document and checking for
the appropriate stock/credential
material;
Æ Checking for an expiration date;
and
Æ Checking for any insignia,
watermark, hologram, signature or other
unique feature.
• What will the facility do if it is
unable to visually verify an affected
individual’s credential or document, if
the credential or document fails visual
verification, or if the credential or
document appears invalid, expired, or
fraudulent?
6. With Regard to Other Options
• A facility that chooses to propose
an option not listed above in its SSP
should provide as much detail as
possible to allow the Department to
consider the potential option and
evaluate whether or not it meets the
RBPS 12(iv) standard.
Caitlin Durkovich,
Assistant Secretary, Office of Infrastructure
Protection, National Protection and Programs
Directorate, U.S. Department of Homeland
Security.
[FR Doc. 2015–31625 Filed 12–17–15; 8:45 am]
BILLING CODE 9110–9P–P

PO 00000

Frm 00039

Fmt 4703

Sfmt 4703

DEPARTMENT OF HOMELAND
SECURITY
Transportation Security Administration
Extension of Agency Information
Collection Activity Under OMB Review:
Airport Security
Transportation Security
Administration, DHS.
ACTION: 30-day notice.
AGENCY:

This notice announces that
the Transportation Security
Administration (TSA) has forwarded the
Information Collection Request (ICR),
Office of Management and Budget
(OMB) control number 1652–0002,
abstracted below to OMB for review and
approval of a revision of the currently
approved collection under the
Paperwork Reduction Act (PRA). TSA is
combining two previously-approved
ICRs (1652–0002 and 1652–0006,
Employment Standards) into this single
request to simplify TSA collections,
increase transparency, and reduce
duplication.1 The ICR describes the
nature of the information collection and
its expected burden. TSA published a
Federal Register notice, with a 60-day
comment period soliciting comments, of
the following collection of information
on September 1, 2015, 80 FR 52778. The
collection involves implementing
certain provisions of the Aviation and
Transportation Security Act and 49
U.S.C. chapter 449 that relate to
providing for the safety and security of
persons and property on an aircraft
operating in air transportation or
intrastate air transportation against an
act of criminal violence, aircraft piracy,
and the introduction of an unauthorized
weapon, explosive, or incendiary onto
an aircraft.
DATES: Send your comments by January
19, 2016. A comment to OMB is most
effective if OMB receives it within 30
days of publication.
ADDRESSES: Interested persons are
invited to submit written comments on
the proposed information collection to
the Office of Information and Regulatory
Affairs, OMB. Comments should be
addressed to Desk Officer, Department
of Homeland Security/TSA, and sent via
SUMMARY:

1 After the publication of the 60 day notice, TSA
decided to include in OMB control number 1652–
0002, Airport Security, 49 CFR part 1542, the
recordkeeping requirements under OMB Control
Number 1652–0006 Employment Standards, which
apply to 49 CFR part 1542. This would reduce
duplication and combine information collected
under the same statute, 49 CFR part 1542. Upon
OMB approval of this revision, TSA intends to
discontinue OMB Control Number 1652–0006
Employment Standards.

E:\FR\FM\18DEN1.SGM

18DEN1

Federal Register / Vol. 80, No. 243 / Friday, December 18, 2015 / Notices
electronic mail to oira_submission@
omb.eop.gov or faxed to (202) 395–6974.
FOR FURTHER INFORMATION CONTACT:
Christina A. Walsh, TSA PRA Officer,
Office of Information Technology (OIT),
TSA–11, Transportation Security
Administration, 601 South 12th Street,
Arlington, VA 20598–6011; telephone
(571) 227–2062; email TSAPRA@
tsa.dhs.gov.
SUPPLEMENTARY INFORMATION:

Comments Invited
In accordance with the Paperwork
Reduction Act of 1995 (44 U.S.C. 3501
et seq.), an agency may not conduct or
sponsor, and a person is not required to
respond to, a collection of information
unless it displays a valid OMB control
number. The ICR documentation is
available at http://www.reginfo.gov.
Therefore, in preparation for OMB
review and approval of the following
information collection, TSA is soliciting
comments to—
(1) Evaluate whether the proposed
information requirement is necessary for
the proper performance of the functions
of the agency, including whether the
information will have practical utility;
(2) Evaluate the accuracy of the
agency’s estimate of the burden;
(3) Enhance the quality, utility, and
clarity of the information to be
collected; and
(4) Minimize the burden of the
collection of information on those who
are to respond, including using
appropriate automated, electronic,
mechanical, or other technological
collection techniques or other forms of
information technology.

mstockstill on DSK4VPTVN1PROD with NOTICES

Information Collection
Title: Airport Security, 49 CFR part
1542.
Type of Request: Revision of a
currently approved collection.
OMB Control Number: 1652–0002.
Forms(s): NA.
Affected Public: Airport operators
regulated under 49 CFR part 1542.
Abstract: TSA is seeking to revise its
OMB control number 1652–0002,
Airport Security, 49 CFR part 1542 to
include the recordkeeping requirements
under OMB control number 1652–0006,
Employment Standards. The
information collection is used to
determine compliance with 49 CFR part
1542 and to ensure passenger safety and
security by verifying airport operator
compliance with security procedures.
The following information collections
and other recordkeeping requirements
with which respondent airport operators
must comply also fall under this OMB
control number: (1) Development of an

VerDate Sep<11>2014

19:20 Dec 17, 2015

Jkt 238001

Airport Security Program (ASP),
submission to TSA, and ASP
implementation; (2) as applicable,
development of ASP amendments,
submission to TSA, and
implementation; (3) collection of data
necessary to complete a criminal history
records check (CHRC) for those
individuals with unescorted access to a
Security Identification Display Area
(SIDA); (4) submission to TSA of
identifying information about
individuals to whom the airport
operator has issued identification
media, such as name, address, and
country of birth, in order for TSA to
conduct a Security Threat Assessment
(STA); (5) recordkeeping requirements
associated with records required for
compliance with the regulation, and for
compliance with Security Directives
(SDs); and (6) watch list matching of
individuals subject to TSA’s regulatory
requirements against government watch
lists.
This information collection is
mandatory for airport operators. As part
of their security programs, affected
airport operators are required to
maintain and update, as necessary,
records of compliance with the security
program provisions set forth in 49 CFR
part 1542. This regulation also requires
affected airport operators to make their
security programs and associated
records available for inspection and
copying by TSA to verify compliance
with transportation security regulations.
Number of Respondents: 438.
Estimated Annual Burden Hours: An
estimated 1,657,102 hours annually.
Dated: December 9, 2015.
Christina A. Walsh,
TSA Paperwork Reduction Act Officer, Office
of Information Technology.
[FR Doc. 2015–31913 Filed 12–17–15; 8:45 am]
BILLING CODE 9110–05–P

DEPARTMENT OF HOMELAND
SECURITY
Transportation Security Administration
[Docket No. TSA–2007–28572]

Revision of Agency Information
Collection Activity Under OMB Review:
Secure Flight Program
Transportation Security
Administration, DHS.
ACTION: 30-day notice.
AGENCY:

This notice announces that
the Transportation Security
Administration (TSA) has forwarded the
Information Collection Request (ICR),
Office of Management and Budget
(OMB) control number 1652–0046,

SUMMARY:

PO 00000

Frm 00040

Fmt 4703

Sfmt 4703

79067

abstracted below to OMB for review and
approval of a revision to the currently
approved collection under the
Paperwork Reduction Act (PRA). The
ICR describes the nature of the
information collection and its expected
burden. TSA published a Federal
Register notice, with a 60-day comment
period soliciting comments, of the
following collection of information on
February 4, 2015, 80 FR 6097. The
collection involves information that
certain U.S. aircraft operators and
foreign air carriers (collectively
‘‘covered aircraft operators’’) submit to
Secure Flight for the purposes of
identifying and protecting against
potential and actual threats to
transportation security and identifying
individuals who are a lower risk to
transportation security and therefore
may be eligible for expedited screening.
TSA is revising this collection to
include the addition of risk-based
assessments generated by aircraft
operators using data in their Computer
Assisted Passenger Prescreening
Systems (CAPPS), Frequent Flyer Code
Words (FFCWs) generated by aircraft
operators, and the collection of lists of
low-risk individuals provided by nonfederal entities who are eligible for
expedited screening. The CAPPS
assessments and FFCWs are used in
risk-based analysis of Secure Flight and
other prescreening data that produces a
boarding pass printing result (BPPR) for
each passenger.
DATES: Send your comments by January
19, 2016. A comment to OMB is most
effective if OMB receives it within 30
days of publication.
ADDRESSES: Interested persons are
invited to submit written comments on
the proposed information collection to
the Office of Information and Regulatory
Affairs, OMB. Comments should be
addressed to Desk Officer, Department
of Homeland Security/TSA, and sent via
electronic mail to oira_submission@
omb.eop.gov or faxed to (202) 395–6974.
FOR FURTHER INFORMATION CONTACT:
Christina A. Walsh, TSA PRA Officer,
Office of Information Technology (OIT),
TSA–11, Transportation Security
Administration, 601 South 12th Street,
Arlington, VA 20598–6011; telephone
(571) 227–2062; email TSAPRA@
tsa.dhs.gov.
SUPPLEMENTARY INFORMATION:
Comments Invited
In accordance with the Paperwork
Reduction Act of 1995 (44 U.S.C. 3501
et seq.), an agency may not conduct or
sponsor, and a person is not required to
respond to, a collection of information
unless it displays a valid OMB control

E:\FR\FM\18DEN1.SGM

18DEN1