I was pulling picket duty in WT's home system 30+ jumps from Korsiki. No WT's online for more than an hour. I'm BSing with another director (Let's call him Warbeer) on TS.
Then at 23:02 buddylist notification of a WT logging in was received. Quick scan of local revealed that WT was not in local. Our intel dept locates WT seconds later in Osmon in Typhoon, where WT had logged off after the earlier engagement where Uni popped a Mega.
Warbeer is in Korsiki & heads to the gate. I dock & jump clone to Korsiki and grab my favorite Scorp. No fleet is up & no one is in ops channel on TS, so I drag Warbeer & myself to the Bar & Grill. Warbeer starts issuing orders and engages the WT jumping into Korsiki from Osmon. I get a fleet started.
WT reapproaches the gate & jumps back to Osmon before anyone else gets to the Osmon gate. Warbeer waits out the aggression time & jumps into Osmon & finds WT still in local & on scan. Our prober locates WT sitting outside a station.
Warbeer warps to the station & engages, WT returns the favor.
The rest of us jump in, warp to the station & engage. One of our frigates goes pop. WT de-agresses to wait out the timer & dock, but we put enough DPS on the Typhon to pop it before the timer expires. WT immediately docks the pod & logs out seconds later. 16 minutes from log in to ship loss.
What we did right:
- Rapid response
- DPS on target
What I could have done better:
- I only set up 1 squad as I formed the fleet. I got the self-invite sorted and the invitation in Alliance chat, but because I only left room for 1 squad, it maxed out. I was too busy to do anything about it until it was too late. My bad guys & I'll do better next time!
Bottom line: Great response, great kill!