Legislative intelligence / 90R
SESSION 2027View project ↗

Health and Safety Code § 361.121: LAND APPLICATION OF CERTAIN SLUDGE; PERMIT REQUIRED

1 bill in the 90th Legislature would change this section

Part of Health and Safety Code Chapter 361, with every bill that changes it.

Bills are matched to sections automatically from their text and can be missed, for example when a bill changes a whole chapter at once or renumbers sections. No bill listed here does not mean no bill changes this section.

Current law

Sec. 361.121. LAND APPLICATION OF CERTAIN SLUDGE; PERMIT REQUIRED. (a) In this section:

(1) "Class B sludge" is sewage sludge that meets one of the pathogen reduction requirements of 30 T.A.C. 312.82(b).

(2) "Land application unit" means an area where wastes are applied onto or incorporated into the soil surface for agricultural purposes or for treatment and disposal. The term does not include manure spreading operations.

(3) "Responsible person" means the person with ultimate responsibility for the land application of the Class B sludge at a land application unit. The responsible person is:

(A) the owner of the land application unit if the sludge being land applied was generated outside this state; or

(B) the person who is land applying the sludge if the sludge being land applied was generated in this state.

(b) Except as provided by Subsection (m), a responsible person may not apply Class B sludge on a land application unit unless the responsible person has obtained a permit for that land application unit issued by the commission under this section on or after September 1, 2003.

(c) The notice and hearing provisions of Subchapter M, Chapter 5, Water Code, as added by Chapter 1350, Acts of the 76th Legislature, Regular Session, 1999, apply to an application under this section for a permit, a permit amendment, or a permit renewal. In addition, at the time published notice of intent to obtain a permit is required under Section 5.552, Water Code, an applicant for a permit, permit amendment, or permit renewal under this section must notify by registered or certified mail each owner of land located within one-quarter mile of the proposed land application unit who lives on that land of the intent to obtain the permit, amendment, or renewal. Notice to landowners must include the information required by Section 5.552(c), Water Code, and information regarding the anticipated date of the first application of the sludge to the proposed land application unit. An owner of land located within one-quarter mile of the proposed land application unit who lives on that land is an affected person for purposes of Section 5.115, Water Code.

(d) In each permit, the commission shall prescribe the conditions under which it is issued, including:

(1) the duration of the permit;

(2) the location of the land application unit;

(3) the maximum quantity of Class B sludge that may be applied or disposed of under the permit;

(4) a requirement that the permit holder submit quarterly to the commission a computer-generated report that includes, at a minimum, information regarding:

(A) the source, quality, and quantity of sludge applied to the land application unit;

(B) the location of the land application unit, either in terms of longitude and latitude or by physical address, including the county;

(C) the date of delivery of Class B sludge;

(D) the date of application of Class B sludge;

(E) the cumulative amount of metals applied to the land application unit throug

The section continues: whole chapter.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.