Panzer Grenadier Battles on November 21st:
Desert Rats #16 - The Panzers Pull Back Desert Rats #19 - The Panzers Return
Desert Rats #17 - The Tomb Of Sidi Rezegh Jungle Fighting #7 - Line Of Departure
Desert Rats #18 - A Pibroch's Skirl South Africa's War #5 - Irish Eyes
Errors? Omissions? Report them!
Beat Down
Red & White #17
(Attacker) Soviet Union vs Poland (Defender)
Formations Involved
Poland 3rd Mechanized Division
Soviet Union 303rd Rifle Division
Soviet Union 4th Guards Airborne Division
Display
Balance:



Overall balance chart for ICRW017
Total
Side 1 0
Draw 0
Side 2 0
Overall Rating, 0 votes
5
4
3
2
1
0
Scenario Rank: of
Parent Game Red & White
Historicity Historical
Date 1951-11-15
Start Time 11:15
Turn Count 24
Visibility Day
Counters 227
Net Morale 0
Net Initiative 1
Maps 3: 17, 22, 24
Layout Dimensions 84 x 43 cm
33 x 17 in
Play Bounty 273
AAR Bounty 227
Total Plays 0
Total AARs 0
Battle Types
Exit the Battle Area
Hill Control
Inflict Enemy Casualties
Road Control
Urban Assault
Paradrops
Entrenchment Control
Conditions
Anti-infantry Wire
Entrenchments
Minefields
Off-board Artillery
Randomly-drawn Aircraft
Smoke
Scenario Requirements & Playability
Cassino '44 Counters
Elsenborn Ridge Maps
Hammer & Sickle Counters
Red & White Base Game
Road to Berlin Maps + Counters
Introduction

The most direct path to Warsaw for the Soviets leads west through Siedlce along Highway 2. Marshal Anders knew that the Soviets would apply overwhelming force along that path. To counter that strategy, he planned a mobile defense in front of a series of hard defenses to whittle the Soviets down. The problem would be getting the Soviets to fight at those defenses and not simply bypass them. Because of the major road intersection there, the Soviets had to take the town, but they'd been preparing for this kind of attack.

Conclusion

An airdrop is always a bit of a gamble. If the drop goes well the enemy planned defense can be seriously compromised, taking out key artillery installations and transportation choke points. If it goes poorly the units are widely scattered and unable to materially affect the battle, thus wasting precious resources. In either case, here, the Poles have set a strong defense in an area that must be taken due to the road confluences. And the Soviet player needs to take this quickly and fairly cheaply to continue the advance on Warsaw.


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
  • Assault Gun: if closed-top, provide the +1 Assault bonus, when applicable
  • Tank Destroyer: do not provide the +1 Assault bonus, even if closed-top (SB)
  • APC – Armored Personnel Carrier: These are Combat Units, but stack like Transports. They can transport personnel units or towed units. They are not counted as combat units for the +1 stacking modifier on the Direct Fire and Bombardment Tables (4.4). They may be activated by regular leaders and tank leaders (1.2, 3.34, 4.3, 5.43). They do not provide the +1 Assault bonus (ACC).
  • 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

Poland Order of Battle
Wojska Lądowe
  • Misc
  • Motorized
Soviet Union Order of Battle
Army (RKKA)
  • Motorized
Guards
  • Towed

Display Errata (3)

3 Errata Items
Overall balance chart for 951

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

(plloyd1010 on 2015 Jul 31)
Overall balance chart for 993

Kommissars never get morale or combat modifiers. Ignore misprints.

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

These units should have a Direct Fire rating of 2-3, just like the RKKA and NKVD counterparts.

(danradz on 2011 May 04)
Errors? Omissions? Report them!
Page generated in 0.379 seconds.