Re: Sinking of Mutsu, June 1943


"a425couple" <a425couple@xxxxxxxxxxx> wrote in message
news:EamdnXGo9O7hYhjVnZ2dnUVZ_rjinZ2d@xxxxxxxxxxxxxx
"Keith Willshaw" <keithnospam@xxxxxxxxxxx> wrote ..
"Dean A. Markley" <deanmarkley@xxxxxxxxxxx> wrote
In June, 1943, the Imperial Japanese Navy battleship Mutsu suffered a
magazine explosion and sank. Did the U.S. have intelligence at the time
regarding the demise of the Mutsu? When did they realize that Japan was
short another battleship?

Given that they were reading the Japanese naval codes by that
stage I'd guess they did. Keith

I can not find any good source re: Dean's question.
(I'll enjoy reading a definitive answer.)

However, very respectfully, I'd tend to disagree with Keith.
Reading a considerable amount of the messages broadcast
in the codes, is very helpful, but still often leaves one in
the dark.

I'll mention the case of the Tirpitz. The German BB was
much more of a serious threat to Allied plans for WWII,
and the German codes were also often being read.
Because of it's serious threat, many very 'expensive'
operations were mounted to damage/destroy it.
Yet the Allies (Churchill, Stalin, RN, FAA, RAF etc.),
remained in the 'dark' about it's true status. The Allies
continued the efforts until it was finally capsized/sunk.
Much later it was found that it had lost it's operational
ability much earlier.


The value/threat of the Mutsu in the PTO from
early 1943 on, was quite limited.
(i.e. when they do not have enough fuel, does
their status much matter? Related - were not
Ise and Hyuga pretty much 'ignored' until the
final days?)



I recall reading in the book 'The Emperors Codes' that
the section at Bletchley Park had a comprehensive
card index on the status of all Japanese warships and
merchant ships based on the JN25 and JN 11 decrypts

Also related, reading the enemy 'code' is also
somewhat limited if the enemy is not able to be
honest with themselves!


Even the Japanese would be hard pressed to suppress news of'
a ship blowing up in Hiroshima bay !

Keith


.

Relevant Pages

  • edict lookup methods, and a list of problematic RPG-item names
    ... containing the search string anywhere", but had no limit on the number ... which I know the reading but not the kanji is to enter that reading into ... I have a list of item names from a Japanese console ... guide consulted because I've not progressed far enough in my translation ...
    (sci.lang.japan)
  • Re: OT who said this ?
    ... Dewey not to reveal the evidence about Pearl Harbor? ... The excuse was that we didn't want the Japanese to know we had broken ... has charge or the most secret documents of the War and Navy ... codes, German as well as Japanese, but our main basis of informa- tion regarding Hitler's intentions in Europe is obtained from Baron Oshima's messages from Berlin reporting his interviews with Hitler ...
    (rec.outdoors.rv-travel)
  • Re: Where the nest Asian financial crisis will emerge...
    ... from reading my postings. ... If u had not why then u still keep on reading it ... Yes I admit I made the wrong call on Arroya. ... The Japanese are not speculating! ...
    (soc.culture.singapore)
  • Re: nss_ldap and openldap on the same server.
    ... Look for Status codes and Actions ... Reading getgrouplistturns out the following: ... The getgrent() and getgrent_rfunctions make no attempt to suppress ... behavior is fully correct as a lookup is done to find out all groups to ...
    (freebsd-questions)
  • Re: nss_ldap and openldap on the same server.
    ... Look for Status codes and Actions ... Reading getgrouplistturns out the following: ... The getgrent() and getgrent_rfunctions make no attempt to suppress duplicate information if multiple sources are specified in nsswitch.conf. ... So after following the way through all man pages, it turns out that the behavior is fully correct as a lookup is done to find out all groups to which the specified slapd user belongs to. ...
    (freebsd-questions)