Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Cmdr Baxter
The Synenose Accord
|
Posted - 2011.07.21 02:49:00 -
[1]
FOR PUBLIC RELEASE [SYNE] Report on Nation Incursion in Kador Prime and Abduction of 24th Imperial Crusade Aeon-class Supercarrier
Summary: From approximately 0340-0630 UTC on 20.07.113YC, Sansha's Nation conducted operations in the Kador Prime System. This AAR will outline the continuation of past Nation TTPs, and circumstances surrounding the disappearance of a 24th Imperial Crusade Aeon-class supercarrier during the engagement.
Assessment: Nation is continuing to target capsuleers using evolving tactics and procedures. SYNE assesses that Nation may have attempted to target an Amarr 24th Imperial Crusade pilot during the course of this engagement, based on circumstances still under investigation.
- As previously observed at Hebisa (07.07.113YC), this engagement began with an ambush of unsuspecting pilots in a combat zone, and eventually escalated to the point when a Nation-class mothership was deployed [1]. Reporting from a fleet led by Dasidar states that they were surprised first by a violent wormhole opening in a mining colony site, followed by the immediate deployment of webbing/scrambling Schmael Medullas. Unlike Hebisa, casualties were sustained by the defending fleet before they were able to scatter and escape.
- Of note, this is the second report SYNE has received of Schmael Medullas being used as "shock" vessels in surprise engagements. We believe this may point to the development of a longer-term trend of Schmael Medullas, or other fast frigates equipped with webs/scrams, being the ship-of-choice in ambushes involving capsuleers.
- At approximately 0500 UTC, the Amarr 24th Imperial Crusade deployed an Aeon-class supercarrier to Kador Prime under the command of Ihsam Dasirel [2]. The name may be familiar to some readers: research has revealed Captain Dasirel was on the field during incursions last year in Kamela (12.05.112YC) and Niarja (12.05.112YC) [3].
- Slightly before 0600, Capt. Dasirel's Aeon was lost to sensors after transiting a Nation WH. From what we know, a string of WH's had been opened in proximity to the Kador system "top station," presumably under the direction of Citizen Astur [4]. Unconfirmed reports suggest that at least some of these were deployed in such a way as to screen the carrier through the deployment of reinforcements in close proximity. One of these WH's was likely utilized to abduct the Aeon, which nevertheless reappeared on the field within 15 minutes and promptly re-engaged a Nation-class mothership piloted by Citizen Astur [5].
- SYNE believes that Capt. Dasirel may have been deliberately targeted by Nation during the course of this engagement, but we have insufficient information to speculate on whether this was the primary goal of the incursion or even if the attempt succeeded. In the past, Nation has often targeted key officers with a high level of interaction with the larger capsuleer community (i.e. Haeldone Dorgiers). We also remind readers that Sansha's Nation is continuing to seek out the Amarr Justicar naval unit. We have no information to suggest that Captain Dasirel is connected to the Justicars, but the possibility nevertheless exists.
// End Report // --
Not indicative of corporate policy unless otherwise stated. |
The Antiquarian
Amarr
|
Posted - 2011.07.21 08:33:00 -
[2]
On behalf of the Arek'Jaalan Acquisition Division, a message has been sent to Captain Dasirel requesting for any information, flight data, or any artifacts associated with the Aeon when the ship "disappeared into the wormhole."
A prompt response from the 24th Imperial Crusade representative would be much appreciated as several of our researchers believe that such info would hold the answer as to how the Sansha manually generates a wormhole.
|
Ugleb
Minmatar Sarz'na Khumatari Ushra'Khan
|
Posted - 2011.07.21 16:29:00 -
[3]
Edited by: Ugleb on 21/07/2011 16:29:28 Is there additional reason to believe that this 24IC was 'abducted' as opposed to the possibility that it merely engaged a cloaking device and intended to ambush the Sansha? I'm not sure how anyone would force something as large as a super carrier to go anywhere it did not wish to go.
The Journal; Walking The Road To Liberation |
Kithrus
Amarr Defensores Fidei Curatores Veritatis Alliance
|
Posted - 2011.07.21 18:33:00 -
[4]
**Kithrus merely transmites a brief footage of him sitting at his Desk at the CLRGY Terrence slowly drumming his fingers looking right at the camera with an frustrated, disappointed gaze.**
**He cuts the feed after 6 seconds.**
|
Ber Kan
Caldari
|
Posted - 2011.07.21 18:39:00 -
[5]
Hmm, never underestimate the enemy. And in doing so will bring a defeat your way.
This surly is interesting and fearful news Commander. I guess we must begin certain operations again and see to how this had happened and to see if there is a way that we can make sure this does not get out of hand. For if the sansha had the ability to take ships out the way they did, and even more, bring wormholes into the fray during our counter attacks to their incursions, then we are soon to be in a rut again. It will be a matter of time before they manage to take an area and keep it as a foot hold.
-COL. II Alaric Ber Kan
|
Cmdr Baxter
The Synenose Accord
|
Posted - 2011.07.22 01:27:00 -
[6]
Originally by: Ugleb Edited by: Ugleb on 21/07/2011 16:29:28 Is there additional reason to believe that this 24IC was 'abducted' as opposed to the possibility that it merely engaged a cloaking device and intended to ambush the Sansha? I'm not sure how anyone would force something as large as a super carrier to go anywhere it did not wish to go.
Over the course of the last seven months, I've discovered that the worst thing we can do is underestimate Sansha's Nation. Remember that this is the organization that raided the Kyonoke Pit. They have hacked CONCORD's computer systems not once, but twice. In the vast majority of engagements, Nation has been able to paralyze the non-capsuleer ships of the Empire militaries through their sophisticated computer systems. And earlier today they attempted to raid commerce transiting the shipping lanes into Jita. These are a few of the highlights.
Considering how long the engagement lasted, I personally believe the cloaking device theory is not credible. By that point of the engagement all defending forces, including capsuleers, were fully committed so for an undamaged supercarrier to withdraw from action is ... illogical, to say the least. Additionally we have spoken with other eyewitnesses at the engagement, and they have confirmed seeing the carrier transit the wormhole.
Like it or not, it appears that an Aeon class supercarrier was unaccounted for, for approximately 15 minutes. --
Not indicative of corporate policy unless otherwise stated. |
Herzog Wolfhammer
Gallente Sigma Special Tactics Group
|
Posted - 2011.07.22 01:37:00 -
[7]
If that carrier was caught in a kind of gravitational field, what are the chances of going along for the ride? All we need is one cyno-capable ship to get to the other side and we can tear the beasts heart out from within.
|
Utremi Fasolasi
Gallente The Scope
|
Posted - 2011.07.22 21:53:00 -
[8]
I think you mean Revenant class supercarrier. There is no such designation as Nation-class ship or motherships.
|
Cmdr Baxter
The Synenose Accord
|
Posted - 2011.07.22 23:28:00 -
[9]
Originally by: Utremi Fasolasi I think you mean Revenant class supercarrier. There is no such designation as Nation-class ship or motherships.
Incorrect sir. Nation-class motherships have been visually and electronically confirmed at five engagements since 06.05.113YC: Hebisa (06.05.113YC), Hebisa and Zith (07.07.113YC), Altrinur (12.07.113YC), and Kador Prime (20.07.113YC). I invite you to examine this galnet page for the raw data captures.
Of note, CONCORD classifies these ships as supercarriers but we at SYNE disagree with the assessment. There is really no way to describe a ship with such raw defensive potential with anything other than the "mothership" classification. --
Not indicative of corporate policy unless otherwise stated. |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |