Main Operationalwolf 1 1
qTTDp9B.png
137c96eed1-576x0.jpg

RPC-XXX

omega-black.png

Registered Phenomena Code: XXX

Object Class: Omega-Black

Hazards: h-ballistic.png h-mechanical.png h-sapient.png

Containment Protocols: Containment for RPC-XXX is currently impractical due to previous attempts to contain RPC-XXX have resulted unsuccessfully. Communications are to be monitored and tracked for RPC-XXX's prefix location, along with the continuation of communications through morse-code by a set of established protocols. Under no circumstances should communications with RPC-XXX are to be disengaged.

While in communication with RPC-XXX, personnel are to identify themselves as a representative of the British Government and are to ensure RPC-XXX is convinced that the British Government is still functioning and not incapacitated. In the event that RPC-XXX launches it's submarine launch based missiles in international waters, all missiles being launched are to be constantly monitored and missile defense systems on standby in the event of any of the missiles changing its designated course.

Furthermore, if established communications fail to contact RPC-XXX in the period of 4-6 hours, personnel are to directly report it to a Level 3 personnel, and Protocol Ultima Ratio is to be executed and Authority facilities worldwide are to be set on the highest alert for an imminent nuclear strike. (See Addendum XXX.04)

Description: RPC-XXX is a sapient submarine vessel of the Vanguard-class commissioned by the British Royal Navy between early and mid 1990s. While it's existence has been largely denied by the British Government, RPC-XXX was originally one of the five commissioning nuclear-powered ballistic missile submarines (SSBNs) of the Trident nuclear program. Additionally, RPC-XXX was given the pennant numerical designation of S27, and commissioned as HMS Voyage.

RPC-XXX has been classified to Omega due to RPC-XXX's constant evasion from Authority Naval Force and Royal Navy. This is mainly because of RPC-XXX's complicated signaling system that changes daily and could not be retraced to RPC-XXX's prefix location. While there were some instances that RPC-XXX's current whereabouts was able to be tracked, RPC-XXX has been observed to evade vessels by surpassing its maximum crush depth, but inexplicably manages to survive under heavy pressure. Furthermore, many signal operators have reported unidentifiable voices in the background and loud noises, while monitoring RPC-XXX's communications. (See Addendum XXX.03)

RPC-XXX is known to currently stock 16 Trident II SLBMs, each of which has the capacity to carry 48 nuclear warheads. However, on June 23rd, ████, it was reported that 16 Trident II missiles were detected from the coast of Canada and later confirmed to have detonated outside of the Earth's orbit. Four years after that incident, another 16 Trident II missiles have been launched, and again, only to detonate in the Earth's orbit. It's been assessed that RPC-XXX was conducting some sort of simulation in the event that a foreign power has successfully launched nuclear missiles towards the United Kingdom. Furthermore, it's unclear how RPC-XXX replicates all of its 16 Trident II missiles despite it originally being launched in ████. Additionally, this also includes the replication of its spearfish torpedoes. (See Addendum XXX.02)

Addendum XXX.01: Discovery

Officially laid down in September, 1984, and commissioned by the British Royal Navy in 1990, RPC-XXX was the first among the Vanguard-class submarine that were replacing Britain's old SSBN submarines of the Resolution-class in the early 1990s. During its tenure service in the early 1990s, RPC-XXX was mainly assigned to conduct naval patrol and intelligence gathering for Defense Intelligence (DI) over at the Baltic Sea.

In 1992, It was reported that the crew members on board of HMS Voyage, or RPC-XXX, had encountered mechanical and system errors throughout their operations of 1993. Due to this, the Royal Navy ordered a mechanical inspection on the vessel to determine if the issues would interfere with its naval operations. Inspections ensued in March 23rd, but was determined that no mechanical errors could be found.

Since its inspection, RPC-XXX had be reassigned to maritime security, and participated in a naval exercise with HMS Trenchant in August 4th, 1993. However, during naval exercises with HMS Trenchant, communications with the Captain onboard of RPC-XXX had failed to respond following four hours of radio silent. Following the disappearance of RPC-XXX on August 4th, a cover story was developed on the disappearance of RPC-XXX, and references to HMS Voyage was abruptly expunged from all government records.

On June 30th, 1997, Defense Intelligence (DI) had detected an unidentified signal that was broadcasting over at the North Sea. Communications with the unknown signal had been ensued, and it was later revealed to be RPC-XXX's pennant code and serial identification. RPC-XXX had also requested in morse-code to ask and clarify regarding the conditional status of Her Majesty's Government. Following this incident, the matter was immediately transferred and coordinated over to GOI-0224 ("MI13").

Addendum XXX.02: The Atlantic Missile Incident No. 1

Foreword: At approximately 03:27 PM Greenwich Mean Time, on June 23rd, ████, RAF Flyingdales reported a nuclear missile being launched from a submarine vessel of unknown country, and immediately caused the British Government to a RED Bikini State. The following is an audio transcript between an operator from RAF Flyingdales and a commissioned officer from the Ministry of Defence.

Addendum XXX.03 Observation Logs

Surveillance operations took place following an autonomous underwater vehicle (AUV) had located RPC-XXX's location, and had been since used to monitor and observe RPC-XXX through acoustical and photographic oceanography. However, three logs were partially recovered following the AUV taking damage during an incident that resulted in RPC-XXX firing a Spearfish torpedo and destroying some of the data in the process.

The following are logs during the observations of RPC-XXX in ████████, North Atlantic.

Addendum XXX.04 Site Incident Report No. ████

Foreword: On April 23rd, ████, RPC-XXX had instigated on its yearly military simulation in the event of a nuclear strike against the United Kingdom. However, during RPC-XXX's simulation, 4 out of the 16 Trident D5s redirected courses to a four known confirmed Authority installations located within Canada, China, United States, and Uzbekistan.

The following is an interview with Specialist Mike and Field Agent Brown following the incident occurring 0700 hours ago.

« RPC-PREVIOUS RPC | RPC-CURRENT RPC | RPC-NEXT RPC »

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License