Search the Community
Showing results for tags 'incident report'.
Found 6 results
-
Name: Brotimes Rank: Associate Researcher Clearance Level: 3 Date of Incident: 12/24/2021 Describe the incident: Following attempts by MP Tazza to fish in SCP-354 a large serpentine entity, hereafter referred to as SCP-354-19, was "caught" and appeared in SCP-354's containment chamber. MTF units were immediately called to the scene, securing the object and running rudimentary tests by feeding SCP-354-19 rats before calling for a researcher to ascertain the nature of the anomaly. By the time research personnel had arrived the entity had grown to an immense size after consuming the previously mentioned rats (likely via anomalous means due to the rate of growth and scale when compared to the relatively low food intake). SCP-354-19 was quickly determined to be too dangerous to study directly and so efforts turned toward the entity's termination. Several means of termination were devised, first of which was the simple use of explosives, however, the entity was able to dodge and grenades or improvised explosive devices used against it. The second means of possible termination was the deliberate feeding of two D-Class personnel to SCP-354-19 in order to make the anomaly so large as to not be able to operate, become crushed in the chamber, or run out of oxygen (based on the belief that the entity required oxygen and its need grew with its body's mass) and suffocate. This attempt at termination also failed as SCP-354-19, instead of consuming the D-Class personnel, bit them, turning them into instances of what will hereafter SCP-354-19A, having D-Class's skin and clothing turn red while their eyes became yellow. The SCP-354-19A instances proved to be intelligent, using a keycard (likely stolen by one of the D-Class prior to the incident) to set SCP-354-19 free, all entities attacking and overcoming MTF operatives. It is at this point that SCP-173 was set free, being in HCZ for use as a final method of termination should the others fail. SCP-173, however, returned to light containment along with SCP-354-19 and the two SCP-354-19A instances. This mass breach coincided with a raid by a local Sarkic Cult (it is unknown whether or not the breach and raid were coincidental or not). In the chaos there was a mass riot by D-Class personnel, many being turned into instances of SCP-354-19A. List classes of SCP(s) involved: Keter and Euclid. Immediate complications due to the incident: Several foundation personnel including members of Security, MTF operatives, and members of the Research division were killed by SCP-354-19, instances of SCP-354-19A, D-Class personnel, and Sarkic Cultists. Many D-Class subjects were lost. Long-term complications due to the incident (if applicable): The implications of instances of SCP-354-19A, being intelligent and possibly having (though possibly without the ability to use) knowledge of the Foundation being within SCP-354 are troubling, posing, if nothing else, the risk of easier breaches for any entities SCP-354 produces. Type of response towards incident (MTF/NTF/Security/ETC): Both MTF and Security responded to human and anomalous threats throughout the facility. Resolution towards incident: For unknown reasons, SCP-354-19 returned to SCP-354 along with many instances of SCP-354-19A. Instances of SCP-354-19A remaining in the facility being terminated by MTF operatives. Members of the Sarkic Cult left the facility on their own accord. D-Class riots were put down by Security. SCP-173 was recontained by a joint team of MTF operatives and Security personnel. How dangerous was the entirety of the situation?: Extremely dangerous. Extra Information: Permission to report to SCP-354 was given by RAM CPRF Avalon Levi.
-
Name: Associate Researcher Samuel J Rank: AR Clearance Level: Level 3 Describe the incident: AR Samuel Jackson and D-5009 was escorted by two Mobile Task Force members to SCP-049's containment chamber, 049 was seen "renovating," it's operating table before stopping once it noticed visitors. AR Samuel Jackson: "Doctor, how was your day," SCP-049: "Have you brought what I asked?" AR Samuel J: "Yes, one moment please,", Associate Researcher Samuel Jackson put their bag on the floor and pulled out a perfectly sized orangutan costume, and ordered D-5009 to put it on, D-5009 entered the containment cell and SCP-049 began to take notice, SCP-049: "You brought me a monkey?" AR Samuel J: "The orangutan's anatomy is very similar to a human's," SCP-049: "Is this what I asked for?". After pausing for a short moment, 049 began to inspect the fake orangutan shortly before touching it, before taking a more angry tone, SCP 049: "Oh, I see, this isn't a monkey at all, you lied to me,", AR Samuel J: "I can assure you that is indeed an orangutan,", 049 began to operate on D-5009's corpse in a rushed surgery, shortly afterwards D-5009 turned into an instance of 049-2. Mobile Task Force soldier SGT Ash F0XT shortly afterwards left the room, before Dr. Bright walked inside the chamber, Dr. Bright: "Who wants to help me kill the 049-2?", 049's containment chamber was opened and the Mobile Task force soldier remaining in the room opened fire on the instance of 049-2 along with Dr. Bright, SCP-049 ran out of the chamber attempting to attack the foundation personel present, the instance of 049-2 was quickly dispatched by the Mobile Task force unit present, 049 appeared to surrender and calm down shortly before Dr. Bright went absent from the room, 049 reassumed it's aggressive state and turned the Mobile Task force soldier into an instance of 049-2, the blast door was closed by Associate Researcher Samuel Jackson and Mobile Task force was called to the location, the first force sent was wiped out by SCP-049 and turned into SCP-049-2. A Chaos Insurgency raid also occured in which case all Chaos Insurgency soldiers were turned into 049-2. RCF reported on the scene and afterwards successfully returned SCP-049 to their containment chamber. List classes of SCP(s) involved: SCP-049, SCP-049-2 Immediate complications due to the incident: Defcon grade lowered, Junior Researchers locked in bunks. Long-term complications due to the incident (if applicable): Distrust of foundation staff by SCP-049. Type of response towards incident (MTF/NTF/Security/ETC): Mobile Task Force, Security RCF, Resolution towards incident: Large RCF force surrounded SCP-049 and moved them back to their chamber. How dangerous was the entirety of the situation?: Euclid breach, moderately dangerous. Extra Information: None.
-
Unknown user please enter login code User: Protégé Password: *Protégé noises* Login code accepted welcome user Protégé Enter command: Access file SCP-5208 Accessing SCP-5208 Enter command: Open incident SCP-5208-B Incident requires level 2 clearance input level 2 credentials to access Input clearance code: *Protégé noises* Password: *Protégé noises* Incident SCP-5208-B opened
-
Unknown user please enter login code User: Protégé Password: *Protégé noises* Login code accepted welcome user Protégé Enter command: Access file SCP-5208 Accessing SCP-5208 Enter command: Open incident SCP-5208-A Incident requires level 2 clearance input level 2 credentials to access Input clearance code: *Protégé noises* Password: *Protégé noises* Incident SCP-5208-A opened
-
// Clearance level 3+ needed to access this document any unauthorized access will be met with memetic kill agents designed to cause cardiac arrest within 5 seconds of exposure // Username: ####### Password: ******** . . . [Credentials accepted] Name: Cancer Rank: Supervisor Clearance Level: 3 Date of Incident: 3-24-20 Describe the incident: when the test was concluded, I went to retrieve 999 from 682's CC and 682 then breached containment after I took 999 away from him, as per last incident report 682 just breached inner CC and not into HCZ. See for more info. List classes of SCP(s) involved: Keter, Safe Immediate complications due to the incident: Personnel loss of life Long-term complications due to the incident (if applicable): N/A Type of response towards incident (MTF/NTF/Security/ETC): MTF [Redacted] were on-site and immediately recontained 682, Nu7 were there too just didn't do much. Resolution towards incident: SCP-682 was RC without anymore casualties. How dangerous was the entirety of the situation?: Not too dangerous but could've been worse. . . . [Connection Terminated]
-
// Clearance level 3+ needed to access this document any unauthorized access will be met with memetic kill agents designed to cause cardiac arrest within 5 seconds of exposure // . . . // Access Granted // Name: Cancer Rank: Supervisor Clearance Level: 3 Date of Incident: 3-20-20 Describe the incident: it was a fine day and I was doing a test with 682 and 999. I had HoR Weiss and about 4 JR-AR's tag along, E11 and Nu7 escorts were there. 682's 2nd bulkhead door wasn't shut yet for unknown reasons and through some miscommunication and lag, 682's main bulkhead door was opened and that lead to 682 breaching to his CC controls. List classes of SCP(s) involved: Safe, Keter Immediate complications due to the incident: About 10 Foundation personnel casualties including clearance rank 4 personnel. Long-term complications due to the incident (if applicable): N/A Type of response towards incident (MTF/NTF/Security/ETC): MTF E11 and Nu7 was on site and recontained 682 without hassle Resolution towards incident: 682 recontained How dangerous was the entirety of the situation?: Not very dangerous but could've been alot worse if he had breached outer containment . . . // Connection Terminated //
