
“Clean comms on a calm day is the muscle you need on a bad day.”
The mission leader asks what happened, and your facilitator stands in for them. Mission Three is scored on the report you hand up, and on whether you can tell a part that is wearing out from somebody who should not be there.
BRIEF THE MISSION
Mission Three flies the same kind of Earth-observation work as Mission Two, over two new regions, from a higher and more steeply inclined orbit. The flying is familiar on purpose. What changes is the deliverable: this mission is scored on the situation report you produce, not on the pass you flew.
- Orbit regime
- Medium Earth orbit, circular
- Altitude
- About 3,122 km
- Inclination
- 63 degrees
- Run
- 9600 seconds at 4.0x
- Ground stations
- Ankara, Auckland, Bangkok, Santiago
- Scripted events
- None
Earth-observation tasking over the Aegean Sea and the Tasman Sea.
WHAT YOU OBSERVE
The flying is Mission Two's, from a higher and more steeply inclined orbit. What changes is the deliverable: this mission is scored on the situation report, and both operating roles carry the same job of telling a failing part from an adversary. Click a role to see what it holds this mission.
You combine and you cut. Two reports go in, one goes up.
- · Combine the Satellite Operations and Payload Operations situation reports into one
- · Drop the per-step raw telemetry samples and the full command logs
- · Write the single most important line: mission status, whether primary tasking was achieved, and any decision required
- · Carry it to the mission leader

CYBER-RELEVANT OR MAINTENANCE-RELEVANT
Every anomaly you will ever see arrives looking the same: a number that is not what you expected. The work is deciding whether a part is wearing out or somebody is in your system, and the two demand completely different responses. Click a step for the reasoning behind it.
The first line of a report states the mission status, whether the primary tasking was achieved, and what decision is required of the reader. Everything after it is support. A report that builds toward its conclusion works for the writer and fails the commander, who has three other reports to read and will act on whichever one told them something in the first sentence.
FLY THE MISSION IN ZENDIR
Zendir, the digital twin and mission simulation platform Kestrel procured, replicates your satellite operations center. Everything you rehearsed here you now do for real inside it: one mission objective and ten scored questions. The ten questions land on the situation report and the discriminator you just walked. Run it in three steps: take your assigned consoles, fly the one objective and answer the ten questions in platform where they are scored, then note the score and come back here for the debrief. Your facilitator provides Zendir access, and two things must be true before you fly.
This mission is worth 100 points, scored in-platform. Points accumulate across Missions One through Five, and the highest cumulative team finishes as the Top SCOR Team.
NOW THAT YOU ARE BACK
Zendir scored your mission out of 100 toward the Top SCOR Team standings. Note where you landed, then run the debrief while it is fresh. Work these three questions in order; the last one is the one that becomes an engineering update in the quarterly SCOR exercise.
Go around the crew once, one observation each, no discussion until everyone has spoken. Write the observations down before debating them; the first answer is usually the honest one.
DETECT.
Mission Three is complete and scored. Mission Four is the first flight where the platform acts on you: several things go wrong, and they do not all have the same cause.
