top of page

Update to Quilty’s Midterm Analysis: The Senate’s Defense Bill

2 minutes ago
10 min read

Nov. 18, 2026

By Kimberly Siversen Burke



An AI-generated image of the U.S. Capitol with a swarm of proliferated LEO satellites crosslinked.
Our safe list survived the Senate’s first draft intact.


Senate appropriators posted their FY27 defense bill on Nov. 16, about eight hours after we published our own post-midterm budget analysis, because of course they did.

The committee’s Republican majority released it without a committee vote, shifting $9.4B for Golden Dome and another $4.8B in Space Force funding out of the reconciliation request and into regular discretionary appropriations. Reconciliation lets Congress tuck mandatory spending (a deceptively reassuring name) into a one-time package, sidestepping the annual appropriations process and line-by-line scrutiny. Regular appropriations put the money — labeled discretionary — back into the base budget for congressional review and approval. The nearly $1.1T bill shifts about $69B of the Pentagon’s one-time mandatory request into the regular budget. In short, Republicans are trying to lock in congressional backing for the money now, before Democrats take control of the appropriations committees in January.

Updates to our report are fairly minor but worth pointing out, since our subscribers barely had a chance to digest our 27-page analysis before the Senate upended our promise not to look at another budget until after Christmas. Beyond pulling some of the reconciliation priorities we flagged as exposed back into the base budget, the bill also preempted the competition rules we expected a Democratic Congress to advance next year.

But none of it is law yet. The bill needs 60 votes on the Senate floor and a deal with the House before the continuing resolution (CR) expires Dec. 11. Another CR would hold the Pentagon’s base budget at about $890B and freeze FY27 new starts. Anything unfinished on Jan. 3 dies with the 119th Congress and gets blue-lined after.

Golden Dome: Less Black Box, More Base Budget

Senate appropriators put $9.39B of Golden Dome funding into the FY27 discretionary budget, shifting more than half of the $17.1B we rated at risk because the White House requested it through reconciliation. The bill brings Golden Dome funding to $9.79B, including the $398M originally requested through regular appropriations. The House Appropriations Committee’s June bill funded only that original $398M.

But the Senate didn’t give the Trump administration the Golden Dome for America Fund it wanted. Instead, appropriators scattered the $9.39B across existing missile defense accounts and a classified annex, moving $367M of the original $398M into the Missile Defense Agency’s midcourse defense research line.

They also stripped the Golden Dome branding off the public funding tables. Each interceptor, radar, and sensor buy sits in a separate budget line, with appropriators setting the dollar amounts and reviewing them annually, and the committee told the Pentagon to keep budgeting Golden Dome that way from FY28 on. So the Pentagon gets a bigger war chest while Congress keeps its hand on the spigot.

The Senate’s approach also answers critics on both sides of the aisle. Sen. Jack Reed (D-R.I.), the Armed Services Committee’s top Democrat, warned in May 2025 that Golden Dome funding headed into the previous year’s reconciliation bill was “essentially a slush fund at this point.” And Republicans had their own objections. At a Sept. 29 hearing, Sen. Mike Rounds (R-S.D.) argued that Golden Dome should never have depended on reconciliation and pressed colleagues to move the money into regular appropriations.

The Senate also wants a second opinion on Golden Dome’s price, from outside the program. The Pentagon’s Cost Assessment and Program Evaluation office must deliver one within 90 days of the bill’s enactment. The Congressional Budget Office estimated in May that a system matching the president’s executive order would cost roughly $1.2T over 20 years — an amount appropriators say doesn’t square with estimates they’ve received from the Golden Dome office.

Space-based interceptors — roughly 60% of CBO’s $1.2T price tag — are nowhere in the bill, the committee’s explanation or its summary. If the Senate funded them, appropriators tucked the money into the classified annex or buried it among the unlabeled increases.

Appropriators Put Sole-Source Deals on Notice

Republican appropriators, whose defense subcommittee Sen. Mitch McConnell (R-Ky.) chairs, threw a flag on the Space Force’s sole-source play for the Space Data Network (SDN) and space-based Air Moving Target Indicator (SB-AMTI) programs. The committee wrote that the service is developing the SDN and an SB-AMTI program that “appears to abandon meaningful competition in favor of sole-source awards.”

As in past years, appropriators contrasted the no-bid contracts of the Space Force and the National Reconnaissance Office (NRO) with the Space Development Agency’s (SDA) practice of splitting successive tranches among multiple vendors to spur competition and keep the industrial base robust — a particularly timely concern after the Government Accountability Office found on Nov. 17 that military and commercial demand for proliferated constellations is straining satellite supply chains.

They drove the point home with the defense secretary’s own words, invoking his Arsenal of Freedom pledge to move the Pentagon away from limited competition and vendor lock.

The committee then funded the multi-vendor on-ramps we marked at risk in our budget analysis because the Space Force had stranded all $940M of them in its reconciliation request. The Senate’s bill would instead provide about $1.5B in the base. Of that, $860.5M funds the SDN’s second delivery order, which builds on the $12M awards Amazon LEO for Government, Lockheed Martin, Northrop Grumman, Rocket Lab, and York Space Systems each received in August.

Another $638M goes to SB-AMTI’s second and third task orders, after Rocket Lab, STR and an undisclosed company split the $615M second order. Notably, Rocket Lab has a toe in both programs.

Then the committee wrote the rule into the bill itself. Sec. 8127 bars the Defense Department from sole-source or noncompetitive contracts above $100M in either program using FY27 or prior-year money. SpaceX’s $6.45B in first-round awards stays on contract, and the Senate moved its expansion into the base, too: $1.33B for SB-AMTI’s first task order and $1.56B to grow the SDN Backbone.

SpaceX still gets paid, but any new award above $100M would have to be competed, which is good news for primes not named SpaceX.

Senate Defunds the Interceptor Network

Senate appropriators zeroed Long Range Kill Chains, a Space Force research account that seems to have changed missions. From FY24 through FY26, it paid for ground moving target indicator (GMTI) sensor and relay payload work with the NRO, and that work has since moved into other budget lines. The account’s entire $1.39B FY27 request funds one new start, SDN–Space Link, a constellation the Space Force designed to plug into the SDN Backbone and serve as the communications layer for Golden Dome’s space-based interceptors.

The Space Force planned a competitive award for Space Link in January 2027, and both defense policy bills and House appropriators funded the effort. But Senate appropriators just went the other way, zeroing out the account without even mentioning Space Link. Then they moved $430M into the SDN’s multi-vendor second delivery order, covering half of that order’s $860.5M, put $250M toward Link 16 support for the SDN, and cut the remaining $712M as money the program could not spend this year. So nearly a third of what the Space Force initially wanted for its interceptor network would instead fund a delivery order shared by the five companies connecting to SpaceX’s SDN. Whether they keep that money depends partly on whether their prototypes can interoperate with the network SpaceX built.

By zeroing Space Link as an interceptor comms layer and shifting about half its funding into broader SDN work, appropriators keep those dollars in the Space Force’s network and sidestep a battle over space-based interceptors, Golden Dome’s costliest piece.

Link 16 Moves Under the SDN

SDA designed its early Transport Layer tranches to deliver data from space to Link 16, the NATO-standard tactical data link that U.S. military and allied nations’ aircraft, ships and ground units have used since the 1990s. SDA chose Link 16 because the radios were already deployed across the force. By March 2022, the Pentagon’s main Link 16 terminal program had delivered more than 14,800 to U.S. forces and more than 59 foreign partners. Using existing equipment skirted a new terminal buy and let SDA move faster than it ever could have if it had developed and fielded an entirely new system.

The Space Force plans to replace that layer with the SDN, which doesn’t support Link 16. Senate appropriators wrote that the omission is “fatally undermining the utility of the network as a tactical communication layer.” So they added $250M to the SDN program to build Link 16 support and ordered the Air Force to keep the requirement in the SDN or any successor.

Watch Items Take the Deepest Cuts

The Senate provided $54.7B for the Space Force, which is $4.4B below the $59.1B base proposal and $800M below the House bill, even after absorbing $4.8B from reconciliation.

Two items on our watch list took the biggest hits:

  • Classified research lost $4.6B. The Space Force asked to grow that account from $6.56B in FY26 to $17.33B without public detail, and we read it as the Pentagon’s catchall for work it would rather not itemize. House appropriators cut $1.26B and Senate authorizers $250M; the Senate appropriators’ cut is nearly four times the House’s.

  • Automate Sat C2 lost $1.3B, leaving just $225M. The $1.52B line is the Space Force’s largest FY27 new start. It pays for Autonomous Tactical Fabric, a ground software program meant to automate satellite command and control (C2) by giving operators shared computing and a common data layer. Most of the early money buys compute infrastructure, with data and AI tools built on top, and the five-year plan totals nearly $7B. Space Systems Command pitched the program to industry in October but has not awarded a contract yet, and as a new start, it can’t be awarded under a CR at all. That left appropriators looking at $1.5B the Space Force cannot spend on schedule, so every defense committee cut it:

    • House authorizers: cut $719M, leaving $805M

    • House appropriators: cut $933M, leaving $591M

    • Senate authorizers: cut $1.5B, leaving about $24M, citing unjustified growth

    • Senate appropriators: cut $1.3B, leaving $225M, citing misaligned acquisition phasing

If Congress funds it, likely players include Palantir, which already supplies Space Systems Command’s C2 data platform; Anduril, whose Lattice software holds a program of record to network the Space Surveillance Network; SpaceX; and a systems integrator to tie it all together.

A few programs that we marked safe also came in below the Pentagon’s request in the Senate’s bill, mostly for acquisition phasing, meaning money a program cannot spend this year:

  • LEO missile tracking: $2.73B, down 23% from the $3.56B request. Of the reduction, $494M for Tranche 4 of the Tracking Layer moved to Next-Gen OPIR Polar missile-warning satellites, which the request zeroed out.

  • MEO missile tracking: $1.02B, down 28% from $1.41B.

  • Space situational awareness systems: $934M, down 29% from $1.32B.

  • Evolved Strategic SATCOM: $1.63B, down 17% from $1.98B, counting research and advance procurement.

  • GMTI procurement: $459M, down 55% from $1.02B. Appropriators explained the cut only in the classified annex to their report, so we can’t really tell whether they killed the money or shifted it to another secret program. They also used the annex to add $82M in advance procurement.

They all stay on our safe list because House appropriators funded each close to the Pentagon’s request. When the chambers negotiate a final bill, we expect the funding to settle somewhere between the House and Senate numbers.

National Security Space Launch climbed to $7.1B for 54 missions. With Vulcan’s Nov. 15 return flight lost and New Glenn grounded since May, SpaceX stands to collect most of that.

One Network, Several Doors

Our read hasn’t changed since MILNET first surfaced in the FY26 request. The SDN Backbone, SB-AMTI, the S-band satellites and the NRO’s pLEO constellation are components of one SpaceX-built architecture, funded through multiple accounts. Most Space Force spending appears in unclassified justification books, while the NRO’s funding is classified and open only to cleared lawmakers and staff. Notably, the Space Force can also put its own money toward NRO contracts, so the dollars show up in its public request while the supplier, price, and terms stay locked up with the NRO.

For SPCX investors, that means the public Space Force budget captures only the visible slice of SpaceX’s government business. A substantial share of its work, and potentially billions more in associated funding, may sit within classified NRO accounts that we can’t quantify and the company doesn’t break out.

The S-band satellites illustrate how the money moves. These are communications spacecraft, separate from Space Link, that relay target data for the Space Force’s space-based GMTI mission. The Space Force funds them through its own procurement account, Auxiliary Payloads, and requested 21 satellites for $241M in FY27, which it plans to buy through its existing relationship with partner agencies. It has not announced a supplier, a contract value, or a competition. We believe the NRO is procuring them under its classified Starshield contract, with the Space Force picking up the bill. In its FY26 research request, the Space Force placed $237M for auxiliary payloads, developed with the NRO to support GMTI, inside MILNET, the joint Space Force-NRO network that evolved into SpaceX’s SDN Backbone. For FY27, it budgeted 21 SDN satellites, the same number as the Auxiliary Payloads buy. They may even belong to the NRO’s pLEO constellation itself, as the communications half of a mixed fleet in which some satellites host radars and others host the radios that move the radar data. That would align the NRO partnership with the GMTI assignment, without requiring any satellite to carry dual payloads.

The Starshield contract would also explain the lower-priced initial buy. In May, we found the Space Force paying $12M apiece for 13 S-band satellites in FY26 and $11.5M apiece for 21 in FY27 — the first 34 of 114 it plans to buy. If the NRO’s Starshield contract already covered spacecraft design, tooling and qualification testing, the Space Force is paying only for extra units off a running production line. The math changes after FY27. The $1.98B budgeted for FY28 through FY31 would buy about 170 more satellites at the FY27 price, so if the buy stops at 114, each remaining one costs closer to $25M.

The Back Door Stays Open

We expect the S-band satellites to carry target tracks from at least two radar constellations. The NRO’s pLEO satellites already support space-based GMTI, and, within two years, the Space Force expects to launch Resilient Radar System-Ground (RRS-G), its own constellation of Northrop Grumman-built GMTI radar satellites developed with the NRO. Because the Space Force assigns the S-band satellites to a GMTI mission, RRS-G will likely route its target data through them rather than through a separate network. The more radar data they handle, the harder they become to break away from SpaceX.

They’re also the piece of this architecture most likely to slip past the Senate’s competition rules. Appropriators left their Auxiliary Payloads line at the $241M requested. Sec. 8127 bars sole-source SDN and SB-AMTI awards above $100M, and the Space Force counts the S-band satellites as SDN satellites. But it funds them outside the SDN line and buys them through a partner agency, so it’s unclear whether the ban would reach them. The NRO gets a lighter touch: the committee directs the Air Force secretary and the NRO director to weigh industrial-base health against schedule and certify that trade-off before approving any sole-source exception.

The Senate bill doesn’t change what we’ve already unearthed by crawling caffeinated and cross-eyed through the FY27 budget maze: the Space Force is picking up a larger share of SpaceX’s government work on its public books. S-band satellites, SDN Backbone capacity, launches and SB-AMTI expansion already sit in FY27 Space Force lines, and some of those spacecraft get pricier in FY28, when the Space Force starts paying its own share of a production line the NRO already bankrolled. What can’t survive a competition mandate in the open budget will move into the intelligence budget alongside the NRO’s pLEO constellation, where the details stay under wraps. If the interceptor communications layer vanishes from the unclassified FY28 request in February instead of returning as a competed SDN order, that’s probably where it went.

###

Quilty White and Blue on Transparent Large
  • X
  • LinkedIn

+1.727.828.7330

info@quiltyspace.com

33 6th St. S, Suite 204  | St. Petersburg, FL 33701 

©2026 Quilty Space. Securities transactions are conducted through Ashton Stewart & Co., Inc., Member FINRA/SIPC, Miami, FL. Certain members of Quilty Space are registered representatives of Ashton Stewart & Co., Inc., which is not an affiliate of Quilty Space. Certain transactions were completed by registered representatives at their prior firms.

bottom of page