[Federal Register Volume 83, Number 50 (Wednesday, March 14, 2018)]
[Notices]
[Pages 11208-11210]
[FR Doc No: 2018-05119]

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

DEPARTMENT OF HEALTH AND HUMAN SERVICES

Food and Drug Administration

[Docket No. FDA-2018-N-0987]

Patient-Focused Drug Development on Opioid Use Disorder; Public
Meeting; Request for Comments

AGENCY: Food and Drug Administration, HHS.

ACTION: Notice of public meeting; request for comments.

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

SUMMARY: The Food and Drug Administration (FDA, the Agency, or we) is
announcing the following public meeting entitled ``Patient-Focused Drug
Development on Opioid Use Disorder.'' The purpose of the public meeting
is to obtain patients' perspectives on the impacts of and treatment
approaches for opioid use disorder (OUD). This meeting is a part of
FDA's ongoing work aimed at reducing the impact of opioid abuse and
addiction.

DATES: The public meeting will be held on April 17, 2018, from 10 a.m.
to 4 p.m. Submit either electronic or written comments on this public
meeting by June 18, 2018. See the SUPPLEMENTARY INFORMATION section for
registration date and information.

ADDRESSES: The public meeting will be held at FDA's White Oak Campus,
10903 New Hampshire Ave., Bldg. 31 Conference Center, the Great Room
(Rm. 1503), Silver Spring, MD 20993. Entrance for the public meeting
participants (non-FDA employees) is through Building 1 where routine
security check procedures will be performed. For parking and security
information, please refer to https://www.fda.gov/AboutFDA/WorkingatFDA/BuildingsandFacilities/WhiteOakCampusInformation/ucm241740.htm.
    You may submit comments as follows. Please note that late, untimely
filed comments will not be considered. Electronic comments must be
submitted on or before June 18, 2018. The https://www.regulations.gov
electronic filing system will accept comments until midnight Eastern
Time at the end of June 18, 2018. Comments received by mail/hand
delivery/courier (for written/paper submissions) will be considered
timely if they are postmarked or the delivery service acceptance
receipt is on or before that date.

Electronic Submissions

    Submit electronic comments in the following way:
     Federal eRulemaking Portal: https://www.regulations.gov.
Follow the instructions for submitting comments. Comments submitted
electronically, including attachments, to https://www.regulations.gov
will be posted to the docket unchanged. Because your comment will be
made public, you are solely responsible for ensuring that your comment
does not include any confidential information that you or a third party
may not wish to be posted, such as medical information, your or anyone
else's Social Security number, or confidential business information,
such as a manufacturing process. Please note that if you include your
name, contact information, or other information that identifies you in
the body of your comments, that information will be posted on https://www.regulations.gov.
     If you want to submit a comment with confidential
information that you do not wish to be made available to the public,
submit the comment as a written/paper submission and in the manner
detailed (see ``Written/Paper Submissions'' and ``Instructions'').

Written/Paper Submissions

    Submit written/paper submissions as follows:

     Mail/Hand delivery/Courier (for written/paper
submissions): Dockets Management Staff (HFA-305), Food and Drug
Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
     For written/paper comments submitted to the Dockets
Management Staff, FDA will post your comment, as well as any
attachments, except for information submitted, marked and identified,
as confidential, if submitted as detailed in ``Instructions.''
    Instructions: All submissions received must include the Docket No.
FDA-2018-N-0987 for ``Patient-Focused Drug Development on Opioid Use
Disorder; Public Meeting; Request for Comments.'' Received comments,
those filed in a timely manner (see ADDRESSES), will be placed in the
docket and, except for those submitted as ``Confidential Submissions,''
publicly viewable at https://www.regulations.gov or at the Dockets
Management Staff between 9 a.m. and 4 p.m., Monday through Friday.
     Confidential Submissions--To submit a comment with
confidential information that you do not wish to be made publicly
available, submit your comments only as a written/paper submission. You
should submit two copies total. One copy will include the information
you claim to be confidential with a heading or cover note that states
``THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION.'' The Agency will
review this copy, including the claimed confidential information, in
its consideration of comments. The second copy, which will have the
claimed confidential information redacted/blacked out, will be
available for public viewing and posted on https://www.regulations.gov.
Submit both copies to the Dockets Management Staff. If you do not wish
your name and contact information to be made publicly available, you
can provide this information on the cover sheet and not in the body of
your comments and you must identify this information as
``confidential.'' Any information marked as ``confidential'' will not
be disclosed except in accordance with 21 CFR 10.20 and other
applicable disclosure law. For more information about FDA's posting of
comments to public dockets, see 80 FR 56469, September 18, 2015, or
access the information at: https://www.gpo.gov/fdsys/pkg/FR-2015-09-18/pdf/2015-23389.pdf.
    Docket: For access to the docket to read background documents or
the electronic and written/paper comments received, go to https://www.regulations.gov and insert the docket number, found in brackets in
the heading of this document, into the ``Search'' box and follow the
prompts and/or go to the Dockets Management Staff, 5630 Fishers Lane,
Rm. 1061, Rockville, MD 20852.

FOR FURTHER INFORMATION CONTACT: Meghana Chalasani, Center for Drug
Evaluation and Research, Food and Drug Administration, 10903 New
Hampshire Ave., Bldg. 51, Rm. 1146, Silver Spring, MD 20993-0002, 240-
402-6525, Fax:<PHONE_NUMBER>, [email protected].

SUPPLEMENTARY INFORMATION:

I. Background

    This meeting will provide FDA the opportunity to better understand
the patient perspective on the impacts of OUD and on treatment
approaches for OUD. OUD is the diagnostic term used for a chronic
neurobiological disease characterized by a problematic pattern of
opioid use leading to significant impairment or distress. OUD includes
signs and symptoms that reflect compulsive, prolonged self-
administration of opioid substances for no legitimate medical purpose,
or, if another medical condition is present that required opioid
treatment, the opioid is used in doses far greater than the amount
needed for treatment of that medical condition. FDA is interested in
learning patients' perspectives on OUD, including the effects on their
health and well-being that have the greatest negative effect on daily
life, their experience using prescription medical treatments and other
treatments or therapies for OUD, and challenges or barriers to
accessing or using medical treatments for OUD.
    There are three drugs approved by FDA for the treatment of OUD:
Buprenorphine, methadone, and naltrexone. FDA is taking steps to
facilitate the development of new medications for the treatment of OUD
and new formulations of existing drugs that could better suit patient
needs. Promoting wider appropriate use of these safe and effective
medications is also the focus of FDA's ongoing work to reduce the scope
and magnitude of the opioid crisis.
    At the meeting, patients and patient representatives will provide
patient perspectives on the symptoms and daily impacts of OUD and on
treatment approaches for OUD. The questions that will be asked of
patients and patient representatives at the meeting are listed in the
following section and organized by topic. For each topic, a brief
initial patient panel discussion will begin the dialogue. This will be
followed by a facilitated discussion inviting comments from other
patient and patient representative participants. In addition to input
generated through this public meeting, FDA is interested in receiving
patient and patient representative input addressing these questions
through written comments, which can be submitted to the public docket
(see ADDRESSES). When submitting comments, if you are commenting on
behalf of a patient, please indicate that you are doing so and answer
the following questions as much as possible from the patient's
perspective.
    FDA will post the agenda and other meeting materials approximately
5 days before the meeting at: https://www.fda.gov/ForIndustry/UserFees/PrescriptionDrugUserFee/ucm591290.htm.

II. Topics for Discussion at the Public Meeting

Topic 1: Symptoms and Daily Impacts of OUD That Matter Most to Patients

    1. Of all the ways that OUD negatively affects your health and
well-being, which effects have the most significant impact on your
daily life? Examples of negative effects may include:
     Effects of using opioids, such as confusion, constipation,
or other symptoms;
     Effects of opioid withdrawal, such as nausea, diarrhea, or
other symptoms;
     Effects of opioid ``cravings;''
     Impacts on ability to function in personal or professional
life;
     Emotional or social effects; and
     Other potential effects.
    2. How does OUD affect daily life on your best days? On your worst
days?
    3. How has your OUD changed over time?
    4. What worries you most about your condition?

Topic 2: Patients' Perspectives on Current Approaches to Treatment of
OUD

    1. Are you currently using, or have you used in the past, any
prescription medical treatments to treat your OUD? Such treatments may
include buprenorphine, methadone, naltrexone, and others that your
health care provider has prescribed. If so, please describe your
experiences with these treatments.
     How well have these treatments worked for you? How well
have they helped address the effects of OUD that are most bothersome to
you?
     What are the biggest problems you have faced in using
these treatments? Examples may include bothersome side effects,
challenges getting the medicines, concern about stigma, and other
possible problems.

    2. Besides prescription medical treatments, are there other
treatments or therapies that you currently use to address your OUD? If
so, please describe. How well do these treatments or therapies help
address the effects of OUD that are most bothersome to you?
    3. Of all treatments, therapies, or other steps that you have taken
to address your OUD, what have you found to be most effective in
helping you manage your OUD?
    4. What are the biggest factors that you take into account when
making decisions about seeking out or using treatments for OUD?
    5. What specific things would you look for in an ideal treatment
for OUD?
    6. If you had the opportunity to consider participating in a
clinical trial studying experimental treatments for OUD, what factors
would you consider when deciding whether or not to participate?

III. Participating in the Public Meeting

    Registration: To register for the public meeting, visit https://www.eventbrite.com/e/public-meeting-for-patient-focused-drug-development-on-opioid-use-disorder-oud-registration-42531194949. Please
register by April 11, 2018. Please provide complete contact information
for each attendee, including name, title, affiliation, address, email,
and telephone. Persons without access to the internet can call 240-402-
6525 to register. If you are unable to attend the meeting in person,
you can register to view a live webcast of the meeting. You will be
asked to indicate in your registration if you plan to attend in person
or via the webcast.
    Registration is free and based on space availability, with priority
given to early registrants. Persons interested in attending this public
meeting must register by April 11, 2018. Early registration is
recommended because seating is limited; therefore, FDA may limit the
number of participants from each organization. Registrants will receive
confirmation when they have been accepted. If time and space permit,
onsite registration on the day of the public meeting will be provided
beginning at 9 a.m.
    If you need special accommodations because of a disability, please
contact Meghana Chalasani (see FOR FURTHER INFORMATION CONTACT) no
later than April 11, 2018.
    Panelist Selection: Patients or patient representatives who are
interested in presenting comments as part of the initial panel
discussions will be asked to indicate in their registration which
topic(s) they wish to address. These patients or patient
representatives also will be asked to send [email protected] a
brief summary of responses to the topic questions by April 2, 2018.
Panelists will be notified of their selection approximately 7 days
before the public meeting. We will try to accommodate all patients and
patient stakeholders who wish to speak, either through the panel
discussion or audience participation; however, the duration of comments
may be limited by time constraints.
    Open Public Comment: There will be time allotted during the meeting
for open public comment. Sign-up for this session will be on a first-
come, first-serve basis on the day of the workshop. Individuals and
organizations with common interests are urged to consolidate or
coordinate and request time for a joint presentation. No commercial or
promotional material will be permitted to be presented or distributed
at the public workshop.
    Streaming Webcast of the Public Meeting: This public meeting will
also be webcast. Please register for the webcast by visiting https://www.eventbrite.com/e/public-meeting-for-patient-focused-drug-development-on-opioid-use-disorder-oud-registration-42531194949.
    If you have never attended a Connect Pro event before, test your
connection at https://collaboration.fda.gov/common/help/en/support/meeting_test.htm. To get a quick overview of the Connect Pro program,
visit https://www.adobe.com/go/connectpro_overview. FDA has verified
the website addresses in this document, as of the date this document
publishes in the Federal Register, but websites are subject to change
over time.
    Transcripts: Please be advised that as soon as a transcript of the
public meeting is available, it will be accessible at https://www.regulations.gov. It may be viewed at the Dockets Management Staff
(see ADDRESSES). A link to the transcript will also be available on the
internet at https://www.fda.gov/ForIndustry/UserFees/PrescriptionDrugUserFee/ucm591290.htm.

    Dated: March 8, 2018.
Leslie Kux,
Associate Commissioner for Policy.
[FR Doc. 2018-05119 Filed 3-13-18; 8:45 am]
 BILLING CODE 4164-01-P


[Federal Register: September 3, 2008 (Volume 73, Number 171)]
[Rules and Regulations]
[Page 51358-51361]
[DOCID:fr03se08-7]

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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 97

[Docket No. 30622; Amdt. No. 3282]

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

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Final rule.

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

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

DATES: This rule is effective September 3, 2008. 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 September 3, 2008.

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 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. Thus, 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 August 8, 2008.
James J. Ballough,
Director, Flight Standards Service.

Adoption of the Amendment

0
Accordingly, pursuant to the authority delegated to me, Under 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 28 AUG 2008

Manchester, NH, Manchester, ILS OR LOC/DME RWY 17, Amdt 1
Manchester, NH, Manchester, RNAV (GPS) Y RWY 17, Orig
Manchester, NH, Manchester, RNAV (RNP) Z RWY 17, Orig

Effective 25 SEP 2008

Anvik, AK, Anvik, GPS RWY 35, Orig, CANCELLED
Anvik, AK, Anvik, RNAV (GPS) RWY 17, Orig
Anvik, AK, Anvik, RNAV (GPS) RWY 35, Orig
Anvik, AK, Anvik, Takeoff Minimums and Obstacle DP, Orig
Galena, AK, Edward G. Pitka, SR, GPS RWY 07, Orig, CANCELLED
Galena, AK, Edward G. Pitka, SR, GPS RWY 25, Orig, CANCELLED
Galena, AK, Edward G. Pitka, SR, RNAV (GPS) RWY 7, Orig
Galena, AK, Edward G. Pitka, SR, RNAV (GPS) RWY 25, Orig
Huslia, AK, Huslia, RNAV (GPS) RWY 3, Amdt 2
Huslia, AK, Huslia, RNAV (GPS) RWY 21, Amdt 2
Huslia, AK, Huslia, Takeoff Minimums and Obstacle DP, Orig
Benton, AR, Saline County Regional, RNAV (GPS) RWY 2, Orig
Benton, AR, Saline County Regional, RNAV (GPS) RWY 20, Orig
Little Rock, AR, Adams Field, ILS OR LOC RWY 22L, Orig
Little Rock, AR, Adams Field, ILS OR LOC RWY 22R, ILS RWY 22R (CAT
II), ILS RWY (CAT III), Amdt 2
Little Rock, AR, Adams Field, LOC RWY 22L, Orig, CANCELLED
Little Rock, AR, Adams Field, Takeoff Minimums and Obstacle DP, Amdt
8
Magnolia, AR, Magnolia Muni, RNAV (GPS) RWY 36, Amdt 1
Newport, AR, Newport Muni, GPS RWY 18, Orig-B, CANCELLED
Newport, AR, Newport Muni, GPS RWY 36, Orig-B, CANCELLED
Newport, AR, Newport Muni, RNAV (GPS) RWY 18, Orig
Newport, AR, Newport Muni, RNAV (GPS) RWY 36, Orig
Newport, AR, Newport Muni, Takeoff Minimums and Obstacle DP, Orig
Arcata/Eureka, CA, Arcata, GPS RWY 32, Orig, CANCELLED
Arcata/Eureka, CA, Arcata, RNAV (GPS) RWY 32, Orig
Burbank, CA, Bob Hope, RNAV (RNP) Z RWY 8, Orig
Merced, CA, Merced Muni/Macready Field, GPS RWY 30, Orig-B,
CANCELLED
Merced, CA, Merced Muni/Macready Field, RNAV (GPS) RWY 30, Orig
Santa Barbara, CA, Santa Barbara Muni, RNAV (GPS) RWY 7, Orig-A
Truckee, CA, Truckee-Tahoe, Takeoff Minimums and Obstacle DP, Amdt 4
Aspen, CO, Aspen-Pitkin County/Sardy Field, Takeoff Minimums and
Obstacle DP, Amdt 8
Denver, CO, Front Range, GPS RWY 35, Orig, CANCELLED
Denver, CO, Front Range, ILS OR LOC RWY 26, Amdt 4
Denver, CO, Front Range, NDB RWY 26, Amdt 4
Denver, CO, Front Range, RNAV (GPS) RWY 17, Orig
Denver, CO, Front Range, RNAV (GPS) RWY 26, Orig
Denver, CO, Front Range, RNAV (GPS) RWY 35, Orig
Rifle, CO, Garfield County Regional, GPS RWY 8, Orig-A, CANCELLED
Rifle, CO, Garfield County Regional, GPS RWY 26, Orig-A, CANCELLED
Rifle, CO, Garfield County Regional, ILS RWY 26, Amdt 1
Rifle, CO, Garfield County Regional, LOC/DME-A, Amdt 7
Rifle, CO, Garfield County Regional, RNAV (GPS) W RWY 26, Orig
Rifle, CO, Garfield County Regional, RNAV (GPS) X RWY 26, Orig
Rifle, CO, Garfield County Regional, RNAV (GPS) Y RWY 8, Orig
Rifle, CO, Garfield County Regional, RNAV (RNP) Y RWY 26, Orig
Rifle, CO, Garfield County Regional, RNAV (RNP) Z RWY 8, Orig
Rifle, CO, Garfield County Regional, RNAV (RNP) Z RWY 26, Orig
Rifle, CO, Garfield County Regional, VOR/DME-C, Amdt 1
Orlando, FL, Orlando Sanford Intl, RNAV (GPS) RWY 9L, Amdt 2
Orlando, FL, Orlando Sanford Intl, RNAV (GPS) RWY 9R, Orig
Orlando, FL, Orlando Sanford Intl, RNAV (GPS) RWY 27R, Amdt 1
Orlando, FL, Orlando Intl, Takeoff Minimums and Obstacle DP, Amdt 1
Palm Coast, FL, Flagler County, RNAV (GPS) RWY 6, Amdt 1
Palm Coast, FL, Flagler County, RNAV (GPS) RWY 11, Amdt 1
Tampa, FL, Tampa Intl, LOC RWY 36R, Amdt 2
Tampa, FL, Tampa Intl, RNAV (GPS) RWY 36R, Amdt 1
Gainesville, GA, Lee Gilmer Memorial, ILS OR LOC/DME RWY 5, Orig
Gainesville, GA, Lee Gilmer Memorial, LOC RWY 4, Amdt 5D, CANCELLED
Gainesville, GA, Lee Gilmer Memorial, RNAV (GPS) RWY 5, Amdt 1
Gainesville, GA, Lee Gilmer Memorial, RNAV (GPS) RWY 23, Amdt 1
Washington, GA, Washington-Wilkes County, RNAV (GPS) RWY 13, Amdt 1
Washington, GA, Washington-Wilkes County, RNAV (GPS) RWY 31, Amdt 1
Denison, IA, Denison Muni, NDB RWY 30, Amdt 6
Denison, IA, Denison Muni, RNAV (GPS) RWY 12, Amdt 1
Denison, IA, Denison Muni, RNAV (GPS) RWY 30, Amdt 1
Denison, IA, Denison Muni, Takeoff Minimums and Obstacle DP, Orig
Perry, IA, Perry Muni, GPS RWY 32, Orig-A, CANCELLED
Perry, IA, Perry Muni, RNAV (GPS) RWY 32, Orig
Perry, IA, Perry Muni, Takeoff Minimums and Obstacle DP, Orig
Chicago, IL, Chicago O'Hare Intl, ILS OR LOC RWY 10, ILS RWY 10 (CAT
II), ILS RWY 10 (CAT III), Amdt 16
Chicago, IL, Chicago O'Hare Intl, ILS OR LOC RWY 28, ILS RWY 28 (CAT
II), ILS RWY 28 (CAT III), Amdt 15
Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 10, Amdt 3
Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 28, Amdt 2
Pekin, IL, Pekin Muni, RNAV (GPS) RWY 9, Orig
Pekin, IL, Pekin Muni, RNAV (GPS) RWY 27, Orig

Pekin, IL, Pekin Muni, Takeoff Minimums and Obstacle DP, Orig
Pekin, IL, Pekin Muni, VOR-A, Amdt 7
Pekin, IL, Pekin Muni, VOR/DME RNAV OR GPS RWY 9, Amdt 5A, CANCELLED
Robinson, IL, Robinson Muni, RNAV (GPS) RWY 9, Orig
Robinson, IL, Robinson Muni, RNAV (GPS) RWY 27, Orig
Robinson, IL, Robinson Muni, Takeoff Minimums and Obstacle DP, Orig
Fort Wayne, IN, Fort Wayne International, RNAV (GPS) RWY 5, Amdt 1
Fort Wayne, IN, Fort Wayne International, RNAV (GPS) RWY 23, Amdt 2
Indianapolis, IN, Eagle Creek Airpark, RNAV (GPS) RWY 21, Orig
Indianapolis, IN, Indianapolis Executive, RNAV (GPS) RWY 18, Orig
Indianapolis, IN, Indianapolis Executive, RNAV (GPS) RWY 36, Orig
Indianapolis, IN, Indianapolis Executive, Takeoff Minimums and
Obstacle DP, Orig
Indianapolis, IN, Indianapolis Executive, VOR RWY 36, Amdt 9
Indianapolis, IN, Indianapolis Executive, VOR/DME RWY 18, Orig
Rochester, IN, Fulton County, RNAV (GPS) RWY 11, Amdt 1
Rochester, IN, Fulton County, RNAV (GPS) RWY 29, Amdt 1
Rochester, IN, Fulton County, Takeoff Minimums and Obstacle DP, Orig
Covington, KY, Cincinnati/Northern Kentucky Intl, ILS OR LOC RWY 9,
Amdt 18
Covington, KY, Cincinnati/Northern Kentucky Intl, ILS OR LOC RWY
18C, Amdt 22
Covington, KY, Cincinnati/Northern Kentucky Intl, ILS OR LOC RWY
18L, Amdt 7
Covington, KY, Cincinnati/Northern Kentucky Intl, ILS OR LOC RWY
18R; ILS RWY 18R (CAT II), Amdt 1
Covington, KY, Cincinnati/Northern Kentucky Intl, ILS OR LOC RWY 27,
Amdt 17
Covington, KY, Cincinnati/Northern Kentucky Intl, ILS OR LOC RWY
36C; ILS RWY 36C (CAT II); ILS RWY 36C (CAT III), Amdt 41
Covington, KY, Cincinnati/Northern Kentucky Intl, ILS OR LOC RWY
36L; ILS RWY 36L, (CAT II), Amdt 1
Covington, KY, Cincinnati/Northern Kentucky Intl, ILS OR LOC RWY
36R; ILS RWY 36R (CAT II); ILS RWY 36R (CAT III), Amdt 8
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (GPS) Y RWY
9, Amdt 1
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (GPS) Y RWY
18C, Amdt 1
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (GPS) Y RWY
18L, Amdt 1
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (GPS) Y RWY
18R, Amdt 1
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (GPS) Y RWY
27, Orig
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (GPS) Y RWY
36C, Amdt 1
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (GPS) Y RWY
36L, Amdt 1
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (GPS) Y RWY
36R, Amdt 1
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (RNP) Z RWY
9, Orig
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (RNP) Z RWY
18C, Orig
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (RNP) Z RWY
18L, Orig
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (RNP) Z RWY
18R, Orig
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (RNP) Z RWY
27, Orig
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (RNP) Z RWY
36C, Orig
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (RNP) Z RWY
36L, Orig
Covington, KY, Cincinnati/Northern Kentucky Intl, RNAV (RNP) Z RWY
36R, Orig
Henderson, KY, Henderson City-County, RNAV (GPS) RWY 9, Amdt 1
Henderson, KY, Henderson City-County, RNAV (GPS) RWY 27, Amdt 1
Louisville, KY, Louisville Intl-Standiford Fld, GPS RWY 17L, Orig,
CANCELLED
Louisville, KY, Louisville Intl-Standiford Fld, GPS RWY 17R, Orig-A,
CANCELLED
Louisville, KY, Louisville Intl-Standiford Fld, GPS RWY 35L, Orig-A,
CANCELLED
Louisville, KY, Louisville Intl-Standiford Fld, GPS RWY 35R, Orig-A,
CANCELLED
Louisville, KY, Louisville Intl-Standiford Fld, ILS OR LOC RWY 17L,
Amdt 3
Louisville, KY, Louisville Intl-Standiford Fld, ILS OR LOC RWY 17R,
Amdt 1
Louisville, KY, Louisville Intl-Standiford Fld, ILS OR LOC RWY 35L;
ILS RWY 35L (CAT II); ILS RWY 35L (CAT III), Amdt 2
Louisville, KY, Louisville Intl-Standiford Fld, ILS OR LOC RWY 35R;
ILS RWY 35R (CAT II); ILS RWY 35R (CAT III), Amdt 3
Louisville, KY, Louisville Intl-Standiford Fld, RNAV (GPS) RWY 17L,
Orig
Louisville, KY, Louisville Intl-Standiford Fld, RNAV (GPS) RWY 17R,
Orig
Louisville, KY, Louisville Intl-Standiford Fld, RNAV (GPS) RWY 35R,
Orig
Louisville, KY, Louisville Intl-Standiford Fld, RNAV (GPS) Y RWY
35L, Orig
Louisville, KY, Louisville Intl-Standiford Fld, RNAV (RNP) Z RWY
35L, Orig
Detroit, MI, Willow Run, RNAV (GPS) RWY 9L, Amdt 1
Detroit, MI, Willow Run, RNAV (GPS) RWY 9R, Amdt 1
Detroit, MI, Willow Run, RNAV (GPS) RWY 14, Amdt 1
Owosso, MI, Owosso Community, RNAV (GPS) RWY 10, Amdt 1
Owosso, MI, Owosso Community, RNAV (GPS) RWY 28, Amdt 1
Owosso, MI, Owosso Community, VOR/DME RWY 28, Amdt 1
Jacksonville, NC, Albert J. Ellis, NDB RWY 5, Amdt 8
Jacksonville, NC, Albert J. Ellis, RNAV (GPS) RWY 5, Orig
Oxford, NC, Henderson-Oxford, LOC RWY 6, Amdt 1
Oxford, NC, Henderson-Oxford, NDB RWY 6, Amdt 2
Oxford, NC, Henderson-Oxford, RNAV (GPS) RWY 6, Orig
Oxford, NC, Henderson-Oxford, RNAV (GPS) RWY 24, Orig
Oxford, NC, Henderson-Oxford, Takeoff Minimums and Obstacle DP, Orig
Atlantic City, NJ, Atlantic City International, COPTER ILS OR LOC/
DME RWY 13, Amdt 1B
Atlantic City, NJ, Atlantic City International, ILS OR LOC RWY 13,
Amdt 8
Atlantic City, NJ, Atlantic City International, ILS OR LOC/DME RWY
31, Orig-A
Atlantic City, NJ, Atlantic City International, RNAV (GPS) RWY 4,
Amdt 1A
Atlantic City, NJ, Atlantic City International, RNAV (GPS) RWY 13,
Amdt 3
Atlantic City, NJ, Atlantic City International, RNAV (GPS) RWY 31,
Amdt 2
Atlantic City, NJ, Atlantic City International, RADAR-1, Amdt 15
Atlantic City, NJ, Atlantic City International, VOR RWY 4, Amdt 15A
Atlantic City, NJ, Atlantic City International, VOR RWY 13, Amt 4A
Atlantic City, NJ, Atlantic City International, VOR RWY 31, Amdt 1
Reno, NV, Reno/Tahoe Intl, RNAV (GPS) X RWY 34L, Amdt 1
Reno, NV, Reno/Tahoe Intl, RNAV (GPS) X RWY 34R, Amdt 1
Reno, NV, Reno/Tahoe Intl, RNAV (GPS) Y RWY 16L, Amdt 1
Reno, NV, Reno/Tahoe Intl, RNAV (GPS) Y RWY 16R, Amdt 1
Reno, NV, Reno/Tahoe Intl, RNAV (GPS) Y RWY 34L, Orig
Reno, NV, Reno/Tahoe Intl, RNAV (GPS) Y RWY 34R, Orig
Reno, NV, Reno/Tahoe Intl, RNAV (RNP) Z RWY 16L, Orig
Reno, NV, Reno/Tahoe Intl, RNAV (RNP) Z RWY 16R, Orig
Reno, NV, Reno/Tahoe Intl, RNAV (RNP) Z RWY 34L, Orig
Reno, NV, Reno/Tahoe Intl, RNAV (RNP) Z RWY 34R, Orig
Hornell, NY, Hornell Muni, Takeoff Minimums and Obstacle DP, Amdt 4
Cleveland, OH, Cleveland-Hopkins Intl, ILS OR LOC RWY 24L, Amdt 20
London, OH, Madison County, GPS RWY 9, Amdt 1, CANCELLED
London, OH, Madison County, GPS RWY 27, Orig, CANCELLED
London, OH, Madison County, NDB RWY 9, Amdt 9
London, OH, Madison County, RNAV (GPS) RWY 9, Orig
London, OH, Madison County, RNAV (GPS) RWY 27, Orig
Portsmouth, OH, Greater Portsmouth Rgnl, GPS RWY 36, Amdt 1B,
CANCELLED
Portsmouth, OH, Greater Portsmouth Rgnl, RNAV (GPS) RWY 18, Orig
Portsmouth, OH, Greater Portsmouth Rgnl, RNAV (GPS) RWY 36, Orig
Portsmouth, OH, Greater Portsmouth Rgnl, VOR/DME-A, Amdt 6
Portsmouth, OH, Greater Portsmouth Rgnl, VOR/DME RNAV OR GPS RWY 18,
Amdt 6B, CANCELLED

Grove, OK, Grove Muni, RNAV (GPS) RWY 18, Amdt 1
Grove, OK, Grove Muni, Takeoff Minimums and Obstacle DP, Orig
Quakertown, PA, Quakertown, Takeoff Minimums and Obstacle DP, Orig
Fort Worth, TX, Bourland Field, Takeoff Minimums and Obstacle DP,
Orig
Plains, TX, Yoakum County, RNAV (GPS) RWY 3, Orig
Plains, TX, Yoakum County, RNAV (GPS) RWY 21, Orig
Taylor, TX, Taylor Muni, Takeoff Minimums and Obstacle DP, Orig
Taylor, TX, Taylor Muni, VOR/DME RWY 17, Amdt 1
Waco, TX, TSTC-Waco, ILS OR LOC RWY 17L, Amdt 12
Waco, TX, TSTC-Waco, Takeoff Minimums and Obstacle DP, Orig
Moses Lake, WA, Grant County Intl, GPS RWY 4, Orig-B, CANCELLED
Moses Lake, WA, Grant County Intl, GPS RWY 14L, Orig-B, CANCELLED
Moses Lake, WA, Grant County Intl, GPS RWY 22, Orig-B, CANCELLED
Moses Lake, WA, Grant County Intl, RNAV (GPS) RWY 4, Orig
Moses Lake, WA, Grant County Intl, RNAV (GPS) RWY 14L, Orig
Moses Lake, WA, Grant County Intl, RNAV (GPS) RWY 22, Orig
Martinsburg, WV, Eastern WV Regional/Shepherd, RNAV (GPS) RWY 8,
Orig
Martinsburg, WV, Eastern WV Regional/Shepherd, RNAV (GPS) RWY 26,
Orig
Martinsburg, WV, Eastern WV Regional/Shepherd, Takeoff Minimums and
Obstacle DP, Amdt 6
Martinsburg, WV, Eastern WV Regional/Shepherd, VOR-A, Amdt 9

    On August 7, 2008 (73 FR 458660) the FAA published an Amendment
in Docket No. 30620, Amdt No. 3280 to Part 97 of the Federal
Aviation Regulations under section 97.31 effective September 25,
2008 which is corrected to read as follows:

Bangore, ME, Bangor Intl, RADAR-1, Amdt 4B
[FR Doc. E8-19514 Filed 9-2-08; 8:45 am]

BILLING CODE 4910-13-P


			  UNITED STATES OF AMERICA

		        DEPARTMENT OF TRANSPORTATION

			  OFFICE OF THE SECRETARY

			          WASHINGTON, D.C.

Issued by the Department of Transportation on May 21, 2004

NOTICE OF ACTION TAKEN -- DOCKET OST 1999-6374

________________________________________________________________________
________________________________________________________

This serves as notice to the public of the action described below, taken
by the Department official indicated (no additional confirming order
will be issued in this matter).

Applicant:  AERO REY, S.A. de C.V.
                                          Date Filed: March 8, 2004

Relief requested:  Exemption from 49 USC section 41301 to permit the
applicant to continue to conduct passenger charter operations between
Mexico and the United States, and other passenger charter operations in
accordance with 14 CFR Part 212, using small equipment.

If renewal, date and citation of last action:  March 13, 2003, in this
Docket.

Applicant representative:  Eugene E. Smith,<PHONE_NUMBER>       DOT
analyst:  Allen F. Brown,<PHONE_NUMBER>

Responsive pleadings:  None.

	DISPOSITION

Action:  Approved.
              Action date:  May 21, 2004

Effective dates of authority granted:  May 21, 2004, through May 21,
2005.

Basis for approval (bilateral agreement/reciprocity):  United
States-Mexico Air Transport Services Agreement of August 15, 1960, as
amended and extended (Agreement).

Except to the extent exempted/waived, this authority is subject to the
terms, conditions, and limitations indicated:  Standard exemption
conditions.

Special conditions/Partial grant/Denial basis/Remarks:  In the conduct
of these operations, the carrier must adhere to all applicable
provisions of the U.S.-Mexico Agreement.  In the conduct of these
operations, the carrier may only use aircraft capable of carrying no
more than 60 passengers and having a maximum payload capacity of no more
than 18,000 pounds (small equipment).  The above grant includes
authority to conduct Third and Fourth Freedom charter operations.  While
we have subjected, consistent with the provisions of the Agreement,
Mexican carriers conducting charter operations with large aircraft to
prior approval or submission of notice for their Third and Fourth
Freedom charters, we determined that any such requirement was not
necessary on public interest grounds in this case, since the carrier
will be conducting these operations solely with small aircraft.  (Other
charter operations to/from the United States under this authority,
however, are subject to prior approval under 14 CFR Part 212.)  Further,
we are continuing to allow Mexican carriers conducting passenger
charters using small equipment to make stopovers in the United States in
the conduct of such operations.

Action taken by:   Paul L. Gretch, Director

		      Office of International Aviation

________________________________________________________________________
________________________________________________________

Under authority assigned by the Department in its regulations, 14 CFR
Part 385, we found that (1) our action was consistent with Department
policy; (2) the applicant was qualified to perform its proposed
operations; (3) grant of the authority was consistent with the public
interest; and (4) grant of the authority would not constitute a major
regulatory action under the Energy Policy and Conservation Act of 1975.
To the extent not granted/deferred/dismissed, we denied all requests in
the referenced Docket.  We may amend, modify, or revoke the authority
granted in this Notice at any time without hearing at our discretion.

Persons entitled to petition the Department for review of the action set
forth in this Notice under the Department’s regulations, 14 CFR
§385.30, may file their petitions within seven (7) days after the date
of issuance of this Notice.  This action was effective when taken, and
the filing of a petition for review will not alter such effectiveness.

An electronic version of this document is available on the World Wide
Web at:

http://dms.dot.gov//reports/reports_aviation.asp


[Federal Register Volume 74, Number 111 (Thursday, June 11, 2009)]
[Rules and Regulations]
[Pages 27714-27716]
[FR Doc No: E9-13481]

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

ENVIRONMENTAL PROTECTION AGENCY

40 CFR Part 52

[EPA-R09-OAR-2009-0230; FRL-8900-8]

Revisions to the California State Implementation Plan, Monterey
Bay Unified Air Pollution Control District, Placer County Air Pollution
Control District

AGENCY: Environmental Protection Agency (EPA).

ACTION: Direct final rule.

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

SUMMARY: EPA is taking direct final action to approve revisions to the
Monterey Bay Unified Air Pollution Control District (MBUAPCD) and
Placer County Air Pollution Control District (PCAPCD) portions of the
California State Implementation Plan (SIP). These revisions concern
volatile organic compound (VOC) emissions from storage tanks and the
operation of steam drive crude oil production wells. We are approving
local rules that regulate these emission sources under the Clean Air
Act as amended in 1990 (CAA or the Act).

DATES: This rule is effective on August 10, 2009 without further
notice, unless EPA receives adverse comments by July 13, 2009. If we
receive such comments, we will publish a timely withdrawal in the
Federal Register to notify the public that this direct final rule will
not take effect.

ADDRESSES: Submit comments, identified by docket number EPA-R09-OAR-
2009-0230, by one of the following methods:
    1. Federal eRulemaking Portal: www.regulations.gov. Follow the on-
line instructions.
    2. E-mail<EMAIL_ADDRESS>    3. Mail or deliver: Andrew Steckel (Air-4), U.S. Environmental
Protection Agency Region IX, 75 Hawthorne Street, San Francisco, CA
94105-3901.

Instructions: All comments will be included in the public docket
without change and may be made available online at www.regulations.gov,
including any personal information provided, unless the comment
includes Confidential Business Information (CBI) or other information
whose disclosure is restricted by statute. Information that you
consider CBI or otherwise protected should be clearly identified as
such and should not be submitted through www.regulations.gov or e-mail.
www.regulations.gov is an ``anonymous access'' system, and EPA will not
know your identity or contact information unless you provide it in the
body of your comment. If you send e-mail directly to EPA, your e-mail
address will be automatically captured and included as part of the
public comment. If EPA cannot read your comment due to technical
difficulties and cannot contact you for clarification, EPA may not be
able to consider your comment. Electronic files should avoid the use of
special characters, any form of encryption, and be free of any defects
or viruses.
    Docket: The index to the docket for this action is available
electronically at www.regulations.gov and in hard copy at EPA Region
IX, 75 Hawthorne Street, San Francisco, California. While all documents
in the docket are listed in the index, some information may be publicly
available only at the hard copy location (e.g., copyrighted material),
and some may not be publicly available in either location (e.g., CBI).
To inspect the hard copy materials, please schedule an appointment
during normal business hours with the contact listed in the FOR FURTHER
INFORMATION CONTACT section.

FOR FURTHER INFORMATION CONTACT: Nicole Law, EPA Region IX, (415) 947-
4126<EMAIL_ADDRESS>
SUPPLEMENTARY INFORMATION: Throughout this document, ``we,'' ``us'' and
``our'' refer to EPA.

Table of Contents

I. The State's Submittal
    A. What rules did the State submit?
    B. Are there other versions of these rules?
    C. What is the purpose of the submitted rule revisions?
II. EPA's Evaluation and Action
    A. How is EPA evaluating the rules?
    B. Do the rules meet the evaluation criteria?
    C. EPA Recommendations to Further Improve the Rules
    D. Public Comment and Final Action
III. Statutory and Executive Order Reviews

I. The State's Submittal

A. What rules did the State submit?

    Table 1 lists the rules we are approving with the dates that they
were adopted by the local air agencies and submitted by the California
Air Resources Board (CARB).

                                            Table 1--Submitted Rules
----------------------------------------------------------------------------------------------------------------
               Local agency                 Rule No.             Rule title               Adopted     Submitted
----------------------------------------------------------------------------------------------------------------
MBUAPCD..................................        427  Steam Drive Crude Oil Production     10/17/07     03/07/08
                                                       Wells.
PCAPCD...................................        212  Storage of Organic Liquids......     06/19/97     07/18/08
----------------------------------------------------------------------------------------------------------------

    On April 17, 2008 and August 22, 2008, these rule submittals were
found to meet the completeness criteria in 40 CFR Part 51, Appendix V,
which must be met before formal EPA review.

B. Are there other versions of these rules?

    We approved versions of MBUAPCD Rule 427 and PCAPCD Rule 212 into
the SIP on August 22, 2002 (see 67 FR 54349) and May 6, 1996 (see 61 FR
20145). There have been no subsequent submittals of these rules.

C. What is the purpose of the submitted rule revisions?

    VOCs help produce ground-level ozone and smog, which harm human
health and the environment. Section 110(a) of the CAA requires States
to submit regulations that control VOC emissions. PCAPCD Rule 212
limits emissions of VOCs from storage tanks. The June 19, 2008
amendments to Rule 212 are mostly administrative changes to improve on
the formatting and clarity of the rule. MBUAPCD Rule 427 limits
emissions of VOCs from the operation of steam drive crude oil
production wells. The majority of the October 17, 2007 amendments to
Rule 427 were editorial in nature, and the major changes made narrowed
an exemption and required documentation to claim exemption. EPA's
technical support documents (TSD) have more information about these
rules.

II. EPA's Evaluation and Action

A. How is EPA evaluating the rules?

    Generally, SIP rules must be enforceable (see section 110(a) of the
Act), must require Reasonably Available Control Technology (RACT) for
each category of sources covered by a Control Techniques Guidelines
(CTG) document

as well as each major source in nonattainment areas (see section
182(a)(2)), and must not relax existing requirements (see sections
110(l) and 193). The PCAPCD regulates an ozone nonattainment area (see
40 CFR part 81), so Rule 212 must fulfill RACT. MBUAPCD has been in
attainment for ozone since 1997. At that time, EPA determined that
MBUAPCD was implementing RACT as required and that subsequent upgrades
to RACT were not required so long as the area continued to maintain the
standard.
    Guidance and policy documents that we use to help evaluate specific
enforceability and RACT requirements consistently include the
following:
    1. Portions of the proposed post-1987 ozone and carbon monoxide
policy that concern RACT, 52 FR 45044, November 24, 1987.
    2. ``Issues Relating to VOC Regulation Cutpoints, Deficiencies, and
Deviations,'' EPA, May 25, 1988 (the Bluebook).
    3. ``Guidance Document for Correcting Common VOC & Other Rule
Deficiencies,'' EPA Region 9, August 21, 2001 (the Little Bluebook).
    4. ``Control of Volatile Organic Emissions from Storage of
Petroleum Liquids in Fixed-Roof Tanks,'' EPA-450/2-77-036, December
1977.
    5. ``Control of Volatile Organic Emissions from Petroleum Liquid
Storage in External Floating Roof Tanks,'' EPA-450/2-78-047, February
1978.
    6. ``Alternative Control Techniques Document: Volatile Organic
Liquid Storage in Floating and Fixed Roof Tanks,'' EPA-453/R-94-001,
January 1994.
    7. ``Assessment of VOC Emissions From Well Vents Associated with
Thermally Enhanced Oil Recovery,'' EPA-0-0/0-81-003, September 1981.

B. Do the rules meet the evaluation criteria?

    We believe these rules are consistent with the relevant policy and
guidance regarding enforceability, RACT, and SIP relaxations. The TSDs
have more information on our evaluation.

C. EPA Recommendations To Further Improve the Rules

    The TSD for PCAPCD Rule 212 describes additional rule revisions
that do not affect EPA's current action but are recommended for the
next time the local agency modifies the rules.

D. Public Comment and Final Action

    As authorized in section 110(k)(3) of the Act, EPA is fully
approving the submitted rules because we believe they fulfill all
relevant requirements. We do not think anyone will object to this
approval, so we are finalizing it without proposing it in advance.
However, in the Proposed Rules section of this Federal Register, we are
simultaneously proposing approval of the same submitted rules. If we
receive adverse comments by July 13, 2009, we will publish a timely
withdrawal in the Federal Register to notify the public that the direct
final approval will not take effect and we will address the comments in
a subsequent final action based on the proposal. If we do not receive
timely adverse comments, the direct final approval will be effective
without further notice on August 10, 2009. This will incorporate these
rules into the federally enforceable SIP.
    Please note that if EPA receives adverse comment on an amendment,
paragraph, or section of this rule and if that provision may be severed
from the remainder of the rule, EPA may adopt as final those provisions
of the rule that are not the subject of an adverse comment.

III. Statutory and Executive Order Reviews

    Under the Clean Air Act, the Administrator is required to approve a
SIP submission that complies with the provisions of the Act and
applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a).
Thus, in reviewing SIP submissions, EPA's role is to approve state
choices, provided that they meet the criteria of the Clean Air Act.
Accordingly, this action merely approves state law as meeting Federal
requirements and does not impose additional requirements beyond those
imposed by state law. For that reason, this action:
     Is not a ``significant regulatory action'' subject to
review by the Office of Management and Budget under Executive Order
12866 (58 FR 51735, October 4, 1993);
     Does not impose an information collection burden under the
provisions of the Paperwork Reduction Act (44 U.S.C. 3501 et seq.);
     Is certified as not having a significant economic impact
on a substantial number of small entities under the Regulatory
Flexibility Act (5 U.S.C. 601 et seq.);
     Does not contain any unfunded mandate or significantly or
uniquely affect small governments, as described in the Unfunded
Mandates Reform Act of 1995 (Pub. L. 104-4);
     Does not have Federalism implications as specified in
Executive Order 13132 (64 FR 43255, August 10, 1999);
     Is not an economically significant regulatory action based
on health or safety risks subject to Executive Order 13045 (62 FR
19885, April 23, 1997);
     Is not a significant regulatory action subject to
Executive Order 13211 (66 FR 28355, May 22, 2001);
     Is not subject to requirements of Section 12(d) of the
National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272
note) because application of those requirements would be inconsistent
with the Clean Air Act; and
     Does not provide EPA with the discretionary authority to
address, as appropriate, disproportionate human health or environmental
effects, using practicable and legally permissible methods, under
Executive Order 12898 (59 FR 7629, February 16, 1994).

In addition, this rule does not have tribal implications as specified
by Executive Order 13175 (65 FR 67249, November 9, 2000), because the
SIP is not approved to apply in Indian country located in the state,
and EPA notes that it will not impose substantial direct costs on
tribal governments or preempt tribal law.
    The Congressional Review Act, 5 U.S.C. 801 et seq., as added by the
Small Business Regulatory Enforcement Fairness Act of 1996, generally
provides that before a rule may take effect, the agency promulgating
the rule must submit a rule report, which includes a copy of the rule,
to each House of the Congress and to the Comptroller General of the
United States. EPA will submit a report containing this action and
other required information to the U.S. Senate, the U.S. House of
Representatives, and the Comptroller General of the United States prior
to publication of the rule in the Federal Register. A major rule cannot
take effect until 60 days after it is published in the Federal
Register. This action is not a ``major rule'' as defined by 5 U.S.C.
804(2).
    Under section 307(b)(1) of the Clean Air Act, petitions for
judicial review of this action must be filed in the United States Court
of Appeals for the appropriate circuit by August 10, 2009. Filing a
petition for reconsideration by the Administrator of this final rule
does not affect the finality of this action for the purposes of
judicial review nor does it extend the time within which a petition for
judicial review may be filed, and shall not postpone the effectiveness
of such rule or action. Parties with objections to this direct final
rule are encouraged to file a comment in response to the parallel
notice of proposed rulemaking for this action published in the proposed
rules section

of today's Federal Register, rather than file an immediate petition for
judicial review of this direct final rule, so that EPA can withdraw
this direct final rule and address the comment in the proposed
rulemaking. This action may not be challenged later in proceedings to
enforce its requirements (see section 307(b)(2)).

List of Subjects in 40 CFR Part 52

    Environmental protection, Air pollution control, Incorporation by
reference, Intergovernmental relations, Ozone, Reporting and
recordkeeping requirements, Volatile organic compounds.

    Dated: April 3, 2009.
Laura Yoshii,
Acting Regional Administrator, Region IX.

0
Part 52, chapter I, title 40 of the Code of Federal Regulations is
amended as follows:

PART 52--[AMENDED]

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

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

Subpart F--California

0
2. Section 52.220 is amended by adding paragraphs (c)(354)(i)(D) and
(359)(i)(C) to read as follows:

Sec.  52.220  Identification of plan.

* * * * *
    (c) * * *
    (354) * * *
    (i) * * *
    (D) Monterey Bay Unified Air Pollution Control District.
    (1) Rule 427, ``Steam Drive Crude Oil Production Wells,'' adopted
on January 16, 1980 and amended on October 17, 2007.
* * * * *
    (359) * * *
    (i) * * *
    (C) Placer County Air Pollution Control District.
    (1) Rule 212, ``Storage of Organic Liquids,'' adopted on May 24,
1977 and amended on June 19, 1997.
* * * * *
[FR Doc. E9-13481 Filed 6-10-09; 8:45 am]
BILLING CODE 6560-50-P


[Federal Register Volume 86, Number 53 (Monday, March 22, 2021)]
[Notices]
[Page 15218]
[FR Doc No: 2021-05864]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Docket No. AD21-14-000]

Resource Adequacy Developments in the Western Interconnection;
Notice of Technical Conference

    Take notice that the Federal Energy Regulatory Commission
(Commission) will convene a Commissioner-led technical conference in
the above-referenced proceeding on Wednesday, June 23, 2021, and
Thursday, June 24, 2021, from approximately 12 p.m. to 5 p.m. Eastern
time on each day. The conference will be held electronically over WebEx
and broadcast on the Commission's website.
    The purpose of this conference is to discuss resource adequacy
developments in the Western Interconnection. The Commission seeks to
engage varied regional perspectives to discuss challenges, trends, and
possible ways to continue to ensure resource adequacy in the Western
Interconnection.
    The conference will be open for the public to attend, and there is
no fee for attendance. Supplemental notices will be issued prior to the
conference with further details regarding the agenda and times,
participant registration, and the format of the conference. Information
on this technical conference will also be posted on the Calendar of
Events on the Commission's website, www.ferc.gov, prior to the event.
    The conference will be transcribed. Transcripts will be available
for a fee from Ace Reporting,<PHONE_NUMBER>.
    Commission conferences are accessible under section 508 of the
Rehabilitation Act of 1973. For accessibility accommodations, please
send an email to<EMAIL_ADDRESS>call toll-free<PHONE_NUMBER>
(voice) or<PHONE_NUMBER> (TTY), or send a fax to<PHONE_NUMBER> with
the required accommodations.
    For more information about this technical conference, please
contact Navin Shekar at<EMAIL_ADDRESS>or<PHONE_NUMBER>. For
information related to logistics, please contact Sarah McKinley at
<EMAIL_ADDRESS>or<PHONE_NUMBER>.

    Dated: March 16, 2021.
Kimberly D. Bose,
Secretary.
[FR Doc. 2021-05864 Filed 3-19-21; 8:45 am]
BILLING CODE 6717-01-P


[Federal Register Volume 83, Number 206 (Wednesday, October 24, 2018)]
[Notices]
[Pages 53630-53631]
[FR Doc No: 2018-23214]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Project No. 14795-002]

Shell Energy North America (US), LP; Notice of Application Ready
for Environmental Analysis, and Soliciting Comments, Recommendations,
Terms and Conditions, and Fishway Prescriptions

    Take notice that the following hydroelectric application has been
filed with the Commission and is available for public inspection.
    a. Type of Application: Original major license.
    b. Project No.: 14795-002.
    c. Date Filed: November 1, 2017.
    d. Applicant: Shell Energy North America (US), L.P.
    e. Name of Project: Hydro Battery Pearl Hill Pumped Storage
Project.
    f. Location: On the Columbia River and Rufus Woods Lake, near
Bridgeport, Douglas County, Washington. The project would be located on
state lands except for the lower reservoir and power generation and
pumping equipment which would be located on Rufus Woods Lake, a
reservoir operated by the U.S. Army Corps of Engineers (Corps).
    g. Filed Pursuant to: Federal Power Act, 16 U.S.C. 791(a)-825(r).
    h. Applicant Contact: Kent Watt, Shell US Hosting Company, Shell
Woodcreek Office, 150 North Dairy Ashford, Houston, TX 77079, (832)
337-1160, [email protected].
    i. FERC Contact: Ryan Hansen at<PHONE_NUMBER> or
[email protected].
    j. Deadline for Filing Comments, Recommendations, Terms and
Conditions, and Prescriptions: 60 days from the issuance date of this
notice; reply comments are due 105 days from the issuance date of this
notice.
    The Commission strongly encourages electronic filing. Please file
comments, recommendations, terms and conditions, and fishway
prescriptions using the Commission's eFiling system at http://www.ferc.gov/docs-filing/efiling.asp. Commenters can submit brief
comments up to 6,000 characters, without prior registration, using the
eComment system at http://www.ferc.gov/docs-filing/ecomment.asp. You
must include your name and contact information at the end of your
comments. For assistance, please contact FERC Online Support at
[email protected],<PHONE_NUMBER> (toll free), or (202) 502-
8659 (TTY). In lieu of electronic filing, please send a paper copy to:
Secretary, Federal Energy Regulatory Commission, 888 First Street NE,
Washington, DC 20426. The first page of any filing should include
docket number P-14795-002.
    k. This application has been accepted and is now ready for
environmental analysis.
    l. The proposed project would utilize the Corps' existing Rufus
Woods Lake Reservoir and would consist of the following new facilities:
(1) A 300-foot-diameter, 20-foot-tall lined corrugated steel tank upper
reservoir with storage capacity of 26.5 acre-feet; (2) a 3-foot-
diameter, 3,400-foot-long above-ground carbon steel penstock
transitioning to a 3-foot-diameter, 2,700-foot-long buried carbon steel
penstock; (3) a 77-foot-long, 77-foot-wide structural steel power
platform housing five 2,400 horsepower vertical turbine pumps, one 5-
megawatt twin-jet Pelton turbine and synchronous generator, and
accompanying electrical equipment; (4) five vertical turbine pump
intakes, each fitted with a 27-inch-diameter by 94-inch-long T-style
fish screen; (5) a 2,500-foot-long, 24.9-kilovolt buried/affixed
transmission line interconnecting to an existing non-project
transmission line; (6) approximately 3,847 feet of gravel project
access road; and (7) appurtenant facilities. The average annual
generation is estimated to be 24 gigawatt-hours.
    m. A copy of the application is available for review at the
Commission in the Public Reference Room or may be viewed on the
Commission's website at http://www.ferc.gov using the ``eLibrary''
link. Enter the docket number excluding the last three digits in the
docket number field to access the document. For assistance, contact
FERC Online Support. A copy is also available for inspection and
reproduction at the address in item h above.
    All filings must (1) bear in all capital letters the title
``COMMENTS'', ``REPLY COMMENTS'', ``RECOMMENDATIONS,'' ``TERMS AND
CONDITIONS,'' or ``PRESCRIPTIONS;'' (2) set forth in the heading the
name of the applicant and the project number of the application to
which the filing responds; (3) furnish the name, address, and telephone
number of the person submitting the filing; and (4) otherwise comply
with the requirements of 18 CFR 385.2001 through 385.2005. All
comments, recommendations, terms and conditions or prescriptions must
set forth their evidentiary basis and otherwise comply with the
requirements of 18 CFR 4.34(b). Agencies may obtain copies of the
application directly from the applicant. Each filing must be
accompanied by proof of service on all persons listed on the service
list prepared by the Commission in this proceeding, in accordance with
18 CFR 4.34(b), and 385.2010.
    Register online at http://www.ferc.gov/docs-filing/esubscription.asp to be notified via email of new filings and issuances
related to this or other pending projects. For assistance, contact FERC
Online Support.
    n. Public notice of the filing of the initial development
application, which has already been given, established the due date for
filing competing applications or notices of intent. Under the
Commission's regulations, any competing development application must be
filed in response to and in compliance with public notice of the
initial development application. No competing applications or notices
of intent may be filed in response to this notice.
    o. Procedural Schedule: The application will be processed according
to the following revised Hydro Licensing Schedule. Revisions to the
schedule may be made as appropriate.

------------------------------------------------------------------------
                  Milestone                           Target date
------------------------------------------------------------------------
Filing of comments, recommendations,           December 2018.
 preliminary terms and conditions, and
 preliminary fishway prescriptions.
Commission issues draft Environmental          June 2019.
 Analysis (EA).
Comments on draft EA.........................  August 2019.
Commission issues final EA...................  November 2019.
------------------------------------------------------------------------

    Dated: October 18, 2018.
Nathaniel J. Davis, Sr.,
Deputy Secretary.
[FR Doc. 2018-23214 Filed 10-23-18; 8:45 am]
 BILLING CODE 6717-01-P


[Federal Register: February 9, 2009 (Volume 74, Number 25)]
[Notices]
[Page 6402-6404]
[DOCID:fr09fe09-31]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Project No. 12775-001]

City of Spearfish, SD; Notice of Application Accepted for Filing
and Soliciting Motions To Intervene and Protests

February 2, 2009.
    Take notice that the following hydroelectric application has been
filed with the Commission and is available for public inspection.
    a. Type of Application: Major Project.
    b. Project No.: P-12775-001.
    c. Date filed: September 10, 2008.
    d. Applicant: City of Spearfish, South Dakota.
    e. Name of Project: Spearfish Hydroelectric Project.
    f. Location: On Spearfish Creek in Lawrence County, South Dakota.
The project occupies about 57.3 acres of United States lands within the
Black Hills National Forest administered by the U.S. Forest Service.
    g. Filed Pursuant to: Federal Power Act 16 U.S.C. 791(a)-825(r).
    h. Applicant Contact: Ms. Cheryl Johnson, Public Works
Administrator, City of Spearfish, 625 Fifth Street, Spearfish, SD
57783;<PHONE_NUMBER>; or e-mail at<EMAIL_ADDRESS>    i. FERC Contact: Steve Hocking at<PHONE_NUMBER>; or e-mail at
<EMAIL_ADDRESS>

    j. Deadline for filing motions to intervene and protests: April 3,
2009.
    All documents (original and eight copies) should be filed with:
Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888
First Street, NE., Washington, DC 20426.
    The Commission's Rules of Practice and Procedures require all
intervenors filing documents with the Commission to serve a copy of
that document on each person on the official service list for the
project. Further, if an intervenor files comments or documents with the
Commission relating to the merits of an issue that may affect the
responsibilities of a particular resource agency, they must also serve
a copy of the document on that resource agency.
    Motions to intervene and protests may be filed electronically via
the Internet in lieu of paper. The Commission strongly encourages
electronic filings. See 18 CFR 385.2001(a)(1)(iii) and the instructions
on the Commission's Web site (http://www.ferc.gov) under the ``e-
Filing'' link. For a simpler method of submitting text only comments,
click on ``Quick Comment''.
    k. This application has been accepted for filing, but is not ready
for environmental analysis at this time.
    l. The existing Spearfish Project consists of: (1) A 130-foot-long,
4-foot-high concrete gravity dam; (2) a 0.32-acre reservoir; (3) a
gatehouse next to the dam that contains four 2-foot-high, 4-foot-wide
steel intake gates; (4) a 4.5-mile-long, 6.5-foot-wide, 9-foot-high
concrete-lined rock tunnel; (5) a forebay pond; (6) two 1,200-foot-
long, 48-inch diameter, wood stave pipelines; (7) four 36-inch-
diameter, 54-foot-high standpipe surge towers; (8) two 4,700-foot-long,
30- to 34-inch diameter steel penstocks; (9) a reinforced concrete
powerhouse containing two Pelton turbines and two, 2,000-kilowatt
generators; and (10) appurtenant facilities.
    m. A copy of the application is available for review at the
Commission in the Public Reference Room or may be viewed on the
Commission's Web site at http://www.ferc.gov using the ``eLibrary''
link. Enter the docket number excluding the last three digits in the
docket number field to access the document. For assistance, contact
FERC Online Support at<EMAIL_ADDRESS>or toll-free at (866)
208-3676, or for TTY,<PHONE_NUMBER>. A copy is also available for
inspection and reproduction at the address in item h above.
    You may also register online at http://www.ferc.gov/docs-filing/
esubscription.asp to be notified via e-mail of new filings and
issuances related to this or other pending projects. For assistance,
contact FERC Online Support.
    n. Any qualified applicant desiring to file a competing application
must submit to the Commission, on or before the specified intervention
deadline date, a competing development application, or a notice of
intent to file such an application. Submission of a timely notice of
intent allows an interested person to file the competing development
application no later than 120 days after the specified intervention
deadline date. Applications for preliminary permits will not be
accepted in response to this notice.
    A notice of intent must specify the exact name, business address,
and telephone number of the prospective applicant, and must include an
unequivocal statement of intent to submit a development application. A
notice of intent must be served on the applicant named in this public
notice.
    Anyone may submit a protest or a motion to intervene in accordance
with the requirements of Rules of Practice and Procedures, 18 CFR
385.210, 385.211, and 385.214. In determining the appropriate action to
take, the Commission will consider all protests filed, but only those
who file a motion to intervene in accordance with the Commission's
Rules may become a party to the proceeding. Any protests or motions to
intervene must be received on or before the specified deadline date for
the particular application.
    When the application is ready for environmental analysis, the
Commission will issue a public notice requesting comments,
recommendations, terms and conditions, or prescriptions.
    All filings must: (1) Bear in all capital letters the title
``PROTEST'' or ``MOTION TO INTERVENE'', ``NOTICE OF INTENT TO FILE
COMPETING APPLICATION'', or ``COMPETING APPLICATION''; (2) set forth in
the heading the name of the applicant and the project number of the
application to which the filing responds; (3) furnish the name,
address, and telephone number of the person protesting or intervening;
and (4) otherwise comply with the requirements of 18 CFR 385.2001
through 385.2005. Agencies may obtain copies of the application
directly from the applicant. A copy of any protest or motion to
intervene must be served upon each representative of the applicant
specified in the particular application.
    o. Procedural schedule: The application will be processed according
to the following Hydro Licensing Schedule. Revisions to the schedule
will be made as appropriate.

------------------------------------------------------------------------
              Milestone                           Target date
------------------------------------------------------------------------
All stakeholders: Comments on Scoping  February 13, 2009.
 Document 1 (SD1) due.
All stakeholders: Interventions and    April 3, 2009.
 protests due.
FERC issues ready for environmental    April 3, 2009.
 analysis notice and SD2.
All Stakeholders: Terms and            June 2, 2009.
 conditions due.
All Stakeholders: Reply comments due.  July 17, 2009.
FERC issues single environmental       August 3, 2009.
 assessment (EA) (no draft EA).
All stakeholders: EA comments due....  September 2, 2009.
All stakeholders: Modified terms and   November 2, 2009.
 conditions due.
------------------------------------------------------------------------

Kimberly D. Bose,
Secretary.
[FR Doc. E9-2604 Filed 2-6-09; 8:45 am]

BILLING CODE 6717-01-P


[Federal Register Volume 76, Number 72 (Thursday, April 14, 2011)]
[Notices]
[Page 20971]
[FR Doc No: 2011-9064]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Docket No. PR10-120-001]

Eagle Rock Desoto Pipeline, L.P.; Notice of Filing

    Take notice that on April 7, 2011, Eagle Rock Desoto Pipeline, L.P.
filed a revised Statement of Operating Conditions to comply with an
unpublished delegated letter order issued on November 12, 2010.
    Any person desiring to participate in this rate filing must file in
accordance with Rules 211 and 214 of the Commission's Rules of Practice
and Procedure (18 CFR 385.211 and 385.214). Protests will be considered
by the Commission in determining the appropriate action to be taken,
but will not serve to make protestants parties to the proceeding. Any
person wishing to become a party must file a notice of intervention or
motion to intervene, as appropriate. Such notices, motions, or protests
must be filed on or before the date as indicated below. Anyone filing
an intervention or protest must serve a copy of that document on the
Applicant. Anyone filing an intervention or protest on or before the
intervention or protest date need not serve motions to intervene or
protests on persons other than the Applicant.
    The Commission encourages electronic submission of protests and
interventions in lieu of paper using the ``eFiling'' link at http://www.ferc.gov. Persons unable to file electronically should submit an
original and 7 copies of the protest or intervention to the Federal
Energy Regulatory Commission, 888 First Street, NE., Washington, DC
20426.
    This filing is accessible on-line at http://www.ferc.gov, using the
``eLibrary'' link and is available for review in the Commission's
Public Reference Room in Washington, DC. There is an ``eSubscription''
link on the Web site that enables subscribers to receive e-mail
notification when a document is added to a subscribed docket(s). For
assistance with any FERC Online service, please e-mail
<EMAIL_ADDRESS>or call<PHONE_NUMBER> (toll free). For
TTY, call<PHONE_NUMBER>.
    Comment Date: 5 p.m. Eastern Time on Tuesday, April 19, 2011.

    Dated: April 8, 2011.
Kimberly D. Bose,
Secretary.
[FR Doc. 2011-9064 Filed 4-13-11; 8:45 am]
BILLING CODE 6717-01-P