- Local time
- 12:06 AM
- 920
- 412
Campaign of Combat Mission: DCS Q1 FTX
Name of Combat Mission: Operation Double Negative
Number Within Campaign: 1/1
Game: DCS
Server: Operations Server 1
Date of Combat Mission: 28FEB2026
Time of Combat Mission (Zulu): 1900Z
OIC: Second Lieutenant Melk.J
Mission Controller: Staff Sergeant Remeslnik.F
Mission Controller: Chief Warrant Officer 2 Dibdin.H
Mission Controller: Warrant Officer 1 Baruch.J
TOTAL - 20
Second Lieutenant Melk.J
Staff Sergeant Remeslnik.F
Chief Warrant Officer 2 Dibdin.H
Warrant Officer 1 Baruch.J
Warrant Officer 1 Folmer.R
Warrant Officer 1 Landry.H
Warrant Officer 1 Swift.A
Corporal White.M
Specialist Ackerman.J
Specialist Bahr.K
Specialist Chilly.K
Specialist Crabtree.B
Specialist Schmidt.B
Specialist Thomas.D
Specialist Ratliff.B
Private Abi.K
Private Granger.L
Private Astro.M
Private Grace.JA
Specialist Harvey.D
Pros
Cons
Planning & Briefing
- ROE was not emphasized / missed in the briefing
- Briefing details not shared early enough (suggest 1-2 days prior)
- This would ideally be followed by Flight Leads meeting to coordinate further
- Additionally, SLs should be prioritized for Flight Leads
- Roll call should open earlier
Mission Setup & Environment
- Weather/visibility too poor, contributing to mission failure for A2G Tasking
- Wind was not considered when selecting RWY 12 for landing
- LotATC drawings blocked too much map area
Callsigns & Coordination
- Callsign confusion caused issues with tasking
- Pilots entered the wrong airframes, which caused some issues with tasking
Threat/Asset Balance
- Too many SAMs, not enough enemy aircraft
+ However from a Mission Perspective, this was intended
- Pilots perceived that there were too many tankers
+ However these were likely civilian airplanes, added to "clutter" the airspace.
- AI difficulty could be increased
Name of Combat Mission: Operation Double Negative
Number Within Campaign: 1/1
Game: DCS
Server: Operations Server 1
Date of Combat Mission: 28FEB2026
Time of Combat Mission (Zulu): 1900Z
OIC: Second Lieutenant Melk.J
Mission Controller: Staff Sergeant Remeslnik.F
Mission Controller: Chief Warrant Officer 2 Dibdin.H
Mission Controller: Warrant Officer 1 Baruch.J
TOTAL - 20
Second Lieutenant Melk.J
Staff Sergeant Remeslnik.F
Chief Warrant Officer 2 Dibdin.H
Warrant Officer 1 Baruch.J
Warrant Officer 1 Folmer.R
Warrant Officer 1 Landry.H
Warrant Officer 1 Swift.A
Corporal White.M
Specialist Ackerman.J
Specialist Bahr.K
Specialist Chilly.K
Specialist Crabtree.B
Specialist Schmidt.B
Specialist Thomas.D
Specialist Ratliff.B
Private Abi.K
Private Granger.L
Private Astro.M
Private Grace.JA
Specialist Harvey.D
Pros
- Overall fun mission enjoyed by most participants
- FTX concept was well-received; participants want more like it
- Target-rich environment
- AI felt realistic and coordinated, with a sense of teamwork on their part
- Good balance to the mission overall
- Opportunity for engagements (e.g., dog-fighting)
Cons
Planning & Briefing
- ROE was not emphasized / missed in the briefing
- Briefing details not shared early enough (suggest 1-2 days prior)
- This would ideally be followed by Flight Leads meeting to coordinate further
- Additionally, SLs should be prioritized for Flight Leads
- Roll call should open earlier
Mission Setup & Environment
- Weather/visibility too poor, contributing to mission failure for A2G Tasking
- Wind was not considered when selecting RWY 12 for landing
- LotATC drawings blocked too much map area
Callsigns & Coordination
- Callsign confusion caused issues with tasking
- Pilots entered the wrong airframes, which caused some issues with tasking
Threat/Asset Balance
- Too many SAMs, not enough enemy aircraft
+ However from a Mission Perspective, this was intended
- Pilots perceived that there were too many tankers
+ However these were likely civilian airplanes, added to "clutter" the airspace.
- AI difficulty could be increased
Last edited:
