Explain It in 30 Seconds
NASAMS combines sensing, command and control, launch equipment and selected missiles in a distributed architecture. The system's value comes from those elements operating together, not from one component independently performing the entire defense task.
The commercial model reflects that structure. Customers procure configurations and support through arrangements involving defined supplier responsibilities. Describing the program as an RTX opportunity does not establish that RTX receives the total value of every national NASAMS purchase.
Where It Sits in the Company
Raytheon's NASAMS-related work belongs within the Raytheon segment. The system is not a separate RTX reportable segment, nor does the cited filing disclose a complete stand-alone NASAMS profit-and-loss statement. [S67]
The partnership boundary matters as much as the reporting boundary. Kongsberg supplies the Fire Distribution Center contribution described in official system material, while Raytheon's role includes AMRAAM and related weapon capabilities. Other equipment and integration responsibilities depend on the actual customer configuration. [S44]
The Problem It Solves
Customers need a coordinated defense capability rather than an inventory of unconnected launchers, missiles and sensors. A system must combine information and equipment through an architecture suited to the customer's procurement and operating requirements.
The distributed approach also creates an integration task: multiple elements must remain compatible and supportable. Modularity has commercial value only if the selected equipment can actually work together and be sustained. A larger catalog of possible components is not the same as a delivered capability.
How It Works — Simple Version
Sensors supply information to the command-and-control structure, which connects with launch equipment and selected missiles. This description establishes the roles without prescribing operational procedures or engagement decisions.
Official material identifies missile options including AMRAAM, AMRAAM-ER and AIM-9X. The presence of several options does not mean every purchased system contains all of them or that configurations can be changed without integration and approval. The specific contract and customer system define what is supplied. [S44]
How the Pieces Connect
NASAMS creates a ground-based demand channel for missile capabilities also connected to other platforms. For AMRAAM, that broadens the commercial relationship beyond new fighter-aircraft production alone.
For the wider system, partner capabilities are complementary rather than interchangeable. Command and control, sensors and interceptors perform different functions. A missile production award can support one part of the architecture while leaving other system purchases and integration work to separate agreements and suppliers.
Who Uses It and Who Pays
- Military operators use the delivered systems.
- Government procurement organizations fund equipment, integration and support, with the contracting structure varying across authorized customer arrangements.
An announced national defense budget is not NASAMS revenue, and a complete system purchase is not necessarily all Raytheon revenue. Identifying the relevant supplier workshare and contract scope is necessary before attributing a financial value to RTX. User demand and the supplier's actual booked work are related but different measures.
What It Depends On
The program depends on partner coordination, compatible interfaces, equipment manufacturing, missile availability and customer schedules. One participant's production success does not independently establish the readiness of the entire system.
Continued support additionally requires configuration knowledge and access to the relevant components. A customer may operate equipment over many years, creating potential upgrade and replenishment demand. The timing and value of that work still depend on funded procurement and the responsibilities assigned to each supplier.
What Depends On It
Customers selecting NASAMS depend on a coordinated delivery rather than separate pieces arriving without integration. Partner suppliers depend on clear technical and contractual interfaces. RTX's missile opportunity depends partly on the architecture continuing to support the selected weapon family.
These connections create durable relationships but also execution risk. A distributed architecture is not automatically simpler to manage commercially. Integration, support and supplier coordination remain real tasks whose costs and timing affect the customer proposition.
Why It Matters to RTX
NASAMS extends Raytheon's participation in layered air defense through partnership rather than exclusive ownership of every layer. It also provides another application for established missile capabilities, supporting potential production and replenishment work over the system's operating life.
That relationship should not be counted twice. A missile order described under AMRAAM and under NASAMS is not two separate sales if it is the same underlying procurement. Product-family exposure and system exposure are different views of a possible transaction, not necessarily additive revenue categories.
Key Milestones
- Joint system development:
Kongsberg and Raytheon established complementary roles within the architecture. [S44]
- Missile integration:
Official material identifies several supported weapon options rather than one universally identical configuration. [S44]
- Installed-system support:
Fielded equipment creates potential maintenance, upgrade and replenishment needs, subject to customer decisions.
- 2026 missile procurement:
What Most People Misunderstand
NASAMS is wholly supplied and owned by RTX
It is a partnered architecture. Kongsberg's command-and-control contribution is central to the official system description. [S44]
A national system purchase equals Raytheon sales
An acquisition can include several suppliers, integration and support. RTX's financial share follows the actual contractual scope, not the total headline procurement value.
Common Questions
Is NASAMS the same system as Patriot?
Can AMRAAM be used in ground-based defense?
Yes. NASAMS is a documented ground-based application. [S44]
Is every missile option included in every configuration?
No such conclusion follows from the family-level product description. The purchased configuration and approved integration define the actual equipment.