Panzer Grenadier Battles on October 24th:
Afrika 1944 #22 - PAKfront Leyte '44 #12 - Flying Wedge
Fronte Russo #9 - Potemkin Village Leyte '44 #13 - Failure at Buri Airfield
Red & White #28 - Bastion
Errors? Omissions? Report them!
Warehouse Find
Saipan 2 #26
(Attacker) Japan vs United States (Defender)
Formations Involved
Japan 9th Tank Regiment
United States 2nd Marine Regiment
Display
Balance:



Overall balance chart for Sap2026
Total
Side 1 0
Draw 0
Side 2 1
Overall Rating, 0 votes
5
4
3
2
1
0
Scenario Rank: --- of 1093
Parent Game Saipan 2
Historicity Historical
Date 1944-06-24
Start Time 18:30
Turn Count 12
Visibility Day
Counters 10
Net Morale 0
Net Initiative 1
Maps 1: 83
Layout Dimensions 43 x 28 cm
17 x 11 in
Play Bounty 153
AAR Bounty 168
Total Plays 1
Total AARs 1
Duplicates Saip026
Battle Types
Exit the Battle Area
Inflict Enemy Casualties
Scenario Requirements & Playability
Saipan 2 Base Game
Introduction

On the afternoon of 19 June, a group of Japanese tankers from the 9th Tank Regiment who had lost their vehicles in the tank battle on the invasions first night entered Garapan. There, they found a warehouse with ten tanks that had been slated for shipment to Truk; apparently, they had mechanical defects. After several days’ work, they got seven of them to run again, and set out to attack the Marines pressing in on the town.

Conclusion

The tanks went forward without coordinating their attack with any other Japanese units; the crews had been out of contact with their regiment for days. They soon ran into Sherman tanks and half-track mounted 75mm guns, which shot of six of them; the seventh somehow escaped. But while the Americans touted their victory over the odd attack, neither had they moved any closer to Garapan.


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
  • Anti-Tank Gun Carrier: half-track with anti-tank gun, NOT a Tank Destroyer

Display Order of Battle

Japan Order of Battle
Imperial Japanese Army
  • Mechanized
United States Order of Battle
Marine Corps
  • Foot
  • Mechanized

Display Errata (1)

1 Errata Item
Overall balance chart for 1466

The 8-3 Marine Infantry counter appears in most of the Saipan 1944 and Marianas 1944 scenarios, replacing the 10-3 DF valued Marine counters for those scenarios and is currently published in the most recent Saipan printing.

(JayTownsend on 2015 Dec 26)

Display AARs (1)

Saipan 2nd Edition, scenario #26: Warehouse Find
Author JayTownsend
Method Solo
Victor United States
Play Date 2026-08-30
Language English
Scenario Sap2026

Saipan 2nd Edition, scenario #26: Warehouse Find

Since the Marines setup first, the Japanese have 4 obvious routes to try, the half hexes north or south flanks, the obvious down the center road or through the southern hill with a light jungle path. They must also decide if they want to wait until dark, stay together or split their two units down different paths and lastly, fight and hope for to eliminate two enemy steps or try and get one step off the eastern edge of the map.

This gameplay, I decided to make a run for it through the light jungle hill and back on to the road, as the Americans were kind of spread-out defending the obvious enemy paths but the Americans were able to react well and intersect the enemy armor about the middle of the map and rolled first on the activation the next turn, eliminating all three Japanese armor steps. Maybe if the Japanese had activated first, they could have eliminated the American M3/75 halftrack and a possible victory, but the M4 Sherman tank would have been a tall order. So, in this gameplay, it was an American victory. The Infantry are more like blocking pawns and are not dug-in.

This was kind of a novelty scenario or a chest-match. The luck of the dice plays a large factor into this scenario.

0 Comments
You must be a registered member and logged-in to post a comment.
Errors? Omissions? Report them!
Page generated in 1.832 seconds.