Close Calls in Spaceflight: Two Ways to Learn From a Near Miss

Every spaceflight programme eventually meets the same quiet moment: a checklist item was skipped, a valve reading looked odd, or a countdown held for a reason nobody can quite explain afterwards, and then everything turned out fine. That moment is a near miss, and what a team does with it in the following week says more about its culture than any launch-day success. Here are two common habits, weighed against each other, to show which one converts a lucky escape into something worth keeping.

The two habits at a glance

The first habit is the informal one. Someone notices the problem, mentions it at the next stand-up, the group exhales, and the day carries on. The second habit is the written one. The same observation is described in a few plain lines, the weak spot is traced back, and one small change is agreed before anybody forgets the details. Neither approach is dramatic. The difference only shows up months later, when the same weak spot appears again and one team recognises it while the other is surprised.

Crewed flight, cargo flights and satellite operations all rely on long chains of small actions. Each link is trusted because the link before it was done properly. A close call is simply a link that almost slipped, and a slip caught in time costs nothing except attention. That is why it is so valuable: it carries the same cause a real failure would carry, minus the damage.

Habit one: the spoken warning

Spoken warnings have real strengths. They are fast, they cost no paperwork, and they keep a crew relaxed about raising small worries. A technician who feels free to say “that looked wrong” is a technician who will say it again on the day it matters. Teams that punish every admission quickly learn silence, and silence is the most expensive thing in a control room.

The weakness is memory. A spoken warning lives in the heads of the people present. Shifts rotate, contractors move on, and a detail that seemed unforgettable on Tuesday becomes a vague impression by the following quarter. Worse, spoken accounts drift. By the third retelling the near miss has grown a villain or shrunk into a joke, and the original sequence of events is gone. Without the sequence, the fix cannot be aimed precisely.

Habit two: the short written account

The written habit asks for very little: what was planned, what was noticed, what stopped the slip, and which assumption turned out to be shaky. Four short answers, written without blame, usually fit on half a page. The aim is not a tidy archive; the aim is that a month later a different engineer can read it cold and understand exactly where the chain was thin.

Aviation has used this idea for decades, and spaceflight borrowed it. Voluntary reporting channels exist precisely because a pilot who nearly misjudged a descent is far more useful to the next pilot as a reporter than as a statistic. The same logic applies on the ground in a launch operations room. When the account is written plainly and the author is thanked rather than questioned, the next close call arrives in the inbox sooner.

If you want background on the stages a mission passes through, the article breaking down each stage of a spacecraft mission is a useful companion, because near misses cluster at the hand-offs between those phases. Readers new to the launch side can also start with a primer on how a rocket gets a spacecraft up to orbit.

Where each habit works best

A fair comparison admits that the spoken warning wins in the moment. During a countdown there is no time to compose a report, and a clear shout beats a tidy form. Written accounts win afterwards, when the pressure is gone and the facts can be laid out in order. The mistake is treating the two as rivals. The strongest teams use the spoken warning to stop the slip and the written account to learn from it.

  • Speed: spoken wins, since the warning reaches the whole room immediately.
  • Accuracy over time: written wins, because the sequence does not blur.
  • Willingness to speak up: a tie, and entirely dependent on how the team reacts to the first admission.
  • Usefulness to newcomers: written wins easily, since a new hire cannot attend last year’s meetings.
  • Cost: spoken is free; written costs a few minutes that pay back many times over.

A worked comparison: the reading nobody wrote down

Picture a ground team preparing a small satellite for transport. During a routine check the technician sees that a connector label does not match the drawing. The drawing is right, the label is wrong, and the unit is wired correctly, so nothing happens. Under the spoken habit, the technician mentions it over coffee and a colleague relabels the part. Under the written habit, the same technician notes that the label template had been copied from an older revision, and the team replaces the template so every future label is generated from the current drawing.

Only the second team has fixed anything lasting. The first team repaired a single label; the second repaired the process that produced the label. When a different satellite arrives next year with the same template problem on a different connector, the first team meets the issue fresh and the second team never sees it at all.

What a useful near-miss note contains

Good notes share a shape, whatever the organisation. They describe the intended action in one sentence, then the thing that went differently, then what caught it. That last part deserves attention, because the catch is often luck. A colleague happened to glance at the screen, or a rarely used alarm happened to fire. If the only thing between the team and a failure was luck, that is the weakest link in the entire note and the first one to strengthen.

Notes should also record what the team did not know at the time. Many close calls trace back to an assumption nobody had checked, such as a tool setting that everyone believed was default, or a handover where the outgoing shift thought one thing was obvious and the incoming shift never heard it. Naming the assumption makes it visible, and visible assumptions can be tested.

Keeping blame out of the room

A written account only works if the author is safe. The moment a near-miss note becomes evidence in a performance review, the notes will stop, and the team will be back to the spoken habit, or worse, to no habit at all. Phrase every entry about the process rather than the person: the checklist allowed the step to be skipped, the handover form had no space for the open item, the display did not show the unit. Systems can be improved without anyone being embarrassed.

It helps if managers go first. When a team head files a note about their own almost-missed approval, the rest of the group learns that the exercise is genuine. A single honest example from the top of the chain is worth a dozen reminder emails.

Sharing the lesson beyond one team

Close calls are rarely unique to one group. The label template problem above could exist in a dozen programmes using the same document tools. Teams that publish short, de-identified summaries inside their own organisation let others check their own templates without waiting to be bitten. The effort is small, and it turns one team’s lucky escape into everybody’s inexpensive lesson.

Outside the engineering world, the same instinct appears in places you might not expect. Software teams have their own version of this habit, and SRE School, a blog and website on site reliability engineering, sits in that world; the idea of writing down a caught mistake travels well between fields. Reading across fields like that is a cheap way to borrow habits that mission teams already respect.

Starting small

No new tool or budget line is required. Pick one recurring operation, perhaps a pre-transport inspection or a data-handover step, and agree that the next time anything almost goes wrong, whoever notices it writes the four short answers within a day. Review the notes at a regular meeting, choose the single most repeatable weakness, and change one thing about the procedure. Then do the same again the following month.

Over a year this produces a small, honest library of how your operation really behaves under mild stress. A newcomer could get through it in one sitting. Experienced staff will recognise patterns they had half noticed but never named. And when a real anomaly eventually does arrive, the team meets it with fewer unexamined assumptions than before.

The verdict

If you can only afford one habit, choose the written account, because it preserves what the spoken warning loses. If you can afford both, and you can, keep the spoken warning for the heat of the moment and the written account for the calm afterwards. In spaceflight the margin for error is thin enough that every close call deserves to be studied once, for free, before it has the chance to come back as something that is not free at all.