2017 ORS 545.494¹
Unpaid charge as lien on land
  • priority respecting other liens and claims

(1) If any incurred charge remains unpaid beyond the due date of the incurred charge, the secretary of the district may file a notice of claim of lien with the recording officer of the county of each county in which land is situated which received or was entitled to receive the benefit of the water delivery for which the incurred charge has been made. The notice of claim of lien shall be in writing and must contain:

(a) The name of the water user to whom the water was delivered or was deliverable;

(b) A statement of the amount claimed past due; and

(c) A description of the land which received or was entitled to receive the benefit of the water delivery sufficient for identification.

(2) Upon filing of the notice, the incurred charge and costs of filing and removing the notice shall become a lien upon all lands described in the notice in the amounts set forth opposite each tract of land. The lien shall be prior to all encumbrances of whatever kind or nature, whether executed before or after the lien of the irrigation district is created, or whether recorded or registered or not. The lien of the irrigation district upon each tract of land shall be subject to all lawful taxes levied and assessed for state and county purposes by the county in which the land is located. The lien of the irrigation district shall not be subject or inferior to any claim, lien or assessment of any other taxing district, whenever levied, or whether extended on the county tax rolls for collection or not. [Amended by 1991 c.459 §423f; 1995 c.42 §115; 2001 c.476 §5]

1 Legislative Counsel Committee, CHAPTER 545—Irrigation Districts IRRIGATION DIST, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors545.­html (2017) (last ac­cessed Mar. 30, 2018).
 
2 OregonLaws.org contains the con­tents of Volume 21 of the ORS, inserted along­side the per­tin­ent statutes. See the preface to the ORS An­no­ta­tions for more information.
 
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.