Compared to the #REKKINGRUSKI group who operates in Aridia and have only 2 days prior acquired their latest Nyx Super Carrier kill, the #REKKINGCREW lead by RoCkEt X last caught this Hel Super Carrier on April 22nd. Following on from the last kill they have now added another Hel to their Super Capital kill tally for the year, as explained below.
RoCkEt X provided the following information regarding the kill:
A few days back, one of our scouts ran through a station-less system to find 3 other pilots in local – one of whom had a suspect timer. He immediately checked it out and found three supercarriers on scan; one Hel, a Wyvern and an Aeon. As he landed, The Aeon on the Hel vanished from space, apparently reaching the end of their safe-log timers. Our scout however was able to aggress the Wyvern pilot, breaking his safe-log timer and forcing him to take action.
Given that this was late US timezone, where #REKKINGCREW normally lacks numbers to deal with spontaneous scenarios like this one – the team didn’t have a bridging titan in range to land HIC’s on the target. After a game of cat and mouse for several minutes, the Wyvern eventually cloaked up safely. Now we had an interesting problem. The alts we’d managed to find and track down were heading in an odd direction – and it meant the only place we could actually stage to hit their next midpoint… was the system they were currently sitting in… which is of course impossible to do without the target getting suspicious.
An hour or so later – even later into USTZ, but still before the euro guys wake up; the two ships that had successfully logged out jumped to the midpoint we had predicted – our covert eyes landed on the cyno; but there was nothing they could do without a bridge titan within range, and with so few numbers too. Some time later, all of the targets safely logged out.
When I woke up in the morning I was briefed by Quickload (Who is also #REKKINGCREW’s #2, and one of the single most active and effective hunters of the group) and several members of the #REKKINGCREW group known as: Domain Research and Mining Inst. [ART0N]. They’d successfully tracked the targets to Miyeli; One had jumped further north and out of our range, another had stored his ship using a holding alt – and the Hel was logged out in space.
During the afternoon we made the call to give these targets some attention over our other currently active kills. We had seen the Hel pilot log in several times that day. I sent a scout over and found a small POS in Miyeli. We assumed that the Hel had logged in and warped to the tower in order to A) Refit, and B) Eject so that he could switch corps. And then probably logged out in the POS.
We waited until some members of the POS’s corp were online, then sent in a neutral dreadnaught to reinforce the tower, hoping the Hel would log back in… but he didn’t. An hour after the dread left system however – they sent scouts in. After another 45 minutes, the Hel logged back in – and I logged my scout in.
The Hel wasn’t in the POS, but the system was huge so I warped across and was able to find him on directional scanner… I knew I didn’t have long. The target logged out, leaving his ship adrift in space for 60 seconds. I launched probes as soon as I landed out of warp and managed to get a 70% hit. I knew I may not have time to get a second hit so I took a screenshot for later reference.
While this was going on, I gave the order to form and the team scrambled together. BLOPS pulling maximum range jumps, Supercaps and the bridge titan making consecutive jumps and HIC’s burning to the staging midpoint. Only 90 seconds after logging out, the target logged back in – He lingered a moment too long as he landed, and I achieved the 100% warpable hit.
I landed at his spot with a HIC we’d burned from a few jumps out… decloaking him and lighting the cyno only moments later.
Most traps set up by the #REKKINGCREW tend to go down by hunting the pilot, moving across space carefully investigating the route he will most likely follow so that the net can be prepared in advance. Clearly this time it wasn’t the same routine as expected but with the pilot logging in on their own accord with neutrals in local it was a big enough window for him to get caught. If the pilot had a cyno in place when he logged back in he may have had a chance to escape but obviously this wasn’t the case – or it simply wasn’t used in time.
We contacted the corporation which the pilot belonged to when it was lost, before he joined an NPC corp again, and Spookzor 4-Eyes replied with the following:
This is what I know and what he has told me. He joined Silver Guardians after returning from being inactive. One week ago he moved his super to the system the Hel was popped in. On the 3rd when the kill happened he logged in his super to set some skills, was cloaked at a deep safe 20AU from nearest celestisal and 5 mins later a Broadsword lands on top of him and lit a cyno. A while back PL tried to kill the pos it was being built in twice. My bet is they were tracking him somehow.
On top of this I spoke to his friend, SephiXan, who also returned to game along with the super pilot and he provided me with this brief statement:
The pilot and myself just returned to the game after 3 years away and got caught on his travels to the new corporation. This whole situation revolves around the EVE meta of having an account designed to hold those ships for other characters to use. The pilot merely removed the character that was no longer going to be needed as its purpose was forfeit.
Clearly it was likely a shocking return to the game and hopefully one that will not have put off the pilot altogether. This does shed some light on it’s reason for travel, although it begs the question as to why this pilot logged off in space instead of either safe logging in the POS or traveling further north as the other 2 Super Carriers clearly did.
[If you have any comments or intel you would like to provide please contact me at [email protected] or via an in-game mail]