Panzer Grenadier Battles on April 27th:
Arctic Front Deluxe #40 - Children's Crusade Broken Axis #14 - Târgu Frumos: The Second Battle Scenario 3: Sledge Hammer of the Proletariat
Army Group South Ukraine #6 - Consternation Road to Berlin #73 - She-Wolves of the SS
PG-HQ Library - Panzer Grenadier Hall > Scenarios > GDaK010
Errors? Omissions? Report them!
With Field-Drill Precision
Grossdeutschland at Kursk #10
(Attacker) Germany vs Soviet Union (Defender)
Formations Involved
Germany 332nd Infantry Division
Germany Grossdeutschland Division
Soviet Union 184th Rifle Division
Soviet Union 219th Rifle Division
Display
Balance:


Overall balance chart for GDaK010
Total
Side 1 0
Draw 0
Side 2 0
Overall Rating, 0 votes
5
4
3
2
1
0
Scenario Rank: --- of 913
Parent Game Grossdeutschland at Kursk
Historicity Historical
Date 1943-07-14
Start Time 04:00
Turn Count 30
Visibility Day
Counters 192
Net Morale 1
Net Initiative 2
Maps 3: 40, 41, 42
Layout Dimensions 84 x 43 cm
33 x 17 in
Play Bounty 274
AAR Bounty 227
Total Plays 0
Total AARs 0
Battle Types
Hill Control
Inflict Enemy Casualties
Road Control
Conditions
Entrenchments
Minefields
Off-board Artillery
Randomly-drawn Aircraft
Reinforcements
Smoke
Terrain Mods
Scenario Requirements & Playability
Broken Axis Counters
Grossdeutschland at Kursk Base Game
Burning Tigers 2 Maps + Counters
Introduction

Having failed in both attempted attacks on the previous day, the Grossdeutschland panzer regiment jumped off promptly when given a chance to redeem itself. With infantry and support elements from the 332nd Infantry Division and strong support from Air Force Stuka dive bombers, the German attack seemed very promising.
Conclusion

Advancing with what Mellenthin would call “field-drill precision,” the Germans struck the boundary between the Soviet 184th and 219th Rifle Divisions, pushing the defenders back and apart to open a breach in the Soviet lines. The Soviets responded with heavy artillery fire that drove off the panzers’ supporting infantry, and followed up with a counter-attack by a tank brigade that devolved into a hard-fought close-range shootout. The German advance ground to a halt, but the lines had, for the moment, been restored.
Display Relevant AFV Rules
AFV Rules Pertaining to this Scenario's Order of Battle
  • Vulnerable to results on the Assault Combat Chart (7.25, 7.63, ACC), and may be attacked by Anti-Tank fire (11.2, DFT). Anti-Tank fire only affects the individual unit fired upon (7.62, 11.0).
  • AFV's are activated by tank leaders (3.2, 3.3, 5.42, 6.8). They may also be activated as part of an initial activating stack, but if activated in this way would need a tank leader in order to carry out combat movement.
  • AFV's do not block Direct Fire (10.1).
  • Full-strength AFV's with "armor efficiency" may make two anti-tank (AT) fire attacks per turn (either in their action segment or during opportunity fire) if they have AT fire values of 0 or more (11.2).
  • Each unit with an AT fire value of 2 or more may fire at targets at a distance of between 100% and 150% of its printed AT range. It does so at half its AT fire value. (11.3)
  • Efficient and non-efficient AFV's may conduct two opportunity fires per turn if using direct fire (7.44, 7.64). Units with both Direct and AT Fire values may use either type of fire in the same turn as their opportunity fire, but not both (7.22, 13.0). Units which can take opportunity fire twice per turn do not have to target the same unit both times (13.0).
  • Demoralized AFV's are not required to flee from units that do not have AT fire values (14.3).
  • Place a Wreck marker when an AFV is eliminated in a bridge or town hex (16.3).
  • AFV's do not benefit from Entrenchments (16.42).
  • AFV's may Dig In (16.2).
  • Open-top AFV's: Immune to M, M1 and M2 results on Direct and Bombardment Fire Tables, but DO take step losses from X and #X results (7.25, 7.41, 7.61, BT, DFT). If a "2X" or "3X" result is rolled, at least one of the step losses must be taken by an open-top AFV if present.
  • Closed-top AFV's: Immune to M, M1 and M2 results on Direct and Bombardment Fire Tables. Do not take step losses from Direct or Bombardment Fire. If X or #X result on Fire Table, make M morale check instead (7.25, 7.41, 7.61, BT, DFT).
  • Closed-top AFV's: Provide the +1 modifier on the Assault Table when combined with infantry. (Modifier only applies to Germans in all scenarios; Soviet Guards in scenarios taking place after 1942; Polish, US and Commonwealth in scenarios taking place after 1943.) (ACC)
  • Tank: all are closed-top and provide the +1 Assault bonus, when applicable
  • Armored Cars: These are Combat Units. They are motorized instead of mechanized. All have their own armored car leaders, who can only activate armored cars (6.85). Do not provide the +1 Assault bonus (ACC).
  • Reconnaissance Vehicle: 8.23 Special Spotting Powers Both foot and vehicle mounted recce units (1.2) possess two special spotting abilities. The first ability is that they can spot enemy in limiting terrain at one hex further than the TEC specifies for other units and leaders. For example, an enemy unit in town can normally be spotted at three hexes or less, but a recce unit can spot them at four hexes.Their second ability is that they can place a Spotted marker on any one enemy unit they can spot per turn, just as if the enemy unit had "blown its cover" by firing. Such Spotted markers are removed as described earlier.
  • Prime Movers: Transports which only transport towed units and/or leaders (May not carry personnel units). May or may not be armored (armored models are open-top). All are mechanized. (SB)
Display Order of Battle
Germany Order of Battle
Grossdeutschland Division
  • Motorized
  • Towed
Heer
Soviet Union Order of Battle
Army (RKKA)
Display Errata (2)
2 Errata Items
Overall balance chart for 63

The morale and combat modifiers of German Sergeant #1614 should be "0", not "8".

(Shad on 2010 Dec 15)
Overall balance chart for 951

The reduced direct fire value in Kursk: Burning Tigers is 4-4.

(plloyd1010 on 2015 Jul 31)
PG-HQ Library - Panzer Grenadier Hall > Scenarios > GDaK010
Errors? Omissions? Report them!
Page generated in 0.408 seconds.