[Federal Register Volume 76, Number 216 (Tuesday, November 8, 2011)]
[Notices]
[Pages 69306-69307]
[FR Doc No: 2011-28910]

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

 SECURITIES AND EXCHANGE COMMISSION

Submission for OMB Review; Comment Request

Upon Written Request, Copies Available From: Securities and Exchange
Commission, Office of Investor Education and Advocacy, Washington, DC
20549-0213.

Extension:
    Rule 30b2-1, SEC File No. 270-213, OMB Control No. 3235-0220.

    Notice is hereby given that, pursuant to the Paperwork Reduction
Act of 1995 (44 U.S.C. 3501 et seq.), the Securities and Exchange
Commission (the ``Commission'') has submitted to the Office of
Management and Budget (``OMB'') a request for extension of the
previously approved collection of information discussed below.
    Rule 30b2-1 (17 CFR 270.30b2-1) under the Investment Company Act of
1940 (15 U.S.C. 80a-1 et seq.) (the ``Investment Company Act'')
requires a registered management investment company (``fund'') to (1)
file a report with the Commission on Form N-CSR (17 CFR 249.331 and
274.128) not later than 10 days after the transmission of any report
required to be transmitted to shareholders under rule 30e-1 under the
Investment Company Act, and (2) file with the Commission a copy of
every periodic or interim report or similar communication containing
financial statements that is transmitted by or on behalf of such fund
to any class of such fund's security holders and that is not required
to be filed with the Commission under (1) above, not later than 10 days
after the transmission to security holders. The purpose of the
collection of information required by rule 30b2-1 is to meet the
disclosure requirements of the Investment Company Act and certification

requirements of the Sarbanes-Oxley Act of 2002 (Pub. L 107-204, 116
Stat. 745 (2002)) and to provide investors with information necessary
to evaluate an interest in the fund.
    The Commission estimates that there are 2,520 funds, with a total
of approximately 9,250 portfolios, that are governed by the rule. For
purposes of this analysis, the burden associated with the requirements
of rule 30b2-1 has been included in the collection of information
requirements of rule 30e-1 and Form N-CSR, rather than the rule. The
Commission has, however, requested a one hour burden for administrative
purposes.
    The collection of information under rule 30b2-1 is mandatory. The
information provided under rule 30b2-1 is not kept confidential. An
agency may not conduct or sponsor, and a person is not required to
respond to, a collection of information unless it displays a currently
valid OMB control number.
    The public may view the background documentation for this
information collection at the following Web site, http://www.reginfo.gov. Comments should be directed to: (i) Desk Officer for
the Securities and Exchange Commission, Office of Information and
Regulatory Affairs, Office of Management and Budget, Room 10102, New
Executive Office Building, Washington, DC 20503, or by sending an email
to<EMAIL_ADDRESS>and (ii) Thomas A. Bayer, Director/
Chief Information Officer, Securities and Exchange Commission, c/o Remi
Pavlik-Simon, 6432 General Green Way, Alexandria, VA 22312; or send an
email to<EMAIL_ADDRESS>Comments must be submitted to OMB
within 30 days of this notice.

    Dated: November 3, 2011.
Kevin M. O'Neill,
Deputy Secretary.
[FR Doc. 2011-28910 Filed 11-7-11; 8:45 am]
BILLING CODE 8011-01-P


[Federal Register: September 14, 2010 (Volume 75, Number 177)]
[Notices]
[Page 55796-55797]
[DOCID:fr14se10-72]

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

DEPARTMENT OF HEALTH AND HUMAN SERVICES

Food and Drug Administration

[Docket No. FDA-2010-P-0157]

Determination That VESANOID (Tretinoin) Capsules, 10 Milligrams,
Were Not Withdrawn From Sale for Reasons of Safety or Effectiveness

AGENCY:  Food and Drug Administration, HHS.

ACTION:  Notice.

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

SUMMARY:  The Food and Drug Administration (FDA) has determined that
VESANOID (tretinoin) Capsules, 10 milligrams (mg), were not withdrawn
from sale for reasons of safety or effectiveness. This determination
means that FDA will not begin procedures to withdraw approval of the
abbreviated new drug application (ANDA) that refers to this drug
product, and it will allow FDA to continue to approve ANDAs that refer
to the product as long as they meet relevant legal and regulatory
requirements.

FOR FURTHER INFORMATION CONTACT:  Molly Flannery, Center for Drug
Evaluation and Research, Food and Drug Administration, 10903 New
Hampshire Ave., Bldg. 51, rm. 6237, Silver Spring, MD 20993-0002, 301-
796-3543.

SUPPLEMENTARY INFORMATION: In 1984, Congress enacted the Drug Price
Competition and Patent Term Restoration Act of 1984 (Public Law 98-

417) (the 1984 amendments), which authorized the approval of duplicate
versions of drug products approved under an ANDA procedure. ANDA
applicants must, with certain exceptions, show that the drug for which
they are seeking approval contains the same active ingredient in the
same strength and dosage form as the ``listed drug,'' which is a
version of the drug that was previously approved. ANDA applicants do
not have to repeat the extensive clinical testing otherwise necessary
to gain approval of a new drug application (NDA). The only clinical
data required in an ANDA are data to show that the drug that is the
subject of the ANDA is bioequivalent to the listed drug.
    The 1984 amendments include what is now section 505(j)(7) of the
Federal Food, Drug, and Cosmetic Act (21 U.S.C. 355(j)(7)), which
requires FDA to publish a list of all approved drugs. FDA publishes
this list as part of the ``Approved Drug Products With Therapeutic
Equivalence Evaluations,'' which is known generally as the ``Orange
Book.'' Under FDA regulations, drugs are removed from the list if the
agency withdraws or suspends approval of the drug's NDA or ANDA for
reasons of safety or effectiveness or if FDA determines that the listed
drug was withdrawn from sale for reasons of safety or effectiveness (21
CFR 314.162). Under Sec.  314.161(a)(1) (21 CFR 314.161(a)(1)), the
agency must determine whether a listed drug was withdrawn from sale for
reasons of safety or effectiveness before an ANDA that refers to that
listed drug may be approved. FDA may not approve an ANDA that does not
refer to a listed drug.
    VESANOID (tretinoin) Capsules, 10 mg, are the subject of NDA 20-
438, held by Hoffman-La Roche Inc. (Roche), and initially approved on
November 22, 1995. VESANOID is indicated for the ``induction of
remission in patients with acute promyelocytic leukemia (APL), French-
American-British (FAB) classification M3 (including the M3 variant),
characterized by the presence of the t(15;17) translocation and/or the
presence of the PML/RAR[agr] [promyelocytic leukemia/retinoic acid
receptor alpha] gene who are refractory to, or who have relapsed from,
anthracycline chemotherapy, or for whom anthracycline-based
chemotherapy is contraindicated'' (VESANOID labeling).
    In a letter dated December 2, 2009, Roche notified FDA that
VESANOID (tretinoin) Capsules, 10 mg, were being discontinued, and FDA
moved the drug product to the ``Discontinued Drug Product List''
section of the Orange Book. There is one approved ANDA for tretinoin
capsules, 10 mg (ANDA No. 77-684); this drug product is listed in the
Orange Book and, following the discontinuation of VESANOID, was
designated as the reference listed drug to which new ANDAs should
refer.
    Rakoczy Molino Mazzochi Siwik LLP submitted a citizen petition
dated March 17, 2010 (Docket No. FDA-2010-P-0157), under 21 CFR 10.30,
requesting that the agency determine whether VESANOID (tretinoin)
Capsules, 10 mg, were withdrawn from sale for reasons of safety or
effectiveness.
    After considering the citizen petition and reviewing agency
records, FDA has determined under Sec.  314.161 that VESANOID
(tretinoin) Capsules, 10 mg, were not withdrawn for reasons of safety
or effectiveness. The petitioner has identified no data or other
information suggesting that VESANOID (tretinoin) Capsules, 10 mg, were
withdrawn for reasons of safety or effectiveness. We have carefully
reviewed our files for records concerning the withdrawal of VESANOID
(tretinoin) Capsules, 10 mg, from sale. We have also independently
evaluated relevant literature and data for possible postmarketing
adverse events and have found no information that would indicate that
this product was withdrawn from sale for reasons of safety or
effectiveness.
    Accordingly, the agency will continue to list VESANOID (tretinoin)
Capsules, 10 mg, in the ``Discontinued Drug Product List'' section of
the Orange Book. The ``Discontinued Drug Product List'' delineates,
among other items, drug products that have been discontinued from
marketing for reasons other than safety or effectiveness. FDA will not
begin procedures to withdraw approval of the approved ANDA that refers
to VESANOID. Additional ANDAs for tretinoin capsules, 10 mg, may also
be approved by the agency as long as they meet all other legal and
regulatory requirements for the approval of ANDAs. If FDA determines
that labeling for this drug product should be revised to meet current
standards, the agency will advise ANDA applicants to submit such
labeling.

    Dated: September 8, 2010.
Leslie Kux,
Acting Assistant Commissioner for Policy.
[FR Doc. 2010-22807 Filed 9-13-10; 8:45 am]
BILLING CODE 4160-01-S


[Federal Register Volume 86, Number 83 (Monday, May 3, 2021)]
[Notices]
[Page 23397]
[FR Doc No: 2021-09162]

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

DEPARTMENT OF HOMELAND SECURITY

Federal Emergency Management Agency

[Internal Agency Docket No. FEMA-4517-DR; Docket ID FEMA-2021-0001]

West Virginia; Amendment No. 4 to Notice of a Major Disaster
Declaration

AGENCY: Federal Emergency Management Agency, DHS.

ACTION: Notice.

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

SUMMARY: This notice amends the notice of a major disaster declaration
for the State of West Virginia (FEMA-4517-DR), dated April 3, 2020, and
related determinations.

DATES: This amendment was issued March 11, 2021.

FOR FURTHER INFORMATION CONTACT: Dean Webster, Office of Response and
Recovery, Federal Emergency Management Agency, 500 C Street SW,
Washington, DC 20472,<PHONE_NUMBER>.

SUPPLEMENTARY INFORMATION: The notice of a major disaster declaration
for the State of West Virginia is hereby amended to include Individual
Assistance limited to COVID-19 Funeral Assistance under Other Needs
Assistance for those areas determined to have been adversely affected
by the event declared a major disaster by the President in his
declaration of April 3, 2020.

    Individual Assistance limited to COVID-19 Funeral Assistance
under Other Needs Assistance for all areas in the State of West
Virginia (already designated for Individual Assistance, limited to
the Crisis Counseling Program and emergency protective measures
[Category B] not authorized under other Federal statutes, including
direct Federal assistance).

(The following Catalog of Federal Domestic Assistance Numbers (CFDA)
are to be used for reporting and drawing funds: 97.030, Community
Disaster Loans; 97.031, Cora Brown Fund; 97.032, Crisis Counseling;
97.033, Disaster Legal Services; 97.034, Disaster Unemployment
Assistance (DUA); 97.046, Fire Management Assistance Grant; 97.048,
Disaster Housing Assistance to Individuals and Households In
Presidentially Declared Disaster Areas; 97.049, Presidentially
Declared Disaster Assistance--Disaster Housing Operations for
Individuals and Households; 97.050 Presidentially Declared Disaster
Assistance to Individuals and Households--Other Needs; 97.036,
Disaster Grants--Public Assistance (Presidentially Declared
Disasters); 97.039, Hazard Mitigation Grant.)

Robert J. Fenton,
Senior Official Performing the Duties of the Administrator, Federal
Emergency Management Agency.
[FR Doc. 2021-09162 Filed 4-30-21; 8:45 am]
BILLING CODE 9111-23-P


[Federal Register: December 13, 2005 (Volume 70, Number 238)]
[Notices]
[Page 73811-73815]
[DOCID:fr13de05-87]

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

SECURITIES AND EXCHANGE COMMISSION

[Release No. 34-52898; File No. SR-PCX-2005-87]

Self-Regulatory Organizations; The Pacific Exchange, Inc.; Notice
of Filing of Proposed Rule Change, and Amendment No. 1 Thereto,
Relating to the Tracking Order Process

December 6, 2005.
    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 July 26, 2005, the Pacific Exchange, Inc. (``PCX'' or ``Exchange'')
filed with the Securities and Exchange Commission (``Commission'') the
proposed rule change as described in Items I, II, and III below, which
Items have been prepared by the PCX. On November 22, 2005, the Exchange
submitted Amendment No. 1 to the proposed rule change.\3\ The
Commission is publishing this notice to solicit comments on the
proposed rule change, as amended, from interested persons.
---------------------------------------------------------------------------

    \1\ 15 U.S.C. 78s(b)(1).
    \2\ 17 CFR 240.19b-4.
    \3\ Amendment No.1, which replaced the original filing in its
entirety, made technical and clarifying changes to the proposed rule
change.
---------------------------------------------------------------------------

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

    The PCX, through its wholly-owned subsidiary PCX Equities, Inc.
(``PCXE''), proposes to amend its rules governing the Archipelago
Exchange (``ArcaEx''), the equities trading facility of PCXE. With this
filing, the Exchange proposes to replace the existing PCXE rules
describing the current ArcaEx Tracking Order Process \4\ with new
provisions setting forth a simplified price/time execution priority for
the Tracking Order Process. Further, the PCX

proposes to modify the Tracking Order \5\ for use in the revised
Tracking Order Process.
---------------------------------------------------------------------------

    \4\ See PCXE Rule 7.37(c).
    \5\ See PCXE Rule 7.31(f).
---------------------------------------------------------------------------

    The text of the proposed rule change, as amended, appears below.
Additions are italicized; deletions are [bracketed].
* * * * *

Rules of PCX Equities, Inc.

Rule 7
Equities Trading; Section 3 Archipelago Exchange-Orders and Modifiers
    Rule 7.31(a)-(e)--No Change.
    (f) Tracking Order.
    An undisplayed, priced round lot order that is eligible for
execution in the Tracking Order Process against orders equal to or less
than the aggregate size of Tracking Order interest available at that
price. If a Tracking Order is executed but not exhausted, the remaining
portion of the order shall be cancelled, without routing the order to
another market center or market participant.
    [(1) Any User may submit an instruction to the Archipelago Exchange
for the parameters of a Tracking Order at any time during the day. The
parameters shall include:]
    [(A) the maximum aggregate size, which is the aggregate size of all
partial orders generated in the Tracking Order Process for a particular
security that the User is willing to trade on that day;]
    [(B) the maximum tradeable size, which is the maximum size of any
partial order generated in response to an order entering the Tracking
Order Process that the User is willing to trade on that day;]
    [(C) the price in relation to the NBBO; and]
    [(D) the relevant security.]
    [(2) Once a User has submitted an instruction for the parameters of
the Tracking Order, the instruction will remain in effect until closing
or until the User has traded its maximum aggregate size for that day,
whichever comes first.]
    [(3) The Tracking Order Process rotation is as follows: Users who
have submitted an instruction for the parameters of a Tracking Order
will be assigned trades on a price/time rotating basis, such that
within each price level, trades shall be assigned by the time the
Users' instructions are received by the Archipelago Exchange. Within
each price level, the first User to send an instruction for a Tracking
Order will be the first User to be assigned a trade in the rotation
process. For each order that enters the Tracking Order Process, the
Tracking Order Process will rotate once through the Users in the
rotation pattern. In each rotation, the User will be responsible for
one trade up to the User's maximum tradeable size.]
    [(4) The order described in the User's Tracking Order instruction
will only be generated if:]
    [(A) an unfilled round or mixed lot order enters the Tracking Order
Process and]
    [(B) it is such User's turn as determined by the Tracking Order
Process rotation pattern.]
    [(5) Each partial order generated in a rotation is a limit order in
which:]
    [(A) The price is set at or better than the NBBO at the time the
unfilled order enters the Tracking Order Process, based on the User's
parameters; and]
    [(B) The size is (i) equal to the User's maximum tradeable size if
the unfilled order is equal to or larger than the maximum tradeable
size; or (ii) equal to the size of the unfilled order if the unfilled
order is smaller than the maximum tradeable size.]
    [(6) A User may modify the parameters of the instruction for the
Tracking Order from time to time, as the Corporation permits.]
    [(7) The Corporation shall suspend the Tracking Order Process for a
security when a locked or crossed market exists in that security. The
Tracking Order Process for that security shall resume when the locked
or crossed market in that security no longer exists.]
    [(8) Whenever in the judgment of the Corporation, because of an
influx of orders, a system malfunction or other unusual conditions or
circumstances, the interests of a fair and orderly market so require,
the Corporation may suspend the Tracking Order Process. The Tracking
Order Process shall resume when the Corporation determines that the
conditions supporting the suspension no longer exist.]
    (g) Odd Lot Tracking Order.
    (1)--No Change.
    (2) An Odd Lot Dealer may submit an instruction to the Archipelago
Exchange for the parameters of an OLTO at any time during the day. The
parameters shall include: [is a Tracking Order, as described in
paragraph (f), in which:]
    (A) The maximum aggregate size [is unlimited;], which is the
unlimited aggregate size of all orders generated in the Odd Lot
Tracking Order Process for a particular security that the Odd Lot
Dealer is willing to trade on that day;
    (B) The maximum tradeable size [is] up to 99 shares, which is the
maximum size of any order generated in response to an order entering
the Odd Lot Tracking Order Process that the Odd Lot Dealer is willing
to trade on that day;
    (C) The price is set at the NBBO; and
    (D) The relevant security [is one] in which the Odd Lot Dealer is
registered as such; and
    (E) The instruction must be in effect for the duration of Core
Trading Hours; provided, however, the order described in the OLTO
instruction will only be generated if:
    (1) An unfilled odd lot market order enters the Odd Lot Tracking
Order Process pursuant to Rule 7.37(c); or
    (2) An odd lot limit order causes a locked market as described in
Rule 7.56.
    (3) Each order generated in a rotation is a limit order in which:
    (A) The price is set at the NBBO at the time the unfilled order
enters the Odd Lot Tracking Order Process, based on the Odd Lot
Dealer's parameters; and
    (B) The size is (i) equal to the Odd Lot Dealer's maximum tradeable
size; or (ii) equal to the size of the unfilled order if the unfilled
order is smaller than the maximum tradeable size.
    (4) An Odd Lot Dealer may modify the parameters of the instruction
for the Odd Lot Tracking Order from time to time, as the Corporation
permits.
    (5) The Corporation shall suspend the Odd Lot Tracking Order
Process for a security when a locked or crossed market exists in that
security. The Odd Lot Tracking Order Process for that security shall
resume when the locked or crossed market in that security no longer
exists.
    (6) Whenever in the judgment of the Corporation, because of an
influx of orders, a system malfunction or other unusual conditions or
circumstances, the interests of a fair and orderly market so require,
the Corporation may suspend the Odd Lot Tracking Order Process. The Odd
Lot Tracking Order Process shall resume when the Corporation determines
that the conditions supporting the suspension no longer exist.
    (h)-(hh)--No Change.
* * * * *
Order Execution
Rule 7.37
* * * * *
    (a)-(b)--No Change.
    (c) Step 4: Tracking Order Process. During Core Trading Hours only,
orders may be matched and executed in the Tracking Order Process as
follows: If an order has not been executed in its entirety pursuant to
paragraphs (a) and (b) of this Rule, the Archipelago Exchange shall
match and execute any remaining part of the order in the Tracking Order
Process in price/time priority [the following manner]; provided,
however, any portion of an

order received from another market center or market participant shall
be cancelled immediately[:].
    [(1) If the unfilled order is a mixed lot or round lot order, the
order shall be matched against any Tracking Orders pursuant to the
rotation pattern described in Rule 7.31(f)(3) for immediate execution
thereafter. After the order has been matched against any Tracking
Orders, if the order has not been executed in its entirety and the
remaining part of the order is an odd lot, the odd lot order shall be
executed in the Odd Lot Tracking Order Process, as described in
paragraph (2).]

Odd Lot Tracking Order Process

    [(2)](1) If the unfilled order is an odd lot, and there is an Odd
Lot Dealer registered in that security, the order shall be matched in
the Odd Lot Tracking Order Process against any OLTOs pursuant to the
following rotation pattern:
    Odd Lot Dealers who have submitted an instruction for the
parameters of an Odd Lot Tracking Order will be assigned trades on a
price/time rotating basis, such that within each price level, trades
shall be assigned by the time the Odd Lot Dealers' instructions are
received by the Archipelago Exchange. Within each price level, the
first Odd Lot Dealer to send an instruction for an Odd Lot Tracking
Order will be the first Odd Lot Dealer to be assigned a trade in the
rotation process. For each order that enters the Odd Lot Tracking Order
Process, the Odd Lot Tracking Order Process will rotate once through
the Odd Lot Dealers in the rotation pattern. In each rotation, the Odd
Lot Dealer will be responsible for one trade up to the Odd Lot Dealer's
maximum tradeable size. [described in Rule 7.31(f)(3) for immediate
execution thereafter.]
    (2) If there is no Odd Lot Dealer registered in that security, the
odd lot will be routed away pursuant to PCXE Rule 7.37(d).
    (d)--No Change.
* * * * *

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 PCX 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
    To enhance participation on the ArcaEx facility, the Exchange
proposes to restructure its Tracking Order Process by modifying the
current rule text governing the Tracking Order Process to implement a
simplified price/time priority execution process. In addition, the
Exchange proposes to modify the existing Tracking Order for use in the
revised and simplified Tracking Order Process.

Current ArcaEx Tracking Order Process

    Current PCXE Rules 7.31(f) and 7.37(c) describe the Tracking Order
Process. The purpose of the Tracking Order Process is to provide a
final opportunity for execution against any remaining liquidity on the
ArcaEx system before routing to an away market center. As currently
written, Users \6\ of the Tracking Order Process submit a Tracking
Order instruction to ArcaEx based on certain parameters. ArcaEx
generates orders based on these User instructions. Executions occur in
a rotating manner pursuant to PCXE Rule 7.37(c). In general, the first
User to send an instruction for a Tracking Order for each price level
is the first User to be assigned a trade in the rotation process. With
each rotation, a User who has entered a Tracking Order is responsible
for one trade up to the User's maximum tradable size.
---------------------------------------------------------------------------

    \6\ See PCXE Rule 1.1(yy).
---------------------------------------------------------------------------

Proposed Changes to the Tracking Order Process

    As proposed, the rule change would modify the current Tracking
Order Process described above and replace it with a new process based
on the submission of orders, rather than instructions, to be executed
in price/time priority. Users would no longer be required to submit and
maintain Tracking Order instructions to participate in the Tracking
Order Process. Instead, Users would simply submit a Tracking Order (as
described below) designed specifically to reside in the modified
Tracking Order Process. ArcaEx would continue to process all orders
residing in the modified Tracking Order Process after it processes
orders entered into the other ArcaEx execution processes.\7\ Within the
Tracking Order Process, the modified Tracking Order would execute based
on its price and time received as opposed to the price and time the
instruction was received.
---------------------------------------------------------------------------

    \7\ See PCXE Rule 7.37 for a description of the ArcaEx execution
processes that precede the Tracking Order Process. These include the
Directed Process, Display Process and Working Order Process.
---------------------------------------------------------------------------

    This filing also proposes changes to the existing Odd Lot Tracking
Order Process.\8\ The Odd Lot Tracking Order Process that is currently
available for incoming odd lot orders would continue to exist and would
be distinct from the Tracking Order Process which would be available
for incoming mixed lot and round lot orders. Accordingly, the existing
Tracking Order Process and associated assignment of trades on a price/
time rotating basis would continue to apply to the Odd Lot Tracking
Order Process. The rule text that previously resided in PCXE Rule
7.31(f)(3) would be inserted into PCXE Rule 7.37(c)(1) to describe the
Odd Lot Tracking Order Process and revised to clarify that only Odd Lot
Dealers \9\ may be assigned trades under the Odd Lot Tracking Order
Process.\10\ Also, under the proposal, orders would only participate in
the Odd Lot Tracking Order Process if there is an Odd Lot Dealer
registered in that security. If no such dealer exists, the odd lot
order would be routed away pursuant to PCXE Rule 7.37(d). Further, the
proposal includes clarifying changes that the Odd Lot Tracking Order
Process does not generate partial fills.
---------------------------------------------------------------------------

    \8\ See PCXE Rule 7.37(c).
    \9\ See PCXE Rule 1.1(gg).
    \10\ Similarly, the rule text that describes the generation of
Tracking Orders in PCXE Rule 7.31(f) and that also applies to Odd
Lot Tracking Orders would be inserted in PCXE Rule 7.31(g). PCXE
Rule 7.31(g) would also be further modified, as necessary, to
accommodate such insertion.
---------------------------------------------------------------------------

The Tracking Order

    The rule proposal modifies an existing order type, the Tracking
Order, for use in the revised Tracking Order Process. Currently, a User
submits a Tracking Order instruction that includes specific parameters
that must be entered including maximum aggregate size and maximum
tradeable size. The revised Tracking Order is an undisplayed, priced
order with a specified size that would be eligible for execution
against other ArcaEx orders that have already been exposed to other
ArcaEx execution processes and have not been executed in full. The
Tracking Order would execute in the revised Tracking Order Process
against an incoming order only if the size of the incoming order is
less than or equal to the aggregate Tracking Order interest available
at the price of the incoming order and the incoming order is not an odd
lot order. If the size of any contra order exposed to the revised
Tracking Order Process is greater than

the size of the aggregate Tracking Order interest residing in the
Tracking Order Process at the executable price, such Tracking Orders
would not execute against the contra order. For example, if a Tracking
Order was entered for 300 shares and a contra order with a size of 301
shares was exposed to the Tracking Order Process (after being exposed
to all other ArcaEx execution processes), the contra order would not
execute against the Tracking Order and would route out of ArcaEx.
    Tracking Orders would execute only if the price of the Tracking
Order is equal to or better than prices found at away markets (and
would therefore execute at the price of the NBBO at the time of
execution or better).\11\ If a Tracking Order is executed but not
exhausted, the remaining portion of the Tracking Order shall be
cancelled, without routing to another market center or market
participant. Tracking Orders residing in the Tracking Order Process
would be sorted and executed against in price/time priority. Tracking
Orders may only be entered as round lots and are not displayed to any
Users. However, mixed lot contra orders exposed to a Tracking Order
would be eligible for execution against such Tracking Order (assuming
the size of the contra order is equal to or less than the size of the
Tracking Order).\12\ An odd lot contra order would be exposed to an Odd
Lot Tracking Order and eligible for execution against such Odd Lot
Tracking Order as described above. In the circumstance when a Tracking
Order receives a partial fill, the unexecuted portion of the Tracking
Order would be cancelled. Because Tracking Orders may be cancelled and
are only executed against once, the current provision in PCXE Rule
7.31(f)(8) that enables ArcaEx to suspend the Tracking Order Process
because of an influx of orders, a system malfunction, or other unusual
circumstances is no longer relevant and would be removed. In addition,
the current provision in PCXE Rule 7.31(f)(7) is no longer relevant
because the new Tracking Order Process would be integrated into
existing order book processing, which is not suspended in the instance
of a locked or crossed market. Accordingly, PCXE Rule 7.31(f)(7) would
not be incorporated into the modified Tracking Order Process. Tracking
Orders would not route to other market centers, would not be eligible
for execution against other Tracking Orders, and would not execute
against incoming ITS orders.
---------------------------------------------------------------------------

    \11\ See PCXE Rule 7.37 which states that ``for an execution to
occur in any Order Process, the price must be equal to or better
than the NBBO.''
    \12\ PCX clarified that a contra order would be eligible for
execution against such Tracking Order if the size of the contra
order is equal to or less than the size of the Tracking Order.
Telephone conversation between Bridget M. Farrell, Director,
Strategy PCX/ArcaEx and Johnna B. Dumler, Attorney, Division of
Market Regulation, Commission, on December 1, 2005.
---------------------------------------------------------------------------

    The Exchange believes that the implementation of the aforementioned
rule changes relating to ArcaEx order processing would enhance order
execution opportunities on ArcaEx. In particular, the Exchange believes
the revisions to the Tracking Order Process and Tracking Order would
simplify the Tracking Order Process and encourage order interaction on
ArcaEx.
2. Statutory Basis
    The Exchange believes that the proposed rule change, as amended, is
consistent with section 6(b) of the Act,\13\ in general, and furthers
the objectives of section 6(b)(5) of the Act \14\ in particular because
it is designed to prevent fraudulent and manipulative acts and
practices, to promote just and equitable principles of trade, to foster
cooperation and coordination with persons engaged in facilitating
transactions in securities, and to remove impediments to and perfect
the mechanism of a free and open market and a national market system.
---------------------------------------------------------------------------

    \13\ 15 U.S.C. 78f(b).
    \14\ 15 U.S.C. 78f(b)(5).
---------------------------------------------------------------------------

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

    The PCX 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.

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

    Written comments on the proposed rule change were neither solicited
nor received.

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

    Within 35 days of the date of publication of this notice in the
Federal Register or within such longer period (i) as the Commission may
designate up to 90 days of such date if it finds such longer period to
be appropriate and publishes its reasons for so finding or (ii) as to
which the Exchange consents, the Commission will:
    (A) By order approve such proposed rule change, as amended, or
    (B) Institute proceedings to determine whether the proposed rule
change, as amended, 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, as amended, is consistent with the Act. Comments may be
submitted by any of the following methods:

Electronic Comments

     Use the Commission's Internet comment form at (http://www.sec.gov/rules/sro.shtml.
); or     Send an e-mail to<EMAIL_ADDRESS>Please include

File Number SR-PCX-2005-87 on the subject line.

Paper Comments

     Send paper comments in triplicate to Jonathan G. Katz,
Secretary, Securities and Exchange Commission, 100 F Street, NE.,
Washington, DC 20549-9303.
    All submissions should refer to File Number SR-PCX-2005-87. This
file number should be included on the subject line if e-mail 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 inspection
and copying in the Commission's Public Reference Room. Copies of such
filing also will be available for inspection and copying at the
principal office of the PCX. 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-PCX-2005-87 and
should be submitted on or before January 3, 2006.

    For the Commission, by the Division of Market Regulation,
pursuant to delegated authority.\15\
---------------------------------------------------------------------------

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

Jonathan G. Katz,
Secretary.
 [FR Doc. E5-7263 Filed 12-12-05; 8:45 am]

BILLING CODE 8010-01-P


[Federal Register Volume 83, Number 207 (Thursday, October 25, 2018)]
[Rules and Regulations]
[Pages 53806-53807]
[FR Doc No: 2018-23146]

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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 71

[Docket No. FAA-2018-0126; Airspace Docket No. 18-AAL-6]
RIN 2120-AA66

Establishment of Class E Airspace; Hoonah, AK

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Final rule.

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

SUMMARY: This action establishes Class E airspace extending upward from
700 feet above the surface, at Hoonah Airport, Hoonah, AK, to
accommodate area navigation (RNAV) procedures at the airport for the
safety and management of instrument flight rules (IFR) operations
within the National Airspace System.

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

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

FOR FURTHER INFORMATION CONTACT: Tom Clark, Federal Aviation
Administration, Operations Support Group, Western Service Center, 2200
S 216th St., Des Moines, WA 98198-6547; telephone<PHONE_NUMBER>.

SUPPLEMENTARY INFORMATION:

Authority for This Rulemaking

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

History

    The FAA published a notice of proposed rulemaking in the Federal
Register (83 FR 19655; May 4, 2018) for Docket No. FAA-2018-0126 to
establish Class E airspace extending upward from 700 feet above the
surface at Hoonah Airport, Hoonah, AK. Interested parties were invited
to participate in this rulemaking effort by submitting written comments
on the proposal to the FAA. No comments were received.
    Class E airspace designations are published in paragraph 6005 of
FAA Order 7400.11C, dated August 13, 2018, and effective September 15,
2018, which is incorporated by reference in 14 CFR 71.1. The Class E
airspace designation listed in this document will be published
subsequently in the Order.

Availability and Summary of Documents for Incorporation by Reference

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

The Rule

    The FAA is amending Title 14 Code of Federal Regulations (14 CFR)
part 71 by establishing Class E airspace extending upward from 700 feet
above the surface within a 3-mile radius of Hoonah Airport, Hoonah, AK,
with a segment 3 miles each side of the 077[deg] bearing from the
airport extending from the 3-mile radius to 8.1 miles east of the
airport. This airspace area supports IFR operations at Hoonah Airport,
and will be unaffected by any proposed changes that occurs at any other
airport.

Regulatory Notices and Analyses

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

Environmental Review

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

List of Subjects in 14 CFR Part 71

    Airspace, Incorporation by reference, Navigation (air).

Adoption of the Amendment

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

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

0
1. The authority citation for 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 7400.11C,
Airspace Designations and Reporting Points, dated August 13, 2018, and
effective September 15, 2018, is amended as follows:

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

* * * * *

AAL AK E5 Hoonah, AK [New]

Hoonah Airport, AK
    (Lat. 58[deg]05'46'' N, long. 135[deg]24'32'' W)

    That airspace extending upward from 700 feet above the surface
within a 3-mile radius of Hoonah Airport, and within 3 miles each
side of the airport 077[deg] bearing extending from the airport 3-
mile radius to 8.1 miles east of the airport.

    Issued in Seattle, Washington, on October 12, 2018.
Shawn M. Kozica,
Group Manager, Operations Support Group, Western Service Center.
[FR Doc. 2018-23146 Filed 10-24-18; 8:45 am]
 BILLING CODE 4910-13-P


[Federal Register Volume 77, Number 223 (Monday, November 19, 2012)]
[Notices]
[Pages 69489-69490]
[FR Doc No: 2012-28053]

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

DEPARTMENT OF HOMELAND SECURITY

Federal Emergency Management Agency

[Internal Agency Docket No. FEMA-3359-EM;Docket ID FEMA-2011-0001]

Virginia; Emergency and Related Determinations

AGENCY: Federal Emergency Management Agency, DHS.

ACTION: Notice.

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

SUMMARY: This is a notice of the Presidential declaration of an
emergency for the Commonwealth of Virginia (FEMA-3359-EM), dated
October 29, 2012, and related determinations.

DATES: Effective Date: October 29, 2012.

FOR FURTHER INFORMATION CONTACT: Peggy Miller, Office of Response and
Recovery, Federal Emergency Management Agency, 500 C Street SW.,
Washington, DC 20472,<PHONE_NUMBER>.

SUPPLEMENTARY INFORMATION: Notice is hereby given that, in a letter
dated October 29, 2012, the President issued an emergency declaration
under the authority of the Robert T. Stafford Disaster Relief and
Emergency Assistance Act, 42 U.S.C. 5121-5207 (the Stafford Act), as
follows:

    I have determined that the emergency conditions in the
Commonwealth of Virginia resulting from Hurricane Sandy beginning on
October 26, 2012, and continuing, are of sufficient severity and
magnitude to warrant an emergency declaration under the Robert T.
Stafford Disaster Relief and Emergency Assistance Act, 42 U.S.C.
5121 et seq. (``the Stafford Act''). Therefore, I declare that such
an emergency exists in the Commonwealth of Virginia.
    You are authorized to provide appropriate assistance for
required emergency measures, authorized under Title V of the
Stafford Act, to save lives and to protect property and public
health and safety, and to lessen or avert the threat of a
catastrophe in the designated areas. Specifically, you are
authorized to provide assistance for emergency protective measures
(Category B), limited to direct Federal assistance, under the Public
Assistance program.
    Consistent with the requirement that Federal assistance is
supplemental, any Federal funds provided under the Stafford Act for
Public Assistance will be limited to 75 percent of the total
eligible costs. In order to provide Federal assistance, you are
hereby authorized to allocate from funds available for these
purposes such amounts as you find necessary for Federal emergency
assistance and administrative expenses.
    Further, you are authorized to make changes to this declaration
for the approved assistance to the extent allowable under the
Stafford Act.

    The Federal Emergency Management Agency (FEMA) hereby gives notice
that pursuant to the authority vested in the Administrator, Department
of Homeland Security, under Executive Order 12148, as amended, Donald
L. Keldsen, of FEMA is appointed to act as the Federal Coordinating
Officer for this declared emergency.
    The following areas of the Commonwealth of Virginia have been
designated as adversely affected by this declared emergency:

    Emergency protective measures (Category B), limited to direct
federal assistance, under the Public Assistance program for all
counties and independent cities in the Commonwealth of Virginia.

The following Catalog of Federal Domestic Assistance Numbers (CFDA)
are to be used for reporting and drawing funds: 97.030, Community
Disaster Loans; 97.031, Cora Brown Fund; 97.032, Crisis Counseling;
97.033, Disaster Legal Services; 97.034, Disaster Unemployment
Assistance (DUA); 97.046, Fire Management Assistance Grant;

97.048, Disaster Housing Assistance to Individuals and Households In
Presidentially Declared Disaster Areas; 97.049, Presidentially
Declared Disaster Assistance--Disaster Housing Operations for
Individuals and Households; 97.050, Presidentially Declared Disaster
Assistance to Individuals and Households--Other Needs; 97.036,
Disaster Grants--Public Assistance (Presidentially Declared
Disasters); 97.039, Hazard Mitigation Grant.

W. Craig Fugate,
Administrator, Federal Emergency Management Agency.
[FR Doc. 2012-28053 Filed 11-16-12; 8:45 am]
BILLING CODE 9111-23-P