	ENVIRONMENTAL PROTECTION AGENCY

	40 CFR Part 52

	[EPA-R03-OAR-2009-0706; FRL-       ]

	Approval and Promulgation of Air Quality Implementation Plans;

	West Virginia; Removal of NOx SIP Call Rules

AGENCY:     Environmental Protection Agency (EPA).

ACTION:     Direct final rule.

SUMMARY:  EPA is taking direct final action to approve a revision to the
West Virginia State Implementation Plan (SIP).  The revision removes
West Virginia’s nitrogen oxides (NOx) SIP Call rules.  EPA is
approving this revision to remove West Virginia’s NOx SIP Call rules
in accordance with the requirements of the Clean Air Act (CAA).

DATES:  This rule is effective on [Insert date 60 days after publication
in the Federal Register]  without further notice, unless EPA receives
adverse written comment by [Insert date 30 days after publication in the
Federal Register].  If EPA receives such comments, it will publish a
timely withdrawal of the direct final rule in the Federal Register and
inform the public that the rule will not take effect.

ADDRESSES:  Submit your comments, identified by Docket ID Number
EPA-R03-OAR-2009-0706 by one of the following methods:

 www.regulations.gov.  Follow the on-line instructions for submitting
comments.

B.    E-mail<EMAIL_ADDRESS>
C.    Mail:   EPA-R03-OAR-2009-0706, Cristina Fernandez, Associate
Director, Office of Air Program Planning, Mailcode 3AP30, U.S.
Environmental Protection Agency, Region III, 1650 Arch Street,
Philadelphia, Pennsylvania 19103.

D.   Hand Delivery: At the previously-listed EPA Region III address.
Such deliveries are only accepted during the Docket’s normal hours of
operation, and special arrangements should be made for deliveries of
boxed information.

Instructions:  Direct your comments to Docket ID No.
EPA-R03-OAR-2009-0706.  EPA's policy is that all comments received will
be included in the public docket without change, and may be made
available online at 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 www.regulations.gov or
e-mail.  The www.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
www.regulations.gov, your e-mail address will be automatically captured
and included as part of the comment that is placed in the public 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 electronic docket are listed in the
www.regulations.gov index. Although listed in the index, some
information is not publicly available, i.e., 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 electronically in www.regulations.gov or
in hard copy during normal business hours at the Air Protection
Division, U.S. Environmental Protection Agency, Region III, 1650 Arch
Street, Philadelphia, Pennsylvania 19103.  Copies of the State submittal
are available at the West Virginia Department of Environmental
Protection, Division of Air Quality, 601 57th Street SE, Charleston,
West Virginia 25304.

FOR FURTHER INFORMATION CONTACT: Marilyn Powers,<PHONE_NUMBER>, or by
e-mail at<EMAIL_ADDRESS>

SUPPLEMENTARY INFORMATION:

I.  Background

Throughout this document, whenever “we,” “us,” or “our” is
used, we mean EPA.

On July 20, 2009, the State of West Virginia submitted a formal revision
to its SIP.  The SIP revision removes West Virginia’s NOx SIP Call
rules.  West Virginia’s NOx SIP Call rules, approved into the West
Virginia SIP on May 10, 2002 (67 FR 31733) and September 28, 2006 (71 FR
56881), established West Virginia’s NOx Budget Trading Program and set
forth requirements for its non-trading sources, respectively.  The
former enabled West Virginia to participate in the EPA-administered
regional NOx budget trading program under the NOx SIP Call.  However,
EPA discontinued the NOx SIP Call trading program after the 2008 ozone
season, and starting in 2009, began administration of the trading
programs under the Clean Air Interstate Rule (CAIR).  CAIR established
three separate emissions trading programs.  One of these, the CAIR ozone
season NOx trading program, applies to the electric generating units
(EGUs) that are subject to the NOx SIP Call but does not apply to the
non-EGUs that were also trading sources under the NOx SIP Call.  To help
States address these sources, CAIR provided States with the flexibility
to include the non-EGUs as part of their CAIR ozone season NOx trading
program.  West Virginia chose to bring these non-EGUs into its CAIR
ozone season NOx trading program by including them in regulation 45CSR40
- Control of Ozone Season Nitrogen Oxide Emissions to Mitigate
Interstate Transport of Ozone and Nitrogen Oxides CAIR.  In addition,
West Virginia chose to recodify the provisions for its non-trading
non-EGUs (internal combustion engines and cement kilns) that were
included in 45CSR1 into 45CSR40.  On August 4, 2009 (74 FR 38536), EPA
approved West Virginia’s CAIR trading programs into the West Virginia
SIP.  West Virginia’s NOx SIP Call requirements have therefore been
subsumed by the State’s CAIR ozone season NOx trading program.

II.	Summary of SIP Revision

West Virginia met its NOx SIP Call requirements through two regulations:
45CSR1 – Control and Reduction of Nitrogen Oxides from Non-Electric
Generating Units As a Means to Mitigate Transport of Ozone Precursors;
and 45CSR26 – NOx Budget Trading Program as a Means of Control and
Reduction of Nitrogen Oxides from Electric Generating Units.  This SIP
revision removes these two regulations.  West Virginia is meeting its
NOx SIP Call emission reduction requirements by its approved CAIR ozone
season NOx trading program, codified in 45CSR40.

III.	Final Action

EPA is approving the SIP revision submitted by West Virginia to remove
its NOx SIP Call rules 45CSR1 and 45CSR26.  West Virginia continues to
meet its NOx SIP Call requirements through its SIP-approved CAIR ozone
season NOx trading program.

EPA is publishing this rule without prior proposal because the Agency
views this as a noncontroversial amendment and anticipates no adverse
comment.  However, in the Proposed Rules( section of today(s Federal
Register, EPA is publishing a separate document that will serve as the
proposal to approve the SIP revision if adverse comments are filed.
This rule will be effective on [Insert date 60 days from date of
publication in the Federal Register] without further notice unless EPA
receives adverse comment by [Insert date 30 days from date of
publication in the Federal Register].  If EPA receives adverse comment,
EPA will publish a timely withdrawal in the Federal Register informing
the public that the rule will not take effect.  EPA will address all
public comments in a subsequent final rule based on the proposed rule.
EPA will not institute a second comment period on this action.  Any
parties interested in commenting must do so at this time.  Please note
that if EPA receives adverse comment on an amendment, paragraph, or
section of this rule and if that provision may be severed from the
remainder of the rule, EPA may adopt as final those provisions of the
rule that are not the subject of an adverse comment.

IV. Statutory and Executive Order Reviews

A.   General Requirements

Under the Clean Air Act, the Administrator is required to approve a SIP
submission that complies with the provisions of the Act and applicable
Federal regulations.  42 U.S.C. 7410(k); 40 CFR 52.02(a).  Thus, in
reviewing SIP submissions, EPA’s role is to approve state choices,
provided that they meet the criteria of the Clean Air Act.  Accordingly,
this action merely approves state law as meeting Federal requirements
and does not impose additional requirements beyond those imposed by
state law.  For that reason, this action:

is not a "significant regulatory action” subject to review by the
Office of Management and Budget under Executive Order 12866 (58 FR
51735, October 4, 1993);

does not impose an information collection burden under the provisions of
the Paperwork Reduction Act (44 U.S.C. 3501 et seq.);

is certified as not having a significant economic impact on a
substantial number of small entities under the Regulatory Flexibility
Act (5 U.S.C. 601 et seq.);

does not contain any unfunded mandate or significantly or uniquely
affect small governments, as described in the Unfunded Mandates Reform
Act of 1995 (Public Law 104-4);

does not have Federalism implications as specified in Executive Order
13132 (64 FR 43255, August 10, 1999);

is not an economically significant regulatory action based on health or
safety risks subject to Executive Order 13045 (62 FR 19885, April 23,
1997);

is not a significant regulatory action subject to Executive Order 13211
(66 FR 28355, May 22, 2001);

is not subject to requirements of Section 12(d) of the National
Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note)
because application of those requirements would be inconsistent with the
Clean Air Act; and

does not provide EPA with the discretionary authority to address, as
appropriate, disproportionate human health or environmental effects,
using practicable and legally permissible methods, under Executive Order
12898 (59 FR 7629, February 16, 1994).

In addition, this rule does not have tribal implications as specified by
Executive Order 13175 (65 FR 67249, November 9, 2000), because the SIP
is not approved to apply in Indian country located in the state, and EPA
notes that it will not impose substantial direct costs on tribal
governments or preempt tribal law.

B.   Submission to Congress and the Comptroller General

The Congressional Review Act, 5 U.S.C. 801 et seq., as added by the
Small Business Regulatory Enforcement Fairness Act of 1996, generally
provides that before a rule may take effect, the agency promulgating the
rule must submit a rule report, which includes a copy of the rule, to
each House of the Congress and to the Comptroller General of the United
States.  EPA will submit a report containing this action and other
required information to the U.S. Senate, the U.S. House of
Representatives, and the Comptroller General of the United States prior
to publication of the rule in the Federal Register.  A major rule cannot
take effect until 60 days after it is published in the Federal Register.
 This action is not a “major rule” as defined by 5 U.S.C. 804(2).

C.  Petitions for Judicial Review

Under section 307(b)(1) of the Clean Air Act, petitions for judicial
review of this action must be filed in the United States Court of
Appeals for the appropriate circuit by [Insert date 60 days from date of
publication of this document in the Federal Register].  Filing a
petition for reconsideration by the Administrator of this final rule
does not affect the finality of this action for the purposes of judicial
review nor does it extend the time within which a petition for judicial
review may be filed, and shall not postpone the effectiveness of such
rule or action.  Parties with objections to this direct final rule are
encouraged to file a comment in response to the parallel notice of
proposed rulemaking for this action published in the proposed rules
section of today's Federal Register, rather than file an immediate
petition for judicial review of this direct final rule, so that EPA can
withdraw this direct final rule and address the comment in the proposed
rulemaking.

This action to approve the West Virginia SIP revision that removes the
State’s NOx SIP Call rules may not be challenged later in proceedings
to enforce its requirements.  (See section 307(b)(2).)

List of Subjects in 40 CFR Part 52

Environmental protection, Air pollution control, Incorporation by
reference, Nitrogen dioxide, Ozone, Particulate matter.

           W. C. Early, Acting

            Regional Administrator

_January 22, 2010____
__________________________

Dated:                                				Shawn M. Garvin,

                                      				Regional Administrator,

                                      				Region III.

40 CFR Part 52 is amended as follows:

PART 52 - [AMENDED]

1.  The authority citation for part 52 continues to read as follows:

               Authority:  42 U.S.C. 7401 et seq.

Subpart XX ( West Virginia

2.  In § 52.2520, the table in paragraph (c) is amended by removing the
entries for 45CSR Series 1 and 45CSR Series 26 in their entirety.

 PAGE

 PAGE

 PAGE  10


[Federal Register Volume 84, Number 35 (Thursday, February 21, 2019)]
[Notices]
[Pages 5532-5536]
[FR Doc No: 2019-02891]

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

SECURITIES AND EXCHANGE COMMISSION

[Release No. 34-85131; File No. SR-BX-2019-001]

Self-Regulatory Organizations; Nasdaq BX, Inc.; Notice of Filing
and Immediate Effectiveness of Proposed Rule Change To Amend Options 7,
Section 2

February 14, 2019.
    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 January 31, 2019, Nasdaq BX, Inc.
(``BX'' or ``Exchange'') filed with the Securities and Exchange
Commission (``SEC'' or ``Commission'') the proposed rule change as
described in Items I and II, 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 amend Options 7, Section 2, which sets
forth fees and rebates for the Exchange's options market (``BX
Options''), to adopt language that allows the Exchange to remove a day
from its options volume calculations for purposes of determining
pricing tiers.
    The text of the proposed rule change is available on the Exchange's
website at http://nasdaqbx.cchwallstreet.com/, at the principal office
of the Exchange, and at the Commission's Public Reference Room.

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

    In its filing with the Commission, the 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
Statutory Basis for, the Proposed Rule Change

1. Purpose
    Today, the Exchange offers a number of pricing incentives based on
volume calculations that are designed to encourage participation in BX
Options through rebates or reduced fees for Participants that trade on
BX Options in increasingly higher volumes.\3\ The Exchange now proposes
to adopt language in Section 2 that would allow it to exclude certain
days from such volume calculations for purposes of determining pricing
tiers. The Exchange is standardizing its practice for removing a day
from options volume calculations in its Pricing Schedule with its
affiliated options market, Nasdaq Phlx (``Phlx'').\4\
---------------------------------------------------------------------------

    \3\ For instance, the Exchange currently offers BX Options
Market Makers and Customers tiered rebates and fees for adding or
removing liquidity in Penny Pilot and Non-Penny Pilot Options that
are based on average daily volume (``ADV'') calculations. See
Options 7, Section 2(1).
    \4\ See Phlx Pricing Schedule, Options 7, Section 1(b). The
Exchange's other affiliated options markets, Nasdaq ISE, Nasdaq
GEMX, Nasdaq MRX, and The Nasdaq Options Market will also file
similar rule change proposals to conform to Phlx's rule.
---------------------------------------------------------------------------

    Specifically in Options 7, Section 2, the Exchange proposes to
adopt new subsection (6) with the title ``Removal of Days for Purposes
of Pricing Tiers,'' which will provide:
    (i)(A) Any day that the Exchange announces in advance that it will
not be open for trading will be excluded from the options tier
calculations set forth in its Pricing Schedule; and (B) any day with a
scheduled early market close (``Scheduled Early Close'') may be
excluded from the options tier calculations only pursuant to paragraph
(iii) below.
    (ii) The Exchange may exclude the following days (``Unanticipated
Events'') from the options tier calculations only pursuant to paragraph
(iii) below, specifically any day that: (A) The market is not open for
the entire trading day, (B) the Exchange instructs Participants in
writing to route their orders to other markets, (C) the Exchange is
inaccessible to Participants during the 30-minute period before the
opening of trade due to an Exchange system disruption, or (D) the
Exchange's system experiences a disruption that lasts for more than 60
minutes during regular trading hours.
    (iii) If a day is to be excluded as a result of paragraph (i)(B) or
(ii) above, the Exchange will exclude the day from any Participant's
monthly options tier calculations as follows:

    (A) the Exchange may exclude from the ADV calculation any
Scheduled Early Close or Unanticipated Event; and
    (B) the Exchange may exclude from any other applicable options
tier calculation provided for in its Pricing Schedule (together with
(iii)(A), ``Tier Calculations'') any Scheduled Early Close or
Unanticipated Event.

provided, in each case, that the Exchange will only remove the day for
Participants that would have a lower Tier Calculation with the day
included.
    The proposed language would: (1) Allow the Exchange to remove a day
from its volume calculations in Options 7, Section 2 \5\ in a number of
specified circumstances, which typically result in artificially low
volume days, (2) categorize potential excluded days as those that are
known in advance (i.e., days in proposed paragraph (i), including
Scheduled Early Closes), and those that are not (i.e., Unanticipated
Events in proposed paragraph (ii)), and (3) allow the Exchange to
remove a day only when doing so would be beneficial for the Participant
(i.e., only if the Participant would have a lower ADV calculation with
the day included, hereinafter, the ``better of rule''). As it relates
to Unanticipated Events, the Exchange will inform all Participants if
any such day will be excluded from its Tier Calculations via a system
status message disseminated to all Participants. The Exchange notes
that it is not proposing to amend the thresholds a Participant must
achieve to become eligible for, or the dollar amount associated with,
the tiered rebates or fees.
---------------------------------------------------------------------------

    \5\ See note 3 above.
---------------------------------------------------------------------------

Potential Excluded Days
    As noted above, the proposal will allow the Exchange to remove days
from Participants' volume calculations in a number of circumstances
that generally result in artificially low volume days. First, the
Exchange proposes to adopt language identical to Phlx providing that it
will always exclude days where the Exchange announces in advance that
it will not be open for trading (e.g., Thanksgiving) from all options
tier calculations set forth in its Pricing Schedule.\6\ This is also
the case today since no trading activity occurs on those days, and the
Exchange is only clarifying its current practice within the proposed
rule. Second, the Exchange proposes to adopt language that would permit
the Exchange to exclude any Scheduled Early Close from its volume
calculations. The Exchange believes that Scheduled Early Closes, which
typically are days before or after a holiday, may preclude some
Participants from submitting orders to the Exchange at the same level
as they might otherwise. This proposal is consistent with the treatment
of such days on Phlx.\7\
---------------------------------------------------------------------------

    \6\ See note 4 above at paragraph (1)(A).
    \7\ See id. at paragraph (1)(B).
---------------------------------------------------------------------------

    Third, the Exchange proposes language allowing it to exclude days
where the market is not open for the entire trading day, such as days
where the Exchange declares a trading halt in all securities or honors
a market-wide trading halt declared by another market, because those
days typically have lower trading volume. This is consistent with
Phlx's practice for removing such days from its volume calculations.\8\
---------------------------------------------------------------------------

    \8\ See id. at paragraph (2)(A).
---------------------------------------------------------------------------

    Fourth, Phlx adopted the language on instructing members to route
away to

prevent situations where days that have artificially lower volume could
not be excluded, for example, because Phlx experienced an issue in the
morning that ultimately did not carry over into the trading day.\9\
Like Phlx, the Exchange believes that it should have the flexibility to
exclude days if Participants have been instructed to send their orders
elsewhere, regardless of whether the issue that resulted in this
instruction ultimately impacts the availability of the Exchange for
trading.
---------------------------------------------------------------------------

    \9\ See id. at paragraph (2)(B).
---------------------------------------------------------------------------

    Fifth, the Exchange proposes to adopt identical language as Phlx to
exclude days where the Exchange is inaccessible to Participants during
the 30-minute period before the opening of trade (i.e., between 9:00
a.m. to 9:30 a.m. Eastern Time) due to an Exchange system
disruption.\10\ While the language proposed above on instructing
Participants to route away may also cover Exchange system disruptions
that occur before the market opens, the Exchange notes that it may not
always instruct Participants to route away in such instances. For
example, the Exchange may be inaccessible to Participants in the
morning due to a systems disruption but the Exchange resolves the issue
shortly before 9:30 a.m. and as a result, the Exchange does not
instruct Participants to route away. In this instance, the Exchange
would not be permitted to exclude the day from its volume calculations.
The Exchange generally experiences a high volume of member
participation within the 30-minute window leading up to the opening of
trade from Participants who submit eligible interest to be included in
the Exchange's opening process. As a result, days where Participants
are precluded from submitting eligible interest during this 30-minute
time period due to an Exchange systems disruption, even if the issue is
ultimately resolved by the Exchange before the market opens (and
Participants therefore are not instructed to route away), are likely to
have lower trading volume. Including such days in calculations of ADV
will therefore make it more difficult for Participants to achieve
particular pricing tiers for that month. Accordingly, excluding such
days from the monthly tier calculations will diminish the likelihood of
a cost increase occurring because a Participant is not able to reach a
pricing tier on that date that it would reach on other trading days
during the month.
---------------------------------------------------------------------------

    \10\ See id. at paragraph (2)(C).
---------------------------------------------------------------------------

    Sixth, the Exchange proposes to adopt language identical to Phlx to
exclude days where there is an Exchange system disruption that lasts
for more than 60 minutes during regular trading hours (i.e., 9:30 a.m.
to 4:00 p.m. Eastern Time), even if such disruption would not be
categorized as a complete outage of the Exchange's system.\11\ Such a
disruption may occur where a certain options series traded on the
Exchange is unavailable for trading due to an Exchange systems issue,
or where the Exchange may be able to perform certain functions with
respect to accepting and processing orders, but may have a failure to
another significant process, such as routing to other market centers,
that would lead Participants who rely on such processes to avoid using
the Exchange until the Exchange's entire system was operational. The
Exchange believes that certain system disruptions that are not complete
system outages could preclude some Participants from submitting orders
to the Exchange. The Exchange also notes that this proposal is
consistent with the rules of other options exchanges.\12\
---------------------------------------------------------------------------

    \11\ See id. at paragraph 2(D).
    \12\ See BATS BZX Options Exchange Fee Schedule (defining an
``Exchange System Disruption'' as any day that the exchange's system
experiences a disruption that lasts for more than 60 minutes during
regular trading hours); and NYSE Arca Options Fee Schedule (defining
an ``Exchange System Disruption'' as a disruption affects an
Exchange system that lasts for more than 60 minutes during regular
trading hours).
---------------------------------------------------------------------------

    Because the potential excluded days proposed above generally have
artificially lower trading volume, the Exchange believes it is
reasonable and equitable to exclude such days in determining its fee
and rebate tiers. The Exchange desires to avoid penalizing Participants
that might otherwise qualify for certain tiered pricing but that,
because of special circumstances on a particular day, did not
participate on the Exchange to the extent that they might have
otherwise participated. Absent the authority to exclude such days,
Participants may experience an effective increase in the cost of
trading on BX Options, a result that is both unintended and undesirable
to the Exchange and to its Participants.
Categories of Excluded Days
    In light of the foregoing proposal, the Exchange seeks to
categorize the potential excluded days proposed above between days that
are known in paragraph (i) and days that are not in paragraph (ii), and
define the latter as Unanticipated Events. Specifically, paragraph (i)
would set forth days that the Exchange announces in advance that it
will not be open for trading in paragraph (i)(A), and Scheduled Early
Closes in paragraph (ii)(B), as further described above. The
Unanticipated Events in paragraph (ii) would cover the days where the
Exchange is not open for the entire trading day (e.g., the Exchange
declares a trading halt in all securities), days that the Exchange
instructs Participants in writing to route away, and the two Exchange
systems-related disruptions, each as described above. The foregoing
proposal is consistent with how Phlx categorizes potential excluded
days today.\13\
---------------------------------------------------------------------------

    \13\ See note 4 above at paragraphs (1) and (2).
---------------------------------------------------------------------------

Better of Rule
    Similar to Phlx, the proposed language also specifies how the
potential excluded days will be removed from the Exchange's volume
calculations. In particular, the language will allow the Exchange to
exclude any Scheduled Early Close or Unanticipated Event from its
calculations of ADV or any other applicable options volume tiers
provided for in its Pricing Schedule, provided that the Exchange will
only remove such days for Participants that would have a lower volume
calculation with the day included (i.e., the better of rule).\14\
---------------------------------------------------------------------------

    \14\ Phlx similarly excludes Scheduled Early Closes and
Unanticipated Events from its ADV calculations and other applicable
volume calculations in its pricing schedule, subject in each case to
the better of rule. See note 4 above at paragraph (3).
---------------------------------------------------------------------------

    Phlx adopted the better of rule to avoid penalizing members that
step up and trade on days with artificially low volume so that it only
excludes such days for members that would have a lower volume
calculation with the day included. This language would also be helpful
on the Exchange as it would ensure that Participants that continue to
execute a large volume of contracts are not inadvertently disadvantaged
when the Exchange removes a day from its volume calculations.
Furthermore, Phlx adopted the catch-all provision applying to other
options tier calculations set forth in its pricing schedule, but not
specified within paragraph (3) of its rule, so that it would have
flexibility to apply the better of rule going forward to all options
pricing programs administered by the Exchange that are based on volume
calculations.\15\ The Exchange believes that adopting a similar
principle-based approach for its options volume calculations would
ensure that days are removed from such calculations only if doing so
would be beneficial for the Participant. As such, the proposed language
will not apply to straight volume accumulations as Participants do not
benefit when a day is removed for such accumulations. Again, the
Exchange believes that the

approach of Phlx would be beneficial as it counts volume executed
during an excluded day toward its members' straight volume
accumulations.
---------------------------------------------------------------------------

    \15\ See id. at paragraph (3)(C).
---------------------------------------------------------------------------

    In addition, the Exchange proposes to harmonize its language with
Phlx's language by adding further detail throughout the proposed rule
text to bring greater transparency as to how the Exchange will apply
the better of rule when removing days from its tier calculations.
Specifically, the Exchange proposes to make clear that it will only
remove days pursuant to the better of rule by specifying in paragraphs
(i)(B) and (ii) that such days may be excluded from the tier
calculations only pursuant to paragraph (iii).\16\ Paragraph (iii) will
then provide that if a day is to be excluded as a result of paragraph
(i)(B) or (ii), the Exchange will be required to exclude the day from
any Participant's monthly options tier calculations as detailed within
paragraph (iii).\17\ With the proposed changes, the Exchange seeks to
clarify that it will exclude days from any Participant's Tier
Calculations in a uniform manner to ensure that days are removed only
in situations where the Participant benefits. The Exchange will look at
each potential excluded day in a month and determine for every
Participant their ADV or other applicable volume calculation based on
their trading volume on that day. If any Participant would have a lower
volume calculation with the particular day included, the Exchange will
exclude that day for that Participant. As such, the proposed changes
specify that the Exchange will apply the better of rule in a uniform
manner for all Participants, and that there is no arbitrary selection
of ``winners'' or ``losers'' when the Exchange excludes days.
---------------------------------------------------------------------------

    \16\ See id. at paragraphs (1)(B) and (2) for similar language
on Phlx.
    \17\ See id. at paragraph (3) for similar language on Phlx.
---------------------------------------------------------------------------

2. Statutory Basis
    The Exchange believes that its proposal is consistent with Section
6(b) of the Act,\18\ in general, and furthers the objectives of
Sections 6(b)(4) and 6(b)(5) of the Act,\19\ in particular, in that it
provides for the equitable allocation of reasonable dues, fees and
other charges among members and issuers and other persons using any
facility, and is not designed to permit unfair discrimination between
customers, issuers, brokers, or dealers.
---------------------------------------------------------------------------

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

    The Exchange believes that the proposed rule change is reasonable
and equitable as it provides a new framework for removing days from the
Exchange's volume calculations that the Exchange believes is beneficial
to Participants and consistent with similar provisions already in place
on Phlx. The proposed rule change would permit the Exchange to remove a
day from its volume calculations in numerous circumstances as described
above, and ensures that the Exchange will only do so when beneficial
for the Participant. The Exchange believes that it is reasonable and
equitable to exclude Scheduled Early Closes from its volume
calculations because this preserves the Exchange's intent behind
adopting volume-based pricing. Absent the authority to exclude
Scheduled Early Closes, Participants may experience an effective
increase in fees or decrease in rebates. The artificially low volumes
of trading on such days typically reduce the trading activity of
Participants. Accordingly, allowing the Exchange to exclude such days
from its volume calculations will diminish the likelihood of an
effective increase in the cost of trading on BX Options, a result that
is unintended and undesirable to the Exchange and to its Participants.
    The Exchange equally believes that it is reasonable and equitable
to exclude a day when Participants are instructed to route their orders
to other markets as this also preserves the Exchange's intent behind
adopting volume-based pricing, and avoids penalizing Participants that
follow this instruction. The Exchange likewise believes it is
reasonable and equitable to exclude a day from its volume calculations
when the Exchange's system experiences a disruption during the 30-
minute period prior to the opening of trade which renders the Exchange
inaccessible to Participants. Without this change, Participants that
are precluded from submitting eligible interest during the 30-minute
window before the opening of trade may be negatively impacted, even if
the Exchange resolves the issue before the market opens and as a
result, does not instruct Participants to route away. The proposed
change to exclude such days will diminish the likelihood of a cost
increase occurring because a Participant is not able to reach a volume
tier calculation on that date that it would reach on other trading days
during the month.
    Similarly, excluding a day where the Exchange's system experiences
a disruption that lasts for more than 60 minutes intra-day is
reasonable and equitable because the proposal seeks to avoid penalizing
Participants that might otherwise qualify for certain tiered pricing
but that, because of an Exchange systems disruption, did not
participate on the Exchange to the extent they might have otherwise
participated. The Exchange believes that certain systems disruptions
could preclude some Participants from submitting orders to the Exchange
even if such issue is not actually a complete systems outage.
    In addition, the Exchange believes that it is reasonable and
equitable to only exclude a day from its volume calculations for
Participants that would otherwise have a lower volume calculation with
the day included. Without these changes, Participants that route away
in accordance with the Exchange's instructions, or that step up and
trade significant volume on excluded trading days, may be negatively
impacted, resulting in an effective cost increase for those
Participants. In addition, having a catch-all in paragraph (iii)(B) so
that the better of rule applies to other options volume calculations
than ADV to allow the Exchange to apply the rule going forward to all
pricing programs based on volume calculations will further protect
Participants. The Exchange notes that aberrant low volume days
resulting from, for instance, an Unanticipated Event, impacts all
volume calculations, and allowing the Exchange to exclude such days
from any volume tier calculation if the Participant would have a lower
tier calculation with the day included will further protect
Participants from being inadvertently penalized.
    Furthermore, the Exchange believes that categorizing the potential
excluded days is reasonable and equitable because it will bring greater
transparency to the application of its rule. Specifically, the Exchange
is distinguishing between planned and unplanned days in paragraphs (i)
and (ii), defining the latter as Unanticipated Events, and stipulating
how the Exchange will exclude such days pursuant to this rule.
Categorizing days in this manner will clarify the application of its
rule in light of the Exchange's proposal to adopt numerous days that
may be excluded from its volume calculations. Providing in paragraph
(i)(A) that the Exchange will always exclude from its tier calculations
days that it announces in advance it will not be open for trading will
clarify current practice. Furthermore, the Exchange believes that the
proposed changes to specify how days in paragraphs (i)(B) and (ii) may
be excluded from its volume calculations will bring greater
transparency by delineating the various circumstances in which the
better of rule will apply. Providing in paragraph (iii) that the
Exchange may exclude any Scheduled Early Close or Unanticipated Event
from

the Tier Calculations, subject to the better of rule, will make clear
that the Exchange will take a consistent approach when excluding days
for purposes of its volume based pricing tiers. Furthermore, the
proposed changes specifying that the days in paragraphs (i)(B) and (ii)
may be excluded only pursuant to paragraph (iii), and requiring the
Exchange to exclude such days pursuant to the specifications in
paragraph (iii) will likewise make clear that the Exchange will take a
consistent approach with respect to excluding days from its Tier
Calculations. As discussed above, these modifications will clarify that
the Exchange will apply the better of rule in a uniform manner to all
Participants, and that there is no arbitrary selection of ``winners''
or ``losers.''
    Finally, the Exchange believes that the proposed rule change is not
unfairly discriminatory because it will apply equally to all
Participants.

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

    The Exchange does not believe that the proposed rule change will
impose any burden on competition not necessary or appropriate in
furtherance of the purposes of the Act. The proposed rule change is
designed to protect Participants from the possibility of a cost
increase by excluding days when overall participation might be
significantly lower than a typical trading day. The Exchange believes
that the proposed modifications to its tier calculations are pro-
competitive and will result in lower total costs to end users, a
positive outcome of competitive markets. Furthermore, other options
exchanges have adopted rules that are substantially similar to the
Exchange's proposal.\20\
---------------------------------------------------------------------------

    \20\ See notes 4 and 12 above.
---------------------------------------------------------------------------

    The Exchange operates in a highly competitive market in which
market participants can readily direct their order flow to competing
venues. In such an environment, the Exchange must continually review,
and consider adjusting, its fees and rebates to remain competitive with
other exchanges. For the reasons described above, the Exchange believes
that the proposed fee changes reflect this competitive environment.

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

    No written comments were either solicited or received.

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)(ii) of the Act \21\ and paragraph (f) of Rule 19b-4
thereunder.\22\ 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.
---------------------------------------------------------------------------

    \21\ 15 U.S.C. 78s(b)(3)(A)(ii).
    \22\ 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-BX-2019-001 on the subject line.

Paper Comments

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

All submissions should refer to File Number SR-BX-2019-001. 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 website (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 website 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. Persons submitting comments are
cautioned that we do not redact or edit personal identifying
information from comment submissions. You should submit only
information that you wish to make available publicly. All submissions
should refer to File Number SR-BX-2019-001, and should be submitted on
or before March 14, 2019.

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

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

Eduardo A. Aleman,
Deputy Secretary.
[FR Doc. 2019-02891 Filed 2-20-19; 8:45 am]
 BILLING CODE 8011-01-P


[Federal Register Volume 77, Number 60 (Wednesday, March 28, 2012)]
[Rules and Regulations]
[Pages 18681-18684]
[FR Doc No: 2012-7220]

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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 97

[Docket No. 30833; Amdt. No. 3470]

Standard Instrument Approach Procedures, and Takeoff Minimums and
Obstacle Departure Procedures; Miscellaneous Amendments

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Final rule.

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

SUMMARY: This rule establishes, amends, suspends, or revokes Standard
Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums
and Obstacle Departure Procedures for operations at certain airports.
These regulatory actions are needed because of the adoption of new or
revised criteria, or because of changes occurring in the National
Airspace System, such as the commissioning of new navigational
facilities, adding new obstacles, or changing air traffic requirements.
These changes are designed to provide safe and efficient use of the
navigable airspace and to promote safe flight operations under
instrument flight rules at the affected airports.

DATES: This rule is effective March 28, 2012. The compliance date for
each SIAP, associated Takeoff Minimums, and ODP is specified in the
amendatory provisions.
    The incorporation by reference of certain publications listed in
the regulations is approved by the Director of the Federal Register as
of March 28, 2012.

ADDRESSES: Availability of matters incorporated by reference in the
amendment is as follows:
    For Examination--
    1. FAA Rules Docket, FAA Headquarters Building, 800 Independence
Avenue SW., Washington, DC 20591;
    2. The FAA Regional Office of the region in which the affected
airport is located;
    3. The National Flight Procedures Office, 6500 South MacArthur
Blvd., Oklahoma City, OK 73169 or
    4. The National Archives and Records Administration (NARA). For
information on the availability of this material at NARA, call 202-741-
6030, or go to: http://www.archives.gov/federal_register/code_of_federal_regulations/ibr_locations.html.
    Availability--All SIAPs and Takeoff Minimums and ODPs are available
online free of charge. Visit http://www.nfdc.faa.gov to register.
Additionally, individual SIAP and Takeoff Minimums and ODP copies may
be obtained from:
    1. FAA Public Inquiry Center (APA-200), FAA Headquarters Building,
800 Independence Avenue SW., Washington, DC 20591; or
    2. The FAA Regional Office of the region in which the affected
airport is located.

FOR FURTHER INFORMATION CONTACT: Richard A. Dunham III, Flight
Procedure Standards Branch (AFS-420), Flight Technologies and Programs
Divisions, Flight Standards Service, Federal Aviation Administration,
Mike Monroney Aeronautical Center, 6500 South MacArthur Blvd., Oklahoma
City, OK 73169 (Mail Address: P.O. Box 25082, Oklahoma City, OK 73125)
Telephone:<PHONE_NUMBER>.

SUPPLEMENTARY INFORMATION: This rule amends Title 14 of the Code of
Federal Regulations, Part 97 (14 CFR part 97), by establishing,
amending, suspending, or revoking SIAPS, Takeoff Minimums and/or ODPS.
The complete regulators description of each SIAP and its associated
Takeoff Minimums or ODP for an identified airport is listed on FAA form
documents which are incorporated by reference in this amendment under 5
U.S.C. 552(a), 1 CFR part 51, and 14 CFR part 97.20. The applicable FAA
Forms are FAA Forms 8260-3, 8260-4, 8260-5, 8260-15A, and 8260-15B when
required by an entry on 8260-15A.
    The large number of SIAPs, Takeoff Minimums and ODPs, in addition
to their complex nature and the need for a special format make
publication in the Federal Register expensive and

impractical. Furthermore, airmen do not use the regulatory text of the
SIAPs, Takeoff Minimums or ODPs, but instead refer to their depiction
on charts printed by publishers of aeronautical materials. The
advantages of incorporation by reference are realized and publication
of the complete description of each SIAP, Takeoff Minimums and ODP
listed on FAA forms is unnecessary. This amendment provides the
affected CFR sections and specifies the types of SIAPs and the
effective dates of the, associated Takeoff Minimums and ODPs. This
amendment also identifies the airport and its location, the procedure,
and the amendment number.

The Rule

    This amendment to 14 CFR part 97 is effective upon publication of
each separate SIAP, Takeoff Minimums and ODP as contained in the
transmittal. Some SIAP and Takeoff Minimums and textual ODP amendments
may have been issued previously by the FAA in a Flight Data Center
(FDC) Notice to Airmen (NOTAM) as an emergency action of immediate
flight safety relating directly to published aeronautical charts. The
circumstances which created the need for some SIAP and Takeoff Minimums
and ODP amendments may require making them effective in less than 30
days. For the remaining SIAPS and Takeoff Minimums and ODPS, an
effective date at least 30 days after publication is provided.
    Further, the SIAPs and Takeoff Minimums and ODPS contained in this
amendment are based on the criteria contained in the U.S. Standard for
Terminal Instrument Procedures (TERPS). In developing these SIAPS and
Takeoff Minimums and ODPs, the TERPS criteria were applied to the
conditions existing or anticipated at the affected airports. Because of
the close and immediate relationship between these SIAPs, Takeoff
Minimums and ODPs, and safety in air commerce, I find that notice and
public procedures before adopting these SIAPS, Takeoff Minimums and
ODPs are impracticable and contrary to the public interest and, where
applicable, that good cause exists for making some SIAPs effective in
less than 30 days.

Conclusion

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

List of Subjects in 14 CFR Part 97

    Air traffic control, Airports, Incorporation by reference, and
Navigation (air).

    Issued in Washington, DC, on March 16, 2012.
John McGraw,
Deputy Director, Flight Standards Service.

Adoption of the Amendment

    Accordingly, pursuant to the authority delegated to me, Title 14,
Code of Federal Regulations, Part 97 (14 CFR part 97) is amended by
establishing, amending, suspending, or revoking Standard Instrument
Approach Procedures and/or Takeoff Minimums and/or Obstacle Departure
Procedures effective at 0902 UTC on the dates specified, as follows:

PART 97--STANDARD INSTRUMENT APPROACH PROCEDURES

0
1. The authority citation for part 97 continues to read as follows:

    Authority:  49 U.S.C. 106(g), 40103, 40106, 40113, 40114, 40120,
44502, 44514, 44701, 44719, 44721-44722.

0
2. Part 97 is amended to read as follows:

Effective 3 MAY 2012

Oakland, CA, Metropolitan Oakland Intl, RNAV (RNP) Z RWY 29, Orig-B
Santa Maria, CA, Santa Maria Pub/Capt G Allan Hancock Fld, RNAV
(GPS) RWY 12, Amdt 1
Santa Maria, CA, Santa Maria Pub/Capt G Allan Hancock Fld, Takeoff
Minimums and Obstacle DP, Amdt 6
Santa Maria, CA, Santa Maria Pub/Capt G Allan Hancock Fld, VOR RWY
12, Amdt 15
Pocatello, ID, Pocatello Rgnl, VOR RWY 3, Amdt 17
Monticello, KY, Wayne County, Takeoff Minimums and Obstacle DP, Amdt
2
Jackson, MI, Jackson County-Reynolds Field, RNAV (GPS) RWY 14, Amdt
1
Jackson, MI, Jackson County-Reynolds Field, RNAV (GPS) RWY 32, Orig-
A
Austin, MN, Austin Muni, ILS OR LOC RWY 35, Amdt 1
Austin, MN, Austin Muni, RNAV (GPS) RWY 35, Amdt 1
Marshall, MN, Southwest Minnesota Rgnl Marshall/Ryan Fld, RNAV (GPS)
RWY 12, Amdt 1
Marshall, MN, Southwest Minnesota Rgnl Marshall/Ryan Fld, RNAV (GPS)
RWY 30, Orig-A
Minneapolis, MN, Airlake, RNAV (GPS) RWY 30, Orig
Kansas City, MO, Charles B. Wheeler Downtown, ILS OR LOC RWY 3, Amdt
3
Kansas City, MO, Charles B. Wheeler Downtown, RNAV (GPS) RWY 3, Amdt
1
Kansas City, MO, Charles B. Wheeler Downtown, RNAV (GPS) RWY 21,
Amdt 1
Kansas City, MO, Charles B. Wheeler Downtown, VOR RWY 3, Amdt 18
Kansas City, MO, Charles B. Wheeler Downtown, VOR RWY 21, Amdt 14
Lee's Summit, MO, Lee's Summit Muni, RNAV (GPS) RWY 11, Amdt 1
Lee's Summit, MO, Lee's Summit Muni, RNAV (GPS) RWY 18, Amdt 2
Lee's Summit, MO, Lee's Summit Muni, RNAV (GPS) RWY 29, Amdt 2
Lee's Summit, MO, Lee's Summit Muni, RNAV (GPS) RWY 36, Amdt 2
Erwin, NC, Harnett Rgnl Jetport, RNAV (GPS) RWY 5, Amdt 2B
Atkinson, NE., Stuart-Atkinson Muni, GPS RWY 29, Orig, CANCELLED
Atkinson, NE., Stuart-Atkinson Muni, RNAV (GPS) RWY 11, Orig
Atkinson, NE., Stuart-Atkinson Muni, RNAV (GPS) RWY 29, Orig
Atkinson, NE., Stuart-Atkinson Muni, Takeoff Minimums and Obstacle
DP, Amdt 1
Atkinson, NE., Stuart-Atkinson Muni, VOR/DME RWY 29, Amdt 1
Kearney, NE., Kearney Rgnl, Takeoff Minimums and Obstacle DP, Amdt 1
Mount Holly, NJ, South Jersey Rgnl, VOR RWY 26, Amdt 3
Newark, NJ, Newark Liberty Intl, ILS OR LOC RWY 22R, Amdt 5B
Poughkeepsie, NY, Dutchess County, VOR/DME RWY 6, Amdt 7
Batavia, OH, Clermont County, RNAV (GPS) RWY 4, Amdt 1
Batavia, OH, Clermont County, RNAV (GPS) RWY 22, Amdt 1
Batavia, OH, Clermont County, Takeoff Minimums and Obstacle DP, Orig
Bellefontaine, OH, Bellefontaine Rgnl, RNAV (GPS) RWY 7, Amdt 1
Bellefontaine, OH, Bellefontaine Rgnl, RNAV (GPS) RWY 25, Amdt 1
Marysville, OH, Union County, GPS RWY 9, Orig-B, CANCELLED
Marysville, OH, Union County, GPS RWY 27, Orig-B, CANCELLED
Marysville, OH, Union County, RNAV (GPS) RWY 9, Orig
Marysville, OH, Union County, RNAV (GPS) RWY 27, Orig
Ardmore, OK, Ardmore Downtown Executive, VOR-A, Amdt 13A, CANCELLED
Kerrville, TX, Kerrville Muni/Louis Schreiner Field, VOR-A, Amdt 3A

Effective 31 MAY 2012

Deadhorse, AK, Deadhorse, RNAV (GPS) RWY 6, Orig
Deadhorse, AK, Deadhorse, RNAV (GPS) RWY 24, Orig
Deadhorse, AK, Deadhorse, Takeoff Minimums and Obstacle DP, Amdt 2

Marshall, AK, Marshall Don Hunter Sr, RNAV (GPS) RWY 7, Amdt 2
Marshall, AK, Marshall Don Hunter Sr, RNAV (GPS)-A, Amdt 2
Mountain Village, AK, Mountain Village, RNAV (GPS) RWY 2, Amdt 1
Mountain Village, AK, Mountain Village, RNAV (GPS) RWY 20, Amdt 1
Scammon Bay, AK, Scammon Bay, RNAV (GPS) RWY 28, Amdt 1
Oneonta, AL, Robbins Field, RNAV (GPS) RWY 5, Orig
Oneonta, AL, Robbins Field, RNAV (GPS) RWY 23, Orig
Oneonta, AL, Robbins Field, Takeoff Minimums and Obstacle DP, Orig
Camden, AR, Harrell Field, RNAV (GPS) RWY 1, Amdt 1
Camden, AR, Harrell Field, RNAV (GPS) RWY 19, Amdt 1
Camden, AR, Harrell Field, Takeoff Minimums and Obstacle DP, Amdt 1
Camden, AR, Harrell Field, VOR/DME RWY 1, Amdt 10
Lake Havasu City, AZ, Lake Havasu City, Takeoff Minimums and
Obstacle DP, Amdt 2
Lake Havasu City, AZ, Lake Havasu City, VOR/DME-A, Amdt 1
Sacramento, CA, Sacramento Intl, ILS OR LOC RWY 16L, Amdt 2
Sacramento, CA, Sacramento Intl, ILS OR LOC RWY 16R, ILS RWY 16R (SA
CAT I), ILS RWY 16R (CAT II), ILS RWY 16R (CAT III), Amdt 15
Sacramento, CA, Sacramento Intl, RNAV (GPS) Y RWY 16L, Amdt 1
Sacramento, CA, Sacramento Intl, RNAV (GPS) Y RWY 16R, Amdt 1
Denver, CO, Centennial, Takeoff Minimums and Obstacle DP, Amdt 5
Denver, CO, Denver Intl, ILS OR LOC RWY 7, Amdt 3
Denver, CO, Denver Intl, ILS OR LOC RWY 8, Amdt 5
Denver, CO, Denver Intl, ILS OR LOC RWY 16L, Amdt 3
Denver, CO, Denver Intl, ILS OR LOC RWY 16R, Amdt 1
Denver, CO, Denver Intl, ILS OR LOC RWY 17L, Amdt 4
Denver, CO, Denver Intl, ILS OR LOC RWY 17R, Amdt 3
Denver, CO, Denver Intl, ILS OR LOC RWY 25, Amdt 3
Denver, CO, Denver Intl, ILS OR LOC RWY 26, Amdt 3
Denver, CO, Denver Intl, ILS OR LOC RWY 34L, ILS RWY 34L (CAT II),
ILS RWY 34L (CAT III), ILS RWY 34L (SA CAT I), Amdt 2
Denver, CO, Denver Intl, ILS OR LOC RWY 34R, ILS RWY 34R (CAT II),
ILS RWY 34R (CAT III), ILS RWY 34R (SA CAT I), Amdt 3
Denver, CO, Denver Intl, ILS OR LOC RWY 35L, ILS RWY 35L (CAT II),
ILS RWY 35L (CAT III), ILS RWY 35L (SA CAT I), Amdt 5
Denver, CO, Denver Intl, ILS OR LOC RWY 35R, ILS RWY 35R (CAT II),
ILS RWY 35R (CAT III), ILS RWY 35R (SA CAT I), Amdt 3
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 7, Amdt 1
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 8, Amdt 1
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 16L, Amdt 1
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 16R, Amdt 1
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 17L, Amdt 1
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 17R, Amdt 1
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 25, Amdt 1
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 26, Amdt 1
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 34L, Amdt 2
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 34R, Amdt 2
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 35L, Amdt 2
Denver, CO, Denver Intl, RNAV (GPS) Y RWY 35R, Amdt 2
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 7, Orig
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 8, Orig
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 16L, Orig
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 16R, Orig
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 17L, Orig
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 17R, Orig
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 25, Orig
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 26, Orig
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 34L, Orig
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 34R, Orig
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 35L, Orig
Denver, CO, Denver Intl, RNAV (RNP) Z RWY 35R, Orig
Denver, CO, Front Range, ILS OR LOC RWY 17, Amdt 1
Denver, CO, Front Range, ILS OR LOC RWY 26, Amdt 5
Denver, CO, Front Range, ILS OR LOC RWY 35, Amdt 1
Denver, CO, Front Range, NDB RWY 26, Amdt 5
Denver, CO, Front Range, RNAV (GPS) RWY 17, Amdt 1
Denver, CO, Front Range, RNAV (GPS) RWY 26, Amdt 1
Denver, CO, Front Range, RNAV (GPS) RWY 35, Amdt 1
Denver, CO, Front Range, Takeoff Minimums and Obstacle DP, Amdt 3
Denver, CO, Rocky Mountain Metropolitan, Takeoff Minimums and
Obstacle DP, Amdt 5
St. Augustine, FL, St Augustine, RNAV (GPS) RWY 31, Amdt 1
Atlantic, IA, Atlantic Muni, RNAV (GPS) RWY 2, Amdt 1
Atlantic, IA, Atlantic Muni, RNAV (GPS) RWY 20, Amdt 1
Belle Plaine, IA, Belle Plaine Muni, GPS RWY 18, Orig-A, CANCELLED
Belle Plaine, IA, Belle Plaine Muni, GPS RWY 36, Orig-A, CANCELLED
Belle Plaine, IA, Belle Plaine Muni, RNAV (GPS) RWY 18, Orig
Belle Plaine, IA, Belle Plaine Muni, RNAV (GPS) RWY 36, Orig
Belle Plaine, IA, Belle Plaine Muni, VOR/DME-A, Amdt 1
Oelwein, IA, Oelwein, Takeoff Minimums and Obstacle DP, Amdt 3
Sac City, IA, Sac City Muni, RNAV (GPS) RWY 18, Orig
Sac City, IA, Sac City Muni, RNAV (GPS) RWY 36, Amdt 1
Sheldon, IA, Sheldon Muni, RNAV (GPS) RWY 15, Amdt 1
Sheldon, IA, Sheldon Muni, RNAV (GPS) RWY 33, Amdt 1
Centralia, IL, Centralia Muni, RNAV (GPS) RWY 18, Amdt 1
Centralia, IL, Centralia Muni, RNAV (GPS) RWY 36, Amdt 1
Centralia, IL, Centralia Muni, Takeoff Minimums and Obstacle DP,
Amdt 2
Chicago/Rockford, IL, Chicago/Rockford Intl, RNAV (GPS) RWY 7, Amdt
1A
Chicago/Rockford, IL, Chicago/Rockford Intl, RNAV (GPS) RWY 25, Amdt
1
Chicago/Rockford, IL, Chicago/Rockford Intl, RNAV (GPS) Y RWY 25,
Orig-B, CANCELLED
Flora, IL, Flora Muni, RNAV (GPS) RWY 3, Amdt 2
Flora, IL, Flora Muni, RNAV (GPS) RWY 21, Amdt 2
Rochelle, IL, Rochelle Muni Airport-Koritz Field, RNAV (GPS) RWY 7,
Amdt 1
Rochelle, IL, Rochelle Muni Airport-Koritz Field, RNAV (GPS) RWY 25,
Amdt 1
Iola, KS, Allen County, RNAV (GPS) RWY 1, Amdt 1
Topeka, KS, Philip Billard Muni, RNAV (GPS) RWY 13, Amdt 1
Topeka, KS, Philip Billard Muni, RNAV (GPS) RWY 31, Amdt 1
Glasgow, KY, Glasgow Muni, RNAV (GPS) RWY 8, Amdt 2
Glasgow, KY, Glasgow Muni, RNAV (GPS) RWY 26, Amdt 2
Glasgow, KY, Glasgow Muni, SDF RWY 8, Amdt 11
Glasgow, KY, Glasgow Muni, VOR/DME RWY 8, Amdt 9
Greenville, KY, Muhlenberg County, RNAV (GPS) RWY 6, Orig
Greenville, KY, Muhlenberg County, RNAV (GPS) RWY 24, Amdt 1
Paducah, KY, Barkley Rgnl, RNAV (GPS) RWY 22, Orig-B
Falmouth, MA, Cape Cod Coast Guard Air Station, ILS OR LOC RWY 23,
Amdt 1
Falmouth, MA, Cape Cod Coast Guard Air Station, ILS OR LOC RWY 32,
Amdt 1
Westminster, MD, Carroll County Rgnl/Jack B Poage Field, RNAV (GPS)
RWY 16, Amdt 2
Portland, ME, Portland Intl Jetport, ILS OR LOC RWY 11, ILS RWY 11
(SA CAT I), ILS RWY 11 (CAT II), ILS RWY 11 (CAT III), Amdt 3
Portland, ME, Portland Intl Jetport, ILS OR LOC RWY 29, ILS RWY 29
(SA CAT I), ILS RWY 29 (SA CAT II), Amdt 3
Portland, ME, Portland Intl Jetport, RNAV (GPS) RWY 11, Amdt 3
Portland, ME, Portland Intl Jetport, RNAV (GPS) RWY 18, Amdt 1
Portland, ME, Portland Intl Jetport, RNAV (GPS) RWY 29, Amdt 2
Portland, ME, Portland Intl Jetport, RNAV (GPS) RWY 36, Amdt 1
Portland, ME, Portland Intl Jetport, Takeoff Minimums and Obstacle
DP, Amdt 5

Drummond Island, MI, Drummond Island, Takeoff Minimums and Obstacle
DP, Amdt 1
Orr, MN, Orr Rgnl, Takeoff Minimums and Obstacle DP, Amdt 2
Columbia, MO, Columbia Rgnl, Takeoff Minimums and Obstacle DP, Amdt
5
Jefferson City, MO, Jefferson City Memorial, NDB RWY 12, Amdt 2C,
CANCELLED
Philadelphia, MS, Philadelphia Muni, NDB RWY 18, Amdt 1A, CANCELLED
Philadelphia, MS, Philadelphia Muni, NDB RWY 36, Amdt 1A, CANCELLED
Billings, MT, Billings Logan Intl, ILS OR LOC/DME RWY 28R, Amdt 1
Billings, MT, Billings Logan Intl, RNAV (GPS) RWY 7, Amdt 1
Billings, MT, Billings Logan Intl, RNAV (GPS) RWY 25, Amdt 1
Portales, NM, Portales Muni, Takeoff Minimums and Obstacle DP, Orig
Socorro, NM, Socorro Muni, RNAV (GPS) RWY 33, Amdt 1
New York, NY, La Guardia, Takeoff Minimums and Obstacle DP, Amdt 9A
Hot Springs, SD, Hot Springs Muni, GPS RWY 19, Orig, CANCELLED
Hot Springs, SD, Hot Springs Muni, RNAV (GPS) RWY 1, Orig
Hot Springs, SD, Hot Springs Muni, RNAV (GPS) RWY 19, Orig
El Paso, TX, El Paso Intl, RNAV (GPS) X RWY 4, Orig-A
El Paso, TX, El Paso Intl, RNAV (RNP) Y RWY 4, Orig
El Paso, TX, El Paso Intl, RNAV (RNP) Z RWY 4, Orig
El Paso, TX, El Paso Intl, RNAV (RNP) Z RWY 22, Orig-A
El Paso, TX, El Paso Intl, RNAV (RNP) Z RWY 26L, Orig
Fort Worth, TX, Fort Worth Spinks, ILS OR LOC RWY 35L, Amdt 2
Fort Worth, TX, Fort Worth Spinks, RNAV (GPS) RWY 17R, Amdt 1
Fort Worth, TX, Fort Worth Spinks, RNAV (GPS) RWY 35L, Amdt 1
Nacogdoches, TX, A L Mangham Jr. Rgnl, GPS RWY 36, Orig-A, CANCELLED
Nacogdoches, TX, A L Mangham Jr. Rgnl, RNAV (GPS) RWY 36, Orig
Nacogdoches, TX, A L Mangham Jr. Rgnl, Takeoff Minimums and Obstacle
DP, Amdt 2
Blackstone, VA, Allen C. Perkinson Muni/Blackstone AAF, Takeoff
Minimums and Obstacle DP, Amdt 2
Galax Hillsville, VA, Twin County, RNAV (GPS) RWY 1, Amdt 1
Galax Hillsville, VA, Twin County, RNAV (GPS) RWY 19, Amdt 1
Galax Hillsville, VA, Twin County, Takeoff Minimums and Obstacle DP,
Amdt 3
Bennington, VT, William H. Morse State, VOR RWY 13, Amdt 1
Milwaukee, WI, General Mitchell Intl, Takeoff Minimums and Obstacle
DP, Amdt 8
Kemmerer, WY, Kemmerer Muni, Takeoff Minimums and Obstacle DP, Amdt
2

[FR Doc. 2012-7220 Filed 3-27-12; 8:45 am]
BILLING CODE 4910-13-P