Pearl Harbor: The Seeds and Fruits of Infamy - Ludwig von Mises ...

Pearl Harbor: The Seeds and Fruits of Infamy - Ludwig von Mises ... Pearl Harbor: The Seeds and Fruits of Infamy - Ludwig von Mises ...

01.01.2013 Views

Joint Congressional Committee, Pearl Harbor Attack: Part 3 747 it.” 54 Saff ord learned much later that the McCollum message had not been sent. 55 Safford Responds to “Winds Execute” as Chief, Naval Communications Security Being in charge of the security section of Naval Communications, Saff ord’s jurisdiction and responsibilities were limited to maintaining the security of communications; he was not permitted to send evaluations or orders to men in the fi eld. 56 Any messages he sent had to deal specifi cally with maintaining document security. In fulfi llment of this obligation and as a result of the receipt of the “Winds Execute,” he fi led four messages for transmittal between 3:00 and 3:20 p.m. on the afternoon of December 4. He instructed the naval attachés at Tokyo, Peiping, Bangkok, and Shanghai “to destroy all secret and confi dential fi les except those essential for current purposes.” 57 Similar instructions were sent to the commander-in-chief Asiatic Fleet in Manila. 58 Saff ord also sent a PRIORITY message to Guam and Samoa at 8 p.m. ordering a change in codes from their then-current code RIP 65 to a new code, RIP 66. 59 Th is order was promptly received in Guam. Seventeen minutes later, a SECRET message was released by Ingersoll to Guam, DEFERRED precedence to allow time for the new code, RIP 66, to be implemented, asking Guam to 54Ibid., p. 3812. 55Ibid., pp. 3701, 3715, 3812, 3878. See also pp. 3761–62, Saff ord’s January 22, 1944, letter to Kramer. 56Ibid., p. 3781. 57Ibid., pp. 3810, 3844; part 29, p. 2397, OpNav. No. 042019, with an information copy to the commander-in-chief Asiatic Fleet (Hart) but not to the C-in-C of the Pacifi c Fleet (Kimmel). 58 Ibid., part 29, p. 2397, #042018. No information copy was sent to Kimmel. 59 Ibid., p. 2397, #042000.

748 Pearl Harbor: The Seeds and Fruits of Infamy destroy all secret and confi dential publications. . . . retaining minimum cryptographic channels necessary for essential communications. . . . Be prepared to destroy instantly in event of emergency all classifi ed matter you retain. 60 Th en in the attempt to warn Wake, Saff ord prepared a strong message that read in part: “In view of imminence of war destroy all registered publications on Wake Island except this system and current editions of aircraft code and direction fi nder code.” 61 Ingersoll refused to send this strongly worded message as drafted by Saff ord. He released instead an “ambiguous” message with Wake’s name deleted from the text. 62 Moreover, it was held up until December 6, when it “was sent deferred precedence which meant delivery [in Pearl Harbor for relay to Wake] by 9:00 on Monday morning, December 8, 1941.” Saff ord didn’t know when it got to Pearl Harbor but, he said, no action was taken on it until long after the attack on Pearl Harbor; and then, because we had sent an ambiguous message, the fl eet communication offi cer sent another ambiguous message. Th e net result was that when Wake was captured, I believe the 24th of December, some of the cryptographic aids fell into Japanese hands, and it was reported at the time by Commandant 14th Naval District, and later on some of the alphabet strips were captured at Kiska in some of the abandoned Japanese dugouts. 63 Given the limitations of their responsibilities and the Navy’s restrictions on their duties, Saff ord and McCollum did all they 60 Ibid., part 8, p. 3845; part 14, p. 1408, #042017; part 29, p. 2398, #042017. Saff ord testimony at APHB; part 33, pp. 1178–79. #042017, NCI Exhibit 21. Information copy to commander-in-chief, Pacifi c Fleet. 61 Ibid., part 29, p. 2399. 62 Ibid., part 14, p. 1408; part 29, p. 2399. 63 Ibid., part 29, p. 2399.

Joint Congressional Committee, <strong>Pearl</strong> <strong>Harbor</strong> Attack: Part 3 747<br />

it.” 54 Saff ord learned much later that the McCollum message had<br />

not been sent. 55<br />

Safford Responds to “Winds Execute”<br />

as Chief, Naval Communications Security<br />

Being in charge <strong>of</strong> the security section <strong>of</strong> Naval<br />

Communications, Saff ord’s jurisdiction <strong>and</strong> responsibilities were<br />

limited to maintaining the security <strong>of</strong> communications; he was<br />

not permitted to send evaluations or orders to men in the fi eld. 56<br />

Any messages he sent had to deal specifi cally with maintaining<br />

document security. In fulfi llment <strong>of</strong> this obligation <strong>and</strong> as a result<br />

<strong>of</strong> the receipt <strong>of</strong> the “Winds Execute,” he fi led four messages<br />

for transmittal between 3:00 <strong>and</strong> 3:20 p.m. on the afternoon <strong>of</strong><br />

December 4. He instructed the naval attachés at Tokyo, Peiping,<br />

Bangkok, <strong>and</strong> Shanghai “to destroy all secret <strong>and</strong> confi dential fi les<br />

except those essential for current purposes.” 57 Similar instructions<br />

were sent to the comm<strong>and</strong>er-in-chief Asiatic Fleet in Manila. 58<br />

Saff ord also sent a PRIORITY message to Guam <strong>and</strong> Samoa<br />

at 8 p.m. ordering a change in codes from their then-current<br />

code RIP 65 to a new code, RIP 66. 59 Th is order was promptly<br />

received in Guam. Seventeen minutes later, a SECRET message<br />

was released by Ingersoll to Guam, DEFERRED precedence to<br />

allow time for the new code, RIP 66, to be implemented, asking<br />

Guam to<br />

54Ibid., p. 3812.<br />

55Ibid., pp. 3701, 3715, 3812, 3878. See also pp. 3761–62, Saff ord’s January 22,<br />

1944, letter to Kramer.<br />

56Ibid., p. 3781.<br />

57Ibid., pp. 3810, 3844; part 29, p. 2397, OpNav. No. 042019, with an information<br />

copy to the comm<strong>and</strong>er-in-chief Asiatic Fleet (Hart) but not to the<br />

C-in-C <strong>of</strong> the Pacifi c Fleet (Kimmel).<br />

58 Ibid., part 29, p. 2397, #042018. No information copy was sent to Kimmel.<br />

59 Ibid., p. 2397, #042000.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!