Civic / Privacy / Digital Rights
Detecting Mal-Intent Before an Attack: FAST, SPOT, Quiet Skies, Secure Flight, and U.S. Traveler-Risk Analytics
Report summary
The central finding of this investigation is that the United States has operated several very different kinds of aviation-security systems under the overlapping language of “risk,” “behavior,” “intent,” “vetting,” and “threat detection.” Treating them as one technological capability produces a misle
Key topics
- Civic / Privacy / Digital Rights
- Civic
- Privacy
- Digital Rights
- Runtime
- Research Archive
- Strategy
- Audit
- Architecture
Research provenance
For citation, use the report title and canonical URL. Archival presence does not establish authorship or promote report statements into portfolio evidence.
Source availability: 138 citation markers in the source export have no recoverable source links. Those markers are omitted from this reader; any supplied bibliography and ordinary links remain. Check the original sources before relying on the cited claims.
This page renders the archived Markdown as safe, formatted HTML. It is background research and does not become a portfolio claim without evidence review.
Full report
On this page
Executive findings and analytical framework
The central finding of this investigation is that the United States has operated several very different kinds of aviation-security systems under the overlapping language of “risk,” “behavior,” “intent,” “vetting,” and “threat detection.” Treating them as one technological capability produces a misleading picture.
Secure Flight is principally an identity-resolution and screening-allocation system. It compares passenger biographical and itinerary data with watchlists and other high- and low-risk lists, then communicates a boarding or checkpoint-screening status. CBP’s Automated Targeting System, including its Unified Passenger interface, is a broader border-enforcement decision-support platform that combines passenger manifests, reservation records, prior encounters, watchlists, intelligence and rule-based indicators to prioritize travelers for review. Silent Partner and Quiet Skies used ATS-derived travel rules to identify non-watchlisted passengers for enhanced screening and, in Quiet Skies cases, sometimes Federal Air Marshal surveillance. SPOT and its successors attempted to infer risk from observable conduct. FAST went furthest conceptually: it was research intended to infer “malintent” from remotely sensed physiological and behavioral responses. Only the last two categories claimed, even indirectly, to detect an internal hostile state from a person’s current presentation.
That distinction produces five major conclusions.
First, FAST never became an operational passenger-screening system on the public record. It passed through laboratory research, controlled experiments, prototype development and limited field-assessment planning. DHS documents described goals, prototypes and successful research “events,” but those descriptions do not establish that FAST screened ordinary airline passengers for real-world security decisions. Its publicly documented lineage continued under names including “Passive Methods for Precision Behavioral Screening” and “Passively Activated Screening System,” but no authoritative public notice identifies an operational deployment or a precise termination date.
Second, SPOT was unquestionably operational, not merely research. TSA tested it beginning in October 2003, expanded it nationally from fiscal year 2007, employed thousands of dedicated Behavior Detection Officers, and spent roughly $900 million through the period GAO examined. Yet its most complete public outcome data showed arrests overwhelmingly associated with ordinary law-enforcement matters such as warrants, immigration violations, false documents, drugs and currency—not detection of terrorists preparing to attack aviation. GAO found that the scientific evidence did not establish that TSA’s indicators could reliably identify aviation threats.
Third, ending the standalone SPOT workforce did not end behavior detection. TSA eliminated the dedicated Behavior Detection Officer position in fiscal year 2017 and integrated former officers into the general screening workforce. As of November 30, 2021, approximately 3,730 officers remained qualified to conduct behavior-detection activities; TSA updated its behavior-detection operating procedures in May 2022. Referral rates fell sharply—from 13,187 referrals in 2016 to 506 in 2018—but the underlying function survived the organizational termination.
Fourth, Quiet Skies was an operational rule-based surveillance and screening program, not a sensor that detected intent. It identified some passengers who were not on a terrorist watchlist through travel-related rules, assigned enhanced screening, and from March 2018 sometimes caused Federal Air Marshals to follow and observe passengers on flights. TSA did not establish a comprehensive effectiveness measure, did not systematically connect marshal observations to rule validation, and could not use the absence of attacks as proof that Quiet Skies had prevented them. DHS announced the program’s termination on June 5, 2025, while stating that critical aviation-vetting functions would continue.
Fifth, Secure Flight and ATS remain active, and their core functions are more durable than individual program names. Secure Flight continues to operate continuously and normally receives passenger information within seventy-two hours of travel. ATS and Unified Passenger remain central CBP vetting platforms, integrated with the National Targeting Center and National Vetting Center. The end of Quiet Skies therefore did not eliminate watchlist matching, rules-based international passenger analysis, travel-pattern analysis, identity resolution, or risk-based screening allocation.
What counts as operational capability
This report uses a deliberately restrictive classification:
| Classification | Evidentiary threshold |
|---|---|
| Laboratory research | Controlled experiments involving recruited participants, mock offenses, scripted scenarios or artificial class labels. |
| Field test or assessment | Testing in an operationally realistic location or workflow, but without evidence that outputs became routine government decisions about ordinary travelers. |
| Operational program | Routine processing of real travelers with outputs that affected screening, boarding, inspection, surveillance or resource deployment. |
| Discontinued initiative | The named program or dedicated organizational structure was formally ended, even if component practices survived elsewhere. |
| Active successor or related system | A current system performs materially similar identity, targeting, screening-allocation or surveillance functions, whether or not it retains the earlier name. |
A promotional statement that a system “predicts hostile behavior,” a research accuracy figure from a balanced mock-crime experiment, or an allegation made in a congressional or executive-branch dispute is not treated as evidence that the capability worked operationally. Likewise, an arrest following a referral is not counted as a hostile-intent detection unless the public record connects the arrest to preparation for an aviation attack.
The four fundamentally different questions these systems answer
The programs are best understood as answering different questions:
| Analytic layer | Question actually asked | Representative systems |
|---|---|---|
| Identity and status | Is this traveler the same person as a known or listed individual? | Secure Flight, CAT identity verification, biometric matching |
| Pattern and association | Does the traveler’s record match a rule, intelligence lead, prior encounter or suspicious travel pattern? | ATS, Unified Passenger, Silent Partner, Quiet Skies |
| Observable presentation | Is the traveler behaving in a way officers have been trained to regard as anomalous? | SPOT, Optimized Behavior Detection |
| Inferred internal state | Do physiological and behavioral signals imply an intention to cause harm? | FAST and related passive-methods research |
Only the final layer approaches literal “pre-crime”: the attempted inference of future harmful intention without a known identity match, discovered weapon, completed offense or necessarily articulable external act.
Comparative lifecycle and present status
Comparative lifecycle timeline
| Date | Program development | Evidentiary status |
|---|---|---|
| October 2001 | CBP’s predecessor organization established the first National Targeting Center–Passenger operation following the September 11 attacks. | Operational passenger targeting infrastructure; the exact public launch date of the ATS-P application itself is not clearly stated in available records. |
| October 2003 | TSA began testing what became SPOT. Initial 2003–2004 pilots at New England airports examined operational feasibility rather than scientifically estimating effectiveness. | Field pilots. |
| September 24, 2004 | TSA published privacy notices for the Secure Flight test phase. | Test program and data-system development. |
| 2006 | TSA describes behavior detection as having been introduced under the Behavior Detection and Analysis program. | Operational precursor to nationwide SPOT deployment. |
| Fiscal year 2007 | TSA began nationwide SPOT deployment at forty-two regulated airports. DHS Science and Technology began the research lineage publicly associated with Project Hostile Intent and later FAST. | SPOT operational expansion; FAST research. |
| 2008 | DHS issued its initial FAST privacy assessment, defining “malintent” and describing passive, non-invasive sensing research. | Laboratory/prototype research, not operational passenger screening. |
| October 28, 2008 | TSA issued the Secure Flight Final Rule. | Regulatory authorization for operational transfer of watchlist matching from carriers to TSA. |
| Late January 2009 | Secure Flight began assuming watchlist-matching responsibility for domestic flights from participating airlines. | Initial operational rollout. |
| December 25, 2009 | Attempted destruction of Northwest Flight 253 became a major catalyst for post-watchlist rules-based screening of non-watchlisted passengers. | Policy trigger, not itself a program start date. |
| 2010 | TSA initiated Silent Partner and Quiet Skies-related rules activity. Silent Partner focused on passengers inbound to the United States. | Operational rule development and screening. Exact day not publicly established. |
| June 2010 | Secure Flight had assumed matching for covered domestic and international operations of U.S. carriers. | Major operational transition. |
| November 23, 2010 | Deadline for covered foreign carriers to transmit data and use Secure Flight results. | Full international-carrier implementation milestone. |
| August 2011 | Secure Flight began screening against a Quiet Skies list in a pilot. | Operational pilot affecting traveler screening. |
| December 21, 2011 | DHS published an updated FAST/Passive Methods privacy assessment. | Research protocol and field-test governance; not proof of operational deployment. |
| January 2012 | TSA established a Quiet Skies working group. | Governance transition. |
| April 2012 | Secretary Janet Napolitano approved transition of Quiet Skies from pilot to permanent status; TSA described it as fully operational. | Operational program. Exact day is not disclosed in the public GAO account. |
| May 2012 | TSA limited Silent Partner list use to U.S.-bound flights. | Operational scope change. |
| January 2013 | TSA reorganized behavior-detection administration, moving research and operations into different offices and using “Behavior Detection and Analysis” nomenclature. | Organizational transition; operational behavior detection continued. |
| February 2013 | Internal FAST materials proposed a restart as the “Passively Activated Screening System,” formerly Passive Methods for Precision Behavioral Screening. | R&D renaming/restart proposal, not documented deployment. |
| November 8, 2013 | GAO concluded TSA lacked scientifically validated evidence sufficient to demonstrate SPOT’s effectiveness and recommended limiting future funding. | Major oversight finding. |
| August 2014 | DHS reported an event using the FAST sensor suite in a kiosk to predict hostile behavior. | Research event/field-style assessment; DHS’s description of success does not establish real-world accuracy or operational use. |
| May 26, 2016 | DHS’s public FAST page and associated materials reflected the FAST/Passive Methods for Precision Behavioral Screening lineage. | Last clear public DHS lifecycle marker located; no public termination order found. |
| Fiscal year 2017 | TSA eliminated the standalone Behavior Detection Officer position and integrated personnel into the broader screening workforce. GAO separately found valid support for only eight of thirty-six revised indicators, with no valid evidence for twenty-eight. | Named standalone program discontinued; underlying behavior-detection function continued. |
| March 2018 | FAMS began attempting to place air marshals on as many flights as possible involving Quiet Skies passengers. | Expansion from checkpoint selection to covert in-flight observation/resource deployment. |
| July 28, 2018 | The Boston Globe publicly disclosed detailed Quiet Skies surveillance practices based on leaked documents and interviews. | Public exposure; details require distinction between leaked instructions and officially confirmed public policy. |
| December 11, 2018 | DHS issued the National Vetting Center privacy assessment following the February 2018 presidential national-vetting memorandum. | Active related vetting architecture. |
| April 19, 2019 | TSA issued a Silent Partner and Quiet Skies PIA. | Formal privacy documentation for active programs. |
| November 20, 2019 | GAO reported that TSA lacked a comprehensive measure of Silent Partner and Quiet Skies rule effectiveness. | Major oversight finding. |
| May 2021 | DHS updated the ATS PIA, documenting Unified Passenger as a technology refresh replacing legacy ATS-P interface functionality. | Active successor/interface modernization, not termination of targeting. |
| November 30, 2021 | TSA reported approximately 3,730 officers qualified to make behavior-detection referrals. | Operational successor activity. |
| May 2022 | TSA updated behavior-detection standard operating procedures to reflect integration into the screening workforce. | Behavior detection remained operational after SPOT’s standalone termination. |
| March 31, 2023 | DHS posted an updated Secure Flight PIA page describing continuing screening of passengers and certain non-travelers. | Active operational system. |
| 2024–2025 | CBP documents continued to describe Unified Passenger, ATS, National Targeting Center integration and PNR-based traveler-risk assessment. | Active border and aviation-risk analytics. |
| June 5, 2025 | DHS Secretary Kristi Noem announced termination of Quiet Skies. DHS stated that critical aviation-security vetting functions would continue. | Quiet Skies name and mission ended; broader vetting infrastructure survived. |
| June 2025 | DHS’s privacy library posted a Secure Flight–Silent Partner–Quiet Skies item even after the public termination announcement. | Likely documentation/archive lag or closeout; it does not by itself prove continued Quiet Skies operations. |
| August 2, 2026 | Secure Flight, ATS/Unified Passenger, CBP PNR analysis, National Vetting Center functions and FAMS remain active. Quiet Skies is publicly terminated. The precise independent status of the name “Silent Partner” and the ultimate disposition of FAST are not publicly resolved. | Current status based on available public documentation; classified and Sensitive Security Information gaps remain. |
Program-status table as of August 2, 2026
| Program or function | What it was | Status as of August 2, 2026 | Confidence and unresolved issue |
|---|---|---|---|
| Project Hostile Intent / FAST | DHS S&T research into remotely measured physiological and behavioral indicators associated with “malintent.” | No evidence of operational passenger deployment; apparently inactive or archived research lineage. | High confidence that it was R&D, not an operational airport program. Low confidence in an exact termination date because no public termination notice was located. |
| Passive Methods for Precision Behavioral Screening / PASS | Continuation, reframing or restart of FAST concepts involving passive stimuli and sensor fusion. | No currently documented operational system. | Public records establish continuity of research concepts through at least 2016 but not an acquisition, deployment or formal closeout. |
| SPOT / dedicated Behavior Detection Officers | Operational observation, questioning and referral program. | Standalone program discontinued in fiscal year 2017. | Exact calendar-day termination is not public; the statutory and budget transition is identified by fiscal year. |
| Integrated TSA behavior detection | Trained TSOs observe indicators, ask security questions and can refer passengers for additional screening. | Operational at least through the latest detailed public GAO review; present 2026 scale not publicly disclosed. | Strong evidence of continuation through 2022. Later public reporting does not provide a comprehensive national head count or outcome series. |
| Silent Partner | ATS-supported rules identifying inbound international passengers for enhanced screening. | Independent named status unclear after June 2025; underlying rules-based vetting continues. | DHS announced termination of Quiet Skies, not a clearly severable, independently documented termination of every Silent Partner function. Public evidence is insufficient to say the name remains operational or that all functions ended. |
| Quiet Skies | Subset of Silent Partner identifying some travelers for limited-period enhanced screening and, later, FAMS surveillance. | Terminated June 5, 2025. | High confidence as to named-program termination; lower confidence about how every rule, list or workflow was reassigned. |
| Secure Flight | Central TSA passenger prescreening, watchlist matching and risk-appropriate screening assignment. | Active. | Current official TSA and DHS materials confirm continuing operation. |
| Federal Air Marshal Service | Armed in-flight security, threat-based flight coverage, special missions and investigative support. | Active; Quiet Skies-specific mission ended. | The service’s broader statutory and intelligence-driven deployment functions remain. |
| CBP ATS / ATS-P | Border-enforcement decision-support and passenger-risk targeting using manifests, reservations, encounters, watchlists, intelligence and rules. | Active. | Current PIA appendices and CBP PNR notices confirm continued operation. |
| Unified Passenger / UPAX | Modernized ATS passenger-vetting interface replacing older ATS-P interface functionality. | Active successor interface. | It modernized presentation and workflow rather than ending the underlying targeting functions. |
| National Vetting Center | Interagency framework for centralized vetting against classified and unclassified government information. | Active related architecture. | Not an aviation-only program and not a hostile-intent sensor, but it extends the ecosystem in which traveler information is evaluated. |
| TSA checkpoint biometrics/CAT | Automated identity-document authentication and, in some settings, facial identity verification. | Active and expanding. | These systems establish identity; they should not be conflated with prediction of intent. |
Program architecture, data inputs and decision consequences
FAST and Project Hostile Intent
DHS defined FAST’s target construct as “malintent”: a mental state involving an intention to cause harm to people or infrastructure. Research concepts involved remotely capturing cardiovascular and respiratory activity, facial temperature, eye movements, facial and body motion and vocal features. Some protocols contemplated presenting passive stimuli designed to activate mental representations associated with a planned harmful act, after which a classifier or sensor-fusion system would distinguish a “malintent” participant from a control.
The crucial limitation is that the labels were generated in experiments. Participants assigned to conceal a mock activity were not terrorists; the cost of detection was not imprisonment, death, mission failure or exposure of a real network; and experimenters generally knew the task structure and approximate class balance. A model that separates instructed “malintent” volunteers from controls in a controlled exercise has not thereby learned the physiological signature of an imminent terrorist attack.
Internal materials described a prototype capable of near-real-time off-body screening and concepts under which FAST would recommend accelerated or normal screening. Other documents discussed an airport-related pilot and kiosk testing. Those are meaningful stages of technology maturation, but the public record does not demonstrate routine screening of ordinary travelers or a binding acquisition decision. DHS’s fiscal year 2014 report calling the kiosk event a success is evidence that the event occurred, not that the system achieved transportable sensitivity, specificity or positive predictive value in the airline population.
FAST therefore belongs in the category laboratory research plus limited field-oriented prototype assessment. There is no public denominator showing how many genuine travelers it screened, how many it referred, how many referrals yielded weapons, or how many intended attacks it identified. No public confusion matrix demonstrates performance in a population with a realistic prevalence of hostile actors.
SPOT and integrated behavior detection
SPOT placed trained officers in or near airport screening environments. Officers observed travelers for behavioral indicators, sometimes engaged them in “casual conversation” or security-related questioning, assigned indicator points, and referred persons crossing a threshold for additional physical and baggage screening. Additional observations, document irregularities or discoveries could produce a referral to law enforcement.
Indicators were treated as deviations from an environmental baseline. Public examples have included changes in breathing, swallowing, excessive or unusual movements, apparent nervousness and responses during interaction. Many specific indicators and thresholds remain Sensitive Security Information. TSA’s operational claim was not necessarily that every displayed behavior meant terrorism; rather, clusters of indicators were said to justify additional screening because they could reflect stress, fear or deception associated with malintent. GAO documented an important conceptual inconsistency: at different times DHS characterized the indicators as detecting stress or fear while defending the program as one that identified malintent. These are not equivalent constructs.
When Congress reduced support for the standalone program, TSA did not abolish the observation function. It removed the dedicated job title, transferred thousands of personnel to general screening and retained qualified officers who could make behavior-based referrals. TSA officials told GAO that the activity became predominantly supportive of canine-enhanced screening. As of late 2021, qualification involved a forty-hour course, a knowledge test and twenty-four hours of on-the-job training.
This successor is narrower and produces far fewer referrals than the earlier SPOT structure. GAO found 13,187 referrals in 2016, or 182 per ten million screened passengers, compared with 506 in 2018, or six per ten million. Rates continued to fall through December 2021. This reduction is consistent with both a real contraction of the activity and a change in how referrals were recorded after dedicated officers disappeared.
Silent Partner and Quiet Skies
Silent Partner and Quiet Skies did not infer intent from a traveler’s face or physiology. TSA used CBP’s ATS infrastructure to evaluate international traveler records against intelligence-derived or experience-derived rules. Relevant data could include citizenship, itinerary, route, travel history, timing, reservation information, links or co-travel patterns, prior government encounters and law-enforcement or intelligence information. A match did not mean TSA had formally determined that the person was a terrorist or should be placed in the Terrorist Screening Database. It meant the person’s record matched a rule associated by the government with elevated risk.
Silent Partner primarily identified passengers inbound to the United States for enhanced checkpoint or gate screening. Quiet Skies was a subset that could place a passenger into a limited-duration status affecting later domestic or outbound travel. Secure Flight translated that status into a screening consequence, such as selectee treatment. In that sense, ATS supplied or supported the analytic match, while Secure Flight operationalized the checkpoint result.
From March 2018, Quiet Skies also became a resource-allocation input for FAMS. Investigative reporting based on leaked material described marshals recording whether selected travelers changed appearance, used telephones, went to lavatories, slept, stared, met other people or displayed other listed behaviors. The leaked duration rule was generally up to ninety days or three encounters. Those details are significant, but they should be described as leaked operational guidance corroborated by reporting—not as a complete official account of all versions of the program.
GAO found that FAMS after-action reports often said “nothing to report” or described an incident, but TSA Intelligence and Analysis did not regularly incorporate the reports into systematic rule evaluation. A program that generates covert observations yet does not consistently use those observations to estimate whether the triggering rule was valid has a broken feedback loop.
Secure Flight
Secure Flight requires covered carriers to transmit Secure Flight Passenger Data. Core elements include full name, date of birth, sex or gender information used for matching, itinerary and record-locator data; redress and Known Traveler Numbers are provided when applicable. Passport information and additional carrier data can be available in relevant international or risk-based contexts. Secure Flight compares records against the No Fly and Selectee components of the federal terrorism-screening system and other lists or risk categories authorized for aviation screening.
The principal consequences are:
- Cleared or ordinary screening;
- expedited screening for eligible low-risk populations;
- enhanced or selectee screening;
- inhibited boarding-pass issuance or denial of boarding for a confirmed No Fly determination; and
- resolution activity where the automated process produces a potential match.
A rules-based designation may result in more intensive screening, but TSA has represented that a person is not denied boarding solely because of general risk analysis; a prohibition ordinarily requires a No Fly or other legally operative restriction.
Secure Flight is therefore best described as an identity-matching and screening-orchestration system with added risk-based categorization. It identifies known or listed persons more directly than it predicts conduct. Its error modes include false identity matches, failure to match a listed person, incorrect list data, stale records and mistaken assignment to expanded or rules-based screening categories. GAO found TSA measured some potential and confirmed matches but did not measure every category of missed high-risk person or every false match to expanded and rules-based lists.
Federal Air Marshal surveillance
FAMS’s ordinary mission is not to classify every passenger. It deploys a scarce armed workforce to selected flights, using threat information, route risk, intelligence requirements and statutory priorities. Quiet Skies temporarily added a particular kind of trigger: the presence of a non-watchlisted passenger selected by a rules-based program.
This distinction matters when evaluating “detection.” An air marshal who observes a person and reports no suspicious activity has not validated the rule that selected the person. A marshal who notices an ordinary crime or disruptive act has not necessarily detected pre-attack terrorism. And an uneventful flight may mean the traveler was harmless, deterred, aware of surveillance, not yet operational, or selected by an overbroad rule. Without comparison groups and prespecified outcome definitions, none of those interpretations can be chosen empirically.
Quiet Skies’ termination ended that named special-mission trigger, according to DHS. It did not terminate FAMS, nor did it prevent FAMS from using watchlist information, intelligence leads, specific threats or broader risk-based flight-selection methods.
CBP Automated Targeting System and Unified Passenger
ATS-P has long been a web-based enforcement and decision-support tool. It applies rules and analyst review to Advance Passenger Information System data, Passenger Name Records and government holdings. APIS supplies manifest and identity data; PNR can contain itinerary, reservation dates, contact information, ticketing and payment information, travel-agency details, frequent-flyer fields, seat and baggage information, special-service requests and information linking travelers in the same reservation. ATS also connects to law-enforcement, immigration, watchlist and prior-encounter data.
Rules reflect intelligence, known smuggling or terrorist methods, suspicious trends and officer experience. ATS produces a relative risk assessment, alert, link or targeting result. Analysts at the National Targeting Center and officers at ports use that result to decide whether to conduct further vetting, issue instructions or recommendations, or refer a traveler for secondary inspection. GAO has emphasized that these tools augment rather than legally replace officer judgment.
Unified Passenger, or UPAX, is a technology refresh that replaces older ATS-P interface functionality. It does not represent abandonment of the ATS targeting model. CBP’s 2024–2028 information-technology strategy describes it as integrated with ATS and the National Vetting Center, including automation of traveler-vetting work.
ATS differs from FAST in three decisive ways. It does not need to claim that a person’s physiology discloses intent. Its features generally correspond to recorded facts, associations, government encounters or travel patterns. And its primary consequence is prioritization for human review or border inspection, not a scientific diagnosis of an internal mental state. Its legitimacy and accuracy nevertheless depend on rule quality, source-data quality, feedback loops, disparate effects and meaningful auditability.
Data-input and decision-consequence matrix
| Program | Observable behavior | Travel and reservation patterns | Identity/watchlists | Associations and prior encounters | Biometrics or physiology | Rule/statistical processing | Immediate consequence | What the system actually determines |
|---|---|---|---|---|---|---|---|---|
| FAST | Yes | Generally not central | Could be used in a larger workflow, but not the research core | Not central to disclosed construct | Cardiovascular, respiratory, facial temperature, eye, voice and body signals | Experimental sensor fusion/classification | Proposed referral to ordinary or secondary screening | Experimental inference that signals resemble a “malintent” class. |
| SPOT | Yes | Sometimes apparent travel context or documents during encounter | Documents and databases became relevant after referral | Law-enforcement checks after escalation | No direct medical sensor; officers inferred stress from visible presentation | Point-based indicator threshold and officer judgment | Pat-down, baggage search, questioning, possible LEO referral | Behavioral anomaly selection, framed by TSA as potentially indicating malintent. |
| Integrated behavior detection | Yes | Secondary role | Identity checks coexist at checkpoint | Possible after referral | No physiological instrument | Reduced indicator set plus trained officer judgment | Additional screening | Screening prioritization, not proven intent detection. |
| Silent Partner | No contemporaneous behavior required | Yes | Yes | Yes | No | Intelligence-derived travel rules through ATS | Enhanced screening | A record matched a rule associated with elevated risk. |
| Quiet Skies | Rules did not require contemporaneous behavior; marshals later observed conduct | Yes | Yes, while focusing partly on non-watchlisted travelers | Yes | No | Subset of Silent Partner rules and list workflow | Enhanced screening and, in selected periods, FAMS surveillance | Selection for temporary heightened attention, not a finding of terrorism. |
| Secure Flight | No | Itinerary and carrier data | Central function | Some high-/low-risk categories incorporate additional government information | Identity biometrics may operate in connected checkpoint systems but are not Secure Flight’s core matching input | Name-matching algorithms, list matching and risk-category logic | Cleared, expedited, selectee, inhibited boarding-pass or No Fly consequence | Identity/list status and screening category. |
| FAMS flight selection | In-flight observations after deployment | Route and flight risk | Watchlist/intelligence inputs | Threat and investigative information | No hostile-intent sensor | Resource-prioritization methods | Armed marshal assigned to flight; observation and reporting | Which flights warrant scarce protective coverage. |
| ATS / Unified Passenger | Generally no live behavioral observation, though encounter reports may become data | Central | Central | Central | Can connect with biometric travel systems | Rules, risk assessments, link analysis, analyst review | Further vetting, secondary inspection, enforcement or carrier instruction | Relative risk and investigatory priority, not a clinical or scientific finding of intent. |
| Checkpoint facial biometrics/CAT | No | Boarding-pass and identity context | Identity record | Generally not a risk-association engine | Face and document image | One-to-one identity comparison/document authentication | Permit progression or require identity resolution | Whether the presented person and credential correspond. |
Scientific validity and quantitative performance
Construct validity: intent is not arousal
A valid hostile-intent detector would require a defensible chain of inference:
- a person actually possesses a sufficiently defined harmful intention;
- that intention generates a psychological state distinguishable from innocent states;
- the state creates physiological or behavioral signals specific enough to hostile intent;
- sensors or observers measure those signals reliably;
- the classification rule generalizes across people, cultures, environments and attack types; and
- the result remains useful at the extremely low base rate of real attackers.
Failure at any link undermines the final claim.
The National Academies’ polygraph review is directly relevant even though FAST was not a conventional polygraph. Heart rate, blood pressure, respiration and electrodermal changes reflect autonomic activation. They do not directly measure lying. Fear of false accusation, social anxiety, unfamiliar procedures, pain, medication, temperature, exertion, anger, trauma and disability can create similar activation. Conversely, practiced offenders, ideologically committed actors, people with atypical autonomic responses or subjects using countermeasures may show little detectable arousal. The Academies found that evidence for screening applications was particularly weak and cautioned against converting physiological reactions into direct conclusions about deception.
The distinction is sharper for hostile intent than for a specific lie. A lie-detection test can at least define a disputed proposition—“Did you place the object in the bag?” Hostile intent is temporally and normatively diffuse. Does an angry traveler who fantasizes about harm possess malintent? What about an undercover officer carrying out a red-team assignment, a protester intending civil disobedience, a passenger concealing an affair, or a person afraid because of immigration status? A system may detect concealment or stress without identifying the object of concealment, and may detect arousal without identifying an intention at all.
Human deception detection and behavioral cues
Bond and DePaulo’s meta-analysis synthesized 206 documents involving 24,483 judges. Average unaided accuracy was about 54 percent: judges correctly classified approximately 47 percent of lies and 61 percent of truths. That modest truth bias is not a basis for high-stakes airport triage, particularly where prevalence is far below the balanced or moderately balanced designs common in experiments.
The broader cue literature finds no equivalent of a behavioral “Pinocchio’s nose.” DePaulo and colleagues examined a very large set of verbal and nonverbal cues, most of which had small, inconsistent or context-dependent relationships with deception. Later work continues to find that very few bodily cues replicate consistently across studies. Emotional arousal, cognitive load and deliberate behavioral control can generate different—and sometimes opposing—presentations.
This does not mean behavior is always irrelevant. Specific conduct can rationally justify attention: attempting to evade a checkpoint, testing a locked door, abandoning a bag, surveilling security routines or providing materially inconsistent answers about a concrete fact. Those are observable actions with situational meaning. The scientific problem arises when generic signs such as gaze, swallowing, fidgeting, sweating, breathing changes or apparent nervousness are treated as transferable indicators of concealed criminal intent.
SPOT compounded that problem by asking officers to detect rare threats in a hurried, culturally diverse, high-stress environment. GAO’s review found substantial variation among airports and officers. Subjective baselines and indicator interpretations reduce inter-rater reliability: two trained officers may score the same traveler differently, while the same officer may score identical conduct differently depending on expectations, workload and context.
Ecological validity
Laboratory studies simplify reality in ways that generally make classification easier:
| Laboratory advantage | Real airport condition |
|---|---|
| Known time window in which the subject may lie | Intent may concern an event hours, months or years away—or no event at all |
| Experimentally assigned “guilty” and “innocent” classes | Ground truth is usually unknown |
| Roughly balanced class sizes | Genuine aviation attackers are extraordinarily rare |
| Standardized task | Travelers differ in language, culture, disability, sleep, medication, stress and experience |
| Sensors optimized for the experiment | Airports introduce motion, heat, noise, occlusion and multiple simultaneous stimuli |
| Cooperative participants | Adversaries can study, evade, mimic and countermeasure |
| Immediate labels | Operational outcomes may not become known for years, if ever |
| Limited consequences | Real actors face arrest, death, ideological commitment or organizational discipline |
FAST’s claimed research success must therefore be discounted heavily when considering operational capability. The task was not simply to reproduce a laboratory metric at a checkpoint; it was to preserve discrimination under massive distribution shift and an extreme class imbalance.
SPOT faced a related ecological problem. Even if some behaviors correlate weakly with deception in structured interviews, passive observation of strangers walking through an airport is a different task. Cognitive-load interview methods sometimes improve information yield by asking unexpected questions or requiring detailed accounts, but that does not validate silent visual diagnosis of hostile intent.
Cultural variation, disability and observer bias
Behavioral meaning varies across cultures. Eye contact can signal confidence in one setting and disrespect in another. Speech latency may reflect deception, second-language processing or a culturally normative conversational rhythm. A 2023 cross-cultural study found that verbal patterns differed among South Asian bilinguals speaking Hindi or English and British monolinguals, illustrating the danger of assuming that a cue set developed largely from Western English-speaking populations is universal.
Disability creates comparable confounds. Autistic travelers may avert gaze, display repetitive movement, speak with unusual prosody, interpret questions literally, have difficulty with unstructured interaction or appear emotionally “flat.” Peer-reviewed studies have found that autistic presentations can cause observers to judge people as more deceptive or less credible despite the absence of deception. Airports themselves create sensory overload that can intensify atypical behavior.
Other confounds include Tourette syndrome, Parkinsonian movement, tremor, hearing impairment, post-traumatic stress, panic disorder, obsessive-compulsive behaviors, cognitive disability, speech disorders and side effects of medication. A procedure can be facially neutral while systematically referring certain populations more often because the proxy variables are not neutral in operation.
Observer bias can amplify those effects. An officer who expects a traveler’s clothing, language, religion, nationality or route to be risky may interpret ambiguous movement as suspicious. Once a conversation begins, confirmation bias can shape which inconsistencies are noticed and how behavior is scored. TSA’s anti-profiling policy is an important control, but GAO found in 2019 that supervisory mechanisms did not adequately direct officials to monitor unlawful profiling. TSA modified its checklists later that year; by 2022 the checklist expressly included race, religion, gender identity, disability and other protected characteristics.
A formal policy cannot by itself measure disparate effect. GAO found TSA did not have sufficiently comprehensive demographic data to determine whether screening practices referred particular passenger groups at disproportionate rates. Low complaint counts are also an unreliable proxy for low discrimination because travelers may not know the complaint process, may not know why they were selected, or may believe that complaining will accomplish nothing.
Inter-rater reliability and adversarial adaptation
For officer-based systems, reliability requires more than training completion. TSA would need blinded scoring studies in which multiple officers independently evaluate the same encounters, with prespecified measures such as Cohen’s kappa, intraclass correlation and test-retest stability. Public GAO work identified variation and subjectivity but does not disclose a robust nationwide reliability estimate demonstrating consistent application of the revised indicator set.
Adversaries also adapt. Once indicators become known through observation, leaks or training materials, an attacker can rehearse calm behavior, manufacture an innocent explanation, send a non-operational traveler to map screening or deliberately create misleading signals in other passengers. Physiology is not immune: breathing control, movement, medications, fatigue and habituation can alter signals. A classifier trained on naive participants may fail against strategic actors, the very population it is supposed to identify.
Rules-based travel targeting has its own adaptation problem. Networks can alter routes, use clean intermediaries, split reservations, avoid known transfer points or exploit people without prior derogatory records. The appropriate response is not necessarily to abandon rules, but to measure rule decay, false-positive rates and adversarial displacement rather than assuming that classified criteria remain effective indefinitely.
Machine learning does not cure weak constructs
FAST’s sensor fusion and modern traveler analytics are often discussed in machine-learning language, but a model cannot recover a target that has not been validly defined and labeled. If “malintent” labels are assigned by experimental role rather than independently verified mental state, the model may learn artifacts of the experiment: the wording of instructions, room location, participant demographics, sensor setup, time sequence or differences in how actors were coached.
Apparent high accuracy can also result from:
- evaluating repeated samples from the same participant in both training and test data;
- tuning features against a small test set;
- balancing guilty and innocent classes unrealistically;
- omitting inconclusive cases;
- failing to test at a new site;
- using proxy labels generated by earlier government decisions; or
- measuring discrimination within one dataset rather than calibration in the deployed population.
Recent cross-dataset research on automated deception detection continues to identify inconsistent cues, shortcut learning and near-chance transfer when models are evaluated outside familiar datasets. That evidence postdates FAST’s principal research period but reinforces the methodological concern: in-domain classification is not proof of a universal deception signal.
The base-rate problem
Suppose, purely for illustration, that one in one million screened travelers is preparing an aviation attack. Assume an extraordinarily strong detector with:
- 90 percent sensitivity; and
- 99 percent specificity.
For one million travelers, the system would detect about 0.9 genuine attackers but falsely flag about 10,000 innocent travelers. The positive predictive value would be roughly 0.009 percent—approximately one true case per 11,000 alerts.
Even increasing specificity to 99.9 percent would produce about 1,000 false alarms per million travelers, leaving fewer than one true case among roughly 1,001 alerts. The operational burden would include secondary searches, interviews, marshal deployments, database checks, missed flights, investigative review and diversion of officers from other threats.
This is why sensitivity figures from a balanced laboratory experiment are nearly meaningless without specificity and prevalence. Rare-event screening requires extraordinarily low false-positive rates, reliable ground truth and a decision consequence proportionate to uncertainty.
Quantitative outcomes and costs
| Program | Public expenditure information | Public operational denominator | Referrals or interventions | Security or law-enforcement outcomes | What cannot be concluded |
|---|---|---|---|---|---|
| FAST / passive methods | A DHS advisory briefing listed a roughly $2.2 million passive-methods project amount in one budget context; other contracts and research costs exist, but no complete audited lifecycle total was located. | No operational traveler denominator | No public operational referral series | Experimental accuracy claims and “successful” research events, but no validated terrorism outcome | The public record cannot establish real-world sensitivity, specificity, false alarms or attacks prevented. |
| SPOT, 2007–2013 period | Approximately $900 million since nationwide deployment; about $200 million annually from fiscal year 2010 in the period GAO examined. | Roughly 1.3 billion passenger-throughput encounters at SPOT airports in fiscal years 2011–2012 | Approximately 61,000 SPOT referrals at forty-nine airports; about 8,700 LEO referrals | 365 arrests: about 0.6% of SPOT referrals and 0.03% relative to the 1.3 billion throughput encounters; publicly described reasons were predominantly ordinary crimes or status violations | Arrests do not validate hostile-intent detection, and TSA could not document terrorism outcomes from reported intelligence referrals. |
| SPOT workforce transition | Transferring personnel and reducing the standalone structure was associated with approximately $72 million in savings. | National referral counts available for selected years | 13,187 referrals in 2016; 506 in 2018; rates continued falling through 2021 | No public terrorism-detection series | Lower referral volume could mean better targeting, reduced use, changed recording or loss of capability; outcomes are insufficient to choose among them. |
| Silent Partner / Quiet Skies | DHS’s June 2025 termination announcement attributed roughly $200 million annually to Quiet Skies; this is an administration claim, not a publicly available program-specific audited cost allocation. | TSA tracked list size and rule matches, but key figures and rule-specific denominators are SSI or unavailable | Enhanced screening; some FAMS deployments | TSA’s retrospective counted some persons later added to the terrorism database, but lacked a comparison group and omitted most Silent Partner rules from the analysis | No comprehensive effectiveness estimate, cost per valid threat, false-positive rate or attacks prevented can be calculated. |
| FAMS overall | Approximately $780 million in fiscal year 2019, not all attributable to Quiet Skies. | Classified flight-coverage and threat data limit public analysis | Armed coverage and special missions | Public performance measures historically focused heavily on activity, training and efficiency proxies | Overall FAMS cost cannot be assigned to Quiet Skies, and uneventful flights do not show what would have happened without marshals. |
| Secure Flight | GAO estimated a lifecycle cost of about $1.36 billion through fiscal year 2020; fiscal year 2014 operations received about $93 million. | Essentially the covered commercial aviation population, but many matching statistics are SSI | Screening categories, match resolution, inhibited boarding | Public reporting confirms operational matching but omits many sensitive match and error figures | No public full confusion matrix exists for No Fly, Selectee, expanded and rules-based categories. |
| ATS / Unified Passenger | No reliable public aviation-passenger-specific lifecycle cost found; ATS is a multi-mission CBP platform. | International travelers and other vetted populations | Targeting alerts, analyst review, secondary inspection and enforcement referrals | CBP uses inspection outcomes to refine targeting, but detailed terrorism denominators and rule-level performance are not public | No credible public cost per terrorist detection or rule-level false-positive rate can be calculated. |
What the SPOT numbers mean
The SPOT data provide the clearest public example of the denominator problem. Of approximately 61,000 referrals at the forty-nine airports in GAO’s fiscal years 2011–2012 dataset, approximately 365 ended in arrest. That can be presented as a 0.6 percent arrest yield among referrals, but it is not a terrorism-detection rate. Most arrests resulted only after additional database checks or searches and involved offenses not uniquely connected to the behavioral indicators.
Moreover, TSA’s validation study compared arrest outcomes among people who had different exposure to law enforcement. A referred passenger was more likely to have identification checked against warrant and immigration databases than an ordinary passenger. Increased arrest yield can therefore arise from increased inspection intensity, not from a valid ability to detect deception or terrorism. GAO criticized this unequal-exposure design.
The public data do not supply the missing categories:
| Required quantity | Public SPOT evidence |
|---|---|
| Genuine terrorists who displayed enough indicators | Unknown |
| Genuine terrorists who did not display enough indicators | Unknown |
| Innocent passengers who displayed enough indicators | At least tens of thousands; complete national total unavailable |
| Innocent passengers correctly passed | Huge but not individually validated |
| Weapons or explosives found because of behavior referral | No comprehensive public national series |
| Attack plots disrupted because of behavior inference | No documented public case established by GAO |
| Opportunity cost | Not quantified, despite hundreds of millions in spending and officer time |
Why the absence of attacks proves little
No successful attack during a program’s operation can be consistent with many competing explanations:
- the program deterred or stopped attackers;
- other layers—intelligence collection, overseas disruption, watchlists, hardened cockpit doors, passenger resistance, explosives screening or luck—prevented attacks;
- no attacker attempted the type of operation the program was designed to detect;
- adversaries selected other targets;
- an attack was planned but abandoned for unrelated reasons;
- the program was ineffective but the base rate was too low for failure to become visible.
Without a credible counterfactual, “no attack occurred” is an outcome of the entire security environment, not a program-specific performance measure. GAO’s Quiet Skies review illustrates the problem: TSA tracked rule matches and later watchlist additions but lacked a comprehensive evaluation design.
Privacy, constitutional law and civil rights
Fourth Amendment
Routine airport screening is treated in federal appellate law as an administrative search justified by the need to prevent weapons, explosives and hijacking. In United States v. Aukai, the Ninth Circuit held that consent is not the constitutional basis once a traveler enters the screening process; reasonableness instead depends on the regulatory purpose and the relationship between the intrusion and aviation security. Later Ninth Circuit cases continue to describe TSA screening as a Fourth Amendment search justified by that limited administrative purpose.
That doctrine does not give TSA unlimited criminal-investigative authority. The closer a search moves from detecting aviation threats toward a general search for drugs, currency, immigration violations or evidence of ordinary crime, the more serious the concern that the administrative rationale is being used as a pretext. Ninth Circuit precedent has specifically distinguished valid weapons-and-explosives screening from schemes designed in part to search for drugs or currency.
SPOT referrals therefore present a doctrinal tension. A behavior-based referral that triggers a proportionate explosives search at the checkpoint fits more comfortably within administrative-search doctrine. An escalating encounter whose practical purpose becomes discovering warrants, narcotics, immigration violations or unexplained cash is harder to justify solely by the original aviation-security rationale—although contraband discovered in a lawful security search is not necessarily suppressed.
Quiet Skies surveillance raised a different issue. Observation of a traveler’s movements, conversations and contacts in airports or aircraft cabins generally occurs in spaces where traditional doctrine recognizes limited expectations of privacy. Yet prolonged, technology-assisted or systematically aggregated monitoring can be more intrusive than an isolated observation. No Supreme Court decision has squarely resolved whether the full Quiet Skies pattern—secret algorithmic selection followed by repeated covert in-flight observation—constituted a search. The strongest constitutional question may therefore concern the combination of selection, duration, data retention and consequence rather than the observation of any one public act.
FAST would have raised a still more novel issue had it become operational. Remote sensing of cardiovascular, respiratory or thermal signals differs from ordinary visual observation because it seeks physiological information not necessarily consciously exposed to the public. Existing airport-search doctrine permits substantial screening for weapons, but a system designed to infer mental state from involuntary bodily signals could require a separate proportionality analysis. Because FAST did not publicly mature into operational deployment, courts have not supplied that analysis.
Fifth Amendment and due process
The Fifth Amendment’s Self-Incrimination Clause ordinarily protects compelled testimonial communication, not the collection of fingerprints, facial appearance, voice characteristics or other physical evidence. Passive physiological sensing would therefore not automatically constitute compelled testimony. The harder question would be whether the government used bodily measurements to extract the functional equivalent of a compelled statement about intention. Existing doctrine offers no clear answer because no operational FAST case reached the courts.
Due process is more concrete in watchlisting. Placement on the No Fly List can prevent travel, yet the underlying intelligence and criteria are often classified. In Kashem v. Barr, the Ninth Circuit rejected a facial vagueness challenge to the revised No Fly criteria and concluded that a reasonable-suspicion standard based on articulable intelligence constrained official discretion. The court evaluated procedures developed after earlier litigation, including notice that a person remained on the list and provision of an unclassified explanation when feasible.
In FBI v. Fikre, the Supreme Court unanimously held in 2024 that removing a plaintiff from the No Fly List and offering a limited assurance did not automatically moot his constitutional challenge. The decision did not decide whether the original listing was lawful. It did, however, prevent the government from defeating review merely by delisting a litigant without demonstrating that the challenged conduct could not reasonably recur.
Those cases involve formal watchlisting, which generally has clearer consequences and redress pathways than a Quiet Skies or ATS rule match. A person selected by a secret rule may experience repeated searches or surveillance without receiving notice of the reason, confirmation that a record exists, access to the rule or a meaningful opportunity to contest the inference. That “shadow classification” can be less severe than a No Fly prohibition but harder to challenge because the government may characterize each incident as an ordinary security measure.
Equal protection, religion and profiling
The federal government is constrained by the equal-protection component of the Fifth Amendment. A traveler alleging intentional racial, national-origin or religious discrimination would ordinarily need more than evidence that a neutral rule had unequal effects; proof of discriminatory purpose can be difficult when rules and intelligence sources are secret.
Behavioral screening is especially vulnerable to proxy discrimination. Race and religion may be formally prohibited factors, yet language, clothing, travel route, anxiety around police, eye-contact norms, family associations and names can influence either the rule or the human interpretation. The problem is not limited to purposeful prejudice. A poorly validated indicator can produce disparate referrals even when every officer acts in subjective good faith.
TSA policies prohibit profiling based on race, color, religion, national origin, ethnicity, sexual orientation, disability and other protected attributes. GAO nevertheless found that TSA’s earlier oversight mechanisms did not adequately direct supervisors to monitor profiling during behavior-detection activities. TSA revised checklists in October 2019, and later GAO work found supervisors were expected to observe whether referrals were made without regard to race, religion, gender identity, disability and related characteristics.
An earlier DHS Inspector General investigation did not corroborate a specific allegation of widespread racial profiling by behavior-detection officers at Boston Logan Airport. That limited finding should not be overstated. It does not establish that profiling never occurred nationally, nor does an allegation itself prove that it did. Civil-society reports documented complaints and statements from officers at several airports, but those records vary in corroboration and should be treated as evidence of risk and contested practice, not as a definitive nationwide prevalence estimate.
Religious profiling additionally implicates the First Amendment. Selection based on attendance at a mosque, religious association or protected expression would require a far stronger justification than selection based on individualized evidence of an operational plot. Fikre arose from allegations that included impermissible religious considerations, although the Supreme Court’s 2024 decision addressed mootness rather than adjudicating those allegations.
Disability law and accessibility
Section 504 of the Rehabilitation Act applies to TSA’s screening activities, and TSA provides accommodation procedures and passenger-support services. The legal risk is not confined to inaccessible equipment. A behavior system can discriminate when disability-associated conduct is treated as suspicious and produces more intensive searches, questioning or law-enforcement encounters.
GAO found that checkpoint technology and screening practices could more frequently refer transgender travelers, people wearing religious headwear, people with coarse hair, passengers using prostheses and persons with disabilities. For behavior detection, the comparable concern is that deviations from an assumed social baseline are not evenly distributed across the population.
Reasonable safeguards would include disability-aware indicator design, explicit prohibitions on scoring disability-related behavior, private accommodation, accessible notice, meaningful complaint retention, independent disparity audits and a mechanism to prevent repeated re-selection caused by the same misunderstood presentation.
Privacy Act, PIAs and systems of records
The Privacy Act regulates federal “systems of records” from which information is retrieved by personal identifier. Agencies must publish System of Records Notices describing categories of individuals, records, purposes, routine uses, retention and access procedures. Secure Flight and ATS operate through such notices and Privacy Impact Assessments. Yet law-enforcement and national-security exemptions can limit a traveler’s ability to learn what information exists or to correct it.
A PIA is a transparency and risk-management document. It is not proof that a system is scientifically valid, constitutionally reasonable or effective. A program can accurately describe its privacy controls while relying on an invalid predictor; conversely, a potentially useful program can still retain information too long or provide inadequate redress.
Secure Flight’s historically published retention framework allowed records with no watchlist match to be retained for up to seven days, potential matches for up to seven years and confirmed matches for ninety-nine years. These periods reflect different governmental interests but also produce different consequences from error: a mistaken confirmed match can become effectively lifelong.
ATS historically reduced its general retention period from forty years to fifteen years, with later records and modules governed by updated schedules and source-system limitations. PNR retention and access remain particularly sensitive because a reservation can disclose companions, contact information, travel agencies, payment arrangements, seat choices, special-service requests and long-term movement patterns.
Quiet Skies data crossed several systems and organizations: ATS supplied rule analysis, Secure Flight supplied screening status, FAMS created observation reports, and operational systems managed mission coverage. DHS OIG found that TSA’s use of some Quiet Skies passenger data was not entirely consistent with privacy guidance in the 2012 PIA. That is significant because privacy compliance depends not only on whether a collection was initially authorized, but whether later use, dissemination and retention remain within the stated purpose.
Watchlisting, notice and redress
DHS TRIP provides a redress process for travelers who experience repeated screening, mistaken identity or boarding problems. A redress number can help Secure Flight distinguish a traveler from a similarly named listed person. It does not necessarily reveal whether the person matched a classified ATS rule, appeared in intelligence reporting or was temporarily selected by a Quiet Skies-type process.
This creates three distinct redress problems:
| Error type | Potential remedy | Structural limitation |
|---|---|---|
| Name collision | Identity resolution and redress number | Does not correct erroneous intelligence about the correct person |
| Incorrect watchlist nomination | DHS TRIP and judicial review, with varying levels of notice | Classified evidence and limited disclosure |
| Secret rule or pattern selection | Complaint, TRIP request or repeated screening review | Traveler may never know that a rule exists or which data triggered it |
The combination of secrecy and transience is especially difficult. A ninety-day Quiet Skies designation might expire before litigation, while retained records or analytic associations survive. Fikre limits one form of mootness gamesmanship in formal No Fly litigation, but it does not give every person selected for secondary screening a right to disclosure of classified criteria.
Aviation-security statutes and oversight
The Aviation and Transportation Security Act placed civil aviation security under TSA and authorized federal passenger screening. The Intelligence Reform and Terrorism Prevention Act of 2004 directed TSA to assume passenger watchlist matching, giving rise to Secure Flight’s central operational role. FAMS statutes authorize deployment on high-risk flights, while the TSA Modernization Act of 2018 imposed additional review and notification requirements concerning Silent Partner and Quiet Skies rules.
Statutory authorization to screen or target travelers does not answer whether a particular scientific inference is valid. Congress can authorize TSA to use behavior observation, but it cannot make swallowing, gaze or facial temperature a reliable indicator of terrorism by legislative declaration. This is why GAO’s methodological reviews were central: they tested whether the evidence justified the claimed screening value, not merely whether TSA possessed a broad security mission.
Classified and unavailable evidence
Several categories remain unavailable to the public:
- current Secure Flight matching thresholds and full error rates;
- most Silent Partner and Quiet Skies rules;
- ATS targeting rules, weights and rule-level yields;
- detailed FAMS flight-selection methods and coverage;
- current behavior-detection indicator thresholds;
- intelligence reporting used to nominate or associate travelers;
- complete terrorism-related referral outcomes;
- operational red-team results; and
- some cost allocations and contractor performance data.
Classification and Sensitive Security Information restrictions can be justified to prevent evasion. They also prevent independent researchers from reproducing agency claims. The appropriate conclusion is not that the programs secretly work or secretly fail. It is that public evidence cannot resolve the gap, and official assertions depending on unavailable evidence should be labeled unverified rather than accepted or rejected categorically.
Oversight findings, alternative explanations and continuity beneath renaming
Official defenses
Agencies have offered several recurring defenses.
TSA argues that layered security does not require each layer to identify a terrorist independently. A behavior referral may locate a weapon, expose fraudulent identity, disrupt reconnaissance or create uncertainty for an adversary. Rules-based targeting can prioritize limited officers even if a matched traveler is not formally suspected. Watchlist matching can prevent known threats from boarding while expedited screening permits resources to focus elsewhere. Secrecy protects criteria from countermeasures. These are plausible operational rationales.
TSA also revised SPOT indicators, altered training, reduced referrals and added anti-profiling oversight. Quiet Skies underwent working-group and stakeholder review, while ATS rules are reviewed using intelligence and inspection outcomes. The strongest official argument is therefore not that the programs literally read minds, but that imperfect indicators can still improve allocation at the margins when used with human judgment and additional screening.
That defense is strongest for Secure Flight, ATS and FAMS route selection, where the systems organize known information or allocate resources. It is weakest for generic behavioral or physiological claims, because marginal utility still requires that the indicators perform better than random, discretionary or alternative allocation after accounting for cost and bias.
Inspector-general, GAO and congressional critiques
GAO’s SPOT critique was scientific and programmatic. TSA had deployed nationally before establishing a sound effectiveness design. Its principal validation study contained methodological defects, indicator support was weak, and behavior-referral rates varied. GAO recommended constraining further funding until TSA could produce scientifically valid evidence.
GAO’s Silent Partner and Quiet Skies critique focused less on whether travel rules could ever be useful and more on absent evaluation. TSA counted rule matches, list size and some later watchlist additions, but did not establish a comprehensive metric. The retrospective analysis lacked a comparison group and covered Quiet Skies rather than the large majority of Silent Partner rules. FAMS reports were not consistently converted into validation evidence.
GAO’s Secure Flight critique was narrower. The core system operated, but TSA did not measure every kind of missed or falsely identified high-risk passenger. Much of the relevant accuracy evidence was withheld as Sensitive Security Information, limiting public evaluation.
DHS OIG’s Quiet Skies work identified governance, data-use and privacy deficiencies rather than proving that every selection was unlawful. Earlier OIG work on Secure Flight examined coordination and implementation, including the challenge of opaque match thresholds.
Congressional debate often followed partisan or episodic controversies. Assertions that a program targeted or protected particular political figures are relevant oversight allegations, but they are not self-proving. The June 2025 DHS announcement included claims of politicization and failure to stop any terrorist attack. The latter is an important official representation; the broader allegations require documentary or adjudicative corroboration before being treated as established fact.
Plausible alternative explanations for claimed successes
At least six alternative explanations can account for positive-looking program results without demonstrating hostile-intent detection.
Inspection-intensity explanation. Referred passengers receive more searches, questioning and database checks. Those procedures will discover more warrants, drugs, immigration violations and false documents even if the original behavioral indicator is unrelated to criminality. GAO identified this unequal-exposure problem in TSA’s SPOT validation.
General nervousness explanation. People carrying drugs, overstaying visas, traveling with false documents or fearing police may be anxious. A behavior system may therefore enrich for ordinary violations while having no capacity to distinguish an aviation attacker from other nervous travelers. Arrest yield can rise without validating the stated terrorism construct.
Shared-data or circularity explanation. A Quiet Skies rule and a later watchlist nomination may rely on overlapping intelligence, travel associations or source reporting. A person later appearing in the terrorism database is not an independent validation if both decisions emerged from the same underlying information. Apparent predictive success can be partly circular.
Broad-net explanation. A rule can identify some later-interesting people simply because it selects a large population. Without the denominator of all matched travelers and a comparison rate among unmatched travelers, the raw count of later watchlist additions is uninterpretable. This was a central defect in TSA’s Quiet Skies retrospective analysis.
Layered-security explanation. The absence of attacks may result from intelligence operations, overseas military or police action, physical screening, hardened aircraft, passenger intervention, cockpit security or a low number of attempted attacks—not the program under evaluation.
Behavioral displacement explanation. An adversary may shift routes, tactics or targets in response to the total security environment. That can be described as deterrence, but it does not show that a particular detector correctly identified anyone. Displacement could also impose costs elsewhere rather than reduce total risk.
Opportunity costs
Every false or low-value alert consumes a scarce resource. For SPOT, the opportunity cost included thousands of personnel, training, supervisory attention, secondary screening space and law-enforcement time. For Quiet Skies, it included air-marshal flight assignments that could have covered another route or threat. For ATS, overbroad rules can congest analyst queues and port inspections. For Secure Flight, weak matching can burden resolution staff and delay travelers.
Opportunity cost also has a security dimension. An officer focused on a nervous but harmless traveler is not observing another checkpoint area. A marshal following a rule-matched passenger may not be on a flight selected by a more current intelligence lead. Excessive false alarms can produce automation bias, alert fatigue and pressure to waive or shortcut review.
Civil-rights costs can become security costs as well. Communities that believe routine religious, ethnic or disability-associated behavior is treated as suspicious may become less willing to report threats or cooperate with investigators. Repeated unjustified screening can teach travelers to distrust redress processes and withhold context that would otherwise resolve an encounter.
Did termination or renaming end the underlying function?
| Named change | What ended | What continued |
|---|---|---|
| Project Hostile Intent → FAST → Passive Methods/PASS | Branding, project framing and particular research phases changed. | The theory that passive physiological and behavioral signals might reveal malintent persisted through multiple research formulations. No public evidence shows an operational deployment, but renaming did not itself falsify or validate the research. |
| SPOT → Behavior Detection and Analysis → integrated behavior detection | Dedicated Behavior Detection Officer position and standalone organizational structure ended in fiscal year 2017. | Trained TSOs retained observation and referral authority; qualifications and operating procedures persisted. |
| ATS-P → Unified Passenger | Legacy user-interface functionality was replaced. | Underlying ATS data, targeting rules, analyst workflows, prior encounters and interagency vetting continued and expanded. |
| Quiet Skies termination | Named program and Quiet Skies-specific surveillance mission ended June 5, 2025. | Secure Flight, ATS, watchlist matching, international rules-based targeting, FAMS and “critical aviation security vetting” continued. |
| Potential Silent Partner ambiguity | No separate, unambiguous public termination date located. | ATS-supported rule screening and Secure Flight consequences remain technically and institutionally possible; current rule branding is not public. |
| Expansion of biometrics | No older hostile-intent function was replaced in a one-for-one manner. | Facial matching increasingly strengthens identity assurance, which may reduce impersonation but does not infer intent. |
The most important institutional lesson is that functions are more durable than labels. Data pipelines, legal authorities, trained personnel, interagency memoranda and user interfaces can be reassigned. A program may “end” for budgetary or political purposes while its narrower practices survive in ordinary operations. Conversely, the persistence of a data field or PIA after termination does not prove that the old operational mission is still being executed.
Quiet Skies is the clearest example. DHS’s termination announcement expressly said critical vetting would continue. Secure Flight still needs to compare travelers with watchlists and risk categories; CBP still analyzes PNR and APIS information; FAMS still allocates marshals using threat information. The termination removed a particular rules-and-surveillance package, not the federal traveler-vetting ecosystem.
What a scientifically defensible successor would require
A credible future program claiming to detect malicious intent would need, at minimum:
| Requirement | Necessary evidence |
|---|---|
| Precise construct | A definition separating harmful intent from anxiety, concealment, anger, ordinary crime and protected belief |
| Independent ground truth | Labels not generated merely by experimental assignment or prior agency suspicion |
| Realistic prevalence | Evaluation under rare-event conditions, not a balanced mock-crime sample |
| External validation | New airports, cultures, equipment, operators and threat scenarios |
| Full error reporting | Sensitivity, specificity, predictive values, inconclusive rate and subgroup performance |
| Inter-rater evidence | Blinded reliability estimates for human observers |
| Disability and cultural testing | Prespecified subgroup analyses and accommodation safeguards |
| Adversarial testing | Countermeasures, rehearsal, route changes and deliberate mimicry |
| Outcome linkage | Weapons, plot disruption or independently verified threat—not merely arrests for unrelated offenses |
| Cost comparison | Performance against random screening, intelligence-led screening, canine teams and physical-detection technology |
| Redress and auditability | Traceable reason codes, retention limits and correction mechanisms |
| Sunset rule | Automatic suspension if validation thresholds are not met |
None of the publicly documented hostile-intent initiatives met that complete standard.
Final spectrum from ordinary screening to genuine “pre-crime”
The ranking below orders programs by how far they move from detecting a physical object or identifying a known person toward inferring future harmful conduct from indirect attributes. It is not a ranking of overall usefulness.
| Rank from least to most “pre-crime” | Program or function | Reason |
|---|---|---|
| Ordinary physical screening | X-ray, computed tomography, metal detection, explosive-trace detection and canine screening | These systems look for prohibited objects or chemical traces. False alarms remain important, but the target construct is concrete and directly related to aircraft safety. |
| Identity authentication | Credential Authentication Technology and one-to-one facial matching | Determines whether the traveler corresponds to a document or existing identity record. It identifies a person; it does not infer criminal intention. |
| Secure Flight watchlist matching | No Fly and Selectee identification | Matches a traveler to a previously nominated identity. The difficult inference occurred upstream in watchlisting; Secure Flight’s central task is identity resolution and screening consequence. |
| FAMS intelligence-based resource allocation | Selection of flights based on known threats, routes and intelligence | Prioritizes a scarce protective resource. It may rely on probabilistic intelligence but usually does not claim to diagnose an individual’s present mental state. |
| ATS / Unified Passenger | Rule-based targeting from travel, reservation, encounter, association and intelligence data | Infers relative risk from patterns and associations. It moves beyond known-person matching but remains a decision-support and inspection-prioritization system. |
| Silent Partner | Selection of non-watchlisted inbound travelers through intelligence-derived rules | Uses patterns to identify people not formally known as threats, imposing enhanced screening based on probabilistic resemblance to risk criteria. |
| Quiet Skies | Temporary enhanced screening plus possible covert FAMS surveillance of non-watchlisted travelers | Adds sustained person-focused surveillance and detailed behavioral reporting to a rules-based selection, despite no formal determination that the person is a terrorist. |
| SPOT and integrated behavior detection | Human inference from observed swallowing, breathing, demeanor, movement and interaction | Attempts to infer concealment, stress or malintent from ambiguous current behavior. Its target is closer to internal state than recorded travel patterns, and scientific support for most indicators was inadequate. |
| FAST / Project Hostile Intent | Remote multimodal sensing intended to classify “malintent” before an overt act | Closest to genuine “pre-crime” because the explicit research goal was to infer intention to cause harm from physiological and behavioral signals, without requiring a weapon, watchlist match or completed offense. It remained research rather than demonstrated operational capability. |
The ranking leads to a final distinction that should govern future oversight.
Secure Flight can be effective without predicting anyone’s intent if it accurately identifies listed persons and assigns the legally required screening status. ATS can provide value without proving that every rule-matched traveler is dangerous if its referrals improve inspection outcomes enough to justify their cost and disparate effects. FAMS can deter attacks without observing a crime on every covered flight if deployment is connected to defensible threat information.
SPOT and FAST require a more demanding showing because their rationale reaches inside the person. The government was not merely asking, “Is this the listed individual?” or “Does this itinerary warrant inspection?” It was asking whether breathing, swallowing, facial temperature, gaze, voice or demeanor revealed concealed hostile intention. The public scientific record does not support confidence in that inference at operational aviation base rates.
Accordingly, the evidence through August 2, 2026 supports the following bottom-line judgments:
| Program | Bottom-line judgment |
|---|---|
| FAST | Ambitious hostile-intent research whose operational validity was never publicly demonstrated; no public evidence of routine deployment and no exact public termination date. |
| SPOT | A costly operational program that generated many ordinary-law-enforcement referrals but did not publicly demonstrate reliable detection of terrorists or hostile intent. |
| Integrated behavior detection | A quieter surviving function with dramatically lower referral volume, continuing scientific and disparity concerns, and insufficient recent public outcome data. |
| Silent Partner | Operational rules-based international traveler screening whose current independent name/status is opaque after Quiet Skies’ termination. |
| Quiet Skies | An operational, non-watchlist risk-selection and surveillance program from its 2011 pilot and April 2012 permanent transition until its June 5, 2025 termination; effectiveness was not comprehensively measured. |
| Secure Flight | An active, indispensable identity- and screening-allocation system, but not evidence that government can predict intent. |
| FAMS surveillance | Active protective capability; Quiet Skies-specific passenger surveillance ended, while intelligence-based flight coverage continues. |
| ATS / Unified Passenger | Active and institutionally central rules-based targeting infrastructure; potentially useful for triage, but publicly unavailable rules and denominators prevent independent measurement of terrorism-specific accuracy. |
| National Vetting Center and biometric successors | Active related architecture expanding data integration and identity assurance, not a demonstrated replacement for FAST-style hostile-intent sensing. |
The strongest public evidence favors systems that detect tangible threats, resolve identity, connect travelers to particularized intelligence, or transparently prioritize inspections. The weakest evidence concerns systems that infer deception or hostile intent from generic behavior and involuntary physiology. Renaming, reorganizing or terminating programs has repeatedly altered their visibility without necessarily eliminating their data flows or underlying screening functions. The central oversight task is therefore not merely to ask whether a named program still exists, but whether the same inputs, rules, personnel and consequences continue elsewhere—and whether they are validated against the specific claim the government makes for them.