Scenario 1:

Adverse actions premised on factually incorrect antecedents

John Day is stopped at airport because his name matches TSDB. However, when the antecedents are checked, it turns out that his DOB is not a match. (It is similar enough that it was probably fuzzy matched.)

Description:

This transaction log is

from the Transportation Security Administration

which is part of the Department of Homeland Security

which is part of the Executive Branch

which is part of the US Government

Receive PNR data

from American Airlines

About John Henry Doe

DOB: 8/24/57

Who traveled on flight

no. 723

from New York (LaGuardia)

to Chicago (O'Hare)

on 6/14/04

This data is automatically

matched against other data

from three sources

the matching ("search") query is looking for

a person named John Henry Dae

with a DOB of 8/24/75

The result of the first match

which was from the Terrorist Screening Database

was the finding of a person named John Henry Doe

with a DOB of 8/24/75

The result of the second match

which was from the LexisNexis database

was the finding of a person named John Henry Doe

who is associated with the address 123 Main , New York, NY 10044

with a DOB of 8/24/75

The result of the third match

which was from the LexisNexis database

was the finding of a person named John Henry Doe

who is associated with the address 723 High Street, Seattle, WA 98104

with a DOB of 8/24/75.

Because there may be a match,

the system displays the information to

Rafael Fajardo

an Inspector

employed by TSA in Queens, NY

working at LaGuardia Airport.

Inspector Fajardo

stops

John Henry Doe

for a secondary inspection

Mr. Doe asks the system "why" he is stopped