đș Part of the Growth List Startup Lists Collection All Startup Lists | By Funding Stage | Sales Outreach | Startup Intelligence
On November 14, 1969, 36 seconds after Apollo 12 cleared the pad at Kennedy Space Center, a bolt of lightning travelled down the Saturn Vâs exhaust trail and into the launch towerâs grounding system. Sixteen seconds later, a second bolt struck. Inside the command module, warning lights lit up across the panel. The fuel cells dropped offline. The inertial platform that kept track of which way was up tumbled into nonsense. Telemetry coming back to Houston turned into garbage.
A flight controller named John Aaron looked at the scrambled data on his console, recognised the pattern, and called out the obscure switch position that would restore telemetry: SCE to AUX.
Nobody else in the room knew what SCE to AUX did. Not the flight director. Not the capsule communicator. Not the commander of the spacecraft, Pete Conrad, sitting on top of a 363-foot rocket climbing through Florida cloud. The only person on the loop who recognised the switch was the lunar module pilot, Alan Bean, who flipped it. The telemetry came back. The fuel cells came back online. The mission continued to the Moon.
The afternoon that mattered was a year earlier
The reason John Aaron knew about SCE to AUX is that, roughly a year earlier, during a routine launch pad simulation, a power glitch produced exactly the same garbled pattern on his screen. Most controllers would have logged the anomaly, waited for the sim to reset, and moved on. Aaron didnât. He went and found the engineer who knew what the Signal Conditioning Equipment did, learned that an obscure auxiliary mode could re-establish telemetry when the main power bus dropped, and filed the procedure away in his head.
That curiosity, on an afternoon nobody else remembers, is the only reason Apollo 12 didnât abort.
What actually happened to the rocket
The Saturn V was effectively acting as a 363-foot lightning rod trailing an ionised exhaust plume back to the wet ground beneath the pad. The first strike at T+36 seconds hit the spacecraft. The second, at T+52 seconds, struck the vehicle again as it climbed through cloud. The currents knocked the three fuel cells offline, scrambled the inertial measurement unit, and dumped the spacecraftâs electrical bus onto battery backup.
Inside the spacecraft, the instruments were lying spectacularly. Dick Gordon, the command module pilot, said it first on the loop: âWhat the hell was that?â Conrad followed a few seconds later. âOkay, we just lost the platform, gang. I donât know what happened here; we had everything in the world drop out.â
Procedural memory in the moment that mattered
The interesting part of the story is not the lightning. Itâs what happened in the 30 seconds after the lightning, in Aaronâs head.
His brain pattern-matched. The scrambled telemetry on his screen in November 1969 looked exactly like the scrambled telemetry heâd seen in a sim a year earlier. He didnât reason his way to SCE to AUX. He retrieved it.
This is procedural memory doing what procedural memory does. Psychology Today describes it as âknowing howâ rather than âknowing thatâ â the ingrained sense of how to complete a pattern of behaviour, often without being able to fully explain how itâs done. Conscious deliberation gets out of the way.
Aaron later said he didnât really have to think about it. The phrase just came out.
Why this kind of retrieval beats deliberation under pressure
Mission Control at T+52 seconds was the definition of acute pressure. Flight director Gerry Griffin came close to calling an abort. An abort at that altitude, with the launch escape tower still attached, was survivable but ugly.
The general principle that gets discussed in cognitive psychology is that deliberative thinking â the slow, conscious, weighing-options kind â tends to degrade under stress, while well-grooved procedural responses tend to hold up. Aaron wasnât weighing options. The answer wasnât sitting in a part of his mind that needed to be calm to access. It was sitting in the procedural system, which is exactly the part of the mind that survives a crisis intact, if youâve done the prep work to put something useful in there.
The prep work, in Aaronâs case, was an unprompted afternoon of curiosity a year earlier.
The switch nobody knew about
SCE to AUX moves the Signal Conditioning Equipment from its primary power source to an auxiliary one, allowing it to operate on lower voltage. When the fuel cells dropped offline, main bus voltage sagged below what the SCE needed. Telemetry from hundreds of sensors stopped being readable in Houston. Flipping to AUX let the SCE function on whatever battery power was available, restored the data stream, and gave controllers the readings they needed to bring the fuel cells back online and realign the platform once the spacecraft reached orbit.
It was an obscure piece of hardware. The switch had a guard cover. Alan Bean had to remember where it was, finding it more or less by feel, while the spacecraft was still ascending.
Why the simulation mattered more than the launch
The Apollo 12 save is usually told as a story about Aaronâs quick thinking. Itâs actually a story about a sim. Without the simulation that produced the matching telemetry pattern, Aaron would have had nothing to retrieve. The procedural memory only existed because someone had bothered, on an ordinary day, to ask what an unfamiliar data signature meant.
NASAâs simulation programme in the 1960s threw garbage at controllers constantly. Sim supervisors would inject failures â burst tanks, dead radios, scrambled telemetry â and watch how the room reacted. Most of the failures never happened in flight. A small number did. The ratio of useful sims to wasted ones is probably impossible to calculate. But the cost of the wasted ones was an afternoon of someoneâs time. The benefit of the one that mattered was Apollo 12.
What this looks like in any high-stakes operation
The pattern repeats outside of spaceflight. Pilots run emergency checklists for engine failures they will probably never experience. Surgeons rehearse complications that occur in less than one percent of cases. Trading desks run drills on market structures that havenât been seen in twenty years. The hit rate on any individual drill is near zero. The hit rate on the corpus of drills, across a career, is what keeps people alive.
The point isnât to remove the stress of the real moment. Itâs to make the right answer the one already grooved into procedural memory before the crisis arrives.
Aaron after the mission
John Aaron went on to play a central role in the Apollo 13 recovery five months later, where he designed the powered-up sequence that brought the crew home on a starving electrical budget. He later directed mission operations for the early Space Shuttle programme.
Conrad himself walked on the Moon five days after the lightning strikes, the third human to do it. Without Aaronâs call, the mission would almost certainly have aborted, and the Surveyor 3 landing site would have stayed unvisited.
The afternoon that doesnât show up in the records
Thereâs no log entry for the moment Aaron walked over to an engineerâs desk and asked about a weird telemetry pattern. No write-up. No memo. The sim ended, the room reset, the controllers went home. The only reason the conversation exists in the historical record is that Aaron mentioned it, years later, when interviewers asked how heâd known what to do.
The most consequential decisions in any technical operation are often invisible at the time theyâre made. They look like curiosity. They look like an extra fifteen minutes spent on something that didnât seem important. They get filed in procedural memory and sit there, unused, for months or years. And then one Friday morning at 11:22 a.m. Eastern, with a rocket climbing through Florida cloud, they come out as five words on a loop and a mission keeps going.
Get a complete database of newly-funded startups delivered every week, with verified decision-maker contacts. Get Leads Every Week
FAQ
Did the lightning actually come from the rocket itself?
Effectively, yes. The Saturn Vâs exhaust plume created a conductive path between the cloud layer and the ground, and the rocketâs body completed the circuit. NASAâs post-flight analysis concluded the vehicle triggered the strikes rather than being hit by pre-existing lightning. After Apollo 12, launch weather rules were rewritten to prohibit flights through clouds capable of producing triggered lightning.
Why didnât they abort?
Flight director Gerry Griffin came close to calling it. The deciding factor was that Aaronâs SCE to AUX call restored telemetry before the abort decision had to be made. Once Houston could read the spacecraftâs data again, the case for continuing was clear â the fuel cells could be brought back online and the inertial platform could be realigned once on orbit.
How did Alan Bean know where the switch was?
Bean recognised the call only because heâd seen the panel layout enough times to locate the switch under a guard cover. Commander Pete Conrad, sitting next to him, had never heard of it. Beanâs familiarity was a small piece of luck stacked on top of Aaronâs.
What happened to John Aaron afterwards?
Aaron stayed at NASA for a 36-year career, including a central role in the Apollo 13 recovery and a later run directing mission operations for the early Space Shuttle programme. The SCE to AUX call is widely taught as a case study in how curiosity during routine training compounds into mission-saving knowledge years later.