Soyuz 7K-OK No.1 | Wikipedia audio article
Channel: wikipedia tts
Date: 2019-05-07

This is an audio version of the Wikipedia Article:
https://en.wikipedia.org/wiki/Soyuz_7K-OK_No.1





Listening is a more natural way of learning, when compared to reading. Written language only began at around 3200 BC, but spoken language has existed long ago.

Learning by listening is a great way to:
- increases imagination and understanding
- improves your listening skills
- improves your own spoken accent
- learn while on the move
- reduce eye strain

Now learn the vast amount of general knowledge available on Wikipedia through audio (audio article). You could even learn subconsciously by playing the audio while you are sleeping! If you are planning to listen a lot, you could try using a bone conduction headphone, or a standard speaker instead of an earphone.

Listen on Google Assistant through Extra Audio:
https://assistant.google.com/services/invoke/uid/0000001a130b3f91
Other Wikipedia audio articles at:
https://www.youtube.com/results?search_query=wikipedia+tts
Upload your own Wikipedia articles through:
https://github.com/nodef/wikipedia-tts
Speaking Rate: 0.81766438119713
Voice name: en-GB-Wavenet-C


"I cannot teach anybody anything, I can only make them think."
- Socrates


SUMMARY
=======
Soyuz 7K-OK No.1 was an unmanned spacecraft of the Soyuz program, originally intended to perform a rendezvous maneouver with Kosmos 133 (Soyuz 7K-OK No.2). After the Kosmos 133 mission failed, the rocket was moved to the launch pad on December 12, 1966 and scheduled to launch on December 14, 1966, 4 PM local time.At ignition, one of the strap-on boosters failed to start and so an automatic command shut down the core stage and remaining strap-ons. Launch personnel began safeing the booster in preparation to take it down from the pad for examination. About 27 minutes after the aborted launch, the launch escape system suddenly activated. The Soyuz descent module was blasted free of the stack and touched down a quarter mile from the pad. Meanwhile, the exhaust from the LES caught the third stage of the booster on fire. Flames began curling down the side of the booster as launch personnel ran for cover. After a few minutes, the core stage and strap-ons exploded, completely destroying the entire launch vehicle and causing major damage to LC-31. One person on the ground was killed and the pad was not used again for seven months following the disaster.Since tracking cameras around LC-31 had been turned off when the launch aborted, there was no film footage of the fire or explosion for analysis, but telemetry data found that the igniter in the Blok D strap-on had failed to activate. This was a minor problem and could have been easily fixed by simply installing a new igniter. The bigger question was why the LES activated. Initially, it was suspected that the booster had been bumped when the gantry tower was put back in place following the abort and that this somehow managed to trigger the LES, but a more thorough investigation found a different cause. During the attempted launch, the booster switched from external to internal power as it normally would do, which then activated the abort sensing system. The Earth's rotation caused the rate gyros to register an approximately 8° tilt 27 minutes after the aborted liftoff, which the abort sensing system then interpreted as meaning that the booster had deviated from its flight path, and thus it activated the LES. The abort sensing system in the Soyuz was thus redesigned to prevent a recurrence of this unanticipated design flaw. On the other hand, the LES had also worked flawlessly and demonstrated its ability to safely pull cosmonauts from the booster should an emergency arise as it did years later in the Soyuz T-10-1 abort.
One more mystery remained, which was why the LES had ignited the third stage on fire, something it was not supposed to do. The conclusion was that when the Soyuz descent module separated from the service module during the abort, it had inadvertently severed coolant lines in the service module, which then leaked out their highly flammable contents and started a fire when they were contacted by the LES exhaust.