Anyone who has worked near spaceflight operations knows the feeling: a telemetry pass goes sideways, the room fills with theories, and within minutes somebody proposes a fix for the first thing that looks broken. Asking why five times is a habit that slows that reflex down. It treats the first explanation as a symptom and keeps pressing until you land on a cause that sits inside your own process, where you can actually change it. This post turns that habit into an audit checklist you can run after any anomaly, whether you work on a student cubesat, a ground segment, or a flight-simulation training programme.
Why the first answer is rarely the answer
When a ground station fails to lock onto a satellite during a scheduled pass, the visible fact is a missed contact. The tempting conclusion is “the antenna misbehaved.” That statement is true in the narrow sense and useless in the practical one, because replacing or recalibrating the antenna will not tell you why the contact was planned the way it was. Asking why again moves you from hardware to scheduling, then from scheduling to the inputs that fed the schedule, and finally to the habit of how those inputs were gathered.
Orbit basics matter here. A craft in a low orbit that circles the planet many times a day gives a ground team short, repeated windows, so a single bad assumption about timing costs a whole pass. A craft parked as described in the piece on holding a fixed position over the equator behaves differently: the geometry is stable, so errors there tend to come from configuration rather than timing. Knowing which regime you are in tells you which “why” questions are worth asking first.
The audit checklist
Use the list below in order. Each item is a question to put to the group, with the answer written down before moving on. Do not skip to the fifth question because you think you already know where it ends.
- State the event in one neutral sentence. Write what was observed, with no cause baked in. “The pass produced no usable data” is acceptable; “the receiver dropped out” already guesses.
- Ask the first why and record the direct trigger. This is the proximate cause, the thing closest in time to the event. Accept it provisionally and mark it as a symptom.
- Ask the second why and look one step upstream. What condition allowed the trigger to occur? Look at the plan, the configuration, or the handoff that preceded it.
- Ask the third why and look at the decision. Somebody or some rule chose that plan or setting. What information did they have at the time, and what did they lack?
- Ask the fourth why and look at the routine. Why did the information gap exist? Usually this exposes a recurring practice, such as a briefing that is skipped under time pressure or a document that is updated by hand.
- Ask the fifth why and stop at something you control. The final answer should name a process step, a missing check, or an unclear responsibility. If it names a person, a vendor, or bad luck, go back one level.
- Write one corrective change at the process level. A new checklist line, a changed order of operations, or a clearer owner. One change, small enough to try next week.
- Set a date to look again. Pick a pass or a review where you will confirm the change was used and whether the original symptom has gone quiet.
One small scenario from a ground team
Picture a university team that operates a small satellite and keeps losing the first few minutes of each contact. The team writes the event plainly: the first minutes of several passes held no usable data.
Why one: the receiver was not tuned correctly when the satellite rose above the horizon. Why two: the tuning values in use were a day out of date. Why three: the values come from a tracking file that is refreshed manually, and the person on shift believed the file had been refreshed overnight. Why four: nothing in the shift handover says who refreshes it or confirms it, so each shift assumes the other did. Why five: the handover is a verbal conversation without a written list, because the team grew from two members to eight and kept the original informal habit.
Notice what happened to the fix. Replacing the receiver, the first instinct, would have cost money and changed nothing. The process-level answer is a single line added to a written handover: refresh the tracking file, record the time, and initial it. That change addresses the cause that produced the symptom for every future pass, not just the ones that were noticed.
Common ways the audit goes wrong
Newcomers to the method stumble in familiar ways, and a decent checklist plans for them.
- Stopping at the first plausible cause. A tidy answer arrives quickly and the meeting ends. Require at least three written whys before anyone proposes an action.
- Blaming a person at level three or four. “The operator forgot” is a description, not a cause. Ask why forgetting was possible and why nothing caught it.
- Branching without noticing. Sometimes a why has two honest answers. Follow each branch separately rather than merging them into a vague sentence.
- Treating five as a rule. The number is a guide. Certain chains finish after three questions, others after seven; the test is whether the final answer names something you can fix.
Where this fits in a training or mission context
The same questions work well in training settings. A student pilot who keeps flying a poor approach in a simulator has an event, a trigger, and a chain behind it. Perhaps the trigger is a late descent. The cause may sit in how the briefing is structured, how checklists are ordered, or how the instructor and student agree on what to rehearse. Asking why in that order keeps the conversation about the process rather than about talent.
If you are curious how other fields lay out their own versions of structured inquiry, directory-style websites that collect procedures and practitioner discussions are worth a look; one example is an orthopaedic directory aimed at medical travellers, with sections for hospitals, physicians, articles and discussion threads. It is an off-topic aside here, nothing more.
Making the checklist stick
A checklist helps only if it is used at the right moment. Keep the audit to a single page, assign a facilitator who is not the person most involved in the anomaly, and time-box the session so it finishes while the details are still fresh.
Review the corrective changes at a regular interval as well. A change that nobody remembers is a change that has quietly expired. If the same symptom returns after the fix, treat that as information: either the chain stopped one level too early, or the fix was never put into daily use.
Finally, keep the tone factual. The goal is to move the room from “who did this” to “what in our routine made this likely.” When that shift happens, reports get more honest, anomalies get reported earlier, and the checklist becomes something the team trusts rather than something it endures. Five questions, asked patiently and written down, are a cheap way to turn a missed pass into a lasting improvement.