2017 ORS 530.061¹
Surety deposit required of successful purchaser

The State Forester may require the successful purchaser at a forest products sale to provide a surety bond, cash deposit, assignment of surety, irrevocable letters of credit or other securities as determined acceptable by the State Forester for the purpose of securing performance by the purchaser. The required amount of a bond, deposit, assignment, letter of credit or other security may not be more than $500,000. Claims by any person against the bond, deposit, assignment, letter of credit or other security shall be made to the State Forester for determination. If the claim is disputed, the State Forester may request settlement of the claim through compromise or mediation or require that the claim be litigated. Unless there is a claim awaiting determination, the State Forester shall return any unexpended amount from the bond, deposit, assignment, letter of credit or other security no later than 180 days after the earlier of the completion of operations under the sales contract or the termination date in the sales contract. [2014 c.47 §2]

Notes of Decisions

Where county transferred forest land that it could have kept and administered for its own benefit to state “in considera­tion of the pay­ment to the county of the percentage of revenue derived from such lands,” county is entitled to enforce that claim and state cannot avoid its obliga­tion to county by conveying the prop­erty to third per­son. Tillamook Co. v. State Board of Forestry, 302 Or 404, 730 P2d 1214 (1986)

Chapter 530

Law Review Cita­tions

42 EL 1275 (2012)

1 Legislative Counsel Committee, CHAPTER 530—State Forests; Community Forests, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors530.­html (2017) (last ac­cessed Mar. 30, 2018).
 
2 Legislative Counsel Committee, Annotations to the Oregon Revised Stat­utes, Cumulative Supplement - 2017, Chapter 530, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ano530.­html (2017) (last ac­cessed Mar. 30, 2018).
 
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.