Legislative intelligence / 90R
SESSION 2027View project ↗

Transportation Code § 228.109: TRUST AGREEMENT

1 bill in the 90th Legislature would change this section

Part of Transportation Code Chapter 228, 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. 228.109. TRUST AGREEMENT. (a) Bonds issued under this subchapter may be secured by a trust agreement between the commission and a corporate trustee that is a trust company or a bank that has the powers of a trust company.

(b) A trust agreement may pledge or assign the tolls and other revenue to be received but may not convey or mortgage any part of a toll project or system.

(c) A trust agreement may not evidence a pledge of the revenue of a toll project or system except:

(1) to pay the cost of maintaining, repairing, and operating the project or system;

(2) to pay the principal of, interest on, and any redemption premium on the bonds as they become due and payable;

(3) to create and maintain reserves for the purposes described by Subdivisions (1) and (2), as prescribed by Section 228.053; and

(4) as otherwise provided by law.

(d) Notwithstanding Subsection (c), surplus revenue may be used for a transportation or air quality project as authorized by Section 228.006.

(e) A trust agreement may:

(1) set forth the rights and remedies of the bondholders and the trustee;

(2) restrict the individual right of action by bondholders as is customary in trust agreements or trust indentures securing corporate bonds and debentures; and

(3) contain provisions the commission determines reasonable and proper for the security of the bondholders.

(f) The expenses incurred in carrying out a trust agreement may be treated as part of the cost of operating the toll project or system.

Acts 1995, 74th Leg., ch. 165, Sec. 1, eff. Sept. 1, 1995. Amended by Acts 1995, 74th Leg., ch. 872, Sec. 2.08, eff. Sept. 1, 1995; Acts 2003, 78th Leg., ch. 312, Sec. 27, eff. June 18, 2003; Acts 2003, 78th Leg., ch. 1325, Sec. 15.28, eff. June 21, 2003.

Transferred from Transportation Code, Section 361.176 and amended by Acts 2005, 79th Leg., Ch. 281 (H.B. 2702), Sec. 2.42, eff. June 14, 2005.

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.