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!
Disappointment
Road to Dunkirk #15
(Defender) Germany vs Britain (Attacker)
France (Attacker)
Formations Involved
Display
Balance:



Overall balance chart for RtDk015
Total
Side 1 0
Draw 1
Side 2 1
Overall Rating, 2 votes
5
4
3
2
1
4
Scenario Rank: --- of 940
Parent Game Road to Dunkirk
Historicity Historical
Date 1940-05-27
Start Time 07:00
Turn Count 20
Visibility Day
Counters 43
Net Morale 1
Net Initiative 2
Maps 2: 123, 125
Layout Dimensions 56 x 43 cm
22 x 17 in
Play Bounty 154
AAR Bounty 227
Total Plays 2
Total AARs 0
Battle Types
Inflict Enemy Casualties
Urban Assault
Conditions
Hidden Units
Off-board Artillery
Smoke
Scenario Requirements & Playability
Road to Dunkirk Base Game
Introduction

The western wing of the combined French-British assault against the German bridgehead at Abbeville involved Dragoons from the 5e Division Légère de Cavalerie and cruiser tanks from the 1st Armoured Division. A combined battle group advanced into the narrow Tire valley, running from south to north almost perpendicular to the Somme River. They expected light opposition from German sentinels on the bridgehead flanks.

Conclusion

The Allies coordinated poorly while the Germans prepared to stand fast. At the mouth of the valley the British tanks achieved some transitory success, pushing away light opposition in Rogeant and Toeufles. Behind them, French infantry mopped up the villages while the cruiser tanks exited the valley and reached the plateau west of Moyenneville. This town was the gate to Abbeville and heavily defended by German AT guns and mortars. The anti-tank guns easily pierced the British tanks’ light armor and cut the attack to pieces, destroying six tanks. The French set up defensive positions north of Toeufles and fought off a German counterattack later in the afternoon. The result was an immense disappointment to Maj. Gen. Roger Evans of 1st Armoured Division.


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).
  • 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.
  • Portees: Trucks with mounted Anti-Tank guns, Anti-Aircraft weapons, or artillery. Stack as combat units. Move like trucks, but fire like guns. Do not limber or unlimber. Have the truck's -1 armor value. Truck and gun are treated as a single unit, and do not transport other units. (SB)

Display Order of Battle

Britain Order of Battle
Army
  • Motorized
France Order of Battle
Armée de Terre
  • Leader
Germany Order of Battle
Heer
  • Towed

Display Errata (3)

3 Errata Items
Overall balance chart for 853

The Mk VIb in Road to Dunkirk were printed with a movement factor of 5. The piece should have a movement of 9.

(plloyd1010 on 2024 Aug 15)
Overall balance chart for 20

The reduced direct fire value of the Heer HMG became 5-5 starting with Fall of France.

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

The movement allowance on the counters in Airborne is misprinted. It should be "3."

(rerathbun on 2012 Jan 30)
Errors? Omissions? Report them!
Page generated in 0.193 seconds.