Docstoc

Secure Flight

Document Sample
Secure Flight Powered By Docstoc
					          Airlines Reporting Corporation (ARC)
10th Annual Corporate Travel Department (CTD) Conference
                    November 11, 2010
Agenda
  Why Secure Flight?
  Secure Flight Mission and Scope
  Program Timeline and Deployment Status
  Passenger Data Requirements
  November 1, 2010 Enforcement
  Secure Flight Process and Timing
  Providing Redress and Ensuring Privacy




                                            2
Why Secure Flight?
  Enhances the security of commercial air travel
  Improves the watch list matching process, resulting in fewer
   misidentified passengers
  Decrease chance for compromised watch list by limiting distribution
  Expedites law enforcement notification by gaining earlier insight to
   potential matches
  Provides fair and consistent watch list matching across all airlines
  Facilitates an expedited and integrated redress process
   for misidentified passengers


                                                                          3
Secure Flight Mission
 The mission of the Secure Flight program is to enhance the
 security of domestic and international commercial air travel in the
 United States through the use of improved watch list matching.

 The program’s goals are to:
    Identify known and suspected terrorists
    Prevent individuals on the No Fly List from boarding an aircraft
    Identify individuals on the Selectee List for enhanced screening
    Facilitate passenger air travel
    Protect individuals’ privacy



                                                                        4
Secure Flight Scope
  Applies to passengers traveling on covered airline flights:
     Into, out of, or within the United States and its territories
     Over the continental United States*
     Between two international points (if operated by a U.S. airline)
  Also applies to non-traveling individuals seeking authorization to enter
   the sterile area of a U.S. airport
  Secure Flight screens more than 2 million daily enplanements




*Note: The implementation of Secure Flight for overflights has been deferred to a future
date, after full cutover of domestic and foreign airlines is complete. DHS will provide the
airlines advance notification of the implementation date, once it has been determined.
                                                                                              5
Program Timeline
 October 28, 2008:    The Secure Flight Final Rule was published in the Federal
   Register, and went into effect on December 29, 2008

 January 2009:     Secure Flight began implementation with volunteer aircraft
   operators

 August 15, 2009:      Aircraft operators are required to request Secure Flight
   Passenger Data (SFPD) ― full name, gender, date of birth, and Redress number
   (if available) ― for flights within the United States

 October 31, 2009:      All aircraft operators are required to request full SFPD on all
   covered flights (into, out of, and within the United States)

 June 22, 2010: All U.S. aircraft operators fully cutover
 November 1, 2010: Secure Flight will no longer process incomplete SFPD
 Deployments for covered foreign air carriers will continue through 2010
                                                                                           6
Deployment Status
 Secure Flight deployment as of November 5, 2010:

                                                                                                Cutover

U.S. Aircraft Operators                                                                              69*
Foreign Air Carriers                                                                               110**
Total                                                                                                179
* Includes three new U.S. aircraft operators that started service this year and have cutover to Secure Flight.
** Includes one new foreign air carrier that started service to the United States this year and has cutover to Secure Flight.

  Currently conducting watch list matching for over 98 percent of the
   total passenger volume covered by the Secure Flight Final Rule
  On schedule for full implementation of remaining foreign air carriers
   by December 2010
                                                                                                                                7
Passenger Data Requirements
 Under Secure Flight, passengers must provide the following Secure
 Flight Passenger Data (SFPD) for the airlines to submit to TSA.
    Full name (as it appears on the government-issued identification the
     passenger plans to use when traveling)
    Date of birth
    Gender
    Redress Number (if available)


 NOTE: Secure Flight also receives passengers’ itinerary information
 and, if available, certain passport information (passport number, country
 of issuance, and expiration date) from the airline.
                                                                             8
November 1 Enforcement
  As of November 1, 2010, aircraft operators will not receive a boarding
   pass printing result until full Secure Flight Passenger Data (SFPD) is
   submitted for watch list matching:
        Full name (as it appears on the government-issued identification
         the passenger plans to use when traveling)
        Date of birth
        Gender


  Currently, over 94 % of aircraft operator submissions contain full SFPD



                                                                             9
Secure Flight Process

                Passenger                    Airline sends
                   sends                      passenger
                reservation                 data to Secure
               data to airline                    Flight



   Passenger                     Airline                        TSA Secure
                                                                  Flight
                Airline prints               Secure Flight
                  boarding                 sends boarding
                  pass for                   pass printing
                 passenger                 results to airline




                                                                             10
 Secure Flight Timing
SFPD is received 72 hours prior to flight to provide early watch list matching
results to airlines.                                    Check-in for Flight
                 72 Hours                                      24 Hours prior
               prior to Flight                                                               Flight Departs
                                                                  to Flight

                                   Airlines Submit SFPD to
 Airline                                 Secure Flight
 Submissions                                                                 Real-time SFPD from
                                                                                    Airlines


                        Automated
                                              Manual Review
  Watch List             Matching
  Matching                                                                  Airport Resolution
                                                                                (if needed)


  Secure Flight                            Boarding Pass Printing Results Sent to Airlines

  Responses                      Unsolicited Updates Sent to Airlines for Changes in Passenger Status

                                                                                                              11
Traveler Redress Inquiry Program (TRIP)
Passengers may apply for redress if they believe they have been misidentified as
an individual on the watch list. Apply at www.dhs.gov/trip.
IMPORTANT: When travelling, the passenger reservation must have the same full
name, DOB, and gender that they used when they applied for TRIP.
IMPORTANT: Redress numbers are provided upon DHS receipt of redress
application but are not effective until DHS TRIP investigates and determines that
the person should be Cleared.




                                                                                    12
 Ensuring Privacy
 TSA has developed a comprehensive privacy plan to incorporate                                     Privacy Risk
                                                                                                    Management
  privacy laws and practices into all areas of Secure Flight                                  Redress &
                                                                                              Response

 TSA will collect the minimum amount of personal information                        Monitoring &
                                                                                     Compliance
  necessary to conduct effective watch list matching
                                                                              Awareness &
                                                                                Training
 The only required data elements for the Secure Flight                  Systems
  mission are full name, date of birth, gender, and                    Development
                                                                        & Security
  itinerary
                                                                  Policy

 TSA will retain personal information for the         Organization
  minimum amount of time necessary

 TSA issued a Privacy Impact Assessment
  (PIA) and System of Records Notice (SORN)                                          Secure Flight privacy
  to provide detailed information about the                                          approach is rooted in
  program's privacy approach in conjunction         Foundational                       Fair Information
  with the Secure Flight Final Rule              Privacy Principles
                                                                                           Practices

                                                                                                                   13

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:9/7/2012
language:
pages:14