Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Infrastructure Pipeline topic
No spam. Unsubscribe anytime.
Pasadena council approves franchise for Bluebonnet Pipeline LLC
Summary
On June 17 the Pasadena City Council approved a first-reading ordinance granting Bluebonnet Pipeline LLC a nonexclusive franchise to install and operate a 6‑inch pipeline in the city; the motion passed by voice vote.
The Pasadena City Council on June 17 approved a first-reading ordinance granting Bluebonnet Pipeline LLC a nonexclusive franchise to lay, operate and maintain a 6‑inch pipeline within the city limits.
City Secretary read the ordinance text and council members voted to approve the measure in a single voice vote. Councilman Dowell moved approval and Councilman Guerrero seconded; the motion passed on the record with council members saying “Aye.”
The ordinance (listed in the meeting as Ordinance 2025-124) describes a right, privilege and permit to “lay, replace, construct, repair, maintain, operate, and remove a 6 inch pipeline within the city of Pasadena,” and references plans and specifications filed with the Department of Public Works and the Department of Planning. The ordinance prescribes terms and conditions under which the franchise is granted and provides for acceptance.
The action was taken during the council’s first-reading segment of the agenda and was bundled with two other first-reading items. No public hearing or separate roll-call tally was recorded in the meeting minutes; the clerk recorded the outcome as passed after a voice vote.
The ordinance text and the city’s filing requirements indicate the franchise will be governed by plans on file with Public Works and Planning. Council did not discuss specific work schedules, routing details beyond the language in the ordinance, or permit conditions during the reading.
The council’s approval at first reading allows the city to proceed with the administrative steps that follow a franchise reading; the ordinance reading itself did not include a separate implementation timetable or effective date beyond the usual acceptance language in the text.
