The archive gets explicit at the missile line
The strongest public capacity language in the current archive is about interceptor output expansion, not about a fully quantified launcher or radar shortfall.
Visual Brief // Brief 21
The interceptor bottleneck: where production pressure shows up first
Europe-facing orders are widening across CAMM, IRIS-T, and David’s Sling pathways. Delivery movement exists, but the strongest public expansion language in the archive shows up where governments and primes talk directly about missile output.
The current archive does not prove a full kill-chain bottleneck map, but it does show where production pressure becomes explicit first: the interceptor line.
7 Dated signals
Signals already normalized into the live archive and reused here.
3 Europe-facing demand lines
Order pressure visible in CAMM, IRIS-T, and David’s Sling pathways.
1 Delivery bridge
System movement is visible, but still sparse relative to demand and expansion language.
3 Explicit interceptor expansions
Where public production pressure becomes clearest in the current archive.
Europe-facing demand is already broadening
The live tracker shows demand across CAMM, IRIS-T SLM, and David’s Sling pathways before the archive can prove a continent-wide production ledger.
That is where pressure becomes visible first
Because the public record turns explicit on missile-output expansion before it turns explicit elsewhere, the safest editorial read is that interceptor pressure surfaces first in visible signals.
Signal ladder
The archive is strongest where the language gets explicit
This is not a full kill-chain bottleneck map. It is a dated readout of where public pressure signals are thin, where they are growing, and where they become direct.
Step 01
Europe-facing demand pull
Orders widen the queue across multiple interceptor families before the archive can cleanly quantify output.
Takeaway
Demand shows up first as growing missile packages and new customer lines.
Caution
These are pressure signals, not direct proof of factory throughput limits.
2023-11-07 Poland
Sky Sabre ORDER VERIFIED
Narew agreement expands Poland's CAMM-family land-defense package
Interceptor family
1,000+ CAMM-ER missiles
Visible signal
Large launcher and missile volumes indicate durable serial demand in Europe.
Why it matters
Poland shows the order book widening at missile scale, not just with a symbolic battery buy.
Delivery window
Program execution underway; exact per-batch window not published in linked release
2023-12 Latvia
IRIS-T SLM ORDER VERIFIED
IRIS-T SLM order for Latvian air-defense buildout
Interceptor family
IRIS-T SLM missiles
Visible signal
European demand extending beyond the Ukraine emergency channel.
Why it matters
IRIS-T demand moves beyond wartime emergency transfer logic into durable European national procurement.
Delivery window
Not published in linked source reviewed
2024-11-12 Finland
David's Sling ORDER VERIFIED
Finnish David's Sling procurement agreement
Interceptor family
Stunner / SkyCeptor family
Visible signal
First export implementation beyond Israel creates a new demand line.
Why it matters
Finland adds a new European demand line for a harder-target interceptor family without publishing a clean output-rate answer.
Delivery window
Implementation active; exact delivery window not published in linked source reviewed
Step 02
Delivery visibility
System movement appears, but public delivery language stays thinner than the order and expansion story.
Takeaway
The archive sees movement into fielding, but not a broad delivery-resolution story.
Caution
One delivery-transition signal does not prove the queue has cleared.
2025-12 France / Italy
SAMP/T DELIVERY VERIFIED
SAMP/T NG first systems moving toward initial deliveries after qualification firings
Interceptor family
Aster 30 B1 / B1NT pathway
Visible signal
Program movement from firing qualification into first deliveries improves visibility on European long-range supply.
Why it matters
The archive does show delivery movement, but it is thinner and more qualitative than the order and interceptor-expansion language.
Delivery window
Early 2026
Step 03
Explicit interceptor expansion
When public statements become direct about capacity, they talk about missile output.
Takeaway
This is where production pressure becomes explicit first in the current archive.
Caution
Explicit missile-line expansion still does not prove the whole kill chain is mapped.
2025-01-16 Israel
Iron Dome PRODUCTION VERIFIED
U.S.-aid-funded contract to expand Iron Dome interceptor output
Interceptor family
Tamir interceptors
Visible signal
Israel MOD explicitly states serial production expansion.
Why it matters
Here the public language gets explicit: the release names interceptor serial-production expansion directly.
Delivery window
Not published in linked source reviewed
2024-12-24 Israel
Arrow 3 PRODUCTION VERIFIED
Arrow 3 interceptor procurement expansion
Interceptor family
Arrow 3 interceptors
Visible signal
Official release explicitly frames this as expanded Arrow 3 interceptor procurement pressure.
Why it matters
Upper-tier pressure is visible through interceptor-procurement expansion rather than through a clean battery-count narrative.
Delivery window
Not published in linked source reviewed
2026-01-29 United States
THAAD PRODUCTION VERIFIED
Framework agreement to expand THAAD interceptor output
Interceptor family
THAAD interceptors
Visible signal
Lockheed says the agreement will quadruple THAAD interceptor production.
Why it matters
The clearest capacity language in the archive is missile-line language: quadrupled interceptor output, not launcher or radar output.
Delivery window
Ramp agreement announced January 2026; exact delivery tranches not published
- The tracker contains explicit interceptor-production expansion language for THAAD, Iron Dome, and Arrow 3.
- Europe-facing demand signals already span CAMM, IRIS-T SLM, and David’s Sling pathways.
- SAMP/T NG delivery movement is visible, but still less explicit than the archive’s missile-line expansion signals.
- The current archive suggests bottleneck visibility appears first at the interceptor line because that is where public expansion language becomes explicit.
- Demand pull and delivery movement are best treated as pressure signals, not as a full quantitative backlog map.
- Do not claim the archive proves a global missile inventory shortfall.
- Do not collapse launcher, radar, integration, and interceptor pressure into one proven metric.
- Do not present upper-tier and lower-tier interceptor families as directly interchangeable.
Methodology
This brief reuses dated procurement, delivery, and production-expansion signals already normalized into the live tracker and system-card archive.
It does not claim to rank launcher, radar, integration, and interceptor bottlenecks quantitatively. It shows the evidence hierarchy visible in the current public record.