[Federal Register: September 2, 2008 (Volume 73, Number 170)]
[Proposed Rules]
[Page 51252-51254]
[DOCID:fr02se08-14]

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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 71

[Docket No. FAA-2008-0453; Airspace Docket No. 08-AAL-12]

Proposed Establishment of Class E Airspace; Kwethluk, AK

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Notice of proposed rulemaking.

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

SUMMARY: This action proposes to establish Class E airspace at
Kwethluk, AK. Two Standard Instrument Approach Procedures (SIAPs) are
being developed for the Kwethluk Airport at Kwethluk, AK. Adoption of
this proposal would result in creating Class E airspace upward from 700
feet (ft.)

and 1,200 ft. above the surface at the Kwethluk Airport, Kwethluk, AK.

DATES: Comments must be received on or before October 17, 2008.

ADDRESSES: Send comments on the proposal to the Docket Management
Facility, U.S. Department of Transportation, 1200 New Jersey Avenue,
SE., West Building Ground Floor, Room W12-140, Washington, DC 20590-
0001. You must identify the docket number FAA-2008-0453/Airspace Docket
No. 08-AAL-12, at the beginning of your comments. You may also submit
comments on the Internet at http://www.regulations.gov. You may review
the public docket containing the proposal, any comments received, and
any final disposition in person in the Dockets Office between 9 a.m.
and 5 p.m., Monday through Friday, except Federal holidays. The Docket
Office (telephone 1-800-647-5527) is on the plaza level of the
Department of Transportation NASSIF Building at the above address.
    An informal docket may also be examined during normal business
hours at the office of the Manager, Safety, Alaska Flight Service
Operations, Federal Aviation Administration, 222 West 7th Avenue, Box
14, Anchorage, AK 99513-7587.

FOR FURTHER INFORMATION CONTACT: Gary Rolf, Federal Aviation
Administration, 222 West 7th Avenue, Box 14, Anchorage, AK 99513-7587;
telephone number<PHONE_NUMBER>; fax:<PHONE_NUMBER>; e-mail:
<EMAIL_ADDRESS>Internet address: http://www.alaska.faa.gov/at.

SUPPLEMENTARY INFORMATION:

Comments Invited

    Interested parties are invited to participate in this proposed
rulemaking by submitting such written data, views, or arguments as they
may desire. Comments that provide the factual basis supporting the
views and suggestions presented are particularly helpful in developing
reasoned regulatory decisions on the proposal. Comments are
specifically invited on the overall regulatory, aeronautical, economic,
environmental, and energy-related aspects of the proposal.
Communications should identify both docket numbers and be submitted in
triplicate to the address listed above. Commenters wishing the FAA to
acknowledge receipt of their comments on this notice must submit with
those comments a self-addressed, stamped postcard on which the
following statement is made: ``Comments to Docket No. FAA-2008-0453/
Airspace Docket No. 08-AAL-12.'' The postcard will be date/time stamped
and returned to the commenter.
    All communications received on or before the specified closing date
for comments will be considered before taking action on the proposed
rule. The proposal contained in this notice may be changed in light of
comments received. All comments submitted will be available for
examination in the public docket both before and after the closing date
for comments. A report summarizing each substantive public contact with
FAA personnel concerned with this rulemaking will be filed in the
docket.

Availability of Notice of Proposed Rulemakings (NPRMs)

    An electronic copy of this document may be downloaded through the
Internet at http://www.regulations.gov. Recently published rulemaking
documents can also be accessed through the FAA's Web page at http://
www.faa.gov or the Superintendent of Documents' Web page at http://
www.access.gpo.gov/nara/index.html.
    Additionally, any person may obtain a copy of this notice by
submitting a request to the Federal Aviation Administration, Office of
Air Traffic Airspace Management, ATA-400, 800 Independence Avenue, SW.,
Washington, DC 20591 or by calling<PHONE_NUMBER>. Communications must
identify both docket numbers for this notice. Persons interested in
being placed on a mailing list for future NPRMs should contact the
FAA's Office of Rulemaking,<PHONE_NUMBER>, to request a copy of
Advisory Circular No. 11-2A, Notice of Proposed Rulemaking Distribution
System, which describes the application procedure.

The Proposal

    The FAA is considering an amendment to the Code of Federal
Regulations (14 CFR Part 71), which would establish Class E airspace at
the Kwethluk Airport, in Kwethluk, AK. The intended effect of this
proposal is to create Class E airspace upward from 700 ft. and 1,200
ft. above the surface to contain Instrument Flight Rules (IFR)
operations at the Kwethluk Airport, Kwethluk, AK.
    The FAA Instrument Flight Procedures Production and Maintenance
Branch has created two new SIAPs for the Kwethluk Airport. The SIAPs
are (1) the Area Navigation (RNAV) Global Positioning System (GPS)
Runway (RWY) 18, Original and (2) the RNAV (GPS) RWY 36, Original.
Class E controlled airspace extending upward from 700 ft. and 1,200 ft.
above the surface in the Kwethluk Airport area would be established by
this action. The proposed airspace is sufficient in size to contain
aircraft executing the instrument procedures at the Kwethluk Airport,
Kwethluk, AK.
    The area would be depicted on aeronautical charts for pilot
reference. The coordinates for this airspace docket are based on North
American Datum 83. The Class E airspace areas designated as 700/1200
foot transition areas are published in paragraph 6005 in FAA Order
7400.9R, Airspace Designations and Reporting Points, signed August 15,
2007, and effective September 15, 2007, which is incorporated by
reference in 14 CFR 71.1. The Class E airspace designations listed in
this document would be published subsequently in the Order.
    The FAA has determined that this proposed 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
will only affect air traffic procedures and air navigation, it is
certified that this rule, when promulgated, will not have a significant
economic impact on a substantial number of small entities under the
criteria of the Regulatory Flexibility Act.
    The FAA's authority to issue rules regarding aviation safety is
found in Title 49 of the United States Code. Subtitle 1, 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 1, Section 40103, Sovereignty and use of
airspace. Under that section, the FAA is charged with prescribing
regulations to ensure the safe and efficient use of the navigable
airspace. This regulation is within the scope of that authority because
it proposes to create Class E airspace sufficient in size to contain
aircraft executing instrument procedures at the Kwethluk Airport, AK,
and represents the FAA's continuing effort to safely and efficiently
use the navigable airspace.

List of Subjects in 14 CFR Part 71

    Airspace, Incorporation by reference, Navigation (air).

The Proposed Amendment

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

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

    1. The authority citation for 14 CFR part 71 continues to read as
follows:

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

Sec.  71.1  [Amended]

    2. The incorporation by reference in 14 CFR 71.1 of Federal
Aviation Administration Order 7400.9R, Airspace Designations and
Reporting Points, signed August 15, 2007, and effective September 15,
2007, is to be amended as follows:
* * * * *

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

* * * * *

AAL AK E5 Kwethluk, AK [New]

Kwethluk, Kwethluk Airport, AK
    (Lat. 60[deg]47'25'' N., long. 161[deg]26'37'' W.)

    That airspace extending upward from 700 feet above the surface
within a 6.3-mile radius of the Kwethluk Airport, AK; and that
airspace extending upward from 1,200 feet above the surface within a
73-mile radius of the Kwethluk Airport, AK.
* * * * *

    Issued in Anchorage, AK, on August 22, 2008.
James Miller,
Acting Manager, Alaska Flight Services Information Area Group.
[FR Doc. E8-20311 Filed 8-29-08; 8:45 am]

BILLING CODE 4910-13-P


[Federal Register Volume 88, Number 23 (Friday, February 3, 2023)]
[Notices]
[Page 7517]
[FR Doc No: 2023-02346]

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

DEPARTMENT OF TRANSPORTATION

Federal Railroad Administration

Notice of Funding Opportunity for the Federal-State Partnership
for Intercity Passenger Rail Grants Program for Projects Not Located on
the Northeast Corridor

AGENCY: Federal Railroad Administration (FRA), Department of
Transportation (DOT).

ACTION: Notice of Funding Opportunity (NOFO or notice); Extension and
Supplemental Funding Notice.

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

SUMMARY: FRA is adding funding and extending the application submittal
period for its Fiscal Year (FY) 2022 NOFO for the Federal-State
Partnership for Intercity Passenger Rail Program (FSP Program) for
projects not located on the Northeast Corridor published on December 7,
2022. The basis for the funding increase and extension is the
appropriation of additional amounts for the FSP Program from the
Consolidated Appropriations Act, 2023, together with the government's
goal of efficiently administering such funds.

DATES: The original due date was March 7, 2023. The period for
submitting applications to the NOFO published on December 7, 2022, is
extended. Applications must now be submitted by 5 p.m. EDT on April 21,
2023.

FOR FURTHER INFORMATION CONTACT: For further information concerning
this Notice, please contact the FRA NOFO Support program staff via
email at [email protected].

Amendment

    FRA amends its FY 2022 NOFO for the Federal-State Partnership for
Intercity Passenger Rail Program (FSP Program) for projects not located
on the Northeast Corridor published December 7, 2022 (87 FR 75119)
https://www.govinfo.gov/content/pkg/FR-2022-12-07/pdf/2022-26610.pdf.
by: (1) adding up to an additional $2,283,150,000 for a total of up to
$4,566,300,000 and (2) extending the period for submitting applications
to April 21, 2023.
    Section B.1. Federal Award Information/Available Award Amount is
deleted in its entirety, and the following is substituted therefore:

B. Federal Award Information

1. Available Award Amount
    The total funding available for awards under this NOFO is up to
$4,566,300,000 made available by IIJA supplemental appropriations, the
Appropriations Act, and the Consolidated Appropriations Act, 2023 (Pub.
L. 117-328, December 29, 2022), as follows:
    a. Up to $4,464,000,000 in IIJA supplemental appropriations: Title
VIII of Division J of IIJA provided $36,000,000,000 in supplemental
appropriations for the FSP Program, with not more than $24,000,000,000
made available for projects for the NEC and thus at least
$12,000,000,000 of such funds made available for FSP-National
($2,400,000,000 made available per year for fiscal years 2022 through
2026). After the funding set aside for FRA award and project management
oversight and the planning and development activities authorized at 49
U.S.C. 24911(k), up to $4,464,000,000 in funding made available for
fiscal year 2022 and fiscal year 2023 is made available for FSP Program
awards under this FSP-National NOFO.
    b. Up to $102,300,000 in fiscal year 2022 and fiscal year 2023
annual appropriations: The appropriations acts for fiscal year 2022 and
fiscal year 2023 provided $200,000,000 for the FSP Program. Consistent
with 49 U.S.C. 24911(d)(3), a minimum of 45 percent and a maximum of 55
percent of this amount is for FSP-National, of which not less than 20
percent (a minimum of $16,740,000) shall be for projects that benefit
(in whole or in part) a long-distance route. After the funding set
aside for FRA award and project management oversight and the planning
and development activities authorized at 49 U.S.C. 24911(k), at least
$83,700,000 and up to $102,300,000 in fiscal year 2022 and fiscal year
2023 annual funding is made available for FSP Program awards under this
FSP-National NOFO.
    Should additional FSP-National funds become available after the
release of this NOFO, FRA may elect to award such additional funds to
applications received under this NOFO. Any selection and award under
this NOFO is subject to the availability of appropriated funds.

    Issued in Washington, DC.
Amitabha Bose,
Administrator.
[FR Doc. 2023-02346 Filed 2-2-23; 8:45 am]
BILLING CODE 4910-06-P


[Federal Register Volume 83, Number 40 (Wednesday, February 28, 2018)]
[Proposed Rules]
[Pages 8647-8648]
[FR Doc No: 2018-04063]

=======================================================================
-----------------------------------------------------------------------

DEPARTMENT OF TRANSPORTATION

National Highway Traffic Safety Administration

49 CFR Part 571

[Docket No. NHTSA-2018-0009]

Removing Regulatory Barriers for Vehicles With Automated Driving
Systems; Extension of Comment Period

AGENCY: National Highway Traffic Safety Administration (NHTSA),
Department of Transportation (DOT).

ACTION: Request for comment; extension of comment period.

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

SUMMARY: In response to a request, NHTSA is extending the comment
period on the Removing Regulatory Barriers for Vehicles with Automated
Driving Systems Request for Comment (RFC) to March 20, 2018. The RFC
was published in the Federal Register on January 18, 2018. The comment
period for the RFC was originally scheduled to end on March 5, 2018.

DATES: The comment period for the request for comment published January
18, 2018, at 83 FR 2607, is extended. Written comments must be received
on or before March 20, 2018 in order to be considered timely.

ADDRESSES: Comments must refer to the docket number above and be
submitted by one of the following methods:
    [ssquf] Federal eRulemaking Portal: Go to http://www.regulations.gov. Follow the online instructions for submitting
comments.
    [ssquf] Mail: Docket Management Facility, M-30, U.S. Department of
Transportation, West Building, Ground Floor, Room W12-140, 1200 New
Jersey Avenue SE, Washington, DC 20590.
    [ssquf] Hand Delivery or Courier: U.S. Department of
Transportation, West Building, Ground Floor, Room W12-140, 1200 New
Jersey Avenue SE, Washington, DC, between 9 a.m. and 5 p.m. Eastern
time, Monday through Friday, except Federal holidays.
    [ssquf] Fax:<PHONE_NUMBER>.

    Regardless of how you submit your comments, you must include the
docket number identified in the heading of this notice.
    Note that all comments received, including any personal information
provided, will be posted without change to http://www.regulations.gov.
Please see the ``Privacy Act'' heading below.
    You may call the Docket Management Facility at<PHONE_NUMBER>.
    Docket: For access to the docket to read background documents or
comments received, go to http://www.regulations.gov or the street
address listed above. We will continue to file relevant information in
the Docket as it becomes available.
    Privacy Act: In accordance with 5 U.S.C. 553(c), DOT solicits
comments from the public to better inform its decision-making process.
DOT posts these comments, without edit, including any personal
information the commenter provides, to http://www.regulations.gov, as
described in the system of records notice (DOT/ALL-14 FDMS), which can
be reviewed at https://www.transportation.gov/privacy. Anyone can
search the electronic form of all comments received into any of our
dockets by the name of the individual submitting the comment (or
signing the comment, if submitted on behalf of an association,
business, labor union, etc.).

FOR FURTHER INFORMATION CONTACT: For research issues, Ellen Lee, Human
Injury Research Division, Office of Vehicle Safety Research, telephone:
202-366-1435, email: [email protected];
    For rulemaking issues, David Hines, Director, Office of Crash
Avoidance Standards, telephone<PHONE_NUMBER>, email [email protected];
    For legal issues, Stephen Wood, Assistant Chief Counsel, Vehicle
Rulemaking and Harmonization, Office of Chief Counsel,<PHONE_NUMBER>,
email [email protected].

SUPPLEMENTARY INFORMATION: On January 18, 2018, NHTSA published a
request for comment (RFC) (83 FR 2607) to identify regulatory barriers
in the existing Federal Motor Vehicle Safety Standards (FMVSS) to the
testing, compliance certification, and compliance verification of motor
vehicles with Automated Driving Systems (ADSs) and certain
unconventional interior designs. The RFC solicited public comments and
stated that the closing date for comment is on March 5, 2018.
    On February 8, 2018, NHTSA received a request for a 15-day
extension of the comment period from the Association of Global
Automakers, Inc. and the Alliance of Automobile Manufacturers. That
request can be found in the docket for the RFC listed above under
ADDRESSES. NHTSA has considered this request and believes that a 15-day
extension beyond the original due date is acceptable to provide
additional time for the public to comment on the RFC. This is to notify
the public that NHTSA is extending the comment period on the RFC, and
allowing it to run until March 20, 2018.
    NHTSA also notes that, on February 13, 2018, it published a notice
of a public meeting on regulatory barriers to be held at the Department
of Transportation headquarters in Washington, DC on March 6, 2018, from
10 a.m. through 3:30 p.m., EST (83 FR 6148). NHTSA is holding this
public meeting to present to the public a summary of the RFC and
activities underway at NHTSA and across the industry to identify and
remove barriers that might impede safe deployment of ADSs. The
combination of the comment period extension and the public meeting will
provide the public with even greater opportunities to learn about
efforts to address regulatory barriers and to provide meaningful input
through oral remarks or written comment.
    NHTSA will consider all comments received before the close of
business on the comment closing date, and will also consider comments
received after that date to the extent practicable. Instructions for
submitting comments are described in the Public Participation section
of the RFC (83 FR 2607, January 18, 2018).

    Issued in Washington, DC, on February 21, 2018 pursuant to
authority delegated in 49 CFR 1.81 and 1.95.
Heidi R. King,
Deputy Administrator.
[FR Doc. 2018-04063 Filed 2-27-18; 8:45 am]
 BILLING CODE 4910-59-P


[Federal Register: May 8, 2008 (Volume 73, Number 90)]
[Proposed Rules]
[Page 26047-26048]
[DOCID:fr08my08-27]

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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 71

[Docket No. FAA-2008-0308; Airspace Docket No. 08-AEA-19]

Modification of Class E Airspace; Rome, NY

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Notice of proposed rulemaking.

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

SUMMARY: This action proposes to modify Class E Airspace at Rome, NY.
Additional airspace is necessary to support the amendment of the
current Terminal Visual Flight Rule (VFR) Radar Service Area (TRSA) and
to allow for a lower vectoring altitude known as the Minimum Vectoring
Altitude (MVA) for vectoring of both VFR and Instrument Flight Rule
(IFR) aircraft around the Rome, NY area. This action would enhance the
safety and airspace management around the Griffiss Airport area.

DATES: Comments must be received on or before June 23, 2008.

ADDRESSES: Send comments on this rule to: U.S. Department of
Transportation, Docket Operations, West Building Ground Floor, Room
W12-140, 1200 New Jersey, SE., Washington, DC 20590-0001; Telephone: 1-
800-647-5527; Fax:<PHONE_NUMBER>. You must identify the Docket Number
FAA-2008-0308; Airspace Docket No. 08-AEA-19, at the beginning of your
comments. You may also submit and review received comments through the
Internet at http://www.regulations.gov.
    You may review the public docket containing the rule, any comments
received, and any final disposition in person in the Dockets Office
(see ADDRESSES section for address and phone number) between 9 a.m. and
5 p.m., Monday through Friday, except Federal holidays.
    An informal docket may also be examined during normal business
hours at the office of the Eastern Service Center, Federal Aviation
Administration, Room 210, 1701 Columbia Avenue, College Park, Georgia
30337.

FOR FURTHER INFORMATION CONTACT: Daryl Daniels, Airspace Specialist,
System Support Group, Eastern Service Center, Air Traffic Organization,
Federal Aviation Administration, P.O. Box 20636, Atlanta, Georgia
30320; telephone<PHONE_NUMBER>.

SUPPLEMENTARY INFORMATION:

Comments Invited

    Interested persons are invited to comment on this rule by
submitting such written data, views, or arguments, as they may desire.
Comments that provide the factual basis supporting the views and
suggestions presented are particularly helpful in developing reasoned
regulatory decisions on the proposal. Comments are specifically invited
on the overall regulatory, aeronautical, economic, environmental, and
energy-related aspects of the proposal. Communications should identify
both docket numbers and be submitted in triplicate to the address
listed above. Those wishing the FAA to acknowledge receipt of their
comments on this notice must submit with those comments a self-
addressed, stamped postcard on which the following statement is made:
``Comments to Docket No. FAA-2008-0308; Airspace Docket No. 08-AEA-
19.'' The postcard will be date/time stamped and returned to the
commenter. All communications received before the specified closing
date for comments will be considered before taking action on the
proposed rule. The proposal contained in this notice may be changed in
light of the comments received. A report summarizing each substantive
public contact with FAA personnel concerned with this rulemaking will
be filed in the docket.

Availability of NPRMs

    An electronic copy of this document may be downloaded from and
comments submitted through http://www.regulations.gov. Recently
published rulemaking documents can also be accessed through the FAA's
Web page at http://www.faa.gov or the Federal Register's Web page at
http://www.gpoaccess.gov/fr/index.html. Persons interested in being
placed on a mailing list for future NPRM's should contact the FAA's
Office of Rulemaking,<PHONE_NUMBER>, to request a copy of Advisory
Circular No. 11-2A, Notice of Proposed Rulemaking Distribution System,
which describes the application procedure.

The Proposal

    The FAA is considering an amendment to Part 71 of the Code of
Federal Regulations (14 CFR Part 71) to modify Class E airspace at
Rome, NY. On January 1, 2007, the Oneida County Airport, Utica, NY was
permanently closed and operations moved to the Griffiss Airfield.
Airspace in this area was modified as published in the Federal Register
on September 7, 2007 (72 FR 51357). Analysis of operations has
determined that there is a need for additional Class E5 airspace
extending upward from 700 feet above the surface of the Earth to
enhance the management, safety and efficiency of air traffic services
in the area. The local area Terminal VFR Radar Service Area (TRSA) is
being revised and there is a requirement for the base of the TRSA to
not be below the associated Class E airspace. This modification would
satisfy that requirement. Class E airspace designations for airspace
areas extending upward from 700 feet or more above the surface of the
Earth are published in Paragraph 6005 of FAA Order 7400.9R, signed
August 15, 2007, and effective September 15, 2007, which is
incorporated by reference in 14 CFR 71.1. The Class E airspace
designation listed in this document would be published subsequently in
the Order.
    The FAA has determined that this proposed 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 will only affect air traffic
procedures and air navigation, it is certified that this proposed rule,
when promulgated, will not have a significant economic impact on a
substantial number of small entities under the criteria of the
Regulatory Flexibility Act.
    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 proposes to modify Class E airspace at Rome, NY.

List of Subjects in 14 CFR Part 71

    Airspace, Incorporation by reference, Navigation (Air).

The Proposed Amendment

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

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

    1. The authority citation for part 71 will continue to read as
follows:

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

Sec.  71.1  [Amended]

    2. The incorporation by reference in 14 CFR 71.1 of Federal
Aviation Administration Order 7400.9R, Airspace Designations and
Reporting Points, signed August 15, 2007, effective September 15, 2007,
is proposed to be amended as follows:

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

* * * * *

AEA NY E5 Rome, NY [Revised]

Griffiss Airfield, NY
    (Lat. 43[deg]14'02'' N, long. 75[deg]24'25'' W)

    That airspace extending upward from 700 feet above the surface
of the Earth within a 15-mile radius of Griffiss Airfield and within
a 26-mile radius of the airport extending clockwise from a 125[deg]
bearing to a 200[deg] bearing from the airport.
* * * * *

    Issued in College Park, Georgia, on April 22, 2008.
Lynda G. Otting,
Acting Manager, System Support Group, Eastern Service Center, Air
Traffic Organization.
[FR Doc. E8-9852 Filed 5-7-08; 8:45 am]

BILLING CODE 4910-13-M


[Federal Register Volume 78, Number 146 (Tuesday, July 30, 2013)]
[Notices]
[Pages 45919-45920]
[FR Doc No: 2013-18208]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Docket No. IC13-14-000]

Commission Information Collection Activities (FERC Form 80);
Comment Request; Extension

AGENCY: Federal Energy Regulatory Commission.

ACTION: Comment request.

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

SUMMARY: In compliance with the requirements of the Paperwork Reduction
Act of 1995, 44 U.S.C. 3507(a)(1)(D), the Federal Energy Regulatory
Commission (Commission or FERC) is submitting the information
collection, FERC Form 80, Licensed Hydropower Development Recreation
Report, to the Office of Management and Budget (OMB) for review of the
information collection requirements. Any interested person may file
comments directly with OMB and should address a copy of those comments
to the Commission as explained below. The Commission issued a Notice in
the Federal Register (78 FR 28820, 5/16/2013) requesting public
comments. FERC received no comments on the FERC Form 80 and is making
this notation in its submittal to OMB.

DATES: Comments on the collection of information are due August 29,
2013.

ADDRESSES: Comments filed with OMB, identified by the OMB Control No.
1902-0106, should be sent via email to the Office of Information and
Regulatory Affairs<EMAIL_ADDRESS>Attention: Federal Energy
Regulatory Commission Desk Officer. The Desk Officer may also be
reached via telephone at<PHONE_NUMBER>.
    A copy of the comments should also be sent to the Federal Energy
Regulatory Commission, identified by the Docket No. IC13-14-000, by
either of the following methods:
     eFiling at Commission's Web site: http://www.ferc.gov/docs-filing/efiling.asp
     Mail/Hand Delivery/Courier: Federal Energy Regulatory
Commission, Secretary of the Commission, 888 First Street NE.,
Washington, DC 20426.
    Instructions: All submissions must be formatted and filed in
accordance with submission guidelines at: http://www.ferc.gov/help/submission-guide.asp. For user assistance contact FERC Online Support
by email at<EMAIL_ADDRESS>or by phone at:<PHONE_NUMBER>
(toll-free), or<PHONE_NUMBER> for TTY.
    Docket: Users interested in receiving automatic notification of
activity in this docket or in viewing/downloading comments and
issuances in this docket may do so at http://www.ferc.gov/docs-filing/docs-filing.asp.

FOR FURTHER INFORMATION CONTACT: Ellen Brown may be reached by email at
<EMAIL_ADDRESS>telephone at<PHONE_NUMBER>, and fax at (202)
273-0873.

SUPPLEMENTARY INFORMATION:
    Title: FERC Form 80, Licensed Hydropower Development Recreation
Report.
    OMB Control No.: 1902-0106.
    Type of Request: Minor revisions to the FERC Form 80 information
collection requirements with no change to the current reporting burden.
    Abstract: FERC uses the information on the FERC Form 80 to
implement the statutory provisions of sections 4(a), 10(a), 301(a), 304
and 309 of the Federal Power Act (FPA), 16 U.S.C. 797, 803, 825c &
8254. FERC's authority to collect this information comes from section
10(a) of the FPA which requires the Commission to be responsible for
ensuring that hydro projects subject to FERC jurisdiction are
consistent with the comprehensive development of the nation's waterway
for recreation and other beneficial public uses. In the interest of
fulfilling these objectives, FERC expects licensees subject to its
jurisdiction to recognize the resources that are affected by their
activities and to play a role in protecting such resources.
    FERC Form 80 is a report on the use and development of recreational
facilities at hydropower projects licensed by the Commission.
Applications for licenses, amendments to licenses, and/or changes in
land rights frequently involve changes in resources available for
recreation. FERC utilizes the FERC Form 80 data when analyzing the
adequacy of existing public recreational facilities and when processing
and reviewing proposed amendments to help determine the impact of such
changes. In addition, the FERC regional office staff uses the FERC Form
80 data when conducting inspections of licensed projects. FERC
inspectors use the data in evaluating compliance with various license
conditions and in identifying recreational facilities at hydropower
projects.
    The FERC Form 80 requires data specified by Title 18 of the Code of
Federal Regulations (CFR) under Parts 8.11 and 141.14 (and discussed at
http://www.ferc.gov/docs-filing/forms.asp#80).
    FERC collects the FERC Form 80 once every six years. The last
collection was due on April 1, 2009, for data compiled during the 2008
calendar year. The next collection of the FERC Form 80 is due on April
1, 2015, with subsequent collections due every sixth year, for data
compiled during the previous calendar year.
    The Commission made minor revisions throughout the form.
Specifically, FERC clarified and simplified instructions, removed
redundancy in certain questions, clarified questions and terms, and
generally improved the readability of the form.
    FERC has attached the revised form to this notice.

    Type of Respondents: Hydropower project licensees.
    Estimate of Annual Burden:\1\ For each reporting period, FERC
estimates the total Public Reporting Burden for this information
collection as: (a) 1,000 respondents, (b) 0.167 responses/respondent,
and (c) 3 hours per response, giving a total of 501 burden hours. The
Commission has increased its total number of respondents to reflect the
actual numbers we received during the last two reporting periods. In
addition, FERC spreads the burden hours and costs over the six-year
collection cycle in the table below to reflect how the information is
collected. The average burden hours per response remains unchanged.
These are the figures FERC will submit to OMB.
---------------------------------------------------------------------------

    \1\ FERC defines burden as the total time, effort, or financial
resources expended by persons to generate, maintain, retain, or
disclose or provide information to or for a Federal agency. For
further explanation of what is included in the information
collection burden, reference 5 Code of Federal Regulations 1320.3.

                           FERC-80--Licensed Hydropower Development Recreation Report
----------------------------------------------------------------------------------------------------------------
                        Number of responses      Total number of      Average burden hours     Estimated total
Number of respondents    per respondent \2\         responses             per response          annual burden
(A)                                  (B)          (A) x (B) = (C)                  (D)                      (C)
----------------------------------------------------------------------------------------------------------------
            1,000                  0.167                    167                      3                    501
----------------------------------------------------------------------------------------------------------------

    The total estimated annual cost burden to respondents is $35,070
[501 hours * $70/hour \3\ = $35,070].
---------------------------------------------------------------------------

    \2\ FERC divides the responses per respondent by six because
this collection occurs once every six years.
    \3\ FY 2013 Estimated Average Hourly Cost per FTE, including
salary + benefits.
---------------------------------------------------------------------------

    Comments: The Commission invites comments on: (1) Whether the
collection of information is necessary for the proper performance of
the functions of the Commission, including whether the information will
have practical utility; (2) the accuracy of the agency's estimate of
the burden and cost of the collection of information, including the
validity of the methodology and assumptions used; (3) ways to enhance
the quality, utility and clarity of the information collection; and (4)
ways to minimize the burden of the collection of information on those
who are to respond, including the use of automated collection
techniques or other forms of information technology.

    Dated: July 23, 2013.
Kimberly D. Bose,
Secretary.
[FR Doc. 2013-18208 Filed 7-29-13; 8:45 am]
BILLING CODE 6717-01-P


[Federal Register Volume 81, Number 233 (Monday, December 5, 2016)]
[Notices]
[Pages 87572-87575]
[FR Doc No: 2016-29028]

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

DEPARTMENT OF HEALTH AND HUMAN SERVICES

Food and Drug Administration

[Docket No. FDA-2016-N-2544]

Agency Information Collection Activities; Submission for Office
of Management and Budget Review; Comment Request; Medical Device:
Current Good Manufacturing Practice Quality System Regulations

AGENCY: Food and Drug Administration, HHS.

ACTION: Notice.

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

SUMMARY: The Food and Drug Administration (FDA) is announcing that a
proposed collection of information has been submitted to the Office of
Management and Budget (OMB) for review and clearance under the
Paperwork Reduction Act of 1995.

DATES: Fax written comments on the collection of information by January
4, 2017.

ADDRESSES: To ensure that comments on the information collection are
received, OMB recommends that written comments be faxed to the Office
of Information and Regulatory Affairs, OMB, Attn: FDA Desk Officer,
FAX:<PHONE_NUMBER>, or emailed to<EMAIL_ADDRESS>All
comments should be identified with the OMB control number 0910-0073.
Also include the FDA docket number found in brackets in the heading of
this document.

FOR FURTHER INFORMATION CONTACT: FDA PRA Staff, Office of Operations,
Food and Drug Administration, Three White Flint North, 10A63, 11601
Landsdown St., North Bethesda, MD 20852<EMAIL_ADDRESS>
SUPPLEMENTARY INFORMATION: In compliance with 44 U.S.C. 3507, FDA has
submitted the following proposed collection of information to OMB for
review and clearance.

Medical Device: Current Good Manufacturing Practice Quality System
Regulations-- OMB Control Number 0910-0073--Extension

    Under section 520(f) of the Federal Food, Drug, and Cosmetic Act
(the FD&C Act) (21 U.S.C. 360j(f)), the Secretary of the Department of
Health and Human Services has the authority to prescribe regulations
requiring that the methods used in, and the facilities and controls
used for, the manufacture, preproduction design validation (including a
process to assess the performance of a device, but not including an
evaluation of the safety and effectiveness of a device), packing,
storage, and installation of a device conform to Current Good
Manufacturing Practice (CGMP), as described in such regulations, to
assure that the device will be safe and effective and otherwise in
compliance with the FD&C Act.
    The CGMP/Quality System (QS) regulation implementing authority
provided by this statutory provision is found under part 820 (21 CFR
part 820) and sets forth basic CGMP requirements governing the design,
manufacture, packing, labeling, storage, installation, and servicing of
all finished medical devices intended for human use. The authority for
this regulation is covered under sections 501, 502, 510, 513, 514, 515,
518, 519, 520, 522, 701, 704, 801, and 803 of the FD&C Act (21 U.S.C.
351, 352, 360, 360c, 360d, 360e, 360h, 360i, 360j, 360l, 371, 374, 381,
and 383). The CGMP/QS regulation includes requirements for purchasing
and service controls, clarifies recordkeeping requirements for device
failure and complaint investigations, clarifies requirements for
verifying/validating production processes and process or product
changes, and clarifies requirements for product acceptance activities
quality data evaluations and corrections of nonconforming product/
quality problems.
    Requirements are compatible with specifications in the
international standards ``ISO 9001: Quality Systems Model for Quality
Assurance in Design/Development, Production, Installation, and
Servicing.'' The CGMP/QS information collections will assist FDA
inspections of manufacturers for compliance with QS requirements
encompassing design, production, installation, and servicing processes.
    Section 820.20(a) through (e) requires management with executive
responsibility to establish, maintain, and/or review the following
topics: (1) The quality policy, (2) the organizational structure, (3)
the quality plan, and (4) the quality system procedures of the
organization. Section 820.22 requires the conduct and documentation of
QS audits and re-audits. Section 820.25(b) requires the establishment
of procedures to identify training needs and documentation of such
training.
    Section 820.30(a)(1) and (b) through (j) requires, in respective
order, the establishment, maintenance, and/or documentation of the
following topics: (1) Procedures to control design of class III and
class II devices and certain class I devices as listed therein; (2)
plans for design and development activities and updates; (3) procedures
identifying, documenting, and approving design input requirements; (4)
procedures defining design output, including acceptance criteria, and
documentation of approved records; (5) procedures for formal review of
design results and documentation of results in the design history file
(DHF); (6) procedures for verifying device design and documentation of
results and approvals in the DHF; (7) procedures for validating device
design, including documentation of results in the DHF; (8) procedures
for translating device design into production specifications; (9)
procedures for documenting, verifying, and validating approved design
changes before implementation of changes; and (10) the records and
references constituting the DHF for each type of device.
    Section 820.40 requires manufacturers to establish and maintain
procedures controlling approval and distribution of required documents
and document

changes. Section 820.40(a) and (b) requires the establishment and
maintenance of procedures for the review, approval, issuance, and
documentation of required records (documents) and changes to those
records.
    Section 820.50(a) and (b) requires the establishment and
maintenance of procedures and requirements to ensure service and
product quality, records of acceptable suppliers, and purchasing data
describing specified requirements for products and services.
    Sections 820.60 and 820.65 require, respectively, the establishment
and maintenance of procedures for identifying all products from receipt
to distribution and for using control numbers to track surgical
implants and life-sustaining or supporting devices and their
components.
    Section 820.70(a) through (e), (g)(1) through (g)(3), (h), and (i)
requires the establishment, maintenance, and/or documentation of the
following topics: (1) Process control procedures; (2) procedures for
verifying or validating changes to specification, method, process, or
procedure; (3) procedures to control environmental conditions and
inspection result records; (4) requirements for personnel hygiene; (5)
procedures for preventing contamination of equipment and products; (6)
equipment adjustment, cleaning, and maintenance schedules; (7)
equipment inspection records; (8) equipment tolerance postings,
procedures for utilizing manufacturing materials expected to have an
adverse effect on product quality; and (9) validation protocols and
validation records for computer software and software changes.
    Sections 820.72(a), (b)(1), and (b)(2); and 820.75(a) through (c)
require, respectively, the establishment, maintenance, and/or
documentation of the following topics: (1) Equipment calibration and
inspection procedures; (2) national, international, or in-house
calibration standards; (3) records that identify calibrated equipment
and next calibration dates; (4) validation procedures and validation
results for processes not verifiable by inspections and tests; (5)
procedures for keeping validated processes within specified limits; (6)
records for monitoring and controlling validated processes; and (7)
records of the results of revalidation where necessitated by process
changes or deviations.
    Sections 820.80(a) through (e) and 820.86, respectively, require
the establishment, maintenance, and/or documentation of the following
topics: (1) Procedures for incoming acceptance by inspection, test, or
other verification; (2) procedures for ensuring that in process
products meet specified requirements and the control of product until
inspection and tests are completed; (3) procedures for, and records
that show, incoming acceptance or rejection is conducted by
inspections, tests or other verifications; (4) procedures for, and
records that show, finished devices meet acceptance criteria and are
not distributed until device master record (DMR) activities are
completed; (5) records in the device history record (DHR) showing
acceptance dates, results, and equipment used; and (6) the acceptance/
rejection identification of products from receipt to installation and
servicing.
    Sections 820.90(a), (b)(1), and (b)(2) and 820.100 require,
respectively, the establishment, maintenance and/or documentation of
the following topics: (1) Procedures for identifying, recording,
evaluating, and disposing of nonconforming product; (2) procedures for
reviewing and recording concessions made for, and disposition of,
nonconforming product; (3) procedures for reworking products,
evaluating possible adverse rework effect and recording results in the
DHR; (4) procedures and requirements for corrective and preventive
actions, including analysis, investigation, identification and review
of data, records, causes, and results; and (5) records for all
corrective and preventive action activities.
    Section 820.100(a)(1) through (a)(7) states that procedures and
requirements shall be established and maintained for corrective/
preventive actions, including the following: (1) Analysis of data from
process, work, quality, servicing records, investigation of
nonconformance causes; (2) identification of corrections and their
effectiveness; (3) recording of changes made; and (4) appropriate
distribution and managerial review of corrective and preventive action
information. Section 820.120 states that manufacturers shall establish/
maintain procedures to control labeling storage/application; and
examination/release for storage and use, and document those procedures.
    Sections 820.120(b) and (d); 820.130; 820.140; 820.150(a) and (b);
820.160(a) and (b); and 820.170(a) and (b), respectively, require the
establishment, maintenance, and/or documentation of the following
topics: (1) Procedures for controlling and recording the storage,
examination, release, and use of labeling; (2) the filing of labels/
labeling used in the DHR; (3) procedures for controlling product
storage areas and receipt/dispatch authorizations; (4) procedures
controlling the release of products for distribution; (5) distribution
records that identify consignee, product, date, and control numbers;
and (6) instructions, inspection and test procedures that are made
available, and the recording of results for devices requiring
installation.
    Sections 820.180(b) and (c); 820.181(a) through (e); 820.184(a)
through (f); and 820.186 require, respectively, the maintenance of
records that are: (1) Retained at prescribed site(s), made readily
available and accessible to FDA, and retained for the device's life
expectancy or for 2 years; (2) contained or referenced in a DMR
consisting of device, process, quality assurance, packaging and
labeling, and installation, maintenance, and servicing specifications
and procedures; (3) contained in a DHR and demonstrate the manufacture
of each unit, lot, or batch of product in conformance with DMR and
regulatory requirements include manufacturing and distribution dates,
quantities, acceptance documents, labels and labeling, and control
numbers; and (4) contained in a quality system record, consisting of
references, documents, procedures, and activities not specific to
particular devices.
    Sections 820.198(a) through (c); and 820.200(a) through (d),
respectively, require the establishment, maintenance, and/or
documentation of the following topics: (1) Complaint files and
procedures for receiving, reviewing, and evaluating complaints; (2)
complaint investigation records identifying the device, complainant,
and relationship of the device to the incident; (3) complaint records
that are reasonably accessible to the manufacturing site or at
prescribed sites; (4) procedures for performing and verifying that
device servicing requirements are met and that service reports
involving complaints are processed as complaints; and (5) service
reports that record the device, service activity, and test and
inspection data.
    Section 820.250 requires the establishment and maintenance of
procedures to identify valid statistical techniques necessary to verify
process and product acceptability; and sampling plans, when used, which
are written and based on valid statistical rationale; and procedures
for ensuring adequate sampling methods.
    The CGMP/QS regulation added design and purchasing controls,
modified previous critical device requirements, revised previous
validation and other requirements, and harmonized device CGMP
requirements with QS specifications in the international standard ``ISO
9001: Quality Systems Model for Quality

Assurance in Design/Development, Production, Installation, and
Servicing.'' The rule does not apply to manufacturers of components or
parts of finished devices, or to manufacturers of human blood and blood
components subject to 21 CFR part 606. With respect to devices
classified in class I, design control requirements apply only to class
I devices listed in Sec.  820.30(a)(2) of the regulation. The rule
imposes burden upon: (1) Finished device manufacturer firms, which are
subject to all recordkeeping requirements; (2) finished device contract
manufacturers, specification developers; and (3) re-packer, re-
labelers, and contract sterilizer firms, which are subject only to
requirements applicable to their activities. In addition,
remanufacturers of hospital single-use devices are now considered to
have the same requirements as manufacturers in regard to the
regulation.
    The establishment, maintenance, and/or documentation of procedures,
records, and data required by the regulation assists FDA in determining
whether firms are in compliance with CGMP requirements, which are
intended to ensure that devices meet their design, production,
labeling, installation, and servicing specifications and, thus are
safe, effective, and suitable for their intended purpose. In
particular, compliance with CGMP design control requirements should
decrease the number of design-related device failures that have
resulted in deaths and serious injuries.
    The CGMP/QS regulation applies to approximately 24,738 respondents.
A query of the Agency's registration and listing database shows that
approximately 13,294 domestic and 11,444 foreign establishments are
respondents to this information collection.\1\ Respondents to this
collection have no reporting activities, but must make required records
available for review or copying during FDA inspection. Except for
manufacturers, not every type of firm is subject to every CGMP/QS
requirement. For example, all are subject to Quality Policy (Sec.
820.20(a)), Document Control (Sec.  820.40), and other requirements,
whereas only manufacturers and specification developers are subject to
subpart C, Design Controls. The Paperwork Reduction Act burden placed
on the 24,738 establishments is an average burden.
---------------------------------------------------------------------------

    \1\ Based on fiscal year 2015 data.
---------------------------------------------------------------------------

    In the Federal Register of September 8, 2016 (81 FR 62144), FDA
published a 60-day notice requesting public comment on the proposed
collection of information. No comments were received.
    FDA estimates the burden of this collection of information as
follows:

                               Table 1--Estimated Annual Recordkeeping Burden \1\
----------------------------------------------------------------------------------------------------------------
                                                         Number of                    Average burden
       Activity/21 CFR section           Number of      records per    Total annual         per          Total
                                       recordkeepers   recordkeeper       records      recordkeeping     hours
----------------------------------------------------------------------------------------------------------------
Quality policy--820.20(a)...........          24,738               1          24,738               7     173,166
Organization--820.20(b).............          24,738               1          24,738               4      98,952
Management review--820.20(c)........          24,738               1          24,738               6     148,428
Quality planning--820.20(d).........          24,738               1          24,738              10     247,380
Quality system procedures--820.20(e)          24,738               1          24,738              10     247,380
Quality audit--820.22...............          24,738               1          24,738              33     816,354
Training--820.25(b).................          24,738               1          24,738              13     321,594
Design procedures--820.30(a)(1).....          24,738               1          24,738               2      49,476
Design and development planning--             24,738               1          24,738               6     148,428
 820.30(b)..........................
Design input--820.30(c).............          24,738               1          24,738               2      49,476
Design output--820.30(d)............          24,738               1          24,738               2      49,476
Design review--820.30(e)............          24,738               1          24,738              23     568,974
Design verification--820.30(f)......          24,738               1          24,738              37     915,306
Design validation--820.30(g)........          24,738               1          24,738              37     915,306
Design transfer--820.30(h)..........          24,738               1          24,738               3      74,214
Design changes--820.30(i)...........          24,738               1          24,738              17     420,546
Design history file--820.30(j)......          24,738               1          24,738               3      74,214
Document controls--820.40...........          24,738               1          24,738               9     222,642
Documentation approval and                    24,738               1          24,738               2      49,476
 distribution and document changes--
 820.40(a) and (b)..................
Purchasing controls--820.50(a)......          24,738               1          24,738              22     544,236
Purchasing data--820.50(b)..........          24,738               1          24,738               6     148,428
Identification--820.60..............          24,738               1          24,738               1      24,738
Traceability--820.65................          24,738               1          24,738               1      24,738
Production and process controls--             24,738               1          24,738               2      49,476
 820.70(a)..........................
Production and process changes and            24,738               1          24,738               2      49,476
 environmental control--820.70(b)
 and (c)............................
Personnel--820.70(d)................          24,738               1          24,738               3      74,214
Contamination control--820.70(e)....          24,738               1          24,738               2      49,476
Equipment maintenance schedule,               24,738               1          24,738               1      24,738
 inspection, and adjustment--
 820.70(g)(1)-(g)(3)................
Manufacturing material--820.70(h)...          24,738               1          24,738               2      49,476
Automated processes--820.70(i)......          24,738               1          24,738               8     197,904
Control of inspection, measuring,             24,738               1          24,738               5     123,690
 and test equipment--820.72(a)......
Calibration procedures, standards,            24,738               1          24,738               1      24,738
 and records--820.72(b)(1)-(b)(2)...
Process validation--820.75(a).......          24,738               1          24,738               3      74,214
Validated process parameters,                 24,738               1          24,738               1      24,738
 monitoring, control methods, and
 data--820.75(b)....................
Revalidation--820.75(c).............          24,738               1          24,738               1      24,738

Acceptance activities--820.80(a)-(e)          24,738               1          24,738               5     123,690
Acceptance status--820.86...........          24,738               1          24,738               1      24,738
Control of nonconforming product--            24,738               1          24,738               5     123,690
 820.90(a)..........................
Nonconforming product review/                 24,738               1          24,738               5     123,690
 disposition procedures and rework
 procedures--820.90(b)(1)-(b)(2)....
Procedures for corrective/preventive          24,738               1          24,738              12     296,856
 actions--820.100(a)(1)-(a)(7)......
Corrective/preventive activities--            24,738               1          24,738               1      24,738
 820.100(b).........................
Labeling procedures--820.120(b).....          24,738               1          24,738               1      24,738
Labeling documentation--820.120(d)..          24,738               1          24,738               1      24,738
Device packaging--820.130...........          24,738               1          24,738               1      24,738
Handling--820.140...................          24,738               1          24,738               6     148,428
Storage--820.150(a) and (b).........          24,738               1          24,738               6     148,428
Distribution procedures and records--         24,738               1          24,738               1      24,738
 820.160(a) and (b).................
Installation--820.170...............          24,738               1          24,738               2      49,476
Record retention period--820.180(b)           24,738               1          24,738               2      49,476
 and (c)............................
Device master record--820.181.......          24,738               1          24,738               1      24,738
Device history record--820.184......          24,738               1          24,738               1      24,738
Quality system record--820.186......          24,738               1          24,738               1      24,738
Complaint files--820.198(a), (c),             24,738               1          24,738               5     123,690
 and (g)............................
Servicing procedures and reports--            24,738               1          24,738               3      74,214
 820.200(a) and (d).................
Statistical techniques procedures             24,738               1          24,738               1      24,738
 and sampling plans--820.250........
                                     ---------------------------------------------------------------------------
    Total...........................  ..............  ..............  ..............  ..............   8,608,824
----------------------------------------------------------------------------------------------------------------
\1\ There are no capital costs or operating and maintenance costs associated with this collection of
  information.

    Dated: November 28, 2016.
Leslie Kux,
Associate Commissioner for Policy.
[FR Doc. 2016-29028 Filed 12-2-16; 8:45 am]
 BILLING CODE 4160-01-P


[Federal Register Volume 82, Number 203 (Monday, October 23, 2017)]
[Notices]
[Pages 49050-49054]
[FR Doc No: 2017-22883]

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

SECURITIES AND EXCHANGE COMMISSION

[Release No. 34-81888; File No. SR-NYSEArca-2017-118]

Self-Regulatory Organizations; NYSE Arca, Inc.; Notice of Filing
and Immediate Effectiveness of Proposed Rule Change To Amend Rule
6.76A-O To Adopt Additional Self-Trade Prevention Modifiers

October 17, 2017.
    Pursuant to Section 19(b)(1) \1\ of the Securities Exchange Act of
1934 (the ``Act''),\2\ and Rule 19b-4 thereunder,\3\ notice is hereby
given that on October 3, 2017, NYSE Arca, Inc. (the ``Exchange'' or
``NYSE Arca'') filed with the Securities and Exchange Commission (the
``Commission'') the proposed rule change as described in Items I and II
below, which Items have been prepared by the self-regulatory
organization. The Commission is publishing this notice to solicit
comments on the proposed rule change from interested persons.
---------------------------------------------------------------------------

    \1\ 15 U.S.C. 78s(b)(1).
    \2\ 15 U.S.C. 78a.
    \3\ 17 CFR 240.19b-4.
---------------------------------------------------------------------------

I. Self-Regulatory Organization's Statement of the Terms of the
Substance of the Proposed Rule Change

    The Exchange proposes to amend Rule 6.76A-O (Order Execution--OX).
The proposed rule change is available on the Exchange's Web site at
www.nyse.com, at the principal office of the Exchange, and at the
Commission's Public Reference Room.

II. Self-Regulatory Organization's Statement of the Purpose of, and
Statutory Basis for, the Proposed Rule Change

    In its filing with the Commission, the self-regulatory organization
included statements concerning the purpose of, and basis for, the
proposed rule change and discussed any comments it received on the
proposed rule change. The text of those statements may be examined at
the places specified in Item IV below. The Exchange has prepared
summaries, set forth in sections A, B, and C below, of the most
significant parts of such statements.

A. Self-Regulatory Organization's Statement of the Purpose of, and
Statutory Basis for, the Proposed Rule Change

1. Purpose
    The purpose of the filing is to amend Commentary .01 to NYSE Arca
Rule 6.76A-O (Order Execution--OX) regarding the Exchange's Self-Trade
Prevention (``STP'') functionality.\4\ The Exchange currently offers a
basic form of self-trade prevention \5\ pursuant to which the Exchange
cancels any resting Market Maker quote(s) and order(s) \6\ to buy
(sell) that are priced equal to or higher (lower) than an incoming
Market Maker quote, order or both to sell (buy) entered under the same
trading permit identification (``TPID'').\7\
---------------------------------------------------------------------------

    \4\ Self-Trade Prevention is only applicable to electronic
trading on the Exchange.
    \5\ See Securities Exchange Act Release No. 66386 (February 13,
2012), 77 FR 9721 (February 17, 2012) (SR-NYSEArca-2012-08).
    \6\ Self-Trade Prevention currently is applicable to the
following order types used by Market Makers: ``PNP Orders,'' ``PNP-
Blind Orders,'' and ``PNP-Light Orders.'' PNP Orders, PNP-Blind
Orders, and PNP-Light Orders are defined in NYSE Arca Rule 6.62-O,
and each is a type of non-routable Limit Order that is only executed
on the Exchange. The Exchange notes that Market Makers primarily use
these order types, as opposed to other order types offered by the
Exchange, because they are similar to quotes (i.e., they are non-
routable Limit Orders). See Regulatory Information Bulletin RBO-12-
04 at https://www.nyse.com/publicdocs/nyse/markets/arca-options/rule-interpretations/2012/NYSEArca%20RBO-12-04.pdf.
    \7\ The Exchange uses a Market Maker's TPID to monitor for self-
trades. TPIDs are assigned to Market Makers, as well as other OTP
Firms and OTP Holders, to identify them in the Exchange's systems.
Market Makers on the Exchange are not able to submit orders on an
agency basis. Thus, a Market Maker within a firm that conducts both
an agency and market making business has a unique TPID that could
only be used for that Market Maker's quotes and orders.
---------------------------------------------------------------------------

    The Exchange proposes to expand the self-trade functionality by
adopting three STP modifiers. The proposed STP modifiers are designed
to prevent incoming Market Maker order(s) or quote(s) designated with
an STP

modifier from executing against an opposite side resting Market Maker
order(s) or quote(s) also designated with an STP modifier and entered
from the same TPID. As proposed, the STP modifier on the incoming
Market Maker order or quote would control the interaction between two
orders and/or quotes marked with STP modifiers. The proposed STP
modifiers are intended to prevent interaction between the same TPIDs.
STP modifiers must be present on both the buy and the sell interest in
order to prevent an interaction from occurring and to effect a cancel
instruction.
    The Exchange believes the proposed functionality will allow OTP
Holders to better manage order flow and prevent undesirable or
unexpected executions with themselves. Given enhancements in technology
in today's trading environment, OTP Holders often have multiple
connections into the Exchange. Orders, for example, routed by the same
OTP Holder via different connections may, in certain circumstances,
trade against each other. The proposed STP modifiers would provide OTP
Holders the opportunity to prevent these potentially undesirable
interactions occurring under the same TPID on both the buy and sell
side of an execution.
    The three new STP modifiers are discussed more thoroughly below.
STP Cancel Newest (``STPN'')
    An incoming order or quote marked with the STPN modifier will not
execute against opposite side resting interest marked with any STP
modifier from the same TPID. The incoming order or quote marked with
the STPN modifier will be cancelled back to the originating TPID. The
resting order(s) or quote(s) will remain on the Consolidated Book.
    STPN Example 1: Market Maker 1 is configured for one of the three
proposed STP modifiers and submits a quote to sell 100 contracts @
$5.50. A Customer order to sell 5 contracts @ $5.49 is resting on the
Consolidated Book. Market Maker 1 enters an order to buy 100 contracts
@ $5.60 with an STPN modifier.
    STPN Result 1: Market Maker 1 buys 5 contracts @ $5.49 because
Market Maker 1 has no interest at $5.49. The remaining quantity of
Market Maker 1's order will be cancelled due to Market Maker 1's quote
at $5.50.
    STPN Example 2: Market Maker 1 is configured for one of the three
proposed STP modifiers and submits a quote to sell 100 contracts @
$5.50. A Customer order to sell 5 contracts @ $5.50 is resting on the
Consolidated Book. Market Maker 1 enters an order to buy 200 contracts
@ $5.60 with an STPN modifier.
    STPN Result 2: Market Maker 1's entire order to buy 200 contracts
is cancelled due to Market Maker 1's quote at $5.50. No execution with
any other interest at $5.50 occurs.
STP Cancel Oldest (``STPO'')
    An incoming order or quote marked with the STPO modifier will not
execute against opposite side resting interest market with any STP
modifier from the same TPID. The resting order(s) or quote(s) marked
with the STP modifier will be cancelled back to the originating TPID.
The incoming order or quote marked with the STPO modifier will remain
on the Consolidated Book.
    STPO Example 1: Market Maker 1 is configured for one of the three
proposed STP modifiers and submits a quote to sell 100 contracts @
$5.50. Market Maker 1 enters an order to buy 100 contracts @ $5.50 with
an STPO modifier.
    STPO Result 1: Market Maker 1's buy order cannot trade with Market
Maker 1's quote because the buy order is marked for STP and the quotes
are configured for STP. Market Maker 1's quote to sell is cancelled and
removed from the Consolidated Book. Market Maker 1's buy order will
post to the Consolidated Book at $5.50.
    STPO Example 2: Market Maker 1 has a resting order on the
Consolidated Book to sell 10 contracts @ $5.51 with an STPN modifier.
Market Maker 1 is configured for one of the three proposed STP
modifiers and submits a quote to sell 100 contracts @ $5.50. Customer 1
has an order to sell 5 contracts @ $5.50 resting on the Consolidated
Book. Customer 2 has an order to sell 10 contracts @ $5.51 resting on
the Consolidated Book. Market Maker 1 enters an order to buy 100
contracts @ $5.51 with an STPO modifier.
    STPO Result 2: Market Maker 1's buy order cannot trade with Market
Maker 1's quote because the buy order is marked for STP and the quotes
are configured for STP. Market Maker 1's quote to sell 100 contracts @
$5.50 is cancelled and removed from the Consolidated Book. Market Maker
1's buy order will trade 5 contracts with Customer 1 at $5.50, leaving
95 contracts. The remaining 95 contracts will now attempt to trade at
the $5.51 price level. Market Maker 1's buy order, however, cannot
trade with Market Maker 1's resting sell order and the sell order is
therefore cancelled and removed from the Consolidated Book. Market
Maker 1's buy order will then trade 10 contracts with the Customer 2 @
$5.51. The remaining 85 contracts of Market Maker 1's buy order will
post to the Consolidated Book at $5.51.
STP Cancel Both (``STPC'')
    An incoming order or quote marked with the STPC modifier will not
execute against opposite side resting interest marked with any STP
modifier from the same TPID. The entire size of both orders and/or
quotes will be cancelled back to the originating TPID.
    STPC Example 1: Market Maker 1 is configured for one of the three
proposed STP modifiers and submits a quote to sell 100 contracts @
$5.50. Market Maker 1 enters an order to buy 100 contracts @ $5.50 with
an STPC modifier.
    STPC Result 1: No execution occurs. Both Market Maker 1's buy order
and Market Maker 1's quote to sell are cancelled and removed from the
Consolidated Book.
    STPC Example 2: Market Maker 1 has a resting order on the
Consolidated Book to sell 10 contracts @ $5.51 with an STPN modifier.
Market Maker 1 is configured for one of the three proposed STP
modifiers and submits a quote to sell 100 contracts @ $5.50. Market
Maker 1 enters an additional order to buy 100 contracts @ $5.51 with an
STPC modifier.
    STPC Result 2: Market Maker 1's buy order cannot trade with Market
Maker 1's quote to sell 100 contracts @ $5.50 because the buy order is
marked for STP and the quotes are configured for STP. Both the Market
Maker 1 buy order and the Market Maker 1 quote to sell are cancelled
and removed from the Consolidated Book. Market Maker 1's resting sell
order to sell 10 contracts @ $5.51 is not impacted as the incoming
Market Maker 1 buy order never attempts to trade at the $5.51 price
level and therefore, Market Maker 1's resting sell order remains on the
Consolidated Book.
Additional Discussion
    As with the current functionality, the enhanced STP functionality
would be in effect throughout the trading day for all Market Makers on
the Exchange,\8\ but not during Trading Auctions.\9\ In this regard,
the Exchange believes, as it previously noted when STP was first
adopted, it is highly unlikely that a Market Maker would trade against
its own resting interest during a Trading Auction.\10\ The enhanced STP

functionality would also not apply to individual legs of Complex
Orders. As previously noted by the Exchange, senders of Complex Orders,
including Market Makers, view them as discrete orders with a desire to
execute all legs and to prevent the execution of one leg would be
contrary to the investment purpose of the Complex Order.\11\
---------------------------------------------------------------------------

    \8\ Market Markers on the Exchange would not have the ability to
deactivate Self-Trade Prevention or change any settings related to
it.
    \9\ See, e.g., NYSE Arca Rule 6.64-O.
    \10\ See supra, note 5. The Exchange also previously noted that
it would be difficult to implement STP from a technological and
operational perspective because it would require the Exchange to
cancel resting, executable Market Maker trading interest as it is
calculating the price at which to conduct the Trading Auction.
    \11\ See supra, note 5.
---------------------------------------------------------------------------

    As proposed, the enhanced STP functionality would not be applicable
to Qualified Contingent Cross (``QCC'') Orders.\12\ QCC Orders are
paired orders intended to serve a particular investment purpose that
are contingent on the options leg of a QCC Order being executed.
Because the non-execution of the options leg is contrary to the
investment purpose of a QCC Order, the Exchange has determined not to
apply STP in a manner that would prevent the execution of a QCC Order.
The Exchange notes that the enhanced STP functionality proposed herein
would not relieve or modify a Market Maker's obligations under the
Exchange's Rules, such as the Market Maker's quoting obligations, or
any other rules and regulations to which the Market Maker is subject.
---------------------------------------------------------------------------

    \12\ A QCC Order is comprised of an originating order to buy or
sell at least 1,000 contracts, or 10,000 mini-options contracts,
that is identified as being part of a qualified contingent trade, as
that term is defined in Commentary .02 to Rule 6.62-O, coupled with
a contra-side order or orders totaling an equal number of contracts.
See NYSE Arca Rule 6.62-O(bb).
---------------------------------------------------------------------------

    The enhanced STP functionality proposed herein is similar to
functionality currently offered by the Bats Exchange, Inc.
(``Bats'').\13\ In particular, Bats offers Match Trade Prevention
(``MTP''), a self-trade prevention functionality where any incoming
order designated with an MTP modifier is prevented from executing
against a resting opposite side order also designated with an MTP
modifier and originating from the same market participant identifier.
Additionally, the Exchange's equities market provides for self-trade
prevention order modifiers that prevent orders so designated from
executing against resting opposite side orders entered under the same
equity trading permit identification that are also designated with the
modifier.\14\ With two exceptions, the Exchange is proposing to adopt
all the STP modifiers that are currently available on Bats.\15\ And
with one exception, the Exchange is proposing to adopt all the STP
modifiers that are currently available on the Exchange's equities
market.\16\ The Exchange notes that while the Bats rule and the NYSE
Arca equities rule apply to orders, and not to orders and quotes, the
Exchange's proposal is otherwise similar to functionality offered on
Bats and on the Exchange's equities market.
---------------------------------------------------------------------------

    \13\ See Bats Rule 21.1(g).
    \14\ See NYSE Arca Rule 7.31-E(i)(2).
    \15\ Bats currently offers MTP Decrement and Cancel (``MDC'')
where an incoming order with the MDC modifier is prevented from
executing against opposite side resting interest marked with any MTP
modifier originating from the same user on that exchange. If both
orders are equal in size, both orders are canceled. For those not
equivalent in size, the smaller order is canceled and the larger
order is decremented by the size of the smaller order with the
balance remaining on the order book. Bats also currently offers MTP
Cancel Smallest (``MCS'') where an incoming order with the MCS
modifier is prevented from executing against opposite side resting
interest marked with any MTP modifier originating from the same
user. If both orders are equal in size, both orders are cancelled.
For those not equivalent in size, the smaller order is canceled and
the larger order remains on the book.
    \16\ The NYSE Arca equities market also currently offers STP
Decrement and Cancel (``STPD'') that provides similar self-trade
prevention functionality as the Bats offering. At this time, the
Exchange is not proposing to adopt the STPD modifier for the options
market.
---------------------------------------------------------------------------

    The NASDAQ Options Market (``NOM'') currently offers functionality
that applies to orders and quotes, but in a limited manner.\17\
Notwithstanding the fact that the STPN and STPC modifiers, as proposed
for orders and quotes, are not currently available on an options
market, the Exchange does not believe the proposed functionality is
novel and does not raise any new regulatory concerns. Further, the STP
functionality currently available on the Exchange applies to both
orders and quotes, and Market Makers are therefore generally familiar
with the application of self-trade prevention to orders and quotes. The
Exchange further believes the proposed adoption of the STPN and STPC
modifiers would add further specificity to the rule while aligning the
proposed functionality with Market Makers' expectation. Self-trade
prevention is a risk mechanism tool to prevent inadvertent trading of
both orders and quotes that has been widely used for many years in both
the equities and options markets. The enhanced functionality proposed
herein would provide Market Makers with a method of managing their
trading interest that is similar to functionality currently available
on other markets.
---------------------------------------------------------------------------

    \17\ See NOM, Chapter VI, Section 10(6). The NOM anti-
internalization (``AIQ'') functionality works similar to the
proposed STPO modifier in that quotes and orders entered by NOM
market makers using the same market participant identifier are
automatically prevented from interacting with each other. Rather
than executing quotes and orders from the same market participant
identifier, the AIQ functionality cancels the oldest of the quotes
and orders.
---------------------------------------------------------------------------

    The Exchange also proposes at this time to make a procedural change
for announcements regarding the STP functionality. Presently the
Exchange issues Regulatory Information Bulletins when making
announcements related to STP functionality. Going forward, the Exchange
proposes to issue a Trader Update in lieu of a Regulatory Information
Bulletin. Regulatory Information Bulletins generally contain
information regarding legal and regulatory matters while a Trader
Update deals with issues such as trading, systems changes and real-time
market announcements. The Exchange believes that it is more appropriate
to make announcements regarding the STP functionality via Trader
Update. Trader Updates, like Regulatory Information Bulletins, are
electronically distributed to OTP Holders and posted on the Exchange's
Web site. Accordingly, the Exchange proposes to amend Commentary .01 to
current Rule 6.76A-O by replacing reference to ``Regulatory Information
Bulletin'' with ``Trader Update.''
Implementation
    Because of the technology changes associated with this proposed
rule change, the Exchange will announce by Trader Update the
implementation date of the proposed rule change, which will be no later
than 60 days from the effective date of this rule filing.
2. Statutory Basis
    The proposed rule change is consistent with Section 6(b) \18\ of
the Securities Exchange Act of 1934 (the ``Act''), in general, and
furthers the objectives of Section 6(b)(5),\19\ in particular, in that
it is designed to prevent fraudulent and manipulative acts and
practices, to promote just and equitable principles of trade, to foster
cooperation and coordination with persons engaged in facilitating
transactions in securities, and to remove impediments to and perfect
the mechanisms of a free and open market and a national market system.
---------------------------------------------------------------------------

    \18\ 15 U.S.C. 78f(b).
    \19\ 15 U.S.C. 78f(b)(5).
---------------------------------------------------------------------------

    As discussed above, the Exchange believes that the proposed rule
change is designed to promote just and equitable principles of trade
because it would provide Market Makers with a functionality that is
similar to functionality currently available on other markets.\20\
Additionally, the Exchange believes that the proposed

rule change is designed to prevent fraudulent and manipulative acts and
practices, to remove impediments to, and perfect the mechanisms of, a
free and open market and a national market system and, in general, to
protect investors and the public interest, because it would allow
Market Makers to better manage their trading interest and provide a
means to prevent executions against their own trading interest.
---------------------------------------------------------------------------

    \20\ See supra, notes 13, 14 and 17.
---------------------------------------------------------------------------

    The Exchange notes that Market Makers have expressed an interest in
the proposed functionality as it would prevent them from inadvertently
trading with their own interest. In such a situation, OTP Holders
currently ask the Exchange to nullify such inadvertent trades, which
they are permitted to do under the Exchange's rules because the OTP
Holder is on both sides of the trade.\21\ While the proposed STP
functionality would prevent inadvertent self-trading, the Exchange
notes that the functionality would also prevent intentional self-
trading. In this regard, the proposed rule change provides a means to
prevent manipulative conduct such as ``wash trading.''
---------------------------------------------------------------------------

    \21\ See NYSE Arca Rule 6.77A-O.
---------------------------------------------------------------------------

    Finally, the replacement of reference to Regulatory Information
Bulletin with Trader Update, would foster cooperation and coordination
with persons engaged in facilitating transactions in securities as
Trader Updates deal with issues such as trading, systems changes and
real-time market announcements and are electronically distributed to
OTP Holders and posted on the Exchange's Web site.

B. Self-Regulatory Organization's Statement on Burden on Competition

    The Exchange does not believe that the proposed rule change will
impose any burden on competition not necessary or appropriate in
furtherance of the purposes of the Act. The proposed rule change is
designed to enhance STP functionality provided to Exchange Market
Makers, and will benefit members that wish to protect their orders and
quotes against trading with other orders and quotes that originate from
the same TPID. The new functionality, which is similar to functionality
currently offered on other markets, is also voluntary, and the Exchange
therefore does not believe that providing an enhanced offering to
prevent against self-trading will have any significant impact on
competition. The Exchange believes that the proposed rule change is
evidence of the competitive environment in the options industry where
exchanges must continually improve their offerings to maintain
competitive standing.

C. Self-Regulatory Organization's Statement on Comments on the Proposed
Rule Change Received From Members, Participants, or Others

    No written comments were solicited or received with respect to the
proposed rule change.

III. Date of Effectiveness of the Proposed Rule Change and Timing for
Commission Action

    Because the foregoing proposed rule change does not: (i)
Significantly affect the protection of investors or the public
interest; (ii) impose any significant burden on competition; and (iii)
become operative for 30 days from the date on which it was filed, or
such shorter time as the Commission may designate, it has become
effective pursuant to Section 19(b)(3)(A) of the Act and Rule 19b-
4(f)(6) thereunder.\22\
---------------------------------------------------------------------------

    \22\ 17 CFR 240.19b-4(f)(6). As required under Rule 19b-
4(f)(6)(iii), the Exchange provided the Commission with written
notice of its intent to file the proposed rule change, along with a
brief description and the text of the proposed rule change, at least
five business days prior to the date of filing of the proposed rule
change, or such shorter time as designated by the Commission.
---------------------------------------------------------------------------

    A proposed rule change filed pursuant to Rule 19b-4(f)(6) under the
Act \23\ normally does not become operative for 30 days after the date
of its filing. However, Rule 19b-4(f)(6)(iii) \24\ permits the
Commission to designate a shorter time if such action is consistent
with the protection of investors and the public interest. The Exchange
has asked the Commission to waive the 30-day operative delay so that
the Exchange can implement the enhanced functionality without delay.
The Exchange believes that waiver of the operative delay is consistent
with the protection of investors and the public interest because it
would enable the Exchange to implement the change when the technology
supporting the change is available, which the Exchange anticipates will
be no later than 60 days from the effective date of this rule filing.
The Commission believes that waiving the 30-day operative delay is
consistent with the protection of investors and the public interest
because the new functionality is designed to provide market makers with
a tool to prevent undesirable executions against themselves and
therefore may assist market makers in managing their order flow.
Therefore, the Commission hereby waives the operative delay and
designates the proposed rule change operative upon filing.\25\
---------------------------------------------------------------------------

    \23\ 17 CFR 240.19b-4(f)(6).
    \24\ 17 CFR 240.19b-4(f)(6)(iii).
    \25\ For purposes only of waiving the 30-day operative delay,
the Commission has considered the proposed rule's impact on
efficiency, competition, and capital formation. See 15 U.S.C.
78c(f).
---------------------------------------------------------------------------

    At any time within 60 days of the filing of the proposed rule
change, the Commission summarily may temporarily suspend such rule
change if it appears to the Commission that such action is necessary or
appropriate in the public interest, for the protection of investors, or
otherwise in furtherance of the purposes of the Act. If the Commission
takes such action, the Commission shall institute proceedings to
determine whether the proposed rule should be approved or disapproved.

IV. Solicitation of Comments

    Interested persons are invited to submit written data, views, and
arguments concerning the foregoing, including whether the proposed rule
change is consistent with the Act. Comments may be submitted by any of
the following methods:

Electronic Comments

     Use the Commission's Internet comment form (http://www.sec.gov/rules/sro.shtml); or
     Send an email to [email protected]. Please include
File Number SR-NYSEArca-2017-118 on the subject line.

Paper Comments

     Send paper comments in triplicate to Secretary, Securities
and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.

All submissions should refer to File Number SR-NYSEArca-2017-118. This
file number should be included on the subject line if email is used. To
help the Commission process and review your comments more efficiently,
please use only one method. The Commission will post all comments on
the Commission's Internet Web site (http://www.sec.gov/rules/sro.shtml). Copies of the submission, all subsequent amendments, all
written statements with respect to the proposed rule change that are
filed with the Commission, and all written communications relating to
the proposed rule change between the Commission and any person, other
than those that may be withheld from the public in accordance with the
provisions of 5 U.S.C. 552, will be available for Web site viewing and
printing in the Commission's Public Reference Room, 100 F Street NE.,
Washington, DC 20549 on official

business days between the hours of 10:00 a.m. and 3:00 p.m. Copies of
such filing also will be available for inspection and copying at the
principal office of the Exchange. All comments received will be posted
without change; the Commission does not edit personal identifying
information from submissions. You should submit only information that
you wish to make available publicly. All submissions should refer to
File Number SR-NYSEArca-2017-118, and should be submitted on or before
November 13, 2017.

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

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

Eduardo A. Aleman,
Assistant Secretary.
[FR Doc. 2017-22883 Filed 10-20-17; 8:45 am]
 BILLING CODE 8011-01-P