Sec Form 4 Filing - DaSilva Kevin G @ RAYTHEON TECHNOLOGIES CORP - 2020-04-03

FORM 4 Check this box if no longer subject to Section 16. Form 4 or Form 5 obligations may continue. See Instruction 1(b).

UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 STATEMENT OF CHANGES IN BENEFICIAL OWNERSHIP Filed pursuant to Section 16(a) of the Securities Exchange Act of 1934, Section 17(a) of the Public Utility Holding Company Act of 1935 or Section 30(h) of the Investment Company Act of 1940

OMB APPROVAL OMB Number: 3235-0287 Expires: November 30, 2011 Estimated average burden hours per response... 0.5

1. Name and Address of Reporting Person DaSilva Kevin G 2. Issuer Name and Ticker or Trading Symbol RAYTHEON TECHNOLOGIES CORP [ RTX] 5. Relationship of Reporting Person(s) to Issuer (Check all applicable) _____ Director _____ 10% Owner X __ Officer (give title below) _____ Other (specify below) Corporate VP and Treasurer (Last) (First) (Middle) 870 WINTER STREET 3. Date of Earliest Transaction (MM/DD/YY) 04/03/2020 (Street) WALTHAM, MA02451 4. If Amendment, Date Original Filed (MM/DD/YY) 6. Individual or Joint/Group Filing (Check Applicable Line) __ X __ Form filed by One Reporting Person _____ Form filed by More than One Reporting Person (City) (State) (Zip)

Table I - Non-Derivative Securities Acquired, Disposed of, or Beneficially Owned 1.Title of Security (Instr. 3) 2. Transaction Date (MM/DD/YY) 2A. Deemed Execution Date, if any (MM/DD/YY) 3. Transaction Code (Instr. 8) 4. Securities Acquired (A) or Disposed of (D) (Instr. 3, 4 and 5) 5. Amount of Securities Beneficially Owned Following Reported Transaction(s) (Instr. 3 and 4) 6. Ownership Form: Direct (D) or Indirect (I) (Instr. 4) 7. Nature of Indirect Beneficial Ownership (Instr. 4) Code V Amount (A) or (D) Price Common Stock ( 1 ) 04/03/2020 A 38,381 ( 2 ) A 38,381 D Common Stock 04/03/2020 F 796 D $ 49.93 37,585 D

Table II - Derivative Securities Acquired, Disposed of, or Beneficially Owned ( e.g. , puts, calls, warrants, options, convertible securities) 1. Title of Derivative Security (Instr. 3) 2. Conversion or Exercise Price of Derivative Security 3. Transaction Date (MM/DD/YY) 3A. Deemed Execution Date, if any (MM/DD/YY) 4. Transaction Code (Instr. 8) 5. Number of Derivative Securities Acquired (A) or Disposed of (D) (Instr. 3, 4, and 5) 6. Date Exercisable and Expiration Date (MM/DD/YY) 7. Title and Amount of Underlying Securities (Instr. 3 and 4) 8. Price of Derivative Security (Instr. 5) 9. Number of Derivative Securities Beneficially Owned Following Reported Transaction(s) (Instr. 4) 10. Ownership Form of Derivative Security: Direct (D) or Indirect (I) (Instr. 4) 11. Nature of Indirect Beneficial Ownership (Instr. 4) Code V (A) (D) Date Exercisable Expiration Date Title Amount or Number of Shares Restricted Stock Units ( 3 ) 04/03/2020 A 6,673 ( 3 ) ( 3 ) Common Stock 6,673 ( 3 ) 6,673 D Restricted Stock Units ( 4 ) 04/03/2020 A 6,787 ( 4 ) ( 4 ) Common Stock 6,787 ( 4 ) 13,460 D Restricted Stock Units ( 5 ) 04/03/2020 A 4,469 ( 5 ) ( 5 ) Common Stock 4,469 ( 5 ) 17,929 D

Reporting Owners Reporting Owner Name / Address Relationships Director 10% Owner Officer Other DaSilva Kevin G 870 WINTER STREET WALTHAM, MA02451 Corporate VP and Treasurer Signatures /s/ Dana Ng, Attorney-in-fact 04/08/2020 Signature of Reporting Person Date

Explanation of Responses:

( 1 )Pursuant to the terms of the Agreement and Plan of Merger, dated as of June 9, 2019, as amended by Amendment No. 1 to the Agreement and Plan of Merger, dated as of March 9, 2020, by and between United Technologies Corporation ("UTC") and Raytheon Company ("Raytheon") (the "Merger Agreement"), on April 3, 2020 (the "Closing Date"), Raytheon became a wholly owned subsidiary of UTC, with UTC becoming Raytheon Technologies Corporation. Pursuant to the Merger Agreement, on the Closing Date, each share of Raytheon Common Stock held by the reporting person was converted automatically into 2.3348 shares of UTC Common Stock. ( 2 )Includes (1) 2,552 restricted shares of RTX Common Stock that were converted from restricted shares of Raytheon Common Stock granted on March 21, 2018, (2) 3,761 restricted shares of RTX Common Stock that were converted from restricted shares of Raytheon Common Stock granted on March 20, 2019, and (3) 4,677 restricted shares of RTX Common Stock that were converted from restricted shares of Raytheon Common Stock granted on March 25, 2020, pursuant to the terms of the Merger Agreement. All such shares continue to vest in one-third increments on each of the second, third and fourth anniversaries of their original date of grant, as applicable. ( 3 )Represents RTX restricted stock units ("RSUs") that, pursuant to the terms of the Merger Agreement, were converted from Raytheon performance-based vesting restricted stock units granted on January 24, 2018 under the 2018-2020 Long-Term Performance Plan ("LTPP"). These RSUs will vest in full at the end of the original LTPP 3-year performance cycle. ( 4 )Represents RTX RSUs that, pursuant to the terms of the Merger Agreement, were converted from Raytheon performance-based vesting restricted stock units granted on January 30, 2019 under the 2019-2021 LTPP. These RSUs will vest in full at the end of the original LTPP 3-year performance cycle. ( 5 )Represents RTX RSUs that, pursuant to the terms of the Merger Agreement, were converted from Raytheon performance-based vesting restricted stock units granted on January 29, 2020 under the 2020-2022 LTPP. These RSUs will vest in full at the end of the original LTPP 3-year performance cycle.

Reminder: Report on a separate line for each class of securities beneficially owned directly or indirectly.

* If the form is filed by more than one reporting person, see Instruction 4(b)(v).

** Intentional misstatements or omissions of facts constitute Federal Criminal Violations. See 18 U.S.C. 1001 and 15 U.S.C. 78ff(a).

Note: File three copies of this Form, one of which must be manually signed. If space is insufficient, see Instruction 6 for procedure.
Persons who respond to the collection of information contained in this form are not required to respond unless the form displays a currently valid OMB Number.