Incident Register
A log of operational incidents, near-misses, notable administrative events, and things that happened that did not fit neatly into a mission report. C. Morrison knows about all of these. Most have their own folder. The folders are maintained by L. Sandhu. The folder system has its own shelf.
Full incident log
Filter by category below. Click any incident row to expand the full record. Incidents are listed in reverse chronological order. A. Kowalski updates the register when incidents occur and during the quarterly review with L. Sandhu.
| Ref | Date | Category | Status | Incident |
|---|
Incidents of particular significance
The following incidents are highlighted by A. Kowalski as being of operational, regulatory, or general significance. L. Sandhu has reviewed all of them. L. Sandhu has a folder for each one. The folders are cross-referenced.
OCELOT declared offline
At 09:14 on 3 August 2023, OCELOT ceased responding to operational commands. T. Davies attempted reconnection at 09:16. The attempt failed. Further attempts have been made every day since. The current count exceeds 1,400. All attempts have failed. This is the incident from which all subsequent OCELOT incidents originate.
2017 object approached without authorisation
The classification-pending object in the 2024 zone was approached without operational authorisation. The approach was not sanctioned by M. Hargreaves or L. Sandhu. Access was denied. The incident has been entered into the register. M. Hargreaves has said what she had to say. This is the third entry of this type in the register. The previous two are INC-2022-055 and INC-2020-018.
ORC-V3 Marigold: maintenance scope expanded (third time)
On 2 April 2026, S. Okafor notified A. Kowalski that the scope of ORC-V3 Marigold’s unscheduled maintenance had expanded for the third time. The original maintenance was initiated in March 2026. S. Okafor has declined to comment on the specifics. Finance has commented on the budget implications. Finance has received no response from S. Okafor.
Rival operator sector agreement dispute
Following mission ORC-2025-056, in which a rival operator was present at the retrieval target before ORC’s arrival, a formal sector agreement dispute was submitted to the ORS. The dispute was submitted in October 2025. The ORS acknowledged receipt in November 2025. The ORS has not yet issued a finding.
About the register
The ORC Incident Register has been maintained since 2014. The register was maintained in OCELOT from 2014 to 2023. Since August 2023, the register has been maintained manually by A. Kowalski. The format has not changed. A. Kowalski prefers it this way.
What gets logged where
| Category | Definition |
|---|---|
| OCELOT | Any incident relating to OCELOT system status, reconnection attempts, or OCELOT-dependent processes that have had to be handled manually. T. Davies is copied on all OCELOT incidents. |
| FLEET | Incidents involving ORC vehicles — maintenance, operational anomalies, scheduling changes. S. Okafor is informed within 24 hours. |
| ADMINISTRATIVE | Internal process failures, outstanding forms, equipment requests, and unresolved administrative matters. A. Kowalski logs and monitors these directly. |
| REGULATORY | Incidents with a regulatory dimension — sector agreement disputes, ORS correspondence, compliance concerns. L. Sandhu is notified for all regulatory incidents. |
| CLIENT | Client behaviour, complaints, or communication incidents during or relating to active missions. A. Kowalski handles initial contact. |
| CLASSIFIED | Incidents involving objects or information of unknown or contested classification. L. Sandhu and M. Hargreaves are notified. C. Morrison is briefed but may not report on these. |
How status is assigned
| Status | Meaning |
|---|---|
| ONGOING | The incident is active. Action is being taken or monitoring is in progress. The register entry is updated at each quarterly review. |
| RESOLVED | The incident has been addressed to the satisfaction of the relevant parties. L. Sandhu confirms resolution for regulatory incidents. A. Kowalski confirms for operational incidents. |
| PENDING | The incident has been logged but the appropriate action has not yet been determined. L. Sandhu is typically consulted before a pending incident is advanced. |
| CLOSED | The incident is no longer active but was not formally resolved — either because the window for action passed or because resolution was not possible. |
| NOTED | Used for incidents that cannot be formally resolved due to classification constraints. The incident is acknowledged and logged. It is not discussed further. L. Sandhu has a file. |