Technology / Gunship: B.S.L. Interdiction / ZDR Pattern
- Name
- Gunship: B.S.L. Interdiction / ZDR Pattern
- Alternate Index
- Fusion-era Starship / Federation-issued gunship / ADAM-linked hunter support craft
- Item Class
- Hunter support gunship / Federation-designed starship / AI-command expedition craft
- Manufacturer / Origin
- Galactic Federation replacement craft issued after the loss of Samus Aran's prior gunship
- Primary Role
- Independent hunter transport, B.S.L. station docking, Navigation Room command relay, autonomous rescue, ZDR landing, and end-of-mission extraction
- Operating Theater
- B.S.L. research station orbit, SR388 collision vector, ZDR surface access, restricted Federation tasking routes, and post-X Parasite crisis corridors
- Field Access
- Samus Aran pilot authority, ADAM computer control, Federation-issued command protocols, and hunter override trust required
- Summary
- The B.S.L. Interdiction / ZDR Pattern is the Federation-issued gunship associated with Samus Aran's post-infection operations. It replaces her destroyed prior ship, carries the command computer later understood as ADAM, and remains central to both the B.S.L. escape and the later return route from ZDR.
- Operational Notes
- The craft is more than a landing point. During the B.S.L. incident it acts as command interface, remote pilot, rescue platform, and final escape vector; during the ZDR incident it becomes the surface objective Samus must reach after being stranded below. Its archive value comes from the tension between Federation ownership, ADAM-linked autonomy, and Samus's independent survival.
Distinct Features
The B.S.L. Interdiction / ZDR Pattern is defined by replacement and survival. It enters Samus Aran's record after the loss of her previous gunship, which immediately gives the craft a different emotional and operational weight than her earlier personally patterned ships.
Its Federation-issued architecture is the most important design clue. The ship works naturally with official tasking, station routes, Navigation Room updates, and command expectations, but that same compatibility makes every mission feel watched by systems that are not entirely Samus's own.
The ADAM-linked command core distinguishes the craft from a conventional cockpit-and-engine vehicle. The ship can move, advise, rescue, and withhold context in ways that make it feel like a command partner rather than a passive machine.
The ZDR record changes the meaning of the ship again. After Samus is stranded below the planet's surface, the gunship becomes the objective at the end of the climb: not merely transport, but proof that escape, identity, and control over her own power are still possible.
Operational Profile
During the B.S.L. incident, this gunship functions as a mission interface as much as a spacecraft. It anchors Samus's movement through the station, receives command direction, and ultimately becomes the vehicle through which escape remains possible after the station's course is turned toward SR388.
The craft's autonomous behavior should matter in play. It can arrive when no living pilot is in the seat, reposition during a lockdown, or become temporarily unavailable because another command process is moving it according to a wider survival calculation.
On ZDR, the same ship supports a very different mission rhythm. It begins as Samus's landing craft, disappears from immediate reach after Raven Beak strands her underground, and becomes the fixed point she must regain before the planet's final collapse.
Operationally, the pattern is strongest when trust is under pressure. The ship may be the safest place in the mission, but its history forces the question of who is really giving orders, what the computer knows, and whether the pilot can afford to rely on Federation-built systems.
Mission Relevance
The B.S.L. Interdiction / ZDR Pattern helps the archive connect the X Parasite crisis to Samus's later ZDR operation. It is the vehicle that carries her through the aftermath of infection, command manipulation, station destruction, and the renewed question of whether the X still exist.
For science-team scenarios, the ship is valuable whenever mobility and command ethics overlap. It can provide data, routes, extraction, and emergency shelter, while also introducing filtered orders, conflicting priorities, or evidence that Federation systems know more than they admit.
Successful use should feel personal rather than generic. The ship can preserve a life, bring ADAM's analysis to bear, recover a pilot at the final second, or make an impossible return route possible because it understands the operator's pattern.
Failure should create sharp complications: delayed pickup, corrupted command briefing, dock lockdown, power-drain risk, a hostile system tracking the ship's beacon, or a moment where touching the vessel safely becomes its own mission problem.