[Federal Register Volume 82, Number 124 (Thursday, June 29, 2017)]
[Rules and Regulations]
[Pages 29435-29438]
[FR Doc No: 2017-13565]

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

DEPARTMENT OF HOMELAND SECURITY

Federal Emergency Management Agency

44 CFR Part 64

[Docket ID FEMA-2017-0002; Internal Agency Docket No. FEMA-8487]

Suspension of Community Eligibility

AGENCY: Federal Emergency Management Agency, DHS.

ACTION: Final rule.

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

SUMMARY: This rule identifies communities where the sale of flood
insurance has been authorized under the National Flood Insurance
Program (NFIP) that are scheduled for suspension on the effective dates
listed within this rule because of noncompliance with the floodplain
management requirements of the program. If the Federal Emergency
Management Agency (FEMA) receives documentation that the community has
adopted the required floodplain management measures prior to the
effective suspension date given in this rule, the suspension will not
occur and a notice of this will be provided by publication in the
Federal Register on a subsequent date. Also, information identifying
the current participation status of a community can be obtained from
FEMA's Community Status Book (CSB). The CSB is available at https://www.fema.gov/national-flood-insurance-program-community-status-book.

DATES: The effective date of each community's scheduled suspension is
the third date (``Susp.'') listed in the third column of the following
tables.

FOR FURTHER INFORMATION CONTACT: If you want to determine whether a
particular community was suspended on the suspension date or for
further information, contact Patricia Suber, Federal Insurance and
Mitigation Administration, Federal Emergency Management Agency, 400 C
Street SW., Washington, DC 20472,<PHONE_NUMBER>.

SUPPLEMENTARY INFORMATION: The NFIP enables property owners to purchase
Federal flood insurance that is not otherwise generally available from
private insurers. In return, communities agree to adopt and administer
local floodplain management measures aimed at protecting lives and new
construction from future flooding. Section 1315 of the National Flood
Insurance Act of 1968, as amended, 42 U.S.C. 4022, prohibits the sale
of NFIP flood insurance unless an appropriate public body adopts
adequate floodplain management measures with effective enforcement
measures. The communities listed in this document no longer meet that
statutory requirement for compliance with program regulations, 44 CFR
part 59. Accordingly, the communities will be suspended on the
effective date in the third column. As of that date, flood insurance
will no longer be available in the community. We recognize that some of
these communities may adopt and submit the required documentation of
legally enforceable floodplain management measures after this rule is
published but prior to the actual suspension date. These communities
will not be suspended and will continue to be eligible for the sale of
NFIP flood insurance. A notice withdrawing the suspension of such
communities will be published in the Federal Register.
    In addition, FEMA publishes a Flood Insurance Rate Map (FIRM) that
identifies the Special Flood Hazard Areas (SFHAs) in these communities.
The date of the FIRM, if one has been published, is indicated in the
fourth column of the table. No direct Federal financial assistance
(except assistance pursuant to the Robert T. Stafford Disaster Relief
and Emergency Assistance Act not in connection with a flood) may be
provided for construction or acquisition of buildings in identified
SFHAs for communities not participating in the NFIP and identified for
more than a year on FEMA's initial FIRM for the community as having
flood-prone areas (section 202(a) of the Flood Disaster Protection Act
of 1973, 42 U.S.C. 4106(a), as amended). This prohibition against
certain types of Federal assistance becomes effective for the
communities listed on the date shown in the last column. The
Administrator finds that notice and public comment procedures under 5
U.S.C. 553(b), are impracticable and unnecessary because communities
listed in this final rule have been adequately notified.
    Each community receives 6-month, 90-day, and 30-day notification
letters addressed to the Chief Executive Officer stating that the
community will be suspended unless the required

floodplain management measures are met prior to the effective
suspension date. Since these notifications were made, this final rule
may take effect within less than 30 days.
    National Environmental Policy Act. FEMA has determined that the
community suspension(s) included in this rule is a non-discretionary
action and therefore the National Environmental Policy Act of 1969 (42
U.S.C. 4321 et seq.) does not apply.
    Regulatory Flexibility Act. The Administrator has determined that
this rule is exempt from the requirements of the Regulatory Flexibility
Act because the National Flood Insurance Act of 1968, as amended,
Section 1315, 42 U.S.C. 4022, prohibits flood insurance coverage unless
an appropriate public body adopts adequate floodplain management
measures with effective enforcement measures. The communities listed no
longer comply with the statutory requirements, and after the effective
date, flood insurance will no longer be available in the communities
unless remedial action takes place.
    Regulatory Classification. This final rule is not a significant
regulatory action under the criteria of section 3(f) of Executive Order
12866 of September 30, 1993, Regulatory Planning and Review, 58 FR
51735.
    Executive Order 13132, Federalism. This rule involves no policies
that have federalism implications under Executive Order 13132.
    Executive Order 12988, Civil Justice Reform. This rule meets the
applicable standards of Executive Order 12988.
    Paperwork Reduction Act. This rule does not involve any collection
of information for purposes of the Paperwork Reduction Act, 44 U.S.C.
3501 et seq.

List of Subjects in 44 CFR Part 64

    Flood insurance, Floodplains.

    Accordingly, 44 CFR part 64 is amended as follows:

PART 64--[AMENDED]

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

    Authority:  42 U.S.C. 4001 et seq.; Reorganization Plan No. 3 of
1978, 3 CFR, 1978 Comp.; p. 329; E.O. 12127, 44 FR 19367, 3 CFR,
1979 Comp.; p. 376.

Sec.  64.6   [Amended]

0
2. The tables published under the authority of Sec.  64.6 are amended
as follows:

----------------------------------------------------------------------------------------------------------------
                                                 Effective date
                                                 authorization/
                                   Community    cancellation of    Current effective map   Date Certain Federal
       State and location             No.        sale of flood             date            assistance  no longer
                                                  insurance in                              available in  SFHAs
                                                   community
----------------------------------------------------------------------------------------------------------------
                                                    Region I
----------------------------------------------------------------------------------------------------------------
Maine: Alexander, Town of,             230303  March 2, 1978,     July 18, 2017.........  July 18, 2017
 Washington County.                             Emerg; September
                                                4, 1985, Reg;
                                                July 18, 2017,
                                                Susp.
Baring Plantation, Washington          230468  March 19, 1974,    -*do-.................  -do-
 County.                                        Emerg; March 15,
                                                1982, Reg; July
                                                18, 2017, Susp.
Brookton, Township of,                 230470  March 19, 1974,    -do-..................  -do-
 Washington County.                             Emerg; November
                                                1, 1985, Reg;
                                                July 18, 2017,
                                                Susp.
Calais, City of, Washington            230134  July 31, 1975,     -do-..................  -do-
 County.                                        Emerg; August 3,
                                                1994, Reg; July
                                                18, 2017, Susp.
Charlotte, Town of, Washington         230437  May 1, 2000,       -do-..................  -do-
 County.                                        Emerg; August 1,
                                                2008, Reg; July
                                                18, 2017, Susp.
Cherryfield, Town of,                  230135  July 23, 1975,     -do-..................  -do-
 Washington County.                             Emerg; May 4,
                                                1988, Reg; July
                                                18, 2017, Susp.
Columbia, Town of, Washington          230307  June 24, 2010,     -do-..................  -do-
 County.                                        Emerg; April 1,
                                                2011, Reg; July
                                                18, 2017, Susp.
Danforth, Town of, Washington          230136  April 14, 1975,    -do-..................  -do-
 County.                                        Emerg; September
                                                18, 1985, Reg;
                                                July 18, 2017,
                                                Susp.
Dennysville, Town of,                  230312  July 23, 1975,     -do-..................  -do-
 Washington County.                             Emerg; August
                                                19, 1985, Reg;
                                                July 18, 2017,
                                                Susp.
East Machias, Town of,                 230313  April 8, 1983,     -do-..................  -do-
 Washington County.                             Emerg; September
                                                4, 1985, Reg;
                                                July 18, 2017,
                                                Susp.
Eastport, City of, Washington          230137  June 11, 1975,     -do-..................  -do-
 County.                                        Emerg; December
                                                3, 1987, Reg;
                                                July 18, 2017,
                                                Susp.
Edmunds, Township of,                  230471  March 19, 1975,    -do-..................  -do-
 Washington County.                             Emerg; August
                                                19, 1985, Reg;
                                                July 18, 2017,
                                                Susp.
Grand Lake Stream Plantation,          230469  March 19, 1975,    -do-..................  -do-
 Washington County.                             Emerg; August 5,
                                                1985, Reg; July
                                                18, 2017, Susp.
Jonesboro, Town of, Washington         230315  February 27,       -do-..................  -do-
 County.                                        2006, Emerg;
                                                August 1, 2008,
                                                Reg; July 18,
                                                2017, Susp.
Lambert Lake, Township of,             230472  March 19, 1975,    -do-..................  -do-
 Washington County.                             Emerg; January
                                                17, 1985, Reg;
                                                July 18, 2017,
                                                Susp.
Machias, Town of, Washington           230140  April 24, 1975,    -do-..................  -do-
 County.                                        Emerg; November
                                                18, 1988, Reg;
                                                July 18, 2017,
                                                Susp.
Milbridge, Town of, Washington         230142  May 14, 1975,      -do-..................  -do-
 County.                                        Emerg; May 3,
                                                1990, Reg; July
                                                18, 2017, Susp.
Pembroke, Town of, Washington          230143  June 9, 1999,      -do-..................  -do-
 County.                                        Emerg; April 1,
                                                2009, Reg; July
                                                18, 2017, Susp.
Perry, Town of, Washington             230319  July 30, 1975,     -do-..................  -do-
 County.                                        Emerg; September
                                                4, 1985, Reg;
                                                July 18, 2017,
                                                Susp.
Princeton, Town of, Washington         230320  June 11, 1975,     -do-..................  -do-
 County.                                        Emerg; August
                                                19, 1985, Reg;
                                                July 18, 2017,
                                                Susp.
Robbinston, Town of, Washington        230321  July 23, 1975,     -do-..................  -do-
 County.                                        Emerg; August
                                                19, 1985, Reg;
                                                July 18, 2017,
                                                Susp.

Roque Bluffs, Town of,                 230322  July 16, 1975,     -do-..................  -do-
 Washington County.                             Emerg; September
                                                18, 1985, Reg;
                                                July 18, 2017,
                                                Susp.
Topsfield, Town of, Washington         230324  June 22, 2010,     -do-..................  -do-
 County.                                        Emerg; March 1,
                                                2011, Reg; July
                                                18, 2017, Susp.
Trescott, Township of,                 230473  March 19, 1975,    -do-..................  -do-
 Washington County.                             Emerg; August 5,
                                                1985, Reg; July
                                                18, 2017, Susp.
Wesley, Town of, Washington            230327  April 1, 1976,     -do-..................  -do-
 County.                                        Emerg; September
                                                18, 1985, Reg;
                                                July 18, 2017,
                                                Susp.
Whitneyville, Town of,                 230329  N/A, Emerg;        -do-..................  -do-
 Washington County.                             February 8,
                                                2001, Reg; July
                                                18, 2017, Susp.
----------------------------------------------------------------------------------------------------------------
                                                   Region III
----------------------------------------------------------------------------------------------------------------
Pennsylvania: Belle Vernon,            420457  July 19, 1974,     -do-..................  -do-
 Borough of, Fayette County.                    Emerg; July 16,
                                                1981, Reg; July
                                                18, 2017, Susp.
Brownsville, Borough of,               420458  July 9, 1975,      -do-..................  -do-
 Fayette County.                                Emerg; September
                                                16, 1981, Reg;
                                                July 18, 2017,
                                                Susp.
Bullskin, Township of, Fayette         421622  March 23, 1976,    -do-..................  -do-
 County.                                        Emerg; April 16,
                                                1991, Reg; July
                                                18, 2017, Susp.
Connellsville, City of, Fayette        420459  July 23, 1973,     -do-..................  -do-
 County.                                        Emerg; March 1,
                                                1978, Reg; July
                                                18, 2017, Susp.
Connellsville, Township of,            421623  March 3, 1977,     -do-..................  -do-
 Fayette County.                                Emerg; July 16,
                                                1991, Reg; July
                                                18, 2017, Susp.
Dunbar, Borough of, Fayette            420461  June 20, 1974,     -do-..................  -do-
 County.                                        Emerg; July 4,
                                                1988, Reg; July
                                                18, 2017, Susp.
Fairchance, Borough of, Fayette        420463  November 14,       -do-..................  -do-
 County.                                        1975, Emerg;
                                                April 16, 1991,
                                                Reg; July 18,
                                                2017, Susp.
Lower Tyrone, Township of,             421630  March 16, 1977,    -do-..................  -do-
 Fayette County.                                Emerg; March 4,
                                                1988, Reg; July
                                                18, 2017, Susp.
Markleysburg, Borough of,              422606  January 18, 1985,  -do-..................  -do-
 Fayette County.                                Emerg; June 19,
                                                1985, Reg; July
                                                18, 2017, Susp.
Menallen, Township of, Fayette         421632  July 18, 1974,     -do-..................  -do-
 County.                                        Emerg; April 16,
                                                1991, Reg; July
                                                18, 2017, Susp.
Newell, Borough of, Fayette            420465  February 20,       -do-..................  -do-
 County.                                        1975, Emerg;
                                                April 15, 1981,
                                                Reg; July 18,
                                                2017, Susp.
Ohiopyle, Borough of, Fayette          421615  March 8, 1985,     -do-..................  -do-
 County.                                        Emerg; December
                                                1, 1986, Reg;
                                                July 18, 2017,
                                                Susp.
Springhill, Township of,               421639  June 15, 1976,     -do-..................  -do-
 Fayette County.                                Emerg; March 18,
                                                1991, Reg; July
                                                18, 2017, Susp.
Uniontown, City of, Fayette            420466  May 4, 1973,       -do-..................  -do-
 County.                                        Emerg; May 1,
                                                1978, Reg; July
                                                18, 2017, Susp.
Wharton, Township of, Fayette          421642  November 19,       -do-..................  -do-
 County.                                        1975, Emerg;
                                                January 1, 1987,
                                                Reg; July 18,
                                                2017, Susp.
----------------------------------------------------------------------------------------------------------------
                                                    Region IV
----------------------------------------------------------------------------------------------------------------
South Carolina: Reevesville,           450218  August 11, 2006,   -do-..................  -do-
 Town of, Dorchester County.                    Emerg; N/A, Reg;
                                                July 18, 2017,
                                                Susp.
Summerville, Town of, Berkeley,        450073  November 5, 1973,  -do-..................  -do-
 Charleston and Dorchester                      Emerg; June 15,
 Counties.                                      1981, Reg; July
                                                18, 2017, Susp.
                                                    Region IX
----------------------------------------------------------------------------------------------------------------
California: Mendocino County,          060183  December 17,       -do-..................  -do-
 Unincorporated Areas.                          1974, Emerg;
                                                June 1, 1983,
                                                Reg; July 18,
                                                2017, Susp.
Point Arena, City of, Mendocino        060185  June 28, 1976,     -do-..................  -do-
 County.                                        Emerg; August 3,
                                                1984, Reg; July
                                                18, 2017, Susp.
----------------------------------------------------------------------------------------------------------------
-*do- = Ditto.
Code for reading third column: Emerg. --Emergency; Reg. --Regular; Susp. --Suspension.

    Dated: June 20, 2017.
Michael M. Grimm,
Assistant Administrator for Mitigation, Federal Insurance and
Mitigation Administration, Department of Homeland Security, Federal
Emergency Management Agency.
[FR Doc. 2017-13565 Filed 6-28-17; 8:45 am]
BILLING CODE 9110-12-P


[Federal Register Volume 81, Number 40 (Tuesday, March 1, 2016)]
[Notices]
[Page 10702]
[FR Doc No: 2016-04516]

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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

Agency Information Collection Activities: Requests for Comments;
Clearance of Renewed Approval of Information Collection: Small Unmanned
Aircraft Registration System (sUAS)

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Notice and request for comments.

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

SUMMARY: In accordance with the Paperwork Reduction Act of 1995, FAA
invites public comments about our intention to request the Office of
Management and Budget (OMB) approval to renew a previously approved
information collection. Aircraft registration is necessary to ensure
personal accountability among all users of the national airspace
system. Aircraft registration also allows the FAA and law enforcement
agencies to address non-compliance by providing the means by which to
identify an aircraft's owner and operator.

DATES: Written comments should be submitted by May 2, 2016.

ADDRESSES: Send comments to the FAA at the following address: Ronda
Thompson, Room 441, Federal Aviation Administration, ASP-110, 950
L'Enfant Plaza SW., Washington, DC 20024.
    Public Comments Invited: You are asked to comment on any aspect of
this information collection, including (a) Whether the proposed
collection of information is necessary for FAA's performance; (b) the
accuracy of the estimated burden; (c) ways for FAA to enhance the
quality, utility and clarity of the information collection; and (d)
ways that the burden could be minimized without reducing the quality of
the collected information. The agency will summarize and/or include
your comments in the request for OMB's clearance of this information
collection.

FOR FURTHER INFORMATION CONTACT: Ronda Thompson by email at:
<EMAIL_ADDRESS>
SUPPLEMENTARY INFORMATION:
    OMB Control Number: 2120-0765.
    Title: Small Unmanned Aircraft Registration System (sUAS).
    Form Numbers: There are no FAA forms associated with this
collection.
    Type of Review: Renewal of an information collection.
    Background: The Secretary of the Department of Transportation (DOT)
and the Administrator of the Federal Aviation Administration (FAA)
recently affirmed that all unmanned aircraft, including model aircraft,
are aircraft. As such, in accordance with 49 U.S.C. 44101(a) and as
further prescribed in 14 CFR part 47, registration is required prior to
operation. See 80 FR 63912, 63913 (October 22, 2015). Aircraft
registration is necessary to ensure personal accountability among all
users of the national airspace system. See id. Aircraft registration
also allows the FAA and law enforcement agencies to address non-
compliance by providing the means by which to identify an aircraft's
owner and operator.
    Respondents: Approximately 1.9 million registrants annually.
    Frequency: Information is collected on occasion.
    Estimated Average Burden per Response: 4.25 minutes.
    Estimated Total Annual Burden: 141,158 hours.

    Issued in Washington, DC, on February 24, 2016.
Ronda Thompson,
FAA Information Collection Clearance Officer, Performance, Policy, and
Records Management Branch, ASP-110.
[FR Doc. 2016-04516 Filed 2-29-16; 8:45 am]
BILLING CODE 4910-13-P


[Federal Register: August 2, 2006 (Volume 71, Number 148)]
[Rules and Regulations]
[Page 43660-43664]
[DOCID:fr02au06-8]

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

ENVIRONMENTAL PROTECTION AGENCY

40 CFR Part 180

[EPA-HQ-OPP-2005-0245; FRL-8079-2]

Fenhexamid; Pesticide Tolerance

AGENCY: Environmental Protection Agency (EPA).

ACTION: Final rule.

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

SUMMARY: This regulation establishes tolerances for residues of
fenhexamid in or on nonbell pepper, pomegranate, and cilantro leaves.
Interregional Research Project No.4 (IR-4) requested these tolerances
under the Federal Food, Drug, and Cosmetic Act (FFDCA), as amended by
the Food Quality Protection Act of 1996 (FQPA).

DATES: This regulation is effective August 2, 2006. Objections and
requests for hearings must be received on or before October 2, 2006,
and must be filed in accordance with the instructions provided in 40
CFR part 178 (see also Unit I.C. of the SUPPLEMENTARY INFORMATION.

ADDRESSES:  EPA has established a docket for this action under docket
identification (ID) number EPA-HQ-OPP-2005-0245. All documents in the
docket are listed in the index for the docket. Although listed in the
index, some information is not publicly available, e.g., Confidential
Business Information (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 in the electronic docket at http://www.regulations.gov, or,

if only available in hard copy, at the OPP Regulatory Public Docket in
Rm. S-4400, One Potomac Yard (South Building), 2777 S. Crystal Drive,
Arlington, VA. The Docket Facility is open from 8:30 a.m. to 4 p.m.,
Monday through Friday, excluding legal holidays. The Docket telephone
number is<PHONE_NUMBER>.

FOR FURTHER INFORMATION CONTACT: Barbara Madden, Registration Division
(7505P), Office of Pesticide Programs, Environmental Protection Agency,
1200 Pennsylvania Ave., NW., Washington, DC 20460-0001; telephone
number:<PHONE_NUMBER>; e-mail address<EMAIL_ADDRESS>
SUPPLEMENTARY INFORMATION:

I. General Information

A. Does this Action Apply to Me?

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

B. How Can I Access Electronic Copies of this Document?

    In addition to accessing an electronic copy of this Federal
Register document through the electronic docket at http://www.regulations.gov
, you may access this Federal Register document

electronically through the EPA Internet under the ``Federal Register''
listings at http://www.epa.gov/fedrgstr. You may also access a

frequently updated electronic version of 40 CFR part 180 through the
Government Printing Office's pilot e-CFR site at http://www.gpoaccess.gov/ecfr.
 To access the OPPTS Harmonized Guidelines

referenced in this document, go directly to the guidelines at http://www.epa.gpo/opptsfrs/home/guidelin.htm
.

C. Can I File an Objection or Hearing Request?

    Under section 408(g) of the FFDCA, as amended by the FQPA, any
person may file an objection to any aspect of this regulation and may
also request a hearing on those objections. The EPA procedural
regulations which govern the submission of objections and requests for
hearings appear in 40 CFR part 178. You must file your objection or
request a hearing on this regulation in accordance with the
instructions

provided in 40 CFR part 178. To ensure proper receipt by EPA, you must
identify docket ID number EPA-HQ-OPP-2005-0245 in the subject line on
the first page of your submission. All requests must be in writing, and
must be mailed or delivered to the Hearing Clerk on or before October
2, 2006.
    In addition to filing an objection or hearing request with the
Hearing Clerk as described in 40 CFR part 178, please submit a copy of
the filing that does not contain any CBI for inclusion in the public
docket that is described in ADDRESSES. Information not marked
confidential pursuant to 40 CFR part 2 may be disclosed publicly by EPA
without prior notice. Submit your copies, identified by docket ID
number EPA-HQ-OPP-2005-0245, by one of the following methods:
     Federal eRulemaking Portal: http://www.regulations.gov.

Follow the on-line instructions for submitting comments.
     Mail: Office of Pesticide Programs (OPP) Regulatory Public
Docket (7502P), Environmental Protection Agency, 1200 Pennsylvania
Ave., NW., Washington, DC 20460-0001.
     Delivery: OPP Regulatory Public Docket (7502P),
Environmental Protection Agency, Rm. S-4400, One Potomac Yard (South
Building), 2777 S. Crystal Drive, Arlington, VA. Deliveries are only
accepted during the Docket's normal hours of operation (8:30 a.m. to 4
p.m., Monday through Friday, excluding legal holidays). Special
arrangements should be made for deliveries of boxed information. The
Docket telephone number is<PHONE_NUMBER>.

II. Background and Statutory Findings

    In the Federal Register of November 30, 2005 (70 FR 71838) (FRL-
7735-7), EPA issued a notice pursuant to section 408(d)(3) of FFDCA, 21
U.S.C. 346a(d)(3), announcing the filing of pesticide petitions (PP
4E6859 and 4E6860) by Interregional Research Project No. 4 (IR-4),
Technology Center of New Jersey, Rutgers, the State University of New
Jersey, 681 U.S. Highway 1 South, North Brunswick, NJ 08902-
3390. The petition requested that 40 CFR 180.553 be amended by
establishing tolerances for residues of the fungicide fenhexamid, (N-
2,3-dichloro-4-hydroxyphenyl)-1-methyl cyclohexanecarboxamide in or on
cilantro, leaves at 30.0 parts per million (ppm) (4E6859); pepper,
nonbell at 0.02 ppm (4E6860) and pomegranate at 3.0 ppm (4E6859). That
notice included a summary of the petition prepared by Arvesta
Corporation, the registrant. There were no comments received in
response to the notice of filing. Petition 4E6859 was subsequently
amended to lower the residue level for pomegranate to 2.0 ppm.
    Section 408(b)(2)(A)(i) of FFDCA allows EPA to establish a
tolerance (the legal limit for a pesticide chemical residue in or on a
food) only if EPA determines that the tolerance is ``safe.'' Section
408(b)(2)(A)(ii) of FFDCA defines ``safe'' to mean that ``there is a
reasonable certainty that no harm will result from aggregate exposure
to the pesticide chemical residue, including all anticipated dietary
exposures and all other exposures for which there is reliable
information.'' This includes exposure through drinking water and in
residential settings, but does not include occupational exposure.
Section 408(b)(2)(C) of FFDCA requires EPA to give special
consideration to exposure of infants and children to the pesticide
chemical residue in establishing a tolerance and to ``ensure that there
is a reasonable certainty that no harm will result to infants and
children from aggregate exposure to the pesticide chemical
residue....''
    EPA performs a number of analyses to determine the risks from
aggregate exposure to pesticide residues. For further discussion of the
regulatory requirements of section 408 of the FFDCA and a complete
description of the risk assessment process, see http://www.epa.gov/fedrgstr/EPA-PEST/1997/November/Day-26/p30948.htm
.

III. Aggregate Risk Assessment and Determination of Safety

    Consistent with section 408(b)(2)(D) of FFDCA, EPA has reviewed the
available scientific data and other relevant information in support of
this action. EPA has sufficient data to assess the hazards of and to
make a determination on aggregate exposure, consistent with section
408(b)(2) of FFDCA, for a tolerance for residues of fenhexamid on
cilantro, leaves at 30.0 ppm; pepper, nonbell at 0.02 ppm; and
pomegranate at 2.0 ppm. EPA's assessment of exposures and risks
associated with establishing the tolerance follows.

A. Toxicological Profile

    EPA has evaluated the available toxicity data and considered its
validity, completeness, and reliability as well as the relationship of
the results of the studies to human risk. EPA has also considered
available information concerning the variability of the sensitivities
of major identifiable subgroups of consumers, including infants and
children. Specific information on the studies received and the nature
of the toxic effects caused by fenhexamid as well as the no-observed-
adverse-effect-level (NOAEL) and the lowest-observed-adverse-effect-
level (LOAEL) from the toxicity studies in the Federal Register of
April 13, 2000 (65 FR 19842) (FRL-6553-7) *http://www.epa.gov/fedrgstr/EPA-PEST/2000/April/Day-13/p9144.htm
.

B. Toxicological Endpoints

    For hazards that have a threshold below which there is no
appreciable risk, the dose at which no adverse effects are observed
(the NOAEL) from the toxicology study identified as appropriate for use
in risk assessment is used to estimate the toxicological level of
concern (LOC). However, the lowest dose at which adverse effects of
concern are identified the (LOAEL) is sometimes used for risk
assessment if no NOAEL was achieved in the toxicology study selected.
An uncertainty factor (UF) is applied to reflect uncertainties inherent
in the extrapolation from laboratory animal data to humans and in the
variations in sensitivity among members of the human population as well
as other unknowns.
    The linear default risk methodology (Q*) is the primary method
currently used by the Agency to quantify non-threshold hazards such as
cancer. The Q* approach assumes that any amount of exposure will lead
to some degree of cancer risk, estimates risk in terms of the
probability of occurrence of additional cancer cases. More information
can be found on the general principles EPA uses in risk
characterization at http://www.epa.gov/pesticides/health/human.htm.

    A summary of the toxicological endpoints for fenhexamid used for
human risk assessment is discussed in Unit III.B. of the final rule
published in the Federal Register of September 26, 2003 (68 FR 55513)
(FRL-7326-7).

C. Exposure Assessment

    1. Dietary exposure from food and feed uses. Tolerances have been
established (40 CFR 180.553) for the residues of fenhexamid, in or on a
variety of raw agricultural commodities. Risk assessments were
conducted by EPA to assess dietary exposures from fenhexamid in food as
follows:
    i. Acute exposure. Quantitative acute dietary exposure and risk
assessments are performed for a food-use pesticide, if a toxicological
study has indicated the possibility of an effect of concern occurring
as a result of a one-day or single exposure. No such effects were
identified in the toxicological studies for fenhexamid; therefore, a
quantitative acute dietary exposure assessment is unnecessary.

    ii. Chronic exposure. In conducting the chronic dietary exposure
assessment EPA used the Dietary Exposure Evaluation Model software with
the Food Commodity Intake Database (DEEM-FCID\TM\), which incorporates
food consumption data as reported by respondents in the USDA 1994-1996
and 1998 Nationwide Continuing Surveys of Food Intake by Individuals
(CSFII), and accumulated exposure to the chemical for each commodity.
The following assumptions were made for the chronic exposure
assessments: one hundred percent of proposed and registered crops are
treated with fenhexamid, default processing factors, average (chronic)
concentration estimates for drinking water and tolerance-level residues
for all commodities.
    iii. Cancer. Fenhexamid is classified as ``not likely'' to be a
human carcinogen. Therefore, a cancer dietary exposure assessment was
not performed.
    2. Dietary exposure from drinking water. The Agency lacks
sufficient monitoring exposure data to complete a comprehensive dietary
exposure analysis and risk assessment for fenhexamid in drinking water.
Because the Agency does not have comprehensive monitoring data,
drinking water concentration estimates are made by reliance on
simulation or modeling taking into account data on the physical
characteristics of fenhexamid. Further information regarding EPA
drinking water models used in pesticide exposure assessment can be
found at http://www.epa.gov/oppefed1/models/water/index.htm .

    Based on the FIRST and SCI-GROW models, the estimated environmental
concentrations (EECs) of fenhexamid for acute exposures are estimated
to be 29 parts per billion (ppb) for surface water and 0.0007 ppb for
groundwater. The EECs for chronic exposures are estimated to be 1.1 ppb
for surface water and 0.0007 ppb for groundwater. Modeled estimates of
drinking water concentrations were directly entered into the dietary
exposure model (DEEM-FCID\TM\). For chronic dietary risk assessment,
the annual average concentration of 1.1 ppb was used to access the
contribution to drinking water
    3. From non-dietary exposure. The term ``residential exposure'' is
used in this document to refer to non-occupational, non-dietary
exposure (e.g., for lawn and garden pest control, indoor pest control,
termiticides, and flea and tick control on pets). Fenhexamid is not
registered for use on any sites that would result in residential
exposure.
    4. Cumulative effects from substances with a common mechanism of
toxicity. Section 408(b)(2)(D)(v) of the FFDCA requires that, when
considering whether to establish, modify, or revoke a tolerance, the
Agency consider ``available information'' concerning the cumulative
effects of a particular pesticide's residues and ``other substances
that have a common mechanism of toxicity.'' Unlike other pesticides for
which EPA has followed a cumulative risk approach based on a common
mechanism of toxicity, EPA has not made a common mechanism of toxicity
finding as to fenhexamid and any other substances and fenhexamid does
not appear to produce a toxic metabolite produced by other substances.
For the purposes of this tolerance action, therefore, EPA has not
assumed that fenhexamid has a common mechanism of toxicity with other
substances. For information regarding EPA's efforts to determine which
chemicals have a common mechanism of toxicity and to evaluate the
cumulative effects of such chemicals, see the policy statements
released by EPA's Office of Pesticide Programs concerning common
mechanism determinations and procedures for cumulating effects from
substances found to have a common mechanism on EPA's website at http://www.epa.gov/pesticides/cumulative
.

D. Safety Factor for Infants and Children

    1. In general. Section 408 of FFDCA provides that EPA shall apply
an additional tenfold margin of safety for infants and children in the
case of threshold effects to account for prenatal and postnatal
toxicity and the completeness of the data base on toxicity and exposure
unless EPA determines based on reliable data that a different margin of
safety will be safe for infants and children. Margins of safety are
incorporated into EPA risk assessments either directly through use of a
MOE analysis or through using uncertainty (safety) factors in
calculating a dose level that poses no appreciable risk to humans. In
applying this provision, EPA either retains the default value of 10X
when reliable data do not support the choice of a different factor, or,
if reliable data are available, EPA uses a different additional safety
factor value based on the use of traditional uncertainty factors and/or
special FQPA safety factors, as appropriate.
    2. Prenatal and postnatal sensitivity. In the rat and the rabbit
developmental toxicity studies, neither quantitative nor qualitative
evidence of increased susceptibility of fetuses to in utero exposure to
fenhexamid was observed. In the rat reproduction study, qualitative
susceptibility was evidenced as significantly decreased pup body
weights in both generations during the lactation period (on lactation
days 7, 14, and 21 in the F2 generation and lactation days
14 and 21 in the F1 generation offspring) in the presence of
lesser maternal toxicity (alterations in clinical chemistry parameters
and decreased organ weights without collaborative histopathology).
Considering the overall toxicity profile and the doses and endpoints
selected for risk assessment for fenhexamid, the degree of concern for
the effects observed in this study was characterized as low, noting
that there is a clear NOAEL and well-characterized dose response for
the offspring effects observed and that these effects occurred in the
presence of parental toxicity. No residual uncertainties were
identified. The NOAEL of 17 mg/kg/day from the chronic dog study used
to establish the chronic Reference Dose (cRfD) for the General
Population (no aRfD was established for any population subgroup) is
lower than the NOAEL of 38.2 mg/kg/day in the reproduction study in
which the offspring effects of concern were observed (LOAEL = 406 mg/
kg/day).
    3. Conclusion. There is a complete toxicity data base for
fenhexamid and exposure data are complete or are estimated based on
data that reasonably accounts for potential exposures. EPA determined
that the 10X Safety Factor to protect infants and children should be
reduced to 1X for the following reasons:
     There are no residual uncertainties for pre and/or post
natal toxicities via the oral route since the doses selected for
concerns for the developmental and offspring toxicities seen in the
above mentioned studies.
     There are no residual uncertainties for pre and/or post
natal toxicities via the dermal route since the dose/endpoint/study/
species of concern was used for dermal-risk assessment.
     The toxicology data base is complete.
     Developmental neurotoxicity studies are not required for
fenhexamid based on the following weight-of-the-evidence
considerations:
    i. Lack of evidence of abnormalities in the development of the
fetal nervous system in the pre/post natal studies.
    ii. Neither brain weight nor histopathological examination of the
nervous system was affected in the subchronic and chronic studies.

    iii. Decreased body temperatures observed in male rats in the acute
neurotoxicity study were not considered to be toxicologically
significant.
     The dietary (food) exposure assessment utilizes existing
and proposed tolerance level residues and assumes 100% of crops treated
with fenhexamid. The assessment is based on reliable data and is not
expected to underestimate exposure/risk.
     Conservative assumptions are used in the drinking water
models. The drinking water exposure assessment is not expected to
underestimate exposure/risk.
      Fenhexamid is not registered for use sites that would
result in residential exposure.

E. Aggregate Risks and Determination of Safety

    The Agency currently has two ways to estimate total aggregate
exposure to a pesticide from food, drinking water, and residential
uses. First, a screening assessment can be used, in which the Agency
calculates drinking water levels of comparison (DWLOCs) which are used
as a point of comparison against estimated drinking water
concentrations (EDWCs). The DWLOC values are not regulatory standards
for drinking water, but are theoretical upper limits on a pesticide's
concentration in drinking water in light of total aggregate exposure to
a pesticide in food and residential uses. More information on the use
of DWLOCs in dietary aggregate risk assessments can be found at http://www.epa.gov/oppfead1/trac/science/screeningsop.pdf
.

    More recently the Agency has used another approach to estimate
aggregate exposure through food, residential and drinking water
pathways. In this approach, modeled surface and groundwater EDWCs are
directly incorporated into the dietary exposure analysis, along with
food. This provides a more realistic estimate of exposure because
actual body weights and water consumption from the CSFII are used. The
combined food and water exposures are then added to estimated exposure
from residential sources to calculate aggregate risks. The resulting
exposure and risk estimates are still considered to be high end, due to
the assumptions used in developing drinking water modeling inputs.
    1. Acute risk. An acute risk assessment was not performed. No
toxicological endpoint attributable to a single (acute) dietary
exposure was identified. Therefore, acute risk from exposure to
fenhexamid is not expected.
    2. Chronic risk. Using the exposure assumptions described in this
unit for chronic exposure, EPA has concluded that exposure to
fenhexamid from food and water will utilize 11% of the cPAD for the
U.S. population, 21% of the cPAD for all infants less than 1 year old,
and 28% of the cPAD for children 1-2 years old, the subpopulation at
greatest exposure. There are no residential uses for fenhexamid.
Therefore, EPA does not expect the aggregate exposure to exceed 100% of
the cPAD
    3. Short-term risk and Intermediate-term. Short-term and
intermediate-term aggregate exposures take into account residential
exposure plus chronic exposure to food and water (considered to be a
background exposure level). Fenhezamid is not registered for use on any
sites that would result in residential exposure. Therefore, the
aggregate risk is the sum of the risk from food and water, which do not
exceed the Agency's level of concern.
    4. Aggregate cancer risk for U.S. population. The Agency has
classified fenhexamid as a ``not likely'' human carcinogen based on
lack of evidence of carcinogenicity in male and female rats as well as
in male and female mice, and on the lack of genotoxicity in an
acceptable battery of mutagenicity studies. Therefore, fenhexamid is
not expected to pose a cancer risk.
    5. Determination of safety. Based on these risk assessments, EPA
concludes that there is a reasonable certainty that no harm will result
to the general population, and to infants and children from aggregate
exposure to fenhexamid.

IV. Other Considerations

A. Analytical Enforcement Methodology

    Adequate enforcement methodology Bayer AG Method 00362 (HPLC - ECD)
is available to enforce the tolerance expression. The method may be
requested from: Chief, Analytical Chemistry Branch, Environmental
Science Center, 701 Mapes Rd., Ft. Meade, MD 20755-5350; telephone
number:<PHONE_NUMBER>; e-mail address<EMAIL_ADDRESS>
B. International Residue Limits

    Fenhexamid per se is the residue to be regulated in pomegranate,
cilantro or non-bell pepper. There are no Canadian, Mexican, or Codex
MRLs for fenhexamid ``for these crops'' , therefore, there are no
issues for international harmonization.

V. Conclusion

    Therefore, the tolerance is established for residues of fenhexamid,
(N-2,3-dichloro-4-hydroxyphenyl)-1-methyl cyclohexanecarboxamide, in or
on cilantro, leaves at 30.0 ppm; pepper, nonbell at 0.02 ppm; and
pomegranate at 2.0.

VI. Statutory and Executive Order Reviews

    This final rule establishes a tolerance under section 408(d) of
FFDCA in response to a petition submitted to the Agency. The Office of
Management and Budget (OMB) has exempted these types of actions from
review under Executive Order 12866, entitled Regulatory Planning and
Review (58 FR 51735, October 4, 1993). Because this rule has been
exempted from review under Executive Order 12866 due to its lack of
significance, this rule is not subject to Executive Order 13211,
Actions Concerning Regulations That Significantly Affect Energy Supply,
Distribution, or Use (66 FR 28355, May 22, 2001). This final rule does
not contain any information collections subject to OMB approval under
the Paperwork Reduction Act (PRA), 44 U.S.C. 3501 et seq., or impose
any enforceable duty or contain any unfunded mandate as described under
Title II of the Unfunded Mandates Reform Act of 1995 (UMRA) (Public Law
104-4). Nor does it require any special considerations under Executive
Order 12898, entitled Federal Actions to Address Environmental Justice
in Minority Populations and Low-Income Populations (59 FR 7629,
February 16, 1994); or OMB review or any Agency action under Executive
Order 13045, entitled Protection of Children from Environmental Health
Risks and Safety Risks (62 FR 19885, April 23, 1997). This action does
not involve any technical standards that would require Agency
consideration of voluntary consensus standards pursuant to section
12(d) of the National Technology Transfer and Advancement Act of 1995
(NTTAA), Public Law 104-113, section 12(d) (15 U.S.C. 272 note). Since
tolerances and exemptions that are established on the basis of a
petition under section 408(d) of FFDCA, such as the tolerance in this
final rule, do not require the issuance of a proposed rule, the
requirements of the Regulatory Flexibility Act (RFA) (5 U.S.C. 601 et
seq.) do not apply. In addition, the Agency has determined that this
action will not have a substantial direct effect on States, on the
relationship between the national government and the States, or on the
distribution of power and responsibilities among the various levels of
government, as specified in Executive Order 13132, entitled Federalism
(64 FR 43255, August 10, 1999). Executive Order 13132 requires EPA to
develop an accountable process to ensure ``meaningful and timely input

by State and local officials in the development of regulatory policies
that have federalism implications.'' ``Policies that have federalism
implications'' is defined in the Executive order to include regulations
that have ``substantial direct effects on the States, on the
relationship between the national government and the States, or on the
distribution of power and responsibilities among the various levels of
government.'' This final rule directly regulates growers, food
processors, food handlers and food retailers, not States. This action
does not alter the relationships or distribution of power and
responsibilities established by Congress in the preemption provisions
of section 408(n)(4) of FFDCA. For these same reasons, the Agency has
determined that this rule does not have any ``tribal implications'' as
described in Executive Order 13175, entitled Consultation and
Coordination with Indian Tribal Governments (65 FR 67249, November 6,
2000). Executive Order 13175, requires EPA to develop an accountable
process to ensure ``meaningful and timely input by tribal officials in
the development of regulatory policies that have tribal implications.''
``Policies that have tribal implications'' is defined in the Executive
order to include regulations that have ``substantial direct effects on
one or more Indian tribes, on the relationship between the Federal
Government and the Indian tribes, or on the distribution of power and
responsibilities between the Federal Government and Indian tribes.''
This rule will not have substantial direct effects on tribal
governments, on the relationship between the Federal Government and
Indian tribes, or on the distribution of power and responsibilities
between the Federal Government and Indian tribes, as specified in
Executive Order 13175. Thus, Executive Order 13175 does not apply to
this rule.

VII. Congressional Review Act

    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 rule 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 this final rule in the Federal Register. This final
rule is not a ``major rule'' as defined by 5 U.S.C. 804(2).

List of Subjects in 40 CFR Part 180

    Environmental protection, Administrative practice and procedure,
Agricultural commodities, Pesticides and pests, Reporting and
recordkeeping requirements.

    Dated: July 21, 2006.
Daniel J. Rosenblatt,
Acting Director, Registration Division, Office of Pesticide Programs.

0
Therefore, 40 CFR chapter I is amended as follows:

PART 180--AMENDED

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

    Authority: 21 U.S.C. 321(q), 346a and 371.

0
2. Section 180.553 is amended by alphabetically adding commodities to
the table in paragraph (a) to read as follows:

Sec.  180.553  Fenhexamid; tolerances for residues.

    (a) * * *

------------------------------------------------------------------------
                                                             Parts per
                        Commodity                             million
------------------------------------------------------------------------
                                * * * * *
Cilantro, leaves                                                    30.0
                                * * * * *
Pepper, nonbell                                                     0.02
                                * * * * *
Pomegranate                                                          2.0
                                * * * * *
------------------------------------------------------------------------

[FR Doc. E6-12348 Filed 8-1-06; 8:45 am]

BILLING CODE 6560-50-S


[Federal Register Volume 87, Number 3 (Wednesday, January 5, 2022)]
[Notices]
[Pages 507-508]
[FR Doc No: 2021-28570]

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

SECURITIES AND EXCHANGE COMMISSION

[Release No. 34-93886; File No. SR-NASDAQ-2021-105]

Self-Regulatory Organizations; The Nasdaq Stock Market LLC;
Notice of Filing and Immediate Effectiveness of Proposed Rule Change To
Delay Implementation of SR-NASDAQ-2021-009

December 30, 2021.
    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 December 23, 2021, The Nasdaq Stock Market LLC (``Nasdaq'' or
``Exchange'') filed with the Securities and Exchange Commission
(``Commission'') the proposed rule change as described in Items I and
II below, which Items have been prepared 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 delay implementation of SR-NASDAQ-2021-
009.
    The text of the proposed rule change is available on the Exchange's
website at https://listingcenter.nasdaq.com/rulebook/nasdaq/rules, 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
    On February 11, 2021, the Exchange filed a proposed rule change to
make certain changes to the Exchange's Limit Up-Limit Down (``LULD'')
closing cross, including the timing of the LULD closing cross, the
process for determining the LULD closing cross price, establishing
price protections for the LULD closing cross, the handling of on-close
orders, and the imbalance information disseminated for the LULD closing
cross.\3\ The Exchange originally intended to implement the new
functionalities in Q3 2021,\4\ and subsequently extended the
implementation to Q4 2021 to allow the Exchange additional time to test
and implement these functionalities.\5\ During the testing conducted to
date, the Exchange has identified some changes that it wishes to make
to the approved rule, which relate to the handling of certain Limit on
Close orders during the LULD closing cross (``Proposed
Amendments'').\6\ Accordingly, the Exchange proposes to delay
implementation of SR-NASDAQ-2021-009 until April 2022 so as to allow
additional time for the Commission to consider the Proposed Amendments.
If the Proposed Amendments are approved by the Commission, the Exchange
will issue an Equity Trader Alert notifying market participants prior
to implementing these functionalities.
---------------------------------------------------------------------------

    \3\ See Securities Exchange Act Release No. 92068 (May 28,
2021), 86 FR 29864 (June 3, 2021) (SR-NASDAQ-2021-009).
    \4\ Id.
    \5\ See Securities Exchange Act Release No. 93250 (October 4,
2021), 86 FR 56307 (October 8, 2021) (SR-NASDAQ-2021-077).
    \6\ The Exchange will submit a separate rule filing to address
these changes. See SR-NASDAQ-2021-101 (not yet published).
---------------------------------------------------------------------------

2. Statutory Basis
    The Exchange believes that its proposal is consistent with Section
6(b) of the Act,\7\ in general, and furthers the objectives of Section
6(b)(5) of the Act,\8\ in particular, in that it is designed to promote
just and equitable principles of trade, to remove impediments to and
perfect the mechanism of a free and open market and a national market
system, and, in general to protect investors and the public interest,
by allowing the Exchange additional time to test and implement the LULD
closing cross changes, pending any Commission action on the Proposed
Amendments.
---------------------------------------------------------------------------

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

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 Exchange's proposal to
delay the implementation of SR-NASDAQ-2021-009 does not impose an undue
burden on competition. Delaying the implementation will simply allow
the Exchange additional time to properly implement SR-NASDAQ-2021-009,
pending any Commission action on the Proposed Amendments.

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

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

    \9\ 15 U.S.C. 78s(b)(3)(A).
    \10\ 17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6)(iii)
requires a self-regulatory organization to give the Commission
written notice of its intent to file the proposed rule change, along
with a brief description and text of the proposed rule change, at
least five business days prior to the date of filing of the proposed
rule change, or such shorter time as designated by the Commission.
The Exchange has satisfied this requirement.

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

    A proposed rule change filed under Rule 19b-4(f)(6) \11\ normally
does not become operative prior to 30 days after the date of the
filing. However, pursuant to Rule 19b-4(f)(6)(iii),\12\ the Commission
may designate a shorter time if such action is consistent with the
protection of investors and the public interest. The Exchange has asked
the Commission to waive the 30-day operative delay. Waiver of the
operative delay would allow the Exchange to immediately delay the
implementation of SR-NASDAQ-2021-009 and provide the Exchange
additional time to test and implement new LULD closing cross
functionalities. The Commission believes that waiving the 30-day
operative delay is consistent with the protection of investors and the
public interest. Accordingly, the Commission hereby waives the
operative delay and designates the proposed rule change operative upon
filing.\13\
---------------------------------------------------------------------------

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

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

IV. Solicitation of Comments

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

Electronic Comments

     Use the Commission's internet comment form (https://www.sec.gov/rules/sro.shtml); or
     Send an email to [email protected]. Please include
File Number SR-NASDAQ-2021-105 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-NASDAQ-2021-105. 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 (https://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-NASDAQ-2021-105 and should
be submitted on or before January 26, 2022.

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

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

Eduardo A. Aleman,
Deputy Secretary.
[FR Doc. 2021-28570 Filed 1-4-22; 8:45 am]
BILLING CODE 8011-01-P


[Federal Register: November 1, 2010 (Volume 75, Number 210)]
[Notices]
[Page 67153-67155]
[DOCID:fr01no10-70]

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

SECURITIES AND EXCHANGE COMMISSION

[Release No. 34-63177; File No. SR-ISE-2010-105]

Self-Regulatory Organizations; International Securities Exchange,
LLC; Notice of Filing and Immediate Effectiveness of Proposed Rule
Change Relating to a Date for the Additional Expiration Months Pilot
Program

October 25, 2010.
    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 October 20, 2010, the International Securities Exchange, Inc. (the
``Exchange'' or ``ISE'') filed with the Securities and Exchange
Commission (the ``Commission'') the proposed rule change as described
in Items I and II below, which Items have been prepared by the
Exchange. The

Exchange has designated the proposed rule change as one constituting a
stated policy, practice, or interpretation with respect to the meaning,
administration, or enforcement of an existing rule under Section
19(b)(3)(A)(i) of the Act \3\ and Rule 19b-4(f)(1) thereunder,\4\ which
renders the proposal effective upon filing with the Commission. 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.
    \3\ 15 U.S.C. 78s(b)(3)(A)(i).
    \4\ 17 CFR 240.19b-4(f)(1).
---------------------------------------------------------------------------

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

    The ISE is proposing to make technical amendments to its rules to
insert the specific date for a pilot program. The text of the proposed
rule change is available on the Exchange's Web site (http://
www.ise.com), at the principal office of the Exchange, and at the
Commission's Public Reference Room.

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

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

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

1. Purpose
    The Exchange proposes to make technical amendments to its rules to
insert a specific date for a pilot program.
    The Commission recently approved the Exchange's proposal to
establish a pilot program that would permit the Exchange to list up to
an additional two expiration months, for a total of six expiration
months for each class of options open for trading on the Exchange.\5\
This rule change proposes to amend the text of Supplementary Material
.08 to Rule 504 to insert the specific conclusion date of the pilot
program, which is October 31, 2011.\6\
---------------------------------------------------------------------------

    \5\ See Securities Exchange Act Release No. 63104 (October 14,
2010), 75 FR 64773 (October 20, 2010) (Approving SR-ISE-2010-91).
    \6\ Previously the rule text indicated that the Exchange would
insert the date 12 months from the next full month from approval,
which approval occurred on October 14, 2010. Id.
---------------------------------------------------------------------------

2. Statutory Basis
    The proposed rule change is consistent with Section 6(b) \7\ of the
Securities Exchange Act of 1934 (the ``Act''), in general, and furthers
the objectives of Section 6(b)(5) \8\ in particular, in that it is
designed to prevent fraudulent and manipulative acts and practices, to
promote just and equitable principles of trade, to foster cooperation
and coordination with persons engaged in facilitating transactions in
securities, and to remove impediments to and perfect the mechanisms of
a free and open market and a national market system in a manner
consistent with the protection of investors and the public interest. In
particular, the proposed rule change seeks to update rule text to
insert specific dates for a pilot program in a manner that is
consistent with the original approval order of the pilot program.
---------------------------------------------------------------------------

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

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

    The proposed rule change does not impose any burden on competition.

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

    The Exchange has not solicited, and does not intend to solicit,
comments on this proposed rule change. The Exchange has not received
any unsolicited written comments from members or other interested
parties.

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

    The foregoing proposed rule change will take effect upon filing
with the Commission pursuant to Section 19(b)(3)(A)(i) of the Act \9\
and Rule 19b-4(f)(1) thereunder,\10\ because it constitutes a stated
policy, practice, or interpretation with respect to the meaning,
administration, or enforcement of an existing rule.
---------------------------------------------------------------------------

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

    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.

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 e-mail to<EMAIL_ADDRESS>Please include
File Number SR-ISE-2010-105 on the subject line.

Paper Comments

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

All submissions should refer to File Number SR-ISE-2010-105. 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 Web site viewing and
printing in the Commission's Public Reference Room, 100 F Street, NE.,
Washington, DC 20549, on official business days between the hours of 10
a.m. and 3 p.m. Copies of the filing also will be available for
inspection and copying at the principal office of the Exchange. All
comments received will be posted without change; the Commission does
not edit personal identifying information from submissions. You should
submit only information that you wish to make available publicly. All
submissions should refer to File Number SR-ISE-2010-105 and should be
submitted on or before November 22, 2010.

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

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

Florence E. Harmon,
Deputy Secretary.
[FR Doc. 2010-27465 Filed 10-29-10; 8:45 am]
BILLING CODE 8011-01-P


[Federal Register: November 23, 2009 (Volume 74, Number 224)]
[Rules and Regulations]
[Page 61024-61027]
[DOCID:fr23no09-5]

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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 97

[Docket No. 30697 Amdt. No 3348]

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

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Final rule.

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

SUMMARY: This 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 November 23, 2009. 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 November 23, 2009.

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: Harry J. Hodges, 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 November 13, 2009.
John M. Allen,
Director, Flight Standards Service.

Adoption of the Amendment

0
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 December 17, 2009

St George, AK, St George, Takeoff Minimums and Obstacle DP, Amdt 1
Wrangell, AK, Wrangell, VOR/DME-B, Amdt 1, CANCELLED
Pell City, AL, St. Clair County, RNAV (GPS) RWY 3, Amdt 2

Pell City, AL, St. Clair County, RNAV (GPS) RWY 21, Amdt 2
Pell City, AL, St. Clair County, Takeoff Minimums and Obstacle DP,
Amdt 2
Pell City, AL, St. Clair County, VOR-A, Amdt 9
Nogales, AZ, Nogales Intl, Takeoff Minimums and Obstacle DP, Amdt 2
Chico, CA, Chico Muni, ILS OR LOC/DME RWY 13L, Amdt 12
Wilmington, DE, New Castle, ILS OR LOC RWY 1, Amdt 22
Avon Park, FL, Avon Park Executive, Takeoff Minimums and Obstacle
DP, Amdt 1
Marco Island, FL, Marco Island, GPS RWY 17, Orig-A, CANCELLED
Marco Island, FL, Marco Island, GPS RWY 35, Orig-A, CANCELLED
Marco Island, FL, Marco Island, RNAV (GPS) RWY 17, Orig
Marco Island, FL, Marco Island, RNAV (GPS) RWY 35, Orig
Marco Island, FL, Marco Island, Takeoff Minimums and Obstacle DP,
Amdt 2
Miami, FL, Kendall-Tamiami Executive, RNAV (GPS) RWY 9L, Orig-A
Naples, FL, Naples Muni, Takeoff Minimums and Obstacle DP, Amdt 2
Sebring, FL, Sebring Rgnl, RNAV (RNP) RWY 18, Orig
West Palm Beach, FL, Palm Beach Intl, ILS OR LOC RWY 10L, Amdt 25
West Palm Beach, FL, Palm Beach Intl, ILS OR LOC RWY 28R, Amdt 3
West Palm Beach, FL, Palm Beach Intl, RNAV (GPS) Y RWY 10L, Amdt 2
West Palm Beach, FL, Palm Beach Intl, RNAV (GPS) Y RWY 14, Amdt 2
West Palm Beach, FL, Palm Beach Intl, RNAV (GPS) Y RWY 28R, Amdt 2
West Palm Beach, FL, Palm Beach Intl, RNAV (GPS) Y RWY 32, Amdt 2
Thomaston, GA, Thomaston-Upson County, RNAV (GPS) RWY 30, Orig
Chariton, IA, Chariton Muni, GPS RWY 10, Orig-A, CANCELLED
Chariton, IA, Chariton Muni, RNAV (GPS) RWY 10, Orig
Chariton, IA, Chariton Muni, RNAV (GPS) RWY 17, Orig
Chariton, IA, Chariton Muni, Takeoff Minimums and Obstacle DP, Orig
Idaho Falls, ID, Idaho Falls Rgnl, Takeoff Minimums and Obstacle DP,
Amdt 4
Rochelle, IL, Rochelle Muni-Koritz Field, RNAV (GPS) RWY 25, Orig-A
Rochelle, IL, Rochelle Muni-Koritz Field, VOR-A, Amdt 8A
Huntingburg, IN, Huntingburg, GPS RWY 9, Orig, CANCELLED
Huntingburg, IN, Huntingburg, GPS RWY 27, Orig, CANCELLED
Huntingburg, IN, Huntingburg, RNAV (GPS) RWY 9, Orig
Huntingburg, IN, Huntingburg, RNAV (GPS) RWY 27, Orig
Lewisport, KY, Hancock Co-Ron Lewis Field, RNAV (GPS) RWY 5, Orig
Lewisport, KY, Hancock Co-Ron Lewis Field, RNAV (GPS) RWY 23, Orig
Lewisport, KY, Hancock Co-Ron Lewis Field, Takeoff Minimums and
Obstacle DP, Orig
Bogalusa, LA, George R Carr Memorial Air Field, LOC RWY 18, Amdt 2
Bogalusa, LA, George R Carr Memorial Air Field, Takeoff Minimum and
Obstacle DP, Amdt 2
Winnfield, LA, David G. Joyce, NDB OR GPS RWY 8, Amdt 2B, CANCELLED
Mankato, MN, Mankato Rgnl, GPS RWY 22, Orig, CANCELLED
Mankato, MN, Mankato Rgnl, RNAV (GPS) RWY 4, Orig
Mankato, MN, Mankato Rgnl, RNAV (GPS) RWY 22, Orig
St Louis, MO, Lambert-St Louis Intl, ILS OR LOC RWY 12R, Amdt 21E
Okolona, MS, Okolona Muni-Richard Stovall Field, RNAV (GPS) RWY 18,
Orig
Okolona, MS, Okolona Muni-Richard Stovall Field, RNAV (GPS) RWY 36,
Orig
Okolona, MS, Okolona Muni-Richard Stovall Field, VOR/DME OR GPS RWY
18, Amdt 5, CANCELLED
Butte, MT, Bert Mooney, ILS Y RWY 15, Amdt 7
Charlotte, NC, Charlotte/Douglas Intl, Takeoff Minimums and Obstacle
DP, Amdt 5
Neligh, NE, Antelope County, RNAV (GPS) RWY 1, Orig
Neligh, NE, Antelope County, RNAV (GPS) RWY 19, Orig
Neligh, NE, Antelope County, Takeoff Minimums and Obstacle DP, Orig
Sidney, NE, Sidney Muni/Lloyd W Carr Field, VOR RWY 31, Amdt 8
Rochester, NH, Skyhaven, GPS RWY 33, Orig-B, CANCELLED
Rochester, NH, Skyhaven, NDB-B, Amdt 2
Rochester, NH, Skyhaven, RNAV (GPS) RWY 33, Orig
Rochester, NH, Skyhaven, Takeoff Minimums and Obstacle DP, Amdt 6
Rochester, NH, Skyhaven, VOR/DME-A, Amdt 2
Teterboro, NJ, Teterboro, RNAV (RNP) RWY 19, Orig-A
Teterboro, NJ, Teterboro, RNAV (RNP) Z RWY 6, Orig-A
Jamestown, NY, Chautauqua County/Jamestown, ILS OR LOC RWY 25, Amdt
7
Jamestown, NY, Chautauqua County/Jamestown, RNAV (GPS) RWY 7, Amdt 1
Jamestown, NY, Chautauqua County/Jamestown, RNAV (GPS) RWY 25, Amdt
1
Jamestown, NY, Chautauqua County/Jamestown, RNAV (GPS) Y RWY 25,
Orig, CANCELLED
Massena, NY, Massena Intl-Richards Field, Takeoff Minimums and
Obstacle DP, Amdt 8
New York, NY, John F. Kennedy Intl, RNAV (RNP) Z RWY 31R, Orig-A
Springfield, OH, Springfield-Beckley Muni, ILS OR LOC RWY 24, Amdt 2
Springfield, OH, Springfield-Beckley Muni, NDB RWY 24, Amdt 17
Springfield, OH, Springfield-Beckley Muni, RNAV (GPS) RWY 6, Orig
Springfield, OH, Springfield-Beckley Muni, RNAV (GPS) RWY 24, Orig
Springfield, OH, Springfield-Beckley Muni, VOR RWY 6, Amdt 11
Kutztown, PA, Kutztown, RNAV (GPS)-A, Orig, CANCELLED
Kutztown, PA, Kutztown, Takeoff Minimums and Obstacle DP, Orig,
CANCELLED
Kutztown, PA, Kutztown, VOR-B, Amdt 1B, CANCELLED
Saluda, SC, Saluda County, Takeoff Minimums and Obstacle DP, Orig
Columbia/Mt Pleasant, TN, Maury County, GPS RWY 24, Orig, CANCELLED
Columbia/Mt Pleasant, TN, Maury County, RNAV (GPS) RWY 6, Orig
Columbia/Mt Pleasant, TN, Maury County, RNAV (GPS) RWY 24, Orig
Columbia/Mt Pleasant, TN, Maury County, VOR/DME-A, Amdt 4
Beaumont/Port Arthur, TX, Southeast Texas Rgnl, ILS OR LOC RWY 12,
Amdt 23
Beaumont/Port Arthur, TX, Southeast Texas Rgnl, LOC BC RWY 30, Amdt
20
Beaumont/Port Arthur, TX, Southwest Texas Rgnl, Takeoff Minimums and
Obstacle DP, Orig
Bridgeport, TX, Bridgeport Muni, Takeoff Minimums and Obstacle DP,
Amdt 2
Burnet, TX, Burnet Muni/Kate Craddock Field, GPS RWY 1, Amdt 1,
CANCELLED
Burnet, TX, Burnet Muni/Kate Craddock Field, GPS RWY 19, Orig,
CANCELLED
Burnet, TX, Burnet Muni/Kate Craddock Field, NDB RWY 1, Amdt 6
Burnet, TX, Burnet Muni/Kate Craddock Field, RNAV (GPS) RWY 1, Orig
Burnet, TX, Burnet Muni/Kate Craddock Field, RNAV (GPS) RWY 19, Orig
Burnet, TX, Burnet Muni/Kate Craddock Field, Takeoff Minimums and
Obstacle DP, Amdt 1
Dallas, TX, Collins County Rgnl at McKinney, ILS OR LOC RWY 17, Amdt
3
Dallas, TX, Collins County Rgnl at McKinney, RNAV (GPS) RWY 17, Amdt
1
Dallas, TX, Collins County Rgnl at McKinney, RNAV (GPS) RWY 35, Amdt
1
Dallas, TX, Collins County Rgnl at McKinney, Takeoff Minimums and
Obstacle DP, Amdt 1
Killeen, TX, Skylark Field, NDB OR GPS RWY 1, Amdt 5C, CANCELLED
Tooele, UT, Bolinder Field-Tooele Valley, RNAV (GPS) RWY 17, Amdt 2A
Tooele, UT, Bolinder Field-Tooele Valley, RNAV (GPS) Y RWY 17, Orig,
CANCELLED
Eastsound, WA, Orcas Island, Takeoff Minimums and Obstacle DP, Amdt
1
Milwaukee, WI, General Mitchell Intl, ILS OR LOC RWY 1L, ILS RWY 1L
(CAT II), ILS RWY 1L (CAT III), Amdt 9
Milwaukee, WI, General Mitchell Intl, RNAV (GPS) RWY 1L, Amdt 1
Minocqua-Woodruff, WI, Lakeland/Noble F. Lee Memorial Field, LOC RWY
36, Amdt 1
Minocqua-Woodruff, WI, Lakeland/Noble F. Lee Memorial Field, NDB RWY
28, Amdt 12
Minocqua-Woodruff, WI, Lakeland/Noble F. Lee Memorial Field, NDB OR
GPS RWY 18, Amdt 12A, CANCELLED
Minocqua-Woodruff, WI, Lakeland/Noble F. Lee Memorial Field, NDB OR
GPS RWY 36, Amdt 9A, CANCELLED
Minocqua-Woodruff, WI, Lakeland/Noble F. Lee Memorial Field, RNAV
(GPS) RWY 18, Orig
Minocqua-Woodruff, WI, Lakeland/Noble F. Lee Memorial Field, RNAV
(GPS) RWY 28, Orig
Minocqua-Woodruff, WI, Lakeland/Noble F. Lee Memorial Field, RNAV
(GPS) RWY 36, Orig
Minocqua-Woodruff, WI, Lakeland/Noble F. Lee Memorial Field, Takeoff
Minimums and Obstacle DP, Orig

Sheboygan, WI, Sheboygan County Memorial, ILS OR LOC/DME RWY 21,
Amdt 3
Sheboygan, WI, Sheboygan County Memorial, RNAV (GPS) RWY 3, Amdt 2
Sheboygan, WI, Sheboygan County Memorial, RNAV (GPS) RWY 21, Amdt 2
Sheboygan, WI, Sheboygan County Memorial, VOR RWY 3, Amdt 8
Sheboygan, WI, Sheboygan County Memorial, VOR RWY 21, Amdt 8

[FR Doc. E9-27898 Filed 11-20-09; 8:45 am]

BILLING CODE 4910-13-P


[Federal Register Volume 81, Number 39 (Monday, February 29, 2016)]
[Notices]
[Page 10250]
[FR Doc No: 2016-04222]

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

DEPARTMENT OF HEALTH AND HUMAN SERVICES

Food and Drug Administration

[Docket No. FDA-2011-D-0147]

Agency Information Collection Activities; Announcement of Office
of Management and Budget Approval; Guidance for Industry and Food and
Drug Administration Staff; Section 905(j) Reports: Demonstrating
Substantial Equivalence for Tobacco Products and Demonstrating the
Substantial Equivalence of a New Tobacco Product: Responses to
Frequently Asked Questions

AGENCY: Food and Drug Administration, HHS.

ACTION: Notice.

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

SUMMARY: The Food and Drug Administration (FDA) is announcing that a
collection of information entitled ``Guidance for Industry and Food and
Drug Administration Staff; Section 905(j) Reports: Demonstrating
Substantial Equivalence for Tobacco Products and Demonstrating the
Substantial Equivalence of a New Tobacco Product: Responses to
Frequently Asked Questions'' has been approved by the Office of
Management and Budget (OMB) under the Paperwork Reduction Act of 1995.

FOR FURTHER INFORMATION CONTACT: FDA PRA Staff, Office of Operations,
Food and Drug Administration, 8455 Colesville Rd., COLE-14526, Silver
Spring, MD 20993-0002<EMAIL_ADDRESS>
SUPPLEMENTARY INFORMATION: On July 16, 2015, the Agency submitted a
proposed collection of information entitled ``Guidance for Industry and
Food and Drug Administration Staff; Section 905(j) Reports:
Demonstrating Substantial Equivalence for Tobacco Products and
Demonstrating the Substantial Equivalence of a New Tobacco Product:
Responses to Frequently Asked Questions'' to OMB for review and
clearance under 44 U.S.C. 3507. 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. OMB has now
approved the information collection and has assigned OMB control number
0910-0673. The approval expires on January 31, 2019. A copy of the
supporting statement for this information collection is available on
the Internet at http://www.reginfo.gov/public/do/PRAMain.

    Dated: February 23, 2016.
Leslie Kux,
Associate Commissioner for Policy.
[FR Doc. 2016-04222 Filed 2-26-16; 8:45 am]
 BILLING CODE 4164-01-P


[Federal Register Volume 81, Number 72 (Thursday, April 14, 2016)]
[Notices]
[Pages 22070-22071]
[FR Doc No: 2016-08604]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

Notice of Staff Attendance at Southwest Power Pool Regional
Entity Trustee, Regional State Committee, Members' and Board of
Directors' Meetings

    The Federal Energy Regulatory Commission (Commission) hereby gives
notice that Commissioners and members of its staff may attend the
meetings of the Southwest Power Pool, Inc. (SPP) Regional Entity
Trustee (RE), Regional State Committee (RSC), SPP Members Committee and
Board of Directors, as noted below. Their attendance is part of the
Commission's ongoing outreach efforts.
    All meetings will be held at the El Dorado Hotel, 309 West San
Francisco St., Santa Fe, NM 87501. The phone number is<PHONE_NUMBER>.

SPP RE

April 25, 2016 (8:00 a.m.-3:00 p.m.)

SPP RSC

April 25, 2016 (1:00 p.m.-5:00 p.m.)

SPP Members/Board of Directors

April 26, 2016 (8:00 a.m.-3:00 p.m.)

    The discussions may address matters at issue in the following
proceedings:

Docket No. ER11-1844, Midcontinent Independent System Operator, Inc.
Docket No. EL12-60, Southwest Power Pool, Inc., et al.
Docket No. ER12-1179, Southwest Power Pool, Inc.
Docket No. ER12-1586, Southwest Power Pool, Inc.
Docket No. ER13-1937, Southwest Power Pool, Inc.
Docket No. ER13-1939, Southwest Power Pool, Inc.
Docket No. EL15-66, Southern Company Services, et al. v. Midcontinent
Independent System Operator, Inc.
Docket No. EL15-77, Morgan Stanley Capital Group Inc. v. Midcontinent
Independent System Operator, Inc.
Docket No. ER14-67, Southwest Power Pool, Inc.
Docket No. ER14-2445, Midcontinent Independent System Operator, Inc.
Docket No. ER15-1499, Southwest Power Pool, Inc.
Docket No. ER15-1775, Southwest Power Pool, Inc.
Docket No. ER15-1777, Southwest Power Pool, Inc.
Docket No. ER15-1943, Southwest Power Pool, Inc.
Docket No. ER15-1976, Southwest Power Pool, Inc.
Docket No. ER15-2028, Southwest Power Pool, Inc.
Docket No. ER15-2069, Northwestern Corporation.
Docket No. ER15-2115, Southwest Power Pool, Inc.
Docket No. ER15-2265, Southwest Power Pool, Inc.
Docket No. ER15-2324, Southwest Power Pool, Inc.
Docket No. ER15-2347, Southwest Power Pool, Inc.
Docket No. ER15-2351, Southwest Power Pool, Inc.
Docket No. ER15-2356, Southwest Power Pool, Inc.
Docket No. EL16-20, Grid Assurance LLC.
Docket No. ER16-13, Southwest Power Pool, Inc.
Docket No. ER16-165, Southwest Power Pool, Inc.
Docket No. ER16-204, Southwest Power Pool, Inc.
Docket No. ER16-209, Southwest Power Pool, Inc.
Docket No. ER16-228, Southwest Power Pool, Inc.
Docket No. ER16-704, Southwest Power Pool, Inc.
Docket No. ER16-791, Southwest Power Pool, Inc.
Docket No. ER16-800, Southwestern Public Service Company.
Docket No. ER16-829, Southwest Power Pool, Inc.
Docket No. ER16-846, Southwest Power Pool, Inc.
Docket No. ER16-862, Southwest Power Pool, Inc.
Docket No. ER16-863, Southwest Power Pool, Inc.
Docket No. ER16-932, Southwest Power Pool, Inc.
Docket No. ER16-1022, Southwest Power Pool, Inc.
Docket No. ER16-1037, Southwest Power Pool, Inc.
Docket No. ER16-1040, Southwest Power Pool, Inc.
Docket No. ER16-1049, Southwest Power Pool, Inc.
Docket No. ER16-1050, Southwest Power Pool, Inc.
Docket No. ER16-1054, Southwest Power Pool, Inc.
Docket No. ER16-1061, Southwest Power Pool, Inc.
Docket No. ER16-1064, Southwest Power Pool, Inc.
Docket No. ER16-1065, Southwest Power Pool, Inc.
Docket No. ER16-1077, Southwest Power Pool, Inc.
Docket No. ER16-1086, Southwest Power Pool, Inc.
Docket No. ER16-1092, Southwest Power Pool, Inc.
Docket No. ER16-1096, Southwest Power Pool, Inc.

Docket No. ER16-1201, Southwest Power Pool, Inc.
Docket No. ER16-1211, Midcontinent Independent System Operator, Inc.
Docket No. ER16-1259, Southwest Power Pool, Inc.
Docket No. ER16-1260, Southwest Power Pool, Inc.
Docket No. ER16-1261, Southwest Power Pool, Inc.
Docket No. ER16-1262, Midcontinent Independent System Operator, Inc.
Docket No. ER16-1268, Southwest Power Pool, Inc.
Docket No. ER16-1282, Southwest Power Pool, Inc.
Docket No. ER16-1284, Southwest Power Pool, Inc.
Docket No. ER16-1285, Southwest Power Pool, Inc.
Docket No. ER16-1286, Southwest Power Pool, Inc.
Docket No. ER16-1288, Southwest Power Pool, Inc.
Docket No. ER16-1294, Southwest Power Pool, Inc.
Docket No. ER16-1305, Southwest Power Pool, Inc.
Docket No. ER16-1351, Westar Energy, Inc.
Docket No. ER16-1355, Westar Energy, Inc.
Docket No. ER16-1312, Southwest Power Pool, Inc.
Docket No. ER16-1314, Southwest Power Pool, Inc.
Docket No. ER16-1318, Westar Energy, Inc.
Docket No. ER16-1331, Southwest Power Pool, Inc.
Docket No. ER16-1341, Southwest Power Pool, Inc.
Docket No. ER16-1350, Southwest Power Pool, Inc.

    These meetings are open to the public.
    For more information, contact Patrick Clarey, Office of Energy
Market Regulation, Federal Energy Regulatory Commission at (317) 249-
5937 or<EMAIL_ADDRESS>
    Dated: April 8, 2016.
Nathaniel J. Davis, Sr.,
Deputy Secretary.
[FR Doc. 2016-08604 Filed 4-13-16; 8:45 am]
 BILLING CODE 6717-01-P