PAPERWORK REDUCTION ACT SUBMISSION Please read the instructions before completing this form. For additional forms or assistance in completing this form, contact your agency's Paperwork Clearance Officer. Send two copies of this form, the collection instrument to be reviewed, the Supporting Statement and any additional documentation to: Office of Information and Regulatory Affairs, Office of Management and Budget, Docket Library, Room 10102, 725 17th Street NW Washington, DC 20503.

1. Agency/ Subagency originating request USEPA/ Office of Enforcement and Compliance Assurance 2. OMB control number b. G None a. 2060 0476 __ __ __ __

3. Type of information collection ( check one) a. G New collection b. G Revision of a currently approved collection c. X Extension of a currently approved collection d. G Reinstatement, without change, of a previously approved collection for which approval has expired e. G Reinstatement, with change, of a previously approved collection for which approval has expired f. G Existing collection in use without an OMB control number 4. Type of review requested ( check one) a. X Regular b. G Emergency  Approval requested by: / / c. G Delegated 5. Small entities Will this information collection have a significant economic impact on a substantial number of small entities? G Yes X No For b f, note item A2 of Supporting Statement Instructions 6. Requested expiration date a. X Three years from approval date b. G Other Specify: / /___

7. Title NESHAP for Primary Copper Smelters ( 40 CFR part 63, subpart QQQ) ( Renewal)

8. Agency form number( s) ( If applicable) 1850.04 9. Keywords Primary copper smelters, copper concentrate dryer, smelting furnace, slag cleaning vessel, copper converter department.

10. Abstract Owners and operators of each new and existing affected source at their primary copper smelters. They are required to comply with the recordkeeping and reporting requirements of the NESHAP General Provisions ( 40 CFR Part 63, Subpart A) and maintain records of specific information needed by EPA to determine if compliance has been achieved.

11. Affected public ( Mark primary with " P" and all others that apply with " X") a. Individuals or households d. Farms b. P Business or other for profit e. Federal Government c. Not for profit institutions f. State, Local or Tribal Government 12. Obligation to respond ( Mark primary with " P" and all others that apply with " X") a. G Voluntary b. G Required to obtain or retain benefits c. P Mandatory 13. Annual reporting and recordkeeping hour burden a. Number of respondents 3 b. Total annual responses 45 1. Percentage of these responses collected electronically 10 ________ % c. Total hours requested 8,837 d. Current OMB inventory 20,506 e. Difference ( 11,669) f. Explanation of difference 1. Program Change 0 2. Adjustment ( 11,669) 14. Annual reporting and recordkeeping cost burden ( in thousands of dollars) a. Total annualized capital/ startup costs 0 b. Total annual costs ( O& M) 8 c. Total annualized cost requested 8 d. Current OMB inventory 98 e. Difference ( 90 ) f. Explanation of difference 1. Program change 0 2. Adjustment ( 90)

15. Purpose of information collection ( Mark Primary With " P" and all others that apply with " X") a. Application for benefits e. Program planning or management b. Program evaluation f. Research c. General purpose statistics g. P Regulatory or compliance d. __ Audit 16. Frequency of recordkeeping or reporting ( check all that apply) a. X Recordkeeping b. Q Third party disclosure c. X Reporting 1. X On occasion 2. Q Weekly 3. X Monthly 4. Q Quarterly 5. X Semi annually 6. X Annually 7. Q Biannually 8. X Other ( describe) Initially 17. Statistical methods Does this information collection employ statistical methods?

Q Yes X No 18. Agency contact ( person who can best answer questions regarding the content of this submission) Name: Learia A. Willaims Phone: ( 202) 564 4113 OMB 83 I 10/ 95 19. Certification for Paperwork Reduction Act Submissions On behalf of this Federal agency, I certify that the collection of information encompassed by this request complies with' 5 CFR 1320.9.

NOTE: The text of 5 CFR 1320.9, and the related provisions of 5 CFR 1320.8( b)( 3), appear at the end of the instructions. The certification is to be made with reference to those regulatory provisions as set forth in the instructions.

The following is a summary of the topics, regarding the proposed collection of information, that the certification covers:

( a) It is necessary for the proper performance of agency functions;

( b) It avoids unnecessary duplication;

( c) It reduces burden on small entities;

( d) It uses plain, coherent, and unambiguous terminology that is understandable to respondents;

( e) Its implementation will be consistent and compatible with current reporting and recordkeeping practices;

( f) It indicates the retention periods for recordkeeping requirements;

( g) It informs respondents of the information called for under 5 CFR 1320.8( b)( 3):

( i) Why the information is being collected; ( ii) Use of information; ( iii) Burden estimate; ( iv) Nature of response ( voluntary, required for a benefit, or mandatory); ( v) Nature and extent of confidentiality; and ( vi) Need to display currently valid OMB control number;

( h) It was developed by an office that has planned and allocated resources for the efficient and effective management and use of the information to be collected ( see note in Item 19 of the instructions);

( i) It uses effective and efficient statistical survey methodology; and ( j) It makes appropriate use of information technology.

If you are unable to certify compliance with any of these provisions, identify the item below and explain the reason in Item 18 of the Supporting Statement.

Signature of Program Official Michael S. Alushin, Director Compliance Assessment and Media Programs Division Office of Compliance Office of Enforcement and Compliance Assurance Date Signature of Senior Official or designee Oscar Morales, Director Collection Strategies Division Office of Environmental Information Date OMB 83 I 10/ 95 Certification Requirement for Paperwork Reduction Act Submissions 5 CFR 1320.9 reads " As part of the agency submission to OMB of a proposed collection of information, the agency ( through the head of the agency, the Senior Official or their designee) shall certify ( and provide a record supporting such certification) that the proposed collection of information

"( a) is necessary for the proper performance of the functions of the agency, including that the information to be collected will have practical utility;

"( b) is not unnecessarily duplicative of information otherwise reasonably accessible to the agency;

"( c) reduces to the extent practicable and appropriate the burden on persons who shall provide information to or for the agency, including with respect to small entities, as defined in the Regulatory Flexibility Act 5 U. S. C. § 601( 6)), the use of such techniques as:

"( 1) establishing differing compliance or reporting requirements or timetables that take into account the resources available to those who are to respond; "( 2) the clarification, consolidation, or simplification of compliance and reporting requirements; or collection of information , or any part thereof; "( 3) an exemption from coverage of the collection of information, or any part thereof;

"( d) is written using plain, coherent, and unambiguous terminology and is understandable to those who are to respond;

"( e) is to be implemented in ways consistent and compatible, to the maximum extent practicable, with the existing reporting and recordkeeping practices of those who are to respond;

"( f) indicates for each recordkeeping requirement the length of time persons are required to maintain the records specified;

"( g) informs potential respondents of the information called for under § 1320.8( b)( 3); [ see below]

"( h) has been developed by an office that has planned and allocated resources for the efficient and effective management and use of the information to be collected, including the processing of the information in a manner which shall enhance, where appropriate, the utility of the information to agencies and the public;

"( i) uses effective and efficient statistical survey methodology appropriate to the purpose for which the information is to be collected; and "( j) to the maximum extent practicable, uses appropriate information technology to reduce burden and improve data quality, agency efficiency and responsiveness to the public."

NOTE: 5 CFR 1320.8( b)( 3) requires that each collection of information:

"( 3) informs and provides reasonable notice to the potential persons to whom the collection of information is addressed of:

"( i) the reasons the information is planned to be and/ or has been used to further the proper performance of the functions of the agency; "( ii) the way such information is planned to be and/ or has been used to further the proper performance of the functions of the agency; "( iii) an estimate, to the extent practicable, of the average burden of the collection ( together with a request that the public direct to the agency any comments concerning the accuracy of this burden estimate and any suggestions for reducing this burden); "( iv) whether responses to the collection of information are voluntary, required to obtain or retain a benefit ( citing authority), or mandatory ( citing authority); "( v) the nature and extent of confidentiality to be provided, if any ( citing authority); and "( vi) the fact that any agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number." OMB 83 I ( Instructions) 10/ 95


Comment Info: =================

General Comment:Please extend the comment period for the E-cig issue. I started smoking when I was 16 years old. That was 53 years ago. I tried to quite smoking many times but nothing worked. I thought I would die like all my aunts and uncles, Lungcancer
3 years ago I tried e-cigs. I could not make the switch to e-cigs the first year because I would only try the cigarette flavor juice.
2 years ago I tried the candy flavors and that was all it took. Once I tried the candy flavors I could not stand the taste of cigarettes any longer and I have been cigarette free since. The fluids that I buy now do not have nicotene in them.


[Federal Register Volume 85, Number 52 (Tuesday, March 17, 2020)]
[Notices]
[Pages 15187-15188]
[FR Doc No: 2020-05354]

-----------------------------------------------------------------------

DEPARTMENT OF HEALTH AND HUMAN SERVICES

Food and Drug Administration

[Docket Nos. FDA-2019-N-3077; FDA-2013-N-0403; FDA-2013-N-0579; FDA-
2016-N-2474; FDA-2013-N-0717; FDA-2018-N-3728; FDA-2013-N-0797; FDA-
2013-N-0578; FDA-2013-N-0879; FDA-2012-N-0197; FDA-2016-N-3586; FDA-
2016-N-4319; and FDA-2013-N-0764]

Agency Information Collection Activities; Announcement of Office
of Management and Budget Approvals

AGENCY: Food and Drug Administration, HHS.

ACTION: Notice.

-----------------------------------------------------------------------

SUMMARY: The Food and Drug Administration (FDA) is publishing a list of
information collections that have been approved by the Office of
Management and Budget (OMB) under the Paperwork Reduction Act of 1995.

FOR FURTHER INFORMATION CONTACT: Ila S. Mizrachi, Office of Operations,
Food and Drug Administration, Three White Flint North, 10A-12M, 11601
Landsdown St., North Bethesda, MD 20852,<PHONE_NUMBER>,
<EMAIL_ADDRESS>
SUPPLEMENTARY INFORMATION: The following is a list of FDA information
collections recently approved by OMB under section 3507 of the
Paperwork Reduction Act of 1995 (44 U.S.C. 3507). The OMB control
number and expiration date of OMB approval for each information
collection are shown in table 1. Copies of the supporting statements
for the information collections are available on the internet at http://www.reginfo.gov/public/do/PRAMain. An Agency may not conduct or
sponsor, and a person is not required to respond to, a collection of
information unless it displays a currently valid OMB control number.

        Table 1--List of Information Collections Approved By OMB
------------------------------------------------------------------------
                                            OMB Control    Date approval
           Title of collection                  No.           expires
------------------------------------------------------------------------
Obtaining Information to Understand            0910-0883       1/31/2021
 Challenges and Opportunities
 Encountered by Compounding Outsourcing
 Facilities.............................
Protection of Human Subjects; Informed         0910-0130       1/31/2023
 Consent; and Institutional Boards......
Biological Products: Reporting and             0910-0458       1/31/2023
 Biological Product Deviations and Human
 Cells, Tissues, and Cellular and Tissue-
 Based Deviations in Manufacturing......
Reporting Associated with Designated New       0910-0605       1/31/2023
 Animal Drugs for Minor Use and Minor
 Species................................
Evaluation of the Food and Drug                0910-0753       1/31/2023
 Administration's General Market Youth
 Tobacco Prevention Campaign............
Collection of Conflict of Interest             0910-0882       1/31/2023
 Information for Participation in Food
 and Drug Administration Non-Employee
 Fellowship and Traineeship Programs....
Human Tissue Intended for                      0910-0302       2/28/2023
 Transplantation........................
General Licensing Provisions: Biologics        0910-0338       2/28/2023
 License Application, Changes to an
 Approved Application, Labeling,
 Revocation and Suspension,
 Postmarketing Studies Status Reports,
 and Form FDA 356h......................
Procedures for the Safe Processing and         0910-0354       2/28/2023
 Importing of Fish and Fishery Products.
Medical Devices; Shortages Data                0910-0491       2/28/2023
 Collection System......................
Focus Groups About Drug Products as Used       0910-0677       2/28/2023
 by the Food and Drug Administration....

Unique Device Identification System.....       0910-0720       2/28/2023
Animal Feed Regulatory Program Standards       0910-0760       2/28/2023
------------------------------------------------------------------------

    Dated: March 11, 2020.
Lowell J. Schiller,
Principal Associate Commissioner for Policy.
[FR Doc. 2020-05354 Filed 3-16-20; 8:45 am]
 BILLING CODE 4164-01-P


[Federal Register Volume 87, Number 171 (Tuesday, September 6, 2022)]
[Notices]
[Pages 54579-54583]
[FR Doc No: 2022-19112]

-----------------------------------------------------------------------

SECURITIES AND EXCHANGE COMMISSION

[Release No. 34-95635; File No. SR-FINRA-2022-013]

Self-Regulatory Organizations; Financial Industry Regulatory
Authority, Inc.; Order Approving a Proposed Rule Change To Amend FINRA
Rule 6730 (Transaction Reporting) To Enhance TRACE Reporting
Obligations for U.S. Treasury Securities

August 30, 2022.

I. Introduction

    On May 23, 2022, the Financial Industry Regulatory Authority, Inc.
(``FINRA'') filed with the Securities and Exchange Commission
(``Commission''), pursuant to Section 19(b)(1) of the Securities
Exchange Act of 1934 (``Act'') \1\ and Rule 19b-4 thereunder,\2\ a
proposed rule change to amend FINRA Rule 6730 (Transaction Reporting)
to Enhance TRACE Reporting Obligations for U.S. Treasury Securities.
The proposed rule change was published for comment in the Federal
Register on June 3, 2022.\3\ On July 13, 2022, pursuant to Section
19(b)(2) of the Act,\4\ the Commission designated a longer period
within which to approve the proposed rule change, disapprove the
proposed rule change, or institute proceedings to determine whether to
disapprove the proposed rule change.\5\ The Commission received five
comments on the proposal.\6\ FINRA submitted a response to the comments
on August 18, 2022.\7\ This order approves the proposed rule change.
---------------------------------------------------------------------------

    \1\ 15 U.S.C. 78s(b)(1).
    \2\ 17 CFR 240.19b-4.
    \3\ See Securities Exchange Act Release No. 95003 (May 27,
2022), 87 FR 33844 (June 3, 2022) (``Notice'').
    \4\ 15 U.S.C. 78s(b)(2).
    \5\ See Securities Exchange Act Release No. 95270 (July 13,
2022), 87 FR 43065 (July 19, 2022).
    \6\ See letters to Vanessa Countryman, Secretary, Commission,
from Rob Toomey, Managing Direct & Associate General Counsel, and
Charles de Simone, Managing Director, Technology and Operations,
Securities Industry and Financial Markets Association (``SIFMA''),
dated June 24, 2022 (``SIFMA Letter''); Howard Meyerson, Managing
Director, Financial Information Forum (``FIF''), dated June 24, 2022
(``FIF Letter''); Gerard O'Reilly, Co-CEO and Chief Investment
Officer, Dimensional Fund Advisors LP, dated June 22, 2022; Stephen
John Berger, Managing Director, Global Head of Government &
Regulatory Policy, Citadel Securities, dated June 24, 2022
(``Citadel Letter''); Joanna Mallers, Secretary, FIA Principal
Traders Group, dated June 24, 2022 (``FIA Letter''). The comment
letters are available at: https://www.sec.gov/comments/sr-finra-2022-013/srfinra2022013.htm.
    \7\ See letter to Vanessa Countryman, Secretary, Commission,
from Robert McNamee, FINRA, dated August 18, 2022 (``FINRA Response
Letter'').
---------------------------------------------------------------------------

II. Description of the Proposal

    FINRA is proposing two changes to its Trade Reporting and
Compliance Engine (``TRACE'') \8\ reporting rules to enhance the
regulatory audit trail and require members to report transactions in
U.S. Treasury Securities \9\ to FINRA in a more timely manner.
Information reported to TRACE regarding transactions in U.S. Treasury
Securities \10\ is used for regulatory and

other official sector \11\ purposes and is not disseminated
publicly.\12\ Among other regulatory uses, FINRA makes the data
available to the official sector to assist in the monitoring and
analysis of the U.S. Treasury Security markets. The first proposed
change would require members to report electronically executed
transactions in U.S. Treasury Securities to TRACE in the finest
increment captured by the system that executed the transaction. FINRA
is proposing to provide an exception from the amended execution
timestamp provision for members with limited trading volume in U.S.
Treasury Securities. The second proposed change would reduce the
reporting timeframe for transactions in U.S. Treasury Securities.
---------------------------------------------------------------------------

    \8\ TRACE is the FINRA-developed system that facilitates the
mandatory reporting of over-the-counter transactions in eligible
fixed income securities. See generally FINRA Rule 6700 Series.
    \9\ Under Rule 6710(p), a ``U.S. Treasury Security'' means a
security, other than a savings bond, issued by the U.S. Department
of the Treasury (the ``Treasury Department'') to fund the operations
of the federal government or to retire such outstanding securities.
The term ``U.S. Treasury Security'' also includes separate principal
and interest components of a U.S. Treasury Security that has been
separated pursuant to the Separate Trading of Registered Interest
and Principal of Securities (STRIPS) program operated by the
Treasury Department.
    \10\ FINRA members began reporting information on transactions
in U.S. Treasury Securities to TRACE on July 10, 2017. See FINRA
Regulatory Notice 16-39 (October 2016); see also Securities Exchange
Act Release No. 79116 (October 18, 2016), 81 FR 73167 (October 24,
2016) (Order Granting Accelerated Approval of File No. SR-FINRA-
2016-027). See Notice, supra note 3, at 33844-45.
    \11\ The Treasury Department, the Board of Governors of the
Federal Reserve System (the ``Federal Reserve''), the Federal
Reserve Bank of New York, the SEC and the U.S. Commodity Futures
Trading Commission comprise the Inter-Agency Working Group for
Treasury Market Surveillance (IAWG or ``official sector'').
    \12\ On March 10, 2020, FINRA began posting on its website
weekly, aggregate data on the trading volume of U.S. Treasury
Securities reported to TRACE. See FINRA Press Release, FINRA
Launches New Data on Treasury Securities Trading Volume, https://www.finra.org/media-center/newsreleases/2020/finra-launches-new-data-treasury-securities-trading-volume; see also Securities
Exchange Act Release No. 87837 (December 20, 2019), 84 FR 71986
(December 30, 2019) (Order Approving File No. SR-FINRA-2019-028).
Information on individual transactions in U.S. Treasury Securities
is not published or disseminated.
---------------------------------------------------------------------------

Execution Timestamps

    Existing Supplementary Material .04 to Rule 6730 provides that,
when reporting transactions in U.S. Treasury Securities executed
electronically to TRACE, FINRA members must report the Time of
Execution \13\ pursuant to paragraph (c)(8) of Rule 6730 to the finest
increment of time captured by the member's system (e.g., millisecond,
microsecond), but at a minimum, in increments of seconds.\14\ The
``member's system'' referenced in the existing rule refers to the
system that is used to report the transaction to TRACE (i.e., the
member's ``reporting system''). Under the existing FINRA rule and
related guidance, if a member uses multiple systems to facilitate trade
reporting and those systems differ in granularity, then the member may
use the finest increment that is common across all systems.\15\ As a
result, currently FINRA members may use a reporting system to report a
trade to TRACE in an increment of time that is less precise than that
captured by the system that is used to execute the transaction (i.e.,
the ``execution system'').\16\
---------------------------------------------------------------------------

    \13\ Under Rule 6710(d), the ``Time of Execution'' generally
means the time when the parties to a transaction agree to all of the
terms of the transaction that are sufficient to calculate the dollar
price of the trade.
    \14\ Existing Supplementary Material .04 provides that a member
must report ``at a minimum, in increment of seconds.'' As discussed
below, FINRA states that, to avoid confusion, the proposed
amendments update this language to clarify that members must report
trades in an increment of ``no longer than a second'' and no shorter
than a microsecond. TRACE currently cannot accept a Time of
Execution in an increment that is finer than a microsecond. The
proposed rule change would also make a non-substantive edit to
Supplementary Material .04 to capitalize the defined term ``Time of
Execution.'' See Notice, supra note 3, at 33845 n. 10.
    \15\ Specifically, TRACE Treasury FAQ #3.5.8 provides as
follows: Question: Our firm will use two separate systems to
facilitate trade reporting of U.S. Treasury Securities for different
business lines. One system (``System A'') has the capability to
capture the time of execution to the millisecond; however, the
second system (``System B'') will only capture the time of execution
to the second. Will our firm be required to update System B to
capture the time of execution to the millisecond? Answer: No. The
rule requires members to report the time of electronic executions to
the finest increment of time captured in the member's system (e.g.,
millisecond, microsecond), but at a minimum, in increments of
seconds. Since the firm would be reporting the time of execution to
the finest increment captured by each system, the firm would not
need to make any updates to System B to comply with a finer time
increment.
    \16\ For purposes of Supplementary Material .04, FINRA would
consider the relevant execution system to be the system used to
execute the particular U.S. Treasury Security transaction being
reported to TRACE, regardless of whether the member is using its own
internal systems for execution or if the transaction is executed
through an external system. For example, if a member executes a
transaction in a U.S. Treasury Security through an alternative
trading system (``ATS'') or other electronic trading platform, the
member would be required to report in the finest increment of time
captured by such ATS or electronic trading platform (but no finer
than a microsecond, in line with TRACE system parameters). See
Notice, supra note 3, at 33845 n. 12.
---------------------------------------------------------------------------

    To improve the granularity and consistency of transaction
information for U.S. Treasury Securities, FINRA is proposing to amend
Supplementary Material .04 to Rule 6730 to instead provide that, when
reporting transactions in U.S. Treasury Securities executed
electronically, members must report the Time of Execution pursuant to
paragraph (c)(8) of Rule 6730 to the finest increment of time captured
by the execution system (e.g., millisecond, microsecond), but reporting
must be in an increment of (i) no longer than a second and (ii) no
shorter than a microsecond. Amended Supplementary Material .04 would
not require FINRA members to update execution systems for U.S. Treasury
Securities--instead members must update their reporting systems, if
necessary, to ensure that their TRACE reports reflect the finest
increment of time captured by the execution system (but not finer than
a microsecond).\17\ Therefore, a FINRA member may be required to update
its reporting system for U.S. Treasury Securities if such reporting
system does not currently report to TRACE to the same level of
granularity as the execution system.\18\
---------------------------------------------------------------------------

    \17\ The TRACE system does not accept trade reports in
increments finer than a microsecond. Where a firm captures time in a
finer increment, the firm must truncate the time when reporting the
transaction to TRACE. Specifically, TRACE FAQ #3.5.37 provides as
follows: Question: Is rounding permitted when reporting the Time of
Execution of a U.S. Treasury Security transaction to TRACE? Answer:
No. Members must accurately report a transaction's Time of Execution
and are not permitted to round when reporting to TRACE. The TRACE
system can accommodate reporting up to the microsecond and, where
the firm captures time in an increment finer than microseconds, the
firm must truncate when reporting to TRACE. See Notice, supra note
3, at 33845 n. 13.
    \18\ See Notice, supra note 3, at 33845. In connection with the
proposed rule change, FINRA also proposes to amend its existing
TRACE FAQs to clarify that a member must report using the finest
increment of time captured by the execution system, and therefore
may need to update other systems to enable trade reporting using the
execution system's level of timestamp granularity. See Notice, supra
note 3, at 33845 n. 14.
---------------------------------------------------------------------------

    FINRA is also proposing to add new Supplementary Material .07 to
Rule 6730 to provide a limited exception for members with limited
trading volume in U.S. Treasury Securities from the proposed
requirement to report electronically executed transactions in U.S.
Treasury Securities to the finest increment of time captured by the
execution system.\19\ The proposed Supplementary Material would define
a ``member with limited trading volume in U.S. Treasury Securities'' as
a FINRA member that executed transactions in U.S. Treasury Securities
of $10 million or less in average daily par value, computed by
aggregating buy and sell transactions, during the preceding calendar
year. Where a member's activity is below the proposed criteria during
the preceding calendar year, such member would not be required to
report transactions in U.S. Treasury Securities in the finest increment
captured by the execution system and would be permitted to continue to

report the Time of Execution for transactions in U.S. Treasury
Securities executed electronically as it does today for the duration of
the following calendar year.
---------------------------------------------------------------------------

    \19\ The proposed rule change would also make non-substantive,
conforming edits to the Supplementary Material to Rule 6730.
Specifically, existing Supplementary Material .06 to Rule 6730
provided a temporary exception for aggregate transaction reporting
of U.S. Treasury Securities executed in ATS trading sessions. By its
terms, that temporary exception expired on April 12, 2019.
Therefore, FINRA is proposing to delete the temporary exception
under existing Supplementary Material .06, renumber existing
Supplementary Material .07 (ATS Identification of Non-FINRA Member
Counterparties for Transactions in U.S. Treasury Securities) as
Supplementary Material .06 and add the new exception for members
with limited trading volume in U.S. Treasury Securities as new
Supplementary Material .07. See Notice, supra note 3, at 33846 n.
15.
---------------------------------------------------------------------------

    Under the proposed rule change, a FINRA member that relies on the
exception for limited trading volume would be required to confirm on an
annual basis that it continues to meet the criteria for the exception
based on its trading activity during the preceding calendar year. Where
a member no longer meets the criteria for the exception based on its
trading activity during a given preceding calendar year, the member may
no longer rely on the exception beginning 90 days after the end of such
calendar year, which FINRA believes would provide such members with a
sufficient amount of time to make any systems changes that may be
needed to comply with the amended timestamp requirement.\20\
---------------------------------------------------------------------------

    \20\ Under the proposed rule change, once a member's activity
falls outside of the scope of the proposed criteria based on its
trading activity during a given preceding calendar year, such member
generally may no longer rely on the exception beginning 90 days
after the end of such calendar year, irrespective of whether it
again meets the criteria in a subsequent calendar year. However, a
member may consult with FINRA staff regarding the availability of
the exception where the member has changed business lines or
undergone a corporate restructuring that significantly impacts its
level of activity in U.S. Treasury Securities. See Notice, supra
note 3, at 33846 n. 16.
---------------------------------------------------------------------------

Reporting Timeframe Reduction

    Under existing Rule 6730(a)(4)(A), transactions in U.S. Treasury
Securities executed on a business day at or after 12:00:00 a.m. Eastern
Time through 5:00:00 p.m. Eastern Time must be reported the same day
during TRACE System Hours, i.e., 8:00:00 a.m. Eastern Time through
6:29:59 p.m. Eastern Time.\21\ A transaction executed on a business day
after 5:00:00 p.m. Eastern Time but before the TRACE system closes can
be reported the same day before the TRACE system closes, but must be
reported no later than the next business day (T+1) during TRACE System
Hours, i.e., 8:00:00 a.m. Eastern Time through 6:29:59 p.m. Eastern
Time, and, if reported on T+1, designated ``as/of'' and include the
date of execution. Finally, a transaction executed on a business day at
or after 6:30:00 p.m. Eastern Time through 11:59:59 p.m. Eastern Time
(or a Saturday, a Sunday, a federal or religious holiday or other day
on which the TRACE system is not open at any time during that day) must
be reported the next business day (T+1) during TRACE System Hours,
i.e., 8:00:00 a.m. Eastern Time through 6:29:59 p.m. Eastern Time,
designated ``as/of,'' and include the date of execution.
---------------------------------------------------------------------------

    \21\ Under Rule 6710(t), ``TRACE System Hours'' means the hours
the TRACE system is open, which are 8:00:00 a.m. Eastern Time
through 6:29:59 p.m. Eastern Time on a business day, unless
otherwise announced by FINRA.
---------------------------------------------------------------------------

    To provide more timely information about transactions in U.S.
Treasury Securities, FINRA is proposing to amend Rule 6730(a)(4) to
reduce the trade reporting timeframe as follows.\22\ Amended Rule
6730(a)(4) would provide that transactions in U.S. Treasury Securities
must be reported as soon as practicable, but no later than the
following time periods.\23\ Amended Rule 6730(a)(4)(A) would require
that a transaction executed on a business day at or after 12:00:00 a.m.
Eastern Time through 7:59:59 a.m. Eastern Time must be reported the
same day no later than 60 minutes after the TRACE system opens. A
transaction executed on a business day at or after the time the TRACE
system opens at 8:00:00 a.m. Eastern Time through when the TRACE system
closes at 6:29:59 p.m. Eastern Time (standard TRACE System Hours) must
be reported within 60 minutes of the Time of Execution, except that a
transaction executed on a business day less than 60 minutes before
6:30:00 p.m. Eastern Time can be reported the same day before the TRACE
system closes, but must be reported no later than 60 minutes after the
TRACE system opens the next business day (T+1), and if reported on T+1,
designated ``as/of'' and include the date of execution. Finally, a
transaction executed on a business day at or after 6:30:00 p.m. Eastern
Time through 11:59:59 p.m. Eastern Time, or a Saturday, a Sunday, a
federal or religious holiday or other day on which the TRACE system is
not open at any time during that day (determined using Eastern Time)
must be reported the next business day (T+1) no later than 60 minutes
after the TRACE system opens, designated ``as/of,'' and include the
date of execution.
---------------------------------------------------------------------------

    \22\ FINRA is not proposing to provide an exception for members
with limited trading activity in U.S. Treasury Securities from the
proposed reduced reporting timeframe requirement. See Notice, supra
note 3, at 33846 n. 18.
    \23\ In connection with the proposed changes to Rule 6730(a)(4)
discussed above, the proposed rule change would also make conforming
changes to Supplementary Material .03 to Rule 6730, which sets forth
standards for firms reporting transactions ``as soon as
practicable'' after the Time of Execution in accordance with Rule
6730(a). Existing Rule 6730.03 provides that ``[e]ach member with a
trade reporting obligation pursuant to paragraph (a) above for a
TRACE-Eligible Security that is subject to dissemination must adopt
policies and procedures reasonably designed to comply with the
requirement that transactions in TRACE-Eligible Securities be
reported `as soon as practicable' by implementing systems that
commence the trade reporting process at the Time of Execution
without delay.'' Under the proposed rule change, the ``as soon as
practicable'' standard would also apply to transactions in U.S.
Treasury Securities, which are not subject to dissemination.
Therefore, FINRA is proposing to update the first sentence of Rule
6730.03 to provide that ``[e]ach member with an obligation to report
a transaction in a TRACE-Eligible Security `as soon as practicable'
pursuant to paragraph (a) of this Rule must adopt policies and
procedures reasonably designed to comply with this requirement by
implementing systems that commence the trade reporting process at
the Time of Execution without delay.'' See Notice, supra note 3, at
33846 n. 19.
---------------------------------------------------------------------------

    FINRA represents that it will announce the effective date of the
proposed rule change in a Regulatory Notice. The effective date will be
no later than 365 days following publication of the Regulatory Notice
announcing Commission approval of the proposed rule change.

III. Discussion and Commission Findings

    After careful review of the proposed rule change, the comment
letters, and FINRA's response to the comments, the Commission finds
that the proposed rule change is consistent with the requirements of
the Act and the rules and regulations thereunder applicable to a
national securities association.\24\ In particular, the Commission
finds that the proposed rule change is consistent with Section
15A(b)(6) of the Act,\25\ which requires, among other things, that
FINRA's rules be designed to prevent fraudulent and manipulative acts
and practices; promote just and equitable principles of trade, and, in
general, protect investors and the public interest. In particular, the
proposed rule change would enhance the regulatory audit trail for U.S.
Treasury Securities available to FINRA and the official sector and
assist FINRA in carrying out its statutory duties to surveil and
regulate this segment of the market.
---------------------------------------------------------------------------

    \24\ In approving this proposed rule change, the Commission has
considered the proposed rule's impact on efficiency, competition,
and capital formation. See 15 U.S.C. 78c(f).
    \25\ 15 U.S.C. 78o-3(b)(6).
---------------------------------------------------------------------------

    Pursuant to Section 19(b)(5) of the Act,\26\ the Commission
consulted with and considered the views of the Treasury Department in
determining to approve the proposed rule change. The Treasury
Department indicated its

support for the proposal.\27\ Furthermore, pursuant to Section 19(b)(6)
of the Act,\28\ the Commission has considered the sufficiency and
appropriateness of existing laws and rules applicable to government
securities brokers, government securities dealers, and their associated
persons in approving the proposal.
---------------------------------------------------------------------------

    \26\ See 15 U.S.C. 78s(b)(5) (providing that the Commission
``shall consult with and consider the views of the Secretary of the
Treasury prior to approving a proposed rule filed by a registered
securities association that primarily concerns conduct related to
transactions in government securities, except where the Commission
determines that an emergency exists requiring expeditious or summary
action and publishes its reasons therefor'').
    \27\ See Email from U.S. Treasury Department staff to Justin
Pica, Division of Trading and Markets, Commission (August 25, 2022).
    \28\ 15 U.S.C. 78s(b)(6).
---------------------------------------------------------------------------

Execution Timestamps

    As stated above, FINRA proposes to require members to report
electronically executed transactions in U.S. Treasury Securities to
TRACE in the finest increment captured by the system that executed the
transaction. FINRA also proposes to provide an exception from the
amended execution timestamp provision for members with limited trading
volume in U.S. Treasury Securities. Two commenters raised operational
and technological concerns associated with this proposal \29\ and two
commenters requested clarification to the definition of an
electronically executed transaction.\30\
---------------------------------------------------------------------------

    \29\ See SIFMA Letter at 3; FIF Letter at 2.
    \30\ See SIFMA Letter at 3; FIF Letter at 2.
---------------------------------------------------------------------------

    FINRA states that it acknowledges the operational and technological
changes that members may need to undertake in order to comply with the
proposed change.\31\ FINRA also states its view that the benefits to
the regulatory audit trail of aligning the timestamps reported to TRACE
with those captured by the relevant execution system are
appropriate.\32\ In response to comments seeking clarification to the
definition of an electronically executed transaction, FINRA notes that
the current timestamp granularity provision in TRACE reporting rules
already applies to transactions that are ``executed electronically''
and further notes that it encourages members to contact FINRA for
guidance on whether a particular transaction would be considered an
electronically executed transaction.\33\
---------------------------------------------------------------------------

    \31\ See FINRA Response Letter at 4-5.
    \32\ See FINRA Response Letter at 5.
    \33\ See id.
---------------------------------------------------------------------------

    The Commission believes that the proposed change to align the level
of granularity provided in TRACE reports with the level of granularity
in the execution systems will enhance the regulatory audit trail for
U.S. Treasury Securities available to FINRA and the official sector by
facilitating more efficient matching and sequencing of transactions in
the audit trail data.\34\ As discussed above, the current rule permits
FINRA members to report a trade to TRACE in an increment of time that
is less precise than that captured by the execution system, which makes
it difficult for FINRA to match and sequence trades. The Commission
believes the proposed change is reasonably designed to address this
concern as FINRA represents that finer time granularity in the audit
trail would allow transactions to be matched more accurately and
sequenced with more precision, thus facilitating trade matching and
sequencing for U.S. Treasury Securities. This, in turn, facilitates
market oversight by providing FINRA and the official sector with more
useful information on U.S. Treasury Security transactions. The
Commission also believes that providing an exception from the amended
execution timestamp requirement for FINRA members with limited trading
volume in U.S. Treasury Securities is appropriate, as the proposed
exception would reduce burdens for FINRA members with limited activity.
---------------------------------------------------------------------------

    \34\ FINRA represents that, under the existing rule, members may
report a trade to TRACE in an increment of time that is less precise
than that captured by the execution system, which makes it difficult
for FINRA to match interdealer trades when two sides report at
different time granularity because coarse granularity in timestamps
makes sequencing trades less precise. To address this concern, the
proposal requires that, when reporting transactions in U.S. Treasury
Securities executed electronically, members must report the Time of
Execution to the finest increment of time captured by the execution
system, but must report in an increment of time that is no longer
than a second and no shorter than a microsecond. See Notice, supra
note 3, at 33847.
---------------------------------------------------------------------------

    The Commission recognizes that the proposed change may result in
costs for FINRA members that trade U.S. Treasury Securities where
members must implement changes to their processes and systems for
reporting U.S. Treasury Securities transactions to TRACE. As discussed
above, however, the Commission believes that the important regulatory
purpose served by the proposal justifies the potential burdens. The
Commission also recognizes that the proposed change may also affect
competition among reporting firms, where firms reporting only a limited
number of trades may face the same costs of upgrading their systems and
therefore find their limited trading in U.S. Treasury Securities less
viable. The Commission nevertheless believes that the impact on such
firms is expected to be mitigated by the proposed exception for
eligible FINRA members with limited trading volume, as previously
described.

Reporting Timeframe Reduction

    As stated above, FINRA proposes to shorten the reporting timeframe
for transactions in U.S. Treasury Securities. Two commenters support
the proposal to require members to report transactions in U.S. Treasury
Securities to TRACE in a more timely manner.\35\ One commenter suggests
that FINRA postpone implementation of a shorter reporting
timeframe.\36\ This commenter notes several current initiatives related
to TRACE, including the Treasury Department's recent publication of a
Request for Information \37\ (RFI) on additional post-trade
transparency of data regarding secondary market transactions of U.S.
Treasury Securities, and suggests that implementing technological and
operational changes now, followed by the possibility of additional
changes at a later date, would be inefficient and could result in work
that is unnecessary in the long term.\38\
---------------------------------------------------------------------------

    \35\ See Citadel Letter at 1; FIA Letter at 1-2.
    \36\ See SIFMA Letter at 1-2. This commenter also encouraged
FINRA to review the benefits of a shortened reporting timeframe in
light of how FINRA and its regulatory partners are using TRACE data,
and to consider whether that use is impeded by the current reporting
timeframes and whether there are any incremental benefits from a 60-
minute timeframe as opposed to an intermediate interval (such as two
hours, as originally recommended by SIFMA). See id. In response,
FINRA states that the proposal strikes an appropriate balance to
provide FINRA and the official sector with more timely information
about U.S. Treasury Security market activity, noting that members
already report over 90 percent of transactions in U.S. Treasury
Securities within 60 minutes of the Time of Execution. See FINRA
Response Letter at 4.
    \37\ See Treasury Department, Notice Seeking Public Comment on
Additional Transparency for Secondary Market Transactions of
Treasury Securities, 87 FR 38259 (June 27, 2022) (Docket No. TREAS-
DO-2022-0012).
    \38\ See SIFMA Letter at 2.
---------------------------------------------------------------------------

    FINRA acknowledges the fact that there are several current TRACE
initiatives \39\ but notes that it does not believe that there is any
conflict presented by advancing the proposal to shorten the reporting
timeframe for transactions in U.S. Treasury Securities and states that
it does not believe that the benefits of a shortened reporting
timeframe for transactions in U.S. Treasury Securities are reduced in
light of these other initiatives.\40\ Further, in response to concerns
that the Treasury Department's RFI could result in a proposal or
recommendation to increase transparency for transactions in U.S.
Treasury Securities,\41\ FINRA notes that prior increases in
transparency provided by TRACE for other fixed income

products have been preceded by a shortened reporting timeframe.\42\
---------------------------------------------------------------------------

    \39\ See, e.g., FINRA Regulatory Notice 22-17 (August 2, 2022)
(FINRA Requests Comment on a Proposal to Shorten the Trade Reporting
Timeframe for Transactions in Certain TRACE-Eligible Securities From
15 Minutes to One Minute) available at https://www.finra.org/rules-guidance/notices/22-17.
    \40\ See FINRA Response Letter at 3.
    \41\ See SIFMA Letter at 2-3
    \42\ See FINRA Response Letter at 3. With respect to the U.S.
Treasury Department's RFI, FINRA further states that, should that
initiative result in a proposal or recommendation to increase
transparency for transactions in U.S. Treasury Securities, such a
result would harmonize with a reduced reporting timeframe for U.S.
Treasury Securities. See id.
---------------------------------------------------------------------------

    The Commission believes that shortening the timeframe for FINRA
members to report transactions in U.S. Treasury Securities to TRACE to
as soon as practicable, but no later than within 60 minutes of the Time
of Execution (or within 60 minutes after the TRACE system opens for
trades executed during specified periods, as described above) will
assist FINRA in carrying out its statutory duties to surveil and
regulate this segment of the market by providing FINRA with more timely
information about activity in the market for U.S. Treasury Securities,
including more timely data about intraday pricing and liquidity.
    The Commission recognizes that the proposal may result in costs for
FINRA members that need to implement changes to their processes and
systems. The Commission notes that, according to FINRA, approximately
96 percent of U.S. Treasury Security transaction reports were reported
within 60 minutes of the Time of Execution during a sample period of
July 2020 to June 2021.\43\ In addition, FINRA represents that some
FINRA members who trade in U.S. Treasury Securities also trade in other
types of TRACE-Eligible Securities that already require reporting
within a shorter timeframe.\44\ While these transactions may occur on
separate trading desks, the Commission agrees with FINRA that, to the
extent that members are able to leverage existing technology within the
firm, the costs associated with the proposed reporting timeframe
changes for U.S. Treasury Securities could potentially be reduced. With
respect to comments suggesting that FINRA should review the benefits of
a shortened reporting timeframe in light of how FINRA and its
regulatory partners are using TRACE data,\45\ the Commission agrees
with FINRA's assessment that the proposal strikes an appropriate
balance to provide FINRA and the official sector with more timely
information about U.S. Treasury Security market activity. The
Commission notes that FINRA members already report over 90 percent of
transactions in U.S. Treasury Securities within 60 minutes of the Time
of Execution.\46\
---------------------------------------------------------------------------

    \43\ See Notice, supra note 3, at 33848.
    \44\ For example, FINRA states that transactions in corporate
bonds and Agency Debt Securities generally are required to be
reported to FINRA as soon as practicable, but no later than within
15 minutes of the Time of Execution. In the FINRA sample period, of
the 750 MPIDs that reported transactions in U.S. Treasury
Securities, 691 MPIDs also reported transactions in corporate bonds
and Agency Debt Securities. See Notice, supra note 3, at 33848.
    \45\ See supra note 36 and accompanying text.
    \46\ See FINRA Response Letter at 4.
---------------------------------------------------------------------------

    Finally, the Commission believes that it would not be appropriate
to delay implementation of the proposal beyond the timeframe set forth
in the Notice. The Commission agrees with FINRA in its assessment that
the proposal does not conflict with other TRACE-related initiatives and
that the benefits of a shortened reporting timeframe for transactions
in U.S. Treasury Securities are not reduced in light of these other
initiatives. Moreover, the Commission believes that further delaying
implementation of the proposal would undermine the regulatory interest
that the official sector and FINRA have in obtaining access to more
timely information about activity in the market for U.S. Treasury
Securities.

IV. Conclusion

    It is therefore ordered, pursuant to Section 19(b)(2) of the
Act,\47\ that the proposed rule change (SR-FINRA-2022-013) is approved.
---------------------------------------------------------------------------

    \47\ 15 U.S.C. 78s(b)(2).

    For the Commission, by the Division of Trading and Markets,
pursuant to delegated authority.\48\
---------------------------------------------------------------------------

    \48\ 17 CFR 200.30-3(a)(12).
---------------------------------------------------------------------------

J. Matthew DeLesDernier,
Deputy Secretary.
[FR Doc. 2022-19112 Filed 9-2-22; 8:45 am]
BILLING CODE 8011-01-P


[Federal Register Volume 81, Number 214 (Friday, November 4, 2016)]
[Rules and Regulations]
[Pages 76857-76858]
[FR Doc No: 2016-26455]

-----------------------------------------------------------------------

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 71

[Docket No. FAA-2012-1308; Airspace Docket No. 12-ASO-44]

Establishment of Class E Airspace; Camden, AL

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Final rule.

-----------------------------------------------------------------------

SUMMARY: This action establishes Class E airspace at Camden, AL to
accommodate new Area Navigation (RNAV) Global Positioning System (GPS)
Standard Instrument Approach Procedures (SIAPs) serving Camden
Municipal Airport. Controlled airspace is necessary for the safety and
management of instrument flight rules (IFR) operations at the airport.

DATES: Effective 0901 UTC, January 5, 2017. The Director of the Federal
Register approves this incorporation by reference action under title 1,
Code of Federal Regulations, part 51, subject to the annual revision of
FAA Order 7400.11 and publication of conforming amendments.

ADDRESSES: FAA Order 7400.11A, Airspace Designations and Reporting
Points, and subsequent amendments can be viewed online at http://www.faa.gov/air_traffic/publications/. For further information, you can
contact the Airspace Policy Group, Federal Aviation Administration, 800
Independence Avenue SW., Washington, DC 20591; telephone:<PHONE_NUMBER>.
The Order is also available for inspection at the National Archives and
Records Administration (NARA). For information on the availability of
FAA Order 7400.11A at NARA, call<PHONE_NUMBER>, or go to http://www.archives.gov/federal_register/code_of_federal-regulations/ibr_locations.html.
    FAA Order 7400.11, Airspace Designations and Reporting Points, is
published yearly and effective on September 15.

FOR FURTHER INFORMATION CONTACT: John Fornito, Operations Support
Group, Eastern Service Center, Federal Aviation Administration, P.O.
Box 20636, Atlanta, Georgia 30320; telephone<PHONE_NUMBER>.

SUPPLEMENTARY INFORMATION:

Authority for This Rulemaking

    The FAA's authority to issue rules regarding aviation safety is
found in Title 49 of the United States Code. Subtitle I, Section 106
describes the authority of the FAA Administrator. Subtitle VII,
Aviation Programs, describes in more detail the scope of the agency's
authority. This rulemaking is promulgated under the authority described
in Subtitle VII, Part, A, Subpart I, Section 40103. Under that section,
the FAA is charged with prescribing regulations to assign the use of
airspace necessary to ensure the safety of aircraft and the efficient
use of airspace. This regulation is within the scope of that authority
as it establishes Class E airspace at Camden Municipal Airport, Camden,
AL.

History

    On July 22, 2016, the FAA published in the Federal Register a
notice of proposed rulemaking (NPRM) to establish Class E airspace
upward from 700 feet above the surface at Camden, AL, (81 FR 47737)
Docket No. FAA-2012-1308, providing the controlled airspace required to
support the new RNAV (GPS) standard instrument approach procedures for
Camden Municipal Airport. Interested parties were invited to
participate in this rulemaking effort by submitting written comments on
the proposal to the FAA. No comments were received.
    Class E airspace designations are published in Paragraph 6005 of
FAA Order 7400.11A dated August 3, 2016, and effective September 15,
2016, which is incorporated by reference in 14 CFR part 71.1. The Class
E airspace designations listed in this document will be published
subsequently in the Order.

Availability and Summary of Documents for Incorporation by Reference

    This document amends FAA Order 7400.11A, Airspace Designations and
Reporting Points, dated August 3, 2016, and effective September 15,
2016. FAA Order 7400.11A is publicly available as listed in the
ADDRESSES section of this document. FAA Order 7400.11A lists Class A,
B, C, D, and E airspace areas, air traffic service routes, and
reporting points.

The Rule

    This amendment to Title 14, Code of Federal Regulations (14 CFR)
part 71 establishes Class E Airspace at Camden

Municipal Airport, Camden, AL. Controlled airspace extending upward
from 700 feet above the surface within a 7.7-mile radius of the airport
is established for IFR operations.

Regulatory Notices and Analyses

    The FAA has determined that this regulation only involves an
established body of technical regulations for which frequent and
routine amendments are necessary to keep them operationally current.
It, therefore: (1) Is not a ``significant regulatory action'' under
Executive Order 12866; (2) is not a ``significant rule'' under DOT
Regulatory Policies and Procedures (44 FR 11034; February 26, 1979);
and (3) does not warrant preparation of a regulatory evaluation as the
anticipated impact is so minimal. Since this is a routine matter that
only affects air traffic procedures and air navigation, it is certified
that this rule, when promulgated, does not have a significant economic
impact on a substantial number of small entities under the criteria of
the Regulatory Flexibility Act.

Environmental Review

    The FAA has determined that this action qualifies for categorical
exclusion under the National Environmental Policy Act in accordance
with FAA Order 1050.1F, ``Environmental Impacts: Policies and
Procedures,'' paragraph 5-6.5a. This airspace action is not expected to
cause any potentially significant environmental impacts, and no
extraordinary circumstances exist that warrant preparation of an
environmental assessment.

Lists of Subjects in 14 CFR Part 71

    Airspace, Incorporation by reference, Navigation (air).

Adoption of the Amendment

    In consideration of the foregoing, the Federal Aviation
Administration amends 14 CFR part 71 as follows:

PART 71--DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR
TRAFFIC SERVICE ROUTES; AND REPORTING POINTS

0
1. The authority citation for Part 71 continues to read as follows:

    Authority: 49 U.S.C. 106(f), 106(g); 40103, 40113, 40120, E.O.
10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.

Sec.  71.1  [Amended]

0
2. The incorporation by reference in 14 CFR 71.1 of FAA Order 7400.11A,
Airspace Designations and Reporting Points, dated August 3, 2016,
effective September 15, 2016, is amended as follows:

Paragraph 6005. Class E Airspace Areas Extending Upward From 700
Feet or More Above the Surface of the Earth.

* * * * *

ASO AL E5 Camden, AL [New]

Camden Municipal Airport, AL
    (Lat. 31[deg]58'47'' N., long. 87[deg]20'21'' W.)

    That airspace extending upward from 700 feet above the surface
within a 7.7-mile radius of Camden Municipal Airport.

    Issued in College Park, Georgia, on October 21, 2016.
Ryan W. Almasy,
Manager, Operations Support Group, Eastern Service Center, Air Traffic
Organization.
[FR Doc. 2016-26455 Filed 11-3-16; 8:45 am]
 BILLING CODE 4910-13-P