Legislative intelligence / 90R
SESSION 2027View project ↗

Local Government Code § 397.005: CONSULTATION WITH OR NOTIFICATION TO MILITARY BASE OR DEFENSE FACILITY AUTHORITIES: PROPOSED ORDINANCE, RULE, OR PLAN

No bill in the 90th Legislature changes this section yet

Follow this section in Texas Bill Atlas: a bill filed later that changes it shows up as new.

Part of Local Government Code Chapter 397, 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. 397.005. CONSULTATION WITH OR NOTIFICATION TO MILITARY BASE OR DEFENSE FACILITY AUTHORITIES: PROPOSED ORDINANCE, RULE, OR PLAN. (a) This subsection applies to a defense community other than a defense community described by Subsection (b). If a defense community determines that an ordinance, rule, or plan proposed by the community may impact a military base or defense facility or the military exercise or training activities connected to the base or facility, the defense community shall seek comments and analysis from the base or facility authorities concerning the compatibility of the proposed ordinance, rule, or plan with base operations. The defense community shall consider and analyze the comments and analysis before making a final determination relating to the proposed ordinance, rule, or plan.

(b) This subsection applies only to a defense community that includes a municipality with a population of more than 125,000 located primarily in a county with a population of less than 145,000 and that has not adopted airport zoning regulations under Chapter 241. A defense community that proposes to adopt or amend an ordinance, rule, or plan in an area located within eight miles of the boundary line of a military base or defense facility shall notify the base or facility authorities concerning the compatibility of the proposed ordinance, rule, or plan with base operations.

(c) A defense community that proposes to adopt or amend an ordinance, rule, or plan that would be applicable in a controlled compatible land use area as defined by Section 241.003 and that may impact base operations shall notify the base or facility authorities concerning the compatibility of the proposed ordinance, rule, or plan with base operations. This subsection applies only to a defense community that has not adopted airport zoning regulations under Chapter 241 and that:

(1) is a county with a population of more than 1.5 million that contains a municipality in which at least 70 percent of the county's population resides;

(2) is a county with a population of 170,000 or more that is adjacent to a county described by Subdivision (1);

(3) is located in a county described by Subdivision (1) or (2); or

(4) is or includes a municipality that is located in a county with a population of more than 100,000 and less than 130,000 that borders the Red River.

(d) A defense community described by Subsection (c) may enter into a memorandum of agreement with the military base or defense facility to establish a smaller area in the controlled compatible land use area for which notification under Subsection (c) would be required by the defense community.

(e) After providing notice under Subsection (c), the defense community shall enter into a memorandum of agreement with the military base or defense facility to establish provisions to maintain the compatibility of the proposed ordinance, rule, or plan with base operations.

Added by Acts 2003, 78th Leg., ch. 149, Sec. 9, eff. May 27, 20

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.