1000 mile war - liberating the Aleutians

[BBfanboy]

Well done on taking Attu! Your casualties are not bad at all - two squads totalling 26 men killed. The disabled ones will recover with rest.
Now that you have the base the enemy's efforts to supply or extract the remaining Japanese will be much tougher for him. He might use subs to bring in supply.

You can count on his bombers trying to bomb your base and troops and maybe ships, but it will be sporadic. Get AA to Attu ASAP. Kiska should be fairly safe from air attack so you can relax on CAP there and just keep his AF and troops under bombardment.
If his bombing on Attu is causing casualties consider building a few levels of forts as soon as the damage is repaired. Forts will reduce the impact of his bombing on your troops and your base facilities.

Also expect the AI to send surface ships to bombard. It has not used them much so far so the "react" script for your taking of Attu might bring them. Sow some mines at Attu if you can - 100+ to start being dangerous and another 100 or 200 to start being nasty. [:)]

EDIT: PS - don't forget to sweep regularly against his mines. Subs could sow them without you knowing.

[Energisteron]

Thanks again, BBf

I'll check out my infantry status (fatigue, combat value, and supplies) and make another attack tomorrow if possible.

To be honest Attu is a desolate mess with hardly any immediate capability remaining.

I have AAA on the way already. They've reached Adak and will be joined by a Combat Engineer Regiment when the Sea Bees disembark and take over all construction work at Adak.

I'm aware supply and reinforcements must be prevented from reaching what must by now be the fairly desperate defenders of both Attu and Kiska.

As for IJN intervention, I am hoping to transfer all naval support to Adak and base my capital ships there. I intend putting a surface ship cordon around both islands with a submarine picket line to the west.

More action soon . . .

[Energisteron]

Day 40 - May 24

A quiet night is followed by our continued air attacks against the ground forces on Attu and Kiska. Kiska airfield also gets some attention and justifiably since a couple of Japanese fighters get into the air to oppose. Results are satisfactory but we lose 1x Ventura to flak. Air to air we score no kills despite the inclusion of Kittyhawks, Wildcats and Lightnings.

Naval operations continue without interruption as before.

Despite our troops being quite frayed after two days heavy combat we make another attack on Attu. This time the defenders are destroyed as a cohesive unit. We have Attu to ourselves!

[BBfanboy]

Nice to wipe out the remnants so quickly! You got some good die rolls there!
Not sure how many days left in the scenario. If you think there might be time enough to invade PJ and kill all chance of reinforcement of the Aleutians by the IJA, you could start prepping now. But if there is less than six weeks left I would keep most troops prepped for Attu to help them fight better if the Japanese try to land more troops.

Sounds like you want to use Combat Engineers at Attu to repair damage and build the base. This is OK if there is no combat to be had, but their first priority role is to assault enemy forts and destroy them. I hope you have some at Kiska.

[Energisteron]

Hi BBf

I believe the scenario is exactly 60 days long so we're two-thirds through. 20 days to go.

P-jima! It crossed my mind but I feel eliminating Kiska is the next priority both strategically and according to my orders. I am hoping it will fall like a ripe plum, but we'll see! Also, placing surface ships much further west than Attu Island is going to invite enemy air attack with all their attendant risks.

I would have liked my Engineers along with the troops on Attu but lack of fast transports and the apparent need of bulking up the Assault Value with another Infantry Regiment prevented them getting them there. I have a Regiment of Combat Engineers who will go to Attu. An equivalent Battalion will go with the invasion to Kiska.

[Energisteron]

Day 41 - May 25

Fairly routine by now. No enemy action except Recon. The Sea Bees disembark at Adak and are replaced on board by a Combat Engineer Regiment. These troops and the AAA already loaded are bound as reinforcements for Attu. Generally, air crew are rested but we make a few air raids on Kiska just to keep annoying the defenders. We have no losses and once more we bombard the island during the night with two Cruisers. Quit a good day.

[Energisteron]

Day 42 - May 26

I thought I'd illustrate how my Air Search and Recon is set-up.

Two groups of 12x Catalinas from Adak and Dutch Harbor are doing the majority of the work operating Naval Search at 10k ft. They have a huge tract of ocean to survey so I make no pretence that we would see everything coming our way! A smaller group of 6x Catalinas on Adak has just been switched from Recon of Attu Island to Naval Search of the SW approaches to Kiska. That zone is through which the enemy seem to have been passing to resupply Kiska Island so I felt we needed extra coverage there.

ASW patrols of 12x Venturas at 8k ft are operating from both Adak and Dutch Harbor in two swathes of about 200 degree arc.

Recon of enemy held islands was done at Attu by the 6x Catalinas mentioned above, and by 6x (from 12) Venturas operating from Dutch Harbor for Kiska. The altitude gradually came down from 14k ft to 10k ft as we assessed the threat from flak.

[Energisteron]

Day 42 - May 26

The action : what action? We make one token air strike against Kiska to little effect and that's it. No losses and the Bettys are a no show today.

So what still opposes our objective of taking Kiska? We could well face a force similar in size to that at Attu although hopefully considerably degraded. Kiska base is in a bad way although it is repeatedly repaired but we've just about kept it inoperable for quite a while now.

And what of distant Paramushiro-jima? We have no Air Recon at that distance, only Signal Intelligence intercepts, and presumably information gathered by agents on the ground, especially the Russians and Chinese. Over the past month there have been reports of tremendous activity and there is no doubt it is a thriving bustling base. A best guess from intelligence received would be as follows: Army - 10-20k troops including Engineers, AAA, Artillery and a Tank detachment: Air: 1x Group Bettys, Recon aircraft, Fighters and Bombers of shorter range plus support troops: Navy - hardly a snippet! - presumably, base defence craft, and maybe a small flotilla of Destroyers to escort Freighters, but surely there's something heavier? Their submarines must operate from there too.

There are constant reports of 'heavy' radio traffic emanating from Paramushiro-jima so something big could be brewing! There's even hints of a Carrier force and Cruisers.

Given that potential threat we need to plan our next operations carefully. I have set the following schedule: 1. Fortify Attu then improve airbase, 2. Invade Kiska, 3. Base BBs and CAs at Adak, 4. Conquer Kiska, 5. Move an offensive SS cordon nearer Paramushiro-jima.

Any other suggestions would be gratefully received.

[Energisteron]

Day 43 - May 27

A quiet day from our point of view. The Bettys pay a visit to Attu but Wildcats from CVE Nassau intercept and they fail to reach their target. Again we claim one kill.

Loading up of the Engineers at Adak seems to be taking forever, but hopefully they'll be on their way to Attu in the morning.

[Energisteron]

Day 44 - May 28

Eleven Bettys make a more determined attack on Attu. Again Wildcats intervene and knock down 2 enemy aircraft. However, 4x Bettys do reach the target but cause little damage.

Elsewhere all proceeds as planned. Supplies and reinforcements are approaching Attu unmolested. A small fast CL TF patrols just west of Attu to intercept or forewarn of any enemy approach. Subs continue to patrol around Attu and Kiska. All land based air operations except Recon suspended for now. Another bombardment TF is sent towards Kiska.

AND most importantly the first wave of the intended Kiska invasion begins to load up. This will consist of 13th Canadian Brigade and 53rd US Infantry Regiment in 4xAPAs and 1x xAP. Escorts being prepared.

[BBfanboy]

ORIGINAL: Energisteron

Day 42 - May 26

I thought I'd illustrate how my Air Search and Recon is set-up.

Two groups of 12x Catalinas from Adak and Dutch Harbor are doing the majority of the work operating Naval Search at 10k ft. They have a huge tract of ocean to survey so I make no pretence that we would see everything coming our way! A smaller group of 6x Catalinas on Adak has just been switched from Recon of Attu Island to Naval Search of the SW approaches to Kiska. That zone is through which the enemy seem to have been passing to resupply Kiska Island so I felt we needed extra coverage there.

ASW patrols of 12x Venturas at 8k ft are operating from both Adak and Dutch Harbor in two swathes of about 200 degree arc.

Recon of enemy held islands was done at Attu by the 6x Catalinas mentioned above, and by 6x (from 12) Venturas operating from Dutch Harbor for Kiska. The altitude gradually came down from 14k ft to 10k ft as we assessed the threat from flak.

Search at those setting must be costing you lots of operational losses! Some things about Nav Search:

- Developers say the best search altitude is 6000 feet - a compromise between distance to the horizon and ability to see a small ship at that distance. Weather of course plays a huge part in actually seeing something, but aircraft with radar get extra detection bonuses.

- Developers also stated that, beyond 12 hexes, search effectiveness falls off sharply because the width of the " 10º wedge" of search gets too big to see all of it. Operational losses also go up sharply as your aircraft approach their maximum range. 12 is a good range for Cats. Venturas should be a bit less. I go at least one hex short of "normal" range for the aircraft. Crew fatigue also decreases from shorter patrol ranges.

- ASW patrols are more intensive than Nav Search because they are looking for such a small vessel or even just a periscope wake. If you set ASW to range 12, it actually only searches to range 6. But out to range 4 in all directions is assumed by the AI to be automatically searched because of the comings and goings of aircraft. Not sure if that is ASW search or just Naval Search.

- because of the difficulty seeing subs, and because you want to be under most clouds, I use 4000 feet for ASW search. If I already have detection I sometimes lower the altitude further to maximize chance of an attack.

- 200º arc search would require at least 20 aircraft. One aircraft searches one 10º arc in one phase and will only search a second time (in the afternoon phase)if the range is very short.


And a comment about the "heavy radio traffic" at PJ - you are correct about needing to prepare for something. That message does not normally appear for small TFs of auxiliary ships and a few xAKs - it is usually from a large amphib TF and/or a TF of major warships (CVs or BBs or CAs at least). You might want to get Nassau under fighter cover until you find out what you are facing.

About sub pickets at PJ - putting them close to the island is unlikely to result in detection of an enemy sortie because it will depart at night and your sub may already be detected by the enemy's air search (which increases his chance to avoid it).
Consider that most Amphib TFs move three hexes in a phase and Naval TFs of fast ships usually move four hexes in the first phase and five in the second phase.
Now place your subs along the path from PJ to Attu at ranges of 3,4, 6 and 9 hexes. Your subs are much more likely to get a chance to attack if the enemy TF ends its movement in the same hex as your sub rather than transiting through the sub hex.

[Energisteron]

Wow, BBf, thanks for your detailed critique of search and interception. Another bit for cut and paste!

I am surprised but Catalina losses are quite low; 2 to flak and 2 to ops. I have lost 5 Venturas to ops though.

Regarding sub interception : so, is movement not fluid and dynamic? Does nothing happen between the start hex and the end hex? If the latter, that would mean a ship could just 'skip over' a sub during its move of 3 hexes say!

I do have a web of sub patrol zones out west of Kiska although I admit 2 are now locked to coastal patrols around Kiska itself.

[Energisteron]

Day 45 - May 29

Not a whisper of anything except the 'heavy radio traffic' at Paramushiro-jima!

Our Transports and Freighters commence unloading at Attu Island. We are vulnerable but no Bettys appear. The Kiska invasion TF is nearly loaded. Just a bit more ammo and supplies to pile into the Transports!

A classic case of, 'It's quiet. It's too quiet!'?

[BBfanboy]

ORIGINAL: Energisteron

Wow, BBf, thanks for your detailed critique of search and interception. Another bit for cut and paste!

I am surprised but Catalina losses are quite low; 2 to flak and 2 to ops. I have lost 5 Venturas to ops though.

Regarding sub interception : so, is movement not fluid and dynamic? Does nothing happen between the start hex and the end hex? If the latter, that would mean a ship could just 'skip over' a sub during its move of 3 hexes say!

I do have a web of sub patrol zones out west of Kiska although I admit 2 are now locked to coastal patrols around Kiska itself.

There is always a chance a sub will get in an attack on a transiting enemy TF but it is not as good as it is when the enemy has finished its phase of movement. Consider for a moment: a transiting enemy detects your sub and the escorts try to attack it or just force it away. Because the enemy still has movement points left it will move and, knowing where the sub is, there is very little chance of the sub getting a second attack attempt. Now consider the enemy TF stopped at the end of its movement - even if it detects your sub it cannot move away so your sub might get some good die rolls and make a second attempt at attack. Sub attack phases are calculated several times after the Naval Movement phases are over so that is three or four more chances on a fixed TF position.

[Energisteron]

Day 46 - May 30

Unloading continues at Attu. The Bettys appear but are repulsed.

The bombardment of Kiska is satisfactory.

[Energisteron]

Hello again, BBf.

Hmmm. I suppose there's some logic in that, certainly from the aspect that the escorts having a chance to prevent attack.

BTW : radio silence from Paramushiro- jima!!!

[BBfanboy]

Radio silence after heavy comms traffic usually means the enemy has sailed/steamed/motored ...

[Energisteron]

Yes, that's exactly how I read the situation; Japanese counterattack imminent!

So, how vulnerable is our current deployment? What objective will the enemy have selected?

Possible targets, in estimated order of probability, would be :-
1. An attack on Attu a) just to hurt us and b) to re-invade,
2. A heavily supported supply and reinforcement operation at Kiska (and this could run straight into our intended invasion!),
3. A retaliatory naval raid to catch and destroy as many of our units as possible (but that would probably mean no counter-invasion in the short term),
4. A bombardment and possibly even an invasion of Adak (this would be our plan in reverse, thus isolating our force on Attu!),
5. A bombardment way back at Dutch Harbor,
6. An opportunistic bluff in the hope to catch a couple of our units off guard and sink them,
7. Nothing at all!

As for our current vulnerablities:-
1. Freighters unloading supplies at Attu,
2. Fast transports at Attu having landed reinforcements and supplies (they can leave today with a fraction of supplies on board or within 24 hours empty),
3. Our troops on Attu Island,
4. Our (intended) invasion force ready to leave for Kiska,
5. Our air combat TF, CVE Nassau, north-east of Attu Island,
6. Our small TF of 2x CLs and 1x DD west of Attu,
7. Our bases at Adak and Dutch Harbor.

One thing is absolutely clear. If the Japanese have one or more Fleet Carriers then we have nothing to oppose them except land-based aircraft and these have little value in an offensive role. CVE Nassau has some good fighters, Wildcats, but alone she'd be overwhelmed so she must retire eastwards within 24 hours. However, we could transfer her Wildcats to a land-base. Unfortunately for the moment Attu as an airfield, or port for that matter, is unuseable so maybe they'd have to be dropped-off at Adak from where, I believe, they could just about transfer to a repaired Attu base.

So, what to do?

I am going to gamble that we have 24 hours (this next turn) free from serious interference and continue unloading at Attu. The next day, the fast transports will leave for Dutch Harbor, and all except one Freighter will go to Adak. Which Freighter draws the short straw I don't know yet!

CVE Nassau will remain near Attu for the next 24 hours only.

The ground forces on Attu are busy digging-in. I don't see what more can be done.

Our invasion of Kiska will go ahead unless a serious threat develops. They should land in 3 days.

What to do with our fast scouting TF with 2x CLs is a difficult question. It would be vulnerable to air attack or a superior enemy Capital Ship. If damaged their subs would close in to finish them off! But, I feel I need something 'out there' to counter attempts at supply for Kiska. They're going to stay on patrol there for at least 24 hours.

We'd have time to regroup against an attack directly on Adak or Dutch Harbor.

The Plan:-
1. Invasion of Kiska to go ahead immediately
2. Surface Combat TFs, one of BBs and one of CAs, will take up position north-east of Attu (approximately north of Kiska) covered by CVE Nassau which will retire on them in 24 hours.
3. All Recon capability will be moved to Adak with the intention of getting good intelligence of any enemy approach.
4. Long range bombers with little naval attack capability will move back to Dutch Harbor.
5. Fighters will be moved into Attu as soon as the airfield reaches level 2.
6. Anything else I think of 'on the hoof'

[BBfanboy]

Good assessment and response. Good luck! [:)]

[Energisteron]

Day 47 - May 31

So, today's moves will be as illustrated in accordance with above plan.

And that's exactly what happens! There's absolutely no interference by the enemy; no Recon, no radio traffic, nothing.

The Kiska Invasion TF has left Dutch Harbor.