7th Cavalry Gaming

Join the Tactical Gaming Excellence

AAR ARMA 3 | A/1-7 FTX Operation Second Strike

After Action Report
Status
Not open for further replies.

Dread.M

Lieutenant Colonel
Active Duty
1-7 HQ
S3 HQ
ODS
Local time
8:44 PM
1,221
1,828
DEPARTMENT OF THE ARMY
S3 BATTLE STAFF
Headquarters
7th Cavalry Regiment
COMBAT AFTER ACTION REPORT

Name of Combat Mission: A/1-7 FTX Operation Second Strike
Game: ARMA 3
Server Hosted on: ARMA 3 Training Server 1
Date of Combat Mission: 14MAY23
Time of Combat Mission (Zulu): 2300z
Mission OIC: - Major Dread.M
Mission Controller: None

7th Cavalry Personnel in Attendance:

  1. Major Dread.M
  2. Chief Warrant Officer 3 Baruch.J
  3. Chief Warrant Officer 2 Berg.J
  4. Warrant Officer 1 Thumper.N
  5. Warrant Officer 1 Hamm.C
  6. Warrant Officer 1 Tyrcon.L
  7. Warrant Officer 1 Bloggins.R
  8. Warrant Officer 1 Villmarsson.L
  9. Warrant Officer 1 Spitnale.K
  10. Sergeant Terp.J
  11. Corporal Dujakovic.R
  12. Corporal Bane.K
  13. Corporal Olson.DJ
  14. Specialist Grizzle.M
  15. Specialist Priest.V
  16. Specialist Lee.RA
  17. Specialist Spin.M
  18. Private First Class Daniel.S
  19. Specialist Searle.I
  20. Corporal Lucander.P


PROS:
  • Elements performed well, and overcame technical difficulties throughout the OP.
  • Mission completed
  • Really cool SERE
  • Good practice on call for fires
CONS:
  • Radios were a nightmare, people only had access to one or two radios despite having three. Some radios just completely disappeared.
  • F-18 mod is broke. HARMs won't lock.
  • MH-60 had an unusual physics issue where it acted like the bird was sling loading. The airframe inverts and crashes. It caused a few crashes today.
 
Last edited by a moderator:

Thumper.N

1st Lieutenant
Active Duty
A/1-7 HQ
S7 HQ
Local time
9:44 PM
914
1,339
DEPARTMENT OF THE ARMY
S3 BATTLE STAFF
Headquarters
7th Cavalry Regiment
COMBAT AFTER ACTION REPORT

Element Callsign: Raider-1
Element Leader: Warrant Officer 1 Nate "Justicar" Thumper

7th Cavalry Personnel Within Element:
Sergeant John Terp

Pro:
  • Good mission plan
  • Attempting to SERE, resulted in TIC and hot extract
Con:
  • Radio issues, not working
  • Lack of turn out
  • Deviation of SOP
 

Priest.V

Corporal
ELOA
Local time
2:44 AM
209
311
Element Callsign: INFIDEL
Element Leader: Priest.V

7th Cavalry Personnel Within Element:
Lucander.P
Searle.I



Pro:
  • Downed RAIDER assisted by IINFIDEL to extract/break contact was awesome
  • RAIDER 1 and 2 did some amazing CAS work
  • Performance of mission file frames etc
  • Scenario simplicity yet demanding and well modulated to meet lower turn out than expected
  • Two INFIDEL assistants did really well and were very much needed - both enjoyed/learned allot
Con:
  • CAS Flights need to check-in as Flights (One check in, sent by Lead)
  • FW didnt seem as slick as usual at sensor taskings did not manage to find enemy force building up resulted in EF pushing up very close and sometimes beyond the blocking line
  • Radios - huge technical issue with radios not working whether in kit or picked up again from boxes.
  • Radios - not appearing in self interact
  • Radios - dissapearing from inventory/becoming unuseable and not able to change channels by interaction
 

Hamm.C

Specialist
Active Duty
1/A/1-7
MP Staff
Local time
9:44 PM
921
1,015
DEPARTMENT OF THE ARMY
S3 BATTLE STAFF
Headquarters
7th Cavalry Regiment
COMBAT AFTER ACTION REPORT

Element Callsign: BUFFALO-1
Element Leader: Warrant Officer 1 Hamm.C

7th Cavalry Personnel Within Element:

Specialist Grizzle.M

Pro:
  • Really good FTX concept and design.
  • Great teamwork efforting and successfully managing terrible tech issues, certainly ACRE comms. We came, we saw, we conquered. And Rotary (transport) delivered, as always.
  • Baruch.J showed up, which helped Rotary out greatly. Better late than never ;-) ....Thanks for a great job.
  • CSARs were handled nicely and prioritized properly. CSAR for downed RAIDER-1 was somewhat problematic but ultimately quite successful.
Con:
  • Terrible tech issues, specifically and mainly with comms. Not sure why, but this always seems to happen on training servers.
  • Issue with the Training Server trade-off between two different 7Cav groups, resulting in significant delay in prep, plan, and execution.
  • EXTREMELY STRANGE glitch in our Blackhawk helicopters tonight, for unknown reasons. Essentially, they would randomly and violently "lurch" out of control, which is normally associated with flying at moderate/high speeds or flight instability with a) Fast ropes deployed, b) Hoist/hook deployed, or c) Sling loading. In my case and in the case of the unfortunate near-ENDEX crash of our aircraft, I CONFIRMED multiple times that these systems were properly stowed and NOT deployed. So why these borky glitches occurred is pretty much anybody's guess. But I can tell you it never happens on TacR. Honestly first time I've seen this happen as a trend, with my bird and Baruch.J bird as well.
  • WAY WAY WAY too much traffic on LR08 for Infidel to manage both CAS and Transport, plus it's not his job. He did well under the circumstances as he always does, however, he cannot possibly manage both at the same time. It's just too much information flow overload. And again, Infidel is for CAS, NOT Pegasus-like flight coordination. Doing this is understandable in a pinch I guess, but it is still not optimal at all.
  • We certainly need to revisit our understanding of ARMA and 7Cav map/nav marking SOP (or lack of SOP, outside of training book stuff), which weirdly came into dispute and led to open antagonism and discord, which is not good. There are multiple ways of indicating/communicating your position (i.e. grid coordinates, cTab, map marks, etc.) in addition to the Bullseye.
 
Last edited:
Status
Not open for further replies.
Top