Pipelines Archives - Page 6 of 9 - FracTracker Alliance

The Falcon: Class Locations, Buildings & Recreational Areas

January 25, 2018/by FracTracker Alliance

Part of the Falcon Public EIA Project

In this segment of the Falcon Public EIA Project we begin to explore the different ways that pipelines are assessed for potential risk to populated areas. We outline a methods dictated by the Pipeline and Hazardous Materials Safety Administration (PHMSA) called Class Locations. This methods identifies occupied structures in proximity to a pipeline.

Quick Falcon Facts

67% of the Falcon route will qualify as Class 1, 27% as Class 2, and 3% as Class 3.
More than 557 single family residences and 20 businesses within 660ft of the pipeline.
Three recreational parks and a planned luxury housing development also at risk.

Map of Falcon Class Locations

The following map will serve as our guide in breaking down the Falcon’s Class Locations. Expand the map full-screen to explore its contents in greater depth. Some layers only become visible as you zoom in. A number of additional layers are not shown by default, but can be turned on in the “layers” tab. Click the “details” tab in full-screen mode to read how the different layers were created.

View Map Fullscreen | How FracTracker Maps Work

Pipeline Class Locations

Pipeline “Class locations” determine certain aspects of how a pipeline is constructed. Essentially, a pipeline’s route is segmented into lengths that are each given different classifications as outlined in PHMSA guidelines. In general terms, a segment’s Class is established by first calculating a buffer that extends 220 yards (660ft) on either side of the pipeline’s center in 1-mile continuous lengths. This buffer area is then analyzed for how many building structures are present. Classes are then assigned to each 1-mile segment using the follow criteria:

Class 1: a segment with 10 or fewer buildings intended for human occupancy
Class 2: a segment with more than 10, but less than 46 buildings intended for human occupancy
Class 3: a segment with 46 or more buildings intended for human occupancy, or where the pipeline lies within 100 yards of any building, or small well-defined outside area occupied by 20 or more people on at least 5 days a week for 10 weeks in any 12-month period (i.e. schools, businesses, recreation areas, churches)
Class 4: a segment where buildings with four or more stories aboveground are prevalent

The finer details of these calculations and their adjustments are complex, however. For instance, Class locations can be shortened to less than 1-mile lengths if building densities change dramatically in an certain area. The example image below shows one of the ways available to operators for doing this, called the “continuous sliding” method:

Calculating Class Locations
(source: PHMSA)

Class location designations may also be adjusted over time as densities change. For instance, if new homes were built in proximity to a previously constructed pipeline, the operator may be required to reduce their operating pressure, strengthen the pipeline, or conduct pressure tests to ensure the segment would technically meet the requirements of a higher Class. Alternatively, operators can apply for a special permit to avoid such changes.

What Class Locations Dictate

Pipeline segments with higher Classes must meet more rigorous safety standards, which are enforced either by PHMSA or by their state equivalent, such as the Pennsylvania Utility Commission. These include:

Soil depth: Class 1 locations must be installed with a minimum soil depth of 30 inches (18 inches in consolidated rock). Class 2, 3, and 4 locations require a minimum soil depth of 36 inches (24 inches in consolidated rock)
Shut-off valves: Class locations determine the maximum distance from shut-off valves to populated areas, as follows: Class 1 (10 miles), Class 2 (7.5 miles), Class 3 (4 miles), and Class 4 (2.5 miles).
Operating pressure: Classes also regulate the maximum allowable operating pressure (MAOP) of pipeline segments
Structural integrity: Classes determine where thicker walled materials must be used to withstand higher pressures, as well as different structural testing methods used in safety inspections

By replicating the 600 foot buffer from the Falcon’s centerline (used as the standard distance for determining Class Locations) we found that 67% of the Falcon route will qualify as Class 1, 27% as Class 2, and 3% as Class 3. These are represented on our interactive maps as green, yellow, and orange segments, respectively. An additional segment is marked as having an “unknown” Class on our maps (shaded in gray). This is the stretch crossing the Ohio River, where Shell’s Class location analysis has not been updated to reflect the route change that occurred in the summer of 2017.

Residential Structures

In total, there are 557 single family residences, 20 businesses, and a church within the 660ft buffer. Shell’s data also identify non-occupied structures along the route, such as sheds, garages, and other outbuildings. There are 535 such structures, but we did not have the time to replicate the locations of these sites. It is also important to note that the points on our interactive map represent only those identified by Shell, which we believe is an incomplete assessment of occupied structures based on our quick review of satellite maps.

Three residential structures lie directly within the 50-foot right-of-way. One of these homes, located in a Class 2 segment in Independence Township, is shown below. The Falcon will come as close as 20 feet to the edge of the structure and surround the home on three sides.

An occupied residence in the right-of-way

Neighborhoods in the following five communities account for the entirety of Falcon’s Class 3 locations. These would be considered the most “at risk” areas along the route in terms of proximity to the number of occupied structures. For instance, below is a satellite view of the Class 3 section of Raccoon Township.

Rumley Township, Harrison OH
Knox Township, Jefferson County OH
Raccoon Township, Beaver County PA
Independence Township, Beaver County PA
Mount Pleasant Township, Washington County PA

Raccoon Township residences & Municipal Park in a Class 3

Recreational Areas

In the above image we also see the location of Raccoon Township Municipal Park (in purple), home to a number of ballfields. Two similar recreation areas are located in the 660ft Class Location buffer: Mill Creek Ballpark, in Beaver County PA, and Clinton Community Park, in Allegheny County PA.

However, the Raccoon Township park is notable in that the Falcon cuts directly through its property boundary. Shell intends to bore under the park using HDD techniques, as stated in their permit applications, “to avoid disturbance to Beaver County baseball field/recreational park,” also stating that, “this HDD may be removed if the recreational group will allow laying the pipeline along the entrance roadway.”

New Housing Developments

One discovery worth attention is that the Falcon runs straight through an under-construction luxury housing development. Located in Allegheny County, PA, its developer, Maronda Homes, bills this growing community as having “picturesque landscapes, waterfront views and a peaceful collection of homes.” Shell mentions this development in their permit applications, stating:

Maronda Homes is in the planning and design stage of a very large housing development and SPLC [Shell Pipeline LC] worked closely with the developer and the Project was rerouted to avoid most of the housing sites.

It stands to reason that this neighborhood will eventually rank as one of the densest Class 3 areas along the Falcon route. Whether or not the pipeline is updated with higher safety standards as a result remains to be seen. The image below illustrates where the Falcon will go relative to lots marked for new homes. This property lots diagram was obtained from Shell’s GIS data layer and can be viewed on the FracTracker interactive map as well.

The Falcon intersects a luxury home development

1/31/18 Note: the Pittsburg Post-Gazette obtained newer lot line records for a portion of the Maronda Farms during their investigation into this story. These new records appear to have some alterations to the development, as seen below.

Maronda Farms, updated lot lines

Issues with Setbacks

There are no setback restrictions for building new homes in proximity to a pipeline. Parcels will eventually be sectioned off and sold to home buyers, begging the question of whether or not people in this community will realize a hazardous liquid pipeline runs past their driveways and backyards. This is a dilemma that residents in a similar development in Firestone, Colorado, are now grappling with following a recent pipeline explosion that killed two people, seen below, due to inadequate building setbacks.

A pipeline explodes in a Colorado home development
(source: InsideEnergy, CO)

Interestingly, we researched these same Maronda Farms parcels in FracTracker’s Allegheny County Lease Mapping Project only to discover that Maronda Homes also auctioned off their mineral rights for future oil and gas drilling. New homeowners would become victims of split-estate, where drilling companies can explore for oil and gas without having to seek permission from property owners, amplifying their level of risk.

* * *

Falcon Project Home

The Falcon: High Consequence Areas & Potential Impact Zones

January 24, 2018/by FracTracker Alliance

Part of the Falcon Public EIA Project

In this segment of the Falcon Public EIA Project we continue to explore the different ways that pipelines are assessed for potential risk – in this case, relative to population centers, drinking water systems, and sensitive habitats. We outline methods dictated by the Pipeline and Hazardous Materials Safety Administration (PHMSA) called “high consequence areas” (HCAs) and how they determine potential impact zones for highly volatile liquid (HVL) pipelines. These methods are then applied to the Falcon to understand its possible dangers.

Quick Falcon Facts

An estimated 940-foot potential impact radius (PIR)
60 of 97 pipeline miles qualifying as High Consequence Areas (HCA)
More than 8,700 people living in the “vapor zone”
5 schools, 6 daycare centers, and 16 emergency response centers in “vapor zone”
In proximity to 8 source-water (drinking water) protection areas
Affecting habitats populated by 11 endangered, protected, or threatened species

Map of Falcon High Consequence Areas

The following map will serve as our guide in breaking down the Falcon’s High Consequence Areas. Expand the map full-screen to explore its contents in greater depth. Some layers only become visible as you zoom in. A number of additional layers are not shown by default, but can be turned on in the “layers” tab. Click the “details” tab in full-screen mode to read how the different layers were created.

View Map Fullscreen | How FracTracker Maps Work

High Consequence Areas

While Class Locations, discussed in a prior project article, dictate the construction and maintenance of a pipeline, high consequence areas (HCAs) designate when operators must implement integrity management programs (IMP) where pipeline failures could cause major impacts to populated areas, as well as drinking water systems and ecological resources — otherwise defined as unusually sensitive areas (USAs).

Populated Areas

Two considerations are used when determining pipeline proximity to population centers:

High Population Areas – an urbanized area delineated by the Census Bureau as having 50,000 or more people and a population density of at least 1,000 people per square mile; and
Other Populated Areas – a Census Bureau designated “place” that contains a concentrated population, such as an incorporated or unincorporated city, town, village, or other designated residential or commercial area – including work camps.

USAs: Drinking Water

PHMSA’s definition of drinking water sources include things such as:

Community Water Systems (CWS) – serving at least 15 service connections and at least 25 year-round residents
Non-transient Non-community Water Systems (NTNCWS) – schools, businesses, and hospitals with their own water supplies
Source Water Protection Areas (SWPA) for a CWS or a NTNCWS
Wellhead Protection Areas (WHPA)
Sole-source karst aquifer recharge areas

These locations are typically supplied by regulatory agencies in individual states.

With the exception of sole-source aquifers, drinking water sources are only considered if they lack an alternative water source. However, PHMSA is strict on what alternative source means, stating that they must be immediately usable, of minimal financial impact, with equal water quality, and capable of supporting communities for at least one month for a surface water sources of water and at least six months for a groundwater sources.

One very important note in all of these “drinking water” USA designations is that they do not include privately owned groundwater wells used by residences or businesses.

USAs: Ecological Resource

Ecological resource areas are established based on any number of qualities with different variations. In general terms, they contain imperiled, threatened, or endangered aquatic or terrestrial species; are known to have a concentration of migratory waterbirds; or are a “multi-species assemblage” area (where three or more of the above species can be found).

Calculating HCAs

Like Class locations, HCAs are calculated based on proximity. The first step in this process is to determine the pipeline’s Potential Impact Radius (PIR) — the distance beyond which a person standing outdoors in the vicinity of a pipeline rupture and fire would have a 99% chance of survival; or in which death, injury, or significant property damage could occur. PIR is calculated based on the pipeline’s maximum allowable operating pressure (MAOP), diameter, and the type of gas. An example of this calculation is demonstrated in FracTracker’s recent article on the Mariner East 2 pipeline’s PIR.

Once the PIR is known, operators then determine HCAs in one of two ways, illustrated in the image below:

Method 1: A Class 3 or Class 4 location, or a Class 1 or Class 2 location where “the potential impact radius is greater than 660 feet (200 meters), and the area within a potential impact circle contains 20 or more buildings intended for human occupancy”; or a Class 1 or Class 2 location where “the potential impact circle contains an “identified site.”
Method 2: An area within PIR containing an “identified site” or 20 or more buildings intended for human occupancy.

Calculating HCAs
(source: PHMSA)

In these definitions, “identified sites” include such things as playgrounds, recreational facilities, stadiums, churches, office buildings, community centers, hospitals, prisons, schools, and assisted-living facilities. However, there is a notable difference in how HCAs are calculated for natural gas pipelines vs. hazardous liquid pipelines.

Beyond just looking at what lies within the PIR, pipelines that contain gasses such as ethane potentially impact a much broader area as vapors flow over land or within a river, stream, lake, or other means. A truly accurate HCA analysis for an ethane pipeline leak requires extensive atmospheric modeling for likely vapor dispersions, such as seen in the example image below (part of a recent ESRI GIS conference presentation).

Vapor dispersion modelling
(source: TRC Solutions)

What HCAs Dictate

HCAs determine if a pipeline segment is included in an operator’s integrity management program (IMP) overseen by PHMSA or its state equivalent. IMPs must include risk assessments that identify the most likely impact scenarios in each HCA, enhanced management and repair schedules, as well as mitigation procedures in the event of an accident. Some IMPs also include the addition of automatic shut-off valves and leak detection systems, as well as coordination plans with local first responders.

The Falcon Risk Zones

Shell’s permit applications to the PA DEP state the pipeline:

…is not located in or within 100 feet of a national, state, or local park, forest, or recreation area. It is not located in or within 100 feet of a national natural landmark, national wildlife refuge, or federal, state, local or private wildlife or plant sanctuaries, state game lands. It is also not located in or within 100 feet of a national wild or scenic river, the Commonwealth’s Scenic Rivers System, or any areas designated as a Federal Wilderness Area. Additionally, there are no public water supplies located within the Project vicinity.

This is a partial truth, as “site” and “vicinity” are vague terms here. A number of these notable areas are within the PIR and HCA zones. Let’s take a closer look.

The PIR (or “Blast Zone”)

Shell’s permit applications state a number of different pipeline dimensions will be used throughout the project. Most of the Falcon will be built with 12-inch steel pipe, with two exceptions: 1) The segment running from the Cadiz, OH, separator facility to its junction with line running from Scio, OH, will be a 10-inch diameter pipe; 2) 16-inch diameter pipe will be used from the junction of the Falcon’s two main legs located four miles south of Monaca, PA, to its end destination at the ethane cracker. We also know from comments made by Shell in public presentations that the Falcon’s maximum allowable operating pressure (MOAP) will be 1,440 psi. These numbers allow us to calculate the Falcon’s PIR which, for a 16″ ethane pipeline at 1,440psi, is about 940 feet. We’ve termed this the “blast zone” on our maps.

The HCA (or “Vapor Zone”)

Shell’s analysis uses an HCA impact radius of 1.25 miles. This much larger buffer reflects the fact that vapors from hazardous liquid pipelines can travel unpredictably at high concentrations for long distances before ignition. This expanded buffer might be called the “vapor zone,” a term we used on our map. Within the HCA “vapor zone” we find that 60 of the Falcon’s 97 miles qualify as high consequence areas, with 35 miles triggered due to their proximity to drinking water sources, 25 miles trigger for proximity to populated areas, and 3 miles for proximity to ecological areas.

Populated Areas

Shell’s HCA buffer intersects 14 US Census-designated populated areas, shown in the table below. Falcon’s right-of-way directly intersects two of these areas: Cadiz Village in Harrison County, Ohio, and Southview CDP (Census Designated Place) in Washington County, PA. These areas are listed below. Additionally, we included on the FracTracker map the locations of public facilities that were found inside the HCA buffer. These include 5 public schools, 6 daycare centers, 10 fire stations, and 6 EMS stations.

Area	Population	State	HCA
Pittsburgh Urbanized Area	High	PA	Indirect
Weirton-Steubenville Urbanized Area	High	WV/OH/PA	Indirect
Scio Village	Other	OH	Indirect
Cadiz Village*	Other	OH	Direct
Amsterdam Village	Other	OH	Indirect
Shippingport Borough	Other	PA	Indirect
Industry Borough	Other	PA	Indirect
Hookstown Borough	Other	PA	Indirect
Midway Borough	Other	PA	Indirect
Clinton CDP	Other	PA	Indirect
Imperial CDP	Other	PA	Indirect
Southview CDP*	Other	PA	Direct
Hickory CDP	Other	PA	Indirect
Westland CDP	Other	PA	Indirect
* Indicates an area the Falcon’s right-of-way will directly intersect

While it is difficult to determine the actual number of people living in the PIR and HCA vapor zone, there are ways one can estimate populations. In order to calculate the number of people who may live within the HCA and PIR zones, we first identified U.S. Census blocks that intersect each respective buffer. Second, we calculated the percentage of that census block’s area that lies within each buffer. Finally, we used the ratio of the two to determine the percentage of the block’s population that lies within the buffer.

Based on 2010 Census data, we estimate that 2,499 people live within a reasonable projection of the Falcon’s PIR blast zone. When expanded to the HCA vapor zone, this total increases to 8,738 people. These numbers are relatively small compared to some pipelines due to the fact that a significant portion of the Falcon runs through fairly rural areas in most places.

	PIR est. pop.	HCA est. pop.
OHIO
Carroll County	11	47
Harrison County	274	915
Jefferson County	334	1,210
Total	619	2,172

WEST VIRGINIA
Hancock County	242	1,155
Total	242	1,155

PENNSYLVANIA
Allegheny County	186	969
Beaver County	990	3,023
Washington County	461	1,419
Total	1,637	5,410

Grand Total	2,499	8,738

Drinking Water Sources

Shell’s data identified a number of drinking water features considered in their HCA analysis. Metadata for this information show these sites were obtained from the Ohio Division of Drinking and Ground Waters, the West Virginia Source Water Assessment and Wellhead Protection Program, and the Pennsylvania DEP Wellhead Protection Program. The exact locations of public drinking water wells and intake points are generally protected by states for safety reasons. However, we duplicated the 5-mile buffer zones used on Shell’s map around these points, presumably denoting the boundaries of source water protection areas, wellhead protection areas, or intake points.

Drinking water buffers in Shell’s HCA analysis

As shown on FracTracker’s interactive map, five of these areas serve communities in the northern portions of Beaver County, shown in the image above, as well as the Cadiz and Weirton-Steubenville designated populated areas. Recall that HCA drinking water analysis only requires consideration of groundwater wells and not surface waters. This is an important distinction, as the Ambridge Reservoir is within the HCA zone but not part of Shell’s analysis — despite considerable risks outlined in our Falcon article on water body crossings.

Ecological Areas

Shell’s permits state that they consulted with the U.S. Fish and Wildlife Service (USFWS), Pennsylvania Game Commission (PGC), Pennsylvania Fish & Boat Commission (PFBC), and the Pennsylvania Department of Conservation and Natural Resources (DCNR) on their intended route in order to determine potential risks to protected species and ecologically sensitive areas.

DCNR responded that the pipeline had the potential to impact six sensitive plant species: Vase-vine Leather-Flower, Harbinger-of-spring, White Trout-Lily, Purple Rocket, Declined Trillium, and Snow Trillium. PFBC responded that the project may impact the Southern Redbelly Dace, a threatened temperate freshwater fish, within the Service Creek watershed. PGC responded that the pipeline had potential impact to habitats used by the Short-Eared Owl, Northern Harrier, and Silver-Haired Bat. Finally, the USFWS noted the presence of freshwater mussels in a number of water features crossed by the Falcon.

The presence of these species, as well as the proximity of protected lands illustrated on our map, factored into the Falcon’s HCA designations. A more detailed analysis of these issues is provided in the Falcon Public EIA Project article on Protected Habitats & Species of Concern.

* * *

Falcon Project Home

By Kirk Jalbert, FracTracker Alliance

The Falcon: Protected Habitats & Species of Concern

January 23, 2018/by FracTracker Alliance

Part of the Falcon Public EIA Project

Major pipeline projects are scrutinized by state and federal agencies for their potential impacts to threatened, endangered, and protected species. As part of the planning process, operators are required to consult with agencies to identify habitats known to support these species and are often asked to conduct detailed field surveys of specific areas. In this segment of the Falcon Pipeline EIA Project, we investigate how Shell corresponded with different agencies in complying with federal and state protected species guidelines.

Quick Falcon Facts

More than half (54%) of construction areas are currently forested or farmland
Botanical species Purple Rocket and Climbing Fern located in proximity to workspaces
67 Northern Harrier observations documented during site studies
One active Bald Eagle nest and two inactive nests in proximity to workspaces
Northern Long-eared Bat roost trees discovered as close as 318 feet from workspaces
Clusters of protected freshwater mussels, coldwater fish, and hellbenders in the path of the Falcon

Map of Protected Habitats & Species of Concern

The following map will serve as our guide to exploring the Falcon’s proximity to protected habitats and species of concern. Expand the map full-screen to explore its contents in greater depth. Some layers only become visible at closer zoom levels. A number of additional layers are not shown by default, but can be turned on in the “layers” tab. Click the “details” tab in full-screen mode to read how the different layers were created.

View Map Fullscreen | How FracTracker Maps Work

Shell’s permit applications detail extensive correspondences over a number of years — as early as August 2015 — with the U.S. Fish and Wildlife Service (USFWS), Pennsylvania Game Commission (PGC), Pennsylvania Fish & Boat Commission (PFBC), Pennsylvania Department of Conservation and Natural Resources (DCNR), Ohio Department of Natural Resources (ODNR), and the West Virginia Division of Natural Resources (WVDNR), among other agencies. These interactions tell a story of locating and cataloging threatened flowers, birds of prey, aquatic species, and bats.

Land Cover Assessment

A number of terrestrial habitat types are present along the Falcon pipeline’s route that will be disrupted during its construction. These are easily determined using data maintained by the USGS that tracks land cover and land use trends often used for understanding geospatial biodiversity. Shell used this data in their ecological impacts analysis and we have used it as well for comparison.

Habitat documentations from Shell’s permit applications

More than half (54%) of land in the Falcon’s construction area is currently forested land (deciduous and evergreen). Shell’s permits describe these areas as “contained cool, forested stream valleys and seeps and rich slopes” similar to the image above, which was submitted as part of Shell’s permit applications. An additional 35% is currently farmland (pasture/hay/crops). The remaining land cover is generally made up of water and wetlands, as well as residential and commercial development.

These numbers reflect the fact that the Falcon will travel through predominantly rural areas. Note that this analysis does not account for disruptions that will result from the pipeline’s 111 temporary and 21 permanent access roads. Land Cover for areas along the pipeline can be seen on the FracTracker map by activating the data in the “layers” tab.

Botanical Studies

In their correspondences with state agencies, Shell was notified that a number of important species would likely be found in these habitats. For instance, Pennsylvania Department of Conservation and Natural Resources (DCNR) noted the following botanical species on their watch list would be present:

Vase-vine Leather-flower (endangered): documented in floodplain and slopes of Raccoon Creek
Harbinger-of-spring (rare): documented in forested floodplain of Raccoon Creek
White Trout-lily (rare): documented in forested floodplain of Raccoon Creek
Purple Rocket (endangered): documented in forested floodplain of Raccoon Creek
Declined Trillium (threatened): documented along wooded tributaries and slopes of Raccoon Creek
Snow Trillium (rare): documented in tributary ravines along Raccoon Creek

DCNR requested a survey the Falcon’s route through all of Beaver County and the portion of Allegheny County north of the western fork of Raredon Run. AECOM, Shell’s contractor for this work, surveyed a 300-foot wide buffer along the pipeline route to allow for “minor alignment shifts” as construction plans are refined.

A final survey report was submitted to DCNR in March 2017. In it, AECOM noted having found multiple populations of Harbinger-of-spring (seen below), Purple Rocket, as well as Climbing Fern (Lygodium palmatum), also the PA Watch List. FracTracker’s map locates the general location of botanical discoveries nearest to the pipeline route.

Documented Harbinger-of-spring

DCNR’s response to the survey stated that route changes and plans to bore under Raccoon Creek using HDDs eliminated risks to Harbinger-of-spring and Purple Rocket. Meanwhile, Climbing Fern was determined to be in close proximity, but not directly in the pipeline’s construction area. Although, documents note that a number of ferns were transplanted “to further the species’ success within the Commonwealth.” As a result of these determinations, DCNR granted clearance for construction in August 2017.

Short-eared Owls & Northern Harriers

Shell was also notified by the Pennsylvania Game Commission (PGC) that portions of the Falcon’s workspace would be located near six areas with known occurrences of Short-eared Owls (PA endangered species) and Northern Harriers (PA threatened species).

PGC requested a study of these areas to identify breeding and nesting locations, which AECOM executed from April-July 2016 within a 1,000-foot buffer of the pipeline’s workspace (limited to land cover areas consisting of meadows and pasture). One Short-eared Owl observation and 67 Northern Harrier observations were recorded during the study, but that some of these harriers appeared to be nesting just outside the study area. The study area is visible on the FracTracker map, as shown below.

AECOM’s Owl & Harrier study areas

In February 2017, Shell notified PGC that a number of reroutes had occurred that would shift the Falcon pipeline away from a subset of the observed Northern Harrier habitat. Although, there is no mention in the permit applications about identifying potential nest locations in the neighboring areas where AECOM’s biologists observed additional harriers. Nevertheless, PGC’s final determination in August 2017, approved the project, stipulating that, “based on the unusually high number of observations at these locations” work should not be done in these areas during harrier breeding season, April 15 through August 31.

Bald Eagles

The U.S. Fish & Wildlife Service (USFWS) notified Shell that a known Bald Eagle nest was located in Beaver County. Meanwhile, the Ohio Department of Natural Resources (ODNR) and West Virginia Division of Natural Resources (WVDNR) noted that two potential “alternate nests” were located where the Falcon crosses the Ohio River. National Bald Eagle Management Guidelines bar habitat disturbances that may interfere with the ability of eagles to breed, nest, roost, and forage.

AECOM surveyed these areas in March 2016 and March 2017. The first stage included an analysis of land cover data to determine other areas along the Falcon’s route that may be desirable eagle habitat. In addition to the sites noted above, AECOM determined that Fort Cherry Golf Course (discussed in gerater detail here) and Beaver Conservation District owned land (discussed in greater detail here) would serve as eagle habitat, although in later field surveys no additional nests were found.

The one active nest in close proximity to the Falcon, called the Montgomery Dam Nest, is located just west of the pipeline’s terminus at Shell’s ethane cracker facility. AECOM’s study determined that the foraging areas for a pair of eagles using the nest span the Ohio River and Raccoon Creek.

An additional nesting site was found near Tomlinson Run, along the Ohio River. During initial field observations it was noted that the nest was not in-use and is in an unmaintained condition. Nevertheless, its use by Bald Eagles as recently as 2015 means it is still considered an “alternate nest” and thus accorded protection from habitat modifications. A second alternate nest was found the west bank of the Ohio River. No previous history of the nest had been recorded by state agencies.

Bald Eagle Study Gaps?

Below are maps from Shell’s permit applications identifying the locations of the three nests. These can also be found on the FracTracker map.[/av_icon_box]

USFWS requested that Shell only implement setback buffers for the one active nest at Montgomery Dam. These include no tree clearing within 330 feet, no visible disturbances with 660 feet, and no excessive noise with 1,000 feet of an active nest. Furthermore, Shell must avoid all activities within 660ft of the nest from January 1st to July 31st that may disturb the eagles, including but not limited to “construction, excavation, use of heavy equipment, use of loud equipment or machinery, vegetation clearing, earth disturbance, planting, and landscaping.”

According to Shell’s permit applications, the reroute that occurred at the Ohio River crossing took the Falcon pipeline away from the two alternate nest sites of concern, and the crossing at the river will be done with HDD boring, thus no impacts will occur. Apparently USFWS agreed with this position. However, as we see in the above maps, the HDD staging area on the WV side of the river (where a great deal of noise will likely occur) is just barely outside the 1,000 foot buffer.

Important Bird Areas

USFWS determined that the Falcon pipeline was also in close proximity to many migratory bird species protected under the Migratory Bird Treaty Act and that “direct or indirect, unintentional take of migratory birds may result even if all reasonable measures to avoid avian mortality are utilized.” In particular, the USFWS brought attention to the Raccoon Creek Valley and State Park Important Bird Area (IBA), which is located just south and west of the Falcon pipeline’s two major branches, as seen below.

USFWS recommended a number of strategies, such as co-locating the Falcon pipeline along rights-of-way used by existing pipelines. We see this indeed became the case, as 11 of the Falcon’s 23 pipeline miles in Beaver County are found adjacent to or parallel to existing ROWs.

Additional restrictions were placed on the project in Ohio, where ODNR determined that the Falcon is within range of the Upland Sandpiper, a state endangered bird that nests in grasslands and pastures. Shell was instructed to avoid construction in these habitat types from April 15-July 31 if such areas were to be disturbed. As we can see on the FracTracker map’s analysis of land cover data, there are significant areas of grassland and pasture in Ohio along the pipeline route.

No Peregrine Falcon?

One absence we noted in AECOM’s birds of prey studies was any mention of Peregrine Falcons, listed as endangered and protected under the PA Game and Wildlife Code. Peregrine Falcons nest in cliffs and bridges along rivers in Allegheny and Beaver counties and are particularly prized by the PA DEP, as evidenced by a prominently displayed booth at their Harrisburg headquarters.

PA DEP Falcon Exhibit

One known nest is located under the East Rochester-Monaca Bridge just north of the Falcon pipeline’s terminus at Shell’s ethane cracker facility. While it is unlikely that activities such as tree clearing would affect falcon habitat, other aspects of the pipeline’s construction, such accidental drilling mud spills at HDD sites or ethane releases along Raccoon Creek, may indeed impact Falcon populations.

Federally Protected Bats

The USFWS notified Shell that the Falcon is located within the range of federally protected Indiana Bats and Northern Long-eared Bats in Pennsylvania and West Virginia and requested Shell conduct a bat “mist net” survey to identify breeding areas. Mist netting involves setting up nylon mesh nets at predetermined locations to capture and document bat populations.

AECOM’s bat survey was conducted from April-July 2016. While bats are known to live in caves and abandoned mines in winter, the study focused on summer habitats — mainly forests that support roost trees — given that tree clearing from building the pipeline would be the most likely impact. These forested areas constituted about 27 of the Falcon pipeline’s 97 miles in the two states. Mist net locations (MNLs) were established at 46 sites along the route, roughly 1/2 mile apart, as shown on the FracTracker map. A later reroute of the pipeline led to setting up 4 additional MNLs in June 2017.

A total of 274 bats from 6 different species were captured in the study, included 190 Big Brown Bats, 2 Silver-haired Bats, 62 Eastern Red Bats, 2 Hoary Bats, and 1 Little Brown Bat. 17 Northern Long-eared Bats were found at 13 of the MNL sites, but no Indiana Bats were captured. Radio transmitters were then attached to the Northern Long-eared Bats in order to follow them to roost trees. A total of 9 roost trees were located, with the nearest roost tree located 318 feet from the pipeline’s workspace.

A captured Northern Long-eared Bat

In January 2018, USFWS stated that, because the Falcon’s construction area is not within 150 feet of a known roost tree during breeding season or within a 1/4 mile of a known year-round hibernation site, that “incidental take that might result from tree removal is not prohibited.” However, USFWS also stated that “Due to the presence of several Northern Long-eared Bat roost trees within the vicinity of the project footprint (although outside of the 150-foot buffer), we recommend the following voluntary conservation measure: No tree removal between June 1 and July 31.”

Furthermore, the PGC noted in early correspondences that Silver-haired Bats may be in the region (a PA species of special concern). This was confirmed in AECOM’s mist net study. PGC did not require a further study for the species, but did request a more restrictive conservation of no tree clearing between April 1 and October 31.

Bat Study Gaps?

There are a number of possible gaps in AECOM’s study that need attention. First, the study notes the nearest roost tree is 318 feet from the Falcon’s workspace, but this does not fully represent the likely impact to bat populations. As is seen in the map below, taken from Shell’s permits, this tree is just one in a cluster of five trees all within 750 feet of the pipeline’s workspace.

A dense cluster of bat roosting trees

Furthermore, tree clearing in this area will be extensive considering its proximity to the Falcon’s juncture in Beaver County that also must accommodate a metering pad and access roads. This area is shown in the permit application map below and can be explored on the FracTracker map as well.

A second questionable aspect of the study is that, while the USFWS letter states the Falcon is not “within a 1/4 mile of a known year-round hibernation site,” this was not proven in the study as it did not identify nearby winter habitats. These omissions are noteworthy given the already significant stressors to bat populations in the region, as well as increasing pressure from oil and gas companies to relax standards for protecting endangered bat species.

A Note on Noise Control

As part of their ability to build the Falcon pipeline, USFWS mandated that Shell employ an “independent noise consultant” to measure ambient pre-construction noise levels at each HDD site and at designated Noise Sensitive Areas (NSA), which are generally determined by the presence of protected bird and bat species. Less is known about the details of this part of AECOM’s study plan for Shell. However, we have located noise monitoring sites on the FracTracker map for reference.

Freshwater Mussels

The USFWS and PGC identified very early in the Shell’s construction plans that the project would likely impact four endangered mussel species: the Northern Riffelshell, the Clubshell, the Rayed Bean, and the Snuffbox. AECOM conducted a survey in May 2016, at the request of Pennsylvania and Ohio agencies at 16 perennial streams along the route in those two states. These are shown on the FracTracker map. In PA, mussels were found to be present at both of the Falcon’s intersections with Raccoon Creek, as seen in a photo from Shell’s permit application below.

Documented freshwater mussels in Raccoon Creek

The results of the Ohio study are unknown at this time. However, we found it interesting that ODNR’s letter to Shell stated that unavoidable impacts could be resolved by allowing specialists to collect and relocate mussels to suitable and similar upstream habitats. Meanwhile, it appears that the USFWS and PFBC have also green lighted construction around the two known Raccoon Creek mussel habitats, as Shell’s applications argue these waters would not be impacted due to the fact that they would be crossing using HDD boring.

Coldwater Fish

The PA Fish & Boat Commission notified Shell that the Falcon may impact the Southern Redbelly Dace. This threatened species is especially vulnerable to physical and chemical (turbidity, temperature) changes to their environment. PAFB explicitly notes in their correspondences that “we are concerned about potential impacts to the fish, eggs and the hatching fry from any in-stream work.” Of note is that these sites of concern are located in HQ/CWF streams of the Service Creek watershed (discussed in greater detail here), as shown on the map below.

Headwater streams in the Service Creek watershed

Early correspondences with PFBC show the agency requesting that directional boring be used for these stream crossings or, if work necessitated direct impacts (such as open-cut crossings), that these activity be avoided during the spawning season. Shell responded to the request in stating that, with the exception of the Service Creek itself which will be crossed by HDD, the terrain surrounding its headwater streams was not suitable for boring, and would thus require open-cuts.

PFBC’s final determination on these matters is that they generally agreed, with the exception of the HDD site and one headwater stream (S-PA-151104-MRK-001), all other crossings must adhere to seasonal restrictions with no in-stream activity being conducted between May 1-July 31.

In Ohio, we see similar circumstances related to the River Darter, the Paddlefish, and the Channel Darter, all threatened species in the state. The ODNR recommended no in-stream work in the Ohio River from March 15-June 30 and no in-stream work in any of the state’s perennial streams from April 15-June 30.

Eastern Hellbenders

The Falcon is also within range of Eastern Hellbender habitat in Ohio, a state endangered species and a federal species of concern. In particular, ODNR noted that Yellow Creek, in Jefferson County, is known to host the species. Because of this, ODNR requested that if any in-stream work was to occur in Yellow Creek, a habitat suitability survey must be conducted to determine if Hellbenders were present. Yellow Creek’s tributaries are indeed crossed by the Falcon. Whether or not a study was conducted as a result of this is unknown due to our not having reviewed Shell’s Ohio permit applications. The below image, captured from our page on water crossings, shows these locations.

Falcon crossing Yellow Creek tributaries

Allowable Work Dates

To summarize, there are numerous implications for how Shell’s construction of the Falcon pipeline must accommodate endangered, threatened, and rare species in different states. In particular, Shell must avoid land and aquatic disturbances during different breeding and spawning seasons. Below is a breakdown of these black-out periods. Note that these only apply to locations where sensitive species were found in AECOM’s studies.

Land Disturbances

Northern Harriers, Short-eared Owls (PGC): No clearing between April 15 and August 31
Bald Eagles (USFWS): No work between January 1 and July 31
Upland Sandpiper (ODNR): No clearing between April 15 and July 31
Bats (USFWS): No clearing between April 1 and October 31

Aquatic Disturbances

Southern Redbelly Dace (PFBC): No in-stream work between May 1 and July 31
River Darter, Paddlefish, Channel Darter (ODNR): No Ohio River work between March 15 and June 30; no perennial stream work between April 15 and June 30

* * *

Falcon Project Home

Falcon Pipeline: Cumulative Development & Compounded Risks

January 22, 2018/by FracTracker Alliance

Part of the Falcon Public EIA Project

In this final section of the Falcon Public EIA Project, we explore the Falcon pipeline’s entanglements with a region already impacted by a long history of energy development. Featured in this article are where the Falcon pipeline intersects underground mining facilities, strip mines, other hazardous pipelines, active oil and gas wells, as well as a very large compressor station. We utilize this information to locate spaces where cumulative development also has the potential for compounded risk.

Quick Falcon Facts

20 miles of the Falcon run through under-mined areas; 5.6 miles through active mines
18 miles of the Falcon run through surface-mined areas; also coal slurry waste site
Shares a right-of-way with Mariner West pipeline for 4 miles in Beaver County
11 well pads, as well as a compressor station, are within the potential impact radius

Map of Falcon relative to mined areas and other energy-related development

The following map will serve as our guide in breaking down where the Falcon intersects areas that have experienced other forms of energy development. Expand the map full-screen to explore its contents in greater depth. Some layers only become visible as you zoom in. A number of additional features of the map are not shown by default, but can be turned on in the “layers” tab. These include information on geological features, water tables, soil erosion characteristics, as well as drinking reservoir boundaries. Click the “details” tab in full-screen mode to read how the different layers were created.

View Map Fullscreen | How FracTracker Maps Work

Mined Lands

The Falcon pipeline intersects a surprising number of active and inactive/abandoned mine lands. While the location of active mines is fairly easy to obtain from mine operators, finding data on abandoned mines is notoriously difficult. State agencies, such as the Pennsylvania Department of Environmental Protection (DEP), have digitized many legacy maps, but these resources are known to be incomplete and inaccurate in many locations.

AECOM’s engineers used data layers on active and abandoned mine lands maintained by state agencies in OH, WV, and PA. FracTracker obtained this data, as well, as shown on the interactive map. Shell states in their permits that AECOM’s engineers also went through a process of obtaining and digitizing paper maps in areas with questionable mine maps.

Shell states that their analysis shows that 16.8 miles of the Falcon pipeline travel through under-mined areas. Our analysis using the same dataset suggests the figure is closer to 20 miles. Of these 20 miles of pipeline:

5.6 miles run through active coal mines and are located in Cadiz Township, OH (Harrison Mining Co. Nelms Mine); Ross Township, OH (Rosebud Mining Co. Deep Mine 10); and in Greene Township, PA (Rosebud Mining Co. Beaver Valley Mine).
More than 18 miles run through areas that have been historically surface-mined (some overlapping under-mined areas).
Of those 18 miles, 1.5 miles run through an active surface mine located in Cadiz Township, OH, managed by Oxford Mining Company.

Beaver Valley Mine

The Beaver Valley Mine in Greene Township, PA, appeared to be of particular importance in Shell’s analysis. Of the three active mines, Shell maintained an active data layer with the mine’s underground cell map for reference in selecting routes, seen in the image below. Note how the current route changed since the map was originally digitized, indicating that a shift was made to accommodate areas around the mine. The FracTracker interactive map shows the mine based on PA DEP data, which is not as precise as the mine map AECOM obtained from Rosebud Mining.

Digitized map of Beaver Valley Mine

Rosebud Mining idled its Beaver Valley Mine in 2016 due to declining demand for coal. However, Rosebud appears to be expanding its workforce at other mines in the area due to changing economic and political circumstances. We don’t know exactly why this particular mine was highlighted in Shell’s analysis, or why the route shifted, as it is not directly addressed in Shell’s permit applications. Possibilities include needing to plan around areas that are known to be unfit for the pipeline, but also perhaps areas that may be mined in the future if the Beaver Valley Mine were to restart operations.

Coal Slurry Site, Imperial PA

As discussed in other segments of the Falcon Public EIA Project, Shell intends to execute 19 horizontal directional drilling (HDD) operations at different sites along the pipeline. A cluster of these are located in Allegheny and Washington counties, PA, with extensive historical surface mining operations. A 2003 DEP report commented on this region, stating:

All of the coal has been underground mined. Most of the coal ribs and stumps (remnants from the abandoned underground mine) have been surface mined… The extensive deep mining, which took place from the 1920’s through the 1950’s, has had a severe effect on groundwater and surface water in this watershed.

Shell’s applications note that AECOM did geotechnical survey work in this and other surface-mined areas co-located with proposed HDD operations, concluding that the ”majority of rock encountered was shale, sandstone, limestone, and claystone.” However, at one proposed HDD (called “HOU-06”) the Falcon will cross a coal waste site identified in the permits as “Imperial Land Coal Slurry” along with a large Palustrine Emergent (PEM) wetland along Potato Garden Run, seen below.

A Falcon HDD crossing under a wetland and coal slurry site

Foreign Pipelines

In addition to its entanglements with legacy coal mining, the Falcon will be built in a region heavily traveled by oil and gas pipelines. More than 260 “foreign pipelines” carrying oil, natural gas, and natural gas liquids, were identified by AECOM engineers when selecting the Falcon’s right-of-way (note that not all of these are directly crossed by the Falcon).

Owners of these pipelines run the gamut, including companies such as Williams, MarkWest, Columbia, Kinder Morgan, Energy Transfer Partners, Momentum, Peoples Gas, Chesapeake, and Range Resources. Their purposes are also varied. Some are gathering lines that move oil and gas from well pads, others are midstream lines connecting things like compressor stations to processing plants, others still are distribution lines that eventually bring gas to homes and businesses. FracTracker took note of these numbers and their significance, but did not have the capacity to document all of them for our interactive map.

Shared Rights-of-Way

However, we did include one pipeline, the Mariner West, because of its importance in the Falcon’s construction plans. Mariner West was built in 2011-2013 as part of an expanding network of pipelines initially owned by Sunoco Pipeline but now operated by Energy Transfer Partners. The 10-inch pipeline transports 50,000 barrels of ethane per day from the Separator plant in Houston, PA, to processing facilities in Canada. Another spur in this network is the controversial Mariner East 2.

Mariner West is pertinent to the Falcon because the two pipelines will share the same right-of-way through a 4-mile stretch of Beaver County, PA, as shown below.

The Falcon and Mariner West sharing a right-of-way

Reuse of existing rights-of-way is generally considered advantageous by pipeline operators and regulatory agencies. The logistics of sharing pipelines can be complicated, however. As noted in Shell’s permit applications:

Construction coordination will be essential on the project due to the numerous parties involved and the close proximity to other utilities. Accurate line location was completed; however, verification will also be key, along with obtaining proper crossing design techniques from the foreign utilities. A meeting with all of pipeline companies will be held to make sure that all of the restrictions are understood prior to starting construction, and that they are documented on the construction alignment sheets/bid documents for the contractor(s). This will save a potential delay in the project. It will also make working around the existing pipelines safe.

Shell’s attention to coordinating with other utility companies is no doubt important, as is their recognition of working near existing pipelines as a safety issue. There are elevated risks with co-located pipelines when they come into operation. This was seen in a major pipeline accident in Salem Township, PA, in 2016. One natural gas line exploded, destroying nearby homes, and damaged three adjacent pipelines that took more than a year to come back online. These findings raise the question of whether or not Class Location and High Consequence Area assessments for the Falcon should factor for the exponential risks of sharing a right-of-way with Mariner West.

Oil & Gas Extraction

The remaining features included on our map relate to oil and gas extraction activities. The Falcon will carry ethane from the three cryogenic separator plants at the pipeline’s source points. But the wet, fracked gas that supplies those plants also comes from someplace, and these are the many thousands of unconventional gas wells spread across the Marcellus and Utica shale.

We found 11 unconventional oil and gas pads, hosting a combined 48 well heads, within the Falcon’s 940-foot PIR. We also found a large compressor station operated by Range Resources, located in Robinson Township, PA. This is shown below, along with a nearby gas pad.

A well pad and compressor station in Falcon’s PIR

We noted these well pads and the compressor station because Class Location and HCA risk analysis may account for proximity to occupied businesses and homes, but does not always consider a pipeline’s proximity to other high-risk industrial sites. Nevertheless, serious incidents have occurred at well pads and processing facilities that could implicate nearby hazardous liquid pipelines. By the same measure, an accident with the Falcon could implicate one of these facilities, given they are all within the Falcon’s blast zone.

* * *

Falcon Project Home

The Falcon: Methods, Mapping, & Analysis

January 21, 2018/by FracTracker Alliance

Part of the Falcon Public EIA Project

FracTracker began monitoring Falcon’s construction plans in December 2016, when we discovered a significant cache of publicly visible GIS data related to the pipeline. At that time, FracTracker was looking at ways to get involved in the public discussion about Shell’s ethane cracker and felt we could contribute our expertise with mapping pipelines. Below we describe the methods we used to access and worked with this project’s data.

Finding the Data

Finding GIS data for pipeline projects is notoriously difficult but, as most research goes these days, we started with a simple Google search to see what was out there, using basic keywords, such as “Falcon” (the name of the pipeline), “ethane” (the substance being transported), “pipeline” (the topic under discussion), and “ArcGIS” (a commonly used mapping software).

In addition to news stories on the pipeline’s development, Google returned search results that included links to GIS data that included “Shell” and “Falcon” in their names. The data was located in folders labeled “HOUGEO,” presumably the project code name, as seen in the screenshot below. All of these links were accessed via Google and did not require a password or any other authentication to view their contents.

Shell’s data on the Falcon remained publicly available at this link up to the time of the Falcon Public EIA Project‘s release. However, this data is now password protected by AECOM.

Google search results related to Falcon pipeline data

Viewing the Data

The HOUGEO folder is part of a larger database maintained by AECOM, an engineering firm presumably contracted to prepare the Falcon pipeline construction plan. Data on a few other projects were also visible, such as maps of the Honolulu highway system and a sewer works in Greenville, NC. While these projects were not of interest to us, our assessment is that this publicly accessible server is used to share GIS projects with entities outside the company.

Within the HOUGEO folder is a set of 28 ArcGIS map folders, under which are hundreds of different GIS data layers pertaining to the Falcon pipeline. These maps could all be opened simply by clicking on the “ArcGIS Online map viewer” link at the top of each page. Alternatively, one can click on the “View in: Google Earth” link to view the data in Google Earth or click on the “View in: ArcMap” link to view the data in the desktop version of the ArcGIS software application. No passwords or credentials are required to access any of these folders or files.

As seen in the screenshot below, the maps were organized topically, roughly corresponding to the various components that would need to be addressed in an EIA. The “Pipeline” folder showed the route of the Falcon, its pumping stations, and work areas. “Environmental” contained data on things like water crossings and species of concern. “ClassLocations” maps the locations of building structures in proximity to the Falcon.

The HOUGEO GIS folders organized by topic

Archiving the Data

After viewing the Falcon GIS files and assessing them for relevancy, FracTracker went about archiving the data we felt was most useful for our assessing the project. The HOUGEO maps are hosted on a web server meant for viewing GIS maps and their data, either on ArcOnline, Google Earth, or ArcMap. The GIS data could not be edited in these formats. However, viewing the data allowed us to manually recreate most of the data.

For lines (e.g. the pipeline route and access roads), points (e.g. shutoff valves and shut-off valves), and certain polygons (e.g. areas of landslide risk and construction workspaces), we archived the data by manually recreating new maps. Using ArcGIS Desktop software, we created a new blank layer and manually inputted the relevant data points from the Falcon maps. This new layer was then saved locally so we could do more analysis and make our own independent maps incorporating the Falcon data. In some cases, we also archived layers by manually extracting data from data tables underlying the map features. These tables are made visible on the HOUGEO maps simply by clicking the “data table” link provided with each map layer.

Other layers were archived using screen captures of the data tables visible in the HOEGEO ArcOnline maps. For instance, the table below shows which parcels along the route had executed easements. We filtered the table in ArcGIS Online to only show the parcel ID, survey status, and easement status. Screen captures of these tables were saved as PDFs on our desktop, then converted to text using optical character recognition (OCR), and the data brought into Microsoft Excel. We then recreated the map layer by matching the parcel IDs in our newly archived spreadsheet to parcel IDs obtained from property GIS shapefiles that FracTracker purchased from county deeds offices.

Transparency & Caveats

FracTracker strives to maintain transparency in all of its work so the public understands how we obtain, analyze, and map data. A good deal of the data found in the HOUGEO folders are available through other sources, such as the U.S. Geological Survey, the Department of Transportation, and the U.S. Census, as well as numerous state and county level agencies. When possible, we opted to go to these original sources in order to minimize our reliance on the HOUGEO data. We also felt it was important to ensure that the data we used was as accurate and up-to-date as possible.

For instance, instead of manually retracing all the boundaries for properties with executed easements for the Falcon’s right-of-way, we simply purchased parcel shapefiles from county deeds and records offices and manually identified properties of interest. To read more on how each data layer was made, open any of our Falcon maps in full-screen mode and click the “Details” tab in the top left corner of the page.

Finally, some caveats. While we attempted to be as accurate as possible in our methods, there are aspects of our maps where a line, point, or polygon may deviate slightly in shape or location from the HOUGEO maps. This is the inherent downside of having to manually recreate GIS data. In other cases, we spent many hours correcting errors found in the HOUGEO datasets (such as incorrect parcel IDs) in order to get different datasets to properly match up.

FracTracker also obtained copies of Shell’s permit applications in January by conducting a file review at the PA DEP offices. While these applications — consisting of thousands of pages — only pertain to the areas in Pennsylvania where the Falcon will be built, we were surprised by the accuracy of our analysis when compared with these documents. However, it is important to note that the maps and analysis presented in the Falcon Public EIA Project should be viewed with potential errors in mind.

* * *

Falcon Project Home

The Falcon Public EIA Project

January 19, 2018/by Guest Author

Map of the Standing Rock protest - Oil is flowing through the DAPL, but the Standing Rock Lakota Sioux Tribe have challenged the permit and are petitioning for the release of Chase Iron Eyes

An Ongoing Fight at Standing Rock

November 28, 2017/by Kyle Ferrar, MPH

We live in a complex environment of local, regional, national, and international issues. We are constantly bombarded with a news cycle that regenerates at increasingly dizzying speeds. How can we possibly know what is truly important when hyped up twitter controversies clog up our news feeds?

In this quantity-over-quality culture, many of the most important issues and fights for civil rights and energy justice become casualties of a regression to ignorance.

At FracTracker, we disagree with this tactic – especially as it relates to the protests at Standing Rock. FracTracker has previously written about these demonstrations (shown in the map above), and has also analyzed and mapped data on oil spills from pipelines in North Dakota. We will continue FracTracker’s coverage of Standing Rock and the Water Protectors who fought – and continue to fight – the Dakota Access Pipeline (DAPL), known as the Black Snake.

Following the Fight

For those unaware, the fight against the Dakota Access Pipeline operated by Energy Transfer Partners, continues. While the project was green-lighted by the Trump Administration and Bakken oil began flowing in June of 2017, the court has returned the permits to the U.S. Army Corps of Engineers. A U.S. District Court judge ruled that the initial approval of the pipeline did not undergo adequate study of its environmental consequences. The finding stated that the Army Corps provided a flawed model, inadequate for predicting the full impacts of a leak under Lake Oahe. The model does not consider what would happen in the event of a leak under the lake. It models only benzene — one of many toxic chemicals present in crude oil — and models its movement in an unrealistic manner. Energy Transfer Partners claims the model is conservative, but it massively underestimates the potential impacts on human health and wildlife. The Army Corps provides no plan to contain an underground leak or clean contaminated soil and groundwater under Lake Oahe.

On a related note, DAPL’s parent company, Energy Transfer Partners, said in a recent annual report that it may not have sufficient liquid assets to finance a major cleanup project and would likely pass those costs onto local landowners and federal taxpayers. Energy Transfer Partners has since filed a racketeering lawsuit seeking $300 million in damages from the Red Warrior Camp at Standing Rock.

Upon finding the Army Corps’s model inadequate, the court returned the permits for further review. According to EarthJustice attorney Jan Hassleman:

… the agency could simply revise or update its environmental review and again conclude that no EIS (environmental impact statement) is required. If that happens, additional legal challenges are likely. The Tribe believes this court decision should trigger a full EIS, including consideration of route alternatives, just as the Obama administration proposed in December.

Normally, when a permit is issued in violation of the National Environmental Protection Act (NEPA), operations are suspended, which would have forced the DAPL to shut down while the review is conducted. Contrary to the usual protocol, on October 11, 2017 a federal judge ruled that the pipeline will remain operational pending the environmental review by the Army Corps. Standing Rock Sioux Chairman Dave Archambault II has said in a statement, however, “Just because the oil is flowing now doesn’t mean that it can’t be stopped.”

More Information and Resources

The Lakota People’s Law Project (LPLP) has been a resource to Lakota country – an area comprised of nine Indian reservation in North and South Dakota – since 2004. The LPLP supports a number of campaigns including divestment and energy justice, and has published several reports:

Special thanks to the Lakota People’s Law Project and Rachel Hallett-Ralston for the information provided.

In January of 2017, 76 Water Protectors including Chase Iron Eyes were arrested on land granted to the Standing Rock Lakota Sioux Tribe under the 1851 Treaty of Fort Laramie. Chase Iron Eyes, Lead Counsel of the Lakota People’s Law Project, has been charged with felony incitement to riot and misdemeanor criminal trespass. In the interview above, Chase Iron Eyes discusses his involvement with Standing Rock and the political pressures to make an example out of him. Read the Lakota People’s Law Project petition here.

By Kyle Ferrar, Western Program Coordinator, FracTracker Alliance

The feature image is a snapshot of our Standing Rock Protest Map, created last year.

Giving Voice to the Sandhill Cranes: Place-based Arguments against Keystone XL

November 8, 2017/by Guest Author

By Wrexie Bardaglio, guest commentator

When we hear his call, we hear no mere bird. We hear the trumpet in the orchestra of evolution. He is the symbol of our untamable past, of that incredible sweep of millennia which underlies and conditions the daily affairs of birds and men…” ~ Aldo Leopold, on the Sandhill Crane, in “Marshland Elegy”

Dilbit – or diluted bitumen – is refined from the naturally-occurring tar sands deposits in Alberta, Canada. In March 2017, I applied to the Nebraska Public Service Commission for standing as an intervenor in the Commission’s consideration of TransCanada’s request for a permit to construct a pipeline transporting dilbit – a project referred to as the Keystone XL pipeline. Below are my reflections on the battle against the permitting process, and how FracTracker’s maps ensured the Sandhill Crane’s voice made it into public record.

A Pipeline’s History

The Keystone 1 pipeline carries the dilbit from Alberta, to Steele City, Nebraska, and ultimately to Port Arthur, Texas and export refineries along the Gulf Coast. The state of Montana had already approved the Keystone XL project, as had the state of South Dakota. The decision of the South Dakota Public Utilities Commission was appealed, however, and has now worked its way to the South Dakota Supreme Court, where it is pending.

Resistance to TransCanada’s oil and gas infrastructure projects is not new. Beginning in 2010, some Nebraska farmers and ranchers joined forces with tribal nations in the Dakotas, who were also fighting TransCanada’s lack of proper tribal consultation regarding access through traditional treaty territory. The indigenous nations held certain retained rights as agreed in the 1868 Fort Laramie Treaty between the United States government and the nine tribes of the Great Sioux Nation. The tribes were also protesting TransCanada’s flaunting of the National Historic Preservation Act’s protections of Native American sacred sites and burial grounds. Further, although TransCanada was largely successful in securing the easements needed in Nebraska to construct the pipeline, there were local holdouts refusing to negotiate with the company. TransCanada’s subsequent attempts to exercise eminent domain resulted in a number of lawsuits.

In January of 2015, then-President Barack Obama denied the international permit TransCanada needed. While that denial was celebrated by many, everyone also understood that a new president could well restore the international permit. Indeed, as one of his first actions in January 2017, the new Republican president signed an executive order granting the permit, and the struggle in Nebraska was reignited.

“What Waters Run Through My Veins…”

While I am a long-time resident of New York, I grew up in the Platte River Valley of South Central Nebraska, in a town where my family had and continues to have roots – even before Nebraska became a state. There was never a question in my mind that in this particular permitting process I would request status as an intervenor; for me, the matter of the Keystone XL Pipeline went far beyond the legal and political and energy policy questions that were raised and were about to be considered. It was about who I am, how I was raised, what I was taught, what waters run through my veins as surely as blood, and who my own spirit animals are, the Sandhill Cranes.

Bardaglio (age 3) and her father, along the banks of the Platte River

When we were growing up, our father told us over and over and over about why Nebraska was so green. The Ogallala Aquifer, he said, was deep and vast, and while eight states partially sat atop this ancient natural cistern, nearly all of Nebraska floated on this body. Nebraska was green, its fields stretching to the horizon, because, as our father explained, the snow runoff from the Rockies that flowed into our state and was used eleven times over was cleansed in water-bearing sand and gravel on its way to the Missouri on our eastern boundary, thence to the Mississippi, and finally to the Gulf.

I grew up understanding that the Ogallala Aquifer was a unique treasure, the largest freshwater aquifer in the world, the lifeblood for Nebraska’s agriculture and U.S. agriculture generally, and worthy of protection. I thought about the peril to the aquifer because of TransCanada’s plans, should there be a spill, and the additional threats an accident would potentially pose to Nebraska’s rivers, waterways and private wells.

The Ogallala Aquifer

Knowing that climate change is real, terrifying, and accelerating, I recognized that a warming world would increasingly depend on this aquifer in the nation’s midsection for life itself.

Migration of the Sandhill Cranes

As I thought about how I would fight the KXL, another narrative took shape rising out of my concern for the aquifer. Growing up in the South Central Platte River Valley, I – and I daresay most everyone who lives there – have been captivated by the annual migration of the Sandhill Cranes, plying the skies known as the Central Flyway. As sure as early spring comes, so do the birds. It may still be bitterly cold, but these birds know that it is time to fly. And so they do – the forward scouts appearing in winter grey skies, soon followed by some 500,000 – 600,000 thousand of them, darkening the skies, their cries deafening and their gorgeous archaeopteryx silhouettes coming in wave after wave like flying Roman Legions.

To this day, no matter where I am, the first thing in my sinews and bones when winter begins to give way is the certainty that the birds are coming, I feel them; they are back. They are roosting on the sandbars in the braided river that is the Platte and gleaning in the stubbled fields abutting it… they are home.

According to The Nature Conservancy:

Scientists estimate that at least one-third of the entire North American population of Sandhill Cranes breed in the boreal forest of Canada and Alaska…

Scientists estimate that approximately 80 percent of all Sandhill Cranes in North America use a 75-mile stretch of Nebraska’s Platte River during spring migration. From March to April, more than 500,000 birds spend time in the area preparing for the long journey north to their breeding grounds in Canada and Alaska. During migration, the birds may fly as much as 400 miles in one day.

Sandhill Cranes rely on open freshwater wetlands for most of their lifecycle. Degradation of these kinds of wetland habitats is among the most pressing threats to the survival of Sandhill Cranes. (Emphasis added)

Giving Sandhill Cranes a Voice

But how could I make the point about the threat TransCanada posed to the migratory habitat of the Sandhill Cranes (and endangered Whooping Cranes, pelicans, and hummingbirds among the other thermal riders who also migrate with them)? Books, scientific papers, lectures – all the words in the world – cannot describe this ancient rite, this mysterious primal navigation of the unique pathway focusing on this slim stretch of river, when viewed from a global perspective a fragile skein in a fragile web in a biosphere in peril.

In my head I called it a river of birds in the grassland of sky. And I am so grateful to my friend, Karen Edelstein at FracTracker Alliance, for her willingness to help map and illustrate the magnificence of the migration flyway in the context of the three proposed options for the KXL pipeline.

Karen prepared two maps for me, but my favorite is the one above.

It shows an ancient, near-primordial, near-mystical event. Guided by rudders and instinct we can barely comprehend, in concert with earth’s intrinsic and exquisitely-designed balance, and as certain as a sunrise, a sunset or a moon rise, these oldest of crane species find their ways through the heavens. They hew to certainties that eclipse the greed of multinational corporations like TransCanada, who barely even pay lip service to the integrity of anything over which they can’t exert dominion. To say they don’t respect the inherent rights of species other than our own, or to ecological communities that don’t directly include us, is an understatement, and a damning comment on their values.

I was prepared for pushback on these maps from TransCanada. And in truth, the company was successful in an in limine motion to have certain exhibits and parts of my testimony stricken from the official record of the proceedings.

But not the maps.

In fact, too many other intervenors to count, as well as several of the lawyers involved in the proceedings commented to me on the beauty and accuracy of the maps. And not only are they now a part of the permanent record of the Nebraska Public Service Commission, should there be an appeal (which all of us expect), on both sides of the issue, there is a very good possibility they will be incorporated into the formal testimonies by the lawyers as the matter moves through the appeals process.

Taking Action, Speaking Out

Ordinary citizens must figure out how to confront the near-impenetrable stranglehold of multi-national corporations whose wealth is predicated on the continuance of fossil fuels as the primary sources of energy. We have had to become more educated, more activist, and more determined to fight the destruction that is now assured if we fail to slow down the impacts of climate change and shift the aggregate will of nations towards renewable energy.

Many activists do not realize that they can formally intervene at the state level in pipeline and infrastructure permitting processes. In doing so, the voice of the educated citizen is amplified and becomes a threat to these corporations whose business models didn’t account for systematic and informed resistance in public agencies’ heretofore pro forma proceedings. The publicly-available documents and filings from corporations can be important tools for “speaking truth to power” when paired with the creative tools born of necessity by the environmental movement.

Technology is value-neutral, but as I learned – as did many others in the Keystone XL Pipeline fight – in skilled hands it becomes a weapon in the struggle for the greater good.

I will be forever grateful for FracTracker, and will be interested to see how others use this tool in the fights that are sure to come.

EXCELSIOR!

For more background on the natural history of Sandhill Cranes, please view this video produced by The Crane Trust.

Wrexie Bardaglio is a Nebraska native living in Covert, New York. She worked for ten years for a member of Congress as a legislative assistant with a focus on Indian affairs and for a DC law firm as legislative specialist in Indian affairs. She left politics to open a bookstore in suburban Baltimore. She has been active in the Keystone XL fights in Nebraska and South Dakota and in fracking and gas infrastructure fights in New York.

This article’s feature image of a Sandhill Crane is the work of a U.S. Fish and Wildlife Service employee, taken or made as part of that person’s official duties. As a work of the U.S. federal government, the image is in the public domain.

FracTracker Alliance makes hundreds of maps, analyses, and photos available for free to frontline communities, grassroots groups, NGO’s, and many other organizations concerned about the industry to use in their oil and gas campaigns. To address an issue, you need to be able to see it.

However, we rely on funders and donations – and couldn’t do all of this without your help!

Donate today

Groundwater risks in Colorado due to Safe Drinking Water Act exemptions

October 26, 2017/by Kyle Ferrar, MPH

Oil and gas operators are polluting groundwater in Colorado, and the state and U.S. EPA are granting them permission with exemptions from the Safe Drinking Water Act.

FracTracker Alliance’s newest analysis attempts to identify groundwater risks in Colorado groundwater from the injection of oil and gas waste. Specifically, we look at groundwater monitoring data near Class II underground injection control (UIC) disposal wells and in areas that have been granted aquifer exemptions from the underground source of drinking water rules of the Safe Drinking Water Act (SDWA). Momentum to remove amend the SDWA and remove these exemption.

Learn more about Class II injection wells.

Aquifer exemptions are granted to allow corporations to inject hazardous wastewater into groundwater aquifers. The majority, two-thirds, of these injection wells are Class II, specifically for oil and gas wastes.

What exactly are aquifer exemptions?

The results of this assessment provide insight into high-risk issues with aquifer exemptions and Class II UIC well permitting standards in Colorado. We identify areas where aquifer exemptions have been granted in high quality groundwater formations, and where deep underground aquifers are at risk or have become contaminated from Class II disposal wells that may have failed.

Of note: On March 23, 2016, NRDC submitted a formal petition urging the EPA to repeal or amend the aquifer exemption rules to protect drinking water sources and uphold the Safe Drinking Water Act. Learn more

Research shows injection wells do fail

Class II injection well in Colorado explodes and catches fire. Photo by Kelsey Brunner for the Greeley Tribune.

Disposal of oil and gas wastewater by underground injection has not yet been specifically researched as a source of systemic groundwater contamination nationally or on a state level. Regardless, this issue is particularly pertinent to Colorado, since there are about 3,300 aquifer exemptions in the US (view map), and the majority of these are located in Montana, Wyoming, and Colorado. There is both a physical risk of danger as well as the risk of groundwater contamination. The picture to the right shows an explosion of a Class II injection well in Greeley, CO, for example.

Applicable and existing research on injection wells shows that a risk of groundwater contamination of – not wastewater – but migrated methane due to a leak from an injection well was estimated to be between 0.12 percent of all the water wells in the Colorado region, and was measured at 4.5 percent of the water wells that were tested in the study.

A recent article by ProPublica quoted Mario Salazar, an engineer who worked for 25 years as a technical expert with the EPA’s underground injection program in Washington:

In 10 to 100 years we are going to find out that most of our groundwater is polluted … A lot of people are going to get sick, and a lot of people may die.

Also in the ProPublic article was a study by Abrahm Lustgarten, wherein he reviewed well records and data from more than 220,000 oil and gas well inspections, and found:

Structural failures inside injection wells are routine.
Between 2007-2010, one in six injection wells received a well integrity violation.
More than 7,000 production and injection wells showed signs of well casing failures and leakage.

This means disposal wells can and do fail regularly, putting groundwater at risk. According to Chester Rail, noted groundwater contamination textbook author:

…groundwater contamination problems related to the subsurface disposal of liquid wastes by deep-well injection have been reviewed in the literature since 1950 (Morganwalp, 1993) and groundwater contamination accordingly is a serious problem.

According to his textbook, a 1974 U.S. EPA report specifically warns of the risk of corrosion by oil and gas waste brines on handling equipment and within the wells. The potential effects of injection wells on groundwater can even be reviewed in the U.S. EPA publications (1976, 1996, 1997).

As early as 1969, researchers Evans and Bradford, who reported on the dangers that could occur from earthquakes on injection wells near Denver in 1966, had warned that deep well injection techniques offered temporary and not long-term safety from the permanent toxic wastes injected.

Will existing Class II wells fail?

For those that might consider data and literature on wells from the 1960’s as being unrepresentative of activities occurring today, of the 587 wells reported by the Colorado’s oil and gas regulatory body, COGCC, as “injecting,” 161 of those wells were drilled prior to 1980. And 104 were drilled prior to 1960!

Wells drilled prior to 1980 are most likely to use engineering standards that result in “single-point-of-failure” well casings. As outlined in the recent report from researchers at Harvard on underground natural gas storage wells, these single-point-of-failure wells are at a higher risk of leaking.

It is also important to note that the U.S. EPA reports only 569 injection wells for Colorado, 373 of which may be disposal wells. This is a discrepancy from the number of injection wells reported by the COGCC.

Aquifer Exemptions in Colorado

According to COGCC, prior to granting a permit for a Class II injection well, an aquifer exemption is required if the aquifer’s groundwater test shows total dissolved solids (TDS) is between 3,000 and 10,000 milligrams per liter (mg/l). For those aquifer exemptions that are simply deeper than the majority of current groundwater wells, the right conditions, such as drought, or the needs of the future may require drilling deeper or treating high TDS waters for drinking and irrigation. How the state of Colorado or the U.S. EPA accounts for economic viability is therefore ill-conceived.

Data Note: The data for the following analysis came by way of FOIA request by Clean Water Action focused on the aquifer exemption permitting process. The FOIA returned additional data not reported by the US EPA in the public dataset. That dataset contained target formation sampling data that included TDS values. The FOIA documents were attached to the EPA dataset using GIS techniques. These GIS files can be found for download in the link at the bottom of this page.

Map 1. Aquifer exemptions in Colorado

View map fullscreen | How FracTracker maps work

Map 1 above shows the locations of aquifer exemptions in Colorado, as well as the locations of Class II injection wells. These sites are overlaid on a spatial assessment of groundwater quality (a map of the groundwater’s quality), which was generated for the entire state. The changing colors on the map’s background show spatial trends of TDS values, a general indicator of overall groundwater quality.

In Map 1 above, we see that the majority of Class II injection wells and aquifer exemptions are located in regions with higher quality water. This is a common trend across the state, and needs to be addressed.

Our review of aquifer exemption data in Colorado shows that aquifer exemption applications were granted for areas reporting TDS values less than 3,000 mg/l, which contradicts the information reported by the COGCC as permitting guidelines. Additionally, of the 175 granted aquifer exemptions for which the FOIA returned data, 141 were formations with groundwater samples reported at less than 10,000 mg/l TDS. This is half of the total number (283) of aquifer exemptions in the state of Colorado.

When we mapped where class II injection wells are permitted, a total of 587 class II wells were identified in Colorado, outside of an aquifer exemption area. Of the UIC-approved injection wells identified specifically as disposal wells, at least 21 were permitted outside aquifer exemptions and were drilled into formations that were not hydrocarbon producing. Why these injection wells are allowed to operate outside of an aquifer exemption is unknown – a question for regulators.

You can see in the map that most of the aquifer exemptions and injection wells in Colorado are located in areas with lower TDS values. We then used GIS to conduct a spatial analysis that selected groundwater wells within five miles of the 21 that were permitted outside aquifer exemptions. Results show that groundwater wells near these sites had consistently low-TDS values, meaning good water quality. In Colorado, where groundwater is an important commodity for a booming agricultural industry and growing cities that need to prioritize municipal sources, permitting a Class II disposal well in areas with high quality groundwater is irresponsible.

Groundwater Monitoring Data Maps

Map 2. Water quality and depths of groundwater wells in Colorado

View live map | How FracTracker maps work

In Map 2, above, the locations of groundwater wells in Colorado are shown. The colors of the dots represent the concentration of TDS on the right and well depth on the left side of the screen. By sliding the bar on the map, users can visualize both. This feature allows people to explore where deep wells also are characterized by high levels of TDS. Users can also see that areas with high quality low TDS groundwater are the same areas that are the most developed with oil and gas production wells and Class II injection wells, shown in gradients of purple.

Statistical analysis of this spatial data gives a clearer picture of which regions are of particular concern; see below in Map 3.

Map 3. Spatial “hot-spot” analysis of groundwater quality and depth of groundwater wells in Colorado

View live map | How FracTracker maps work

In Map 3, above, the data visualized in Map 2 were input into a hot-spots analysis, highlighting where high and low values of TDS and depth differ significantly from the rest of the data. The region of the Front Range near Denver has significantly deeper wells, as a result of population density and the need to drill municipal groundwater wells.

The Front Range is, therefore, a high-risk region for the development of oil and gas, particularly from Class II injection wells that are necessary to support development.

Methods Notes: The COGCC publishes groundwater monitoring data for the state of Colorado, and groundwater data is also compiled nationally by the Advisory Committee on Water Information (ACWI). (Data from the National Groundwater Monitoring Network is sponsored by the ACWI Subcommittee on Ground Water.) These datasets were cleaned, combined, revised, and queried to develop FracTracker’s dataset of Colorado groundwater wells. We cleaned the data by removing sites without coordinates. Duplicates in the data set were removed by selecting for the deepest well sample. Our dataset of water wells consisted of 5,620 wells. Depth data was reported for 3,925 wells. We combined this dataset with groundwater data exported from ACWI. Final count for total wells with TDS data was 11,754 wells. Depth data was reported for 7,984 wells. The GIS files can be downloaded in the compressed folder at the bottom of this page.

Site Assessments – Exploring Specific Regions

Particular regions were further investigated for impacts to groundwater, and to identify areas that may be at a high risk of contamination. There are numerous ways that groundwater wells can be contaminated from other underground activity, such as hydrocarbon exploration and production or waste injection and disposal. Contamination could be from hydraulic fracturing fluids, methane, other hydrocarbons, or from formation brines.

From the literature, brines and methane are the most common contaminants. This analysis focuses on potential contamination events from brines, which can be detected by measuring TDS, a general measure for the mixture of minerals, salts, metals and other ions dissolved in waters. Brines from hydrocarbon-producing formations may include heavy metals, radionuclides, and small amounts of organic matter.

Wells with high or increasing levels of TDS are a red flag for potential contamination events.

Methods

Groundwater wells at deep depths with high TDS readings are, therefore, the focus of this assessment. Using GIS methods we screened our dataset of groundwater wells to only identify those located within a buffer zone of five miles from Class II injection wells. This distance was chosen based on a conservative model for groundwater contamination events, as well as the number of returned sample groundwater wells and the time and resources necessary for analysis. We then filtered the groundwater wells dataset for high TDS values and deep well depths to assess for potential impacts that already exist. We, of course, explored the data as we explored the spatial relationships. We prioritized areas that suggested trends in high TDS readings, and then identified individual wells in these areas. The data initially visualized were the most recent sampling events. For the wells prioritized, prior sampling events were pulled from the data. The results were graphed to see how the groundwater quality has changed over time.

Case of Increasing TDS Readings

If you zoom to the southwest section of Colorado in Map 2, you can see that groundwater wells located near the injection well 1 Fasset SWD (EPA) (05-067-08397) by Operator Elm Ridge Exploration Company LLC were disproportionately high (common). Groundwater wells located near this injection well were selected for, and longitudinal TDS readings were plotted to look for trends in time. (Figure 1.)

The graphs in Figure 1, below, show a consistent increase of TDS values in wells near the injection activity. While the trends are apparent, the data is limited by low numbers of repeated samples at each well, and the majority of these groundwater wells have not been sampled in the last 10 years. With the increased use of well stimulation and enhanced oil recovery techniques over the course of the last 10 years, the volumes of injected wastewater has also increased. The impacts may, therefore, be greater than documented here.

This area deserves additional sampling and monitoring to assess whether contamination has occurred.

Figures 1a and 1b. The graphs above show increasing TDS values in samples from groundwater wells in close proximity to the 1 Fassett SWD wellsite, between the years 2004-2015. Each well is labeled with a different color. The data for the USGS well in the graph on the right was not included with the other groundwater wells due to the difference in magnitude of TDS values (it would have been off the chart).

Groundwater Contamination Case in 2007

We also uncovered a situation where a disposal well caused groundwater contamination. Well records for Class II injection wells in the southeast corner of Colorado were reviewed in response to significantly high readings of TDS values in groundwater wells surrounding the Mckinley #1-20-WD disposal well.

When the disposal well was first permitted, farmers and ranchers neighboring the well site petitioned to block the permit. Language in the grant application is shown below in Figure 2. The petitioners identified the target formation as their source of water for drinking, watering livestock, and irrigation. Regardless of this petition, the injection well was approved. Figure 3 shows the language used by the operator Energy Alliance Company (EAC) for the permit approval, which directly contradicts the information provided by the community surrounding the wellsite. Nevertheless, the Class II disposal well was approved, and failed and leaked in 2007, leading to the high TDS readings in the groundwater in this region.

Figure 2. Petition by local landowners opposing the use of their drinking water source formation for the site of a Class II injection disposal well.

Figure 3. The oil and gas operation EAC claims the Glorietta formation is not a viable fresh water source, directly contradicting the neighboring farmers and ranchers who rely on it.

Figure 4. The COGCC well log report shows a casing failure, and as a result a leak that contaminated groundwater in the region.

Areas where lack of data restricted analyses

In other areas of Colorado, the lack of recent sampling data and longitudinal sampling schemes made it even more difficult to track potential contamination events. For these regions, FracTracker recommends more thorough sampling by the regulatory agencies COGCC and USGS. This includes much of the state, as described below.

Southeastern Colorado

Our review of the groundwater data in southeastern Colorado showed a risk of contamination considering the overlap of injection well depths with the depths of drinking water wells. Oil and gas extraction and Class II injections are permitted where the aquifers include the Raton formation, Vermejo Formation, Poison Canyon Formation and Trinidad Sandstone. Groundwater samples were taken at depths up to 2,200 ft with a TDS value of 385 mg/l. At shallower depths, TDS values in these formations reached as high as 6,000 mg/l, and 15 disposal wells are permitted in aquifer exemptions in this region. Injections in this area start at around 4,200 ft.

In Southwestern Colorado, groundwater wells in the San Jose Formation are drilled to documented depths of up to 6,000 feet with TDS values near 2,000 mg/l. Injection wells in this region begin at 565 feet, and those used specifically for disposal begin at below 5,000 feet in areas with aquifer exemptions. There are also four disposal wells outside of aquifer exemptions injecting at 5,844 feet, two of which are not injecting into active production zones at depths of 7,600 and 9,100 feet.

Western Colorado

In western Colorado well Number 1-32D VANETA (05-057-06467) by Operator Sandridge Exploration and Production LLC’s North Park Horizontal Niobara Field in the Dakota-Lokota Formation has an aquifer exemption. The sampling data from two groundwater wells to the southeast, near Coalmont, CO, were reviewed, but we can’t get a good picture due to the lack of repeat sampling.

Northwestern Colorado

http://digital.denverlibrary.org/cdm/ref/collection/p16079coll32/id/346073

A crew from Bonanza Creek repairs an existing well in the McCallum oil field. Photo by Ken Papaleo / Rocky Mountain News

In Northwestern Colorado near Walden, CO and the McCallum oil field, two groundwater wells with TDS above 10,000 ppm were selected for review. There are 21 injection wells in the McCallum field to the northwest. Beyond the McCallum field is the Battleship field with two wastewater disposal wells with an aquifer exemption. West of Grover, Colorado, there are several wells with high TDS values reported for shallow wells. Similar trends can be seen near Vernon. The data on these wells and wells from along the northern section of the Front Range, which includes the communities of Fort Collins, Greeley, and Longmont, suffered from the same issue. Lack of deep groundwater well data coupled with the lack of repeat samples, as well as recent sampling inhibited the ability to thoroughly investigate the threat of contamination.

Trends and Future Development

Current trends in exploration and development of unconventional resources show the industry branching southwest of Weld County towards Fort Collins, Longmont, Broomfield and Boulder, CO.

These regions are more densely populated than the Front Range county of Weld, and as can be seen in the maps, the drinking water wells that access groundwaters in these regions are some of the deepest in the state.

This analysis shows where Class II injection has already contaminated groundwater resources in Colorado. The region where the contamination has occurred is not unique; the drinking water wells are not particularly deep, and the density of Class II wells is far from the highest in the state.

Well casing failures and other injection issues are not exactly predictable due to the variety of conditions that can lead to a well casing failure or blow-out scenario, but they are systemic. The result is a hazardous scenario where it is currently difficult to mitigate risk after the injection wells are drilled.

Allowing Class II wells to expand into Front Range communities that rely on deep wells for municipal supplies is irresponsible and dangerous.

The encroachment of extraction into these regions, coupled with the support of Class II injection wells to handle the wastewater, would put these groundwater wells at particular risk of contamination. Based on this analysis, we recommend that regulators take extra care to avoid permitting Class II wells in these regions as the oil and gas industry expands into new areas of the Front Range, particularly in areas with dense populations.

Feature Image: Joshua Doubek / WIKIMEDIA COMMONS

Article by: Kyle Ferrar, Western Program Coordinator, FracTracker Alliance

October 31, 2017 Edit: This post originally cited the Clean Water Act instead of the Safe Drinking Water Act as the source that EPA uses to grant aquifer exemptions.

ME2 pipeline and spills map by Kirk Jalbert

Mariner East 2 Drilling Fluid Spills – Updated Map and Analysis

July 26, 2017/by FracTracker Alliance

Updated 8/2/17: An analysis by FracTracker and the Clean Air Council finds that approximately 202,000 gallons of drilling fluids have been accidentally released in 90 different spill events while constructing the Mariner East 2 pipeline in Pennsylvania. In a more recent update, FracTracker estimates these occurred at 42 distinct locations. Explore the map of these incidents below, which we have updated to reflect this growing total.

Last week, a judge with the PA Environmental Hearing Board granted a two week halt to horizontal directional drilling (HDD) operations pertaining to the construction of Sunoco Logistics’ Mariner East 2 (ME2) pipeline. The temporary injunction responds to a petition from the Clean Air Council, Mountain Watershed Association, and the Delaware Riverkeeper Network. It remains in effect until a full hearing on the petition occurs on August 7-9, 2017.

ME2 is a 350-mile long pipeline that, when complete, will carry 275,000 barrels of propane, ethane, butane, and other hydrocarbons per day from the shale gas fields of Western Pennsylvania to a petrochemical export terminal located on the Delaware River.

The petition relates to a complaint filed by the three groups detailing as many as 90 “inadvertent returns” (IRs) of drilling fluids and other drilling related spills along ME2’s construction route. IRs refer to incidents that occur during HDD operations in which drilling fluids consisting of water, bentonite clay, and some chemical mixtures used to lubricate the drill bit, come to the surface in unintended places. This can occur due to misdirected drilling, unanticipated underground fissures, or equipment failure.

What is Horizontal Directional Drilling?

An illustration of an “ideal” horizontal directional drilling boring operation is seen in the first graphic below (image source). The second image shows what happens when HDDs go wrong (image source).

Mapping Inadvertent Returns

The Pennsylvania Department of Environmental Protection (DEP) posted information on potential regulatory violations associated with these IRs on the PA Pipeline Portal website on July 24, 2017. This original file listed 49 spill locations. Our original map was based on those locations. As part of their legal filing, volunteer at the Clean Air Council (CAC) have parsed through DEP documents to discover 90 unique spills at these and other locations. On July 31, 2017, the DEP posted a new file that now lists 61 spills, which account for some of these discrepancies but not all.

Working with the CAC, we have created a map, seen below, of the 90 known IRs listed in the DEP documents and from CAC’s findings. Also on the map are the locations of all of ME2’s HDD boring locations, pumping stations, and workspaces, as well as all the streams, ponds, and wetlands listed in Sunoco’s permits as implicated in the project’s construction (see our prior article on ME2’s watershed implications here). Open the map full-screen to see many of these features and their more detailed information.

View map fullscreen | How FracTracker maps work

Analysis Results for ME2

From our analysis, we find that, conservatively, more than 202,000 gallons of drilling fluids have been accidentally released while constructing the Mariner East 2 pipeline in Pennsylvania since the first documented incident on May 3rd. We say conservatively because a number of incidents are still under investigation. In a few instances we may never know the full volume of the spills as only a fraction of the total drilling muds lost were recovered.

We analyzed where these 90 spills occurred relative to known HDD sites and estimate that there are 38 HDDs implicated in these accidents. An additional 11 spills were found at sites where the DEP’s data shows no HDDs, so we calculate the total number of “spill locations” at 42. A full breakdown by county and known gallons spilled at these locations is seen below.

County	Number of IRs/Spills	Gallons Spilled
Allegheny	4	2,050
Berks	3	540
Blair	3	2,400
Chester	4	205
Cumberland	32	162,330
Delaware	8	2,380
Huntingdon	1	300
Lancaster	7	5945
Lebanon	1	300
Washington	9	4,255
Westmoreland	17	21,532
York	1	25
Total	90	202,262

A few important notes on our methods and the available data we have to work with:

CAC obtained spills from DEP incident reports, inadvertent return reports, and other documents describing spills of drilling fluid that have occurred during Mariner East 2 construction. Those documents reflected incidents occurring between April 25, 2017 and June 17, 2017. In reviewing these documents, volunteers identified 61 discrete spills of drilling fluid, many of which happened at similar locations. Unfortunately, separate coordinates and volumes were not provided for each spill.
When coordinates were not provided, approximate locations of spills were assigned where appropriate, based on descriptions in the documentation. Two IRs have no known location information whatsoever. As such, they are not represented on the map.
Spill volumes were reported as ranges when there was inconsistency in documentation regarding the same spill. The map circles represent the high-end estimates within these ranges. Of the 90 known spills, 29 have no volume data. These are represented on the map, but with a volume estimate of zero until more information is available.
All documentation available to CAC regarding these spills was filed with the Environmental Hearing Board on July 19, 2017. DEP subsequently posted a table of inadvertent returns on its website on July 24, 2017. Some of those spills were the same as ones already identified in documents CAC had reviewed, but 29 of the spills described on the DEP website were ones for which CCAC had never received documentation, although a subset of these are now listed in brief in the DEP spreadsheet posted on July 31, 2017. In total then, the documentation provided to CAC from DEP and spreadsheets on the DEP website describe at least 90 spills.

HDD Implications

The DEP’s press release assures the public that the drilling fluids are non-toxic and the IRs are “not expected to have any lasting effects on impacted waters of the commonwealth.” But this is not entirely the case. While the fluids themselves are not necessarily a public health threat, the release of drilling fluids into aquifers and drinking wells can make water unusable. This occurred in June in Chester County, for example.

More commonly, drilling fluid sediment in waterways can kill aquatic life due to the fine particulates associated with bentonite clay. Given that HDD is primarily used to lay pipe under streams, rivers, and ponds (as well as roads, parks, and other sensitive areas), this latter risk is a real concern. Such incidents have occurred in many of the instances cited in the DEP documents, including a release of drilling muds into a creek in Delaware County in May.

We hope the above map and summaries provide insights into the current risks associated with the project and levels of appropriate regulatory oversight, as well as for understanding the impacts associated with HDD, as it is often considered a benign aspect of pipeline construction.

By Kirk Jalbert, Manager of Community Based Research and Engagement, FracTracker Alliance

If you have any questions about the map on this page or the data used to create it, please contact Kirk Jalbert at jalbert@fractracker.org.

Pipeline Class Locations

What Class Locations Dictate

Residential Structures

Recreational Areas

New Housing Developments

Issues with Setbacks

Related Articles

High Consequence Areas

Populated Areas

USAs: Drinking Water

USAs: Ecological Resource

Calculating HCAs

What HCAs Dictate

The Falcon Risk Zones

The PIR (or “Blast Zone”)

The HCA (or “Vapor Zone”)

Populated Areas

Drinking Water Sources

Ecological Areas

Related Articles

Land Cover Assessment

Botanical Studies

Short-eared Owls & Northern Harriers

Bald Eagles

Bald Eagle Study Gaps?

Important Bird Areas

No Peregrine Falcon?

Federally Protected Bats

Bat Study Gaps?

A Note on Noise Control

Freshwater Mussels

Coldwater Fish

Eastern Hellbenders

Allowable Work Dates

Land Disturbances

Aquatic Disturbances

Related Articles

Mined Lands

Beaver Valley Mine

Coal Slurry Site, Imperial PA

Foreign Pipelines

Shared Rights-of-Way

Oil & Gas Extraction

Related Articles

Finding the Data

Viewing the Data

Archiving the Data

Transparency & Caveats

Related Articles

Following the Fight

More Information and Resources

A Pipeline’s History

“What Waters Run Through My Veins…”

Migration of the Sandhill Cranes

Giving Sandhill Cranes a Voice

Taking Action, Speaking Out

Research shows injection wells do fail

Will existing Class II wells fail?

Aquifer Exemptions in Colorado

Groundwater Monitoring Data Maps

Site Assessments – Exploring Specific Regions

Methods

Case of Increasing TDS Readings

Groundwater Contamination Case in 2007

Areas where lack of data restricted analyses

Southeastern Colorado

Western Colorado

Northwestern Colorado

Trends and Future Development

What is Horizontal Directional Drilling?

Mapping Inadvertent Returns

Analysis Results for ME2

HDD Implications