## What MNTS is building toward: in-orbit servicing enabled by proximity operations Momentus positions its longer-term product roadmap around “in-orbit servicing” (inspection, refueling, life extension, repositioning, salvage, maintenance/repair, de-orbiting), and explicitly ties that roadmap to acquiring the ability to “maneuver in close proximity to other spacecraft” and physically interact (e.g., grapple/dock/berth) via future vehicle upgrades (e.g., robotic arms). ["In-Orbit Servicing"](0001781162-25-000008|0) ["maneuver in close proximity"](0001781162-25-000008|0) That matters because “formation flying,” rendezvous, and proximity operations (often grouped as RPO) are not “nice-to-have demos”—they are core enabling capabilities for (i) on-orbit servicing and (ii) any credible path to reusability / multi-client missions where a vehicle can complete one delivery, then approach another object/satellite to provide additional services. ["Rendezvous and Proximity Operations"](0001781162-23-000057|1) ["in-orbit maintenance and refueling"](0001781162-23-000057|1) ## Disclosed RPO approach: release a satellite, then close in and hold relative distance (a “formation-like” demonstration) In MNTS’s disclosed RPO demonstration concept, Momentus planned to **release a satellite** and then **maneuver its Vigoride Orbital Service Vehicle into close proximity**, including attempting to **maintain relative distance** using an RPO sensor suite. ["plans to release a satellite"](0001781162-23-000013|2) ["attempt to maintain relative distance"](0001781162-23-000013|2) Separately, MNTS described an RPO demo (framed as a “new Momentus capability”) with direct applicability to “inspection, servicing, refueling, and de-orbit missions,” again using the “release a satellite then maneuver into close proximity” construct. ["Rendezvous and Proximity Operations demonstration"](0001781162-23-000059|0) ["release a satellite and then maneuver"](0001781162-23-000059|0) **Analytical implication:** Even where filings don’t use the exact phrase “formation flying,” MNTS’s disclosed test objectives (close approach + maintaining separation) are directionally consistent with the minimum viable building blocks you’d need for coordinated relative-motion operations between two spacecraft. ["maneuver closer and farther"](0001781162-23-000013|2) ["maintain relative distance"](0001781162-23-000013|2) ## NASA workstream in filings: a sequence of contracts and flight activity that (a) funds platform utilization and (b) creates flight heritage ### 1) NASA Flight Opportunities / Small Spacecraft Technology IDIQ base contract (contracting “on-ramp”) NASA selected Momentus (among 15 companies) to provide flight and payload integration services under an **indefinite delivery / indefinite quantity (IDIQ) base contract**, where actual work depends on subsequent **task orders or delivery orders**. ["selected 15 companies"](0001140361-24-011286|0) ["indefinite delivery / indefinite-quantity"](0001140361-24-011286|0) ["task order or delivery order"](0001140361-24-011286|0) Momentus characterized the IDIQ as a five-year base contract award to provide flight and payload integration services (and noted eligibility to receive task/delivery orders). ["performance period of five years"](0001140361-24-011286|1) ["eligible to receive task"](0001140361-24-011286|1) **Analytical implication:** IDIQ vehicles are often best thought of as a pipeline-enablement mechanism rather than guaranteed revenue—economically, the value is in converting the base award into funded task orders, which is why subsequent contract announcements matter disproportionately. ["IDIQ base contracts allow for contracting"](0001140361-24-011286|0) ### 2) NASA VADR launch-provider selection (dedicated rideshare channel) Momentus disclosed NASA selection to participate as a **launch provider** in the Venture-Class Acquisition of Dedicated Rideshare (VADR) contract, and stated it executed the VADR contract with NASA. ["selected the Company"](0001781162-24-000010|0) ["executed the VADR contract"](0001781162-24-000010|0) **Analytical implication:** VADR aligns with payload classes that include CubeSats and higher risk-tolerant payloads, which fits the operational envelope where a “demonstration-first” RPO/servicing capability can get flight reps. ["deliver Class D, CubeSats"](0001781162-24-000010|0) ### 3) NASA-related on-orbit activity already performed: CubeSat deployment for NASA LLITED (with an operational mishap) Momentus disclosed that during the Vigoride-6 mission it deployed **two CubeSats** as part of NASA’s LLITED mission, but those CubeSats were deployed at the intended altitude while at a **different inclination than the intended target orbit**, and Momentus identified the root cause as **human error in mapping a software command** (and implemented corrective actions). ["deployed two CubeSats"](0001140361-25-003793|0) ["different inclination"](0001140361-25-003793|0) ["root cause as human error"](0001140361-25-003793|0) **Analytical implication:** This disclosure is important for evaluating the credibility of future proximity-ops demonstrations: RPO/formation-style operations are software- and procedure-intensive, so MNTS’s own disclosed failure mode (command mapping / human process error) is directly relevant to operational risk assessment. ["mapping of a software command"](0001140361-25-003793|0) ### 4) 2025 NASA contract announcements: hosted payload/platform missions (Vigoride as an orbital testbed) **June 30, 2025 — NASA contract (power system / Hall thruster PPU demonstration):** Momentus disclosed a NASA-awarded contract supporting an in-orbit demonstration of a power processing unit for Hall thrusters (CisLunar Industries payload), and stated it would fly among several payloads aboard **Vigoride 7**, scheduled for launch **no earlier than February 2026** on a SpaceX Transporter mission to LEO. ["awarded a contract"](0001140361-25-024111|1) ["Vigoride 7 Orbital Service Vehicle"](0001140361-25-024111|1) ["no earlier than February 2026"](0001140361-25-024111|1) **Oct 9, 2025 — NASA contract (COSMIC microgravity demonstration):** Momentus disclosed a **$5.1 million** NASA Flight Opportunities contract to support the COSMIC demonstration, where Vigoride would serve as the orbital platform hosting payloads. ["awarded a $5.1 million contract"](0001140361-25-037763|1) ["Vigoride orbital service vehicle"](0001140361-25-037763|1) **Oct 9, 2025 — NASA contract (RDRE thruster demonstration):** Momentus disclosed a **$2.5 million** contract awarded by NASA’s Armstrong Flight Research Center for an on-orbit demonstration of a rotating detonation rocket engine (RDRE), stating Momentus would provide the Vigoride satellite platform and operate it in space so the thruster could be tested in orbit. ["awarded a $2.5 million contract"](0001140361-25-037763|2) ["provide the Vigoride satellite platform"](0001140361-25-037763|2) **Analytical implication:** These NASA items are economically meaningful in two ways: (1) they are direct contract dollars (at least as disclosed for COSMIC/RDRE), and (2) they help keep the platform flying as a government-grade orbital testbed—creating flight heritage and maturing operations, which are prerequisites for higher-value proximity and servicing missions. ["operate it in space"](0001140361-25-037763|2) ["serve as the next-generation orbital platform"](0001140361-25-037763|1) ## How this connects to “in-orbit servicing” and “formation-style” operations (capability logic) 1) **Servicing requires relative-motion competence before robotics.** MNTS’s filings describe the end-state (robotic arms + grappling/docking/berthing), but the nearer-term gating item is reliable close approach/navigation and station-keeping around another object—i.e., RPO. ["robotic arms"](0001781162-25-000008|0) ["maneuver in close proximity"](0001781162-25-000008|0) 2) **Demonstrations are framed as stepping stones to service expansion.** MNTS explicitly described RPO as “key” to expanding services into maintenance/refueling/life-extension/de-orbiting, and also described RPO demonstrations as applicable to “inspection, servicing, refueling, and de-orbit missions.” ["RPO is the key"](0001781162-23-000057|2) ["inspection, servicing, refueling"](0001781162-23-000059|0) 3) **NASA-hosted payload flights can be dual-purpose: payload mission + platform capability maturation.** Even when a NASA award is not itself an RPO mission, flying Vigoride with demanding payload operations (power, comms, mission ops cadence, data return, anomaly response) advances operational maturity, which tends to be a hidden constraint in proximity operations. ["operate it in space"](0001140361-25-037763|2) ["real-time data transmissions"](0001140361-25-024111|1) ## What to watch in upcoming disclosures (filing-driven checkpoints) - **Evidence of task-order conversion under the NASA IDIQ** (new 8-Ks / contract PR exhibits referencing funded task orders rather than base-award eligibility). ["IDIQ base contract"](0001140361-24-011286|1) - **Vigoride 7 execution updates** (launch timing, mission manifest, and any mention of proximity operations demonstrations tied to specific government payloads). ["Vigoride 7"](0001781162-25-000041|0) ["scheduled for launch"](0001140361-25-024111|1) - **Operational risk controls** described post-LLITED deployment error (process controls, software command validation, mission assurance), because RPO missions amplify these same failure modes. ["root cause as human error"](0001140361-25-003793|0)

## What MNTS is building toward: in-orbit servicing enabled by proximity operations Momentus positions its longer-term product roadmap around “in-orbit servicing” (inspection, refueling, life extension, repositioning, salvage, maintenance/repair, de-orbiting), and explicitly ties that roadmap to acquiring the ability to “maneuver in close proximity to other spacecraft” and physically interact (e.g., grapple/dock/berth) via future vehicle upgrades (e.g., robotic arms). ["In-Orbit Servicing"](0001781162-25-000008|0) ["maneuver in close proximity"](0001781162-25-000008|0) That matters because “formation flying,” rendezvous, and proximity operations (often grouped as RPO) are not “nice-to-have demos”—they are core enabling capabilities for (i) on-orbit servicing and (ii) any credible path to reusability / multi-client missions where a vehicle can complete one delivery, then approach another object/satellite to provide additional services. ["Rendezvous and Proximity Operations"](0001781162-23-000057|1) ["in-orbit maintenance and refueling"](0001781162-23-000057|1) ## Disclosed RPO approach: release a satellite, then close in and hold relative distance (a “formation-like” demonstration) In MNTS’s disclosed RPO demonstration concept, Momentus planned to **release a satellite** and then **maneuver its Vigoride Orbital Service Vehicle into close proximity**, including attempting to **maintain relative distance** using an RPO sensor suite. ["plans to release a satellite"](0001781162-23-000013|2) ["attempt to maintain relative distance"](0001781162-23-000013|2) Separately, MNTS described an RPO demo (framed as a “new Momentus capability”) with direct applicability to “inspection, servicing, refueling, and de-orbit missions,” again using the “release a satellite then maneuver into close proximity” construct. ["Rendezvous and Proximity Operations demonstration"](0001781162-23-000059|0) ["release a satellite and then maneuver"](0001781162-23-000059|0) **Analytical implication:** Even where filings don’t use the exact phrase “formation flying,” MNTS’s disclosed test objectives (close approach + maintaining separation) are directionally consistent with the minimum viable building blocks you’d need for coordinated relative-motion operations between two spacecraft. ["maneuver closer and farther"](0001781162-23-000013|2) ["maintain relative distance"](0001781162-23-000013|2) ## NASA workstream in filings: a sequence of contracts and flight activity that (a) funds platform utilization and (b) creates flight heritage ### 1) NASA Flight Opportunities / Small Spacecraft Technology IDIQ base contract (contracting “on-ramp”) NASA selected Momentus (among 15 companies) to provide flight and payload integration services under an **indefinite delivery / indefinite quantity (IDIQ) base contract**, where actual work depends on subsequent **task orders or delivery orders**. ["selected 15 companies"](0001140361-24-011286|0) ["indefinite delivery / indefinite-quantity"](0001140361-24-011286|0) ["task order or delivery order"](0001140361-24-011286|0) Momentus characterized the IDIQ as a five-year base contract award to provide flight and payload integration services (and noted eligibility to receive task/delivery orders). ["performance period of five years"](0001140361-24-011286|1) ["eligible to receive task"](0001140361-24-011286|1) **Analytical implication:** IDIQ vehicles are often best thought of as a pipeline-enablement mechanism rather than guaranteed revenue—economically, the value is in converting the base award into funded task orders, which is why subsequent contract announcements matter disproportionately. ["IDIQ base contracts allow for contracting"](0001140361-24-011286|0) ### 2) NASA VADR launch-provider selection (dedicated rideshare channel) Momentus disclosed NASA selection to participate as a **launch provider** in the Venture-Class Acquisition of Dedicated Rideshare (VADR) contract, and stated it executed the VADR contract with NASA. ["selected the Company"](0001781162-24-000010|0) ["executed the VADR contract"](0001781162-24-000010|0) **Analytical implication:** VADR aligns with payload classes that include CubeSats and higher risk-tolerant payloads, which fits the operational envelope where a “demonstration-first” RPO/servicing capability can get flight reps. ["deliver Class D, CubeSats"](0001781162-24-000010|0) ### 3) NASA-related on-orbit activity already performed: CubeSat deployment for NASA LLITED (with an operational mishap) Momentus disclosed that during the Vigoride-6 mission it deployed **two CubeSats** as part of NASA’s LLITED mission, but those CubeSats were deployed at the intended altitude while at a **different inclination than the intended target orbit**, and Momentus identified the root cause as **human error in mapping a software command** (and implemented corrective actions). ["deployed two CubeSats"](0001140361-25-003793|0) ["different inclination"](0001140361-25-003793|0) ["root cause as human error"](0001140361-25-003793|0) **Analytical implication:** This disclosure is important for evaluating the credibility of future proximity-ops demonstrations: RPO/formation-style operations are software- and procedure-intensive, so MNTS’s own disclosed failure mode (command mapping / human process error) is directly relevant to operational risk assessment. ["mapping of a software command"](0001140361-25-003793|0) ### 4) 2025 NASA contract announcements: hosted payload/platform missions (Vigoride as an orbital testbed) **June 30, 2025 — NASA contract (power system / Hall thruster PPU demonstration):** Momentus disclosed a NASA-awarded contract supporting an in-orbit demonstration of a power processing unit for Hall thrusters (CisLunar Industries payload), and stated it would fly among several payloads aboard **Vigoride 7**, scheduled for launch **no earlier than February 2026** on a SpaceX Transporter mission to LEO. ["awarded a contract"](0001140361-25-024111|1) ["Vigoride 7 Orbital Service Vehicle"](0001140361-25-024111|1) ["no earlier than February 2026"](0001140361-25-024111|1) **Oct 9, 2025 — NASA contract (COSMIC microgravity demonstration):** Momentus disclosed a **$5.1 million** NASA Flight Opportunities contract to support the COSMIC demonstration, where Vigoride would serve as the orbital platform hosting payloads. ["awarded a $5.1 million contract"](0001140361-25-037763|1) ["Vigoride orbital service vehicle"](0001140361-25-037763|1) **Oct 9, 2025 — NASA contract (RDRE thruster demonstration):** Momentus disclosed a **$2.5 million** contract awarded by NASA’s Armstrong Flight Research Center for an on-orbit demonstration of a rotating detonation rocket engine (RDRE), stating Momentus would provide the Vigoride satellite platform and operate it in space so the thruster could be tested in orbit. ["awarded a $2.5 million contract"](0001140361-25-037763|2) ["provide the Vigoride satellite platform"](0001140361-25-037763|2) **Analytical implication:** These NASA items are economically meaningful in two ways: (1) they are direct contract dollars (at least as disclosed for COSMIC/RDRE), and (2) they help keep the platform flying as a government-grade orbital testbed—creating flight heritage and maturing operations, which are prerequisites for higher-value proximity and servicing missions. ["operate it in space"](0001140361-25-037763|2) ["serve as the next-generation orbital platform"](0001140361-25-037763|1) ## How this connects to “in-orbit servicing” and “formation-style” operations (capability logic) 1) **Servicing requires relative-motion competence before robotics.** MNTS’s filings describe the end-state (robotic arms + grappling/docking/berthing), but the nearer-term gating item is reliable close approach/navigation and station-keeping around another object—i.e., RPO. ["robotic arms"](0001781162-25-000008|0) ["maneuver in close proximity"](0001781162-25-000008|0) 2) **Demonstrations are framed as stepping stones to service expansion.** MNTS explicitly described RPO as “key” to expanding services into maintenance/refueling/life-extension/de-orbiting, and also described RPO demonstrations as applicable to “inspection, servicing, refueling, and de-orbit missions.” ["RPO is the key"](0001781162-23-000057|2) ["inspection, servicing, refueling"](0001781162-23-000059|0) 3) **NASA-hosted payload flights can be dual-purpose: payload mission + platform capability maturation.** Even when a NASA award is not itself an RPO mission, flying Vigoride with demanding payload operations (power, comms, mission ops cadence, data return, anomaly response) advances operational maturity, which tends to be a hidden constraint in proximity operations. ["operate it in space"](0001140361-25-037763|2) ["real-time data transmissions"](0001140361-25-024111|1) ## What to watch in upcoming disclosures (filing-driven checkpoints) - **Evidence of task-order conversion under the NASA IDIQ** (new 8-Ks / contract PR exhibits referencing funded task orders rather than base-award eligibility). ["IDIQ base contract"](0001140361-24-011286|1) - **Vigoride 7 execution updates** (launch timing, mission manifest, and any mention of proximity operations demonstrations tied to specific government payloads). ["Vigoride 7"](0001781162-25-000041|0) ["scheduled for launch"](0001140361-25-024111|1) - **Operational risk controls** described post-LLITED deployment error (process controls, software command validation, mission assurance), because RPO missions amplify these same failure modes. ["root cause as human error"](0001140361-25-003793|0)