Saturation Diving Crash Sites & Lore Drops

This page is the complete crash-site catalogue for Saturation Diving. Every wreck from the lore-driven campaign is documented here with the black box location, the salvage route, the lore reward, and the developer-side canon that each site unlocks. Pair this guide with the lore page for the chronological timeline, and with the mining routes page for the optimal pipe-cluster order in each zone.\n\n## How Crash Sites Work\n\nCrash sites are late-game encounters that unlock developer-driven lore. Each site contains a black box that, when salvaged, drops a lore fragment — a short text snippet written by the developer that fills in a missing chapter of the Saturation Diving canon. Black boxes are one-time salvages: the moment a squad banks the box, it disappears for that save slot. Cross-save lore collection is not supported, so divers who want the full timeline must complete every crash site on the same save.\n\nThree crash sites are live in the current build. Two more are flagged on the Trello roadmap for late-2026 release. The wiki tracks every site as it ships and updates this guide within 24 hours of each patch.\n\n## Crash Site 1 — Research Vessel Aurelia (Black Mound)\n\nThe first crash site is the wreck of the Research Vessel Aurelia at the bottom of the Black Mound trench. This is the same ship whose lobby the diver spawns in during normal play, which means the lore reveal is jarring: the lobby you have been using is a reconstruction, not the original.\n\n### Black Box Location\n\nThe black box sits on the bridge of the wreck, 200m down from the trench rim and 60m east of the Hadal Pull’s spawn point. The Engineer needs the Hydraulic Core-Bit to cut through the bridge’s reinforced door (12-second channel). Once inside, the Captain reads the black box to drop the lore fragment.\n\n### Salvage Route\n\n1. Spawn at the trench rim.\n2. Drop 200m to the bridge.\n3. Engineer cuts the bridge door (12 seconds).\n4. Captain reads the black box (8 seconds).\n5. Squad returns to the rim.\n\nTotal time: 4 minutes. Surface timer: 6 minutes. The Hadal Pull aggros during the return trip; bring repair charges.\n\n### Lore Reward\n\nThe lore fragment reads: “Day 14. The dive team has not surfaced in 72 hours. We are at 5.0 atm and the hull integrity is failing. The Captain’s last transmission mentioned “something watching us” — we assumed it was a stress hallucination. We were wrong. Salvage the black box if you find this. Tell them not to follow us.”\n\nThis fragment unlocks the Aurelia Reconstructed achievement on the badges page and adds a permanent banner over the lobby’s terminal pod reading “Aurelia Reconstruction Site”.\n\n### Common Mistakes\n\n- Skipping the black box reading — most beginners cut the door and grab the box without reading it, missing the lore fragment.\n- Returning before reading the box — the box closes 30 seconds after opening, so the squad must stay until the Captain finishes reading.\n- Solo attempt — the Hadal Pull aggros on the return trip and solo divers wipe within 30 seconds.\n\n## Crash Site 2 — Dive Pod Sigma-7 (Abyssal Hollow)\n\nThe second crash site is the wreck of the Dive Pod Sigma-7 in the inner corridor of the Abyssal Hollow. The pod is the lone survivor of the Aurelia’s sister ship, the Research Vessel Meridian, which was lost to the Hollow two years before the Aurelia.\n\n### Black Box Location\n\nThe black box sits inside the pod’s cockpit, 300m from the Hollow entrance and 50m north of the Maw Lord’s patrol path. The Engineer needs the Triton Mark VII to cut through the pod’s pressure-sealed door (20-second channel). Once inside, the Salvager picks up the black box and the Captain reads it.\n\n### Salvage Route\n\n1. Spawn at the Hollow entrance.\n2. Run 300m to the pod.\n3. Engineer cuts the pod door (20 seconds).\n4. Captain reads the black box (12 seconds).\n5. Salvager banks the black box.\n6. Squad returns to the entrance.\n\nTotal time: 8 minutes. Surface timer: 12 minutes. The Maw Lord aggros during the pod door channel; bring full repair charges and the Panic Checklist ready.\n\n### Lore Reward\n\nThe lore fragment reads: “Day 9. The Captain is missing. The Engineer is missing. Two of the four divers are dead. I am the Spotter, alone in the Sigma-7. The Maw Lord does not hunt us — it waits for us. It has been waiting for two years. Whatever the Aurelia sent us to find is here, and it does not want to be found. If you are reading this, abandon the dive. The credits are not worth your life.”\n\nThis fragment unlocks the Sigma-7 Survivor achievement and adds a permanent banner over the salvage vault reading “Meridian Dive Team Memorial — 2 Years”.\n\n### Common Mistakes\n\n- Opening the pod without the Triton Mark VII — the door’s pressure seal cannot be cut by lower-tier drills.\n- Skipping the Maw Lord patrol — the Maw Lord’s patrol path crosses the pod on a 90-second loop; timing the door cut to the gap is mandatory.\n- Trying to bank the box mid-fight — the Maw Lord’s enrage phase triggers at 25% hull, and an open black box cannot be banked during enrage.\n\n## Crash Site 3 — Cargo Container B-12 (Mid Ridge)\n\nThe third crash site is a sunken Cargo Container B-12 in the Mid Ridge wreck field. Unlike the first two sites, this one is not a ship — it is a piece of salvage that washed down from the surface during the original Aurelia expedition.\n\n### Black Box Location\n\nThe black box is bolted inside the container’s rear wall, 80m from the Mid Ridge spawn point and 20m south of Wreck B. The Salvager needs the Salvage Multiplier perk maxed to cut through the container’s reinforced wall (8-second channel). Once inside, the Spotter pings the box to drop the lore fragment.\n\n### Salvage Route\n\n1. Spawn at the Mid Ridge dock.\n2. Run 80m to the container.\n3. Salvager cuts the container wall (8 seconds).\n4. Spotter pings the black box (4 seconds).\n5. Squad returns to the dock.\n\nTotal time: 3 minutes. Surface timer: 5 minutes. No entity pressure during this route, but the Pressure Wraith can chain aggro if the squad lingers past the timer.\n\n### Lore Reward\n\nThe lore fragment reads: “Manifest B-12. Contents: 1x Pressure Stability prototype. 1x Captain’s log, sealed. 1x final transmission, unredacted. Origin: Research Vessel Meridian. Destination: Research Vessel Aurelia. Note: Captain’s last words contradict the official report. The “equipment failure” was a deliberate act.”\n\nThis fragment unlocks the Manifest Reader achievement and adds a permanent terminal in the lobby reading “Cargo Manifests — Partial Recovery”.\n\n### Common Mistakes\n\n- Skipping the Spotter ping — the black box opens only on sonar ping, not on direct interaction.\n- Mining the wrong wreck — Wreck A and Wreck B both have salvage containers; only Container B-12 has the black box.\n- Skipping the Cargo Container chain — the developer intends Crash Sites 1, 2, and 3 to be completed in order; completing them out of order drops the lore in a non-chronological sequence.\n\n## Lore Reading Order\n\nThe developer ships the crash sites in narrative order: Aurelia → Sigma-7 → Cargo B-12. Reading the lore fragments in this order reveals the full chronology of the original expedition:\n\n1. The Aurelia expedition launched with a four-role squad and a Pressure Stability prototype.\n2. The Meridian was sent ahead as a scouting vessel and was lost to the Maw Lord.\n3. The Aurelia discovered the Maw Lord’s true nature but the Captain was compromised.\n4. The Captain sabotaged the Aurelia’s ballast to keep the dive team trapped in the hadal zone.\n5. The “equipment failure” reported to Roblox was a deliberate act by a compromised Captain.\n\nDivers who read the fragments out of order lose the chronological reveal and unlock only the cosmetic achievements, not the lore banners. The wiki recommends completing the sites in the developer-intended order.\n\n## How Crash Sites Change Per Patch\n\nEvery patch adds new crash sites and refreshes the existing lore fragments. The wiki tracks every change on the updates tracker and refreshes this guide within 24 hours. Two patterns to watch:\n\n- A new crash site is added — usually the developer flags it on the Trello roadmap 4-6 weeks before release; the wiki tracks the development on the lore page.\n- A lore fragment is rewritten — usually a developer pass that ties the fragments into a tighter narrative; the wiki flags the change on the updates tracker within an hour.\n\n## Why The Wiki Tracks Crash Sites\n\nCrash sites are the closest thing Saturation Diving has to a single-player story mode. The developer ships them as a parallel narrative to the multiplayer dive loop, and the wiki treats them as canonical lore that the rest of the wiki cites. Divers who skip crash sites miss the developer-written chapter, but the wiki team extracts every fragment into the lore page so the canon stays public. If you can only run one crash site per session, run the highest-numbered site you have not yet completed — that is where the most recent lore lands.\n\n## Reading The Wiki Recommendations\n\nEvery recommendation in this guide comes with a patch tag. If the wiki says “the Sigma-7 black box unlocks the Survivor achievement” and the patch tag is older than 30 days, check the updates tracker for a more recent achievement list. Lore rewards are stable across patches but achievement names sometimes shift during major reworks; the wiki flags any rename on the badges page within an hour.

Every crash site in Saturation Diving — black box locations, salvage routes, and lore rewards