NASA Adds Relativity's Terran R to Its Launch Roster
NASA has made Relativity Space's Terran R eligible for future launch task orders under the NLS II contract, an eligibility step rather than a mission award.
NASA has added Relativity Space's Terran R to the list of rockets it can buy launches on. The vehicle joined the NLS II contract through the contract's on-ramp provision, which opens once a year to let new providers in and to let existing contractors add vehicles they had not previously offered. The release announcing the addition carries no date.
What Relativity got is eligibility. Not a mission, not a launch date, not money.
NLS II is a multiple-award, indefinite-delivery/indefinite-quantity contract, managed by NASA's Launch Services Program at Kennedy Space Center. Those contracting terms carry weight and the release does not spell out what they mean, so the reading below is mine rather than the document's. Multiple-award means more than one company holds the contract at once: the roster is a list, not a single winner. Indefinite-delivery means the agency is not committed to buy any particular amount under it. The quantity half says the same about the number of launches.
| Question | Before the on-ramp | After |
|---|---|---|
| Is Terran R orderable under NLS II? | No | Yes |
| Which NASA directorates can order it? | n/a | Human Spaceflight, Science, Research and Technology |
| Can other agencies use it? | n/a | Yes, through NASA; NOAA named |
| Missions assigned to Terran R | n/a | None |
| Task orders placed | n/a | None announced |
| Contract value to Relativity | n/a | Not stated |
The left column of that table is my reading of what an on-ramp does rather than something the release states. What the release says is that an NLS II contract has been awarded to Relativity Space Inc. and its Terran R launch service in accordance with the contract's on-ramp provision. It does not say whether Relativity held an NLS II contract before this, and an on-ramp also covers existing contractors adding a vehicle to a contract they already hold. What the release supports is the right-hand column: Terran R is on the contract now, and NASA can order it for future missions.
A program office decides it needs to launch an instrument. It settles the orbit, the mass and the schedule. The Launch Services Program matches those requirements against the vehicles on NLS II, solicits bids from the contractors whose vehicles fit, and awards a task order to one of them. That company launches. Being on the list puts Relativity in the pool that gets asked. It does not decide which vehicle flies, and it does not skip the competition. This sequence is how the contract type works, not something the release describes.
The dates give the example its shape. NLS II has an ordering period running through June 2030 and an overall period of performance through December 2032. A task order placed in June 2030, at the edge of the ordering window, would have to produce a launch by December 2032 for the mission to stay inside the contract. Order earlier and the margin widens; order later and there is nothing left to order under. That is the constraint a program office would be working against when deciding whether to put a mission out to the vehicles on the list, Terran R included. Both sets of dates are in the release. The arithmetic joining them, and the claim that they constrain a mission this way, are mine.
The reason an on-ramp exists at all is timing. A launch market does not hold still across a period that long. Vehicles enter service and retire inside it, and companies that were not credible bidders when the contract was first awarded sometimes become credible later. The release describes the mechanism: the on-ramp "provides an opportunity annually for new launch service providers to compete for future missions and allows existing contractors to introduce launch vehicles not currently on their NLS II contracts." The complement to that, that NASA reopens the roster annually rather than recompeting the whole contract each time it goes stale, is my reading of why the provision is written that way.
NLS II behaves less like a prize handed out once and more like a supplier list that gets revised every year. A vehicle's absence from it is not permanent. Its presence is not an assignment.
The scope runs wider than science missions. The contract supports NASA's Human Spaceflight Mission Directorate, its Science Mission Directorate and its Research and Technology Mission Directorate. NASA can also use it to buy launches on behalf of other government agencies. NOAA is the one the release names as an example; the release does not say what NOAA would launch under it. For a reader who follows planetary science or Earth observation, the practical consequence is that Terran R can now appear in competitions for NASA missions, and might win one.
Whatever the on-ramp required of Relativity, the release does not say. That gap limits how much can be read into the addition. Acceptance means a company's submission cleared whatever bar the contract sets. It says nothing about the vehicle itself, and this release offers no flight history to check. A reader cannot tell from the announcement how much vetting stands behind the name on the list, as opposed to the ordinary machinery of the contract running its course.
No mission is named, so there is no way to know what class of payload this vehicle would be asked to carry. No task order has been placed, so there is no evidence any NASA mission has been matched to it. No dollar value is given, which leaves open whether the addition carries money at all or is purely a listing. No launch date appears. Nothing technical appears either: not the mass Terran R can lift, not what a launch costs, not whether it has flown or how many times. Those are the numbers that decide whether a list turns into flying. Nor does the release say what Relativity had to demonstrate to qualify, or how many other vehicles have been added the same way.
The next visible step is a task order with a mission name on it.