This bill directs the Secretary of Homeland Security to negotiate with Canada to create a bilateral framework enabling integrated cross‑border aerial law enforcement operations and to stand up a Program under that agreement. It also requires a near‑term DHS study on unmanned aircraft systems along the northern border and sets training, privacy, and congressional‑notification requirements tied to any Program.
Why this matters: the measure would move binational cooperation from maritime and land domains into controlled airspace above the border, raising practical questions about airspace sovereignty, rules of engagement, data sharing, and who bears the operational and legal responsibilities. The bill avoids authorizing new appropriations, meaning agencies would need to implement any new activities within existing budgets or seek separate funding.
At a Glance
What It Does
The bill authorizes the Secretary to establish an integrated cross‑border aerial law enforcement Program if a U.S.–Canada bilateral agreement is finalized; the Program is modeled on the 2009 maritime framework and includes specified training, civil‑rights protections, interagency communications protocols, and notification to congressional oversight committees. It sets a territorial limit for Program activity near the border, creates two reporting triggers (a one‑year unclassified UAS report with a possible classified annex and a two‑year report if the Program is not established), and explicitly states no additional funds are authorized.
Who It Affects
Affected parties include DHS components (border and investigative elements), appropriate Canadian law enforcement agencies, operators of manned and unmanned aircraft near the northern border, border communities subject to aerial operations, and privacy and civil‑liberties stakeholders who will monitor training and oversight. Congress receives required notifications and oversight materials.
Why It Matters
This bill sets a precedent for integrated, bilateral aerial policing and pushes operational coordination into a legally and technically complex domain—airspace management, evidence collection, and cross‑border pursuit—while also requiring DHS to confront UAS threats and privacy risks. The lack of new funding and required privacy safeguards create immediate trade‑offs for implementation and oversight.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill’s core instruction is procedural: negotiate and, if both governments agree, implement an integrated aerial operations regime between the United States and Canada. Rather than prescribing every operational detail, the statutory structure punts much of the granular rulemaking to the bilateral agreement: what authorities cross border teams will exercise, how missions will be planned and authorized, and how Canadian and U.S. officers will operate together.
The statute does, however, insist that civil‑rights and privacy protections be written into any agreement and that participating officers complete training on those obligations before deployment.
On oversight and accountability, the bill creates two distinct reporting hooks. One requires DHS to produce a substantive unclassified study (with a classified annex if needed) about unmanned aircraft use and countermeasures along the northern border, including coordination gaps, jurisdictional obstacles, and malign‑actor use cases.
The other requires the Secretary to explain to Congress why the Program has not been established if negotiations do not produce an agreement within two years; that report must identify unresolved issues, civil‑rights concerns, and whether the effort should continue.Operationally, the statute authorizes participating agencies to set up communications protocols and to staff the Program with approved federal and Canadian law‑enforcement officers, but it also constrains the Program geographically and by exception—leaving details about pursuit, hot pursuit, and exigent circumstances to the implementing bilateral pact. Finally, by declaring that no additional funds are authorized, the bill forces DHS and partner agencies to implement any negotiated authorities using existing appropriations or to seek new funding separately, which will materially affect how rapidly and extensively the Program can be deployed.
The Five Things You Need to Know
The bill conditions any integrated aerial operations Program on a finalized bilateral agreement between the United States and Canada; DHS cannot unilaterally create the Program without that pact.
Program operations are geographically capped to a corridor near the international border but include narrow exceptions for aircraft origin/destination needs and exigent emergencies.
All U.S. and Canadian officers must complete privacy, civil‑rights, and civil‑liberties training before participating in Program activities, and agreements must include explicit protections for U.S. citizens.
DHS must deliver a detailed report on unmanned aircraft system (UAS) activity along the northern border within one year (with a classified annex if needed) and, if the Program is not established within two years, a second report explaining obstacles and offering recommendations.
The Act contains a funding limitation: it does not authorize additional appropriations, so agencies must use existing resources to carry out any obligations created by the bill or obtain separate funding.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Establishes the Act’s name as the 'Cross Border Aerial Law Enforcement Operations Act.' This is a purely formal provision but signals the legislative focus on integrating aerial operations with a foreign partner rather than a domestic reform.
Authority to negotiate and core Program design features
Directs the Secretary of Homeland Security to negotiate a bilateral agreement with Canada and authorizes the Secretary to establish an integrated Program if both governments assent. The statute sets out high‑level elements the Program must include—approved participating law‑enforcement personnel, training requirements, civil‑rights and privacy protections, and required congressional notifications—while delegating most operational specifics to the bilateral text. For implementers, that means planning and legal work will be divided: Congress requires safeguards up front, but the actual rules of engagement, data‑handling practices, and day‑to‑day authority flows will be embodied in the international instrument.
Geographic limits, exceptions, and communications; training and notifications
The bill limits where Program activities may occur relative to the border while carving out exceptions for logistical departures/returns and exigent circumstances; it also authorizes agencies to build communications protocols needed for safety and coordination. Practically, negotiators and DHS counsel will have to reconcile that geographic constraint with airspace control regimes, local air‑traffic rules, and contingency plans for pursuits that cross beyond the prescribed area. The statutory requirement that officers be trained on privacy and civil‑liberties obligations before deployment creates a compliance checkpoint that agencies must operationalize—curriculum development, recordkeeping, and audit trails will all be necessary for accountability.
Two‑year failure‑to‑finalize report requirement
If negotiations do not produce an operational Program within two years of enactment, the Secretary must report to specific congressional committees identifying unresolved negotiation points, civil‑rights concerns that impeded progress, recommended congressional actions, and a recommendation on whether to continue. That report both compels transparency about diplomatic and legal sticking points and creates a legislative oversight lever: Congress will receive a structured brief on why talks stalled and options to move forward or terminate the effort.
Unmanned aircraft systems report
Requires DHS to submit an unclassified study, with a possible classified annex, describing UAS activity and threats along the northern border, jurisdictional impediments to countering unauthorized UAS, malign uses (surveillance, smuggling, espionage), and the feasibility of joint UAS or counter‑UAS operations. For practitioners, this is the statute’s analytical backbone: it pushes DHS to map technical, legal, and operational gaps that a future bilateral agreement would need to address, while also flagging privacy and civil‑liberties risks tied to expanded UAS or C‑UAS deployments.
No additional funds authorized
States that the Act does not authorize new appropriations. That constraint effectively ties pace and scale of any Program to existing budgets or to separate appropriations decisions by Congress, creating a practical constraint on implementation and a political lever for oversight.
This bill is one of many.
Codify tracks hundreds of bills on Foreign Affairs across all five countries.
Explore Foreign Affairs in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- U.S. and Canadian law enforcement agencies — gain a formal mechanism to coordinate aerial responses and share operational plans, potentially shortening response times for cross‑border incidents and improving situational awareness.
- Border communities and local first responders — may see faster assistance during aviation emergencies or cross‑border incidents because integrated operations facilitate cooperative rescue, pursuit, or interdiction efforts.
- Federal homeland‑security planners and analysts — receive mandated UAS reporting and structured interagency coordination authorities that can clarify threat vectors and inform procurement or doctrine decisions.
Who Bears the Cost
- DHS components and partner agencies — must absorb training costs, adapt operational doctrine, build communications protocols, and reallocate existing appropriations to implement Program obligations without statutory new funding.
- Canadian partner agencies — must reconcile domestic legal constraints with joint operations and may face additional operational and liability exposure when acting under a bilateral regime.
- Civil‑liberties and privacy oversight entities — will need to monitor compliance, review training and incident records, and potentially litigate or investigate to enforce the statutory protections the bill requires.
Key Issues
The Core Tension
The central dilemma is between operational effectiveness and legal/constitutional constraints: integrated aerial operations promise faster, more coordinated responses to cross‑border threats, but extending law‑enforcement activity across national airspace and sharing surveillance data with a foreign government risks eroding sovereignty guardrails and individual privacy unless tightly constrained and funded.
The bill deliberately leaves major operational decisions to a negotiated bilateral agreement, which creates both flexibility and uncertainty. Flexibility allows the two governments to tailor arrangements to operational realities, but the lack of statutory detail on rules of engagement, evidence collection, or cross‑border arrest authorities risks producing legal gray zones.
If the bilateral text grants permissive authorities without clear limits, courts and oversight bodies could face disputes over jurisdiction, admissibility of evidence, and accountability for use‑of‑force incidents.
The funding prohibition is consequential. By not authorizing additional appropriations, Congress forces agencies to implement any new obligations within current budgets or to request separate funding later.
That creates a practical bottleneck: training programs, communications upgrades, and procurement of counter‑UAS equipment all carry costs that, if unmet, will limit the Program’s scale or effectiveness. Finally, the bill requires public reporting on UAS threats but allows a classified annex, which creates a transparency trade‑off—sensitive operational details can be withheld from public view while still shaping policy, complicating external oversight and public trust.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.