pmaidhof

awe shucks, there's always next year...

Two more Intermediate Turns last night got us to a point of being just within range so that the 3rd Generation ESM on the Tarantul III should be able to detect the LCS's active radar. With that I would assume that the minelaying operation would cease as the Natya I tries to get out of Dodge, with the Tarantul III providing cover. Also, the Kilo has gotten itself out of the mud and is now prowling. Finally, the EL/M-2226 Coastal Surveillance Radar has been retro-fitted to be in the Redrock ports of Panstrike and Briarton, so we will see if the Exocet-equipped Super Puma may have its presence felt. The map scale has played the devil with me as I have grown accustom to 1”=1nm whereas this map is roughly .5”=10nm. Hopefully I can transition over to two pieces of 8.5x11 graph paper taped together for the upcoming engagements at 1"=1nm. Should have a couple of undisturbed RW hours tonight so things may get hot. For that we shall see.

Here was the opponent to the LCS that I used in the first two clashes. The K-130 Braunschweig, recently commissioned. K-130

If you scroll all the way to the bottom of this page, you will see the info on the Israeli EL/M-2226 Coastal Surveillance Radar. Here It speaks of detecting, in Sea State 3, rubber boats at >20km and patrol craft at >60km. My handy-dandy converter says thats >10.8nm and >32.4nm respectively. Will fudge the numbers upward a bit to take into account the ">" and go with that. Any other suggestions...?

"Since dropping the first two games at home, the Carolina Hurricanes have stormed back for three consecutive one-goal victories over the Canadiens." Oh-no!

The two merchantmen and a tanker left at dawn under an escort of Grayback gunboats to link up with the LCS “Task Group” (is that the right term for a three ship sub-grouping) 10nm outside of the port of Freeport. The USN LCS’ will escort these vessels to the port of Coupville. The LCS’ are equipped as follows: LCS 1: F(12)1 Mk48 VLS w/24 ESSM//1 Mk91, F(21)1 Mk31 w/21 RIM-116A RAM, P/S (1)2 12.7mm, A®1 Mk15 Phalanx Block 1B 20mm/76, ACommand and Control Module (Cooperative Engagement Capability), A Helicopter Platform fitted with RAST w/3 RQ-8 Firescout VTUAV. LCS 2: F(1)1 Bofors Mk3 57mm/70//F GFCS, F(21)1 Mk31 w/21 RIM-116A RAM, P/S (1)2 12.7mm, A(4)2 Mk141 w/4 Harpoon, A 1 AN/WLD-1 Remote Mine Hunting System and 1 AN/SLQ-48 Mine Neutralization Vehicle, A Helicopter Platform fitted with RAST w/3 RQ-8 Firescout VTUAV.. LCS 3: F(12)1 Mk48 VLS w/24 ESSM//1 Mk91, F(21)1 Mk31 w/21 RIM-116A RAM, P/S(1)2 12.7mm, A(4)2 Mk141 w/4 Harpoon, A(3)2 Mk32 w/3 Mk46 or Mk54 torpedoes, AQS-22 Sonar, and space for 40 sonarbuoys. The Task Group has conducted an uneventful movement to the its current position 10nm and on a bearing of 209 degrees from Port Known. The Task Groups current heading and speed is 090 degrees at 10kts. RQ-8 #1 is on a 45 degree bearing from the task group at a distance of 30nm. RQ-8 #2 is on a 135 degree bearing at a distance of 30nm. RQ-8 #2 has made a VISID of a Redrock Tarantul III. The Tarantul III is on a 158 degree bearing from the Task Group at a distance of about 26nm. The Redrock vessel did not display any hostile intent so it was not attacked. The activity of this vessel will be monitored. Unknown to BluFor, there is a Kilo sitting on the bottom just NNE of Middle Island. It’s MGK-400 Rubicon sonar operating passively failed to detect either the stealthy LCS or the "rumblin-stumblin-fumblin" civilian ships. The distance is just under 40nm so the Kilo may have to get off it's duff and begin to stalk the group. Also unknown to BluFor, just beyond the Radar Line of Sight, there is a Natya I minelayer escorted by a Tarantul III. The Natya is prepping to sow a mine barrier. Contact should occur over the next couple of tactical turns.

Brad, et al. As depicted in H4.1 and when employed as a networked team, the LCS concept seems to be solid. BlueFor has two of its three RQ-8's aloft with their 3rd Generation ESM on bearings of 045 left and right of center and at distances of 30nm from the main body of a three LCS force escorting three non-combatants. The opposing force initially has had a very difficult time getting into position undetected with its surface and air units. The next phase will be to test the ability of the Kilo and mine barriers to influence the battle. This phase also is proceeding into a tighter bottleneck, thereby providing the LCS force with less reaction time to attacks coming from Redrock proper. The SS will be sitting quietly at the bottom ENE of what I have labeled “Middle Island”. After a quick look at the map, it should be apparent where Middle Island is located. Also, about 15nm north of Middle Island a Natya I, with a mine rack of 7 mines, will begin to attempt sowing a mine barrier while escorted by a Tarantul III. A fairly serious drawback for the opfor is lack of an effective way to counter the RQ-8's. Non of the ships have an AS radar and all of their anti-air missiles have IRH guidance requiring a visual line of sight, which against an RQ-8 is 1.5nm - then subject to environmental conditional degredation. While it is open to debate, it does seem to be essential to have one of the LCS’ equipped with the Command Suite. This provides for the full cooperative engagement capability (CEC) so that the various LCS platforms can take advantage of each other’s unique capabilities and engage hostile targets with the most effective weapon systems. This is something that I will sortie from Freeport at high speed as I have been assigned a total of 5 LCS’.

I think I'll just use the H4 International generic AS and SS radar in each of the redfor ports unless you think it is too much of a stretch. Thanks for looking into it Brad.

What would be a good example of surface search radar, and air search radar while I’m asking, for a small to medium OpFor port facility . Port installations in HC seem to have them and their use in H4 would seem to be plausible. If not in the H4/High Tide, please hint to a link where I'd be able to find some stats. Thanks

While I'll still follow and enjoy the playoffs, NY Rangers stick a fork in ya...your done. Break out the golf clubs. Started ok with a 1-0 lead but the the dam broke. Can't negate the fact that Rangers entered the playoffs with a 5(?) game losing streak. While they performs at above expections from the start of the season, their good play actually raised expectations as the season went on. Oh well.

The way the NY Rangers played this regular season, up to the Olympic break, rejuvenated the franchise after failing to make the playoffs for more years than I care to remember. The lock-out/strike forced the Rangers to go with more of a youth movement than I believe management ever thought possible here in New York. We'll have to see how this project proceeds next season and beyond. The Rangers fate this year seems all but certain. The NJ Devils have outplayed the Rangers in every facet of the game. The 2005-2006 Devils will truely be a handful for their second round opponent and a valid contender for Lord Stanley's Cup. Thoughts,...how your team is faring?

DND Defers HMCS Chicoutimi Repair article (Source: Canadian Department of National Defence; issued April 27, 2006) OTTAWA --- The Department of National Defence today announced that repairs to Her Majesty's Canadian Ship (HMCS) Chicoutimi, damaged by fire in 2004, will be deferred until 2010 when a two-year refit on the submarine is conducted. This decision means that repairs caused by the 2004 fire incident will be conducted at the same time as the two-year refit process known as the Extended Dock Work Period, which is scheduled for 2010. If the repair process had begun immediately, HMCS Chicoutimi would have been back in service for less than two years before going back for the scheduled refit in 2010. The decision has the potential to save the department millions of dollars through a more effective allocation of resources. The Victoria-class fleet's operational capability will not be negatively impacted because of the deferral. Deferring these repairs will allow the Navy to focus its resources on other vessels and the surface fleet. This decision is the most cost effective method to address other competing priorities on current naval resources. "This will improve our ability to get Victoria and Corner Brook back into service and better position the Navy to have two boats fully operational in 2009," said Vice-Admiral Drew Robertson, Chief of the Maritime Staff. HMCS Chicoutimi is currently located at Halifax Shipyards Ltd. and will be placed in an extended limited maintenance period until the Extended Dock Work Period begins in 2010. With the application of skills, knowledge, and efficiencies gained from work on other Victoria-class submarines HMCS Chicoutimi is expected to rejoin the fleet in 2012.

HMAS Sydney Handed Back to Navy Following Major Upgrade article (Source: ADI, Ltd.; issued April 28, 2006) Australia’s largest defence company ADI Limited has today formally handed back to the Royal Australian Navy (RAN) the guided missile frigate HMAS Sydney following a major upgrade. Project directors from ADI Limited and the Defence Materiel Organisation joined HMAS Sydney’s Commanding Officer Commander Peter Quinn in a formal signing ceremony at the RAN’s Sydney fleet base to mark the occasion on Friday April 28. The hand back ceremony comes after a successful sea trials program over recent months, during which the ships new weapons systems, sensors, machinery and combat system were thoroughly tested. Today’s ceremony is not the end of the technology improvements for HMAS Sydney. As the lead ship in the upgrade program, Sydney will continue to serve as the prototype ship for further software improvements and enhanced war fighting capabilities. Vice President Thales Naval Australia and ADI’s Director of Naval, Ali Baghaei, described the occasion as an important milestone in the $1bn FFG Upgrade Project. “Equipping a 20-year old ship with the latest naval combat system technology was never going to be easy. “This project has been a significant challenge for ADI, with many issues often outside our control. We have demonstrated great commitment & persistence in meeting these challenges where many other contractors may well have given up. “By introducing new management to provide vision and focus, the project has been turned around such that HMAS Sydney is being handed over today, and HMAS Melbourne has commenced her upgrade and is on schedule. “This achievement today reflects the dedication and efforts of Industry, the DMO and Navy. I would especially like to acknowledge both the ADI and DMO Project Teams, and the Officers and Ships Company of HMAS Sydney for their outstanding contribution,” Mr Baghaei said. The FFG Upgrade project is the most sophisticated naval systems integration task ever undertaken in Australia by an Australian company involving both new technologies and legacy equipment. Central to the upgrade is the ADI-developed Australian Distributed Architecture Combat System (ADACS). ADI is the only Australian company to have designed, developed and installed an Australian naval combat system. The second ship to be upgraded, HMAS Melbourne, entered dry dock at ADI’s Garden Island facility in February. Her upgrade installation is expected to be completed by early 2007.

Regarding the above article and LCS program in general, is anyone aware of a link that would describe the amount of effort needed to exchange mission modules? The amount of time/man-hours; where it can be done, home port or in theater; if in theater, how much airlift is needed to get the module(s) and qualified "technicians/contactors" to the location? Thanks

article Navy to Base First Four Littoral Combat Ships in San Diego (Source: US Department of Defense; issued April 27, 2006) The Navy announced today that the first four Littoral Combat Ships (LCS) will be homeported at Naval Station San Diego, Calif. Key in the success of implementing these new concepts is the ability to collocate these ships to achieve readiness alignment and economy of scale. This collocation is especially important for the first ships in the class as waterfront facilities, infrastructure, training and maintenance efficiencies are developed. San Diego was chosen as the initial homeport because of the Navy’s increased emphasis on the Pacific theater based on the Quadrennial Defense Review. “Homeporting the first four ships in San Diego will enable us to establish synergy between the ships and with local commands,” said Vice Adm. Terry Etnyre, commander, Naval Surface Forces, based in Coronado, Calif. “With the Undersea Warfare Command here in San Diego and the Mine Warfare Command moving here soon, the undersea warfare and mine warfare mission packages will have direct coordination and representation locally.” LCS will carry some core capabilities, such as self-defense and command and control; but its true war-fighting capability will come from its innovative and tailored mission modules. These ships will be configured for one mission package at a time, consisting of modules, manned aircraft, unmanned vehicles, off-board sensors, and mission-manning detachments. This will operate within open-systems architecture giving it the capability to reconfigure mission modules and ship systems to tailor it for specific warfighting missions. The Littoral Combat Ships are the first Navy vessels to separate capability from hull form and provide a robust, affordable, mission-focused warship designed to provide assured access for our joint forces. LCS will have the size, speed, endurance, and connectivity to deploy as a member of carrier strike groups, expeditionary strike groups or surface strike groups. The innovative concepts in LCS do not end with its modularity. LCS will operate with a quarter of the crew normally assigned to ships this size through a combination of technology and process improvements for maintenance, logistics, training and administration. The keel for the first Littoral Combat Ship, to be named USS Freedom (LCS 1), was laid on June 3, 2005 and the second, to be named USS Independence (LCS 2), on Jan. 19, 2006.

Herman, I have recently been toying around with diesel subs in H4.1 and I must say that their employment in the littorals presents a facinating tactical dilemma for the ASW commander, albeit I only find it facinating since I am not the one looking for the sub.

Link fixed.

Here is a scan of the LCS Scenario map found in HNR03 with home-scored 10nm x 10nm grid squares to facilitate play. map

Another asset, also known as a force multiplier, is the fact that the RQ-8's are equipped with 3rd Generation ESM. This will allow for greater abilities to triangulate the location of a potential enemy craft.

Ran through it again last night/this afternoon and found out the following. The LCS, as equipped in this scenario, must avoid engagement and use its high speed to live to fight another day. It was equipped as follows: F(1)1 57mm/70 F(21)1 RIM 116-A RAM A(R.) Mk15 Phalanx 3 RQ-8 VTUAV AN/WLD-1 Remote Mine Hunting System AN/SLQ-48 Mine Neutralization Vehicle Also, hostile TRS 3D-16 can detect the vsmall RQ-8 beginning at 14nm. The RQ-8's 3rd Generation FLIR can only detect the small signature ship at 8nm and then have to classify it at 4nm. There is a +3 ratio or 60% chance that the RQ-8, at 125m (Low) will be shot down prior to or during its classification of the hostile FFL. The above 60% pH assumes that the DATA Modifier of +1 for the target being at or more than 1 level higher and the the attacker not using snap up/down missiles is appropriate here. If not, the pH of the hostile RAM will be somewhat lower. I can only assume that these platforms are not envisioned being used singly. That there would be air on station (may not have helped in this run through), or that the LCS will operate in multicraft units, with the individual crafts equipped differently. Say one Counter Mine package with two more ASuW-capable equipped craft. Thoughts?

In response to lst night's discussion on the Rolling Airframe Missile, please see the attached manufactuer's link and once there the data sheet in the upper right hand corner. RAM

Apparently made some true rookie tactical mistakes after forwarding my log to a Harpoon-astute friend. Will try this again with some different actions/reactions. And, hopefully some better luck on the die rolls as to not have the director crap out.

Wasn’t the genesis of this class of ship to be able to go into harms way and conduct missions that may be cost prohibitive if done by larger, more expensive platforms? Hey, I was a Infantry 2nd Lieutenant once so I believe that I can say this, the Littoral Combat Ship has an acceptable level of “expendability”. With this said, the LCS should not be thought of as operating in a vacuum. While no level of support can have guaranteed availability 24/7, the ships’ CO should have some level of comfort knowing that there is support available. The operations order that sends an LCS, or pack of them more likely, into a hostile littoral environment to conduct operations would contain tasks to other units subordinate to that ordering authority to provide “x” level of support. Would it be too much to ask the “squadron” to equip other LCS’ with the Mission Packages to provide the support or protection to the “unlucky” one ordered to “go clear mines”? I know on the green side, if we would send people forward to “clear mines”, a larger force is providing some type of overwatch. In the situation of a single LCS returning from a counter-mine mission being jumped by a hostile corvette/FFL, I would go out on a limb and say that there would have been two F/A-18’s on station waiting to be tasked, not waiting to react to an LCS being destroyed. There would obviously be other assets on strip alert as well. Even without a carrier on station, there is Marine air and land based assets to call on for support. The Littoral Combat Ship is not the be all end all, but a tool – like all tools – with strengths and weaknesses. It is up to the commander to employ his tools in such a way to accomplish the assigned missions with minimum loss of life and equipment. I do not believe that it would come to each LCS being escorted by destroyer to ensure its safety. Bottom line for me is that it would be folly to employ the Littoral Combat Ship alone, or unsupported by other assets.

Brad, The HNR2003 has quite an article on the LCS and various scenario to conduct with it or more conventional platforms, all along the lines of the missions which LCS is expected to accomplish. I realize that it must have become overcome by events since its publication, but fun none the less. Special rules for these scenarios are US ROE, Merchant Shipping, Satellite Recon. Unconventional forces, Explosive motorboats, coastal traffic, mines/minefields, and the various modular mission packages of LCS. Plenty of fodder for debate/constructive argument. Pete

1603 – Plotting: LCS: heading 270, speed 20kts, sensors active. RQ-8: heading 090 (turn 180 – intent is to screen LCS northern flank), speed 100kts, altitude 125m (Low). K-130: heading 225, speed 30kts, sensors active. 1603 – Movement: LCS: 1nm. RQ-8: 5nm. K-130: 1.5nm. Distances from LCS to K-130: 030, 23nm. From LCS to RQ-8: 007, 15nm. RQ-8 to K-130: 062, 11nm. 1603 - Planned Fire: None. 1603 - Detection: LCS Radar: No. RQ-8 FLIR: No. K-130 Radar: No. Both ship’s ESM contacts continue. 1603 - Reaction Fire: None. 1606 – Plotting: LCS: continue. RQ-8: RQ-8: heading 270 (turn 180 – intent is to continue to screen LCS northern flank). K-130: continue. 1606 – Movement: LCS: 1nm. RQ-8: 5nm. K-130: 1.5nm. Distances from LCS to K-130: 031, 23nm. From LCS to RQ-8: 352, 15nm. RQ-8 to K-130: 073, 14nm. 1606 – Detection: LCS Radar: No. RQ-8 FLIR: No. K-130 Radar: No. Both ship’s ESM contacts continue. 1606 – Reaction Fire Phase: None. 1609 – Plotting: LCS: continue. RQ-8: RQ-8: heading 090 (turn 180 – intent is to continue to screen LCS northern flank). K-130: heading and speed continue. Fire 2x RBS-15 Mk3 missiles Range and Bearing Launch (RBL) Mode on a 211 heading and with a 15nm Enabling Point. 1609 – Movement: LCS: 1nm. RQ-8: 5nm. K-130: 1.5nm. Distances from LCS to K-130: 033, 22nm. From LCS to RQ-8: 015, 15nm. RQ-8 to K-130: 069, 9nm. 1609 – Planned Fire: 2x (ROF in Annex A is “?”) 1609 – Detection: LCS Radar: No. RQ-8 FLIR: No. K-130 Radar: No. Both ship’s ESM contacts continue. 1609 – Reaction Fire: None. 1612.0 – Plotting: LCS: continue. RQ-8: RQ-8: heading 270 (turn 180 – intent is to continue to screen LCS northern flank). K-130: continue. 1612.0 – 1st Move: LCS: 0.2nm. RQ-8: 5nm. K-130: 0.25nm. V1 and V2: 2.5nm. Distances from LCS to K-130: 036, 22nm. From LCS to RQ-8: 000, 15nm. RQ-8 to K-130: 078, 13nm. 1612.0 – 1st Fire: None. 1612.0 – 1st Air Attack Resolution: None. 1612 - Detection: LCS Radar to K-130: No, ESM: Yes. LCS Radar to Vampires: No. RQ-8 FLIR to K-130: No. K-130 to LCS: Radar No, ESM Yes. 1612.5 – Second Move: V1 and V2: 2.5nm. Distance LCS to V1&2: 18nm 1612.5 – Second Fire: None. 1612.5 – Second Air Attack Resolution: None. 1613.0 – Plotting: LCS: continue. RQ-8: RQ-8: heading 090 (turn 180 – intent is to continue to screen LCS northern flank). K-130: continue. Vampires: continue. 1613.0 – 1st Move: LCS: 0.2nm. RQ-8: 0.8nm. K-130: 0.25nm. V1 and V2: 2.5nm. Distances from LCS to K-130: 036, 22nm. LCS to RQ-8: 020, 16nm. RQ-8 to K-130: 071, 8nm. 1613.0 – 1st Fire: None. 1613.0 - 1st Air Attack Resolution: None. 1613.0 - 1st Air Attack Resolution: None. 1613.0 - Detection: LCS Radar to K-130: No, ESM: Yes. LCS Radar to Vampires: Range 16nm, D100=18, Yes. RQ-8 FLIR to K-130: Yes (8nm). K-130 to LCS: Radar No, ESM Yes. 1613.5 - 2nd Move: V1 and V2: 2.5nm. Distance LCS to V1&2: 15.5nm 1613.5 - 2nd Fire: LCS launches 2x Enhanced Sea Sparrow Missiles on a bearing of 034. 1613.5 - 2nd Air Attack Resolution: None. 1614.0 - Plotting: LCS: heading 270, increase speed to 38kts (+18kts). RQ-8: RQ-8: heading 270 (turn 180 – intent is to continue to screen LCS northern flank). K-130: continue. Vampires: continue. 1614.0 - 1st Move: LCS: 0.2nm. RQ-8: 0.8nm. K-130: 0.25nm. V1 and V2: 2.5nm. ESSM’s: 11.0nm. Distances from LCS to K-130: 037, 22nm. LCS to RQ-8: 018, 16nm. RQ-8 to K-130: 072, 9nm. 1614.0 - 1st Fire: 2nd Fire: LCS launches 2x Enhanced Sea Sparrow Missiles on a bearing of 037. 1614.0 - 1st Air Attack Resolution: ESSM (SSC) ATA = 6.5 vs. RBS-15 (SS). Modifiers: 0.5 unmanned drone or cruise missile, +1 to target due to SS vs. SSC; +1 Low RCS (3rd Gen/VSmall) = 6.5-2.5 = 4.0 = pH70%. D100 #1 = 98 miss, D100 #2 = 00 **6.2.2 Weapons Mount Accidents. Mk91 deemed broken down. ESSM missiles in the air go stupid! 1614.0 - Detection: LCS Radar to K-130: No, ESM: Yes. LCS Radar to Vampires: Range 11nm RQ-8 FLIR to K-30: No K-130 to LCS: Radar No, ESM Yes. 1614.5 - 2nd Move: V1 and V2: 2.5nm. Distances from LCS 8.5nm 1614.5 - 2nd Fire: None. 1614.5 - 2nd Air Attack Resolution: None. 1615.0 - Plotting: LCS: heading 270, increase speed to 47kts (+18kts). RQ-8: RQ-8: heading 270 (continue to screen LCS northern flank). K-130: continue. Vampires: continue. 1615.0 - 1st Move: LCS: 0.2nm. RQ-8: 0.8nm. K-130: 0.25nm. V1 and V2: 2.5nm. Distances from LCS to K-130: 037, 22nm. LCS to RQ-8: 015, 16nm. RQ-8 to K-130: 074, 9nm. 1615.0 - 1st Fire: None. 1615.0 - 1st Air Attack Resolution: None. 1615.0 - Detection: LCS Radar to K-130: No, ESM: Yes. LCS Radar to Vampires: Range 8.5nm RQ-8 FLIR to K-30: No K-130 to LCS: Radar No, ESM Yes. 1615.5 - 2nd Move: V1 and V2: 2.5nm. Distances from LCS 6.0nm 1615.5 - 2nd Fire: None. 1615.5 - 2nd Air Attack Resolution: None. 1616.0 - Plotting: LCS: heading 270, increase speed to 50kts (+2kts). RQ-8: RQ-8: heading 270 (continue to screen LCS northern flank). K-130: continue. Vampires: continue. 1616.0 - 1st Move: LCS: 0.2nm. RQ-8: 0.8nm. K-130: 0.25nm. V1 and V2: 2.5nm. Distances from LCS to K-130: 037, 22nm. LCS to RQ-8: 015, 16nm. RQ-8 to K-130: 074, 9nm. 1616.0 - 1st Fire: None 1616.0 - 1st Air Attack Resolution: None. 1616.0 – Detection: LCS Radar to K-130: No, ESM: Yes. LCS Radar to Vampires: Range 3.5nm RQ-8 FLIR to K-30: No K-130 to LCS: Radar No, ESM Yes. 1616.5 – 2nd Move: V1 and V2: 2.5nm. Distances from LCS 1nm 1616.5 – 2nd Fire: Mk15: Far Range 1.4nm pH: 0.55. D100 = 53. Scratch one RBS-15 Mk3. Three seconds traveling at 2.5nm/phase is 0.5nm so there is no fragmentation damage. 1616.5 – 2nd Air Attack Resolution: None. 1617.0 – Plotting: “Assume the position.” 1617.0 – 1st Movement: 1x RBS-15 moves to point of impact. 1617.0 – 1st Fire: Mk15 Close Range 0.7, pH: 0.85. D100=99. Forward Bofors 57mm/70 masked. 1617.0 1st Air Attack Resolution: 1x 3rd Gen RBS-15 vs Stealthy Signature Target with 3rd Gen J&D = pH 0.29. D100 = 18. Missile Hits with 50DP. Using Method 3: The One-Roll Approach found in Dave Schueler’s Variable Damage article (pp. 38-39 HNR2003). 18/29 = .62 which falls in the 61-70 band = DP*70% = 35DP. LCS coasts to a flaming halt, dead in the water after suffering between 75-90% damage. Lost its stealth signature. Damage ratio is .83, round down to .80. D6 = 6 = 9 Critical Hits. 9 D10’s to determine CH’s. 8,9,3,4,10,5,3,8,2. Weapons Mounts (2) Weapons Mount (3,3) Sensor (4) Sensor (5) Engineering (8,8) Bridge/CIC (9) Rudder (10) * Lessons Learned: (a.) 5.3.4 Active Radar Homing (ARH) could have an effect on an engagement such as this. “…ARH seekers cannot distinguish between ships within 5nm of the coast and the land itself. They cannot attack land targets.” (b.) 5.3.13 Inertial Guidance (I/-) went over again. (c.) 5.3.14 Terminal Guidance (-/T----) RBS-15 is 3rd Generation vs. Small Seeker Acquisition Cone = 045 and 10nm. (d.) Distances for corvette to launch SSM and then both ships to engage in surface gunfire seems to be somewhat out of whack. (e.) Can 3rd Generation FLIR detect VSmall SSM at cruise profile? (f.) TRS-3D-16 vs. Vsmall = 18nm (g.) VLS rate of fire? 5.2 “Multiple-celled missile launchers fire four rounds per Engagement Turn.” Phase or Turn? (h.) Some errors are apparent in regards to the movement of the RQ-8 once Engagement Turns were declared. Not corrected due to the RQ-8 not playing a significant role thus far. (i.) After beginning this scenario with the combatants 25nm apart, and given the disadvantage that the LCS begins due to its Counter Mine mission package, provided the LCS defends itself against the two SSM’s, I do not believe that the CO of the LCS would turn toward the opposing FFL to engage with its 57mm/70 not knowing whether or not the FFL had additional missiles. It would chose to live to fight another day, accelerate to 50kts, and contact HHQ and request air support in the form of the 2x F-35 discussed in the original article. Comments please…