<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="215637" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://declassified.library.utoronto.ca/items/show/215637?output=omeka-xml" accessDate="2026-08-15T08:00:46-04:00">
  <fileContainer>
    <file fileId="193566">
      <src>https://declassified.library.utoronto.ca/files/original/4c3f5c640c7e6c43de90dd951521b606.pdf</src>
      <authentication>bb5bc6be05760db00dc2c50343422a86</authentication>
      <elementSetContainer>
        <elementSet elementSetId="31">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="131">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="2056881">
                  <text>Document disclosed under the Access to Information Act ■
Document divulge en vertu de la Loi surl’acces a /’information

Copy No. 1,

Ext. 181A

of 3 copies
OTTAWA FILE
No

WISER

Letter No

10

SECURITY CLASSIFICATION

WISER TOP SECRET

Date. April. 22, • -1952
FROM:

THE UNDER-SECRETARY OF STATE FOR EXTERNAL AFFAIRS, CANADA

TO:

THE CANADIAN AMBASSADOR, WASHINGTON, D.C.

Reference..

Subject:

Your Wiser telegrams NQ...40 . of April .15, and No.. . 39. of

April 5, and our Wiser letter No. 8 of April 3.

Procedures for S.A.C* Plight Clearances...... ..... .

Attached for your information are three copies of the
Order-in-Council as passed on April 17. We did not
learn in advance that it was being submitted, and the
text is so innocuous that the Privy Council Office did
not realize that this Department was concerned. Thus
we have only now received copies.

Copies Referred
To.........................

No. of Enclosures

Six

Post File

No

You will notice that paragraph 2 of the
2.
Regulations contained in the Order-in-Council refers
to ’’orders and directions issued by the Minister of
National Defence”. This phrase is intended to cover
the two schedules A and B appended to our letter No. 8
of April 3. We are not certain whether the copy of
Schedule B which we sent to you was the most recent text
carrying under the heading the following annotation:
"NOTE: All S.A.C. flights carrying .special weapons
are to comply with the restrictions on
routing, heights, and numbers laid down in
Appendix B, Part I, Section 1.”
In order to avoid any confusion, I am enclosing three
copies of the most recent text, which is that to be
applied by National Defence. You will notice in the
attached copies that the note mentioned has been amended
so that the reference to ’’Appendix B, Part I, Section 1”
now reads ’’Schedule A, Part I, Section 1".
You may now transmit the Order-in-Council and
Schedule B to the State Department on a formal basis.
Either of the methods suggested in paragraph 3 of your
telegram No. 39 of April 5 would appear satisfactory.
On the whole there might be some advantage in having a
record on paper; unless you see any objection, therefore,
it would probably be better to transmit these documents
under a covering letter. .
3.

4.
The Chief of Air Staff is being given instructions to ensure that the procedures outlined in Schedule
B are followed. We understand that these instructions
will probably take effect on Eriday, April 25. A few
of the most senior RCAE officers concerned will be instructs
in accordance with the provisions of the subsidiary unnumbered schedule outlining .domestic procedures, and it
will be made clear to them that information concerning
these domestic procedures should be rigorously restricted
to Canadian personnel. We agree entirely with the arguments in paragraph 4 of your telegram No. 39 to the effect
that these domestic procedures should not be explained
to U.S. authorities.

467-il —
Acting Under-Secretary of State
m

Aye'

A 0 P. * M

00021

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="2056884">
              <text>CDNW16923</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="2056887">
              <text>Wiser Letter No. 10 from USSEA to WashDC</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="2056890">
              <text>22-Apr-52</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="2056893">
              <text>Wiser Consultations, RG25-B-2, Volume number: 3095</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
