DRAFT

ENVIORNMENTAL SAMPLING, ANALYSIS

AND RESULTS: MONITORING LOCATION

DATA STANDARD

Standard No.: EX000003.2

July 10, 2009

This standard has been produced through the

Exchange Network Leadership Council (ENLC).

The Exchange Network Leadership Council (ENLC) is a partnership among US
EPA, States and Tribal partners to promote the efficient sharing of
environmental information through the efficient management of the
Exchange Network development and adoption of data standards. More
information about is available at www.exchangenetwork.net/standards
HYPERLINK "http://"   .

Foreword

The Exchange Network Leadership Council (ENLC) is a partnership among US
EPA, States and Tribal partners to develop and agree upon data standards
for environmental information collection and exchange.  The Council
seeks to promote efficient sharing of environmental information between
State, US EPA and Tribal partners through the development of data
standards.  More information about data standards is available at
http://www.exchangenetwork.net/standards.

1.0	INTRODUCTION

Environmental information is a key tool in the effective management of
our environmental resources and human health conditions.  As a result,
much effort goes into data acquisition, management, maintenance,
exchange, and oversight.  Greater access is the goal of many data
consumers, and data managers. Providers invest significant resources
meeting their requirements. In response, many data providers are
improving access as they post usable copies of their environmental
information on the web.  These efforts are a vast improvement over
previous conditions; however, there is a growing desire and need to both
provide and receive data in a clearly defined and a uniform way.  Data
from multiple sources can then be aggregated and used without the
inherent variations that exist between data sets across agencies.

1.1	Scope

This standard provides and describes data groupings and data elements
that are used to define and exchange data and information about
Environmental Sampling, Analysis, and Results:  Monitoring Location.

1.2	Revision History

Date	Version	Description

January 6, 2006	EX000003.1	Initial Environmental Data Standards Council
Adoption

July 22, 2008	EX000002.2	Modification of data standard to incorporate
additional water quality and biological data elements.

1.3	References to Other Data Standards

This standard relies on other standards to make it complete and provide
the necessary support. As such users should consider the references to
other data standards noted below as integral to the Monitoring Location
Data Standard. These include:

Contact Information [EX000019.2] Data Standard

Latitude/Longitude [EX000017.2] Data Standard

Attached Binary [EX000006.1] Object Data Standard

Bibliographic Reference [EX000007.1] Data Standard

Measure [EX000010.1] Data Standard

Representation of Date and Time [EX000013.1] Data Standard

Well Information [EX000025.2] Data Standard

1.4	Terms and Definitions

For the purposes of this document, the following terms and definitions
apply.

Term	Definition

Monitoring Location	An identifiable location where an environmental
sample, onsite measurement, and/or observation is determined.

Probe	A specialized inlet used where a sample is collected from an
environmental matrix for delivery to a sampler or point analyzer for
pollutant analysis.

1.5	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 ( HYPERLINK "http://www.exchangenetwork.net/"
http://www.exchangenetwork.net ).

1.6	Document Structure

The structure of this document is briefly described below:

Section 2.0 ESAR: Monitoring Location Diagram illustrates the principal
data groupings contained within this standard.

Section 3.0 ESAR:  Monitoring Location Data Standard Table provides
information on the high level, intermediate and elemental ESAR:
Monitoring Location 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 number
of characters for the associated data element, where “A” specifies
alphanumeric, “N” designates numeric, “G” and “D” are used
for grouping and date/time.

Data Element 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 elemental level.

Code and Identifier Metadata: Metadata, defined here as data about data
or data elements, includes their descriptions and/or any needed context
setting information required to identify the origin, conditions of use,
interpretation, or understanding  the information being exchanged or
transferred.  (Adapted from ISO/IEC 2382-17:1999 Information Technology
Vocabulary—Part 17: Databases 17.06.05 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:

Code List Identifier, which is a standardized reference to the context
or source of the set of codes

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

Appendix A, ESAR: Monitoring Location Data Structure Diagram illustrates
the hierarchical classification of the data standard. This diagram
enables business and technical users of this standard to quickly
understand its general content and complexity.  Appendix B, lists the
references for the ESAR Monitoring Location Document.

2.0 	ENVIRONMENTAL SAMPLING, ANALYSIS, AND RESULTS: MONITORING LOCATION
DIAGRAM

This diagram specifies the major data groups that may be used to
identify the characteristics and/or to catalog a monitoring location or
locations.

3.0	ENVIRONMENTAL SAMPLING, ANALYSIS, AND RESULTS: MONITORING LOCATION
DATA TABLE

1.0	Monitoring Location Point of Contact

Definition: 	Identifies the organization or person where questions about
the Monitoring Location may be directed.

Relationships:  	None.

	Notes:		Refer to the Contact Information [EX000019.2] Data Standard.

			The following items may be needed:

			Individual

				Organization

				Affiliation

				Mailing Address

				Location Address

				Telephonic

				Electronic Address

XML Tag:	MonitoringLocationPointContact

2.0	Monitoring Location Identification

Definition: 	The text or code sets and numbers that uniquely identify a
Monitoring Location.

Relationships:  	None.

Notes:		None.

XML Tag: 	MonitoringLocationIdentification

Data Element Name	Data Element Definitions	Notes	Format 	XML Tags

2.1 Monitoring Location  Identifier	A designator used to uniquely
identify the Monitoring Location.	Example List of Values:

32WAL-34.0

HAV-OU3-CW16D-0904

WGMW-9G_060804

04S10595

2420-10/MW/RW #10

CF-SD047

AQS#: 180030002

STORET#: 133318

Note: Based on the business need, additional metadata may be required to
sufficiently describe an identifier. This additional metadata is
described in the Introduction section 1.6.d.	A
MonitoringLocationIdentifier

2.2 Monitoring Location Name	The designator specified by the sampling
organization for the site at which sampling or other activities are
conducted.	Example List of Values:

Walla Walla River at Swegle Road

1018 E LARCH Ave. OSBURN, ID

PR07GF01/2420

Tillamook Bay at Station 14

Springfield Mobile Estates

Freshwater System

Potato Creek State Park

Douglas County Landfill	A	MonitoringLocationName

2.3 Monitoring Location Type Name	The descriptive name for a type of
monitoring location.	Note: Multiples of Monitoring Location Type Name
may be allowed.

Example List of Values:

NAMS	National Air Monitoring Station

SLAMS	State/Local Air Monitoring Station

Index

PSD

Industrial

Tribal

Superfund Site

Shellfish Monitoring Station	A	MonitoringLocationTypeName

2.4 Monitoring Location Description Text	Text description of the
location of the monitoring location.	Example List of Values:

Sample reach extends 100 meters downstream of station latitude/longitude

Walla Walla River at Swegle Road, river mile 34.0, sampled from right
bank

On top of Smalley school in Timberville, Oregon	A
MonitoringLocationDescriptionText

3.0	Geographic Monitoring Location

Definition: 	Provides location information about a monitoring location.

Relationships:  	None.

	Notes:		None.

XML Tag:	GeographicMonitoringLocation

3.1	Monitoring Location Latitude and Longitude Measure

Definition: 	The point on the earth of the monitoring location.

Relationships:  	None.

	Notes:		Refer to Latitude/Longitude [EX000017.2] Data Standard.

			The following items may be needed

			Latitude Measure

				Longitude Measure

				Horizontal Accuracy Measure

				Source Map Scale Number

				Coordinate Data Source Name or Code

				Horizontal Collection Method Name or Code

				Horizontal Reference Datum Name or Code, and

				Reference Point Text or Code

				Vertical Measure

				Vertical Accuracy Measure

				Vertical Collection Method Text or Code

				Vertical Reference Datum Name or Code

XML Tag:	MonitoringLocation

Data Element Name	Data Element Definitions	Notes	Format 	XML Tags

3.2 Vertical Reference Point Text

	The point or range at which the vertical measurement was established.
Note: This element may also be used in special circumstances to describe
for example, the tidal conditions at the time of measurement, such as
mean low tide, or the point on a physical structure, such as the top of
the well casing.

Example List of Values:

Mean low tide,

Top of well casing,

Probe location on stack	A	VerticalReferencePointText

3.3 Horizontal Reference Point Offset Measure

	The measure of the distance (i.e. offset) from the Monitoring Location
to the horizontal reference point.

	Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	HorizontalReferencePointOffsetMeasure

3.4 Vertical Reference Point Offset Measure

	The measure of the distance (i.e. offset) from the Monitoring Location
to the vertical reference point.

	Note: When the point of sample collection (i.e. Monitoring Location) is
above the Vertical Reference Point, this will have positive value.

Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	VerticalReferencePointOffsetMeasure

3.5 Probe Height Measure

	Distance of the probe from local ground level or vertical reference
point.	Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	ProbeHeightMeasure

3.6 Probe Vertical Distance Measure

	The vertical distance of the probe from its support structure.

	Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	ProbeVerticalDistanceMeasure

3.7 Probe Horizontal Distance Measure

	The horizontal distance of the probe from its support structure.

	Reference the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	ProbeHorizontalDistanceMeasure

4.0	Monitoring Location Attached Binary Object

	Definition: 	References documents, images, maps, photos, laboratory
materials, geospatial coverages, and other objects within the 				data
submission that pertain to the Monitoring Location.

Relationships:  	None.

Notes:		Refer to the Attached Binary Object [EX000006.1] Data Standard.

		Multiple objects may be attached to data submission for each project
included in the submission. Where a binary object is 				attached, both
the type code and the title of the file must be provided. Attached
Binary Object descriptors will adhere to 				the specified technical
standards.

XML Tag: 	MonitoringLocationAttachedBinaryObject

Monitoring Location – Supplemental Information

Note: The following data elements are supplemental information that may
be tracked for monitoring locations. In some cases, these elements are
more commonly used for a particular environmental media (e.g. Water) or
regulatory program.

5.0	Monitoring Location Influences

Definition: 	Supplemental information whose primary purpose is to
describe physical features proximate to a monitoring location that
may influence monitoring data values.

Relationships:  	None.

Notes:		None.

XML Tag: 	MonitoringLocationInfluences

5.1	Air Monitoring Location Influences

Definition: 	Supplemental information whose primary purpose is to
describe physical features proximate to a monitoring location that
may influence air monitoring data values.

Relationships:  	None.

Notes:		None.

XML Tag: 	AirMonitoringLocationInfluences

5.1.1	Road Influences

Definition: 	Proximate road features that may influence monitoring data
values.

Relationships:  	None.

Notes:		There may be any number of Road Influences/ Local Impacts.

XML Tag: 	RoadInfluences

	Data Element Name	Data Element Definitions	Notes	Format 	XML Tags

<IP_ADDRESS> Direction from Monitor to Road Code	The compass direction from
the monitor to the road at its nearest point.	Example List of Values:

NNE

W

SE	A	DirectionMonitorRoadCode

<IP_ADDRESS> Road Name	The designator for a road. 	Example List of Values:

I95

US1

Kildaire Farm Rd.

Access 1	A	RoadName

<IP_ADDRESS> Road Type Name	The type of road being described.	Example List of
Values:

Highway

Secondary

Residential	A	RoadTypeName

<IP_ADDRESS> Road Surface Type Name	The type of surface present on the road.
Example List of Values:

Paved

Unpaved 	A	RoadSurfaceTypeName

<IP_ADDRESS> Traffic Count Measure 	An estimate of the traffic volume on the
roadway.	Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	TrafficCountMeasure

<IP_ADDRESS> Traffic Count Date	The date when the traffic count value was
estimated.	Refer to the Representation of Date and Time [EX000013.1]
Data Standard.	D	TrafficCountDate

<IP_ADDRESS> Traffic Count Source Name	The agency providing the traffic count
data.	Example List of Values:

US-DOT

VA-DOT	A	TrafficCountSourceName

<IP_ADDRESS> Distance from Monitor to Road Measure 	The distance between the
sensing of air sampling equipment at a monitoring site and the nearest
edge of the roadway.	Reference the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	DistanceMonitorRoadMeasure

5.1.2	Obstruction Influences

	Definition: 	Proximate obstruction features that may influence
monitoring data values.

Relationships:  	None.

Notes:		There may be any number of Obstruction Influences/ Local
Impacts.

XML Tag: 	ObstructionInfluences

Data Element Name	Data Element Definitions	Notes	Format 	XML Tags

<IP_ADDRESS> Obstruction Identifier	A designator used to uniquely identify an
obstruction. 	Note: Based on the business need, additional metadata may
be required to sufficiently describe an identifier. This additional
metadata is described in the Introduction section 1.6.d.	A
ObstructionIdentifier

<IP_ADDRESS> Obstruction Type Name	The type of obstruction responsible for
the restricted airflow of a monitor.	Example List of Values:

Tree

Building

Outcrop	A	ObstructionTypeName

<IP_ADDRESS> Distance from Monitor to Obstruction Measure 	The distance
between a probe and obstruction.	Refer to the Measure [EX000010.1] Data
Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	DistanceMonitorObstructionMeasure

<IP_ADDRESS> Obstruction Height Measure

	The height of the top of the obstruction above a probe.	Refer to the
Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	ObstructionHeightMeasure

<IP_ADDRESS> Obstruction Width Measure

	The width of the obstruction at the height of a probe.	Refer to the
Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	ObstructionWidthMeasure

<IP_ADDRESS> Direction from Monitor to Obstruction Code	The direction from
the monitor to the obstruction.	Example List of Values:

NW

S

WSW	A	DirectionMonitorObstructionCode

5.2	Water/Waste Monitoring Location Influences

	Definition: 	Supplemental information whose primary purpose is to
describe physical features proximate to a monitoring location that
may influence water or waste monitoring data values.

Relationships:  	None.

	Notes:		Example List of Values:

Station located upgradient from Amalgamated Industries’ discharge

Station located below the spillway of Acme Dam to monitor total
dissolved gas

XML Tag:	WaterWasteMonitoringLocationInfluence

6.0	Air Emission Release Point Identification

Definition: 	Description of the characteristics of an emission release
point (usually a stack) that may be used for monitoring activities at a
facility.

Relationships:  	None.

Notes:		None.

XML Tag:	AirEmissionReleasePointIdentification

Data Element Name	Data Element Definitions	Notes	Format 	XML Tags

6.1 Air Emission Release Point Identifier	A designator used to uniquely
identify a location where emissions are released to ambient air.	Note:
Unique identifier – If no stack, then ID for fugitive release.

Note: Based on the business need, additional metadata may be required to
sufficiently describe an identifier. This additional metadata is
described in the Introduction section 1.6.d.	A
AirEmissionReleasePointIdentifier

6.2 Air Emission Release Point Type Name	A description of the physical
configuration of the release point. 	Example List of Values:

Fugitive

Vertical

Horizontal

Gooseneck

Vertical with Rain Cap

Downward Facing Vent	A	AirEmissionReleasePointTypeName

6.3	Air Emission Release Point Parameters - Stack

	Definition: 	The parameters of an emission release point if it is a
stack.

Relationships:  	None.

Notes:		These parameters may be measured, calculated, or estimated.

XML Tag:	AirEmissionReleasePointParametersStack

Data Element Name	Data Element Definitions	Notes	Format 	XML Tags

6.3.1 Air Emission Release Point Stack Height Measure 	The height of a
stack from the ground.	Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	AirEmissionReleasePointStackHeightMeasure

6.3.2 Air Emission Release Point Stack Diameter Measure

	The diameter of a stack at the release height.	Refer to the Measure
[EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	AirEmissionReleasePointStackDiameterMeasure

6.3.3 Air Emission Release Point Stack Fence Line Distance Measure 	The
measure of the horizontal distance from a stack to the nearest fence
line of a property within which the stack is located.

	Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	AirEmissionReleasePointStackFenceLineDistanceMeasure

6.3.4 Air Emission Release Point Exit Gas Temperature Measure

	The temperature of an exit gas stream.

	Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	AirEmissionReleasePointExitGasTemperatureMeasure

6.3.5 Air Emission Release Point Exit Gas Velocity Measure

	The velocity of an exit gas stream.	Refer to the Measure [EX000010.1]
Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	AirEmissionReleasePointExitGasVelocityMeasure

6.3.6 Air Emission Release Point Exit Gas Flow Rate Measure

	The value of the stack gas flow rate.	Refer to the Measure [Final
EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	AirEmissionReleasePointExitGasFlowRateMeasure

6.4	Air Emission Release Point Parameters – Fugitive

	Definition: 	The parameters of an emission release point if it is a
fugitive release point that cannot be traced to a single source point.

Relationships:  	None.

Notes:		These parameters may be measured, calculated, or estimated.

XML Tag:	AirEmissionReleasePointParametersFugitive

Data Element Name	Data Element Definitions	Notes	Format 	XML Tags

6.4.1 Air Emission Release Point Horizontal Area Fugitive Measure
Horizontal area of the source of fugitive emissions.	Refer to the
Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	AirEmissionReleasePointHorizontalAreaFugitiveMeasure

6.4.2 Air Emission Release Point Height Fugitive Measure

	Release height (above terrain) of fugitive emissions.	Refer to the
Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	AirEmissionReleasePointHeightFugitiveMeasure

7.0	Air Open Path Monitoring Location

	Definition: 	Supplemental information that more fully describes the
open path monitoring configuration, in which an energy beam 				(laser,
microwave, etc.) is sent from a transmitter to a receiver to measure
compounds in the air between the two devices.

Relationships:  	None.

Notes:		None.

XML Tag:	AirOpenPathMonitoringLocation

Data Element Name	Data Element Definitions	Notes	Format 	XML Tags

7.1 Open Path Identifier	A designator used to uniquely identify each
individual orientation of an open path measurement at a site. 	Note:
Based on the business need, additional metadata may be required to
sufficiently describe an identifier. This additional metadata is
described in the Introduction section 1.6.d.	A	OpenPathIdentifier

7.2 Open Path Transmitter Horizontal Reference Point Offset Measure 	The
measure of the distance (i.e. offset) from the Open Path Transmitter to
the horizontal reference point.	Note: This offset value may also be
valid to measure the offset distance for the Receiver as well, if a
Reflector is used and the Transmitter and Receiver are the same.

Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G
OpenPathTransmitterHorizontalReferencePointOffsetMeasure

7.3 Open Path Receiver Horizontal Reference Point Offset Measure 	The
measure of the distance (i.e. offset) from the Open Path Receiver to the
horizontal reference point.

	Note: This offset value may also be valid to measure the offset
distance for the Reflector, if the Transmitter and Receiver are the
same, or they are at the same location.

Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	OpenPathReceiverHorizontalReferencePointOffsetMeasure

7.4 Open Path Transmitter Vertical Reference Point Offset Measure 	The
measure of the distance (i.e. offset) from the Open Path Transmitter to
the vertical reference point.

	Note: When the point of sample collection (i.e. Monitoring Location) is
above the Vertical Reference Point, this will have a positive value.
This offset value may also be valid to measure the offset distance for
the Receiver as well, if a Reflector is used and the Transmitter and
Receiver are the same.

Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	OpenPathTransmitterVerticalReferencePointOffsetMeasure

7.5 Open Path Receiver Vertical Reference Point Offset Measure 	The
measure of the distance (i.e. offset) from the Open Path Receiver to the
vertical reference point.

	Note: When the point of sample collection (i.e. Monitoring Location) is
above the Vertical Reference Point, this will have a positive value.
This offset value may also be valid to measure the offset distance for
the Reflector, if the Transmitter and Receiver are the same, or they are
at the same location.

Refer to the Measure [EX000010.1] Data Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	OpenPathReceiverVerticalReferencePointOffsetMeasure

7.6 Open Path Beam Vertical Angle Measure 	Angle measure in degrees from
the horizontal at the height of the transmitter. 	Note: Angle can be
positive (i.e., upward from the horizontal) or negative (i.e., downward
from the horizontal).

Refer to the Measure [EX000010.1] Data Standard 	G
OpenPathBeamVerticalAngleMeasure

7.7 Open Path Beam Azimuth Angle Measure 	Horizontal orientation angle
of beam measured clockwise from north in degrees.	Refer to the Measure
[EX000010.1] Data Standard

Example List of Values:

90 degrees   (for East)

180 degrees  (for South) 	G	OpenPathBeamAzimuthAngleMeasure

7.8 Open Path Beam Length Measure 	The measure of the length of the open
path beam projected between the transmitter and the receiver or
reflector (as appropriate).	Refer to the Measure [EX000010.1] Data
Standard.

The following items may be needed:

Measure Value,

Measure Unit Code,

Measure Qualifier Code,

Measure QA/QC.	G	OpenPathBeamLengthMeasure

7.9 Open Path Location Land Use Text	Description of the land use of the
monitoring location used during open path monitoring. 	Note: This could
include prevalent land use under the path of the beam projected, as well
as the land use in the opposite direction of the beam transmission for a
distance at least equal to beam length.

Example List of Values:

One mile downwind from town landfill

	A	OpenPathLocationLandUseText

8.0	Waterbody Identification and Use

Definition: 	Supplemental information that more fully describes the
waterbody associated with monitoring activities and the typical use
classification of the waterbody.

Relationships:  	None.

Notes:		None.

XML Tag:	WaterbodyIdentificationAndUse

Data Element Name	Data Element Definitions	Notes	Format 	XML Tags

8.1 Waterbody Name	Name of the lake, stream, river, estuary, aquifer, or
other water body type related to the monitoring location.	Example List
of Values:

Spokane Rathdrum Prairie Aquifer

Ogallala	A	WaterbodyName

8.2 Waterbody Use Classification Text	Designated use classification of
the water body sampled, if applicable.	Example List of Values:

Fish & Widlife

Swimming

Limited Warmwater Fishery	A	WaterbodyUseClassificationText

8.2.1 Waterbody Use Classification Text Reference	Elements or attributes
that describe the bibliographic reference for the Waterbody Use
Classification.	Refer to the Bibliographic Reference [EX000007.1] Data
Standard	G	WaterbodyUseClassificationTextReference

8.3 River Mile Text	River mile where the monitoring location is located.
Example List of Values:

953.80 624.93 5.0

35.67	A	RiverMileText

8.3.1 River Mile Text Reference	Elements or attributes that describe the
bibliographic reference for the River Mile Text.	Refer to the
Bibliographic Reference [EX000007.1] Data Standard	G
RiverMileTextReference

8.4 EPA Reach Code	EPA Reach Code for the monitoring location.

A	EPAReachCode

8.4.1 EPA Reach Code Reference	Elements or attributes that describe the
bibliographic reference for the EPA Reach Code.	Refer to the
Bibliographic Reference [EX000007.1] Data Standard	G
EPAReachCodeReference

9.0	Well Information

	Definition: 	Description of the information about a well that may be
used for monitoring activities.  				.

Relationships:  None.

Notes:		Refer to the Well Information Data Standard [EX000025.2].

XML Tag:	WellInformation

Appendix A

Environmental Sampling, Analysis and Results: Monitoring Location
Structure Diagram

Appendix B

References

ISO/IEC 2382-17:1999 Information Technology Vocabulary—Part 17:
Databases 17.06.

Environmental Sampling, Analysis And Results:

Monitoring Location Data Standard

Standard No.: EX000003.2

July 22, 2008	Page   PAGE  4

Environmental Sampling, Analysis And Results:

Monitoring Location Data Standard

Standard No.: EX000003.2

July 22, 2008	Page   PAGE  24

ENVIORNMENTAL SAMPLING, ANALYSIS

AND RESULTS: MONITORING LOCATIONDATA STANDARD

Standard No.: 1-XXX

Version 1 – FINAL DRAFT

Environmental Sampling, Analysis and Results: Monitoring Location

Data Standard

4.0 Monitoring Location Attached Binary Object

3.0 Geographic Monitoring Location

2.0 Monitoring Location Identification

1.0 Monitoring Location Point of Contact

8.0 Waterbody Identification and Use

7.0 Air Open Path Monitoring Location

5.0 Monitoring Location Influences

6.0 Air Emission Release Point Identification

 Environmental Sampling, Analysis and Results: Monitoring Location Data
Standard

2.0 Monitoring Location Identification

2.1 Monitoring Location Identifier

2.2 Monitoring Location Name

2.3 Monitoring Location Type Name

2.4 Monitoring Location Description Text

3.0 Geographic Monitoring Location

3.1 Monitoring Location Lat/Long Measure

3.2 Vertical Reference Point Text

3.3 Horizontal Reference Point Offset Measure

3.4 Vertical Reference Point Offset Measure

3.5 Probe Height Measure

3.6 Probe Vertical Distance Measure

3.7 Probe Horizontal Distance Measure

4.0 Monitoring Location Attached Binary Object

9.0 Well Information Data Standard Details

1.0 Monitoring  Location Point of Contact

6.0 Air Emission Release Point Identification

6.1 Air Emission Release Point Identifier

6.2 Air Emission Release Point Type Name

6.3 Air Emission Release Point Parameters-Stack

6.3.1 Air Emission Release Point Stack Height Measure

6.3.2 Air Emission Release Point Stack Diameter Measure

6.3.3 Air Emission Release Point Stack Fence Line Distance Measure

6.3.4 Air Emission Release Point Exit Gas Temperature Measure

6.3.5 Air Emission Release Point Exit Gas Velocity Measure

6.3.6 Air Emission Release Point Exit Gas Flow Rate Measure

6.4 Air Emission Release Point Parameters – Fugitive

6.4.1 Air Emission Release Point Horizontal Area Fugitive Measure

6.4.2 Air Emission Release Point Height Fugitive Measure

5.0 Monitoring Location Influences

5.1 Air Monitoring Location Influences

5.1.1Road Influences

<IP_ADDRESS> Direction from Monitor to Road Code

<IP_ADDRESS> Road Name

<IP_ADDRESS> Road Type Name

<IP_ADDRESS> Road Surface Type

<IP_ADDRESS> Traffic Count Measure

<IP_ADDRESS> Traffic Count Date

<IP_ADDRESS> Traffic Count Source Name

<IP_ADDRESS> Distance from Monitor to Road Measure

5.1.2 Obstruction Influences

<IP_ADDRESS> Obstruction Identifier

<IP_ADDRESS> Obstruction Type Name

<IP_ADDRESS> Distance from Monitor to Obstruction Measure

<IP_ADDRESS> Obstruction Height Measure

<IP_ADDRESS> Obstruction Width Measure

<IP_ADDRESS> Direction from Monitor to Obstruction Code

5.2 Water/Waste Monitoring Location Influences

7.0 Air Open Path Monitoring Location

7.1 Open Path Identifier

7.2 Open Path Transmitter Horizontal Reference Point Offset Measure

7.3 Open Path Receiver Horizontal Reference Point Offset Measure

7.4 Open Path Transmitter Vertical Reference Point Offset Measure

7.5 Open Path Receiver Vertical Reference Point Offset Measure

7.6 Open Path Beam Vertical Angle Measure

7.7 Open Path Beam Azimuth Angle Measure

7.8 Open Path Beam Length Measure

7.9 Open Path Location Land Use Text

8.0 Waterbody Identification and Use

8.1 Waterbody Name

8.2 Waterbody Use Classification Text

8.2.1 Waterbody Use Classification Text Reference

8.3 River Mile Text

8.3.1 River Mile Text Reference

8.4 EPA Reach Code

8.4.1 EPA Reach Code Reference

9.0 Well Information


[Federal Register Volume 87, Number 156 (Monday, August 15, 2022)]
[Proposed Rules]
[Pages 50005-50009]
[FR Doc No: 2022-17140]

========================================================================
Proposed Rules
                                                Federal Register
________________________________________________________________________

This section of the FEDERAL REGISTER contains notices to the public of
the proposed issuance of rules and regulations. The purpose of these
notices is to give interested persons an opportunity to participate in
the rule making prior to the adoption of the final rules.

========================================================================

Federal Register / Vol. 87, No. 156 / Monday, August 15, 2022 /
Proposed Rules

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 39

[Docket No. FAA-2022-0992; Project Identifier MCAI-2022-00173-R]
RIN 2120-AA64

Airworthiness Directives; Bell Textron Canada Limited (Type
Certificate Previously Held by Bell Helicopter Textron Canada Limited)
Helicopters

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Notice of proposed rulemaking (NPRM).

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

SUMMARY: The FAA proposes to supersede Airworthiness Directive (AD) 99-
23-18, AD 2005-03-07, AD 2013-12-07, and AD 2014-04-07, which apply to
certain Bell Helicopter Textron Canada (now Bell Textron Canada
Limited) Model 407 helicopters. AD 99-23-18 requires revising the life
limits for certain parts, replacing each part that has exceeded its
life limit, and revising the Airworthiness Limitation Section (ALS) of
the existing maintenance manual. AD 2005-03-07 requires establishing a
maximum accumulated Retirement Index Number (RIN) count for certain
crosstube assemblies and revising the ALS of the existing maintenance
manual. AD 2013-12-07 requires inspecting the tailboom assembly for a
crack, loose rivet, or other damage and depending on the inspection
results, replacing certain parts. AD 2014-04-07 requires preflight
checking, repetitively inspecting for a crack in certain tailbooms,
modifying and re-identifying certain tailbooms, installing an improved
horizontal stabilizer assembly, and revising the ALS of the existing
maintenance manual. Since the FAA issued those ADs, a report was
received of a crack on the tailboom lower skin due to fatigue damage
and new and more restrictive airworthiness limitations have been
issued. This proposed AD would require incorporating into existing
maintenance records requirements (airworthiness limitations) as
specified in the ALS service information. The FAA is proposing this AD
to address the unsafe condition on these products.

DATES: The FAA must receive comments on this proposed AD by September
29, 2022.

ADDRESSES: You may send comments, using the procedures found in 14 CFR
11.43 and 11.45, by any of the following methods:
     Federal eRulemaking Portal: Go to 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: Deliver to Mail address between 9 a.m. and
5 p.m., Monday through Friday, except Federal holidays.
    For service information that is identified in this NPRM, contact
Bell Textron Canada Limited, 12,800 Rue de l'Avenir, Mirabel, Quebec
J7J 1R4, Canada; telephone 1-450-437-2862 or 1-800-363-8023; fax 1-450-
433-0272; email [email protected]; or at
www.bellflight.com/support/contact-support. You may view this service
information at the FAA, Office of the Regional Counsel, Southwest
Region, 10101 Hillwood Pkwy., Room 6N-321, Fort Worth, TX 76177. For
information on the availability of this material at the FAA, call (817)
222-5110.

Examining the AD Docket

    You may examine the AD docket at www.regulations.gov by searching
for and locating Docket No. FAA-2022-0992; or in person at Docket
Operations between 9 a.m. and 5 p.m., Monday through Friday, except
Federal holidays. The AD docket contains this NPRM, the Transport
Canada AD, any comments received, and other information. The street
address for Docket Operations is listed above.

FOR FURTHER INFORMATION CONTACT: Andrea Jimenez, Aerospace Engineer,
COS Program Management Section, Operational Safety Branch, Compliance &
Airworthiness Division, FAA, 1600 Stewart Ave., Suite 410, Westbury, NY
11590; telephone<PHONE_NUMBER>; email [email protected].

SUPPLEMENTARY INFORMATION:

Comments Invited

    The FAA invites you to send any written relevant data, views, or
arguments about this proposal. Send your comments to an address listed
under ADDRESSES. Include ``Docket No. FAA-2022-0992; Project Identifier
MCAI-2022-00173-R'' at the beginning of your comments. The most helpful
comments reference a specific portion of the proposal, explain the
reason for any recommended change, and include supporting data. The FAA
will consider all comments received by the closing date and may amend
this proposal because of those comments.
    Except for Confidential Business Information (CBI) as described in
the following paragraph, and other information as described in 14 CFR
11.35, the FAA will post all comments received, without change, to
www.regulations.gov, including any personal information you provide.
The agency will also post a report summarizing each substantive verbal
contact received about this NPRM.

Confidential Business Information

    CBI is commercial or financial information that is both customarily
and actually treated as private by its owner. Under the Freedom of
Information Act (FOIA) (5 U.S.C. 552), CBI is exempt from public
disclosure. If your comments responsive to this NPRM contain commercial
or financial information that is customarily treated as private, that
you actually treat as private, and that is relevant or responsive to
this NPRM, it is important that you clearly designate the submitted
comments as CBI. Please mark each page of your submission containing
CBI as ``PROPIN.'' The FAA will treat such marked submissions as
confidential under the FOIA, and they will not be placed in the public
docket of this NPRM. Submissions containing CBI should be sent to
Andrea Jimenez, Aerospace Engineer, COS Program Management Section,
Operational Safety Branch, Compliance & Airworthiness Division, FAA,
1600 Stewart Ave., Suite 410, Westbury, NY 11590; telephone (516) 228-
7330; email [email protected]. Any commentary that the FAA
receives which is not specifically designated as CBI will be placed in
the public docket for this rulemaking.

Background

    The FAA issued AD 99-23-18, Amendment 39-11414 (64 FR 61784,
November 15, 1999) (AD 99-23-18) for all Bell Helicopter Textron Canada
(now Bell Textron Canada Limited) Model 407 helicopters. AD 99-23-18
was prompted by an engineering evaluation of additional flight test
data, which resulted in redefining the service life for certain parts
and revising the ALS of the existing maintenance manual AD 99-23-18
requires before further flight, revising the life limits for certain
parts, and replacing each part that has exceeded its life limit with an
airworthy part. AD 99-23-18 also requires revising the ALS of the
existing maintenance manual to reflect these new life limits and
annotating the component history card or equivalent record with the
revised life limits.
    The FAA issued AD 2005-03-07, Amendment 39-13963 (70 FR 7016,
February 10, 2005) (AD 2005-03-07) for Bell Helicopter Textron Canada
(now Bell Textron Canada Limited) Model 407 helicopters with landing
gear crosstube assemblies, part number (P/N) 407-050-101-101 and -103;
P/N 407-050-102-101 and -103; P/N 407-050-201-101 and -103; P/N 407-
050-202-101 and -103; P/N 407-704-007-119; P/N 407-722-101; P/N 407-
723-104; P/N 407-724-101; or P/N 407-725-104, installed. AD 2005-03-07
was prompted by fatigue testing, analysis, and evaluation by the
manufacturer that determined that run-on landings impose a high stress
on landing gear or crosstubes and may cause cracking in the area above
the skid tube saddle. AD 2005-03-07 requires before further flight,
establishing a component history card or equivalent record, converting
accumulated run-on landings to an accumulated RIN count, and
establishing a maximum accumulated RIN for certain crosstube
assemblies. AD 2005-03-07 also requires replacing any crosstube
assembly before it exceeds the maximum RIN life limit and revising the
ALS of the existing maintenance manual to reflect this new life limit.
    The FAA issued AD 2013-12-07, Amendment 39-17485 (78 FR 38546, June
27, 2013) (AD 2013-12-07) for Bell Helicopter Textron Canada (now Bell
Textron Canada Limited) Model 407 helicopters with tailboom assembly P/
N 407-030-801-201, 407-030-801-203, or 407-030-801-205, installed. AD
2013-12-07 was prompted by a stress analysis of the tailboom skin that
revealed that high-stress-concentration areas are susceptible to skin
cracking. AD 2013-12-07 requires for tailboom assemblies with 8,600 or
more hours time-in-service (TIS), or with an unknown number of hours
TIS, before the first flight of each day, inspecting the tailboom
assembly for a crack; or within 25 hours TIS, or 30 days, whichever
comes first, and thereafter at intervals not to exceed 50 hours TIS,
inspecting for a crack around each fastener and above the edge of the
upper stabilizer support. AD 2013-12-07 also requires for certain
tailboom assemblies with 6,900 or more hours TIS, within 25 hours TIS
or 30 days, whichever occurs first, inspecting the tailboom assembly
for a crack by using either a 10X or higher power magnifying glass and
thereafter inspecting at intervals not to exceed 150 hours TIS; or by
eddy current inspecting and thereafter inspecting at intervals not to
exceed 500 hours TIS.
    Additionally, AD 2013-12-07 requires, within 100 hours TIS or at
the next tailboom inspection, whichever occurs first, and thereafter at
intervals not to exceed 300 hours TIS, inspecting the tailboom assembly
for a crack, loose rivet, or other damage. Depending on the inspection
results, AD 2013-12-07 requires if there is a crack, before further
flight replacing the tailboom assembly with an airworthy part.
    The FAA issued AD 2014-04-07, Amendment 39-17766 (79 FR 35481, June
23, 2014) (AD 2014-04-07) for Bell Helicopter Textron Canada (now Bell
Textron Canada Limited) Model 407 helicopters serial numbers (S/Ns)
53000 through 53475, with tailboom P/N 407-030-801-101, -105, or -107,
or 407-530-014-101 or -103, installed. AD 2014-04-07 was prompted by
additional reports of cracked tailboom skins. AD 2014-04-07 requires
for certain part-numbered tailbooms that have not been modified,
conducting daily preflight checks of the tailboom for a crack; and for
tailbooms with 600 or more hours TIS, within 25 hours TIS, and
thereafter at intervals not to exceed 50 hours TIS, visually inspecting
the tailboom for a crack using a 10X or higher power magnifying glass,
and within 600 hours TIS but not later than 30 days modifying and re-
identifying certain part-numbered tailbooms, and installing an improved
horizontal stabilizer assembly. AD 2014-04-07 also requires for certain
part-numbered tailbooms, after the modification, before further flight,
establishing a component history card or equivalent record, and
revising the existing ALS of the maintenance manual to reflect a new
life limit.
    AD 2014-04-07 also requires, for certain part-number tailbooms,
within 25 hours TIS or 30 days, whichever occurs first, daily visual
inspections of the tailboom for a crack, and within 100 hours TIS and
thereafter at intervals not to exceed 100 hours TIS, using a 10X or
higher power magnifying glass, inspecting each tailboom for a loose
rivet, crack, skin corrosion, or any other damage. Depending on the
inspection results, AD 2014-04-07 requires corrective actions,
including, if there is a crack, replacing the tailboom assembly before
further flight.

Actions Since AD 99-23-18, AD 2005-03-07, AD 2013-12-07, and AD 2014-
04-07 Were Issued

    Since the FAA issued AD 99-23-18, AD 2005-03-07, AD 2013-12-07, and
AD 2014-04-07, Transport Canada, which is the aviation authority for
Canada, issued AD CF-2021-34, dated October 22, 2021 (Transport Canada
AD CF-2021-34), to correct an unsafe condition for Bell Textron Canada
Limited Model 407 helicopters, S/N 53000 through 53900, 53911 through
54166, and 54300 and subsequent. Transport Canada advises of a report
of a crack on the tailboom lower skin due to fatigue damage, which
could affect the structural integrity of the tailboom. Transport Canada
advises that Bell Textron Canada Limited issued a revision to the ALS,
which adds a new inspection zone for tailboom assemblies to address the
unsafe condition.
    Accordingly, Transport Canada AD CF-2021-34 requires compliance
with Bell BHT-407-MPI, Chapter 04, ALS, Issue 3, dated June 21, 2021,
of Bell Model 407 Maintenance Planning Information, PMC-407-97499-
01000-00, Issue No. 005, dated July 6, 2022 (BHT-407-MPI, ALS Issue 3),
which includes maintenance tasks and life limits for the tailboom and
other parts. The FAA is proposing this AD to prevent failure of a part,
which could result in loss of control of the helicopter.
    Additionally, although AD 99-23-18 and AD 2005-03-07 were prompted
by unsafe conditions not related to the tailboom crack that prompted
this proposed AD, the actions required to address the unsafe conditions
in AD 99-23-18 and AD 2005-03-07 are included in BHT-407-MPI, ALS Issue
3. Therefore, the FAA is superseding AD 99-23-18, AD 2005-03-07, AD
2013-12-07, and AD 2014-04-07, in order to reduce the burden on
operators by requiring compliance with a single AD in lieu of multiple
FAA ADs.
    AD 99-23-18 requires reducing the life limit for drive ring set P/N
406-010-126-107 from 49,000 RIN to 48,000 RIN, and replacing each part
that has exceeded its life limit. BHT-407-MPI, ALS Issue 3 states the
life limit for drive

ring set P/N 406-010-126-107 is 100,000 RIN.
    AD 2005-03-07 requires establishing a maximum accumulated RIN for
certain crosstube assemblies of 5,000 RIN and replacing any crosstube
assembly before it exceeds the maximum accumulated RIN. BHT-407-MPI,
ALS Issue 3 adds an additional life limit to certain part-numbered
crosstube assemblies of 2,500 landings or 5,000 RIN.
    AD 2013-12-07 requires for tailboom assemblies with P/N 407-030-
801-201, 407-030-801-203, or 407-030-801-205 and with 8,600 or more
hours TIS, or with an unknown number of hours TIS, inspecting the
tailboom assembly for a crack within 25 hours TIS or 30 days, whichever
comes first; and thereafter at intervals not to exceed 50 hours TIS,
inspecting for a crack. AD 2013-12-07 also requires for tailboom
assemblies with 6,900 or more hours TIS, inspecting the tailboom
assembly for a crack within 25 hours TIS or 30 days, whichever comes
first. Thereafter AD 2013-12-07 requires either inspecting using a 10X
or higher power magnifying glass and thereafter repeating that
inspection at intervals not to exceed 150 hours TIS or eddy current
inspecting and thereafter repeating the eddy current inspection at
intervals not to exceed 500 hours TIS. AD 2013-12-07 also requires
within 100 hours TIS or at the next tailboom inspection, whichever
comes first, and thereafter at intervals not to exceed 300 hours TIS,
inspecting the tailboom assembly for a loose rivet, crack, or other
damage.
    BHT-407-MPI, ALS Issue 3 adds tailboom assembly P/N 407-530-013-105
and successive dash numbers, and also specifies for tailboom assembly
P/N 407-530-013-105 and successive dash numbers and P/N 407-030-801-201
and successive dash numbers, inspecting for a crack every 300 hours;
and for tailbooms that have accumulated 6,900 or more hours in service
inspecting every 150 hours using a 10X magnifying glass inspection
method, or eddy current inspecting every 500 hours; and for tailboom
assemblies that have accumulated 8,600 or more hours in service, or
with total time unknown, inspecting for a crack either with a daily
visual inspection or with a 10X magnifying glass inspection method at
intervals not to exceed 50 hours. Additionally, BHT-407-MPI, ALS Issue
3 specifies additional inspection zones, intervals, and criteria.
    AD 2014-04-07 requires modifying and re-identifying tailboom P/N
407-030-801-101 as 407-530-014-101, and P/N 407-030-801-105 as P/N 407-
530-014-103. AD 2014-04-07 also requires for tailboom P/N 407-530-014-
101 and -103, and P/N 407-030-801-107, establishing a retirement life
of 5,000 hours TIS, and daily checks for a crack and recurring
inspections using a 10X or higher power magnifying glass at intervals
not to exceed 100 hours TIS for a loose rivet, a crack, skin corrosion,
or other damage. BHT-407-MPI, ALS Issue 3 specifies for tailboom P/N
407-530-014-101 and successive dash numbers, and P/N 407-030-801-107
and successive dash numbers, daily and recurring inspections for a
crack every 100 hours TIS. BHT-407-MPI, ALS Issue 3 also revises the
inspection areas.

FAA's Determination

    These helicopters have been approved by the aviation authority of
Canada and are approved for operation in the United States. Pursuant to
the FAA's bilateral agreement with Canada, Transport Canada, its
technical representative, has notified the FAA of the unsafe condition
described in its AD. The FAA is proposing this AD after evaluating all
known relevant information and determining that the unsafe condition
described previously is likely to exist or develop on other helicopters
of the same type design.

Related Service Information Under 1 CFR Part 51

    The FAA reviewed BHT-407-MPI, ALS Issue 3, which specifies certain
actions and associated thresholds and intervals, including life limits
and maintenance tasks. These requirements (airworthiness limitations)
include new inspection zones and new maintenance tasks (e.g.,
inspections for cracks) with new compliance times.
    This service information is reasonably available because the
interested parties have access to it through their normal course of
business or by the means identified in the ADDRESSES section.

Proposed AD Requirements in This NPRM

    This proposed AD would supersede AD 99-23-18, AD 2005-03-07, AD
2013-12-07, and AD 2014-04-07, and would require incorporating into
existing maintenance records requirements (airworthiness limitations),
which are identified in BHT-407-MPI, ALS Issue 3, as described
previously.

ADs Mandating Airworthiness Limitations

    The FAA has previously mandated airworthiness limitations by
mandating each airworthiness limitation task (e.g., inspections and
replacements (life limits)) as an AD requirement or issuing ADs that
require revising the ALS of the existing maintenance manual or
instructions for continued airworthiness to incorporate new or revised
inspections and life limits. This proposed AD, however, would require
operators to incorporate into maintenance records required by 14 CFR
91.417(a)(2) or 135.439(a)(2), as applicable for your rotorcraft, the
requirements (airworthiness limitations) identified in the ALS service
information, as described previously. The FAA does not intend this as a
substantive change. For these ADs, the ALS requirements for operators
are the same but are complied with differently. Requiring the
incorporation of the new ALS requirements into the existing maintenance
records, rather than requiring individual ALS tasks (e.g., repetitive
inspections and replacements), requires operators to record AD
compliance once after updating the maintenance records, rather than
after every time the ALS task is completed.

Differences Between This Proposed AD and Transport Canada AD CF-2021-34
or the Service Information

    Transport Canada AD CF-2021-34 does not supersede any previously
issued Transport Canada ADs, whereas this proposed AD would supersede
FAA AD 99-23-18, AD 2005-03-07, AD 2013-12-07, and AD 2014-04-07. The
airworthiness limitations specified in Transport Canada AD CF-2021-34
encompass the requirements of AD 99-23-18, AD 2005-03-07, AD 2013-12-
07, and AD 2014-04-07.
    Additionally, Transport Canada AD CF-2021-34 is applicable to
certain serial-numbered Bell Textron Canada Limited Model 407
helicopters, whereas this proposed AD would be applicable to all
serial-numbered Model 407 helicopters.
    The service information specifies replacing each component before
exceeding the applicable airworthiness life limit, accomplishing all
applicable maintenance tasks within the defined thresholds and
intervals, and performing the specified corrective action(s) if a
defect is found during the inspection, whereas this proposed AD would
require incorporating requirements (airworthiness limitations) into
existing maintenance records within 30 days after the effective date of
the AD.

Costs of Compliance

    The FAA estimates that this AD, if adopted as proposed, would
affect 791 helicopters of U.S. Registry. Labor rates are estimated at
$85 per work-hour. Based on these numbers, the FAA

estimates the following costs to comply with this proposed AD.
    Incorporating requirements (airworthiness limitations) into
existing maintenance records would take about 2 work-hours for an
estimated cost of $170 per helicopter and $134,470 for the U.S. fleet.

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.
    The FAA is 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

    The FAA 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, I certify this proposed regulation:
    (1) Is not a ``significant regulatory action'' under Executive
Order 12866,
    (2) Would not affect intrastate aviation in Alaska, and
    (3) Would not have a significant economic impact, positive or
negative, on a substantial number of small entities under the criteria
of the Regulatory Flexibility Act.

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

0
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]

0
2. The FAA amends Sec.  39.13 by:
0
a. Removing Airworthiness Directive 99-23-18, Amendment 39-11414 (64 FR
61784, November 15, 1999); Airworthiness Directive 2005-03-07,
Amendment 39-13963 (70 FR 7016, February 10, 2005); Airworthiness
Directive 2013-12-07, Amendment 39-17485 (78 FR 38546, June 27, 2013);
and Airworthiness Directive 2014-04-07, Amendment 39-17766 (79 FR
35481, June 23, 2014); and
0
b. Adding the following new airworthiness directive:

Bell Textron Canada Limited (Type Certificate Previously Held by
Bell Helicopter Textron Canada Limited): Docket No. FAA-2022-0992;
Project Identifier MCAI-2022-00173-R.

(a) Comments Due Date

    The FAA must receive comments on this airworthiness directive
(AD) by September 29, 2022.

(b) Affected ADs

    This AD replaces the ADs specified in paragraphs (b)(1) through
(4) of this AD.
    (1) AD 99-23-18, Amendment 39-11414 (64 FR 61784, November 15,
1999).
    (2) AD 2005-03-07, Amendment 39-13963 (70 FR 7016, February 10,
2005).
    (3) AD 2013-12-07, Amendment 39-17485 (78 FR 38546, June 27,
2013).
    (4) AD 2014-04-07, Amendment 39-17766 (79 FR 35481, June 23,
2014).

    Note 1 to paragraph (b): The requirements of this AD capture the
latest tasks and life limits required to prevent the unsafe
conditions addressed by the ADs that are identified in paragraphs
(b)(1) through (4) of this AD.

(c) Applicability

    This AD applies to all Bell Textron Canada Limited (type
certificate previously held by Bell Helicopter Textron Canada
Limited) Model 407 helicopters, certificated in any category.

(d) Subject

    Joint Aircraft Service Component (JASC) Code: 5300, Fuselage
Structure.

(e) Unsafe Condition

    This AD was prompted by a report of a crack on the tailboom
lower skin due to fatigue damage and the issuance of new and more
restrictive airworthiness limitations. The FAA is issuing this AD to
prevent failure of a part, which could result in loss of control of
the helicopter.

(f) Compliance

    Comply with this AD within the compliance times specified,
unless already done.

(g) Required Actions

    Within 30 days after the effective date of this AD, incorporate
into maintenance records required by 14 CFR 91.417(a)(2) or
135.439(a)(2), as applicable for your helicopter, the requirements
(airworthiness limitations) specified in Bell BHT-407-MPI, Chapter
04, Airworthiness Limitations Schedule, Issue 3, dated June 21,
2021, of Bell Model 407 Maintenance Planning Information, PMC-407-
97499-01000-00, Issue No. 005, dated July 6, 2022.

(h) Provisions for Alternative Requirements (Airworthiness Limitations)

    After the actions required by paragraph (g) of this AD have been
done, no alternative requirements (airworthiness limitations) are
allowed unless they are approved as an alternative method of
compliance (AMOC) in accordance with the procedures specified in
paragraph (j)(1) of this AD.

(i) Special Flight Permits

    Special flight permits may be issued in accordance with 14 CFR
21.197 and 21.199, provided no passengers are onboard.

(j) Alternative Methods of Compliance (AMOCs)

    (1) The Manager, International Validation Branch, 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 manager of the International Validation Branch, send
it to the attention of the person identified in paragraph (k)(1) of
this AD. Information may be emailed to: [email protected].
    (2) 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.

(k) Related Information

    (1) For more information about this AD, contact Andrea Jimenez,
Aerospace Engineer, COS Program Management Section, Operational
Safety Branch, Compliance & Airworthiness Division, FAA, 1600
Stewart Ave., Suite 410, Westbury, NY 11590; telephone (516) 228-
7330; email [email protected].
    (2) For service information identified in this AD, contact Bell
Textron Canada Limited, 12,800 Rue de l'Avenir, Mirabel, Quebec J7J
1R4, Canada; telephone 1-450-437-2862 or 1-800-363-8023; fax 1-450-
433-0272; email [email protected]; or at
www.bellflight.com/support/contact-support. You may view this
referenced service information at the FAA, Office of the Regional
Counsel, Southwest Region, 10101 Hillwood Pkwy., Room 6N-321, Fort
Worth, TX 76177. For information on the availability of this
material at the FAA, call<PHONE_NUMBER>.

    (3) The subject of this AD is addressed in Transport Canada AD
CF-2021-34, dated October 22, 2021. You may view the Transport
Canada AD on the internet at www.regualtions.gov in Docket No. FAA-
2022-0992.

    Issued on August 4, 2022.
Christina Underwood,
Acting Director, Compliance & Airworthiness Division, Aircraft
Certification Service.
[FR Doc. 2022-17140 Filed 8-12-22; 8:45 am]
BILLING CODE 4910-13-P


[Federal Register Volume 79, Number 105 (Monday, June 2, 2014)]
[Notices]
[Page 31324]
[FR Doc No: 2014-12637]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Docket No. EL14-54-000]

Great River Energy; Notice of Petition for Partial Waiver

    Take notice that on May 16, 2014, pursuant to section 292.402 of
the Federal Energy Regulatory Commission's (Commission) regulations, 18
CFR 292.402, Great River Energy (Great River), on behalf of itself and
its twenty ``all-requirements'' electric distribution cooperative
member-owners (collectively, Participating Members) \1\ filed a
petition for a partial waiver of certain obligations imposed on Great
River and the Participating Members under sections 292.303(a) and
292.303(b) of the Commission's Regulations \2\ implementing section 210
of the Public Utility Regulatory Policies Act of 1978, as amended.\3\
---------------------------------------------------------------------------

    \1\ The Participating Members joining in this petition include
all of Great River's ``all-requirements'' members which members
purchase substantially all of their electric requirements from Great
River, including: Arrowhead Cooperative; BENCO Electric Cooperative;
Brown County Rural Electrical Association, Connexus Energy;
Cooperative Light & Power; Dakota Electric Association; East Central
Energy; Goodhue County Cooperative Electric Association; Itasca-
Mantrap Cooperative Electrical Association; Kandiyohi Power
Cooperative; Lake Country Power; Lake Region Electric Cooperative;
McLeod Cooperative Power Association; Mille Lacs Energy Cooperative;
Nobles Cooperative Electric; North Itasca Electric Cooperative;
Runestone Electric Association; Stearns Electric Association;
Steele-Waseca Cooperative Electric; and Todd-Wadena Electric
Cooperative. Great River has eight other members who are not ``all-
requirements'' members of Great River and who are not Participating
Members for the purpose of this petition.
    \2\ 18 CFR 292.303(a) and (b).
    \3\ 16 U.S.C. 824a-3.
---------------------------------------------------------------------------

    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. On or
before the comment date, it is not necessary to serve motions to
intervene or protests on persons other than the Applicant.
    The Commission encourages electronic submission of protests and
interventions in lieu of paper using the ``eFiling'' link at http://www.ferc.gov. Persons unable to file electronically should submit an
original and 5 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 email
notification when a document is added to a subscribed docket(s). For
assistance with any FERC Online service, please email
<EMAIL_ADDRESS>or call<PHONE_NUMBER> (toll free). For
TTY, call<PHONE_NUMBER>.
    Comment Date: 5:00 p.m. Eastern Time on June 6, 2014.

    Dated: May 23, 2014.
Kimberly D. Bose,
 Secretary.
[FR Doc. 2014-12637 Filed 5-30-14; 8:45 am]
BILLING CODE 6717-01-P


[Federal Register Volume 83, Number 160 (Friday, August 17, 2018)]
[Rules and Regulations]
[Page 40986]
[FR Doc No: 2018-17800]

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

DEPARTMENT OF HOMELAND SECURITY

Coast Guard

33 CFR Part 117

[Docket No. USCG-2018-0676]

Drawbridge Operation Regulation; Willamette River at Portland, OR

AGENCY: Coast Guard, DHS.

ACTION: Notice of deviation from drawbridge regulation; modification.

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

SUMMARY: The Coast Guard has modified a temporary deviation from the
operating schedule that governs the Hawthorne Bridge crosses the
Willamette River, mile 13.1, at Portland, OR. The deviation is
necessary to accommodate a filming event for a movie. This modified
deviation changes the period the bridge is authorized to remain in the
closed-to-navigation position.

DATES: This modified deviation is effective from 6 p.m. on September 8,
2018, to 12:01 a.m. on September 9, 2018.

ADDRESSES: The docket for this deviation, USCG-2018-0676 is available
at http://www.regulations.gov. Type the docket number in the ``SEARCH''
box and click ``SEARCH.'' Click on Open Docket Folder on the line
associated with this deviation.

FOR FURTHER INFORMATION CONTACT: If you have questions on this
modification, call or email Mr. Steven Fischer, Bridge Administrator,
Thirteenth Coast Guard District; telephone<PHONE_NUMBER>, email [email protected].

SUPPLEMENTARY INFORMATION: On July 19, 2018, we published a temporary
deviation entitled ``Drawbridge Operation Regulation; Willamette River
at Portland, OR'' in the Federal Register (83 FR 34041). That temporary
deviation allowed the subject bridge to not open to marine vessels from
6 p.m. on September 1, 2018 to 12:01 a.m. on September 2, 2018.
Multnomah County, the bridge owner, requested a modification of the
current published deviation to the following times: 6 p.m. on September
8, 2018, to 12:01 a.m. on September 9, 2018. This change is due to
scheduling issues with the filming crew for a movie.
    The Hawthorne Bridge provides a vertical clearance of 49 feet in
the closed-to-navigation position referenced to the vertical clearance
above Columbia River Datum 0.0. The subject bridge operates per 33 CFR
117.897(c)(3)(v). Waterway usage on this part of the Willamette River
includes vessels ranging from commercial tug and barge to small
pleasure craft. The Coast Guard requested objections to this
modification from local mariners via email. No objections were
submitted to us. Waterway usage on this part of the Willamette River
includes vessels ranging from commercial tug and barge to small
pleasure craft.
    Vessels able to pass through the bridge in the closed-to-navigation
position may do so at any time. The bridge will be able to open for
emergencies, and there is no immediate alternate route for vessels to
pass. The Coast Guard will inform the users of the waterway, through
our Local and Broadcast Notices to Mariners, of the change in operating
schedule for the bridge so that vessel operators can arrange their
transits to minimize any impact caused by the temporary deviation.
    In accordance with 33 CFR 117.35(e), the drawbridge must return to
its regular operating schedule immediately at the end of the effective
period of this temporary deviation. This deviation from the operating
regulations is authorized under 33 CFR 117.35.

    Dated: August 9, 2018.
Steven M. Fischer,
Bridge Administrator, Thirteenth Coast Guard District.
[FR Doc. 2018-17800 Filed 8-16-18; 8:45 am]
 BILLING CODE 9110-04-P