In 1969, lightning struck Apollo 12 seconds after launch; John Aaron’s “SCE to AUX” call restored telemetry and helped save the Moon mission
Apollo 12 astronauts encountered a significant crisis when lightning struck their rocket, not once but twice. A neglected protocol related to the Signal Conditioning Equipment proved to be a lifesaver for their mission. This incident led to import...

The Saturn V SA-507 rocket en route to the launch pad during the Apollo 12 mission. Image credits: Wikimedia Commons

The rocket that accidentally invented its own weather
Apollo 12 did not get hit by an existing storm. Rather, the ionized cloud of hot exhaust created by the rising Saturn V acted like a giant lightning rod and initiated the electrical discharges. NASA's own pre-launch weather rules at the time were built to check for one thing: active lightning near the pad. They had no way to flag a rocket that could trigger its own strike out of a sky that wasn't otherwise showing that kind of activity, which is exactly the gap that let Apollo 12 launch that morning. The 3,000-ton Saturn V itself, and the possibility that its exhaust plume could complete a circuit through a charged but non-stormy sky, simply wasn't part of what forecasters were checking for.
The misunderstanding of such an important factor is precisely why atmospheric scientists were prompted to investigate the process of "triggered lightning". Indeed, a 1989 peer-reviewed paper titled “Natural and Artificially Initiated Lightning,” published in the journal Science, by lightning researchers Martin Uman and E. Philip Krider, cited the Apollo 12 lightning-initiation event as a key early trigger for what had by then become an established field of research into rocket-and-structure-triggered lightning. This led to significant changes in the decision-making process regarding launching into an active storm system for NASA and the US Air Force.
The switch nobody had heard of
Back in Mission Control, the readings seemed cryptic: fuel cell pressures, AC bus voltages, and guidance system information all displaying meaningless values at once, usually meaning a full system malfunction. But the flight controller John Aaron knew better; a year earlier, while working a night shift, he had happened to watch a routine ground test at Kennedy Space Center in which operators accidentally dropped the spacecraft's power. The telemetry that came back wasn't just blank zeros, it settled into the same strange, specific numbers he was now looking at. Curious, Aaron had traced that anomaly on his own time to an obscure piece of hardware called Signal Conditioning Electronics (SCE), and learned that switching it into its auxiliary power mode let it keep working even on low voltage. That's the memory he drew on now.

The unglamorous truth
The real story is not so much about the genius of one man but rather of a system that thought highly enough of its own obscure corner cases to run simulations for them, and of a control room that had somebody paying attention to a tedious test that everyone else may have thought to be boring. In a world where technology companies boast about “moving fast,” Apollo 12 reminds us that living through the unexpected generally requires preparation: someone studying the manual, performing the strange simulation, remembering the edge case scenario, which suddenly became crucial only 36 seconds into flight.
The Economic Times Business News App for the Latest News in Business, Sensex, Stock Market Updates & More.
The Economic Times News App for Quarterly Results, Latest News in ITR, Business, Share Market, Live Sensex News & More.