ICE Searched Nashville Airport’s Flock License-Plate Data 416 Times

Audit logs show that U.S. Immigration and Customs Enforcement (ICE) agents searched the Metropolitan Nashville Airport Authority’s Flock license-plate-reader database 416 times on ICE’s behalf. The database is part of a surveillance system supplied by Flock Safety. The reported figure describes searches attributed to ICE, rather than all immigration-related searches recorded in the system, and underscores that public-sector technology agreements can shape how data is accessed beyond the purchasing organization.

The reporting also states that approximately 3,591 searches were logged for immigration-related reasons through July 7. That broader total includes searches not attributed to ICE, so it should not be treated as an ICE-only count. The distinction matters for agency oversight, vendor reporting, and public accountability: buyers and reviewers need records that identify who searched, on whose behalf, and under what stated purpose, while avoiding unsupported conclusions about searches that the logs do not attribute to a specific agency.

For airport authorities and other public buyers, the procurement implication is that surveillance agreements should explicitly govern external-agency access—not leave it to informal practice or technical defaults. Solicitations, contracts, and renewals can define which outside agencies may query collected information, which purposes are authorized, whether approval is required, and how access can be suspended or changed. Requirements should also address how search purposes are documented and how exceptions are handled, giving the customer a contractual basis to administer access consistently.

The report identifies no new solicitation, procurement opportunity, or contract value. Its relevance to GovCon is therefore in contract administration, requirements development, and oversight of existing digital-infrastructure deployments rather than a specific near-term award. For Flock Safety and comparable providers, customer-defined permissions, purpose limitations, and reliable audit records can become important capabilities in public-sector evaluations. Buyers should align those technical controls with agreement terms, audit procedures, and disclosure expectations so that external searches remain reviewable throughout the system’s lifecycle.

• 416 searches of the Metropolitan Nashville Airport Authority’s Flock database were attributed to ICE.
• Approximately 3,591 immigration-related searches were logged through July 7; the total includes searches not attributed to ICE.
• The surveillance system is associated with Flock Safety and uses license-plate-reader data.
• The reported activity involves the Metropolitan Nashville Airport Authority, ICE, and the U.S. Department of Homeland Security.
• The reporting identifies no new solicitation or contract value; the signal concerns oversight of an existing system.
• Buyers should specify which external agencies may access surveillance data and for what authorized purposes.
• Procurement documents should require auditable records that identify search activity and support customer review.
• Agreements should set expectations for audit-log availability and disclosure, including how external searches are accounted for.
• Vendors may need to support customer-defined access controls, purpose limits, and records suitable for oversight.