Legislative intelligence / 90R
SESSION 2027View project ↗

Health and Safety Code § 382.055: REVIEW AND RENEWAL OF PRECONSTRUCTION PERMIT

1 bill in the 90th Legislature would change this section

Part of Health and Safety Code Chapter 382, 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. 382.055. REVIEW AND RENEWAL OF PRECONSTRUCTION PERMIT. (a) A preconstruction permit issued or renewed by the commission is subject to review to determine whether the authority to operate should be renewed according to the following schedule:

(1) a preconstruction permit issued before December 1, 1991, is subject to review not later than 15 years after the date of issuance;

(2) a preconstruction permit issued on or after December 1, 1991, is subject to review:

(A) every 10 years after the date of issuance; or

(B) on the filing of an application for an amendment to the permit, if:

(i) the applicant is subject to Section 382.056;

(ii) the application is filed with the commission not more than three years before the date the permit is scheduled to expire; and

(iii) the applicant does not object to having the permit subjected to review at that time; and

(3) for cause, a preconstruction permit issued on or after December 1, 1991, for a facility at a nonfederal source may contain a provision requiring the permit to be renewed at a period of between five and 10 years.

(b) The commission by rule shall establish:

(1) a deadline by which the holder of a preconstruction permit must submit an application to renew the permit;

(2) the general requirements for an application for renewal of a preconstruction permit; and

(3) the procedures for reviewing and acting on renewal applications.

(c) Not less than 180 days before the date on which the renewal application is due, the commission shall provide written notice to the permit holder, by registered or certified mail or as provided by Subsection (c-1), that the permit is scheduled for review in accordance with this section. The notice must include a description of the procedure for filing a renewal application and the information to be included in the application.

(c-1) A notice under Subsection (c) may be sent by electronic communication if the commission develops a system that reliably replaces registered or certified mail as a means of verifying receipt of the notice.

(d) In determining whether and under which conditions a preconstruction permit should be renewed, the commission shall consider, at a minimum:

(1) the performance of the owner or operator of the facility according to the method developed by the commission under Section 5.754, Water Code; and

(2) the condition and effectiveness of existing emission control equipment and practices.

(e) The commission shall impose as a condition for renewal of a preconstruction permit only those requirements the commission determines to be economically reasonable and technically practicable considering the age of the facility and the effect of its emissions on the surrounding area. The commission may not impose requirements more stringent than those of the existing permit unless the commission determines that the requirements are necessary to avoid a condition of air pollution or to ensure compliance with otherwise applicable federal or state a

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.