N00019-27-RFI-PMX201-SILENTANVIL RFI.pdf

Request for Information (RFI)

N00019-27-RFI-PMX201-SILENTANVIL

Title: Silent Anvil Air-Launched Torpedo (SAA-LT) StandoƯ Delivery Solutions Issued By: Naval Air Systems Command (NAVAIR), on behalf of Program Management OƯice, Precision Strike Weapons (PMX-201) NAICS Code: 336414 (Guided Missile and Space Vehicle Manufacturing) Date of Issuance: 25 August 2026 Response Due Date: 29 September 2026, 5:00 PM ET

1.0 GENERAL INFORMATION & DISCLAIMER

THIS REQUEST FOR INFORMATION (RFI) IS ISSUED SOLELY FOR INFORMATION AND

PLANNING PURPOSES AND DOES NOT CONSTITUTE A SOLICITATION. THE GOVERNMENT

MAY USE THE INFORMATION RECEIVED TO INFORM A POTENTIAL PROTOTYPE PROJECT

UNDER OTHER TRANSACTION AUTHORITY (OTA), PURSUANT TO 10 U.S.C. § 4022. THIS

ANNOUNCEMENT DOES NOT CONSTITUTE A COMMITMENT BY THE GOVERNMENT. ALL

INFORMATION SUBMITTED IN RESPONSE TO THIS RFI IS VOLUNTARY AND THE

GOVERNMENT WILL NOT COMPENSATE ANY RESPONDENT FOR ANY COST INCURRED IN

DEVELOPMENT OF INFORMATION PROVIDED TO THE GOVERNMENT.

THIS IS NOT A REQUEST FOR PROPOSAL; YET IS A MARKET RESEARCH TOOL TO

DETERMINE POTENTIAL FIRMS CAPABLE OF PROVIDING THE SUPPLIES DESCRIBED

HEREIN PRIOR TO AN ISSUANCE OF A REQUEST FOR PROPOSAL. THE GOVERNMENT IS

NOT OBLIGATED TO PAY FOR ANY INFORMATION RECEIVED FROM POTENTIAL SOURCES

AS A RESULT OF THIS RFI. THIS DOES NOT CONSTITUTE A SOLICITATION AND SHALL NOT

BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT OF ANY KIND. RESPONSES IN

ANY FORM ARE NOT OFFERS AND THE GOVERNMENT IS UNDER NO OBLIGATION TO

AWARD A CONTRACT OR NON-FAR BASED AGREEMENT (E.G. OTHER TRANSACTION) AS A

RESULT OF THIS ANNOUNCEMENT. NO FUNDS ARE AVAILABLE TO PAY FOR PREPARATION

OF RESPONSES TO THIS ANNOUNCEMENT.

ANY INFORMATION SUBMITTED BY RESPONDENTS IN RESPONSE TO THIS RFI IS STRICTLY

VOLUNTARY. FAILURE TO SUBMIT A RESPONSE WILL NOT PREVENT A COMPANY FROM

PARTICIPATION IN ANY FUTURE COMPETITION RELATED TO PMX-201'S SILENT ANVIL

PROGRAM.

CLASSIFICATION OF RESPONSES: ALL SUBMTTED INFORMATION PROVIDED MUST BE

UNCLASSIFIED. ANY PROPRIETARY INFORMATION SUBMITTED MUST BE CLEARLY

MARKED AS SUCH AND WILL BE SAFEGUARDED IN ACCORDANCE WITH APPLICABLE

GOVERNMENT REGULATIONS. ANY INFORMATION SUBMITTED MAY BE REVIEWED AND

USED ACROSS THE GOVERNMENT

2.0 BACKGROUND & ACQUISITION PHILOSOPHY

The Naval Air Systems Command (NAVAIR), on behalf of Strike Weapons Program OƯice (PMX-201), is seeking to determine industry’s capabilities to design, develop, test, and fabricate cost-eƯective, rapid prototyping alternatives for the Silent Anvil Air-Launched Torpedo (SAA-LT).

SAA-LT is a next-generation Anti-Submarine Warfare (ASW) standoƯ delivery system being developed by the U.S. Navy to address emerging threats in undersea warfare. It is designed to expand the range of manned and unmanned aircraft platforms capable of executing ASW missions. SAA-LT will be captive-carried and released from both internal and external aircraft weapons stations utilizing standard Department of War (DOW) carriage systems.

SAA-LT will operate as a precise and highly maneuverable glide weapon, transitioning quietly to target areas to engage enemy submarines from distance.

Prototyping Objectives & Timeline

Demonstration: Demonstrate an end-to-end prototype capability of the SAA-LT system within eighteen (18) months of agreement award

Fabrication: Rapidly assemble and deliver approximately one hundred eighty (180) prototype all-up-rounds (AURs) within the three (3) years following the successful end—to-end demonstration.

Acquisition Pathways

The Navy is exploring two parallel design options and invites industry partners to respond to Option 1, Option 2, or both:

Design Option 1 (End-to-End Solution): A complete, integrated SAA-LT solution from aircraft separation to the underwater target.

Design Option 2 (Wing Kit StandoƯ Design): An unpropelled glide wing kit configured to carry a Government Furnished Equipment (GFE) / Government Furnished Information (GFI) eƯector (torpedo) to the target area.

3.0 REQUIRED CAPABILITIES & TECHNICAL BASELINE

Critical Subsystems Definition (Pending RFI responses):

EƯector (Torpedo) o Acoustics Sensor o Warhead o Command and Control Section o Electric Propulsion System

Flight Components (Wing Kit) o Wing Kit o Radio with Aperture o Guidance and Control

3.1. Compact Design: SAA-LT must maintain a compact, lightweight form factor similar to the GBU-39 Small Diameter Bomb (SDB) to maximize aircraft carriage options across multiple manned and unmanned platforms.

a. Class: 250-pound class munition

b. Maximum Weight: 268 pounds (complete weapon system)

c. Maximum Length: 70 inches

d. Maximum Diameter: 7.5 inches

e. Speed and Maneuverability: SuƯicient to engage submarine targets of interest

3.2. SAA-LT System Characteristics

The SAA-LT system must integrate guidance, navigation, and control (GN&C) and targeting systems to enable kinetic strikes against submarines in littoral environments.

a. SAA-LT deployment range (aircraft to target): The Government is seeking industry input on the maximum standoƯ glide range achievable. (Note:

Respondents should outline expected range curves in their submission.)

b. SAA-LT shall maximize aerial flight endurance while minimizing aquatic immersion time, restricting water residence strictly to the minimum duration required for successful mission execution.

c. SAA-LT shall be capable of a mission kill.

d. SAA-LT environmental characteristics:

1. Shall operate in standard military aircraft flight environments within the proposed aircraft environment.

2. Shall be US Navy Carrier storage, handling, and launch capable.

3.3. Air-Launched Capable (T): SAA-LT will be designed for air-launched deployment from applications that include manned and unmanned aircraft, internal and external carriage. Additional aircraft integration requirements include:

a. Carriage: Must be compatible with the BRU-61/A bomb rack.

b. Aircraft Electrical Interface - Universal Armament Interface (UAI) compliant.

c. Mission Planning: SAA-LT will be compatible with current Navy aircraft mission planning applications.

d. Subsonic Release

Figure 1. Template altitude vs. range plot for multiple SAA-LT deployment speeds.

Release Speed Release Altitude Range (kft) Expected Range Over Ground (nm) Mach 0.25 10 to 60 Industry to propose expected performance Mach 0.50 10 to 60 Industry to propose expected performance Mach 0.85 10 to 60 Industry to propose expected performance

3.4. Modular Payload & Open Systems Architecture :

The SAA-LT program is built upon a Weapons System Open Architecture (WOSA) approach.

a. SAA-LT is planning to utilize a modular design with Government-owned interfaces and standard software interfaces to enable rapid, low-cost modifications, allowing for customization of its payload to meet specific mission requirements.

b. SAA-LT will be designed to be modified, and reconfigured should the USN or USAF seek additional capabilities. System modeling may leverage Cameo as its Model-Based Systems Engineering (MBSE) tool and employ Cameo’s “Black Box”/White Box architecture.

3.5. Networked Capability:

Al tit ud e

(k ft

Distance over ground (nm)

Deploy Speeds

M = 0.25 M = 0.5

M = 0.85

a. SAA-LT must integrate with the Department of War’s (DoW) broader warfare systems, using Tactical Command and Control Systems, taking advantage of coordinated operations and enhanced situational awareness, and receiving In- Flight Target Updates (IFTU).

b. The system may utilize the standard Small-Form-Factor Weapon Attritable Radio Multi-Mode software defined radio to enable the Beyond Line of Sight (BLOS) communications link.

3.6 Logistics and Sustainment:

a. Packaging: Shipped and stored in standard, fully qualified, environmental shipping containers.

b. Built-In Test (BIT) Must be capable of performing BIT Testing:

1. While secured inside the storage container.

2. On the aircraft flight line prior to take oƯ.

3. In-flight prior to weapon release

3.7 Design Option 2 – Wing Kit/EƯector Specific Design Considerations

Under Option 2, the SAA-LT system is comprised of two top-level subsystems: an unpropelled, gliding wing kit (vendor developed) and an eƯector payload torpedo (GFE/GFI). The U.S. Navy is assessing the feasibility and requirements for the wing kit that will glide from weapon release at various altitudes and speeds to a designated target area carrying the eƯector payload.

3.7.1 The Wing Kit Functions:

a. Aircraft Integration (physical & electrical)

b. Carry the EƯector – stored on aircraft & in-flight

c. Communicate (with aircraft, BLOS, & EƯector)

d. Navigate – calculate appropriate splash point & update in-flight

e. Controlled flight

f. Aircraft separation

g. EƯector delivery & separation

h. Provide power (wing kit & EƯector initiation)

3.7.2 The Government EƯector Physical & Launch characteristics:

a. EƯector Weight: 175 pounds

c. EƯector Dimensions: Length: 68 inches | Diameter: 6.75 inches

e. A sabot (protective nose cover) will be part of the captive carried and in-flight configuration. It is designed to separate from the eƯector upon water entry. Physical characteristics of the Sabot:

1. Diameter: 7.25 inches

2. Length: 12 inches (covering approx. 10 inches of the EƯector’s nose)

3. Weight: Less than 4 pounds

f. Body Constraints: There are no physical mounting points on the EƯector’s body. It is smooth to optimize in-water performance.

g. EƯector Release & Water Entry Parameters: To ensure the EƯector is able to execute the in-water portion of the mission, the wing kit will need to release the EƯector at the splash point given the following characteristics:

1. Water entry angle: 45 – 90 degrees

2. Water entry velocity: 40 -120 feet per second

3. EƯector must remain nose down from wing kit release to water entry to ensure sabot stays on

4. Max altitude of release: Vendors should specify their recommended altitude release limits to achieve stable entry.

h. Power Initiation: Approximately 30 seconds prior to EƯector release, the wing kit will provide power to the EƯector. EƯective peak power draw will be 265 watts (average) and 30 watts (peak).

i. Pre-Launch Force Limits: After power is applied to the EƯector, the following force limitations will need to be included:

1. Body-frame angular rates (magnitude): < 1000 degrees per second

2. Body-frame accelerations (magnitude): < 30 g

3.7.3 The physical design limitation for the Option 2 - Wing Kit/EƯector AUR design:

a. Weapon Class: 250-pound class munition

b. Total AUR Weight: 268 pounds (complete weapon system)

c. Maximum Length: 70 inches

d. Maximum Width: 7.5 inches

e. Maximum Height: 9.5 inches

4.0 INFORMATION REQUESTED FROM INDUSTRY

Interested parties are requested to provide a Capabilities Statement (CS). The CS shall be limited to 10 pages (including tables of content, definitions lists, etc.) for a single design option submission and no more than 20 pages if providing a solution for both design options. The CS shall address the following:

4.1 Corporate Capability & Experience

Provide company name, address, CAGE Code, UEI, business size status, and socio-economic classification.

Provide facility security clearance level (current or in-process). Selected performers must be capable of performing at the SECRET level during all phases.

Describe experience with similar standoƯ warfare systems, particularly glide munitions, flight kits, or integrated aerial weapons.

Describe experience with underwater environments, munitions, sensors, and subsystems.

Describe experience with weapons integration on naval aircraft including Universal Armament Interface (UAI), physical carriage integration on BRU-61/A bomb racks, or similar multi-carriage bomb rack units.

Describe experience with energetics handling, safe separation designs, and secure facility operations.

4.2 Technical Approach & Design Alternatives

Baseline Configuration Feedback: Detail your conceptual approach to addressing the performance requirements in Section 3.

Architecture: Describe your solution’s architecture (hardware, software, and interfaces), theory of operation, technical assumptions, and performance characteristics.

System Maturity (TRL): Provide the pertinent Technology Readiness Level (TRL) for the overall system and critical subsystems utilizing the definitions in Table 1.

Level Definition TRL 9 Actual system proven through successful mission operation.

TRL 8 Actual system completed and qualified through test and demonstration.

TRL 7 System prototype demonstration in an operational environment.

TRL 6 System/subsystem model or prototype demonstration in a relevant environment.

TRL 5 Component and/or breadboard validation in a relevant environment.

TRL 4 Component and/or breadboard validation in a laboratory environment.

TRL 3 Analytical and experimental critical function and/or characteristic proof of concept.

TRL 2 Technology concept and/or application formulated.

TRL 1 Basic principles observed and reported.

Table 1: Technology Readiness Level (TRL) Definitions Table

4.3 Schedule, Producibility, & Scaling

Prototyping Schedule: Provide a realistic target date and high-level schedule to perform an end-to-end demonstration of your system.

Manufacturing Capacity: Describe your ability to scale prototype production to 60 AURs within one year after an initial demonstration with the capacity to maintain a minimum of 60 AURs per year for another 2 years (total of 60 AUR’s per year for 3 years).

Supply Chain Resilience: Describe your manufacturing approach, supply chain resilience, and logistics plan to support a low-cost, scalable production process.

4.4 Cost Parameters (ROM)

Provide a rough order of magnitude (ROM) cost estimate for the rapid proof-of-concept demonstration eƯort (~18 months).

Provide a rough order of magnitude (ROM) cost estimate for the design, development, integration, and qualification testing, and fabrication of your provided solution.

Provide a rough order of magnitude (ROM) cost estimate for the per unit cost of a prototype production unit.

4.4 Risks & Mitigations

Identify the top 3-5 technical, programmatic, and industrial base/supply chain risks to successfully delivering this capability.

Propose practical, actionable risk mitigation strategies for each identified risk.

5.0 DISCLAIMER

Any information received in response to this request will be properly protected and handled accordingly. In order to complete its review, NAVAIR must be able to share information within the Government.

6.0 RESPONSE SUBMISSION

6.1 Submission Instructions

All responses shall be submitted via email in Microsoft Word or Adobe PDF format to the points of contact below no later than 5:00 PM ET on 29 September 2026. Responses to this RFI are not to exceed 10 pages in length (unless submitting technical solutions to both options in which case submissions are not to exceed 15 pages) on 8.5X11 inch paper with one-inch margins and font no smaller than 10 points Times New Roman.

Primary POC: Joseph Perriello, Contract Specialist, joseph.c.perriello.civ@us.navy.mil

Secondary POC: Raymond Cannon, Procuring Contracting OƯicer / Agreements OƯicer, raymond.c.cannon2.civ@us.navy.mil

6.2 Additional Information

Questions regarding this RFI shall be submitted via email to the primary point and secondary point of contact. The Government is not obligated to respond to questions submitted by industry as part of this RFI.

The Government is not accepting phone calls regarding this RFI prior to deadline for submissions. However, the Government is intending to host an Industry Day for further market research and to provide vendor’s the opportunity to seek clarification of the required capability being sought in this RFI. The Government also anticipates holding one-on-one sessions at the SECRET level with interested vendors after receipt of RFI submissions. The Government may elect to arrange additional meetings/phone calls with vendors to conduct further market research at its discretion.

Classified material SHALL NOT be submitted. All submissions shall include this RFI Reference Number, company name, company address, CAGE code, Unique Entity Identifier (UEI) number, and a point of contact information (including name, position, phone number, and email address) who is able to discuss the Capability Statement submitted.

All information submitted will be adequately safeguarded from unauthorized disclosure.

The Government will not accept responses marked with Distribution F per DoDI 5230.24.

Responses that fail to comply with the above instructions or present ideas not pertinent to subject, may not be reviewed. All information received in response to this Notice that is marked proprietary will be handled accordingly. Information submitted in response to this RFI is submitted at no cost to the Government and will not be returned. The Government is under no obligation to provide responses or comments to information received from interested parties.

The Government is considering utilizing the Naval Air Systems Consortium (NASC) to potentially award one or more OTAs pursuant to 10 U.S.C. 4022 “Authority of the Department of Defense to carry out certain prototype projects”. Note: If an interested person is a foreign concern or if a U.S. interested person has a team member or partner who is a foreign entity, adherence to all International TraƯic and Arms Regulations (ITAR) is required.

6.2.1 Industry Day

The Government will host an Industry Day through the NASC to conduct market research and provide clarification to industry on information relating to this RFI. The PMX-201 SAA- LT Industry Day will be held in person at the Curtis North and South Conference Room, 22290 Exploration Drive, Lexington Park, MD 20653 on 17 September 2026 from 0800 to 1600 ET. For registration and additional information, please visit the NASC website (nascsolutions.org/upcoming-events). Failure to participate in this industry day event will not prevent a company from future participation in any competition relating to PMX-201’s Silent Anvil program.

6.2.2 One-On-Ones

The Government is intending to provide one-on-one sessions that may discuss information at the Collateral Secret Level after the Industry Day. As part of your response to the RFI, reply that you are interested in attending a one-on-one session and provide a POC for the company to coordinate scheduling a session. Prior to scheduling a one-on-one, NAVAIR Security must vet companies and individuals prior to the session. Companies will need to provide the Government with a copy of the company’s DD-254 for any Navy contract and a signed non-disclosure agreement (NDA) Access Form for each person. Furthermore, site-visit requests may be required to be coordinated with your company’s Facility Security OƯice prior to the one-on-one session. These one-on-one sessions are at the discretion of the Government and are intended for further market research. Failure to participate will not prevent a company from future participation in a competition related to the PMX-201 Silent Anvil program.