
“When the pressure hits, you do not rise to the occasion. You fall to the clarity of your role.”
You came out of Mission One with the roles assigned and the console learned. Mission Two puts both against a live tasking, where the window is short and the product at the end has to be right first time.
BRIEF THE MISSION
Mission Two is a working Earth-observation flight over two tasking regions, run at four times speed across a much longer window, with four ground stations coming into view and leaving it again. Nothing is scripted to go wrong here either. The difficulty is the pass itself: short windows, real tasking, and a product at the end that somebody downstream will act on.
- Orbit regime
- Medium Earth orbit, circular
- Altitude
- About 2,622 km
- Inclination
- 26 degrees
- Run
- 9600 seconds at 4.0x
- Ground stations
- Cape Town, Singapore, Honolulu, Santiago
- Scripted events
- None
Earth-observation tasking over the Strait of Malacca and Hawaii.
WHAT YOU FOCUS ON
Mission Two is a working Earth-observation flight over two tasking regions, with four ground stations coming into view and leaving again. Nothing is scripted to go wrong, so every role is judged on discipline rather than on reaction. Click a role to see what it holds this mission.
You run the pass. You open it, you hold the thresholds, and you close it.
- · Confirm contact, the pass timeline and the ground station at the start of every pass
- · Approve safe-mode entry or a spacecraft reset personally, never by delegation
- · Review whether primary tasking completed and whether anomalies occurred, the moment the pass ends
- · Set the escalation thresholds the two operators work to

THE PASS LIFECYCLE
A contact window is short and it does not pause. Crews that improvise inside one lose it. The lifecycle gives every phase of the pass a fixed job, so the crew is deciding what to do about the vehicle rather than deciding what to do next. Click a step for the reasoning behind it.
A pass opens with three confirmations and none of them are commands: that you have contact, that you know the pass timeline, and that you know which station you are working. Commanding into an unverified link is how a crew loses a window, because a command that is not acknowledged has to be reissued and the window does not wait. Confirm first, command second.
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 pass lifecycle 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.
OBSERVE.
Mission Two is complete and scored. Mission Three flies the same kind of work from a different orbit, but the deliverable changes: you are scored on the report you hand up, not on the pass you flew.
