Skip to content

Security1 publisher2 min readPublished

DHS's Predictive Intelligence Targeting Teams screen financial activity to seed local traffic stops

A DHS document Kyle Olson received in discovery names the Spokane Sector unit that flagged his financial patterns to a Montana trooper, and it identifies neither the systems searched nor a crime he was suspected of.

The Watch · Security desk

Illustration accompanying DHS's Predictive Intelligence Targeting Teams screen financial activity to seed local traffic stops

What happened

  • 404 Media names Border Patrol's Predictive Intelligence Targeting Teams, units that analyze Americans' financial activity and pass the result to local police, who then stop drivers not suspected of any specific crime.
  • A DHS document Kyle Olson received in discovery, written by a Spokane Sector agent assigned to the sector's Targeting & Intelligence Division PITT, explains how Border Patrol instigated his traffic stop.
  • A Montana Highway Patrol sergeant pulled Olson over on Interstate 90 one night in May for a plate obstructed by a tinted cover and a luggage holder, tested his blood, and charged him with DUI.

Compiled by The WatchSomething wrong?How this is made

Why it matters

  • exposure A transaction record that reaches a law enforcement-sensitive system can become the input to a roadside stop, and the institution that supplied the record gets no signal that it was used that way.
  • constraint A driver contesting this kind of stop can only litigate the plate cover, because the trooper's report is where the stated reason lives and the financial analysis sits in a federal document he may never be handed.
  • precedent Two sector teams and a named division inside Border Patrol's intelligence structure make financial-pattern targeting look like a standing program, which raises the expectation that other sectors run the same play.
  • contradiction 404 Media describes PITT targets as people not suspected of a specific crime, while the Phelps document says his intelligence was not the sole basis for the stop, and the record does not say what the rest of the basis was.

The workflow in the Phelps document runs in one direction. An agent inside the Spokane Sector Border Patrol Targeting & Intelligence Division reviews law enforcement-sensitive databases, including Americans' financial activity, and hands what he develops to local police [12]. In Olson's case Phelps wrote that he saw "information contained within law enforcement-sensitive systems suggesting financial activity patterns commonly associated with illicit narcotics activity," and that he also reviewed Olson's prior arrest and criminal history [13]. He sent it to Sergeant Beck to "support general interdiction efforts" [14]. Beck supplied the stop. On bodycam he told Olson the plate was "a little bit obstructed" and that this was the reason for the stop [8].

Nothing in the document, as described by 404 Media, names a system, a bank, or a data broker [16]. "Law enforcement-sensitive databases" is the whole of the provenance [12]. For an institution that files, sells, or shares transaction records, that is the unknown that matters: whether the input was a regulatory filing, a subpoenaed account record, or purchased data. The material does not answer it, and the driver had no way to ask.

Olson learned any of it because he was charged and discovery produced the DHS document, which he then shared with 404 Media [10]. A stop that finds nothing produces no charge, no discovery, and no paper connecting a financial pattern to a roadside encounter. Jake Laperruque of the Center for Democracy & Technology told 404 Media that "genuine probable cause cannot be synthetically generated," that Border Patrol appears to be using parallel construction to cloak the reason behind its car stops, and that systems which cannot be meaningfully reviewed cannot be trusted [5].

Two teams are named so far, one on each land border: Spokane Sector on the Canadian side, Laredo Sector in Texas on the Mexican side [3]. How many sectors run one is not public [15]. The other half of the program is already documented, since the Associated Press reported last year that Border Patrol used automatic license plate readers as part of the same predictive policing effort [4]. Plate reads and financial-pattern analysis feed the same interdiction pipeline, and the practice by design targets people against whom no evidence of a crime yet exists [17].

What to watch

  • Whether Olson's defense moves to suppress and whether a court orders Border Patrol to produce the underlying PITT queries.
  • Whether CBP or DHS states how many sectors operate a PITT beyond Spokane and Laredo.
  • Whether any filing identifies the actual source of the financial data: regulatory filings, subpoenaed bank records, or purchased data.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories