JuiceBox

@graveyard4DCS That is the chef's kiss right there.

I'm not advocating we build missions with large stacks, rather sharing what was done, and i'm sure we can simplify it in DCS but give the payer the feeling of the stack.

Community/mods, please let me know if this content is all in the right place or I should be posting this somewhere else. As I think more about mission creation here, allow me to share an important concept to think about while editing. I don't know how common knowledge this piece is. The Stack In the OEF Afghanistan campaigns around 2010-2013 (my time there) the US usually employed a “stack” concept when providing close air support (CAS). At its most basic, this meant placing multiple aircraft at different altitudes, each with distinct responsibilities that together created persistent coverage for ground forces. Below is a simplified breakdown of how that often looked: High altitude/ on call strikers Aircraft such as B1B Lancers or even B52s (in certain cases) could orbit above 20,000 to 25,000+ feet. Their primary role was to deliver heavier ordnance if needed, providing a large weapons payload and long loiter times. The B52 was the ONLY aircraft I didn't see while in country. Because they were high above the fight, these bombers could remain on station for extended periods and quickly respond when a JTAC on the ground requested precision strikes Mid altitude CAS and overwatch Fighters like the F18, F16, F15E, or sometimes A10s would orbit at medium altitude (15,000–20,000 feet). They offered a mix of precision-guided munitions and the ability to drop quickly into lower altitude if needed for more direct engagement. They often acted as armed overwatch using targeting pods to keep eyes on the ground situation, track movement, and coordinate with the JTAC or an airborne command element (like an AWACS). Low altitude / direct attack layer Closer to the ground, rotary-wing aircraft (AH64 Apache, UH1/AH1 in the Marine Corps) might operate for immediate direct fire support. In certain situations, AH64s orA10s or even armed UAVs could orbit lower if required for more precise strikes or to maintain sensor coverage. This lower altitude “layer” was more intimately involved with troops in contact, conducting shows of force and direct strafing runs if needed. Supporting elements AWACS could remain on station even higher up or off to the side of the operations area, providing big-picture radar coverage, deconfliction of airspace, and communications relays. KC135 or KC10 Tankers loitered in safe zones, enabling fighters, bombers, and other aircraft to quickly refuel and remain onstation for longer periods this was essential to maintain a persistent presence Coordination and deconfliction A key part of the CAS stack concept was strict altitude separation. Each flight would “own” a particular block of airspace, preventing accidents and ensuring quick maneuverability without colliding or interfering with the other aircraft. The JTAC on the ground used radio nets and datalinks to talk to the different layers, requesting strikes or shows of force as the ground situation evolved. The overlapping fields of sensor coverage and ordnance meant ground forces could quickly receive the best suited air asset for their immediate threat. If one layer was busy or low on fuel, another layer could hand over coverage. This fluid hand-off minimized “gaps” in CAS availability. By stacking aircraft at multiple altitudes, the U.S. could keep eyes on the ground, quickly move fighters or bombers into strike positions, and respond to dynamic threats with minimal delay. When setting up a scenario in DCS to replicate this doctrine, you can simulate each “layer” at different altitudes (and possibly different orbits or racetracks). Incorporate AWACS for overall awareness, include tankers to keep your fighters and bombers on station, and ensure that a JTAC unit on the ground controls strikes, if mission dictates. Most of the time there was not a JTAC unless it was an offensive raid of some kind, or a TIC (troops in contact). This approach will give you a realistic feel for how layered CAS was typically executed by US forces around 2010. As the lowest layer AC supporting the TIC would run out of fuel or munitions, the stack would all go down one level. It would not be uncommon to have 8-10 aircraft during the fighting season. Khost's fighting season was longer than the rest for the reasons I mentioned in post 1. I couldn't find a diagram online so I made a crappy one with chat gtp Altitude (High) ┌───────────────────┐ │ B-1B/B-52 │ (Long loiter, heavy payload) └───────────────────┘ Altitude (Medium) ┌───────────────────┐ │ F-15E / F-16 / A-10 / F-18 │ (Precision strikes, armed overwatch) └───────────────────┘ Altitude (Low) ┌───────────────────┐ │ AH-64 │ (Direct fire support) └───────────────────┘ Ground Level ┌───────────────────┐ │ JTAC / Troops │ └───────────────────┘ Tanker & AWACS often hold in adjacent orbits off to the side (not shown) to handle refueling and overall command & control. Does all of that make sense? ASk me any question here, or if you want me to give a scenario. What I don’t know is how it would work in the editor.

@DD_Friar Afghanistan easily hit 120+ F in the summer, and very humid, the hot air and high altitude made it very difficult for the AH64 to perform well. It wasn't designed for this and suffered a lot in performance. fun facts

@toubey In the east the AGL was very high. So 10k feet was the basis of aircraft prep. Extra fuel, 300 rounds in the cannon, one rocket pod, 2 hellfires. And they had to do a rolling take off because of the weight. I saw one nearly crash into the berm because it couldn't get the lift it needed. I bounced off the top and sheared the wire uptop.

@toubey I have not created a list yet. On the east side, most fixed wing a/c will come out of Bagram Airfield. The primary helicopter airfields were FOB Shank, FOB Salerno, and the main on in Jalalabad (FOB Fenty?). Those three had Apache, Chinooks, and Black Hawks. The rest of the bases were smaller combat outposts, some may have had UH60s there for Medevac, or short time stationing. Maintenance and supply were the main reasons you had consolidation at the larger bases. @Ala12Rv-Tundra You're not going to find good photos on google maps right now, it appears to be scrubbed. I do have google earth photos of the main bases back when I was over there. They were public facing so it shouldn't be any issues sharing. Right now I'm not going to openly post them.

That is the Bala Hesar fortress in the center of Gardez City. https://www.google.com/maps/place/Gardez+Forte+بالاحصار+گردیز‭/@33.5977221,69.2315127,17.5z/data=!4m15!1m8!3m7!1s0x38d69270321aa10b:0x62e2e20e2c5374a3!2sGardez,+Afghanistan!3b1!8m2!3d33.6042793!4d69.2281531!16zL20vMDFia3c0!3m5!1s0x38d69354a36793c1:0x898e33683dd0ac53!8m2!3d33.5977614!4d69.2315198!16s%2Fg%2F11kmrrfvc7?entry=ttu&g_ep=EgoyMDI1MDIxOS4xIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3

How's this!? These are Google Earth screen shots I took before they were taken down around 10 years ago. I did Med-evac there

Hello community! Long time reader, first time posting. Call me JuiceBox, a call-sign given to be because I was the youngest guy in my unit (by far). I deployed to both Iraq and Afghanistan as a crew-chief for medical evacuation on UH-60s. With the upcoming eastern Afghanistan map coming, I wanted to try to find someone who can create some of my deployment missions in the Khost region. It was the single most dangerous region of all of Afghanistan for reasons I’ll share below. I’m not diminishing all the other incredibly dangerous regional locations, but Khost concentrated a lot of conflict to a small area that the US was never able to fully control. Allow me to share a little context of the importance of Khost in terms of the war against the Taliban and playing DCS. This is a 1-inch-deep level of depth I’m sharing. We dive deeper another time. Khost is well populated, easy to hide. And because of some unique geographical mountain ranges during the winter, the ranges shielded the region from the heaviest snowfall making the goat paths traversable year round. This was the major insurgent highway. What also increased the danger of this region was that was only one developed mountain roadway from Khost and the rest of Afghanistan to the west. Known as “ambush alley”. So the insurgency had a year round passage. Needless to say there was a lot of activity there. I highlighted the heaviest are of conflict in the east side of the country. The farthest right side of the circle is Khost, and the mountain passes to the left of it. I hope the developers give the region a extra attention here because I imagine a lot of play time will be centered in this region. I thought the community might enjoy going through some missions based on real life events and situations that I experienced throughout the year. While I can supply the mission context, I need an experienced mission creator to help make it come to life. This region is especially great for DCS, the mountains will make for challenging air to ground missions, 2 major bases are in the region Bagram Air Base, and FOB Shank so close places for A-10s, F-16s, F-15s, B-1s and F/A-18s to launch missions from, 6 FOBs for helicopters missions, a secret CIA base, and several more combat outposts to support. There were 3 main FOBs inside of the Khost valley to the far east. I lived at nearly all of them and even lived and slept in one of buildings Osama bin laden used to plan the 9/11 attacks. FOB Gardez was one of the first US bases used by Special Forces in the very beginning of the war. Every kind of mission set can take place in this area. I or my unit was involved in almost everyone from SF raids, med-evacs, combat escort, TICs (troops in contact), fire support, base defense, hunter killer mission of a 61k lbs truck bomb (yes I was there for that), and more. Heck, we learned the Taliban had a ZSU-23 hidden somewhere (yes it was terrifying to go on mission knowing that). We never found it, so we can even do a SEAD mission. I would love to work with someone(s) to help create some real life context to missions in a very strategic region.