[Federal Register Volume 76, Number 75 (Tuesday, April 19, 2011)]
[Proposed Rules]
[Pages 21820-21822]
[FR Doc No: 2011-9408]

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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 39

[Docket No. FAA-2011-0381; Directorate Identifier 2010-NM-203-AD]
RIN 2120-AA64

Airworthiness Directives; Bombardier, Inc. Model DHC-8-400 Series
Airplanes

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Notice of proposed rulemaking (NPRM).

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

SUMMARY: We propose to adopt a new airworthiness directive (AD) for the
products listed above. This proposed AD results from mandatory
continuing airworthiness information (MCAI) originated by an aviation
authority of another country to identify and correct

an unsafe condition on an aviation product. The MCAI describes the
unsafe condition as:

    Several reports have been received on failures of the main
landing gear (MLG) stabilizer extension springs. A landing gear
audit has confirmed that the MLG may not lock in the down-lock
position with the absence of both MLG stabilizer extension springs.
The loss of the locking mechanism could result in the collapse of
the main landing gear.
* * * * *
The proposed AD would require actions that are intended to address the
unsafe condition described in the MCAI.

DATES: We must receive comments on this proposed AD by June 3, 2011.

ADDRESSES: You may send comments by any of the following methods:
     Federal eRulemaking Portal: Go to http://www.regulations.gov. Follow the instructions for submitting comments.
     Fax:<PHONE_NUMBER>.
     Mail: U.S. Department of Transportation, Docket
Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New
Jersey Avenue, SE., Washington, DC 20590.
     Hand Delivery: U.S. Department of Transportation, Docket
Operations, M-30, West Building Ground Floor, Room W12-40, 1200 New
Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m., Monday
through Friday, except Federal holidays.
    For service information identified in this proposed AD, contact
Bombardier, Inc., Q-Series Technical Help Desk, 123 Garratt Boulevard,
Toronto, Ontario M3K 1Y5, Canada; telephone<PHONE_NUMBER>; fax 416-375-
4539; e-mail<EMAIL_ADDRESS>Internet http://www.bombardier.com. You may review copies of the referenced service
information at the FAA, Transport Airplane Directorate, 1601 Lind
Avenue, SW., Renton, Washington. For information on the availability of
this material at the FAA, call<PHONE_NUMBER>.

Examining the AD Docket

    You may examine the AD docket on the Internet at http://www.regulations.gov; or in person at the Docket Operations office
between 9 a.m. and 5 p.m., Monday through Friday, except Federal
holidays. The AD docket contains this proposed AD, the regulatory
evaluation, any comments received, and other information. The street
address for the Docket Operations office (telephone<PHONE_NUMBER>) is
in the ADDRESSES section. Comments will be available in the AD docket
shortly after receipt.

FOR FURTHER INFORMATION CONTACT: Fabio Buttitta, Aerospace Engineer,
Airframe and Mechanical Systems Branch, ANE-171, FAA, New York Aircraft
Certification Office, 1600 Stewart Avenue, Suite 410, Westbury, New
York 11590; telephone<PHONE_NUMBER>; fax<PHONE_NUMBER>.

SUPPLEMENTARY INFORMATION:

Comments Invited

    We invite you to send any written relevant data, views, or
arguments about this proposed AD. Send your comments to an address
listed under the ADDRESSES section. Include ``Docket No. FAA-2011-0381;
Directorate Identifier 2010-NM-203-AD'' at the beginning of your
comments. We specifically invite comments on the overall regulatory,
economic, environmental, and energy aspects of this proposed AD. We
will consider all comments received by the closing date and may amend
this proposed AD based on those comments.
    We will post all comments we receive, without change, to http://www.regulations.gov, including any personal information you provide. We
will also post a report summarizing each substantive verbal contact we
receive about this proposed AD.

Discussion

    Transport Canada Civil Aviation (TCCA), which is the aviation
authority for Canada, has issued Canadian Airworthiness Directive CF-
2010-22, dated July 20, 2010 (referred to after this as ``the MCAI''),
to correct an unsafe condition for the specified products. The MCAI
states:

    Several reports have been received on failures of the main
landing gear (MLG) stabilizer extension springs. A landing gear
audit has confirmed that the MLG may not lock in the down-lock
position with the absence of both MLG stabilizer extension springs.
The loss of the locking mechanism could result in the collapse of
the main landing gear.
    This [TCCA] directive is to mandate the incorporation of a new
maintenance task for the MLG stabilizer extension springs.

You may obtain further information by examining the MCAI in the AD
docket.

Relevant Service Information

    Bombardier has issued Temporary Revision MRB-45, dated October 6,
2009 to Section 1-32, Systems/Powerplant Maintenance Program of Part 1
of the Maintenance Review Board (MRB) Report of the Bombardier Q400
Dash 8 Maintenance Requirements Manual, PSM 1-84-7. The actions
described in this service information are intended to correct the
unsafe condition identified in the MCAI.

FAA's Determination and Requirements of This Proposed AD

    This product has been approved by the aviation authority of another
country, and is approved for operation in the United States. Pursuant
to our bilateral agreement with the State of Design Authority, we have
been notified of the unsafe condition described in the MCAI and service
information referenced above. We are proposing this AD because we
evaluated all pertinent information and determined an unsafe condition
exists and is likely to exist or develop on other products of the same
type design.

Differences Between This AD and the MCAI or Service Information

    We have reviewed the MCAI and related service information and, in
general, agree with their substance. But we might have found it
necessary to use different words from those in the MCAI to ensure the
AD is clear for U.S. operators and is enforceable. In making these
changes, we do not intend to differ substantively from the information
provided in the MCAI and related service information.
    We might also have proposed different actions in this AD from those
in the MCAI in order to follow FAA policies. Any such differences are
highlighted in a Note within the proposed AD.

Costs of Compliance

    Based on the service information, we estimate that this proposed AD
would affect about 65 products of U.S. registry. We also estimate that
it would take about 1 work-hour per product to comply with the basic
requirements of this proposed AD. The average labor rate is $85 per
work-hour. Based on these figures, we estimate the cost of the proposed
AD on U.S. operators to be $5,525, or $85 per product.

Authority for This Rulemaking

    Title 49 of the United States Code specifies the FAA's authority to
issue rules on aviation safety. Subtitle I, section 106, describes the
authority of the FAA Administrator. ``Subtitle VII: Aviation
Programs,'' describes in more detail the scope of the Agency's
authority.
    We are issuing this rulemaking under the authority described in
``Subtitle VII, Part A, Subpart III, Section 44701: General
requirements.'' Under that section, Congress charges the FAA with
promoting safe flight of civil aircraft in air commerce by prescribing
regulations for practices, methods, and procedures the Administrator
finds necessary for safety in air commerce. This regulation

is within the scope of that authority because it addresses an unsafe
condition that is likely to exist or develop on products identified in
this rulemaking action.

Regulatory Findings

    We determined that this proposed AD would not have federalism
implications under Executive Order 13132. This proposed AD would not
have a substantial direct effect 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.
    For the reasons discussed above, I certify this proposed
regulation:
    1. Is not a ``significant regulatory action'' under Executive Order
12866;
    2. Is not a ``significant rule'' under the DOT Regulatory Policies
and Procedures (44 FR 11034, February 26, 1979); and
    3. Will not have a significant economic impact, positive or
negative, on a substantial number of small entities under the criteria
of the Regulatory Flexibility Act.
    We prepared a regulatory evaluation of the estimated costs to
comply with this proposed AD and placed it in the AD docket.

List of Subjects in 14 CFR Part 39

    Air transportation, Aircraft, Aviation safety, Incorporation by
reference, Safety.

The Proposed Amendment

    Accordingly, under the authority delegated to me by the
Administrator, the FAA proposes to amend 14 CFR part 39 as follows:

PART 39--AIRWORTHINESS DIRECTIVES

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

    Authority:  49 U.S.C. 106(g), 40113, 44701.

Sec.  39.13  [Amended]

    2. The FAA amends Sec.  39.13 by adding the following new AD:

Bombardier, Inc.: Docket No. FAA-2011-0381; Directorate Identifier
2010-NM-203-AD.

Comments Due Date

    (a) We must receive comments by June 3, 2011.

Affected ADs

    (b) None.

Applicability

    (c) This AD applies to Bombardier, Inc. Model DHC-8-400, -401,
and -402 airplanes, certificated in any category, serial numbers
4001, 4003 and subsequent.

Subject

    (d) Air Transport Association (ATA) of America Code 32: Landing
Gear.

Reason

    (e) The mandatory continuing airworthiness information (MCAI)
states:
    Several reports have been received on failures of the main
landing gear (MLG) stabilizer extension springs. A landing gear
audit has confirmed that the MLG may not lock in the down-lock
position with the absence of both MLG stabilizer extension springs.
The loss of the locking mechanism could result in the collapse of
the main landing gear.
* * * * *

Compliance

    (f) You are responsible for having the actions required by this
AD performed within the compliance times specified, unless the
actions have already been done.

Actions

    (g) Within 30 days after the effective date of this AD, revise
the maintenance program by incorporating Task 320100-213 as
specified in Bombardier Temporary Revision MRB-45, dated October 6,
2009, to Section 1-32, Systems/Powerplant Maintenance Program, of
Part 1 of the Maintenance Review Board Report of the Bombardier Q400
Dash 8 Maintenance Requirements Manual, PSM 1-84-7. The initial
compliance time for Task 320100-213 is within 600 flight hours after
the effective date of this AD.

No Alternative Actions or Intervals

    (h) After accomplishing the revision required by paragraph (g)
of this AD, no alternative actions (e.g., inspections) or intervals
may be used unless the actions or intervals are approved as an
alternative method of compliance (AMOC) in accordance with the
procedures specified in paragraph (i) of this AD.

FAA AD Differences

    Note 1:  This AD differs from the MCAI and/or service
information as follows: No differences.

Other FAA AD Provisions

    (i) The following provisions also apply to this AD:
    (1) Alternative Methods of Compliance (AMOCs): The Manager, New
York ACO, ANE-170, FAA, FAA, has the authority to approve AMOCs for
this AD, if requested using the procedures found in 14 CFR 39.19. In
accordance with 14 CFR 39.19, send your request to your principal
inspector or local Flight Standards District Office, as appropriate.
If sending information directly to the ACO, send it to ATTN: Program
Manager, Continuing Operational Safety, FAA, New York ACO, 1600
Stewart Avenue, Suite 410, Westbury, New York 11590; telephone 516-
228-7300; fax<PHONE_NUMBER>. Before using any approved AMOC, notify
your appropriate principal inspector, or lacking a principal
inspector, the manager of the local flight standards district
office/certificate holding district office. The AMOC approval letter
must specifically reference this AD.
    (2) Airworthy Product: For any requirement in this AD to obtain
corrective actions from a manufacturer or other source, use these
actions if they are FAA-approved. Corrective actions are considered
FAA-approved if they are approved by the State of Design Authority
(or their delegated agent). You are required to assure the product
is airworthy before it is returned to service.

Related Information

    (j) Refer to MCAI Transport Canada Civil Aviation (TCCA)
Airworthiness Directive CF-2010-22, dated July 20, 2010; and
Bombardier Temporary Revision MRB-45, dated October 6, 2009, to
Section 1-32, Systems/Powerplant Maintenance Program, of Part 1 of
the Maintenance Review Board Report of the Bombardier Q400 Dash 8
Maintenance Requirements Manual, PSM 1-84-7; for related
information.

    Issued in Renton, Washington, on April 12, 2011.
Ali Bahrami,
Manager, Transport Airplane Directorate, Aircraft Certification
Service.
[FR Doc. 2011-9408 Filed 4-18-11; 8:45 am]
BILLING CODE 4910-13-P


[Federal Register Volume 86, Number 243 (Wednesday, December 22, 2021)]
[Notices]
[Page 72594]
[FR Doc No: 2021-27738]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

Combined Notice of Filings

    Take notice that the Commission has received the following Natural
Gas Pipeline Rate and Refund Report filings:

Filings Instituting Proceedings

    Docket Numbers: RP22-416-000.
    Applicants: ANR Pipeline Company.
    Description: Sec.  4(d) Rate Filing: ANR--Citadel Energy Negotiated
Rate Agreement No. 136886 to be effective 12/15/2021.
    Filed Date: 12/15/21.
    Accession Number: 20211215-5092.
    Comment Date: 5 p.m. ET 12/27/21.

    Docket Numbers: RP22-417-000.
    Applicants: Tennessee Gas Pipeline Company, L.L.C.
    Description: Sec.  4(d) Rate Filing: TGP PCG Pooling to be
effective 1/17/2022.
    Filed Date: 12/15/21.
    Accession Number: 20211215-5172.
    Comment Date: 5 p.m. ET 12/27/21.

    Docket Numbers: RP22-418-000.
    Applicants: Columbia Gulf Transmission, LLC.
    Description: Sec.  4(d) Rate Filing: LAXP Tariff Implementation,
Waiver and Request for Shortened Comment Period to be effective 1/7/
2022.
    Filed Date: 12/15/21.
    Accession Number: 20211215-5187.
    Comment Date: 5 p.m. ET 12/27/21.

    Docket Numbers: RP22-419-000.
    Applicants: Total Peaking Services, L. L. C.
    Description: Compliance filing: TPS Order No. 587-Z Compliance
Filing Changes to be effective 6/1/2022.
    Filed Date: 12/15/21.
    Accession Number: 20211215-5218.
    Comment Date: 5 p.m. ET 12/27/21.

    Docket Numbers: RP22-420-000.
    Applicants: Portland Natural Gas Transmission System.
    Description: Compliance filing: 2021 Fuel Mechanism Report to be
effective N/A.
    Filed Date: 12/15/21.
    Accession Number: 20211215-5261.
    Comment Date: 5 p.m. ET 12/27/21.

    Docket Numbers: RP22-421-000.
    Applicants: NEXUS Gas Transmission, LLC.
    Description: Sec.  4(d) Rate Filing: Negotiated Rates--CNX to
Direct Energy 962064 to be effective 12/17/2021.
    Filed Date: 12/16/21.
    Accession Number: 20211216-5090.
    Comment Date: 5 p.m. ET 12/28/21.

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

    Dated: December 16, 2021.
Debbie-Anne A. Reese,
Deputy Secretary.
[FR Doc. 2021-27738 Filed 12-21-21; 8:45 am]
BILLING CODE 6717-01-P


[Federal Register Volume 83, Number 195 (Tuesday, October 9, 2018)]
[Notices]
[Page 50672]
[FR Doc No: 2018-21791]

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

DEPARTMENT OF HOMELAND SECURITY

Federal Emergency Management Agency

[Internal Agency Docket No. FEMA-3385-EM; Docket ID FEMA-2018-0001]

Florida; Amendment No. 4 to Notice of an Emergency Declaration

AGENCY: Federal Emergency Management Agency, DHS.

ACTION: Notice.

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

SUMMARY: This notice amends the notice of an emergency declaration for
the State of Florida (FEMA-3385-EM), dated September 5, 2017, and
related determinations.

DATES: The change occurred on August 29, 2018.

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

SUPPLEMENTARY INFORMATION: The Federal Emergency Management Agency
(FEMA) hereby gives notice that pursuant to the authority vested in the
Administrator, under Executive Order 12148, as amended, Thomas J.
McCool, of FEMA is appointed to act as the Federal Coordinating Officer
for this emergency.
    This action terminates the appointment of Allan Jarvis as Federal
Coordinating Officer for this emergency.

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

Brock Long,
Administrator, Federal Emergency Management Agency.
[FR Doc. 2018-21791 Filed 10-5-18; 8:45 am]
 BILLING CODE 9111-11-P


[Federal Register: April 2, 2007 (Volume 72, Number 62)]
[Notices]
[Page 15682-15683]
[DOCID:fr02ap07-55]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Project No. 6641-067]

American Municipal Power--Ohio, Inc., City of Marion, Kentucky
and Smithland Hydroelectric Partners; Notice of Availability of
Environmental Assessment

March 27, 2007.
    In accordance with the National Environmental Policy Act of 1969
and the Federal Energy Regulatory Commission (Commission or FERC)
regulations contained in the Code of Federal Regulations (CFR) (18 CFR
Part 380 [FERC Order No. 486, 52 FR 47897]), the Office of Energy
Projects staff (staff) reviewed a proposal to amend the design
authorized by the license for the Smithland Hydroelectric Project, to
be located the U.S. Army Corps of Engineers' Smithland Locks and Dam on
the Ohio River in Livingston County, Kentucky, and prepared an
environmental assessment (EA) for the proposed amendment of the project
license. In this EA, staff analyzes the potential environmental effects
of replacing the authorized 170 small generator units with three
conventional turbine and generator units and concludes that the
amendment would not constitute a major federal action significantly
affecting the quality of the human environment.
    A copy of the EA is attached to a Commission order titled ``Order
Amending License'', issued March 22, 2007 and is available for review
at the Commission in the Public Reference

Room, located at 888 First Street, NE., Room 2A, Washington, DC 20426,
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, call toll-free 1-866-208-3676 or e-mail
<EMAIL_ADDRESS>For TTY, call<PHONE_NUMBER>.

Philis J. Posey,
Acting Secretary.
[FR Doc. E7-6001 Filed 3-30-07; 8:45 am]

BILLING CODE 6717-01-P


[Federal Register Volume 81, Number 175 (Friday, September 9, 2016)]
[Notices]
[Page 62550]
[FR Doc No: 2016-21706]

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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

Notice of Intent To Rule on Disposal of Aeronautical Property at
Bowman Field Airport Louisville, KY (LOU)

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Notice.

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

SUMMARY: The Federal Aviation Administration is requesting public
comment on a request by the Louisville Regional Airport Authority
(LRAA), to release 0.11 acres of land at Bowman Field Airport from
federal obligations. This release will be retroactive for a project
that was necessary for the construction of Interstate Highway 64.The
request consists of the following:
    A 0.11 acre of parcel of airport property was condemned by the
Commonwealth of Kentucky in 1959. The court awarded this property to
the State of Kentucky via quitclaim deed. This property is bounded by
Beargrass Creek to the north, Cannons Lane to the east and Old Cannons
Lane to the West. The current use of this property is as a small
segment of Interstate Highway 64.This property was part of the 291.95
acre parcel conveyed from the United States of America with obligations
to the Louisville And Jefferson County Air Board (now The Louisville
Regional Airport Authority) on February 2, 1948. This request will
release this property from federal obligations. This action is taken
under the provisions of 49 U.S.C. 47107(h)(2).

DATES: Comments must be received on or before October 11, 2016.

ADDRESSES: Comments on this notice may be mailed or delivered in
triplicate to the FAA at the following address: Memphis Airports
District Office, Attn: Jamal Stovall, Community Planner, 2600 Thousand
Oaks Boulevard, Suite 2250, Memphis, TN 38118.
    In addition, one copy of any comments submitted to the FAA must be
mailed or delivered to Mr. Charles T. Miller, Executive Director,
Louisville Regional Airport Authority at the following address: 700
Administration Drive, Louisville, KY 40209.

FOR FURTHER INFORMATION CONTACT: Mr. Jamal Stovall, Community Planner,
Federal Aviation Administration, Memphis Airports District Office,
2600, Thousand Oaks Boulevard, Suite 2250, Memphis, TN 38118-2482. The
application may be reviewed in person at this same location, by
appointment.

SUPPLEMENTARY INFORMATION: The FAA proposes to rule and invites public
comment on the request to release property for disposal at Bowman Field
Airport, 2815 Taylorsville Rd. Louisville, KY 40205, under the
provisions of 49 U.S.C. 47107(h)(2). The FAA determined that the
request to release property at Bowman Field Airport (LOU) submitted by
the Sponsor meets the procedural requirements of the Federal Aviation
Administration and the release of the property does not and will not
impact future aviation needs at the airport. The FAA may approve the
request, in whole or in part, no sooner than thirty days after the
publication of this notice.
    The following is a brief overview of the request:
    The Louisville Regional Airport Authority is releasing
approximately 0.11 acres of airport property. This parcel was conveyed
from the United States of America to the Louisville And Jefferson
County Air Board (now The Louisville Regional Airport Authority) in
1948 with obligations. This release will be retroactive for a project
that was necessary for the construction of Interstate Highway 64. This
request will release this property from federal obligations.
    Any person may inspect the request in person at the FAA office
listed above under FOR FURTHER INFORMATION CONTACT.
    In addition, any person may, upon request, inspect the request,
notice and other documents germane to the request in person at the
Louisville Regional Airport Authority.

    Issued in Memphis, Tennessee, on August 30, 2016.
Tommy L. Dupree,
Assistant Manager, Memphis Airports District Office, Southern Region.
[FR Doc. 2016-21706 Filed 9-8-16; 8:45 am]
 BILLING CODE 4910-13-P


[Federal Register: June 13, 2007 (Volume 72, Number 113)]
[Notices]
[Page 32633]
[DOCID:fr13jn07-46]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Docket No. EF07-2021-000]

U.S. Department of Energy; Bonneville Power Administration;
Notice of Filing

June 6, 2007.
    Take notice that on May 22, 2007, U.S. Department of Energy,
Bonneville Power Administration (Bonneville), tendered for filing
proposed rate adjustments for its 2008 Transmission and Ancillary
Services Rates pursuant to sections 7(a)(2) and 7(i)(6) of the Pacific
Northwest Electric Power Planning and Conservation Act, 16 U.S.C.
839e(a)(2) and 839e(i)(6). Pursuant to Commission regulations sections
300.10 and 300.21 (18 CFR 300.10 and 300.21), Bonneville seeks interim
approval of the proposed transmission and ancillary services effective
October 1, 2007, followed by final confirmation and approval.
Bonneville also seeks a finding by the Commission that the proposed
rates satisfy the Commission's comparability standards applicable to
non-public utilities pursuant to the reciprocity conditions of Order
No. 888, FERC Stats. & Regs. ] 31,760 et seq.
    Any person desiring to intervene or to protest this filing must
file in accordance with Rules 211 and 214 of the Commission's Rules of
Practice and Procedure (18 CFR 385.211, 385.214). Protests will be
considered by the Commission in determining the appropriate action to
be taken, but will not serve to make protestants parties to the
proceeding. Any person wishing to become a party must file a notice of
intervention or motion to intervene, as appropriate. Such notices,
motions, or protests must be filed on or before the comment date.
Anyone filing a motion to intervene or protest must serve a copy of
that document on the Applicant and all the parties in this proceeding.
    The Commission encourages electronic submission of protests and
interventions in lieu of paper using the ``eFiling'' link at http://www.ferc.gov.
 Persons unable to file electronically should submit an

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

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

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

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

BILLING CODE 6717-01-P


The Policy Group Meeting with Water Permits Division, Office of Wastewater Management February 10, 2004 Attendees Deborah Nagle, Water Permits Division, OWM Christian Richter, The Policy Group B. J. Mason, Mid Atlantic Finishing Corporation J. L. Lindstedt, Artistic Plating Bill Wiggins, Automation Plating J. Kelly Lowry, ( illegible) Bill Saas, Yaskem, Inc. David Jacobs, Northwussors Plating Joelie Zak, Scientific Control Labs Mike Kelly, Asko Processing, Inc. David S. Marsh, Marsh Plating Corp. Jeff Hannapel, The Policy Group Elaine Brenner, Water Permits Division, OWM Jan Pickrel, Water Permits Division, OWM Greg Schaner, Water Permits Division, OWM Purpose and Summary of Meeting The Policy Group met with Water Permits Division staff to outline its priorities for the Pretreatment Streamlining Rule. The following summarizes the discussion:

  Sampling for Pollutants Not Present   Policy Group members consider this a major priority. One member discusses the rising costs of sampling in Region 5 and the need to provide some reasonable relief from these costs.

  Non Significant CIU   Policy Group indicated that if EPA chooses to finalize the 100 gpd threshold, it will provide no streamlining for their finishing members. They would prefer that EPA not go forward with the 100 gpd threshold, in favor of collecting more data on a more significant cutoff. They suggested instead that EPA adopt the 0.01% approach that NACWA has supported.

  Many of the industry's arguments in support of streamlining has to do with the decreased profit margins faced by their operations. Attendees also mentioned the fact that POTWs are increasing their sewer rates despite their water conservation efforts.

  Equivalent mass limits   Policy Group and members indicated that they favored concentration limits. They indicated that when water consumption is reduced, they are still able to reduce pollutant loadings because of the chemical precipitation treatment that they have installed.


LATITUDE/ LONGITUDE DATA STANDARD Standard No.: 1 19939: 2 Version 2  FINAL DRAFT July 26, 2005 This data standard is produced by the Environmental Data Standards Council ( EDSC)

The Environmental Data Standards Council ( EDSC) is a partnership among US EPA, States and Tribal partners to promote the efficient sharing of environmental information through the development and adoption of data standards. More information about the EDSC is available at www. envdatastandards. net. Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Final Draft July 26, 2005 Page 2 Foreword The Environmental Data Standards Council ( EDSC) identifies, prioritizes, and pursues the creation of data standards for those areas where information exchange standards will provide the most value in achieving environmental results. The Council involves Tribes and Tribal Nations, state and federal agencies in the development of the standards and then provides the draft materials for general review. Business groups, non governmental organizations, and other interested parties may then provide input and comment for Council consideration and standard finalization. Draft and final standards are available at http:// www. envdatastandards. net.

1.0 INTRODUCTION The Latitude/ Longitude Data Standard is a set of data elements that can be used for recording horizontal and vertical coordinates and associated metadata that define a point on the earth. The latitude/ longitude data standard establishes the requirements for documenting latitude and longitude coordinates and related method, accuracy, and description data for places of interest to the Environmental Protection Agency ( EPA). Places include facilities, sites, monitoring stations, observation points, and other features regulated or tracked under Federal environmental programs within the jurisdiction of the EPA.

1.1 Scope The purpose of the standard is to provide a common set of data elements to specify a point by latitude/ longitude. This standard describes data elements and data groupings that are used to exchange Latitude/ Longitude data and information.

1.2 References to other data standards This standard relies on two other standards to make it complete and provide the necessary support. As such, users should reference the normative standards listed below and consider them integral to the Latitude/ Longitude Standard. These include:

  Representation of Date and Time [ Final Draft Version 2.0] Data Standard   Measure [ Final Draft Version 1.0] Data Standard   QA/ QC [ Final Draft Version 1.0] Data Standard 1.3 Terms and Definitions None.

1.4 Implementation Users are encouraged to use the XML registry housed on the Exchange Network Web site to download schema components for the construction of XML schema flows ( http:// www. exchangenetwork. net).

1.5 Document Structure The structure of this document is briefly described below: a. Section 2.0 Latitude/ Longitude Diagram illustrates the principal data groupings contained within this standard.

b. Section 3.0 Latitude/ Longitude Data Standard Table provides information on the high level, intermediate and elemental Latitude/ Longitude data groupings. Where applicable, for each level of this data standard a definition, XML tag, note( s), example list of values and format are provided. The format column may include the required number of characters for the associated Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Final Draft July 26, 2005 Page 3 data element, where " A" specifies alphanumeric and " N" designates numeric and date and time reference the Representation of Date and Time Standard.

c. Data Standard Numbering: For purposes of clarity and to enhance understanding of data standard hierarchy and relationships, each data group is numerically classified from the primary to the data element level.

d. Code and Identifier metadata: Based on the business need, additional metadata may be required to sufficiently describe an identifier or a code. A note regarding this additional metadata is included in the notes column for identifier and code elements. Additional metadata for identifiers may include:

° Identifier Context, which identifies the source or data system that created or defined the identifier Additional metadata for codes may include:

° Code List Identifier, which is a standardized reference to the context or source of the set of codes ° Code List Version Identifier, which identifies the particular version of the set of codes.

° Code List Version Agency Identifier, which identifies the agency responsible for maintaining the set of codes ° Code List Name, which describes the corresponding name for which the code represents e. Appendix A, Longitude/ Latitude Data Structure Diagram illustrates the hierarchical classification of the contact information data standard. This diagram enables business and technical users of this standard to quickly understand its general content and complexity. Appendices " B" through " I" provide the lists of permissible values for the designated data elements. The tables present code, name and value meaning for each permitted value. Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Final Draft July 26, 2005 Page 4 2.0 LATITUDE/ LONGITUDE DIAGRAM This diagram exhibits the major data groups associated with the Latitude/ Longitude Data Standard.

Latitude/ Longitude Data Standard Mandatory Latitude/ Longitude Optional Latitude/ Longitude Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Final Draft July 26, 2005 Page 5 3.0 LATITUDE/ LOGITUDE DATA STANDARDS TABLE 1.0 Mandatory Latitude/ Longitude Definition: Mandatory Information needed for recording coordinates of a location on the earth Relationship: None Identified.

Notes: None.

XML Tag: MandatoryLatLong Name Definition Notes Format XML tags 1.1 Latitude Measure The measure of the angular distance on a meridian north or south of the equator. A LatitudeMeasu re 1.2 Longitude Measure The measure of the angular distance on a meridian east or west of the prime meridian. A LongitudeMea sure 1.3 Source Map Scale Number The number that represents the proportional distance on the ground for one unit of measure on the map or photo. A SourceMapSc aleNumber 1.4 Horizontal Accuracy Measure The measure of the accuracy of the latitude and longitude coordinates. Refer to the Measure [ DRAFT]

Data Standard.

The following items are needed:

Measure Value Measure Unit Code Measure QA/ QC A HorizontalAcc uracyMeasure 1.5 Horizontal Collection Method Code The code that represents the method used to determine the latitude and longitude coordinates for a point on the earth. List of Permitted Values:

[ 38 values specified   See appendix B]

Note: Based on the business need,

additional metadata may be required to sufficiently describe a code. This additional metadata is listed in the Introduction 1.5. d. A HorizontalColl ectionMethod Code Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Final Draft July 26, 2005 Page 6 Name Definition Notes Format XML tags 1.6 Horizontal Collection Method Name The text that describes the method used to determine the latitude and longitude coordinates for a point on the earth. List of Permitted Values:

[ 38 values specified   See appendix B] A HorizontalColl ectionMethod Text 1.7 Geographic Reference Point Code The code that represents the place for which geographic coordinates were established. List of Permitted Values:

[ 20 values specified   See appendix C]

Based on the business need,

additional metadata may be required to sufficiently describe a code. This additional metadata is listed in the Introduction section1.5. d. A GeographicRe ferencePointC ode 1.8 Geographic Reference Point Name The text that identifies the place for which geographic coordinates were established. List of Permitted Values:

[ 8 values specified   See appendix C] A GeographicRe ferencePointT ext 1.9 Horizontal Reference Datum Code The code that represents the reference datum used in determining latitude and longitude coordinates. List of Permitted Values:

[ 3 values specified   See appendix D]

Based on the business need,

additional metadata may be required to sufficiently describe a code. This additional metadata is listed in the Introduction section 1.5. d. A HorizontalRef erenceDatum Code 1.10 Horizontal Reference Datum Name The name that describes the reference datum used in determining latitude and longitude coordinates. List of Permitted Values:

[ 3 values specified   See appendix D] A HorizontalRef erenceDatum Name Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Final Draft July 26, 2005 Page 7 2.0 Optional Latitude/ Longitude Definition: Optional data needed to address coordinates of a location on the earth Relationship: None Identified.

Notes: None.

XML Tag: OptionalLatLong Name Definition Notes Format XML tags 2.1 Data Collection Date The calendar date when data were collected. Reference the Representation of Date and Time Data Standard YYYYMM DD DataCollection Date 2.2 Location Comments Text The text that provides additional information about the geographic coordinates. A LocationCom mentsText 2.3 Vertical Measure The measure of elevation ( i. e., the altitude), above or below a reference datum. Reference the Measure [ Draft]

Data Standard.

The following items are needed:

Measure Value,

Measure Unit Code,

Measure QA/ QC. A VerticalMeasu re 2.4 Vertical Collection Method Code The code that represents the process used to verify the latitude and longitude coordinates. List of Permitted Values:

[ 14 values specified   See appendix E]

Based on the business need,

additional metadata may be required to sufficiently describe a code. This additional metadata is listed in the Introduction section 1.5. d. A VerificationMe thodCode 2.5 Vertical Collection Method Name The text that describes the method used to collect the vertical measure ( i. e., the altitude) of a reference point. List of Permitted Values:

[ 14 values specified   See appendix E] A VerticalCollect ionMethodTex t Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Final Draft July 26, 2005 Page 8 Name Definition Notes Format XML tags 2.6 Vertical Reference Datum Code The code that represents the reference datum used to determine the vertical measure ( i. e., the altitude). List of Permitted Values:

[ 4 values specified   See appendix F]

Based on the business need,

additional metadata may be required to sufficiently describe a code. This additional metadata is listed in the Introduction section 1.5. d. A VerticalRefere nceDatumCod e 2.7 Vertical Reference Datum Name The name of the reference datum used to determine the vertical measure ( i. e., the altitude). List of Permitted Values:

[ 4 values specified   See appendix F] A) VerticalRefere nceDatumNa me 2.8 Verification Method Code The code that represents the process used to verify the latitude and longitude coordinates. Permitted Values:

[ 14 values specified   See appendix G]

Based on the business need,

additional metadata may be required to sufficiently describe a code. This additional metadata is listed in the Introduction section 1.5. d. A VerificationMe thodCode 2.9 Verification Method Name The text that describes the process used to verify the latitude and longitude coordinates. List of Permitted Values:

[ 14 values specified   See appendix G] A VerificationMe thodText Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Final Draft July 26, 2005 Page 9 Name Definition Notes Format XML tags 2.10 Coordinate Data Source Code The code that represents the party responsible for providing the latitude and longitude coordinates. List of Permitted Values:

[ 79 values specified   See appendix H]

Based on the business need,

additional metadata may be required to sufficiently describe a code. This additional metadata is listed in the Introduction section 1.5. d. A( 3) CoordinateD ataSourceC ode 2.11 Coordinate Data Source Name The name of the party responsible for providing the latitude and longitude coordinates. List of Permitted Values:

[ 79 values specified   See appendix H] A( 35) CoordinateD ataSourceN ame 2.12 Geometric Type Code The code that represents the geometric entity represented by one point or a sequence of latitude and longitude points. List of Permitted Values:

[ 5 values specified   See appendix I]

Based on the business need,

additional metadata may be required to sufficiently describe a code. This additional metadata is listed in the Introduction section 1.5. d. A( 3) GeometricTy peCode 2.13 Geometric Type Name The name that identifies the geometric entity represented by one point or a sequence of latitude and longitude points. List of Permitted Values:

[ 5 values specified   See appendix I] A( 6) GeometricTy peName July 26, 2005 Page 10 Appendix A: Latitude/ Longitude Data Structure Diagram Latitude/ Longitude Data Standard 1.0 Mandatory Latitude/ Longitude Data 1.1 Latitude Measure 1.2 Longitude Measure 1.3 Source Map Scale Number 1.4 Horizontal Accuracy Measure 1.5 Horizontal Collection Method Code 1.6 Horizontal Collection Method Name 1.7 Geographic Reference Point Code 1.8 Geographic Reference Point Name 1.9 Horizontal Reference Datum Code 1.10 Horizontal Reference Datum Name 2.0 Optional Latitude/ Longitude Data 2.1 Data Collection Date 2.2 Location Comments Text 2.3 Vertical Measure 2.4 Vertical Collection Method Code 2.5 Vertical Collection Method Name 2.6 Vertical Reference Datum Code 2.7 Vertical Reference Datum Name 2.8 Verification Method Code 2.9 Verification Method Name 2.10 Coordinate Data Source Code 2.11 Coordinate Data Source Name 2.12 Geometric Type Code 2.13 Geometric Type Name July 26, 2005 Page 11 Appendix B [ Normative]

Horizontal Collection Method Code and Horizontal Collection Method Name  Permitted Values See the U. S. Environmental Protection Agency Environmental Data Registry [ www. epa. gov/ EDR ] for the most current list Code Name Value Meaning 001 Address Matching House Number The geographic coordinate determination method based on address matching house number.

002 Address Matching Block Face The geographic coordinate determination method based on address matching block face.

003 Address Matching Street Centerline The geographic coordinate determination method based on address matching street centerline.

004 Address Matching Nearest Intersection The geographic coordinate determination method based on address matching nearest intersection 005 Address Matching Primary Name The geographic coordinate determination method based on address matching primary name.

006 Address Matching Digitized The geographic coordinate determination method based on address matching digitized.

007 Address Matching Other The geographic coordinate determination method based on address matching other.

008 Census Block 1990 Centroid The geographic coordinate determination method based on census block 1990 centroid.

009 Census Block/ Group 1990 Centroid The geographic coordinate determination method based on census/ group 1990 centroid.

010 Census Block/ Tract 1990 Centroid The geographic coordinate determination method based on census/ tract 1990 centroid.

011 Census Other The geographic coordinate determination method based on census other.

012 GPS Carrier Phase Static Relative Position The geographic coordinate determination method based on GPS carrier phase static relative positioning technique.

013 GPS Carrier Phase Kinematic Relative Position The geographic coordinate determination method based on GPS carrier phase kinematic relative positioning technique.

014 GPS Code ( Pseudo Range) Differential The geographic coordinate determination method based on GPS code measurements ( pseudo range) differential ( DGPS).

015 GPS Code ( Pseudo Range) Precise Position The geographic coordinate determination method based on GPS code measurements ( pseudo range) precise positioning service.

016 GPS Code ( Pseudo Range) Standard Position ( SA Off) The geographic coordinate determination method based on GPS code measurements ( pseudo range) standard positioning service ( SA Off).

017 GPS Code ( Pseudo Range) Standard Position ( SA On) The geographic coordinate determination method based on GPS code measurements ( pseudo range) standard positioning service ( SA On).

018 Interpolation Map The geographic coordinate determination method based on interpolation map.

019 Interpolation Photo The geographic coordinate determination method based on interpolation photo.

020 Interpolation Satellite The geographic coordinate determination method based on interpolation satellite.

021 Interpolation Other The geographic coordinate determination method based on interpolation other.

022 Loran C The geographic coordinate determination method based on Loran C.

023 Public Land Survey Quarter Section The geographic coordinate determination method based on public land survey quarter of a section.

024 Public Land Survey Section The geographic coordinate determination method based on public land survey section.

025 Classical Surveying Techniques The geographic coordinate determination method based on classical surveying techniques.

026 ZIP Code Centroid The geographic coordinate determination method based on zipcode centroid.

027 Unknown The information is not known. Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Version 2 July 26, 2005 Page 12 Code Name Value Meaning 028 GPS Unspecified Global Positioning Method, with unspecified parameters.

029 GPS, with Canadian Active Control System GPS Code Measurements ( pseudo range) Standard Positioning Service Corrected using Canadian Active Control System.

030 Interpolation  Digital Map Source ( TIGER) The geographic coordinate determination method is based on a digital map source ( TIGER).

031 Interpolation SPOT The geographic coordinate determination method uses SPOT ( Systeme Probatoire d'Observation de la Terre), a French owned satellite launched in 1984.

032 Interpolation MSS The geographic coordinate determination method is based on the use of a Multi Spectral Scanner ( MSS).

033 Interpolation TM The geographic coordinate determination method is based on the use of a Thematic Mapper ( TM).

034 Public Land Survey Eighth Section The geographic coordinate determination method is based on a public land survey, an eighth of a section.

035 Public Land Survey Sixteenth Section The geographic coordinate determination method is based on a public land survey, a sixteenth of a section.

036 Public Land Survey Footing The geographic coordinate determination method is based on a public land survey footing.

037 ZIP+ 4 Centroid The center of an area defined by the 5 digit ZIP code and its 4 digit geographic segment extension.

038 ZIP+ 2 Centroid The center of an area defined by the 5 digit ZIP code and its 2 digit geographic segment extension. Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Version 2 July 26, 2005 Page 13 Appendix C [ Normative]

Reference Point Code and Reference Point Name  Permitted Values See the U. S. Environmental Protection Agency Environmental Data Registry [ www. epa. gov/ EDR ] for the most current list General Code Specific Code General Name Specific Name Value Meaning 101 Facility/ Station Location Entrance Point of a Facility, System, or Station 002 Plant Entrance ( general)

004 Plant Entrance ( personnel)

005 Plant Entrance ( freight)

015 Loading Facility 019 Administrative Building 102 Facility Center/ Centroid Center of a Facility/ System 016 Loading Area Centroid 020 Geographic Centroid of the Facility 025 Center of Production Facility 103 Facility Boundary Boundary point for a facility or System ( Facility boundary points can be singular, or part of a series of boundary points 021 NE Corner of Parcel 022 NW Corner of Parcel 023 SE Corner of Parcel 024 SW Corner of Parcel 104 Intake Point Point where water or other substance could be drawn from environment for delivery to a facility or distribution system ( substance destination could range from a single residence to a large facility)

030 Intake pipe 032 Water Well 033 Spring 037 Well Head 043 Oil Well 044 Sulfur Well 045 Gas Well 105 Treatment/ storage Point Point where substance is processed, treated,

stored ( point from which substance could be released into the environment 008 Storage Tank 010 Lagoon or Settling Pond 011 Liquid Waste Treatment Unit 017 Process Unit Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Version 2 July 26, 2005 Page 14 General Code Specific Code General Name Specific Name Value Meaning 018 Process Unit Centroid 106 Release Point Point where substance is released ( point where substance is directly released into the environment)

006 Air Release Stack 007 Air Release Vent 009 Water Release Pipe 012 Atmospheric Emission 013 Solid Waste Treatment and Disposal 014 Solid Waste Storage Area 035 Potential Contaminant Source 038 End of Pipe 046 Underground Injection Well 107 Monitoring Point Point where substance is monitored or sampled 028 Water Monitoring Station 029 Air Monitoring Station 039 Grid Origin 040 Point of Record 041 Sampling Point 042 Transect Origin 108 Points not represented by 101 107, 109 Points not represented by general codes 101 107,

109 or their specific codes 001 Unknown 003 Other 108 Points not represented by 101 107 109 Point of Transfer The point where one discharge point goes directly into an intake point Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Version 2 July 26, 2005 Page 15 Appendix D [ Normative]

Horizontal Reference Datum Code and Horizontal Reference Datum Name  Permitted Values See the U. S. Environmental Protection Agency Environmental Data Registry [ www. epa. gov/ EDR ] for the most current list Code Name Value Meaning 001 NAD27 North American Datum of 1927 002 NAD83 North American Datum of 1983 003 WGS84 World Geodetic System of 1984 Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Version 2 July 26, 2005 Page 16 Appendix E [ Normative]

Vertical Collection Method Code and Vertical Collection Method Name  Permitted Values See the U. S. Environmental Protection Agency Environmental Data Registry [ www. epa. gov/ EDR ] for the most current list Code Name Value Meaning 001 GPS Carrier Phase Static Relative Position The geographic coordinate determination method based on GPS carrier phase static relative positioning technique.

002 GPS Carrier Phase Kinematic Relative Position The geographic coordinate determination method based on GPS carrier phase kinematic relative positioning technique.

003 GPS Code ( Pseudo Range) Differential The geographic coordinate determination method based on GPS code measurements ( pseudo range) differential ( DGPS).

004 GPS Code ( Pseudo Range) Precise Position The geographic coordinate determination method based on GPS code measurements ( pseudo range) precise positioning service.

005 GPS Code ( Pseudo Range) Standard Position ( SA Off) The geographic coordinate determination method based on GPS code measurements ( pseudo range) standard positioning service ( SA Off).

006 GPS Code ( Pseudo Range) Standard Position ( SA On) The geographic coordinate determination method based on GPS code measurements ( pseudo range) standard positioning service ( SA On).

007 Classical Surveying Techniques The geographic coordinate determination method based on classical surveying techniques.

008 Other Other, unspecified.

009 Altimetry A method used to determine vertical components based on altimetry.

010 Precise Leveling Bench mark Precise leveling from a bench mark.

011 Leveling Non Bench Mark Control Points Leveling between non bench mark control points.

012 Trigonometric Leveling Trigonometric leveling.

013 Photogrammetic Photogrammetric.

014 Topographic Map Interpolation Topographic map interpolation. Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Version 2 July 26, 2005 Page 17 Appendix F [ Normative]

Vertical Reference Datum Code and Vertical Reference Datum Name  Permitted Values See the U. S. Environmental Protection Agency Environmental Data Registry [ www. epa. gov/ EDR ] for the most current list Code Name Value Meaning 001 NAVD88 North American Vertical Datum of 1988.

002 NGVD29 National Geodetic Vertical Datum of 1929.

003 Mean Sea Level The level of the surface of the sea at its position midway between mean high and low water.

004 Local Tidal Datum A known tidal measurement characteristic of a particular place. Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Version 2 July 26, 2005 Page 18 Appendix G [ Normative]

Verification Method Code and Verification Method Name  Permitted Values See the U. S. Environmental Protection Agency Environmental Data Registry [ www. epa. gov/ EDR ] for the most current list Code Name Value Meaning 004 Point in Polygon ( Other) The coordinates are a point within an undefined polygon.

005 Point in Polygon ( County) The coordinates are a point within the county.

006 Point in Polygon ( ZIP) The coordinates are a point within the ZIP Code area.

002 Proximity to Alternative Facility Coordinates The coordinates are proximate to alternative coordinates for the facility.

003 Proximity to Polygon Centroid ( Other) The coordinates are proximate to the centroid of another polygon.

001 Proximity to Polygon Centroid ( County) The coordinates are proximate to the centroid of the county.

012 Proximity to Polygon Centroid ( ZIP Code) The coordinates are proximate to the centroid of the ZIP Code.

010 Verified, Unknown Method The coordinates are verified by an unknown method.

008 Verified Relative to Map ( 1: 100K or TIGER) The coordinates are verified relative to map features ( 1: 100K or TIGER).

007 Verified Relative to Map Features ( 1: 24K) The coordinates are verified relative to map features ( 1: 24K).

009 Verified Relative to Map Features ( Other) The coordinates are verified relative to other map features.

011 Ground Truth Conducted The coordinates were determined by ground truth.

014 Point in Bounding Box ( County) The coordinates were verified as a point in the county bounding box.

013 Point in Bounding Box ( ZIP) The coordinates were verified as a point in the ZIP Code bounding box. Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Version 2 July 26, 2005 Page 19 Appendix H [ Normative]

Coordinate Data Source Code and Coordinate Data Source Name  Permitted Values See the U. S. Environmental Protection Agency Environmental Data Registry [ www. epa. gov/ EDR ] for the most current list Code Name Value Meaning 001 Alabama The state of Alabama.

002 Alaska The state of Alaska.

004 Arizona The state of Arizona.

005 Arkansas The state of Arkansas.

006 California The state of California.

008 Colorado The state of Colorado.

009 Connecticut The state of Connecticut.

010 Delaware The state of Delaware.

011 District of Columbia The state of District of Columbia.

012 Florida The state of Florida.

013 Georgia The state of Georgia.

015 Hawaii The state of Hawaii.

016 Idaho The state of Idaho.

017 Illinois The state of Illinois.

018 Indiana The state of Indiana.

019 Iowa The state of Iowa.

020 Kansas The state of Kansas.

021 Kentucky The state of Kentucky.

022 Louisiana The state of Louisiana.

023 Maine The state of Maine.

024 Maryland The state of Maryland.

025 Massachusetts The state of Massachusetts.

026 Michigan The state of Michigan.

027 Minnesota The state of Minnesota.

028 Mississippi The state of Mississippi.

029 Missouri The state of Missouri.

030 Montana The state of Montana.

031 Nebraska The state of Nebraska.

032 Nevada The state of Nevada.

033 New Hampshire The state of New Hampshire.

034 New Jersey The state of New Jersey.

035 New Mexico The state of New Mexico.

036 New York The state of New York.

037 North Carolina The state of North Carolina.

038 North Dakota The state of North Dakota. Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Version 2 July 26, 2005 Page 20 Code Name Value Meaning 039 Ohio The state of Ohio.

040 Oklahoma The state of Oklahoma.

041 Oregon The state of Oregon.

042 Pennsylvania The state of Pennsylvania.

044 Rhode Island The state of Rhode Island.

045 South Carolina The state of South Carolina.

046 South Dakota The state of South Dakota.

047 Tennessee The state of Tennessee.

048 Texas The state of Texas.

049 Utah The state of Utah.

050 Vermont The state of Vermont.

051 Virginia The state of Virginia.

053 Washington The state of Washington.

054 West Virginia The state of West Virginia.

055 Wisconsin The state of Wisconsin.

056 Wyoming The state of Wyoming.

060 American Samoa The territory of American Samoa.

064 Federated States of Micronesia The federated states of Micronesia.

066 Guam The territory of Guam.

068 Marshall Islands The republic of the Marshall Islands.

069 Northern Mariana Islands The territory of Northern Mariana Islands.

070 Palau The republic of Palau.

072 Puerto Rico The territory of Puerto Rico.

074 U. S. Minor Outlying Islands The territory of U. S. Minor Outlying Islands.

078 Virgin Islands of the United States The territory of the Virgin Islands of the United States.

080 Contractor An organization or individual that contracts to perform work.

081 Dun & Bradstreet Dun & Bradstreet.

082 EPA Headquarters EPA headquarters.

083 Other Other, unspecified.

084 Other Federal Agency An agency of the federal government other than EPA.

085 Private Belonging to or concerning an individual person, company, or interest.

086 Tribe A group of Native Americans or Native Alaskans having jurisdiction over an area and population.

087 Unknown The information is not known.

088 Region 1 The EPA Region that includes the U. S. states of CT, ME, MA, NH, RI, VT.

089 Region 10 The EPA Region that includes the U. S. states of WA, OR, ID, AK.

090 Region 2 The EPA Region that includes the U. S. states of NJ, NY, PR, VI.

091 Region 3 The EPA Region that includes the U. S. states of PA, DE, DC, MD, VA, WV.

092 Region 4 The EPA Region that includes the U. S. states of KY, TN, NC, SC, MS, AL, GA, FL.

093 Region 5 The EPA Region that includes the U. S. states of MN, WI, IL, MI, IN, OH.

094 Region 6 The EPA Region that includes the U. S. states of NM, TX, OK, AR, LA.

095 Region 7 The EPA Region that includes the U. S. states of NE, KS, IA, MO. Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Version 2 July 26, 2005 Page 21 Code Name Value Meaning 096 Region 8 The EPA Region that includes the U. S. states of MT, ND, WY, SD, UT, CO.

097 Region 9 The EPA Region that includes the U. S. states of CA, NV, AZ, HI, AS, GU.

098 Regulated Entity The establishment or organization subject to a law or governmental order. Latitude/ Longitude Data Standard Std No.: 1 19939: 2 Version 2 July 26, 2005 Page 22 Appendix I [ Normative]

Geometric Type Code and Geometric Type Name  Permitted Values See the U. S. Environmental Protection Agency Environmental Data Registry [ www. epa. gov/ EDR ] for the most current list Code Name Value Meaning 001 Point The point referenced by geographic coordinates.

002 Line The line referenced by geographic coordinates.

003 Area The area referenced by geographic coordinates.

004 Region The geometric entity, described by locational coordinates, that includes two or more related areas is a region.

005 Route The geometric entity, described by locational coordinates, that form a contiguous network is a route.


[Federal Register Volume 85, Number 175 (Wednesday, September 9, 2020)]
[Notices]
[Pages 55717-55718]
[FR Doc No: 2020-19843]

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

SECURITIES AND EXCHANGE COMMISSION

[Release No. 34-89743; File No. SR-CBOE-2020-034]

Self-Regulatory Organizations; Cboe Exchange, Inc.; Notice of
Designation of a Longer Period for Commission Action on a Proposed Rule
Change To Authorize for Trading Flexible Exchange Options on Full-Value
Indexes With a Contract Multiplier of One

September 2, 2020.
    On June 30, 2020, Cboe Exchange, Inc. filed with the Securities and
Exchange Commission (``Commission''), pursuant to Section 19(b)(1) of
the Securities Exchange Act of 1934 (``Act'') \1\ and Rule 19b-4
thereunder,\2\ a proposed rule change to authorize for trading flexible
exchange options on full-value indexes with a contract multiplier of
one. The Commission published notice of the proposed rule change in the
Federal Register on July 20, 2020.\3\
---------------------------------------------------------------------------

    \1\ 15 U.S.C. 78s(b)(1).
    \2\ 17 CFR 240.19b-4.
    \3\ See Securities Exchange Act Release No. 34-89308 (July 14,
2020), 85 FR 43923. Comments received on the proposed rule change
are available on the Commission's website at: https://www.sec.gov/comments/sr-cboe-2020-034/srcboe2020034.htm.
---------------------------------------------------------------------------

    Section 19(b)(2) of the Act \4\ provides that, within 45 days of
the publication of notice of the filing of a proposed rule change, or
within such longer period up to 90 days as the Commission may designate
if it finds such longer period to be appropriate and publishes its
reasons for so finding or as to which the self-regulatory organization
consents, the Commission shall either approve the proposed rule change,
disapprove the proposed rule change, or institute proceedings to
determine whether the proposed rule change should be disapproved. The
45th day after publication of the notice for this proposed rule change
is September 3, 2020. The Commission is extending this 45-day time
period.
---------------------------------------------------------------------------

    \4\ 15 U.S.C. 78s(b)(2).
---------------------------------------------------------------------------

    The Commission finds that it is appropriate to designate a longer
period within which to take action on the proposed rule change so that
it has

sufficient time to consider the proposed rule change. Accordingly, the
Commission, pursuant to Section 19(b)(2) of the Act,\5\ designates
October 18, 2020, as the date by which the Commission shall either
approve or disapprove or institute proceedings to determine whether to
disapprove the proposed rule change (File Number SR-CBOE-2020-034).
---------------------------------------------------------------------------

    \5\ Id.

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

    \6\ 17 CFR 200.30-3(a)(31).
---------------------------------------------------------------------------

J. Matthew DeLesDernier,
Assistant Secretary.
[FR Doc. 2020-19843 Filed 9-8-20; 8:45 am]
BILLING CODE 8011-01-P


[Federal Register Volume 87, Number 5 (Friday, January 7, 2022)]
[Notices]
[Pages 953-954]
[FR Doc No: 2022-00090]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Docket No. ER22-729-000]

CPV Retail Energy LP; Supplemental Notice That Initial Market-
Based Rate Filing Includes Request for Blanket Section 204
Authorization

    This is a supplemental notice in the above-referenced proceeding of
CPV Retail Energy LP's application for market-based rate authority,
with an accompanying rate tariff, noting that such application includes
a request for blanket authorization, under 18 CFR part 34, of future
issuances of securities and assumptions of liability.
    Any person desiring to intervene or to protest should file with the
Federal Energy Regulatory Commission, 888 First Street NE, Washington,
DC 20426, in accordance with Rules 211 and 214 of the Commission's
Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone
filing a motion to intervene or protest must serve a copy of that
document on the Applicant.
    Notice is hereby given that the deadline for filing protests with
regard to the applicant's request for blanket authorization, under 18
CFR part 34, of future issuances of securities and assumptions of
liability, is January 24, 2022.
    The Commission encourages electronic submission of protests and
interventions in lieu of paper, using the FERC Online links at http://www.ferc.gov. To facilitate electronic service, persons with internet
access who will eFile a document and/or be listed as a contact for an
intervenor must create and validate an eRegistration account using the
eRegistration link. Select the eFiling link to log on and submit the
intervention or protests.
    Persons unable to file electronically may mail similar pleadings to
the Federal Energy Regulatory Commission, 888 First Street NE,
Washington, DC 20426. Hand delivered submissions in docketed
proceedings should be delivered to Health and Human Services, 12225
Wilkins Avenue, Rockville, Maryland 20852.
    In addition to publishing the full text of this document in the
Federal Register, the Commission provides all

interested persons an opportunity to view and/or print the contents of
this document via the internet through the Commission's Home Page
(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. At this time, the Commission has suspended access
to the Commission's Public Reference Room, due to the proclamation
declaring a National Emergency concerning the Novel Coronavirus Disease
(COVID-19), issued by the President on March 13, 2020. For assistance,
contact the Federal Energy Regulatory Commission at
[email protected] or call toll-free,<PHONE_NUMBER> or TYY,
(202) 502-8659.

    Dated: January 3, 2022.
Kimberly D. Bose,
Secretary.
[FR Doc. 2022-00090 Filed 1-6-22; 8:45 am]
BILLING CODE 6717-01-P


[Federal Register Volume 80, Number 202 (Tuesday, October 20, 2015)]
[Notices]
[Pages 63635-63636]
[FR Doc No: 2015-26592]

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

DEPARTMENT OF TRANSPORTATION

Federal Railroad Administration

[Docket Number FRA-2009-0124]

Petition for Waiver of Compliance

    In accordance with part 211 of Title 49 Code of Federal Regulations
(CFR), this provides the public notice that by a document dated
September 22, 2015, the Peninsula Corridor Joint Powers Board (JPB) has
petitioned the Federal Railroad Administration (FRA) for a modification
to its existing waiver of compliance from certain provisions of the
Federal railroad safety regulations contained at 49 CFR part 238. FRA
assigned the petition Docket Number FRA-2009-0124.
    JBP, located in San Carlos, CA, seeks an amendment to its permanent
waiver of compliance from 49 CFR 238.203, Static end strength, 238.205,
Anti-climbing mechanism, and 238.207, Link between coupling mechanism
and car body. JPB is considering purchasing non-FRA-compliant electric
multiple unit (EMU) vehicles, constructed to European safety standards,
for its Caltrain commuter rail service between San Francisco and
Gilroy, CA. JPB seeks to amend two of the nine conditions specified in
FRA's waiver decision letter dated May 27, 2010.
    Specifically, JPB requests that Condition 1 (that EMUs that are the
subject of this waiver meet or exceed the crashworthiness performance
levels identified and presented in the petition) be modified to align
with proposed rule text for alternatively compliant Tier I equipment
developed through the Railroad Safety Advisory Committee and its
Engineering Task Force. Secondly, JPB requests removal of Condition 7
(that JPB submit a comprehensive temporal separation plan to FRA for
approval before the EMUs are operated).
    JPB states that the proposed rule text does not require temporal
separation because trains built to these new rules are considered as
safe or safer in collisions than trains built to current Federal
standards. In addition, JPB states that it is currently implementing
Positive Train Control and new EMUs will be compatible with the system,
thereby reducing the risk of an impact between freight and passenger
trains.
    A copy of the petition, as well as any written communications
concerning the petition, is available for review online at
www.regulations.gov and in person at the U.S. Department of
Transportation's (DOT) Docket Operations Facility, 1200 New Jersey
Avenue SE., W12-140, Washington, DC 20590. The Docket

Operations Facility is open from 9 a.m. to 5 p.m., Monday through
Friday, except Federal Holidays.
    Interested parties are invited to participate in these proceedings
by submitting written views, data, or comments. FRA does not anticipate
scheduling a public hearing in connection with these proceedings since
the facts do not appear to warrant a hearing. If any interested party
desires an opportunity for oral comment, they should notify FRA, in
writing, before the end of the comment period and specify the basis for
their request.
    All communications concerning these proceedings should identify the
appropriate docket number (e.g., Waiver Petition Docket Number FRA-
2004-20000) and may be submitted by any of the following methods:
     Web site: http://www.regulations.gov. Follow the online
instructions for submitting comments.
     Fax:<PHONE_NUMBER>.
     Mail: Docket Operations Facility, U.S. Department of
Transportation, 1200 New Jersey Avenue SE., W12-140, Washington, DC
20590.
     Hand Delivery: 1200 New Jersey Avenue SE., Room W12-140,
Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday,
except Federal holidays.
    Communications received by December 4, 2015 will be considered by
FRA before final action is taken. Comments received after that date
will be considered as far as practicable.
    Anyone is able to search the electronic form of any written
communications and comments received into any of our dockets by the
name of the individual submitting the comment (or signing the document,
if submitted on behalf of an association, business, labor union, etc.).
In accordance with 5 U.S.C. 553(c), DOT solicits comments from the
public to better inform its processes. DOT posts these comments,
without edit, including any personal information the commenter
provides, to www.regulations.gov, as described in the system of records
notice (DOT/ALL-14 FDMS), which can be reviewed at www.dot.gov/privacy.
See also http://www.regulations.gov/#!privacyNotice for the privacy
notice of regulations.gov.

    Issued in Washington, DC, on October 15, 2015.
Ron Hynes,
Director, Office of Technical Oversight.
[FR Doc. 2015-26592 Filed 10-19-15; 8:45 am]
 BILLING CODE 4910-06-P


[Federal Register Volume 84, Number 123 (Wednesday, June 26, 2019)]
[Notices]
[Pages 30103-30104]
[FR Doc No: 2019-13583]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Docket No. CP19-480-000]

Texas Gas Transmission, LLC; Notice of Request Under Blanket
Authorization

    Take notice that on June 11, 2019, Texas Gas Transmission, LLC
(Texas Gas), 9 Greenway Plaza, Suite 2800, Houston, Texas 77046, filed
a prior notice application pursuant to sections 157.205 and 157.216 of
the Federal Energy Regulatory Commission's (Commission) regulations
under the Natural Gas Act (NGA), and its blanket certificate issued in
Docket No. CP82-407-000. Texas Gas requests

authorization to plug and abandon Injection/Withdrawal Well No. 5710,
abandon in-place its related well lateral line and side valve, and
abandon by removal its associated above-ground equipment located in
Texas Gas' Leesville Storage Field in Lawrence County, Indiana, all as
more fully set forth in the application, which is open to the public
for inspection. The filing may also be viewed on the web 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 at<EMAIL_ADDRESS>or
call toll-free,<PHONE_NUMBER> or TTY,<PHONE_NUMBER>.
    Any questions regarding this application should be directed to Juan
Eligio, Supervisor of Regulatory Affairs, Texas Gas Transmission, LLC,
9 Greenway Plaza, Suite 2800, Houston, Texas 77046, by telephone at
(713) 479-3480, or by email at<EMAIL_ADDRESS>and Payton
Barrientos, Senior Regulatory Analyst, Texas Gas Transmission, LLC, 9
Greenway Plaza, Suite 2800, Houston, Texas 77046, by telephone at (713)
479-8180, or by email at<EMAIL_ADDRESS>    Any person or the Commission's staff may, within 60 days after
issuance of the instant notice by the Commission, file pursuant to Rule
214 of the Commission's Procedural Rules (18 CFR 385.214) a motion to
intervene or notice of intervention and pursuant to section 157.205 of
the regulations under the NGA (18 CFR 157.205), a protest to the
request. If no protest is filed within the time allowed therefore, the
proposed activity shall be deemed to be authorized effective the day
after the time allowed for filing a protest. If a protest is filed and
not withdrawn within 30 days after the allowed time for filing a
protest, the instant request shall be treated as an application for
authorization pursuant to section 7 of the NGA.
    Pursuant to section 157.9 of the Commission's rules, 18 CFR 157.9,
within 90 days of this Notice the Commission staff will either:
Complete its environmental assessment (EA) and place it into the
Commission's public record (eLibrary) for this proceeding, or issue a
Notice of Schedule for Environmental Review. If a Notice of Schedule
for Environmental Review is issued, it will indicate, among other
milestones, the anticipated date for the Commission staff's issuance of
the final environmental impact statement (FEIS) or EA for this
proposal. The filing of the EA in the Commission's public record for
this proceeding or the issuance of a Notice of Schedule for
Environmental Review will serve to notify federal and state agencies of
the timing for the completion of all necessary reviews, and the
subsequent need to complete all federal authorizations within 90 days
of the date of issuance of the Commission staff's FEIS or EA.
    Persons who wish to comment only on the environmental review of
this project should submit an original and two copies of their comments
to the Secretary of the Commission. Environmental commenters will be
placed on the Commission's environmental mailing list, will receive
copies of the environmental documents, and will be notified of meetings
associated with the Commission's environmental review process.
Environmental commenters will not be required to serve copies of filed
documents on all other parties. However, the non-party commenter will
not receive copies of all documents filed by other parties or issued by
the Commission (except for the mailing of environmental documents
issued by the Commission) and will not have the right to seek court
review of the Commission's final order.
    The Commission strongly encourages electronic filings of comments,
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 5 copies of the protest or intervention to the
Federal Energy Regulatory Commission, 888 First Street NE, Washington,
DC 20426.

    Dated: June 20, 2019.
Nathaniel J. Davis, Sr.,
Deputy Secretary.
[FR Doc. 2019-13583 Filed 6-25-19; 8:45 am]
 BILLING CODE 6717-01-P


[Federal Register Volume 79, Number 144 (Monday, July 28, 2014)]
[Notices]
[Pages 43761-43763]
[FR Doc No: 2014-17620]

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

DEPARTMENT OF HOMELAND SECURITY

Federal Emergency Management Agency

[Docket ID FEMA-2014-0002; Internal Agency Docket No. FEMA-B-1418]

Proposed Flood Hazard Determinations

AGENCY: Federal Emergency Management Agency, DHS.

ACTION: Notice.

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

SUMMARY: Comments are requested on proposed flood hazard
determinations, which may include additions or modifications of any
Base Flood Elevation (BFE), base flood depth, Special Flood Hazard Area
(SFHA) boundary or zone designation, or regulatory floodway on the
Flood Insurance Rate Maps (FIRMs), and where applicable, in the
supporting Flood Insurance Study (FIS) reports for the communities
listed in the table below. The purpose of this notice is to seek
general information and comment regarding the preliminary FIRM, and
where applicable, the FIS report that the Federal Emergency Management
Agency (FEMA) has provided to the affected communities. The FIRM and
FIS report are the basis of the floodplain management measures that the
community is required either to adopt or to show evidence of having in
effect in order to qualify or remain qualified for participation in the
National Flood Insurance Program (NFIP). In addition, the FIRM and FIS
report, once effective, will be used by insurance agents and others to
calculate appropriate flood insurance premium rates for new buildings
and the contents of those buildings.

DATES: Comments are to be submitted on or before October 27, 2014.

ADDRESSES: The Preliminary FIRM, and where applicable, the FIS report
for each community are available for inspection at both the online
location and the respective Community Map Repository address listed in
the tables below. Additionally, the current effective FIRM and FIS
report for each community are accessible online through the FEMA Map
Service Center at www.msc.fema.gov for comparison.
    You may submit comments, identified by Docket No. FEMA-B-1418, to
Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance
and Mitigation Administration, FEMA, 500 C Street SW., Washington, DC
20472,<PHONE_NUMBER>, or (email<EMAIL_ADDRESS>
FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering
Management Branch, Federal Insurance and Mitigation Administration,
FEMA, 500 C Street SW., Washington, DC 20472,<PHONE_NUMBER>, or
(email<EMAIL_ADDRESS>or visit the FEMA Map Information
eXchange (FMIX) online at www.floodmaps.fema.gov/fhm/fmx_main.html.

SUPPLEMENTARY INFORMATION: FEMA proposes to make flood hazard
determinations for each community listed below, in accordance with
section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C.
4104, and 44 CFR 67.4(a).
    These proposed flood hazard determinations, together with the
floodplain management criteria required by 44 CFR 60.3, are the minimum
that are required. They should not be construed to mean that the
community must change any existing ordinances that are more stringent
in their floodplain management requirements. The community may at any
time enact stricter requirements of its own or pursuant to policies
established by other Federal, State, or regional entities. These flood
hazard determinations are used to meet the floodplain management
requirements of the NFIP and also are used to calculate the appropriate
flood insurance premium rates for new buildings built after the FIRM
and FIS report become effective.
    The communities affected by the flood hazard determinations are
provided in the tables below. Any request for reconsideration of the
revised flood hazard information shown on the Preliminary FIRM and FIS
report that satisfies the data requirements outlined in 44 CFR 67.6(b)
is considered an appeal. Comments unrelated to the flood hazard
determinations also will be considered before the FIRM and FIS report
become effective.
    Use of a Scientific Resolution Panel (SRP) is available to
communities in support of the appeal resolution process. SRPs are
independent panels of experts in hydrology, hydraulics, and other
pertinent sciences established to review conflicting scientific and
technical data and provide recommendations for resolution. Use of the
SRP only may be exercised after FEMA and local communities have been
engaged in a collaborative consultation process for at least 60 days
without a mutually acceptable resolution of an appeal. Additional
information regarding the SRP process can be found online at http://floodsrp.org/pdfs/srp_fact_sheet.pdf.
    The watersheds and/or communities affected are listed in the tables
below. The Preliminary FIRM, and where applicable, FIS report for each
community are available for inspection at both the online location and
the respective Community Map Repository address listed in the tables.
Additionally, the current effective FIRM and FIS report for each
community are accessible online through the FEMA Map Service Center at
www.msc.fema.gov for comparison.

------------------------------------------------------------------------
                                             Community map repository
               Community                             address
------------------------------------------------------------------------
            Maricopa County, Arizona, and Incorporated Areas
------------------------------------------------------------------------
Maps Available for Inspection Online at: http://www.fema.gov/preliminaryfloodhazarddata preliminaryfloodhazarddata
------------------------------------------------------------------------
City of Avondale.......................  Development and Engineering
                                          Services Department, 11465
                                          West Civic Center Drive,
                                          Avondale, AZ 85323.
City of Chandler.......................  Transportation and Development,
                                          215 East Buffalo Street,
                                          Chandler, AZ 85255.
City of Goodyear.......................  Engineering Department, 14455
                                          West Van Buren Street, Suite D
                                          101, Goodyear, AZ 85338.
City of Mesa...........................  Engineering Department, City
                                          Hall, 20 East Main Street, 5th
                                          Floor, Mesa, AZ 85211.
City of Phoenix........................  Street Transportation
                                          Department, 200 West
                                          Washington Street, 5th Floor,
                                          Phoenix, AZ 85003.
City of Scottsdale.....................  Planning Records, 7447 East
                                          Indian School Road, Suite 100,
                                          Scottsdale, AZ 85251.
Town of Gila Bend......................  Town Hall, 644 West Pima
                                          Street, Gila Bend, AZ 85337.
Town of Gilbert........................  Development Engineering, 90
                                          East Civic Center Drive,
                                          Gilbert, AZ 85296.
Unincorporated Areas of Maricopa County  Flood Control District of
                                          Maricopa County, 2801 West
                                          Durango Street, Phoenix, AZ
                                          85009.
------------------------------------------------------------------------
            Sierra County, California, and Incorporated Areas
------------------------------------------------------------------------
Maps Available for Inspection Online at: http://www.fema.gov/preliminaryfloodhazarddata preliminaryfloodhazarddata
------------------------------------------------------------------------
Unincorporated Areas of Sierra County..  Sierra County Department of
                                          Planning, 101 Courthouse
                                          Square, Downieville, CA 95936.
------------------------------------------------------------------------
             Adams County, Colorado, and Incorporated Areas
------------------------------------------------------------------------
Maps Available for Inspection Online at: http://www.fema.gov/preliminaryfloodhazarddata preliminaryfloodhazarddata
------------------------------------------------------------------------
City of Northglenn.....................  11701 Community Center Drive,
                                          Northglenn, CO 80233.
City of Thornton.......................  12450 Washington Street,
                                          Thornton, CO 80241.
Unincorporated Areas of Adams County...  4430 South Adams County
                                          Parkway, Suite W2000B,
                                          Brighton, CO 80601.
------------------------------------------------------------------------
     City and County of Broomfield, Colorado, and Incorporated Areas
------------------------------------------------------------------------
Maps Available for Inspection Online at: www.fema.gov/preliminaryfloodhazarddata preliminaryfloodhazarddata
------------------------------------------------------------------------
City and County of Broomfield..........  City Hall, Engineering
                                          Department, One Descombes
                                          Drive, Broomfield, CO 80020.
------------------------------------------------------------------------
           Jefferson County, Colorado, and Incorporated Areas
------------------------------------------------------------------------
Maps Available for Inspection Online at: www.fema.gov/preliminaryfloodhazarddata preliminaryfloodhazarddata
------------------------------------------------------------------------
City of Arvada.........................  Engineering Department, 8101
                                          Ralston Road, Arvada, CO
                                          80001.
City of Westminster....................  4800 West 92nd Ave.,
                                          Westminster, CO 80031.
Unincorporated Areas of Jefferson        Jefferson County Department of
 County.                                  Planning and Zoning, 100
                                          Jefferson County Parkway,
                                          Suite 3550, Golden, CO 80419.
------------------------------------------------------------------------
            Flathead County, Montana, and Incorporated Areas
------------------------------------------------------------------------
Maps Available for Inspection Online at: http://www.fema.gov/preliminaryfloodhazarddata preliminaryfloodhazarddata
------------------------------------------------------------------------
City of Kalispell......................  Planning Director, Planning
                                          Department, 17 2nd Street
                                          East, Suite 211, Kalispell, MT
                                          59901.
City of Whitefish......................  Planning Director, Planning &
                                          Building Department, 1005C
                                          Baker Avenue, Whitefish, MT
                                          59937.
Unincorporated Areas of Flathead County  Planning Director, Planning &
                                          Zoning Office, 1035 1st Avenue
                                          West, Kalispell, MT 59901.
------------------------------------------------------------------------
           Stillwater County, Montana, and Incorporated Areas
------------------------------------------------------------------------
Maps Available for Inspection Online at: http://www.fema.gov/preliminaryfloodhazarddata preliminaryfloodhazarddata
------------------------------------------------------------------------
Town of Columbus.......................  Stillwater County West Annex,
                                          431 Quarry Road, Columbus, MT.
Unincorporated Areas of Stillwater       Stillwater County West Annex,
 County.                                  431 Quarry Road, Columbus, MT.
------------------------------------------------------------------------

       Mecklenburg County, North Carolina, and Incorporated Areas
------------------------------------------------------------------------
Maps Available for Inspection Online at: http://www.fema.gov/preliminaryfloodhazarddata preliminaryfloodhazarddata
------------------------------------------------------------------------
City of Charlotte......................  Mecklenburg County Storm Water
                                          Services Office, 700 North
                                          Tryon Street, Charlotte, NC
                                          28202.
Town of Cornelius......................  Town Hall, 21445 Catawba
                                          Avenue, Cornelius, NC 28031.
Town of Huntersville...................  Planning Department, 101
                                          Huntersville-Concord Road,
                                          Huntersville, NC 28078.
Town of Pineville......................  Town Hall, 200 Dover Street,
                                          Pineville, NC 28134.
Unincorporated Areas of Mecklenburg      Mecklenburg County Storm Water
 County.                                  Services Office, 700 North
                                          Tryon Street, Charlotte, NC
                                          28202.
------------------------------------------------------------------------
               Davis County, Utah, and Incorporated Areas
------------------------------------------------------------------------
Maps Available for Inspection Online at: http://www.fema.gov/preliminaryfloodhazarddata preliminaryfloodhazarddata
------------------------------------------------------------------------
City of Bountiful......................  City Hall, 790 South 100 East,
                                          Bountiful, UT 84010.
City of Centerville....................  Community Development
                                          Department, 655 North 1250
                                          West, Centerville, UT 84014.
City of Farmington.....................  City Hall, 160 South Main
                                          Street, Farmington, UT 84025.
City of Fruit Heights..................  City Hall, 910 South Mountain
                                          Road, Fruit Heights, UT 84037.
City of Kaysville......................  City Hall, 23 East Center
                                          Street, Kaysville, UT 84037.
City of Layton.........................  City Center, 437 North Wasatch
                                          Drive, Layton, UT 84041.
City of South Weber....................  City Hall, 1600 East South
                                          Weber Drive, South Weber, UT
                                          84405.
City of West Bountiful.................  City Hall, 550 North 800 West,
                                          West Bountiful, UT 84087.
City of Woods Cross....................  City Hall, 1555 South 800 West,
                                          Woods Cross, UT 84087.
Unincorporated Areas of Davis County...  Davis County Administration
                                          Building, 61 South Main
                                          Street, Farmington, UT 84025.
------------------------------------------------------------------------

(Catalog of Federal Domestic Assistance No. 97.022, ``Flood
Insurance.'')

    Dated: June 26, 2014.
Roy E. Wright,
Deputy Associate Administrator for Mitigation, Department of Homeland
Security, Federal Emergency Management Agency.
[FR Doc. 2014-17620 Filed 7-25-14; 8:45 am]
BILLING CODE 9110-12-P


[Federal Register Volume 82, Number 229 (Thursday, November 30, 2017)]
[Notices]
[Pages 56852-56853]
[FR Doc No: 2017-25843]

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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

Agency Information Collection Activities: Requests for Comments;
Clearance of Extension Without Change of a Currently Approved
Information Collection: Pilots Convicted of Alcohol or Drug Related
Motor Vehicle Offenses or Subject to State Motor Vehicle Administrative
Procedures

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 extend an information
collection. Pilots who have been involved in a drug or alcohol related
motor vehicle action are required to send specific information to the
FAA . The information to be collected will be used to and/or is
necessary for the FAA to ensure the safety of the National Airspace
System with regard to those airmen.

DATES: Written comments should be submitted by January 29, 2018.

ADDRESSES: Send comments to the FAA at the following address: Barbara
Hall, Federal Aviation Administration, ASP-110, 10101 Hillwood Parkway,
Fort Worth, TX 76177.
    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: Barbara Hall by email at:
[email protected]; phone:<PHONE_NUMBER>.

SUPPLEMENTARY INFORMATION:
    OMB Control Number: 2120-0543.
    Title: Pilots Convicted of Alcohol or Drug Related Motor Vehicle
Offenses or Subject to State Motor Vehicle Administrative Procedures.
    Form Numbers: No forms.
    Type of Review: Extension Without Change.
    Background: After a study and audit conducted from the late 1970's
through the 1980's by the Department of Transportation, Office of the
Inspector General, (DOT/OIG), the DOT/OIG recommended the FAA find a
way to track alcohol abusers and those dependent on the substance that
may pose a threat to the National Airspace (NAS). Through a
Congressional act issued in November of 1990, the FAA established a
Driving Under the Influence (DUI) and Driving While Impaired (DWI)
Investigations Branch. The final rule for this program is found in
Title 14 Code of Federal Regulations (CFR)--part 61 Sec.  61.15.
    This regulation calls for pilots certificated by the FAA to send
information regarding Driving Under the Influence (or similar charges)
of alcohol

or drugs to the FAA within 60 days from either an administrative action
against their driver's license and/or criminal conviction. Part of the
regulation also calls for the FAA to seek certificate action should an
airman be involved in multiple, separate drug/alcohol related motor
vehicle incidents within a three-year period. Information sent by the
airmen is used to confirm or refute any violations of these
regulations, as well as by the Civil Aerospace Medical Institute (CAMI)
for medical qualification purposes. Collection by CAMI is covered under
a separate OMB control number 2120-0034.
    An airman is required to provide a letter via mail or facsimile,
with the following information: Name, address, date of birth, pilot
certificate number, the type of violation which resulted in the
conviction or administrative action, and the state which holds the
records or action.
    Respondents: Airmen with drug/alcohol related motor vehicle
actions.
    Frequency: Approximately 1,000 per year.
    Estimated Average Burden per Response: 15 Minutes.
    Estimated Total Annual Burden: 10-20 minutes per respondent, 167
hours total for all respondents.

    Issued in Fort Worth, TX on November 21, 2017.
Barbara L. Hall,
FAA Information Collection Clearance Officer, Performance, Policy, and
Records Management Branch, ASP-110.
[FR Doc. 2017-25843 Filed 11-29-17; 8:45 am]
 BILLING CODE 4910-13-P