Three Days Early. The Client Was Not Prepared For This.
ORC-V2 “Reg” completed a standard LEO retrieval of a defunct upper stage at 430 km for a UK defence prime client. The object posed a conjunction risk to an active commercial constellation. Pre-mission conjunction analysis was performed and cross-verified. Capture and controlled deorbit were completed three days ahead of the planned schedule. Re-entry was confirmed over the South Pacific uninhabited zone on 02 July 2025. The mission is considered complete and successful.
The object was where the client said it would be. The object had the mass the client said it would have. The attitude state was as characterised. Reg performed the rendezvous without complication. The capture was clean. The deorbit corridor was clear. There were no anomalies. Nothing required escalation. T. Davies, monitoring from ground, described the mission in his log as [REDACTED].
We completed the mission three days ahead of schedule. This is not unusual for ORC. We plan conservatively and execute efficiently. We have been doing this since 2014.
The client’s response to being told the mission was complete three days early was [REDACTED].
The client asked, during the reference call conducted for this report, whether we could guarantee early completion on future missions. The answer is no. We cannot guarantee early completion. We can guarantee that we will not manufacture delays to match the planned timeline. These are different things. The client said they understood. We are [REDACTED].
Re-entry was confirmed at 21:18 UTC on 02 July 2025. Documentation was issued within 14 working days. The documentation noted the early completion. The client asked if the invoice reflected the early completion. The invoice was fixed-price. The answer was yes, and also no, in the sense that the price had not changed but the outcome had. The client found this confusing. We explained it twice.
| Service tier | S-01 Standard Retrieval |
| Vehicle | ORC-V2 “Reg” |
| Altitude | LEO · 430 km |
| Object type | Defunct upper stage |
| Mission duration | 23 days (planned: 26) |
| Days ahead of schedule | 3. Three. The client mentioned this four times. |
| Anomalies | None. Zero. It went exactly as planned, only faster. |
| Characterisation accuracy | Excellent. The object was where they said. This went in our records. |
| Re-entry confirmed | 02 JUL 2025 · 21:18 UTC · South Pacific |
| Documentation issued | Within 14 working days |
| Client questions about early completion | Several. All answered. Same answer each time. |
| Client follow-on missions booked | 1 (pending manifest) |
- Early completion is the correct outcome of efficient mission planning and execution. It is not something we need to apologise for, explain at length, or add a warning about in pre-mission briefings. We have discussed this internally. We remain of this view.
- The client’s statement that ORC was the first contractor to complete a job early in eleven years has been added to the internal record. We have not shared this with the rest of the team because we do not want it to affect anyone’s approach to mission planning. We are sharing it here because this report is external and the team does not read the dispatch archive.
- Reg continues to perform at the highest level. Reg does not receive Employee of the Quarter. Reg is a vehicle. We have addressed this point in a previous report and will not revisit it here.
- The client has booked a second mission. We will complete it on time. Possibly early. We make no promises.