Dossier No. 219–27 · Legislative Tracking Passed House, 216–212

Begich voted yes on the provision his own caucus-mate voted down

Section 219 of the FY2027 NDAA hands one country's defense-tech partnership its own Pentagon advocate with override power. Rep. Thomas Massie, Begich's fellow Freedom Caucus member, broke ranks over it. Begich didn't.

H.R. 8800 · 119th Congress Roll Call 278 · July 22, 2026

Briefing

What actually got voted on

The House didn't vote on the United States–Israel Defense Technology Cooperation Initiative. It voted on a $1.15 trillion defense bill that happened to contain it, under a rule that made sure the two questions could never be separated.

Section 219 directs the Secretary of Defense to name a Pentagon "executive agent" charged with expanding and accelerating joint research, testing, and industrial cooperation with Israel across a long list of domains — missile defense, AI, cyber, biotechnology, counter-drone systems, and more. Reps. Thomas Massie and Ro Khanna filed a bipartisan amendment to strike it. The Rules Committee left that amendment out of the structured rule entirely. Members got one choice: the whole bill, provision included, or nothing.

The rule governing debate passed 214–211 on July 21. It excluded the strike amendment before a single word of floor debate on Section 219 occurred.

The Mechanism

Why "executive agent" is the load-bearing phrase

Most of what Section 219 authorizes — joint R&D, coproduction, technology sharing — the United States could already do under existing law. What's new is who decides, and that authority comes from a specific designation buried in DoD Directive 5101.01.

Standard Every other allied partnership — UK, NATO, Japan, Australia — routes through the Under Secretary of Defense for Policy, a neutral, general-purpose channel with no mandate to favor any one country.

Sec. 219 Creates a dedicated executive agent whose statutory job is to expand and accelerate integration — and whose authority takes precedence over other DoD components on related matters, including the office that screens tech-transfer risk.

That last point is the structural risk critics keep returning to: the agency built to say "not yet" on a risky transfer can be overruled by the agency whose entire mandate is "faster."

Case File

Five points where oversight gives way

01

Override authority, not just coordination

The executive agent's precedence authority means it can outrank the ████████████████████████████ — the office that exists specifically to catch risky international technology transfers — on matters touching this one relationship.

02

No capability gap it actually closes

Iron Dome, the Trophy active protection system, Arrow and David's Sling — all built under authorities the U.S. already has: 22 U.S.C. §2767(j)(1), the Arms Export Control Act, standard FMS/DCS channels. The initiative doesn't unlock new access. It installs ████████████████████████████████████ on top of tools that already function.

03

Reporting looks back, not forward

Annual reports and a 180-day interim briefing tell Congress what already happened. Nothing in the text requires notice-and-wait before an individual technology transfer, licensing deal, or co-production agreement is finalized — oversight arrives ██████████████████████████.

04

Entrenchment raises the cost of ever saying no

The deeper co-production runs, the harder a future disagreement is to act on. When Turkey was removed from the F-35 supply chain in 2019 over its S-400 purchase, roughly 1,000 parts had to be re-sourced — ████████████████████████████████████████. Integration is a one-way ratchet unless someone plans the exit first.

05

Aid Congress can cut, replaced by structure it can't

Direct aid gets an annual vote. A standing initiative embedded in acquisition pipelines does not. Critics frame this as part of a broader pattern — alongside a working group created in the FY2026 NDAA and a draft Senate intelligence provision — of converting ████████████████████████████████████████████████████.

Supporters, including the initiative's original bipartisan sponsors, describe it as routine modernization that formalizes cooperation already underway. Both readings agree on what the text does — they disagree on whether that's a problem.

The Vote

Roll Call 278 — and the Alaska seat

H.R. 8800 · On Passage 216 – 212

Republican209 Yea · 7 Nay · 2 NV

Democratic6 Yea · 205 Nay · 1 NV

Independent1 Yea

Rep. Nick Begich (R–AK, at‑large)

Freedom Caucus · missed 1.0% of votes this Congress

VOTED YEA

No separate vote held — the Massie–Khanna amendment to strike Section 219 never reached the floor. Massie, Begich's fellow Freedom Caucus member, broke ranks and voted Nay on final passage specifically over this provision. Begich did not. No public statement from his office addressing Section 219 has surfaced as of this writing.

Status

Where it stands

House Passed, Section 219 intact. This is one chamber — not law.

Senate Parallel text sits in S. 4784 as Section 1217. A procedural vote to begin debate failed 50–46 on July 14, short of the 60 needed.

Conference If both chambers pass a bill, negotiators reconcile the differences. Section 219 could survive, shrink, or disappear there.

Primary sources

• H.R. 8800, FY2027 NDAA, Sec. 219/224 — House Armed Services Committee, Chairman's Mark
• DoD Directive 5101.01, "DoD Executive Agent" (Sept. 3, 2002, as amended)
• Clerk of the House, Roll Call Vote 278 (119th Cong., 2nd Sess.)
• House Rules Committee, H. Res. 1438 and floor rule debate record
• Quincy Institute for Responsible Statecraft, "Cooperation without Oversight" (Policy Note No. 27, June 2026)

Compiled from public legislative records. Supporters and critics of Section 219 dispute its practical effect, not the text of the provision itself; both framings are represented above.