http://www.bakersfield.com/news/arvin-looks-to-impose-more-regulations-on-oil-gas-operators/article_2beb26d6-cbdc-11e7-ba1a-4b0ac35a0fa8.html

Arvin, CA – a City in the Most Drilled County in the Country – files for a Setback Ordinance

The City of Arvin, with a population of about 20,000, is located in Kern County, California just 15 miles southeast of Bakersfield. Nicknamed ‘The Garden in the Sun,’ Arvin is moving forward with establishing new regulations that would limit oil and gas development within the city limits.

Setback Map

The new ordinance proposes setback distances for sensitive sites including hospitals and schools, as well as residentially and commercially zoned parcels. The proposal establishes a 300-foot buffer for new development and 600’ for new operations.

In the map below, FracTracker Alliance has mapped out the zoning districts in Arvin and mapped the reach of the buffers around those districts. The areas where oil and gas well permits will be blocked by the ordinance are shown in green, labeled “Buffered Protected Zones.” The “Unprotected Zones” will still allow oil and gas permits for new development.

There are currently 13 producing oil and gas wells within the city limits of Arvin, 11 of them are located in the protected zones. Those within the protected zones are operated by Sun Mountain Oil and Gas and Petro Capital Resources. They were all drilled prior to 1980, and are shown in the map below.

Map 1. Arvin, CA Proposed setback ordinance

View map fullscreen | How FracTracker maps work

Information on the public hearings and proposals can be found in the Arvin city website, where the city posts public notices. As of January 24, 2018, these are the current documents related to the proposed ordinance that you will find on the webpage:

Earlier Proposals in Arvin

The proposed 2017 setback ordinance is in response to a previously proposed 2016 ordinance that would allow Kern County to fast track permits for oil and gas activities without environmental review or any public notice for the next 20 years. This could mean 72,000 new wells without review, in an area that already possesses the worst air quality in the country. Communities of color would of course be disproportionately impacted by such policy. In Kern County, the large percentage of Latinx residents suffer the impacts of oil drilling and fracking operations near their homes schools and public spaces.

In December of 2016, Committee for a Better Arvin, Committee for a Better Shafter, and Greenfield Walking Group, represented by Center for Race, Poverty and the Environment, sued Kern County. The lawsuit was filed in coordination with EarthJustice, Sierra Club, Natural Resources Defense Council, and the Center for Biological Diversity.

The Importance of Local Rule

Self-determination by local rule is fundamental of United States democracy, but is often derailed by corporate industry interests by the way of state pre-emption. There is a general understanding that local governments are able to institute policies that protect the interests of their constituents, as long as they do not conflict with the laws of the state or federal government. Typically, local municipalities are able to pass laws that are more constrictive than regional, state, and the federal government.

Unfortunately, when it comes to environmental health regulations, states commonly institute policies that preserve the rights of extractive industries to access mineral resources. In such cases, the state law “pre-empts” the ability of local municipalities to regulate. Local laws can be considered the mandate of the people, rather than the influence of outside interest on representatives. Therefore, when it comes to land use and issues of environmental health, local self-determination must be preserved so that communities are empowered in their decision making to best protect the health of their citizens.

For more on local policies that regulate oil and gas operations in California, see FracTracker’s pieces, Local Actions in California, as well as What Does Los Angeles Mean for Local Bans?


By Kyle Ferrar, Western Program Coordinator, FracTracker Alliance

Feature image by: Henry A. Barrios / The Californian

Falcon Public EIA Project feature image

Wingspan of the Falcon Pipeline

A Public EIA of Shell’s Ethane Cracker Pipeline

Pittsburgh, Pennsylvania – Jan. 29 – FracTracker Alliance has released a detailed environmental impact assessment (EIA), including digital maps, of the Falcon Ethane Pipeline being built to feed Shell Appalachia’s ethylene cracker plant in Beaver County, PA.

FracTracker’s Falcon Public EIA Project offers a rich series of interactive maps and articles detailing the Falcon’s proposed route through PA, WV, and OH, likely impacts to waterways, potential blast zones, ecological footprint, proximity to hazardous industrial areas, and more.

Given the issues associated with Mariner East 2 – a PA-based natural gas liquids pipeline whose history has been fraught with citations, public scrutiny is a crucial facet of pipeline construction. The Falcon Public EIA Project represents the first time that public stakeholders have been given such a significant amount of time and detail to investigate a proposed pipeline, including access to specific location information. Public comments are being accepted by the PA Department of Environmental Protection on the Falcon’s permit until February 20th.

“Companies are generally not required to publicly disclose GIS data when applying for permits,” remarked Kirk Jalbert, project lead and Manager of Community Based Research and Engagement at FracTracker. “While concerned citizens can stitch together paper maps provided by companies in their applications, that process can be complex and very labor intensive.”

With FracTracker’s project, however, digital maps and figures are front and center.

Early access to what is being proposed for the Falcon pipeline will enable nearby communities to better understand how its construction and the associated ethane cracker facility, which will produce 1 million tons of ethylene annually for making plastics, will affect their lives. Upon analyzing the data, FracTracker uncovered a number of particularly noteworthy statistics, for example:

  • There are 97.5 miles of pipeline proposed to be built through 22 townships in 3 states.
  • 2,000 properties have been surveyed; 765 easements executed.
  • Falcon will intersect 319 streams and 174 wetlands, with hundreds more proximate to work areas.
  • 550 family residences, 20 businesses, 240 groundwater wells, 12 public parks, 5 schools, 6 daycare centers, and 16 emergency response centers are within potential risk areas.
  • Learn more

“Extreme levels of risk and injustice are commonplace in petrochemical pipeline siting, as well as in where their contents come from and how they get used. This project provides context for the importance of reducing these impacts, both for curtailing environmentally unfriendly plastics as well as for moving away from fossil fuel dependencies,” said Brook Lenker, Executive Director of FracTracker.

The Falcon Public EIA Project is meant to expand public dialogue about what should be included in EIAs and how they should apply to petrochemical pipelines. The project also serves as a model for how regulatory agencies can be more transparent with data when engaging the public. This is especially important in the case of the Falcon pipeline, which will be exempt from Federal Energy Regulatory Commission (FERC) scrutiny and, therefore, not be subject to a full environmental impact assessment.

Pipeline Regulations & Impact Assessments, a Primer

Part of the Falcon Public EIA Project

Pipelines are categorized by what they carry — natural gas, oil, or natural gas liquids (NGLs) — and where they go — interstate or intrastate. The regulatory system is complicated. This primer is a quick guide to the agencies that may be involved in Falcon’s permit reviews.

Regulating Pipelines

The siting of natural gas pipelines crossing state or country boundaries is regulated by the Federal Energy Regulatory Commission (FERC). Meanwhile, determination of the location of natural gas routes that do not cross such boundaries are not jurisdictional to FERC, instead determined by the owner pipeline company. Hazardous liquids and NGL pipelines are not regulated for siting by FERC regardless of their location and destination. However, FERC does have authority over determining rates and terms of service in these cases. The U.S. Army Corps of Engineers gets involved when pipelines cross navigable waters such as large rivers and state Environmental Protection Agencies.

Pipeline design, operation, and safety regulations are established by the Pipeline and Hazardous Materials Safety Administration (PHMSA), but these regulations may vary state-by-state as long as minimal federal standards are met by the pipeline project. Notably, PHMSA’s oversight of safety issues does not determine where a pipeline is constructed as this is regulated by the different agencies mentioned above – nor are PHMSA’s safety considerations reviewed simultaneously in siting determinations done by other agencies.

An excerpt from the U.S. Army Corps’ EIS of the Atlantic Sunrise pipeline

These federal agencies are required by the National Environmental Policy Act (NEPA) to prepare an Environmental Impact Statement (EIS) investigating how the pipeline pertains to things like the Clean Water Act, the Endangered Species Act, the National Historic Preservation Act, as well as state and local laws. The image above, for instance, is a caption from the Army Corp’s assessment of the Atlantic Sunrise, a natural gas pipeline.

An EIS is based on surveying and background research conducted by the company proposing the project, then submitted to agencies as an Environmental Impact Assessment (EIA). An EIS can exceed hundreds of pages and can go through many drafts as companies are asked to refine their EIA in order to qualify for approval.

An excerpt from the PA DEP’s review of water crossings for the Mariner East 2 pipeline

Pipeline proposals are also evaluated by state and local agencies. In Pennsylvania, for instance, the PA DEP is responsible for assessing how to minimize pipeline impacts. The DEP’s mission is to protect Pennsylvania’s air, land and water from pollution and to provide for the health and safety of its citizens through a cleaner environment. The PA Fish and Boat Commission oversees the avoidance or relocation of protected species. Local township zoning codes can also apply, such as to where facilities are sited near zoned residential areas or drinking reservoirs, but these can be overruled by decisions made at the federal level, especially when eminent domain is granted to the project.

Regulating the Falcon

For the Falcon pipeline, an interstate pipeline that will transport ethane (an NGL), FERC will likely have authority over determining rates and terms of service, but not siting. Construction permitting will be left state agencies and PHMSA will retain its federal authority with the Pennsylvania Public Utilities Commission (PUC) acting as PHMSA’s state agent to ensure the project complies with federal safety standards and to investigate violations. The Army Corps will almost certainly be involved given that the Falcon will cross the Ohio River. As far as we know, the Falcon will not have eminent domain status because it supplies a private facility and, thus, does not qualify as a public utility project.

Questioning Impact Assessments

The contents of EIAs vary, but are generally organized along the lines of the thematic categories that we have created for assessing the Falcon data, as seen above. However, there is also much that EISs fail to adequately address. The Army Corp’s assessment of the Atlantic Sunrise is a good example. The final EIS resulting from the operators EIA includes considerations for socioeconomic impacts, such effects on employment and environmental justice, as seen in the excerpt below. But potential negative impact in these areas are not necessarily linked to laws requiring special accommodations. For instance, federal regulations mandate achieving environmental justice by “identifying and addressing, as appropriate, disproportionately high and adverse human health or environmental effects” of projects subject to NEPA’s EIS requirement. However, there are no laws that outline thresholds of unacceptable impact that would disallow a project to proceed.

An excerpt from the Atlantic Sunrise EIS addressing environmental justice concerns

Furthermore, the narratives of EIAs are almost always written by the companies proposing the project, using sources of data that better support their claims of minimal or positive impact. This is again seen in the Atlantic Sunrise EIS, where several studies are cited on how pipelines have no affect on property values or mortgages, with no mention of other studies that contradict such findings. Other factors that may be important when considering pipeline projects, such as concerns for sustainability, climate change, or a community’s social well-being, are noticeably absent.

Complicating matters, some pipeline operators have been successful in skirting comprehensive EIAs. This was seen in the case of the Mariner East 2 pipeline. Despite being the largest pipeline project in Pennsylvania’s history, a NEPA review was never conducted for ME2.

* * *

Related Articles

By Kirk Jalbert, FracTracker Alliance

The Falcon: Routes, Facilities & Easements

Part of the Falcon Public EIA Project

In this segment of the Falcon Public EIA Project, we first focus on the route of the pipeline and prior routes that were considered. We take a closer look at the properties along the route that required easement agreements from landowners. Finally, we locate facilities that will be built as part of the project, such as metering stations and shut-off valves, as well as the pipeline’s construction areas and access roads.

Quick Falcon Facts

  • 97.5 miles of proposed pipeline (an additional 200+ miles surveyed during the process)
  • 2,000 parcels of land surveyed; 765 easements executed; 469 will be needed to execute the route
  • Five meter pads and 18 shut-off valves
  • 111 temporary access roads, 21 permanent access roads
  • 1,273 acres required for construction space; 650 acres for the permanent right-of-way

Map of Falcon pipeline routes, properties, and facilities

The following map will serve as our guide in breaking down these first components. Expand the map full-screen to explore its contents in greater depth. Some layers only become visible at closer zoom levels. Click the “details” tab in full-screen mode to read how the different layers were created.

View Map Fullscreen | How FracTracker Maps Work


Finding a Right-of-Way

Pipeline operators must consider a variety of factors when searching for a viable right of way (ROW) for their project—the continuous stretch of land needed to construct, maintain, and operate the pipeline. This process begins with reviewing data and maps made available by federal, state, and local agencies in order to identify features that would complicate the project. These might include such things as protected wetlands, drinking water sources, abandoned mines, or heavily populated areas.

A second step is to conduct manual field surveys along their planned route. During this stage, engineers do precise measurements to determine how the pipeline will cross individual properties as well as locate site-specific concerns that need to be accounted for, such as the presence of endangered species or archeological sites. FracTracker previously produced a guide to pipeline surveying, which can be found here.

The process of finding a viable pipeline route can undergo dozens of revisions and take months or years to complete. The example image seen below, taken from our interactive map at the top of the page, shows a few of the many different 50ft. ROWs considered by Shell. These were documented every few months as the data changed.

A section of the Falcon route with prior routes considered

The most recent route is highlighted in red, totaling 97.5 miles (Shell’s original press releases stated 94 miles). Segments that represent alternative routes considered in certain places are shown in blue (these earlier divergences total 19 miles). Other areas surveyed at some point in the process are shown in dotted purple (totaling 91.3 miles). Given that the route has changed very little in recent months, as well as the fact that Shell has submitted their permit applications for project, we believe that the route in red is likely the route proposed to regulatory agencies.

Note that, in the interactive map, there is an additional “Air Liquide” pipeline (this is the name of a gas products company) proposed by Shell that will run from the ethane cracker south for about .5 miles. Based on comments made by Shell at public hearings, we assume this will be a nitrogen pipeline feeding the plant from an unknown source.

Acquiring Easements

Perhaps the most significant factor that can determine a pipeline route is finding landowners amenable to having their land surveyed and, ultimately, willing to sign easements to allow the pipeline on their property. In some instances, pipeline companies can be granted eminent domain as a “public utility” to take land by force (ME2). However, Shell has stated publicly that eminent domain in not an option for Falcon, due to the fact that the pipeline services a private facility. FracTracker previously produced a guide for landowners who might be approached by pipeline operators seeking to survey their properties.

The Falcon pipeline will have a permanent ROW of 50ft that will cross 10 municipalities in Pennsylvania, 12 townships in Ohio, as well as northern Hancock County, West Virginia. More than 2,000 individual parcels of land were surveyed across this region. Of those 2,000, Shell approached landowners for 765 unique parcels at some point in the process to obtain easements, either for the pipeline ROW itself or for access roads.

To date, Shell has executed 572 easements. Of these, 469 will be needed to execute the current proposed route. However, as of this time, 14 parcels along the proposed route are still listed as “landowner contacted,” meaning that the easement has not yet been executed. The image below is a page from Shell’s permit applications to the PA DEP listing properties pending in Pennsylvania.

Pending PA easements from Shell’s permit applications

Media sources have reported on some of the details of Shell’s Pipeline easement agreements. In some instances, contracts stated a transactional price of $10 per linear foot as a “placeholder” to get the process started. In other cases, Shell has paid landowners as much as $75 per linear foot of pipeline. These agreements also state that Shell reserved the right to “lay, construct, test, maintain, inspect, operate, repair, renew, relocate, replace, substitute, change the size of, upgrade, alter, mark, protect and remove or abandon in place” any pipelines on the property. Below is an example of how our interactive map represents these parcels and their status. For instance, executed easements are in green and pending or stalled agreements in yellow.

Parcels along the Falcon route and their easement status

Valves & Metering Stations

Pipelines require a number of facilities to properly manage the flow and pressure of gas from one end of the line to another. For instance, metering stations are installed to measure how much gas is in the pipeline system at given points. Falcon has five “pads” where metering stations will be located. Three of these are co-located at the origin points of the pipeline (the MarkWest separator facilities) and a fourth at the ethane cracker end-point. However, the fifth meter stations will be located where the two legs of the pipeline meet in northeast Raccoon Township, Beaver County, PA. This site is called the “Junction” meter pad.

Shut-off valves will also placed along the route—18 in all for Falcon—in order to section off lengths of the pipeline that can be turned off as needed. These valves will be located at fairly regular intervals of 8-10 miles in most places, but are also found just before and after sensitive locations, such as the Oho River crossing and areas and where the lines juncture.

The Risks of Proximity

Metering stations and shut-off valves bring particular risks. For instance, when valves are closed at a section of pipeline for maintenance, or in the event of an emergency, excess gasses must vented to relieve pressure. This is one reason why communities have become concerned about the location of these facilities, such as with a Mariner East 2 pipeline valve in West Goshen Township, PA. Similarly, the Falcon pipelines’ valve in New Somerset, OH, is especially close to residential areas, seen below.

A proposed Falcon shut-off valve site in New Somerset, Ohio

Workspaces & Access Roads

Finally, pipeline operators must identify in their permit applications the “workspace” needed for construction. Shell’s temporary ROW for workspace is approximately 100ft in most stretches along the Falcon’s route, similar to what is shown in the image below. Site-specific conditions, such as road, railroad crossings, and buildings make the workspace narrower in some instances, but much larger workspaces will be needed around sites like metering stations and shut-off valves.

A typical pipeline workspace; this one from the Mariner East 2

The locations of access roads must also be identified in permit applications. Access roads come in two categories and typically require a 25ft ROW. Temporary access roads are used during the construction process and often utilize existing private driveways, farm roads, or are built after clearing land acquired in the easement process. Permanent roads allow long-term access to facilities, such as valves and pumping stations, as well as for bringing in equipment to maintain the pipeline’s ROW. Shell’s plan proposes 111 temporary access roads (28 miles) and 21 permanent access roads (2.3 miles).

Shell’s permit applications state that the total disturbed workspace needed for construction and access roads is approximately 1,273 acres. About half of this will remain cleared for the permanent right-of-way and permanent access roads.

A Closer Look

When a pipeline project is subject to regulatory review, alternative routes are typically offered up by the operator for consideration in weighing different costs and benefits. Major reroutes typically deviate from the proposed route for significant distances in order to avoid significant impediments such as large cities or protected lands. Minor alternatives are shorter in length and used to avoid specific areas of concern, such as a protected wetland. An alternative route might also be selected in order to utilize an existing ROW from other pipelines.

Ohio River Crossing

As noted, there are a number of places along the Falcon route where we see examples of major route changes. Many of these reroutes appear to be due to landowners along the preferred path not signing easements for one reason or another. One of the more significant change occurred at the location where the Falcon crosses the Ohio River in Hancock County, West Virginia, seen below. For many months, Shell’s maps showed a planned crossing south of the current proposed route, but later took a dramatic diversion to the north, apparently due to an easement not having been executed for a single property. What is notable about the new route is that it utilizes property owned by the popular Mountaineer Casino, Racetrack, and Resort.

The current and former Falcon route crossing the Ohio River

Fort Cherry Golf Course Reroute

In another instance, we see a reroute near the Fort Cherry Golf Course in McDonald, Washington County, PA. An earlier route took the Falcon straight through the course, whereas the current proposed route goes further east, disrupting a smaller number of fairways. Notice in the image below that a temporary access road for the pipeline’s construction will also still utilize Fort Cherry Golf Course’s driveway.

The current and former Falcon routes crossing the Ft. Cherry Golf Course

Montour Trail Intersections

Finally, we bring attention to what appears to be some of the few remaining properties with easements not yet settled in order to begin construction. As noted in the excerpt from Shell’s permit application at the top of this page, a number of parcels owned by the Montour Trail Council have a status of: “in negotiation and depended on submitted crossing permit applications,” presumably meaning they would agree to the easement if PA DEP approved Shell’s permits.

Falcon intersections with the Montour Trail

The Montour Trail is a 46-mile long multi-use non-motorized recreational rail-trail located in Washington and Allegheny County, PA, used by more than 400,000 people annually. It also makes up part of the Great Allegheny Passage (GAP), a trail system that stretches over 335 miles from Pittsburgh to Washington, DC. The trail is managed by the nonprofit Montour Trail Council with support from state agencies such as the Pennsylvania Department of Conservation and Natural Resources (DCNR).

We were surprised to find that the Montour Trail will be crossed by the Falcon in 9 locations: 5 by the pipeline itself, 3 by temporary access roads, and 1 by a permanent access road, as illustrated in the image above. Two of the pipeline intersections will be executed using HDD boring. The trail and its intersection with the Falcon can be seen by activating these layers on FracTracker’s interactive map, as illustrated in the image above.

 

* * *

Related Articles

By Kirk Jalbert, FracTracker Alliance

The Falcon: Water Crossings & Hazards

Part of the Falcon Public EIA Project

In this section of the Falcon Public EIA Project, we explore the hydrological and geological conditions of the pipeline’s construction areas. We first identify the many streams, wetlands, and ponds the Falcon must cross, as well as describe techniques Shell will likely use in these water crossings. The second segment of this section highlights how the areas in the Falcon’s path are known for their complex geological features, such as porous karst limestone and shallow water tables that can complicate construction.

Quick Falcon Facts

  • Intersects 319 streams; 361 additional streams located only 500ft from construction areas
  • Intersects 174 wetlands; 470 additional wetlands located only 500ft from construction areas
  • Majority of crossings will be open cuts and dry-ditch trenching
  • A total of 19 horizontal directional drilling (HDD) sites; 40 conventional boring sites
  • 25 miles of pipeline overlap karst limestone formations, including 9 HDD sites
  • 240 groundwater wells within 1/4 mile of the pipeline; 24 within 1,000ft of an HDD site

Map of Falcon water crossings and hazards

The following map will serve as our guide in breaking down the Falcon’s risks to water bodies. 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

Defining Water Bodies

The parts of Pennsylvania, West Virginia, and Ohio where the Falcon pipeline will be built lie within the Ohio River Basin. This landscape contains thousands of streams, wetlands, and lakes, making it one of the most water rich regions in the United States. Pipeline operators are required to identify waters likely to be impacted by their project. This two-step process involves first mapping out waters provided by the U.S. Geological Survey’s national hydrological dataset. Detailed field surveys are then conducted in order to locate additional waters that may not yet be accounted for. Many of the streams and wetlands we see in our backyards are not represented in the national dataset because conditions can change on the ground over time. Yet, plans for crossing these must also be present in pipeline operator’s permit applications.

Streams

Streams (and rivers) have three general classifications. “Perennial” streams flow year-round, are typically supplied by smaller up-stream headwaters, and are supplemented by groundwater. In a sense, the Ohio River would be the ultimate perennial stream of the region as all smaller and larger streams eventually end up there. “Intermittent” streams flow for only a portion of the year and are dry at times, such as during the summer when water tables are low. Finally, “ephemeral” streams flow only during precipitation events.

These classifications are important because they can determine the extent of aquatic habitat that streams can support. Working in streams that have no dry period can put aquatic lifeforms at elevated risk. For this and other reasons, many states further designate streams based on their aquatic life “use” and water quality. In Pennsylvania, for instance, the PA DEP uses the designations: Warm Water Fishes (WWF), Trout Stocked (TSF), Cold Water Fisheries (CWF) and Migratory Fishes (MF). Streams with exceptional water quality may receive an additional designation of High Quality Waters (HQ) and Exceptional Value Waters (EV).

Wetlands

Similar to streams, wetlands also have unique designations. These are based on the U.S. Fish and Wildlife Services’ national wetlands inventory. Wetlands are generally defined as “lands transitional between terrestrial and aquatic systems where the water table is usually at or near the surface or the land is covered by shallow water.” As such, wetlands are categorized by their location (such as a tidal estuary or an inland wetland that lacks flowing water), its substrate (bedrock, sand, etc.), and plant life that might be present. While there are hundreds of such categories, only four pertain to the wetlands present in the regions where the Falcon pipeline will be built. Their designations roughly translate to the following:

  • Palustrine Emergent (PEM): Marshes and wet meadows hosting perennial small trees, shrubs, mosses, or lichens
  • Palustrine Shrub (PSS): Similar to PEMs, but characterized by also having well-established shrubs
  • Palustrine Forested (PFO): Similar to PEMs and PSSs, but having trees larger than 6 meters high
  • Palustrine Unconsolidated Bottom (PUB) and Palustrine Opem Water (POW) (aka ponds)

Pipeline operators are required to report the crossing length of each wetland they will encounter, as well as the area of permanent and temporary disturbance that would occur in each of these wetlands. When building the pipeline, operators are required to ensure that all measures are taken to protect wetlands by minimizing impacts to plant life, as well as by taking “upland protective measures” to prevent sedimentation runoff during precipitation events. When undergoing FERC EIA scrutiny, operators are also required to limit the width of wetland construction areas to 75 feet or less.

Crossing Methods

Open-Cut Trenching

Pipeline operators use a variety of methods when crossing streams, wetlands, and ponds. Shorter length crossings often employ a rudimentary trench. After the cuts, construction crews attempts to repair damage done in the process of laying the pipeline. For longer crossings, operators can use boring techniques to go underneath water features.

Open-cut trenching

There are two general types of trenches. The first, “open-cut” crossings, are typically used for smaller waterbodies, such as in intermittent streams where flow may not be present during time of construction, or when construction can be completed in a short period of time (typically 24-48 hours). In this process, a trench is laid through the water body without other provisions in place.

The second type, “dry-ditch” crossing, are required by FERC for waterbodies up to 30 feet wide “that are state-designated as either coldwater or significant coolwater or warmwater fisheries, or federally-designated as critical habitat.” In these spaces, pumps are used to transfer stream flow around the area where trenching occurs. In places where sensitive species are present, dry-ditches must include a flume to allow these species to pass through the work area.

Conventional Boring

Conventional boring consists of creating a tunnel for the pipeline to be installed below roads, waterbodies, and other sensitive resources. Bore pits are excavated on either sides of the site. A boring machine is then used to tunnel under the resource and the pipeline is pushed through the bore hole.

Horizontal Directional Drilling

In more difficult or lengthy crossings, operators may choose to bore under a water feature, road, or neighborhood. Horizontal directional drilling (HDD) involves constructing large staging areas on either side of the crossing. A large drill bit is piloted through the ground along with thousands of gallons of water and bentonite clay for lubricant (commonly referred to as drilling muds). HDDs are designed to protect sensitive areas, but operators prefer not to use them as HDDs can be expensive and require in-depth planning in order for things to go well.

Bentonite sediment pollutes a stream at a Mariner East HDD spill site
(source: Washington, PA, Observer-Reporter)


An example of what happens when things are rushed can be seen in Sunoco’s Mariner East 2 pipeline. The PA DEP has cited Sunoco for over 130 inadvertent returns (accidental releases of drilling muds) since construction began. These spills led to damaged water wells and heavy sedimentation in protected streams, as exemplified in the image above. Making matters worse, Sunoco later violated terms of a settlement that required them to re-survey before recommencing construction. See FracTracker’s article on these spills.

Footprint of the Falcon

The overwhelming majority of Falcon’s water body crossings will be executed with either open-cut or dry-ditch methods. There are 40 locations where conventional boring will be used, but only a 3 are used for crossing water resources. Shell intends to use 19 HDDs and, of these, only 13 are used for crossing water bodies of some kind (the longest of which crosses the Ohio River). All other conventional and HDD boring locations will be used to cross under roads and built structures. This is not entirely unusual for pipelines. However, we noted a number of locations where one would expect to see HDDs but did not, such as in the headwaters of the Ambridge and Tappen Reservoirs, as was seen in the images above.

Stream Impacts

Shell identified and/or surveyed a total of 993 stream sections in planning for the Falcon’s construction. As shown on FracTracker’s map, the pipeline’s workspace and access roads will directly intersect 319 of these streams with the following classifications: perennial (96), ephemeral (79), and intermittent (114). An additional 361 streams are located only 500ft from construction areas.

A number of these streams have special designations assigned by state agencies. For instance, in Pennsylvania, we found 10 stream segments listed as Trout Stocked (TS), which are shown on our interactive map.

Crossing HQ headwater streams of the Ambridge Reservoir

Perhaps more concerning, the Falcon will cross tributaries to the Service Creek watershed 13 times. These feed into three High Quality Cold Water Fishes (HQ/CWF) headwater streams of the Ambridge Reservoir in Beaver County, PA, shown in the image above. They also support the endangered Southern Redbelly Dace (discussed in greater depth here). On the eastern edge of the watershed, the Falcon will cross the raw water line leading out of the reservoir.

The reservoir supplies 6.5 million gallons of water a day to five townships in Beaver County (Ambridge, Baden, Economy, Harmony, and New Sewickley) and four townships in Allegheny County (Leet, Leetsdale, Bell Acres & Edgeworth). This includes drinking water services to 30,000 people.

We found a similar concern in Ohio where the Falcon will cross protected headwaters in the Tappan Reservoir watershed at six different locations. The Tappan is the primary drinking water source for residents in Scio. Below is a page from Shell’s permit applications to the PA DEP outlining the crossing of one of the Ambridge Reservoir’s CWF/HQ headwater streams.

Wetland Impacts

Shell identified a total of 682 wetland features relevant to Falcon’s construction, as well as 6 ponds. Of these, the pipeline’s workspace and access roads will directly intersect 174 wetlands with the following classifications: PEM (141), PSS (13), PFO (7), PUB (10), POW (3). An additional 470 of these wetlands, plus the 6 ponds, are located only 500ft from construction areas.

Example 1: Lower Raccoon Creek

A few wetland locations stand out as problematic in Shell’s construction plans. For instance, wetlands that drain into Raccoon Creek in Beaver County will be particularly vulnerable in two locations. The first is in Potter Township, where the Falcon will run along a wooded ridge populated by half a dozen perennial and intermittent streams that lead directly to a wetland of approximately 14 acres in size, seen below. Complicating erosion control further, Shell’s survey data shows that this ridge is susceptible to landslides, shown in the first map below in dotted red.

Landslide areas along Raccoon Creek wetlands and streams

This area is also characterized by the USGS as having a “high hazard” area for soil erosion, as seen in this second image. Shell’s engineers referenced this soil data in selecting their route. The erosion hazard status within 1/4 mile of the Falcon is a layer on our map and can be activated in the full-screen version.

Shell’s permit applications to the PA DEP requires plans be submitted for erosion and sedimentation control of all areas along the Falcon route. Below are the pages that pertain to these high hazard areas.

Example 2: Independence Marsh

The other wetland area of concern along Raccoon Creek is found in Independence Township. Here, the Falcon will go under the Creek using horizontal drilling (highlighted in bright green), a process discussed in the next section. Nevertheless, the workspace needed to execute the crossing is within the designated wetland itself. An additional 15 acres of wetland lie only 300ft east of the crossing but are not accounted for in Shell’s data.

This unidentified wetland is called Independence Marsh, considered the crown jewel of the Independence Conservancy’s watershed stewardship program. Furthermore, the marsh and the property where the HDD will be executed are owned by the Beaver County Conservation District, meaning that the CCD signed an easement with Shell to cross publicly-owned land.

Independence Marsh, unidentified in Shell’s survey data

 

Groundwater Hazards

The Falcon’s HDD locations offer a few disturbing similarities to what caused the Mariner East pipeline spills. Many of Sunoco’s failures were due to inadequately conducted (or absent) geophysical surveys prior to drilling that failed to identify karst limestone formations and shallow groundwater tables, which then led to drilling muds entering nearby streams and groundwater wells.

Karst Limestone

Karst landscapes are known for containing sinkholes, caves, springs, and surface water streams that weave in and out of underground tunnels. Limestone formations are where we are most likely to see karst landscapes along the Falcon’s route.

In fact, more than 25 of the Falcon’s 97 pipeline miles will be laid within karst landscapes, including 9 HDD sites. However, only three of these HDDs sites are identified in Shell’s data as candidates for potential geophysical survey areas. The fact that the geology of the other 10 HDD sites will not be investigated is a concern.

One site where a geophysical survey is planned can be seen in the image below where the Falcon crosses under PA Highway 576. Note that this image shows a “geological formations” layer (with limestone in green). This layer shows the formation types within 1/4 mile of the Falcon and can activated in the full-screen version of our interactive map.

A potential HDD geophysical survey area in karst limestone

Water Tables

We also assessed the Falcon’s HDDs relative to the groundwater depths and nearby private groundwater wells. The USGS maintains information on minimum water table depths at different times of the year. In the image below we see the optional “water table depth” layer activated on the FracTracker map. The groundwater at this HDD site averages 20ft on its western side and only 8ft deep on the eastern side.

Shallow groundwater and private wells near a planned HDD site

Groundwater Wells

Also seen in the above image is the “groundwater wells” layer from the FracTracker map. We found 240 private water wells within 1/4 mile of the Falcon. This data is maintained by the PA Department of Natural Resources as well as by the Ohio Department of Natural Resources. Comparable GIS data for West Virginia were not readily available thus not shown on our map.

While all of these wells should be assessed for their level of risk with pipeline construction, the subset of wells nearest to HDD sites deserve particular attention. In fact, Shell’s data highlights 24 wells that are within 1,000 feet of a proposed HDD site. We’ve isolated the groundwater wells and HDD sites in a standalone map for closer inspection below. The 24 most at-risk wells are circled in blue.

View Map Fullscreen | How FracTracker Maps Work

* * *

Related Articles

By Kirk Jalbert, FracTracker Alliance

The Falcon: Class Locations, Buildings & Recreational Areas

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 guidelinesIn 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.

* * *

Related Articles

The Falcon: High Consequence Areas & Potential Impact Zones

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:

  1. 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
  2. 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.

* * *

Related Articles

By Kirk Jalbert, FracTracker Alliance

The Falcon: Protected Habitats & Species of Concern

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

* * *

Related Articles

Falcon Pipeline: Cumulative Development & Compounded Risks

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 onlineThese 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.

* * *

Related Articles

The Falcon: Methods, Mapping, & Analysis

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.

* * *

Related Articles