We (13xx) strive to value all educated opinions from any community, so don’t play the game of “you’re not URL, so STFU”. You’re the actual clown here.
@LFCFan was simply stating that there is an entire contingent of people whose job it is to mission plan for TLAM strikes (you do know that, right??), NOT that SWOs have nothing to do with planning for the use of TLAMs. Failed straw man, bro.
Look I won't use the same..."eloquent language" as azguy, but the issue as I see it is that people are drawing misguided conclusions from incomplete/anecdotal understandings of how other communities do things.
Let’s break this down, because you obviously have reading comprehension issues and you probably launched the worst straw man argument in history: He said that there is a contingent of people whose job it is to plan TLAM strikes. Not that SWOs on the ships don’t do any planning of their own for TLAM strikes. LATER in the comment, he said that VFA guys do all their own mission planning, while CRUDES do not. If we put this all together, we see that VFA guys don’t have an inorganic group that does some of the planning for them, while the SWOs do. Do we understand now? Not everything is a personal attack on you.
Honest question, is VFA not getting Intel support during the mission planning?
So here's the deal. The shore side has the role they have now in "real world" ops because our Navy is not operating in a comms and link degraded environment. As long as we enjoy that luxury, it makes sense for us to do things this way, because the shore side has better access to the full scope of C4I and ISR support offered by our Joint brethren.
Now drawing a conclusion from the current baseline that CRUDES
can't do their own mission planning would be as misguided as drawing the conclusion that TACAIR can't pull off a SAG Takedown just because you've never seen them do it.
Right now, Fleet owns it because...presumably they look at Strike Group and the CVW's capabilities and wonder 90% of the time why the fuck they would need a land attack cruise missile against the threats of today. Now if TLAM ever got released to Strike Group...?
As for the "weapons release" bit...that goes into the whole "picking up the phone" ridiculousness that's practically becoming a meme on this thread. The CO is called for a purpose, not for every little thing. Yes, in some cases it is to obtain permission. In others, it's because reporting requirements exist.
To draw an analogy, I assume a Squadron CO/CAG gets clued in and has some input on who is going over the beach to drop JDAMs all over things that need to die? Or wants to know if Force Weapons Posture changes? I mean I don't know the real reason you have a SDO on the boat, but presumably it's for more than to be the guy getting prank called by JOPA.
Look, fundamentally this is Naval Command and Control 101. To the extent you have time/access, the boss wants to be in the loop. When you don't, they trust the subordinates can work with Commander's Intent and other previous higher guidance.
When you are doing a TLAM strike, the boss has time to get in there and watch what's going on. So they will generally write their orders to require their permission to launch.
If you are doing ASCM defense (like we've done real world), they will not. So pretty much no CO ever will require you to call them.
Conflating how one mission area is executed with how another would be demonstrates a pretty poor understanding of the how/why things are the way they are. Which is why he's being called out on it.