Cinder
Fresh but Wrong
The data look current. Which clock is the mission using?
The next time-dependent action is sequenced against the wrong mission time.
DEMONSTRATION SCENARIO
This is a demonstration scenario. It is not a live demonstration and does not report an executed result.
The situation
Telemetry is fresh and displays look current. Commands and events are being ordered by a governing mission clock.
Displays look current. Events occur at the wrong mission time.
Why this is hard
Fresh displays can hide a wrong mission time, a sample that should be quarantined, or a navigation fault. Those are different repairs. This is not a false position.
Quarantining good samples, or treating the fault as a navigation lie, should not count.
What the operator can see
- FlowData look current
- Open questionTime or the samples
- At riskThe next action
What V8Y must determine
V8Y must distinguish a wrong mission time base from a sample that should be quarantined and from a navigation fault. This is not a false position.
What may happen next
The next time-dependent action is mis-sequenced if the time base stays wrong.
What counts as recovery
Not recovery
Success is not a display that looks fresh.
Recovery
Success is that event times agree with an independent time reference.
Observed results
No executed results are published for this thread.
What this evaluation would test
- Fresh telemetry, with the time question still open.
- Sample quarantine and a navigation fault kept open.
- Not a false position.
- The independent time reference is the edge.
These are the conditions the evaluation would test. They are not reported results.
Operational basis
View operational basis and sources
Derived from Starliner’s first orbital flight: the mission timer was set from the wrong launch-time sample while telemetry continued. A simple offset here is synthetic. The historical poll chain is not reproduced.
Related threads
False Motion Again is a different time problem. Do not treat these as the same repair.
Discuss evaluating this situation
Does your environment face a similar problem?
The request keeps this mission and thread. It is not a claim that the demonstration has been validated in your environment.
The printable flyer is being revised and is not available for download.