The Byelokoroviche Base Incident

The account is set at Byelokoroviche in what was then the Soviet Union. It describes a large silent disc some nine hundred feet across holding position for hours over a ballistic missile base. During the sighting the launch-preparation signal lights on the dual control panels are said to have activated without any human input, and the base is described as losing control of its nuclear weapons for roughly fifteen seconds. A four-man commission is said to have investigated the following day.

What is on the record

The archive resolves a single named claimant, Vladimir Platunov, to this event, and the telling comes from one channel. A British Ministry of Defence file was for a time attached to this case as corroboration. In a 2026 audit of every document link in the archive, a full-text check found the file never mentions the base or the incident, so it has been removed. A later report-by-report reading of the released Ministry files did find the story, twice. DEFE 24/2049 holds an April 1996 letter from a South Wales correspondent describing a segment of ABC's Primetime Live on Soviet UFO investigations. DEFE 24/2064 holds a ufologist's letter citing the same report. Both place the base in Ukraine and date the event to 4 October 1982. Neither names Platunov, and neither is a record the Ministry made.

The gaps are large. There is one named witness and one video channel, and the documents amount to a foreign ministry filing letters about a television programme. The most dramatic detail, the loss of weapons control, rests on the telling alone.

Why it sits where it does

The case grades L2, the tier for the same account carried by more than one channel: the video telling, and the television report that reached the Ministry in two letters. The second channel carries the story rather than the man, and it is not corroboration. The tier measures sourcing and never truth. It was previously shown higher on the strength of a document that turned out not to concern it, and the archive corrects itself in public rather than quietly. What actually happened over the base is not resolved here.