[Federal Register Volume 78, Number 95 (Thursday, May 16, 2013)]
[Notices]
[Pages 28906-28908]
[FR Doc No: 2013-11676]

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

SECURITIES AND EXCHANGE COMMISSION

[Release No. 34-69560; File No. SR-CBOE-2013-050]

Self-Regulatory Organizations; Chicago Board Options Exchange,
Incorporated; Notice of Filing and Immediate Effectiveness of a
Proposed Rule Change Relating to the Complex Order Router Subsidy
Program

May 10, 2013.
    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934
(the ``Act''),\1\ and Rule 19b-4 thereunder,\2\ notice is hereby given
that on May 8, 2013, Chicago Board Options Exchange, Incorporated (the
``Exchange'' or ``CBOE'') filed with the Securities and Exchange
Commission (the ``Commission'') the proposed rule change as described
in Items I, II, and III below, which Items have been prepared by the
Exchange. 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\ 17 CFR 240.19b-4.
---------------------------------------------------------------------------

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

    The Exchange proposes to adopt an additional qualification
requirement to participate in CBOE's Complex Order Router Subsidy
Program. The text of the proposed rule change is available on the
Exchange's Web site (http://www.cboe.com/AboutCBOE/CBOELegalRegulatoryHome.aspx), at the Exchange's Office of the
Secretary, 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 Exchange 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 these 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 aspects of such
statements.

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

1. Purpose
    On March 8, 2013, CBOE established the Complex Order Router Subsidy
Program (the ``CORS Program'' or ``Program'') which allows CBOE to
enter into subsidy arrangements with any CBOE Trading Permit Holder
(``TPH'') (each, a ``Participating TPH'') or Non-CBOE TPH broker-dealer
(each a ``Participating Non-CBOE TPH'') that provide certain order
routing functionalities to other CBOE TPHs, Non-CBOE TPHs and/or use
such functionalities themselves.\3\ (The term ``Participant'' as used
in this filing refers to either a Participating TPH or a Participating
Non-CBOE TPH). Specifically, CBOE TPHs and non-CBOE TPHs that
participate in the CORS Program receive a payment from CBOE for every
executed contract for complex orders routed to CBOE through their
system. The purpose of this proposed change is to add an additional
feature that a Participant's order routing functionality must have to
qualify for the Program.
---------------------------------------------------------------------------

    \3\ See Securities Exchange Act Release No. 69203 (March 21,
2013), 78 FR 18655 (March 27, 2013) (SR-CBOE-2013-032).
---------------------------------------------------------------------------

    SR-CBOE-2013-032 includes a description of the features that an
order routing functionality of a Participant must have, and the
performance requirements that the order routing functionality must
satisfy, in order to qualify for the program.\4\ Any CBOE TPH or
broker-dealer that is not a CBOE TPH is permitted to avail itself of
this arrangement, provided that its order routing functionality
incorporates the features required in SR-CBOE-2013-032. In addition to
the features described in SR-CBOE-2013-032, the Exchange is proposing
to require a Participant's order routing functionality to provide
current consolidated market data for complex orders from the U.S.
options exchanges that offer complex order execution systems in order
for the Participant to qualify to participate in the Program. A
Participant shall have forty-five (45) days from the date that an
exchange launches trading of complex orders to provide that exchange's
market data for complex orders as part of its

order routing functionality for any exchange that does not yet exist or
that does not offer complex order execution systems as of May 6, 2013.
---------------------------------------------------------------------------

    \4\ SR-CBOE-2013-032, pp. 5-7. The primary functional
requirements under the CORS Program are that an order routing
functionality has to: (i) be capable of interfacing with CBOE's API
to access current CBOE trade engine functionality and (ii) cause
CBOE to be the default destination exchange for complex orders, but
allow any user to manually override CBOE as the default destination
on an order-by-order basis.
---------------------------------------------------------------------------

    Nothing in the proposed subsidy arrangement relieves any CBOE TPH
or non-CBOE TPH broker-dealer that is using an order routing
functionality whose provider is participating in the CORS Program
(``Users'') from complying with its best execution obligations. Just as
with any customer order and any other routing functionality, both a
CBOE TPH and a non-CBOE TPH broker dealer have an obligation to
consider the availability of price improvement at various markets and
whether routing a customer order through a functionality that
incorporates the features described above would allow for access to
such opportunities if readily available. The Exchange recognizes that,
unlike simple, non-complex orders, there is no NBBO for complex orders
and an exception from the prohibition on trade-throughs is provided for
any transaction that is effected as a portion of a complex order.\5\
The Exchange believes that the proposed additional requirement to
provide consolidated market data for complex orders provides an
additional tool for Users to assess the availability of price
improvement at other markets and therefore facilitates compliance with
their best execution obligations. Finally, any User, whether or not a
CBOE TPH, needs to conduct best execution evaluations on a regular
basis, at a minimum quarterly, that include its use of any router
incorporating the features described above.
---------------------------------------------------------------------------

    \5\ See CBOE Rule 6.81(b)(7).
---------------------------------------------------------------------------

2. Statutory Basis
    The proposed rule change is consistent with Section 6(b) of the
Securities Exchange Act of 1934 (``Act''), in general. Specifically,
the Exchange believes the proposed rule change is consistent with
Section 6(b)(4) of the Act,\6\ which requires that Exchange rules
provide for the equitable allocation of reasonable dues, fees, and
other charges among its Trading Permit Holders and other persons using
its facilities. Additionally, the Exchange believes the proposed rule
change is consistent with the Section 6(b)(5) \7\ requirements that the
rules of an exchange be designed to promote just and equitable
principles of trade, to prevent fraudulent and manipulative acts, to
remove impediments to and to perfect the mechanism for a free and open
market and a national market system, and, in general, to protect
investors and the public interest.
---------------------------------------------------------------------------

    \6\ 15 U.S.C. 78f(b)(4).
    \7\ 15 U.S.C. 78f(b)(5).
---------------------------------------------------------------------------

    In particular, the proposed rule change ensures that CBOE TPHs and
non-CBOE TPH broker dealers that use a Participant's order router
functionality are provided current consolidated market data for complex
orders, which lets them assess the availability of price improvement at
other markets. This information facilitates a User's compliance with
its best execution obligations, thereby enhancing investor protection
and promoting just and equitable principles of trade.
    In addition, the Exchange believes that this proposed change is not
unfairly discriminatory because the proposed additional requirement is
applicable to every Participating CBOE TPH and Participating Non-CBOE
TPH. Additionally, every user of a Participant's order routing
functionality would be receiving the consolidated market data for
complex orders. Finally, any CBOE TPH or broker-dealer that is not a
CBOE TPH may participate in the CORS Program, provided that its complex
order routing functionality incorporates the requirements set forth in
SR-CBOE-2013-032 and above.

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

    CBOE does not believe that the proposed rule change will impose any
burden on competition that is not necessary or appropriate in
furtherance of the purposes of the Act. The Exchange does not believe
that the proposed change will impose an unnecessary burden on
intramarket competition because it will apply equally to all
participating parties. Additionally, the Exchange believes the proposed
rule change will reduce the burdens on investors who use a
Participant's order routing functionality that result from having to
comply with best execution obligations, as they will not themselves
individually receive market data for complex orders from each exchange
that offers complex order execution systems. Further, the Exchange does
not believe that such change will impose any burden on intermarket
competition that is not necessary or appropriate in furtherance of the
purposes of the Act. The Exchange notes that, should the proposed
changes make CBOE more attractive for trading, market participants
trading on other exchanges can always elect to provide order routing
functionality to CBOE for complex orders or use order routing
functionalities that are a part of the CORS Program for complex orders.

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

    The Exchange neither solicited nor received comments on the
proposed rule change.

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

    The foregoing rule change has become effective pursuant to Section
19(b)(3)(A) of the Act \8\ and paragraph (f) of Rule 19b-4 \9\
thereunder. 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 will institute proceedings to
determine whether the proposed rule change should be approved or
disapproved.
---------------------------------------------------------------------------

    \8\ 15 U.S.C. 78s(b)(3)(A).
    \9\ 17 CFR 240.19b-4(f).
---------------------------------------------------------------------------

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_ADDRESS>Please include
File Number SR-CBOE-2013-050 on the subject line.

Paper Comments

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

All submissions should refer to File Number SR-CBOE-2013-050. 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
the 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-CBOE-2013-050, and should be submitted on or before June
6, 2013.

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

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

Kevin M. O'Neill,
Deputy Secretary.
[FR Doc. 2013-11676 Filed 5-15-13; 8:45 am]
BILLING CODE 8011-01-P


Record for the Final Metal Product and Machinery Rule 12 3456789 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 A B C D E F VARIABLE DESCRIPTIONS FOR ' VOS by Establishment Size by NAICS. xls' VARIABLE DESCRIPTION WORKSHEET COLUMN CBI FORMULA NAICS NAICS original data A N Employee Group Employment size category original data B N Empflag Employment size category number original data C N VOS 1997 value of shipments original data D N # of estabs # of establishments in 1997 original data E N Source data: NAICS NAICS corrections A N Source data: Employee Group Employment size category corrections B N Source data: Empflag Employment Size Category Number corrections C N Source data: VOS 1997 Value of Shipments corrections D N Source data: # of estabs # of establishments in 1997 corrections E N distributed from 100+ employees: VOS VOS distributed to employment group from 100+ employees group corrections F N = D34* 0.53, = D34*. 3, = D34*. 12, = D34*. 05 distributed from 100+ employees: estabs # of establishments distributed to employment group from 100+ employees group corrections G N = E34* 0.75, = E34*. 2, = E34*. 04, = E34*. 01 distributed from 1000+ employees: VOS VOS distributed to employment group from 1000+ employees group corrections H N = D38 distributed from 1000+ employees: estabs # of establishments distributed to employment group from 1000+ employees group corrections I N = E38 Subtotals: VOS 1997 Value of shipments corrections J N = H24+ F24+ D24 Subtotals: estabs # of establishments in 1997 corrections K N = I24+ G24+ E24 distributed from ' Estabs not operated all year': VOS VOS distributed to employment group from ' Estabs not operated all year' corrections L N =( J24/( D35 D36))* D36 distributed from ' Estabs not operated all year': estabs # of establishments distributed to employment group from ' Estabs not operated all year' corrections M N =( K24/( E35 E36))* E36 Totals: VOS 1997 value of shipments corrections N N = L24+ J24 Totals: estabs # of establishments in 1997 corrections O N = M24+ K24 NAICS NAICS corrected data A N Employee Group Employment size category corrected data B N Empflag Employment size category number corrected data C N VOS 1997 value of shipments corrected data D N # of Establishments # of establishments in 1997 corrected data E N February 14, 2003 Page 1 of 252 VOS by Establishment Size by NAICS. xls  Var Desc Record for the Final Metal Product and Machinery Rule 1 2 34 5 6789 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 A B C D E Data on VOS and # of Estabs, for 1997, by NAICS code and employment size group.

NAICS Employee Group Empflag VOS # of estabs 234990 0 4 employees 1 2212274 10100 234990 5 9 employees 2 2521996 3442 234990 10 19 employees 3 3753603 2326 234990 20 49 employees 4 6427371 1662 234990 50 99 employees 5 5025590 422 234990 100 249 employees 6 5382349 215 234990 250 499 employees 7 3329840 54 234990 500 999 employees 8 1352782 10 234990 1000 2499 employees 9 0 0 234990 2500+ employees 10 0 0 234990 100+ employees 11 0 0 234990 All establishments 12 31536094 18236 234990 Estabs not operated all year 13 0 0 234990 Estabs operated all year 14 0 0 234990 1000+ employees 15 1530289 6 234990 Total 16 0 0 314999 0 4 employees 1 99121 727 314999 5 9 employees 2 221238 414 314999 10 19 employees 3 373977 399 314999 20 49 employees 4 1063157 404 314999 50 99 employees 5 1048373 165 314999 100 249 employees 6 1269383 90 314999 250 499 employees 7 1101790 29 314999 500 999 employees 8 783275.5443 8 314999 1000 2499 employees 9 228542.4557 1 314999 2500+ employees 10 0 0 314999 100+ employees 11 0 0 314999 All establishments 12 6188857 2237 314999 Estabs not operated all year 13 0 0 314999 Estabs operated all year 14 0 0 314999 1000+ employees 15 0 0 314999 Total 16 0 0 316110 0 4 employees 1 53509 151 316110 5 9 employees 2 52312 50 316110 10 19 employees 3 104504 44 316110 20 49 employees 4 347502 48 316110 50 99 employees 5 588473 35 316110 100 249 employees 6 476130 17 316110 250 499 employees 7 780539 8 316110 500 999 employees 8 657045.0778 5 316110 1000 2499 employees 9 306737.9222 1 316110 2500+ employees 10 0 0 316110 100+ employees 11 0 0 316110 All establishments 12 3366752 359 316110 Estabs not operated all year 13 0 0 316110 Estabs operated all year 14 0 0 316110 1000+ employees 15 0 0 316110 Total 16 0 0 321999 0 4 employees 1 151630 1061 321999 5 9 employees 2 220771 433 321999 10 19 employees 3 445182 403 321999 20 49 employees 4 923763 337 321999 50 99 employees 5 759447 114 Source: Taken from the file ' VOS Est Emp by Employment Size by NAICS. mdb', query ' Truly Final Empgroups with all Sizes'.


[Federal Register Volume 81, Number 188 (Wednesday, September 28, 2016)]
[Notices]
[Pages 66647-66648]
[FR Doc No: 2016-23444]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

Combined Notice of Filings #1

    Take notice that the Commission received the following exempt
wholesale generator filings:

    Docket Numbers: EG16-157-000.
    Applicants: Deerfield Wind Energy, LLC.
    Description: Notice of Self-Certification of Exempt Wholesale
Generator Status of Deerfield Wind Energy, LLC.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5049.
    Comments Due: 5 p.m. ET 10/13/16.

    Take notice that the Commission received the following electric
rate filings:

    Docket Numbers: ER15-1943-001.
    Applicants: Southwest Power Pool, Inc.
    Description: Compliance filing: Missouri River Energy Services
Formula Rate Compliance Filing to be effective 1/1/2017.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5139.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-829-000.
    Applicants: Southwest Power Pool, Inc.
    Description: Report Filing: Refund Report in ER16-829--Bylaws
Section 8.4 Revisions to be effective N/A.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5038.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2340-001.
    Applicants: Emera Energy Services Subsidiary No. 6 LLC.
    Description: Tariff Amendment: Errata to be effective 7/1/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5106.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2341-001.
    Applicants: Emera Energy Services Subsidiary No. 7 LLC.
    Description: Tariff Amendment: Errata to be effective 7/1/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5102.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2342-001.
    Applicants: Emera Energy Services Subsidiary No. 8 LLC.
    Description: Tariff Amendment: Errata to be effective 7/1/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5101.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2343-001.
    Applicants: Emera Energy Services Subsidiary No. 9 LLC.
    Description: Tariff Amendment: Errata to be effective 7/1/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5098.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2344-001.
    Applicants: Emera Energy Services Subsidiary No. 10 LLC.
    Description: Tariff Amendment: Errata to be effective 7/1/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5097.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2347-001.
    Applicants: Bridgeport Energy LLC.
    Description: Tariff Amendment: Errata to be effective 7/1/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5109.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2376-000; ER16-2377-000.
    Applicants: FPL Energy Marcus Hook, L.P.
    Description: Supplement to August 4, 2016 FPL Energy Marcus Hook,
L.P. and FPL Energy MH50, L.P. tariff filings (Reactive Power
Capability Testing Forms).
    Filed Date: 9/22/16.
    Accession Number: 20160922-5137.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2455-001.
    Applicants: Emera Energy Services Subsidiary No. 11 LLC.
    Description: Tariff Amendment: Errata to be effective 10/22/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5096.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2456-001.
    Applicants: Emera Energy Services Subsidiary No. 12 LLC.
    Description: Tariff Amendment: Errata to be effective 10/22/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5095.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2457-001.
    Applicants: Emera Energy Services Subsidiary No. 13 LLC.
    Description: Tariff Amendment: Errata to be effective 10/22/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5093.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2458-001.
    Applicants: Emera Energy Services Subsidiary No. 14 LLC.
    Description: Tariff Amendment: Errata to be effective 10/22/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5092.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2459-001.
    Applicants: Emera Energy Services Subsidiary No. 15 LLC.
    Description: Tariff Amendment: Errata to be effective 10/22/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5090.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2496-001.
    Applicants: CXA Sundevil I, Inc.
    Description: Tariff Amendment: Amendment to Application for MBR to
be effective 9/30/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5088.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2497-001.
    Applicants: CXA Sundevil II, Inc.
    Description: Tariff Amendment: Amendment to Application for MBR to
be effective 9/30/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5089.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2639-000.
    Applicants: PJM Interconnection, L.L.C.
    Description: Sec.  205(d) Rate Filing: Service Agreement Nos. 3069
and 3070; Queue Nos. V4-046/V4-047 and V4-048/V4-049 to be effective 8/
22/2016.
    Filed Date: 9/21/16.
    Accession Number: 20160921-5141.
    Comments Due: 5 p.m. ET 10/12/16.

    Docket Numbers: ER16-2642-000.
    Applicants: Southern California Edison Company.
    Description: Sec.  205(d) Rate Filing: DSA Mojave Water Agency Deep
Creek Hydroelectric Project to be effective 11/22/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5072.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2643-000.
    Applicants: Panda Stonewall LLC.
    Description: Baseline eTariff Filing: FERC Electric Tariff, Volume
No. 1 (Market-Based Rate Application) to be effective 11/21/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5077.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2644-000.
    Applicants: Northern Indiana Public Service Company.

    Description: Sec.  205(d) Rate Filing: Contribution in Aid of
Construction Agreement to be effective 9/18/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5086.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2646-000.
    Applicants: El Paso Electric Company.
    Description: Sec.  205(d) Rate Filing: Concurrence of EPE to APS
Service Agreement No. 284 to be effective 10/31/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5111.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2647-000.
    Applicants: Puget Sound Energy, Inc.
    Description: Initial rate filing: BPA NITSA & NOA to be effective
9/1/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5121.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2648-000.
    Applicants: Niagara Mohawk Power Corporation, New York Independent
System Operator, Inc.
    Description: Tariff Cancellation: Notice of cancellation SA 1949
among NMPC and EDGE Corporation to be effective 11/22/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5160.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2649-000.
    Applicants: Duke Energy Progress, LLC, Duke Energy Carolinas, LLC.
    Description: Sec.  205(d) Rate Filing: Loss Factor Filing Amendment
to be effective 8/1/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5165.
    Comments Due: 5 p.m. ET 10/13/16.

    Docket Numbers: ER16-2650-000.
    Applicants: Niagara Mohawk Power Corporation, New York Independent
System Operator, Inc.
    Description: Tariff Cancellation: Notice of cancellation SA 1951
between NYISO, NMPC and NYPA to be effective 11/22/2016.
    Filed Date: 9/22/16.
    Accession Number: 20160922-5168.
    Comments Due: 5 p.m. ET 10/13/16.
    Take notice that the Commission received the following electric
securities filings:

    Docket Numbers: ES16-55-000.
    Applicants: Consolidated Edison Company of New York, Inc.
    Description: Application of Consolidated Edison Company of New
York, Inc. for an order pursuant to Section 204 of the Federal Power
Act.
    Filed Date: 9/21/16.
    Accession Number: 20160921-5184.
    Comments Due: 5 p.m. ET 10/12/16.

    The filings are accessible in the Commission's eLibrary system by
clicking on the links or querying the docket number.
    Any person desiring to intervene or protest in any of the above
proceedings must file in accordance with Rules 211 and 214 of the
Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5:00
p.m. Eastern time on the specified comment date. Protests may be
considered, but intervention is necessary to become a party to the
proceeding.
    eFiling is encouraged. More detailed information relating to filing
requirements, interventions, protests, service, and qualifying
facilities filings can be found at:
    http://www.ferc.gov/docs-filing/efiling/filing-req.pdf. For other
information, call<PHONE_NUMBER> (toll free). For TTY, call (202) 502-
8659.

    Dated: September 22, 2016.
Nathaniel J. Davis, Sr.,
Deputy Secretary.
[FR Doc. 2016-23444 Filed 9-27-16; 8:45 am]
 BILLING CODE 6717-01-P


[Federal Register Volume 87, Number 64 (Monday, April 4, 2022)]
[Proposed Rules]
[Pages 19410-19411]
[FR Doc No: 2022-07027]

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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 71

[Docket No. FAA-2022-0299; Airspace Docket No. 22-AAL-18]
RIN 2120-AA66

Proposed Revocation of Colored Federal Airway Amber 6 (A-6); St.
Mary's, AK

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Notice of proposed rulemaking (NPRM).

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

SUMMARY: This action proposes to revoke Colored Federal airway Amber 6
(A-6) in the vicinity of St. Mary's, AK due to the pending
decommissioning of St. Mary's, AK, (SMA) Non-Directional Beacon (NDB).

DATES: Comments must be received on or before May 19, 2022.

ADDRESSES: Send comments on this proposal to the U.S. Department of
Transportation, Docket Operations, 1200 New Jersey Avenue SE, West
Building Ground Floor, Room W12-140, Washington, DC 20590; telephone:
(800) 647-5527, or<PHONE_NUMBER>. You must identify FAA Docket No.
FAA-2022-0299; Airspace Docket No. 22-AAL-18 at the beginning of your
comments. You may also submit comments through the internet at https://www.regulations.gov.
    FAA Order JO 7400.11F, Airspace Designations and Reporting Points,
and subsequent amendments can be viewed online at https://www.faa.gov/air_traffic/publications/. For further information, you can contact the
Rules and Regulations Group, Federal Aviation Administration, 800
Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-
8783.

FOR FURTHER INFORMATION CONTACT: Christopher McMullin, Rules and
Regulations Group, Office of Policy, Federal Aviation Administration,
800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-
8783.

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
the 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 would modify the route structure as necessary to
preserve the safe and efficient flow of air traffic within the National
Airspace System (NAS).

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 (FAA Docket No.
FAA-2022-0299; Airspace Docket No. 22-AAL-18) and be submitted in
triplicate to the Docket Management Facility (see ADDRESSES section for
address and phone number). You may also submit comments through the
internet at https://www.regulations.gov.
    Commenters wishing the FAA to acknowledge receipt of their comments
on this action must submit with those comments a self-addressed,
stamped postcard on which the following statement is made: ``Comments
to FAA Docket No. FAA-2022-0299; Airspace Docket No. 22-AAL-18.'' The
postcard will be date/time stamped and returned to the commenter.
    All communications received on or before the specified comment
closing date will be considered before taking action on the proposed
rule. The proposal contained in this action 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 comment
closing date. A report summarizing each substantive public contact with
FAA personnel concerned with this rulemaking will be filed in the
docket.

Availability of NPRM

    An electronic copy of this document may be downloaded through the
internet at https://www.regulations.gov. Recently published rulemaking
documents can also be accessed through the FAA's web page at https://www.faa.gov/air_traffic/publications/airspace_amendments/.
    You may review the public docket containing the proposal, any
comments received and any final disposition in person in the Dockets
Office (see ADDRESSES section for address and phone number) between
9:00 a.m. and 5:00 p.m., Monday through Friday, except Federal
holidays. An informal docket may also be examined during normal
business hours at the office of the Operations Support Group, Western
Service Center, Federal Aviation Administration, 2200 South 216th St.,
Des Moines, WA 98198.

Availability and Summary of Documents for Incorporation by Reference

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

Background

    The aviation industry/users have indicated a desire for the FAA to
transition the Alaskan en route navigation structure away from the
dependency on NDBs. The advances in technology have allowed for
alternate navigation methods to support decommissioning of high cost
ground navigation equipment. The FAA conducted a non-rulemaking study
in accordance with FAA Order JO 7400.2, Procedures for Handling
Airspace Matters in 2021 on SMA, due to the high cost of maintenance
and repairs. As a result of the study, there were no objections
received and the FAA added SMA to the schedule to be decommissioned.
    Colored Federal airway A-6 navigates from SMA to the North River,
AK, (JNR) NDB. The decommissioning of SMA would result in A-6 being
unusable. Therefore, the FAA is proposing to revoke A-6. The proposed
revocation will be mitigated by a future United States Area Navigation
route that would overlay the current route.

The Proposal

    The FAA is proposing an amendment to 14 CFR part 71 to revoke
Colored Federal airway A-6 in the vicinity of St. Mary's, AK due to the
decommissioning of SMA. A-6 currently navigates between SMA and JNR.
The FAA proposes to revoke A-6 in its entirety.
    Colored Federal airways are published in paragraph 6009(c) of FAA
Order JO 7400.11F dated August 10, 2021 and effective September 15,
2021, which is incorporated by reference in 14 CFR 71.1. The Colored
Federal airway listed in this document would be removed subsequently in
FAA Order JO 7400.11.
    FAA Order JO 7400.11, Airspace Designations and Reporting Points,
is published yearly and effective on September 15.

Regulatory Notices and Analyses

    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
Department of Transportation (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.

Environmental Review

    This proposal will be subject to an environmental analysis in
accordance with FAA Order 1050.1F, ``Environmental Impacts: Policies
and Procedures'' prior to any FAA final regulatory action.

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, B, C, D, AND E AIRSPACE AREAS; AIR
TRAFFIC SERVICE ROUTES; AND REPORTING POINTS

0
1. The authority citation for 14 CFR 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 JO
7400.11F, Airspace Designations and Reporting Points, dated August 10,
2021, and effective September 15, 2021, is amended as follows:

Paragraph 6009(c) Colored Federal Airways.

* * * * *

A-6 [Remove]

* * * * *

    Issued in Washington, DC, on March 29, 2022.
Scott M. Rosenbloom,
Manager, Airspace Rules and Regulations.
[FR Doc. 2022-07027 Filed 4-1-22; 8:45 am]
BILLING CODE 4910-13-P


[Federal Register: May 1, 2009 (Volume 74, Number 83)]
[Notices]
[Page 20298-20300]
[DOCID:fr01my09-40]

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

ENVIRONMENTAL PROTECTION AGENCY

[EPA-HQ-OPP-2009-0029; FRL-8404-9]

Pesticide Products; Registration Applications

AGENCY: Environmental Protection Agency (EPA).

ACTION: Notice.

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

SUMMARY: This notice announces receipt of applications to register
pesticide products containing new active ingredients not included in
any currently registered products pursuant to the provisions of section
3(c)(4) of the Federal Insecticide, Fungicide, and Rodenticide Act
(FIFRA), as amended.

DATES: Comments must be received on or before June 1, 2009.

ADDRESSES: Submit your comments, identified by docket identification
(ID) number EPA-HQ-OPP-2009-0029, by one of the following methods:
     Federal eRulemaking Portal: http://www.regulations.gov.
Follow the on-line instructions for submitting comments.
     Mail: Office of Pesticide Programs (OPP) Regulatory Public
Docket (7502P), Environmental Protection Agency, 1200 Pennsylvania
Ave., NW., Washington, DC 20460-0001.
     Delivery: OPP Regulatory Public Docket (7502P),
Environmental Protection Agency, Rm. S-4400, One Potomac Yard (South
Bldg.), 2777 S. Crystal Dr., Arlington, VA. Deliveries are only
accepted during the Docket Facility's normal hours of operation (8:30
a.m. to 4 p.m., Monday through Friday, excluding legal holidays).
Special arrangements should be made for deliveries of boxed
information. The Docket Facility telephone number is<PHONE_NUMBER>.
    Instructions: Direct your comments to docket ID number EPA-HQ-OPP-
2009-0029. EPA's policy is that all comments received will be included
in the docket without change and may be made available on-line at
http://www.regulations.gov, including any personal information
provided, unless the comment includes information claimed to be
Confidential Business

Information (CBI) or other information whose disclosure is restricted
by statute. Do not submit information that you consider to be CBI or
otherwise protected through regulations.gov or e-mail. The
regulations.gov website is an ``anonymous access'' system, which means
EPA will not know your identity or contact information unless you
provide it in the body of your comment. If you send an e-mail comment
directly to EPA without going through regulations.gov, your e-mail
address will be automatically captured and included as part of the
comment that is placed in the docket and made available on the
Internet. If you submit an electronic comment, EPA recommends that you
include your name and other contact information in the body of your
comment and with any disk or CD-ROM you submit. If EPA cannot read your
comment due to technical difficulties and cannot contact you for
clarification, EPA may not be able to consider your comment. Electronic
files should avoid the use of special characters, any form of
encryption, and be free of any defects or viruses.
    Docket: All documents in the docket are listed in the docket index
available at http://www.regulations.gov. Although listed in the index,
some information is not publicly available, e.g., CBI or other
information whose disclosure is restricted by statute. Certain other
material, such as copyrighted material, is not placed on the Internet
and will be publicly available only in hard copy form. Publicly
available docket materials are available either in the electronic
docket at http://www.regulations.gov, or, if only available in hard
copy, at the OPP Regulatory Public Docket in Rm. S-4400, One Potomac
Yard (South Bldg.), 2777 S. Crystal Dr., Arlington, VA. The hours of
operation of this Docket Facility are from 8:30 a.m. to 4 p.m., Monday
through Friday, excluding legal holidays. The Docket Facility telephone
number is<PHONE_NUMBER>.

FOR FURTHER INFORMATION CONTACT:  The Regulatory Action Leader listed
in the table in this unit.

----------------------------------------------------------------------------------------------------------------
                                       Telephone Number and E-
       Regulatory Action Leader             mail  Address           Mailing Address            File Symbol
----------------------------------------------------------------------------------------------------------------
John Bazuin<PHONE_NUMBER>           Registration Division    55050-G
<EMAIL_ADDRESS>  (7505P), Office of      55050-L
                                                                 Pesticide Programs,     55050-U
                                                                 Environmental
                                                                 Protection Agency,
                                                                 1200 Pennsylvania
                                                                 Ave., NW., Washington,
                                                                 DC 20460-0001
----------------------------------------------------------------------------------------------------------------
Samantha Hulkower<PHONE_NUMBER>           Do.                      8033-RNE
<EMAIL_ADDRESS>                         8033-RNG
                                        ov.                                              8033-RNU
----------------------------------------------------------------------------------------------------------------
Autumn Metzger<PHONE_NUMBER>           Do.                      56228-UN
<EMAIL_ADDRESS>----------------------------------------------------------------------------------------------------------------

SUPPLEMENTARY INFORMATION:

I. General Information

A. Does this Action Apply to Me?

    You may be potentially affected by this action if you are an
agricultural producer, food manufacturer, or pesticide manufacturer.
Potentially affected entities may include, but are not limited to:
     Crop production (NAICS code 111).
     Animal production (NAICS code 112).
     Food manufacturing (NAICS code 311).
     Pesticide manufacturing (NAICS code 32532).
    This listing is not intended to be exhaustive, but rather provides
a guide for readers regarding entities likely to be affected by this
action. Other types of entities not listed in this unit could also be
affected. The North American Industrial Classification System (NAICS)
codes have been provided to assist you and others in determining
whether this action might apply to certain entities. If you have any
questions regarding the applicability of this action to a particular
entity, consult the person listed under FOR FURTHER INFORMATION
CONTACT.

B. What Should I Consider as I Prepare My Comments for EPA?

    1. Submitting CBI. Do not submit this information to EPA through
regulations.gov or e-mail. Clearly mark the part or all of the
information that you claim to be CBI. For CBI information in a disk or
CD-ROM that you mail to EPA, mark the outside of the disk or CD-ROM as
CBI and then identify electronically within the disk or CD-ROM the
specific information that is claimed as CBI. In addition to one
complete version of the comment that includes information claimed as
CBI, a copy of the comment that does not contain the information
claimed as CBI must be submitted for inclusion in the public docket.
Information so marked will not be disclosed except in accordance with
procedures set forth in 40 CFR part 2.
    2. Tips for preparing your comments. When submitting comments,
remember to:
    i. Identify the document by docket ID number and other identifying
information (subject heading, Federal Register date and page number).
    ii. Follow directions. The Agency may ask you to respond to
specific questions or organize comments by referencing a Code of
Federal Regulations (CFR) part or section number.
    iii. Explain why you agree or disagree; suggest alternatives and
substitute language for your requested changes.
    iv. Describe any assumptions and provide any technical information
and/or data that you used.
    v. If you estimate potential costs or burdens, explain how you
arrived at your estimate in sufficient detail to allow for it to be
reproduced.
    vi. Provide specific examples to illustrate your concerns and
suggest alternatives.
    vii. Explain your views as clearly as possible, avoiding the use of
profanity or personal threats.
    viii. Make sure to submit your comments by the comment period
deadline identified.

II. Registration Applications

     EPA received applications as follows to register pesticide
products containing active ingredients not included in any previously
registered products pursuant

to the provision of section 3(c)(4) of FIFRA. Notice of receipt of
these applications does not imply a decision by the Agency on the
applications.
    1. File Symbol: 8033-RNE. Applicant: Nippon Soda Co., Ltd., c/o
Nisso America Inc., 45 Broadway, Suite 2120, New York, NY 10006.
Product name: Cyflufenamid Technical Fungicide. Product type:
Fungicide. Active ingredient: Cyflufenamid at 98.9%. PC Code: 555550.
Proposed classification: Cyflufenamid is a new mode-of-action fungicide
and has not yet been classified with the Fungicide Resistance Action
Committee (FRAC). Use: Manufacturing use only.
    2. File Symbol: 8033-RNG. Applicant: Nippon Soda Co., Ltd., c/o
Nisso America Inc., 45 Broadway, Suite 2120, New York, NY 10006.
Product name: Miltrex 10 SC Fungicide. Product type: Fungicide. Active
ingredient: Cyflufenamid at 10% suspension concentrate. PC Code:
555550. Proposed classification: Cyflufenamid is a new mode-of-action
fungicide and has not yet been classified with FRAC. Use: For use on
pome fruit (Crop Group 11), cucurbits (Crop Group 9), grapes (and other
climbing vine small fruit except fuzzy kiwifruit, Crop Subgroup 13-
07F), and strawberries (Crop Subgroup 13-07G).
    3. File Symbol: 8033-RNU. Applicant: Nippon Soda Co., Ltd., c/o
Nisso America Inc., 45 Broadway, Suite 2120, New York, NY 10006.
Product name: Miltrex 10 SC Fungicide. Product type: Fungicide. Active
ingredient: Cyflufenamid at 10% suspension concentrate. PC Code:
555550. Proposed classification: Cyflufenamid is a new mode-of-action
fungicide and has not yet been classified with FRAC. Use: For use on
outdoor nursery and outdoor landscape ornamentals.
    4. File Symbol: 55050-G. Applicant: Arkema, Inc., 630 Freedom
Business Center, Suite 402, King of Prussia, PA 19406. Product name:
Accolade Technical. Product type: Fungicide. Active ingredient:
Dimethyl disulfide at 99.8%. Proposed classification/use: Manufacturing
use only.
    5. File Symbol: 55050-L.  Applicant: Arkema, Inc., 630 Freedom
Business Center, Suite 402, King of Prussia, PA 19406. Product name:
Accolade EC. Product type: Fungicide. Active ingredient: Dimethyl
disulfide at 98.8%. Proposed classification/use: None. For use on
vegetable crops, fruit crops, floral crops, and nursery/ornamental
crops.
    6. File Symbol: 55050-U. Applicant: Arkema, Inc., 630 Freedom
Business Center, Suite 402, King of Prussia, PA 19406. Product name:
Accolade. Product type: Fungicide. Active ingredient: Dimethyl
disulfide at 98.8%. Proposed classification/use: None. For use on
vegetable crops, fruit crops, floral crops, nursery crops, and forest
nursery crops.
    7. File Symbol: 56228-UN. Applicant: U.S. Department of
Agriculture, Animal and Plant Health Inspection Service (USDA APHIS),
4700 River Road, Unit 149, Riverdale, MD 20737. Product name: Gonacon
Immunocontraceptive Vaccine. Active Ingredient: Mammalian Gonadotropin
Releasing Hormone (GnRH). PC Code: 116800. Use: Gonacon will be used to
control contraception in wild, white-tailed deer (Odocoileus
virginianus). The product will be applied as a vaccination delivered by
hand injection and will be a Restricted Use Product only to be
administered by USDA APHIS Wildlife Services or state wildlife
management agency personnel, or persons working under their authority.
The proposed end-use product contains .03% GnRH.

List of Subjects

    Environmental protection, Pesticides and pest.

    Dated: April 3, 2009.
Lois Rossi,
Director, Registration Division, Office of Pesticide Programs.
[FR Doc. E9-10093 Filed 4-30-09; 8:45 a.m.]

BILLING CODE 6560-50-S


[Federal Register Volume 83, Number 26 (Wednesday, February 7, 2018)]
[Notices]
[Pages 5506-5508]
[FR Doc No: 2018-02437]

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

DEPARTMENT OF TRANSPORTATION

Federal Motor Carrier Safety Administration

[Docket No. FMCSA-2014-0177]

Crash Preventability Demonstration Program

AGENCY: Federal Motor Carrier Safety Administration (FMCSA), DOT.

ACTION: Notice.

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

SUMMARY: On July 27, 2017, FMCSA announced the initiation of a crash
preventability demonstration program in which the Agency would accept
requests for data review (RDRs) to evaluate the preventability of
certain categories of crashes through its national data correction
system known as DataQs. This notice provides additional information to
help submitters and other interested parties understand the
demonstration program.

DATES: The crash preventability demonstration program began accepting
RDRs on August 1, 2017, for crashes that occurred on or after June 1,
2017.

FOR FURTHER INFORMATION CONTACT: Mr. Catterson Oh, Compliance Division,
Federal Motor Carrier Safety Administration, 1200 New Jersey Avenue SE,
Washington, DC 20590, Telephone<PHONE_NUMBER> or by email:
[email protected]. If you have questions regarding viewing or
submitting material to the docket, contact Docket Services, telephone
(202) 366-9826.

SUPPLEMENTARY INFORMATION:

Background

    In a Federal Register noticed dated July 12, 2016, FMCSA proposed a
demonstration program to determine the efficacy of preventability
determinations on certain types of crashes that are generally less
complex. (81 FR 45210) The Agency proposed to accept RDRs to evaluate
the preventability of certain categories of crashes through its
national data correction system known as DataQs. It proposed that a
crash challenged through an RDR would be found not preventable when
documentation submitted with the RDR

established that the crash was not preventable.
    On July 27, 2017, FMCSA published a subsequent Federal Register
notice announcing the start of the demonstration program and explaining
the details of the program.
    Since August 1, 2017, over 2,500 RDRs have been submitted to FMCSA.
Based on the experiences operating the program for the first few
months, the Agency identified some areas of the program requiring more
instruction and details.

Demonstration Program Details

Correctly Submitting Eligible Crashes to the Demonstration Program

    The DataQs system includes both the standard review program and the
crash preventability demonstration program. Some submitters have
entered crashes under the standard review program, rather than the
crash preventability demonstration program, by selecting ``Not an
FMCSA-reportable crash'' or requesting the review of an ineligible
crash. A selection of ``Not an FMCSA-reportable crash'' is for those
crashes that do not meet FMCSA's recordable crash definition of a
fatality, injury, or property damage requiring a vehicle to be towed
from the scene. DataQs RDRs entered into the standard review program
will be closed without a preventability determination because they were
not submitted under the demonstration program. Also, when an RDR is
submitted for a crash that is not eligible for the demonstration
program, the system will close the RDR without any action. Examples of
ineligible crashes include those that do not fall under the eight types
of crashes and those that occurred before June 1, 2017.
    For the crash preventability demonstration program, submitters
should choose ``Crash could not be prevented,'' ensure that the crash
event date is on or after June 1, 2017, and select an eligible crash
type. For more information, submitters should view the FMCSA video at
https://www.fmcsa.dot.gov/safety/crash-preventability-demonstration-program-video.

Types of Crashes

    The only types of crashes that will be reviewed using the RDR
process during the demonstration program are:

    1. When the commercial motor vehicle (CMV) was struck by a
motorist driving under the influence (or related offense);
    2. When the CMV was struck by a motorist driving the wrong
direction;
    3. When the CMV was struck in the rear;
    4. When the CMV was struck while it was legally stopped or
parked, including when the vehicle was unattended;
    5. When the CMV struck an individual committing or attempting to
commit suicide by stepping or driving in front of the CMV;
    6. When the CMV sustained disabling damage after striking an
animal in the roadway;
    7. When the crash was the result of an infrastructure failure,
falling trees, rocks, or other debris; or
    8. When the CMV was struck by cargo or equipment from another
vehicle.

    A significant number of RDRs submitted are, in fact, not eligible
for the demonstration program. Below are examples of crash types that
were submitted, and determined to be not eligible for the program:

    1. Crashes that do not match any eligible crash type.
    2. RDRs asserting the driver who struck the CMV was operating
under the influence without any supporting evidence, such as
documents showing testing results, citation, or arrest.
    3. RDRs submitted for crashes identified as ``struck by a
motorist driving the wrong direction'' where the vehicle that struck
the CMV was not operating completely in the wrong lane and in the
wrong direction. These crashes do not include when the vehicle that
struck the CMV swerved across the center line but did not travel
entirely in the wrong lane and in the wrong direction. In addition,
this crash type does not include crashes at intersections, crashes
with vehicles completing a U-turn, or when a vehicle traveling in
the same direction as the CMV crashes into the CMV for whatever
reason.
    Eligible crashes include when the vehicle that struck the CMV
completely crossed the median or center line and traveled into
opposing traffic or was operating in the wrong direction on a
divided highway.
    4. RDRs for crashes where the CMV was struck in other places on
the vehicle, but not in the rear. For the purposes of this
demonstration program, FMCSA is defining ``struck in the rear'' to
mean only crashes when the rear plane of the CMV was struck. Crashes
where the CMV was struck on the side near the rear of the vehicle,
or other places on the vehicle, are not eligible. This includes
crashes where the vehicle was struck at the 7 o'clock or 5 o'clock
positions.
    5. RDRs for crashes when the vehicle was stopped in traffic and
not legally stopped or parked.
    6. RDRs alleging a suicide attempt without any supporting
evidence.
    7. RDRs indicating the CMV struck other vehicles stopped for a
fallen tree or rocks, but the CMV did not strike the tree or rocks.
    8. RDRs asserting the CMV was struck by cargo or equipment, but
the documentation establishes the CMV was actually hit by another
vehicle.
    These parameters are needed so that the Agency can accurately
and consistently assess the evaluation of crashes during the
demonstration program.

Documents To Be Submitted

    Because the burden is on the submitter to show by compelling
evidence that the crash was not preventable, the submitter should
submit all evidence in support of the preventability determination. The
Agency considers all relevant evidence submitted. FMCSA is not,
however, requiring any specific documentation in support of a
preventability determination.
    FMCSA advised in its July 27, 2017, Federal Register notice that
the Agency could request additional information on the crash, which may
include any documentation the carrier is required to maintain under the
Agency's regulations. In some instances, FMCSA will request additional
information to confirm that the driver was operating in compliance with
applicable regulatory requirements. To date in the demonstration
program, FMCSA has requested the following types of documents:

    1. Proof of a valid Commercial Driver's License (CDL) on the
date of the crash--If the license was renewed after the crash date,
FMCSA is unable to determine the license status on the date of the
crash because the Commercial Driver's License Information System
(CDLIS) provides only the new license issuance date. If the
submitter does not provide documentation of a valid CDL on the date
of the crash, in response to FMCSA's request, the crash
determination will be ``Undecided'' because FMCSA cannot confirm the
driver was operating with a valid CDL.
    2. Proof of a valid medical certificate on the date of the
crash--If the CDLIS system indicates the medical certificate was
expired on the date of the crash and evidence of a valid medical
certificate on the date of the crash is not submitted in response to
FMCSA's request, the crash determination will be ``Undecided''
because FMCSA cannot confirm the driver was operating with a valid
medical certificate.
    3. Proof that the driver was operating in accordance with the
excepted status--If a CDL driver has an exempt license, FMCSA is
requesting information about the load to confirm the driver was
operating within the restrictions of the license. If the
documentation of the load is not provided, the determination will be
``Undecided'' because FMCSA cannot confirm the driver was operating
in compliance with CDL restrictions.

    It is incumbent on the submitter to accurately provide the
requested document such as a medical card or CDL for the date of the
crash. In addition, when documents such as police accident reports and
insurance papers are submitted, full copies should be provided.

Re-Opening RDRs

    If a submitter receives a determination that the crash was
preventable or undecided, or the RDR is closed for another reason, the
RDR may be re-opened once. The request will be reconsidered by FMCSA
only if additional documentation or new information is submitted. If
additional information or documentation is not provided, the RDR will
be closed with the initial determination without further consideration.
    Additionally, once an RDR is closed, the Agency will not be
responding to additional comments submitted through the DataQs system.
The RDR must be reopened and additional information submitted as cause
for FMCSA to reconsider the determination.

Input From the Public

    The opportunity to collect information from other parties is
critical to determining the impacts and costs of this demonstration
program. During the demonstration program, if a crash review results in
a preliminary determination that the crash was not preventable, the
Agency will publish the crash report number, U.S. DOT number, motor
carrier name, crash event date, crash event State and crash type on its
DataQs website.
    Any member of the public with documentation or data to refute the
proposed determination has 30 days to submit the documentation through
the DataQs system at https://dataqs.fmcsa.dot.gov. Information on how
to submit additional documentation is available at https://www.fmcsa.dot.gov/safety/crash-preventability-demonstration-program.
    Any new documents or data will be reviewed and considered before
FMCSA makes a final determination. Final determinations will be
published on SMS within 60 days of the final decision.
    However, based on feedback from some stakeholders, the Agency
recognizes that some parties involved in the crash might not be able to
provide input within 30 days. The Agency will maintain a list of not
preventable final determinations on its website at https://www.fmcsa.dot.gov/safety/crash-preventability-demonstration-program.
This list will be updated monthly. If at any time during this
demonstration program a party has information and documentation to
counter this determination, FMCSA will accept that information at
[email protected]. Therefore, determinations may be revised
after consideration of this additional information.

Agency Use of Data

    As explained in the July 17, 2017, Federal Register notice, final
determinations made through this demonstration program will be noted on
the Agency's Safety Measurement System (SMS). No crashes are removed
from SMS as a result of this demonstration program. For the purpose of
prioritizing motor carriers for safety interventions, FMCSA will
continue to use all crashes during the demonstration program.
    The crash preventability determinations made under this program
will not affect any carrier's safety rating or ability to operate.
FMCSA will not issue penalties or sanctions based on these
determinations, nor do they establish any obligations or impose legal
requirements on any motor carrier. These determinations also will not
change how the Agency will make enforcement decisions.
    Information submitted about a crash as part of this demonstration
program may be shared with the appropriate FMCSA Division Office for
further investigation. Likewise, if an investigation reveals additional
information about a crash for which the demonstration program made a
preventability determination, this information may be shared within the
Agency and the crash subjected to further review.
    Throughout this demonstration period, FMCSA will maintain data so
that at the conclusion of the demonstration program, the Agency can
conduct analyses. It is expected that the Agency's analyses would
include, but not be limited to, the cost of operating the test and its
extrapolation to a larger program; future crash rates of carriers that
submitted RDRs, future crash rates of motor carriers with not
preventable crashes, and impacts to SMS crash rates and improvements to
prioritization.
    Additionally, under 49 U.S.C. 504(f), ``No part of a report of an
accident occurring in operations of a motor carrier, motor carrier of
migrant workers, or motor private carrier and required by the
Secretary, and no part of a report of an investigation of the accident
made by the Secretary, may be admitted into evidence or used in a civil
action for damages related to a matter mentioned in the report or
investigation.'' The crash preventability determinations made under
this program are intended only for FMCSA's use in determining whether
the program may improve the Agency's prioritization tools. These
determinations are made on the basis of information available to FMCSA
at the time of the determination and are not appropriate for use by
private parties in civil litigation. These determinations do not
establish fault or negligence by any party and are made by persons with
no personal knowledge of the crash.

DataQs

    Motor carriers and drivers, as well as any member of the public,
may submit crash preventability RDRs through the Agency's DataQs
system. DataQs has been modified to provide this functionality. The
DataQs system is available at: https://dataqs.fmcsa.dot.gov. The DataQs
User Guide advises that it should take 2 weeks to have an RDR reviewed.
The User Guide is for RDRs that are not in the demonstration program.
Based on the volume of RDRs submitted, the Agency's timeframe for
review is averaging 3 to 4 weeks.
    Additional information on how to submit a crash preventability RDR
is available on the Agency's website at https://www.fmcsa.dot.gov/safety/crash-preventability-demonstration-program.

    Issued under the authority delegated in 49 CFR 1.87 on: January
31, 2018.
Cathy F. Gautreaux,
Deputy Administrator.
[FR Doc. 2018-02437 Filed 2-6-18; 8:45 am]
 BILLING CODE 4910-EX-P


Steam Electric Data Request Follow-Up Questions

Project Name:  Steam Electric Detailed Study

	Project No.:  0<IP_ADDRESS>

Company Name:  Georgia Power

	Contact Name:  William R. Evans

Plant Name:  Plant Wansley	Contact Phone Number:<PHONE_NUMBER>

or Email Address<EMAIL_ADDRESS>
ERG Staff (or ERG Rep) Name: Sarah Holman

Company Affiliation: ERG	Date: 12/19/07

This document contains CBI:   ___  Yes    x       No

	Type of  Contact:     x      Email       x    Telephone

General Subject:  Data Request Assistance / Follow-Up

Follow-Up Question Number	CBI =

Yes (Y)

No (N)	Data Request Question Number	Data Request Page Number

Question/Answer

1	N	8	B-3	Q: The combined cycle units (Units 6-9) operated at Plant
Wansley are not included in Table 2.  Please verify that the reason
Georgia Power did not include these combine cycle units in its data
request response is that it did not operate these units in 2006.

Please confirm that Unit 5 was not included in Table 2 because it is an
oil-fired combustion turbine with no steam electric operations.

A:  Verified.  Units 6 – 9 are typical combined cycle units: the steam
cycle is about 1/3 of the total unit.  Wastewater from these units
discharges into the ash pond and the approximate flow rates are listed
in the Form 2C.

Confirmed.

2	N	11	B-8	Q: Frequency of drainage from coal pile is given as 365 days.
 Does the plant have an estimation of the actual number of days of
drainage from the coal pile, or an estimation of the number of days of
rain in 2006?

A:  Mr. Evans believes that the coal pile is so large that there is
likely continuous drainage from the coal pile to the two coal pile
runoff ponds.  Water is pumped continuously from the coal pile runoff
ponds, and the plant used the combination of the two flow rates to
estimate the drainage into the pond.

3	N	16	B-10	Q: Type of fly ash handling system is listed as both wet and
dry.  What is the approximate percentage of the time that the fly ash is
handled in a dry fashion?

A:  1.16% of the fly is handled dry and sold: 4,997 tons in 2006.  The
rest of the fly ash is sluiced, and sluicing is continuous 24 hpd, 365
dpy.  The tpd of ash provided in Table 5 includes the fly ash sold and
sluiced.

4	N	18	B-12	Q: The total bottom ash sluice flow rate for Units 1 and 2
is 2,566 gpm in Table 6, whereas it is listed as 2,580 gpm in the
process diagram, 5-1.  Please explain this difference.  Which flow rate
is more accurate?

A:  The Table 6 response is more accurate.

5	N	31	B-21	Q: Why was wastewater generated from the Unit 2 air
pre-heater, but not from the Unit 1 air pre-heater in 2006?

A: Air pre-heater cleaning was not necessary for Unit 1 in 2006.
Typically, the air pre-heaters are only washed when the units are
brought down and that typically occurs every three to four years.

6	N	38	B-25	Q: CT 1 and CT 2 both used gaseous chlorine in 2006, with
the same average addition amount, but the amount is listed as ppd for CT
1 and gpd for CT 2.  Please confirm that the measurement units should be
ppd for both.

A:  Confirmed.

7	N	38	B-25	Q: No measurement units were provided for the average
addition amount of liquid sodium hypochlorite for CT 2.  Please provide
the measurement units.

A:  gpd.

8	N	43	B-26	Q: Outfalls 01D, 01F-01K, 02, 02D-02K, 03A, 03B, and 04-06
are not listed in Table 14 or the process diagrams.  Did they discharge
in 2006?  03A and 03 B refer to a north and south ash pond.  Does the
plant operate two ash ponds (only one is indicated on the process
diagram and in the wastewater treatment tables)?

A:  See attached table.

The plant operates one large ash pond that has a north and a south end.

9	N	47	B-28	Q: Regarding Diagram 5-1, please confirm that no wastewater
treatment occurs in the Low Volume Waste Basin.

A:  Confirmed.

10	N	47	B-28	Q: For WWT-1 (Diagram 5-1), please confirm that pH
adjustment occurs within (as part of) the ash pond and not within a
separate tank/pond as indicated in the diagram.

A:  pH adjustment occurs in the discharge line from the ash pond to the
retention pond.

11	N	47	B-28	Q: On Diagram 5-1, there is more wastewater shown entering
the ash pond than exiting.  Please confirm that the reason for this is
evaporation.

A:  The reason is a combination of evaporation and rain water entering
the pond.

12	N	47	B-28	Q: For WWT-2 (Diagram 5-2), please confirm that pH
adjustment and chemical precipitation occur within the settling pond and
not within separate vessels as shown on the diagram?  What chemicals are
typically added for chemical precipitation?

A:  Confirmed.  The plant has added “advanced chemicals” to the
settling pond in the past, but did not add any chemicals in 2006.

13	N	47	B-28	Q: For WWT-3 (Diagram 5-3), is the effluent from the coal
pile runoff pond continuous at 30 gpm or intermittent?

A:  The response for Table 19 is more accurate.

14	N	49	B-32	Q: For WWT-2, does the plant operate two settling ponds
(only one is shown on Diagram 5-2)?  If so, what is the volume and
wastewater residence time in each pond?

A:  The plant operates only one basin for WWT-2 and the wastewater
residence time is indefinite.

15	N	49	B-32	Q: For WWT-3, does the plant operate two settling ponds
(only one is shown on Diagram 5-3)?  If so, what is the volume and
wastewater residence time in each pond?

A:  The plant operates two WWT-3 settling ponds that are identical.  The
volume for each is half of the total volume given in Table 17 (37,000
m3) and the wastewater residence time is 82 hours for each pond.

16	N	51	B-33	Q: For WWT-1, the “Average Dose Concentration” of
sulfuric acid is listed as “Not measured – varies as necessary for
pH”.  As requested in EPA’s email to UWAG on 7/11/07, please provide
the concentration of the active ingredient added (i.e., the amount of
active ingredient contained in the chemical product).

A:  93% sulfuric acid.

17	N	52	B-34	Q: For WWT-1, did FAS, BAS, and PMRS enter the ash pond 24
hpd and 365 dpy?  Was the recycle from the ash pond used for RECYC-FAS,
RECYC-BAS, and RECYC-PMRS 24 hpd and 365 dpy?

A:  Yes.  Yes.


[Federal Register Volume 77, Number 110 (Thursday, June 7, 2012)]
[Notices]
[Pages 33794-33796]
[FR Doc No: 2012-13767]

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

SECURITIES AND EXCHANGE COMMISSION

[Release No. 34-67095; File No. SR-OCC-2012-08]

Self-Regulatory Organizations; The Options Clearing Corporation;
Notice of Filing of Proposed Rule Change Relating to Amendments to
Certain Rules Applicable to Stock Futures

June 1, 2012.
    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934
(``Act'') \1\ and Rule 19b-4 thereunder \2\ notice is hereby given that
on May 24, 2012, The Options Clearing Corporation (``OCC'') filed with
the Securities and Exchange Commission (``Commission'') the proposed
rule change as described in Items I and II below, which Items have been
prepared primarily by OCC. 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\ 17 CFR 240.19b-4.
---------------------------------------------------------------------------

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

    Several separate purposes underlie the proposed rule change. First,
the rule change clarifies the applicability of OCC's rules to stock
futures overlying index-linked securities. Second, it eliminates a de
minimis exception relating to adjustments to stock futures overlying
ETFs. Third, it makes a technical change to the rules that permit the
acceleration of the maturity (expiration) date of stock futures (stock
options) following an adjustment in response to cash-out events.

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

    In its filing with the Commission, OCC 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 these statements may be examined at the places specified in
Item IV below. The self-regulatory organization has prepared summaries,
set forth in sections (A), (B), and (C) below, of the most significant
aspects of such statements.\3\
---------------------------------------------------------------------------

    \3\ The Commission has modified the text of the summaries
prepared by OCC.
---------------------------------------------------------------------------

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

    The first purpose of this proposed rule change is to clarify the
applicability of OCC's By-Laws and Rules to security futures on index-
linked securities such as exchange-traded notes, which are currently
traded on OneChicago, LLC. Index-linked securities are non-convertible
debt of a major financial institution that typically have a term of at
least one year but not greater than thirty years and that provide for
payment at maturity based upon the performance of an index or indexes
of equity securities or futures contracts, one or more physical
commodities, currencies or debt securities, or a combination of any of
the foregoing. Index-linked securities are traded on national
securities exchanges and, although they are technically debt
securities, meet the definition of ``NMS stock'' under Regulation
NMS.\4\ Furthermore, index-linked securities traded on designated
contract markets meet the requirements of Commodity Futures Trading
Commission Regulation 41.21 for the underlying securities of security
futures products that are eligible to be treated as a single security.
OneChicago therefore treats security futures on index-linked securities
as security futures on single securities, or ``single stock futures,''
for listing and trading purposes, and trading in them will generally be
governed by the same rules that are applicable to other single stock
futures. OCC similarly treats futures on index-linked securities as
single stock futures, and accordingly is proposing to amend the
definition of ``stock future'' in Article I of its By-Laws to
explicitly include index-linked securities.\5\
---------------------------------------------------------------------------

    \4\ ``NMS stock'' is defined in Rule 600(b)(47) of Regulation
NMS to mean ``any NMS security other than an option.'' ``NMS
security'' is defined in Rule 600(b)(46) to mean any security for
which transaction reports are collected and disseminated under an
effective national market system plan, and because index-linked
securities are exchange traded they fall within this definition.
    \5\ Article I of OCC's By-Laws defines ``index-linked security''
to mean ``a debt security listed on a national securities exchange,
the payment upon maturity of which is based in whole or in part upon
the performance of an index or indexes of equity securities or
futures contracts, one or more physical commodities, currencies or
debt securities, or a combination of any of the foregoing.''
---------------------------------------------------------------------------

    In addition to amending the definition of ``stock future'' to
reference index-linked securities, OCC is proposing to amend
Interpretation and Policy .05 to Article XII, Section 3 of its By-Laws
to clarify that a call of an entire class of index-linked securities
will result in an adjustment of security futures on index-linked
securities similar to the adjustment that would be made to other stock
futures in the event of a cash merger, but that a partial call will not
result in an adjustment. OCC is also proposing to add Interpretation
and Policy .11 to Article XII, Section 3 of its By-Laws to establish
that interest payments on index-linked securities will generally be
considered ``ordinary cash dividends or distributions'' within the
meaning of paragraph (c) of Section 3. The proposed amendments parallel
amendments previously made to Article VI, Section 11A of the By-Laws to
accommodate options on index-linked securities.\6\
---------------------------------------------------------------------------

    \6\ Securities Exchange Act Release No. 34-60872 (October 23,
2009), 74 FR 55878 (October 29, 2009).
---------------------------------------------------------------------------

    The second purpose of this proposed rule change is to amend
Interpretation and Policy .08 to Article XII, Section 3, which provides
that OCC will ordinarily adjust for capital gains distributions on
underlying ``fund shares,'' i.e., shares of exchange-traded funds
(``ETFs'') but with a de minimis exception under which no adjustment
will be made in respect of distributions of less than $.125 per fund
share. (An equivalent de minimis provision is contained in the
Interpretations and Policies to Article VI, Section 11A, governing
stock options.) However, in the case of stock futures, OneChicago, the
only futures exchange clearing through OCC that currently trades such
futures, has requested that adjustments be made for capital gains
distributions in respect of fund shares without exception in order to
permit the stock futures on ETFs to more closely reflect the economic
characteristics of the ETFs' underlying stocks. This revision to the
provision for fund shares futures will establish consistency with
Interpretation and Policy .01(b) to Article XII, Section 3 which also
does not contain a de minimis threshold for stock futures adjusted for
cash distributions. Accordingly, OCC is proposing to amend
Interpretation and Policy .08 to eliminate the de minimis exception.
    Additionally, OCC proposes to make a technical correction to Rule
1304, which permits the acceleration of the maturity date for stock
futures adjusted to require the delivery of cash, and Rule 807, which
permits the acceleration of the expiration date of stock options
adjusted to require the delivery of cash. Rules 1304 and 807 contain
language that could be read to suggest that such acceleration would
occur only in the event of a cash-out merger. However, cash-outs also
may occur as a result of bankruptcies, ADS liquidations and other
events, and there is no reason to limit such accelerations to cash-out
merger events. Accordingly, OCC proposes to amend Rules 1304 and 807 to
delete language that may be perceived to limit OCC's ability to
accelerate a maturity or expiration date to such events. OCC is also
proposing to delete as obsolete a version of Rule 807 that was
effective before January 1, 2008, and related language regarding the
effective date in what would now be the only version of Rule 807.
    OCC believes that the proposed changes to OCC's By-Laws are
consistent with the purposes and requirements of Section 17A of the Act
\7\ and the rules and regulations thereunder applicable to OCC because
they will promote the prompt and accurate clearance and settlement of
securities transactions by clarifying that security futures on index-
linked securities will be cleared and settled subject to the same rules
and procedures that are used successfully by OCC to clear and settle
stock futures, eliminating an unnecessary de minimis threshold for
adjusting stock futures on

ETFs, and clarifying OCC's ability to accelerate maturity dates of
stock futures or expiration dates of stock options in events other than
cash-out merger events and eliminating obsolete rules or references.
The proposed rule change is not inconsistent with any rules of OCC,
including any that are proposed to be amended.
---------------------------------------------------------------------------

    \7\ 15 U.S.C. 78q-1.
---------------------------------------------------------------------------

(B) Self-Regulatory Organization's Statement on Burden on Competition

    OCC does not believe that the proposed rule change would impose any
burden on competition.

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

    Written comments relating to the proposed rule change have not been
solicited or received. OCC will notify the Commission of any written
comments received by OCC.

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

    Within 45 days of the date of publication of this notice in the
Federal Register or within such longer period up to 90 days (i) as the
Commission may designate if it finds such longer period to be
appropriate and publishes its reasons for so finding or (ii) as to
which the self-regulatory organization consents, the Commission will:
    (A) By order approve or disapprove the proposed rule change or
    (B) Institute proceedings to determine whether the proposed rule
change should be 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_ADDRESS>Please include
File Number SR-OCC-2012-08 on the subject line.

Paper Comments

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

All submissions should refer to File Number SR-OCC-2012-08. 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 Section, 100 F Street
NE., Washington, DC 20549-1090, on official business days between the
hours of 10:00 a.m. and 3:00 p.m. Copies of such filing will also be
available for inspection and copying at the principal office of OCC and
on OCC's Web site at http://www.theocc.com/components/docs/legal/rules_and_bylaws/sr_occ_12_08.pdf. 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-OCC-2012-08 and should be submitted on
or before June 28, 2012.

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

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

Kevin M. O'Neill,
Deputy Secretary.
[FR Doc. 2012-13767 Filed 6-6-12; 8:45 am]
BILLING CODE 8011-01-P


[Federal Register: December 20, 2007 (Volume 72, Number 244)]
[Notices]
[Page 72348]
[DOCID:fr20de07-41]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Docket No. ID-3110-001]

Louder, Stephen R.; Notice of Filing

December 13, 2007.
    Take notice that on December 12, 2007, pursuant to section 305(b)
of the Federal Power Act, 16 U.S.C. 825d(b) (2006), Part 45 of the
Commission's Rules of Practice and Procedure, 18 CFR part 45 (2006),
and Order No. 664, Commission Authorization to Hold Interlocking
Positions, 112 FERC ] 61,298 (2005); order on reh'g, 114 FERC ] 61,142
(2006), Stephen R. Louder filed a revised page 1 and page 7 of his
application for authorization to hold interlocking positions. The
revision on page 1 deletes the word ``Director'' in the second line of
the first paragraph under Introductions and replaces that language with
``Secretary/Treasurer'' to correct an inadvertent typographical error.
The revision on page 7 eliminates language relating to the confidential
nature of Mr. Louder's estimated 2007 compensation from Golden Spread
and inserts in lieu thereof the estimated value for that compensation.
    Any person desiring to intervene or to protest this filing must
file in accordance with Rules 211 and 214 of the Commission's Rules of
Practice and Procedure (18 CFR 385.211, 385.214). Protests will be
considered by the Commission in determining the appropriate action to
be taken, but will not serve to make protestants parties to the
proceeding. Any person wishing to become a party must file a notice of
intervention or motion to intervene, as appropriate. Such notices,
motions, or protests must be filed on or before the comment date.
Anyone filing a motion to intervene or protest must serve a copy of
that document on the Applicant and all the parties in this proceeding.
    The Commission encourages electronic submission of protests and
interventions in lieu of paper using the ``eFiling'' link at http://www.ferc.gov.
 Persons unable to file electronically should submit an

original and 14 copies of the protest or intervention to the Federal
Energy Regulatory Commission, 888 First Street, NE., Washington, DC
20426.
    This filing is accessible on-line at http://www.ferc.gov, using the

``eLibrary'' link and is available for review in the Commission's
Public Reference Room in Washington, DC. There is an ``eSubscription''
link on the Web site that enables subscribers to receive e-mail
notification when a document is added to a subscribed docket(s). For
assistance with any FERC Online service, please e-mail
<EMAIL_ADDRESS>or call<PHONE_NUMBER> (toll free). For

TTY, call<PHONE_NUMBER>.
    Comment Date: 5 p.m. Eastern Time on December 26, 2007.

Kimberly D. Bose,
Secretary.
 [FR Doc. E7-24668 Filed 12-19-07; 8:45 am]

BILLING CODE 6717-01-P


[Federal Register: June 23, 2010 (Volume 75, Number 120)]
[Rules and Regulations]
[Page 35651-35652]
[DOCID:fr23jn10-20]

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

DEPARTMENT OF HOMELAND SECURITY

Coast Guard

33 CFR Part 165

[Docket No. USCG 2010-0367]

Safety Zone; San Francisco Chronicle Fireworks Display, San
Francisco, CA

AGENCY: Coast Guard, DHS.

ACTION: Notice of enforcement of regulation.

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

SUMMARY: The Coast Guard will enforce the Independence Day Celebration
for the City of San Francisco Fireworks safety zone from 11 a.m.
through 10 p.m. on July 4, 2010. The fireworks will be fired
simultaneously from two separate locations. This action is necessary to
control vessel traffic and to ensure the safety of event participants
and spectators. During the enforcement period, unauthorized persons or
vessels are prohibited from entering into, transiting through, or
anchoring in the safety zone, unless authorized by the Patrol Commander
(PATCOM).

DATES: The regulations in 33 CFR 165.1191 will be enforced from 11 a.m.
through 10 p.m. on July 4, 2010.

FOR FURTHER INFORMATION CONTACT: If you have questions on this notice,
call or e-mail Lieutenant Simone Mausz, U.S. Coast Guard, Waterways
Safety Division; telephone<PHONE_NUMBER>, e-mail D11-PF-
<EMAIL_ADDRESS>
SUPPLEMENTARY INFORMATION:
    The Coast Guard will enforce the Independence Day Celebration for
the City of San Francisco Fireworks safety zone from 11 a.m. through 10
p.m. on July 4, 2010. The fireworks will be fired simultaneously from
two separate locations: Location 1 will be held 1,000 feet from Pier 39
in position 37[deg]48.710' N and 122[deg]24.464' W and Location 2 will
be fired from the Municipal Pier in Aquatic Park in position
37[deg]48.611' N and 122[deg]25.532' W on July 4, 2010.
    For Location 1, while the barge is being towed to the display
location, and until fifteen minutes before the start of the fireworks
display, the safety zone applies to the navigable waters around and
under the fireworks barge within a radius of 100 feet. Fifteen minutes
before and during the fireworks display,

the area to which this safety zone applies to will increase in size to
encompass the navigable waters around and under the fireworks barge
within a radius of 1,000 feet. Loading of the pyrotechnics onto the
fireworks barge is scheduled to commence at 11 a.m. on July 4, 2010,
and will take place at Pier 50 in San Francisco. Towing of the barge
from Pier 50 to the display location is scheduled to take place on July
4, 2010 at 8 p.m. During the fireworks display, scheduled to start at
approximately 9:30 p.m., the fireworks barge will be located
approximately 1,000 feet off of Pier 39 in position 37[deg]48.710' N,
122[deg]24.464' W (NAD 83). This safety zone will be enforced from 11
a.m. to 10:00 p.m. on July 4, 2010.
    For Location 2, the fireworks will be launched from the Municipal
Pier in position 37[deg]48.611' N, 122[deg]25.532' W (NAD 83). The
safety zone will apply to the navigable waters around and under the
fireworks site within a radius of 500 feet. The fireworks display is
scheduled to launch at 9:30 p.m. and will last approximately twenty
five minutes. This safety zone will be enforced from 9 p.m. to 10 p.m.
on July 4, 2010.
    Under the provisions of 33 CFR 165.1191, unauthorized persons or
vessels are prohibited from entering into, transiting through, or
anchoring in the safety zone during all applicable effective dates and
times, unless authorized to do so by the PATCOM. Additionally, each
person who receives notice of a lawful order or direction issued by an
official patrol vessel shall obey the order of direction. The PATCOM is
empowered to forbid entry into and control the regulated area. The
PATCOM shall be designated by the Commander, Coast Guard Sector San
Francisco. The PATCOM may, upon request, allow the transit of
commercial vessels through regulated areas when it is safe to do so.
    This notice is issued under authority of 33 CFR 165.1191 and 5
U.S.C. 552(a). In addition to this notice in the Federal Register, the
Coast Guard will provide the maritime community with extensive advance
notification of this enforcement period via the Local Notice to
Mariners. If the Captain of the Port determines that the regulated area
need not be enforced for the full duration stated in this notice, he or
she may use a Broadcast Notice to Mariners to grant general permission
to enter the regulated area.

    Dated: June 11, 2010.
P. M. Gugg,
Captain, U.S. Coast Guard, Captain of the Port San Francisco.
[FR Doc. 2010-15153 Filed 6-22-10; 8:45 am]
BILLING CODE 9110-04-P