My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Vantage to Pomona FEIS Index 34
>
Meetings
>
2018
>
12. December
>
2018-12-18 10:00 AM - Commissioners' Agenda
>
Vantage to Pomona FEIS Index 34
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/13/2018 1:49:29 PM
Creation date
12/13/2018 1:34:21 PM
Metadata
Fields
Template:
Meeting
Date
12/18/2018
Meeting title
Commissioners' Agenda
Location
Commissioners' Auditorium
Address
205 West 5th Room 109 - Ellensburg
Meeting type
Regular
Meeting document type
Supporting documentation
Supplemental fields
Alpha Order
a
Item
Conduct a Closed Record Meeting to consider the Hearing Examiner's Recommendation for the Vantage to Pomona Transmission Line Conditional Use Permit (CU-18-00001)
Order
1
Placement
Board Discussion and Decision
Row ID
50108
Type
Conduct closed record hearing
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
980
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Vantage to Pomona Heights Chapter 4 <br />230 kV Transmission Line Project FEIS Environmental Consequences <br /> <br /> PAGE 4-25 <br />difficult to accurately determine whether this occurrence truly intersect the ROW corridor. The known <br />occurrences of awned halfchaff sedge are within wetlands along the Columbia River. Within the proposed <br />Project, wetlands and the area immediately adjacent to the Columbia River would be avoided. As not all <br />federal and state land were surveyed, additional awned halfchaff sedge occurrences could be present. <br />With the implementation of RDFs described above and the assumption that occurrences would be <br />spanned and avoided, Project construction, operation, and maintenance activities could impact individuals <br />or habitat (moderate impact), but would not contribute a trend toward federal listing. <br />Beaked Spike-Rush <br />Beaked spike-rush is a BLM Strategic and Washington Sensitive species. Beaked spike-rush is known <br />from Vancouver Island to Nova Scotia, Canada south to northern Mexico and the Greater Antilles and in <br />the South American Andes. In Washington, beaked spike-rush is currently known from Grant and Yakima <br />counties. Within the region, beaked spike-rush is known from six populations occupying approximately <br />563 acres. The primary threats to this species are the invasion of habitat by exotic species and loss of <br />habitat through the increased density of woody species (WNHP and BLM 2005). WNHP data indicate <br />that beaked spike-rush intersects Route Segment 3b for 0.7 mile. Impacts from the proposed Project are <br />similar to those described above for Nuttall’s sandwort. With the implementation of RDFs described <br />above and the assumption that potential occurrences would be spanned and avoided, Project construction, <br />operation, and maintenance activities could impact individuals or habitat (moderate impact), but would <br />not contribute a trend toward federal listing. <br />Bristle-flowered Collomia <br />Bristle-flowered collomia is a BLM Strategic and a Washington Sensitive species. This species is <br />distributed from north-central Oregon into central Washington. In Washington, it is known to occur in <br />Kittitas and Yakima counties. Within the region, nine populations occupying 869 acres are known to <br />occur. Primary threats to bristle-flowered collomia are habitat loss through non-native plant invasion, <br />grazing, OHV use and military training (WNHP and BLM 2005). WNHP data indicate that bristle- <br />flowered collomia intersects Route Segment 3b for approximately 0.3 mile; however, special status <br />species locations include large buffers, so it is uncertain whether this occurrence intersects the ROW <br />corridor. With the implementation of RDFs described above and the assumption that any occurrences <br />found during pre-construction surveys would be spanned and avoided, Project construction, operation, <br />and maintenance activities could impact individuals or habitat(moderate impact), but would not contribute <br />toward the need for federal listing. <br />Caespitose Evening-Primrose <br />Caespitose evening-primrose is a BLM Strategic and Washington Sensitive species. This species is <br />known from eastern Oregon eastward, through Montana and Wyoming to the Dakotas. In Washington, it <br />occurs in Kittitas, Yakima, Grant and Benton counties. Within the region, nine populations occupying <br />approximately 1,737 acres are known to occur. This species was identified along a 0.4-mile section of <br />Route Segment 3b during special status plant surveys (Table 4.2-5). The occurrence of caespitose evening <br />primrose was located within a previously documented location and consisted of approximately 75 <br />individuals scattered along the ROW. Approximately 0.3 acre of long-term disturbance and 1.4 acres of <br />short-term disturbance are anticipated to occur in this location, 0.1 percent of known occupied habitat for <br />caespitose evening-primrose in the region. WNHP data indicate additional occurrences of caespitose <br />evening-primrose may occur along Route Segment 3b. These locations include large buffers; therefore, it <br />is difficult to accurately determine whether these occurrences truly intersect the ROW corridor. Direct <br />impacts to this species could occur due to habitat loss from ground disturbance, injury and/or mortality <br />from vehicle and human trampling during construction and maintenance, and increased OHV activity. <br />Indirect impacts could occur through the degradation in habitat quality through the establishment of <br />noxious weeds and invasive plants (e.g., cheatgrass) and increased wildland fire. In addition to RDFs <br />described above, the following RDFs would be also be implemented to reduce direct and indirect impacts
The URL can be used to link to this page
Your browser does not support the video tag.