• Thanks for stopping by. Logging in to a registered account will remove all generic ads. Please reach out with any questions or concerns.

The Navy's Kessel Run - USNI Blog

dimsum

Army.ca Relic
Mentor
Reaction score
20,542
Points
1,280
While the idea of a program that can instantly compute different CoAs and such is useful for bringing junior TACCOs up to speed and broaden their horizons instead of what's currently in the pubs.  However, as someone pointed out on social media, this may backfire and a new generation of TACCOs may end up relying on it to do their prosecution. 

Tactics evolve.

Imagine you are a tactical coordinator (TACCO) on a P-8 Poseidon, the Navy’s newest antisubmarine warfare (ASW) aircraft. Your job is to maximize the tactical impact of your sensors and weapons while leading your crew. The United States is at war and you are tasked with finding and killing an adversary submarine. Intelligence indicates there is a high probability you will find your target, so you take what little time you have before the flight to make sure you’ve thought through every contingency. You know what behaviors and detection ranges other crews have observed against similar submarines, so you sketch out a few basic plans you can carry out rapidly if you have a detection opportunity. You use a few rules-of-thumb and some mental math to come up with the numbers behind your tactics. The plans are by no means optimized, but at least you have something with a chance of working.

You get to the plane, takeoff, and head toward your search area. Once you get on-station, you sample the environment and realize your plan was all wrong. The detection ranges will be far less than anticipated, and all of the tactics you planned will be laughably inadequate. You do not have the time to laboriously create new ones, though. So, you adjust your old plans to make them a little bit more conservative. It’s an art form practiced by decades of TACCOs before you. It was fine when the art hadn’t always worked in peacetime, but the stakes are much higher now.

You soon get a sniff of your target and enact your planned response to refine its exact position, course, and speed. While trying to do that, the target slips away. The rule-of-thumb plan you massaged for the dynamic environment was not up to the task. Years of training, flying, and deploying were for naught. And the adversary submarine is free to wreak havoc on U.S. forces. It did not have to be this way, though.

https://blog.usni.org/posts/2019/01/03/the-navys-kessel-run?fbclid=IwAR3rOAWo21NBSKxKOdXGY0wGkfFvbDppWryBOfB4KRu3B6ZJmyjCr4BMaVc
 
Dimsum,

Thank-you for the article! It crystallizes some thinking that I have been doing as we transition from Sea King to Cyclone. The current (legacy) method of ASW for an MH TACCO is very much "intuition based"- you learn the tactics and then you apply them when the conditions "feel" right.



 
SeaKingTacco said:
Dimsum,

Thank-you for the article! It crystallizes some thinking that I have been doing as we transition from Sea King to Cyclone. The current (legacy) method of ASW for an MH TACCO is very much "intuition based"- you learn the tactics and then you apply them when the conditions "feel" right.

From the little that I know about the Cyclone systems, that intuition won't go away.  We do the same.
 
Thanks for sharing the article.  The Naval Software Team (NST) that implemented that tool are a blessing for the P-8A fleet.


Having a team of uniformed or civilian talent in the organization is often overlooked and underappreciated.  I wonder if the elements that existed in 14SES have any mandate (or manpower) remaining in 415 Sqn to perform similar agile software development to develop and support similar tools for CP140M.
 
Back
Top