Angatalie – 2025-11-09
Summary
- Threat level: Low to Moderate (Real Threat Range: 2.0–3.5) for transits through Angatalie (Low‑sec).
- Incident date/time: 2025-11-03 at 21:31:35Z (UTC).
- Confirmed aggressor: arataks1s flying an Angel Cartel Mekubal (Destroyer).
- Victim: Rahna Klaar in a Jackdaw (Tactical Destroyer).
- Nature of attack: Solo, hit‑and‑run style; fast alpha damage and warp acceleration typical of Mekubal play.
What happened (facts)
- A single, confirmed kill on 2025-11-03 shows arataks1s in a Mekubal quickly defeating a Jackdaw at 21:31:35Z.
- The event indicates an opportunistic solo pirate operating during late‑evening UTC hours who favors high‑speed, high‑damage engagements against transiting ships.
- Given the Mekubal’s profile, the pilot can close and apply heavy projectile damage fast enough to overcome a well‑fitted cruiser/destroyer if the target is not prepared or supported.
Threat assessment and implications
- Primary threat actor: arataks1s (Mekubal) — treat as a confirmed local threat while active in Angatalie.
- Time window of heightened risk: ~20:00Z–23:00Z (late European evening / early U.S. prime), based on the observed incident.
- Target profile at risk: solo cruisers/destroyers and other non‑dedicated combat hulls transiting gates/stations or lingering near choke points.
- Real risk: this pilot and hull combination are capable of swift kills on tactical destroyers and similar ships; transiting pilots should assume increased danger during the identified time window.
Recommended mitigations (grounded in observed data)
- Avoid transiting Angatalie during heightened window (20:00Z–23:00Z) when possible.
- Do not autopilot through the system.
- Avoid loitering near gates, stations, and choke points—keep warp routes clean and align to a safe bookmark before warping.
- If you must transit at risk times, travel with escorts or in numbers; a single lone cruiser/destroyer is the preferred target profile for the aggressor.
- Use fast, well‑tanked, or cloaked/micro‑jump capable alternatives for high‑value runs; prioritize ships and fittings that increase survivability and reduce time-to-warp.
- Keep d‑scan and local awareness up while in system; assume the aggressor may be scouting the gate/station approach.
- If burned into a fight unexpectedly, prioritize getting aligned and warping out rather than prolonged engagement unless supported.
Operational note
- The assessment is based on a single, well‑characterized incident. That incident demonstrates capability and a preferred operating window for the aggressor; plan operations accordingly and treat arataks1s in a Mekubal as a confirmed localized hazard while active.
Issued by Everyshore Intel Network — Angatalie Low‑Sec Advisory Unit