Or. Admin. Code § 629-643-0100 - Western Oregon; Standard Practice Vegetation Retention Prescription for Type F and Type SSBT Streams
(1)
The purpose of this rule is to provide the standard practice vegetation
retention prescription for Western Oregon Type F and Type SSBT streams, as
shown in Table 1. The riparian management area distances described in Table 1
are listed for each stream size category, as defined in OAR
629-635-0200. The operator shall
apply the vegetation retention requirements described in this rule. Small
forestland owners, as defined in OAR
629-600-0100, may follow the
alternative vegetation retention option described in OAR
629-643-0141.
[Insert Table 1. Western Oregon Standard Practice Vegetation Retention Riparian Management Area Distances]
(2) Within an operation, the operator shall
not combine or average together the vegetation retention requirements for
stream segments of streams that are in different size categories.
(3) The operator shall retain:
(a) All trees and vegetation within the
distances from the edge of the active channel or the channel migration zone, as
described in Table 1; and
(b) All
trees leaning over the channel.
(4) Within riparian management areas the
operator shall retain all downed wood and snags that are not safety or fire
hazards. The operator shall leave snags felled for safety or fire hazard
reasons where they are felled unless used for stream improvement
projects.
(5) The operator may
fall, move, or harvest vegetation, snags, and trees within the distances
described in Table 1 as allowed in other rules for road construction and
temporary stream crossings (OAR
629-625-0000 through
629-625-0920), yarding corridors
(OAR 629-630-0000 through
629-630-0925), or for stream
improvement (OAR 629-643-0200).
(6) The operator may conduct pre-commercial
thinning and other release activities to maintain the growth and survival of
reforestation or to promote fire resiliency within riparian management areas if
the operator conforms to the following:
(a)
The operator shall ensure these activities contribute to and are consistent
with enhancing the stand's ability to meet the desired future condition;
and
(b) The operator shall submit
to the State Forester a written plan that describes how the operator will meet
these requirements and the goals of the desired future condition.
(7) The operator may count
retained trees within harvest type 2 or harvest type 3 units, pursuant to ORS
527.676, as follows:
(a) For all medium and large Type F and Type
SSBT streams, the operator may count retained trees within the outer 20 feet of
the distances described in Table 1 when those retained trees otherwise meet the
wildlife leave trees requirements within harvest type 2 or harvest type 3
units, pursuant to ORS
527.676.
(b) For all small Type F and Type SSBT
streams, the operator may count retained trees within the distances described
in Table 1 that otherwise meet the wildlife leave trees requirements within
harvest type 2 or harvest type 3 units, pursuant to ORS
527.676.
(8) If the vegetation retention requirements
span a road and a safety hazard presents a risk to road users, the operator may
request that the State Forester approve a plan to remove trees upslope of the
road. The State Forester shall authorize tree removal within the designated
tree retention area only under the following conditions:
(a) Within the tree retention area, the width
of the area where trees may be harvested from the upslope edge of the road
shall be less than 15 feet.
(b) An
equivalent basal area is retained elsewhere within the harvest unit adjacent to
the tree retention area or designated debris flow traversal areas.
Notes
To view attachments referenced in rule text, click here to view rule.
Statutory/Other Authority: ORS 527.710 & Section 2(1), Chapter 33, Oregon Laws 2022
Statutes/Other Implemented: ORS 527.715, 527.765 & Section 2(2), Chapter 33, Oregon Laws 2022
State regulations are updated quarterly; we currently have two versions available. Below is a comparison between our most recent version and the prior quarterly release. More comparison features will be added as we have more versions to compare.
No prior version found.