King Arthur Boulevard traffic-calming project

King Arthur Boulevard · Lewisville, Texas

A non-partisan grassroots effort helping Castle Hills residents concerned about the King Arthur traffic-calming project be heard, share evidence, and advocate for change.

Close view of a damaged concrete traffic-calming barrier on King Arthur Boulevard
Get involved

The question behind the project

No speed-related crashes. No data on complainants. Why were permanent barriers the answer?

The official record documents speeding. It does not document a crash crisis or state how many residents whose concerns started the project.

01 · What the City says

Speeding and stop-sign concerns

Lewisville staff says it initiated the project due to documented speeding. The November 2024 presentation cited a history of speeding concerns and stop-sign running, a 25 mph limit, 85th-percentile speeds of 31–36 mph, and roughly 4,000 vehicles per day.

02 · What the same deck says

Zero speed-related crashes

The same presentation reported zero speed-related crashes from 2020 through 2024. It said signage and targeted enforcement had already been used after annexation and noted that a full $25M-plus rebuild was not included in the bond program because of cost and priority.

03 · What is still missing

How many residents officially complained?

The presentation does not state how many residents raised the original speeding concerns, how many complaints the City received, when they were submitted, or any signed neighborhood petition asking for the installed design. A later memo documents resident requests for eight more crosswalks and 24 new or reconfigured ADA ramps, but still does not name those residents.

3.5 miLength of King Arthur Boulevard reviewed by the City
25 mphPosted speed limit on the studied corridor
31–36 mphObserved 85th-percentile speeds
≈4,000Vehicles using the corridor each day
$675KCity's documented FY2023-24 project budget
0Reported speed-related crashes from 2020–24
?

Speeding was documented; a crash pattern was not. Why were permanent barriers judged safer and more proportionate than enforcement or less intrusive alternatives? How can concerned residents ensure that the traffic-calming project will not be expanded without clear notice, public input, extensive blueprints, and documented justification?

Audit the archived presentation

More questions residents are asking

These concise questions synthesize recurring themes in public Facebook and petition comments. Expand a theme to review them and follow each source.

Safety and performance4 questions

What do before-and-after crash, tire-damage and lane-departure records show? Source

How many accidents have there been to date? Source

Did the installed configuration receive a field safety review, and will that review be published? Source

How was nighttime visibility evaluated for visitors and drivers unfamiliar with the street? Source

Design and alternatives3 questions

Could the bike lanes remain without concrete barriers narrowing the vehicle lanes? Source

Were painted buffers, flexible posts, targeted enforcement or other less rigid treatments compared? Source

How were turning movements at Old Denton Road and neighborhood intersections tested? Source

Public process and accountability9 questions

Who requested the project, how many complaints were received and when were they submitted? Source

What changed between the November 2024 public presentation and the final design? Source

Why was the slide presentation given to those that attended different than the end product? Source

How can residents ensure that what is presented is what gets built? Source

Where are the plans to continue the calming project between Josey and King Arthur? Source

Can the City clarify whether there is a plan to extend traffic calming to Josey Lane? Source

Apart from the King Arthur traffic-calming project, are there any separate plans to extend bike paths or modify traffic lanes along Lady of the Lake Boulevard or any other roads within Castle Hills? Source

If no extension is currently planned, what formal notice, public input, detailed plans and Council action would be required before that could change? Source

What measurable criteria will determine whether the City modifies or removes an installed feature? Source

Cost and maintenance3 questions

How much has actually been invoiced and paid, rather than budgeted or authorized? Source

What will damaged barriers, signs and pavement repairs cost over the useful life of the project? Source

Will the City publish change orders, final invoices and project closeout records in one place? Source

New official-record findings

What the records add

Qualified findings from City, TxDOT and regional planning records. Expand an item for the data, limits and primary evidence.

Official presentation

November 2024 project presentation

City deck covering the project rationale, traffic data, crash history, concept design and budget shown at the time.

Lewisville staff says it initiated the project due to documented speeding. The November 2024 presentation cited a history of speeding concerns and stop-sign running, a 25 mph limit, 85th-percentile speeds of 31–36 mph, and roughly 4,000 vehicles per day.

The same presentation reported zero speed-related crashes from 2020 through 2024. It said signage and targeted enforcement had already been used after annexation and noted that a full $25M-plus rebuild was not included in the bond program because of cost and priority.

The presentation does not state how many residents raised the original speeding concerns, how many complaints the City received, when they were submitted, or any signed neighborhood petition asking for the installed design. A later memo documents resident requests for eight more crosswalks and 24 new or reconfigured ADA ramps, but still does not name those residents.

Open the official presentation deck
Traffic baseline

October 2024 traffic-counter baseline

City-provided traffic studies counted vehicles and speeds in both directions at three King Arthur locations on October 30, 2024.

City-provided traffic observations · October 30, 2024
LocationDirectionVehiclesAverage85th percentileMaximum
Between Polser and MorganIncoming1,33927.93 mph32 mph41 mph
Between Polser and MorganOutgoing1,39429.12 mph33 mph47 mph
Near Lake AvalonIncoming1,39628.6 mph33 mph44 mph
Near Lake AvalonOutgoing1,35528.9 mph33 mph41 mph
Near Lady CarolIncoming1,29128.32 mph32 mph51 mph
Near Lady CarolOutgoing1,40630.1 mph35 mph51 mph

These are one-day observations for each location and direction—not annual averages or proof of long-term conditions. “Maximum” is the highest recorded speed in that sample, not the typical speed.

City traffic-count summary pages
Crash history

Carefully bounded 2016–2026 crash query

A City-provided TxDOT CRIS aggregate query covering January 1, 2016 through June 25, 2026 reports two reportable crashes in the queried King Arthur segment: one speed-related crash, zero fatal crashes, and zero suspected-serious-injury crashes.

The query is bounded to Route ID 1154709, DFO 0.01–1.35. It is not a complete record of every curb strike, tire-damage event, near miss, private-property incident, or non-reportable crash. Its longer 2016–2026 range does not contradict the City's separate statement of zero speed-related crashes during 2020–2024.

TxDOT CRIS aggregate query
Accountability benchmark

What the City says it will measure

The City says evaluation should follow an adjustment period of 6–9 months.

The City says drivers generally need 6–9 months to adapt to the new configuration, after which engineers can assess long-term effectiveness through follow-up speed studies.

Concerned residents are asking the City to publish the pre-installation baseline, follow-up methodology, study dates, raw or summarized results, and any resulting design decision.

This is the City's stated evaluation approach—not a guaranteed outcome or proof that the installation is effective.

Official King Arthur project page and FAQ
Design progression

From public concept to construction package

Compare the 2024 discussion concept, supplied 95% file and 100% package.

Nov. 7, 2024

Public presentation

A discussion presentation—not a formal plan set—showed lane narrowing, bike lanes, parking, crosswalks, signage, and bump-outs labeled “Design TBD.”

2024 public presentation · p. 10
July 18, 2025

95% plan set

The supplied 76-page interim set translated the concept into location-specific roadway sheets 29–36. Its roadway title blocks say “100% Submittal” while also stating it was for interim review and not for construction, bidding, or permits.

95% file · reviewed sheets 1–2, 7, 29–38
Aug.–Oct. 2025

100% plan set

The 77-page package kept the same 1.45-mile limits and eight roadway-plan sheets, added a project-specific curb-bump-out detail, identified 158 parking spaces, changed the island material schedule from colored textured concrete to landscape/concrete pavers, and reduced scheduled bike-lane buffers from 242 to 167.

100% package · sheets 1, 7, 29, 34 and 38

The public presentation is a discussion concept, not a formal 60% plan set. The comparison documents visible scope, schedule, callout, quantity and detail changes; it does not establish motives, field conditions, approval history, final cost, or whether every drafting change became a construction change.

Scope and context

Current project vs. regional planning

The City's current King Arthur project page defines the corridor from Old Denton Road to Lady of the Lake Boulevard. Separately, NCTCOG's regional bikeway data marks a King Arthur segment as “Planned.”

A regional planned-network designation is not a City construction award, project funding, Council approval, construction schedule, or evidence that the current project extends to Josey Lane. It is appropriate context for questions about future planning—not proof of a committed extension.

Cost, Maintenance, and Exposure

Cost to the Taxpayer

The three summaries stay visible; supporting records and calculations are collapsed until you need them.

Initial Cost Estimate

Initial costs could reach $900k

Known design and construction authorizations total $529,967.17; final invoices, approved change orders, payments and closeout are TBD.

Initial cost, funding and solicitation detailsBudget, authorizations, planning estimate and bid record

Funding-source explanation

$925,000 identified

A City-provided project financial snapshot identifies $675,000 from the General Fund and a $250,000 transfer from the Castle Hills Public Improvement District fund, for $925,000 in funding identified for the project.

Funding identified is not the same as final spending, invoices paid, or project closeout. The extract also reports balances as of its snapshot date.

City funding-source extract
General Fund
$675,000
Castle Hills PID fund
$250,000
Project budget, bid, adjustments, authorizations and potential planning total
StageAmountWhat it meansSources
Original budget$675,000Documented FY2023–24 project budgetBudget—not spending. A later November 2024 presentation showed $650,000.
Base bid$420,902.07Quick Set Construction base bidLowest responsive, responsible bid opened January 21, 2026.
Construction adjustment+$21,045.10Five-percent construction contingencyAuthorized allowance—not evidence it was spent.
Construction authorization$441,947.17Base bid plus contingency$420,902.07 bid + $21,045.10 contingency.
Original design$49,620Original LJA engineering authorizationDesign services authorized before the later amendment.
Design adjustment+$38,400Additional survey and ADA-ramp designJune 2025 engineering amendment.
Design authorization$88,020Total engineering authorization$49,620 original + $38,400 amendment.
Known authorization$529,967.17Design and construction authorizations combined$88,020 design + $441,947.17 construction; not proof all funds were spent.
Potential total$938,020Pre-bid planning comparison$850,000 revised pre-bid construction estimate + $88,020 design authorization; not a current contract or paid cost.

Solicitation 26-33-C

Two sealed bids. Quick Set Construction was the low bidder.

Competitive sealed bidding. Lewisville received two bids and staff recommended the lowest responsive, responsible bidder under Texas Local Government Code §252.043.

Approved as Consent Agenda item 6 on April 6, 2026; the Legistar record does not show an item-level roll-call vote.

BidderBase bid
Quick Set Construction, LLCLowest responsive, responsible bidder$420,902.07
Gibson & Associates, Inc.$535,685.13
Council authorization
Includes $21,045.10 contingency
$441,947.17

Maintenance

Potential ongoing maintenance: $20,865–$25,740 per year

Modeled range for separate repair campaigns using original bid unit prices—not a City forecast.

Five-year maintenance scenarios

What repeated buffer damage could add

Quick Set's bid priced 167 bike-lane buffers at $325 each, mobilization at $20,000, and stationary traffic control at $215 per day. The scenarios below assume two, eight, or seventeen buffer replacements per year (about 1%, 5%, or 10%), one traffic-control day, and either no new mobilization or a separate mobilization comparable to the original bid.

Light

2 buffers/year

Direct units / year
$650
Separate repair campaign / year
$20,865
Moderate

8 buffers/year

Direct units / year
$2,600
Separate repair campaign / year
$22,815
Heavy

17 buffers/year

Direct units / year
$5,525
Separate repair campaign / year
$25,740
One bike-lane buffer$3251 × $325
Ten bike-lane buffers$3,25010 × $325
All 167 bike-lane buffers$54,275167 × $325
All scheduled 4-inch striping$44,403.76$28,698.17 white + $15,705.59 yellow
All scheduled 24-inch white striping$12,045.701,630 LF × $7.39
One ADA curb ramp$2,9401 × $2,940

These are potential scenarios, not a City forecast or contractor quote. They assume the authorized capital ceiling is fully used, repeat 2026 unit prices without inflation, and exclude restriping, signs, curb/sidewalk work, pavement repair, City labor, engineering, and legal costs. City crews or bundling repairs could avoid separate mobilization; emergency work could cost more.

Exposure

Potential taxpayer liability exposure

Roadway hazards or inaccessible pedestrian features could expose the City—and therefore taxpayers—to liability; no project-specific amount is known.

Unpriced contingent exposure

Potential Legal Exposure

These authorities support two specific concerns raised here: a municipality can face roadway-safety exposure after repeated notice of a dangerous traffic condition, and ADA Title II can reach inaccessible sidewalks, curb ramps, and other pedestrian-right-of-way barriers. Turturro is the closest traffic-safety analogue; Frame is especially relevant because the en banc Fifth Circuit governs federal ADA cases in Texas; Barden documents that sidewalk-barrier litigation can require a long-term municipal remediation program.

The Texas Tort Claims Act caps municipal liability under the Act at $250,000 per person and $500,000 per occurrence for bodily injury or death, and $100,000 per occurrence for property damage. Those are statutory ceilings—not forecasts, automatic payouts, or proof immunity is waived.

General civic information only—not legal advice. Statutory caps do not determine whether a particular claim is permitted or succeeds.

From annexation to installation

How we got here

01

Castle Hills annexation—and why Place 6 exists

Full-purpose annexation took effect at 12:01 a.m. for approximately 2,568.38 acres encompassing Castle Hills freshwater-supply districts 1-A through 1-H. A voter-approved Charter amendment expanded Council from five to six places when an annexation increased Lewisville's land mass by at least 8%. Place 6 requires residency in its corresponding district but is elected at large citywide.

02

City Council Place 6 Filled

Patrick Kelly received 2,114 votes (72.85%) to Tom Cottrell's 788 in the first Place 6 contest after annexation. The electorate was citywide, not Castle Hills-only. Kelly, a resident of Castle Hills, later wrote, “I voted for the KA project. I support the KA project.” His December 2022 post says he asked the City for enforcement and described a City review of King Arthur, making him a documented early Council advocate for traffic calming; the reviewed City records do not identify a formal project sponsor.

03

Calming Project Planned

The official FY2023-24 budget was $675,000. Later City records show an $850,000 construction estimate and $88,020 in authorized engineering, producing a $938,020 planning estimate—not a final paid cost.

04

LJA engineering agreement executed

The City executed the original $49,620 LJA agreement before the November public meeting. Its scope called for data collection, conceptual, 30%, 60%, 90% and final design, plus public outreach and coordination. The agreement confirms LJA was under contract; it does not prove a 100% plan set was complete in July or that no earlier traffic data existed.

Signed LJA engineering agreement
05

City presents a draft to residents

At LISD TECC East, Lewisville described speeding and stop-sign concerns, showed traffic data, proposed lane narrowing, parking/bike-lane changes and concrete features, and requested comments. The deck does not name the original complainants or report a neighborhood vote.

Official city presentation
06

Place 6 incumbent re-elected unopposed

Patrick Kelly—an ardent supporter of the King Arthur traffic-calming project in his own public statements—was re-elected unopposed with 1,640 votes in the citywide Place 6 election.

Official election results · Kelly public statement
07

Calming Project design expands

The City authorized a $38,400 LJA amendment for added ADA ramps and survey/design work. Staff recorded the construction estimate moving from $620,000 to $850,000 while design authorization reached $88,020.

Lewisville matter 25-4101
08

Two construction bids opened

Quick Set bid $420,902.07 and Gibson & Associates bid $535,685.13. Quick Set was $114,783.06 lower and staff identified it as the lowest responsive, responsible bidder.

Official bid tabulation
09

Council authorizes construction

Council approved a $441,947.17 authorization to Quick Set, including a $21,045.10 contingency, as Consent Agenda item 6. The public Legistar record does not expose an item-level roll-call vote.

Lewisville matter 26-4500
10

Significant community concerns are raised

Community members have reported many incidents and concerns involving vehicles, cyclists, damaged separators, opposing-lane movements and other safety issues since installation.

Crowd-sourced community reports
11

Residents take concerns to the City Council

Five residents addressed the King Arthur project during Visitors Forum. They described navigation, vehicle-damage and safety concerns, asked for a prompt safety review, and requested that Council reconsider or modify the concrete barriers. The official transcript does not preserve the first grouped speaker's full name clearly, so that link is labeled rather than guessed.

12

Residents speak about King Arthur at City Council

Nine residents addressed King Arthur during Visitors Forum. Eight speakers raised concerns about concrete features, roadway geometry, maintenance, cost, crashes or injuries and asked the City to reconsider or modify the installation. One speaker defended the project and said it was reducing speeds and reckless driving. The Mayor noted the August 19 Special Called Council Meeting and said Council would continue receiving information.

13

Upcoming: Special Called Council Meeting

The City of Lewisville scheduled a Special Called Council Meeting for August 19 at 6:00 p.m. in City Hall Council Chambers to discuss the King Arthur Boulevard traffic calming project.

City of Lewisville staff announcement

Reported issues

A timeline of community-reported problems

Open the Castle Hills Community discussion

30 sourced incident, near-miss, hazard, and supporting-context entries are shown below. Resident accounts are identified as reports rather than official findings.

Resident report

Odyssey reportedly lost both tires after striking the King Arthur median

First-hand resident report
Redacted community photo of a gray minivan stopped beside a King Arthur traffic-calming median
Permissioned community exhibit. Faces and the license-plate area were irreversibly blurred before publication.

A first-hand community report says a gray Honda Odyssey struck the traffic-calming median and lost both tires.

Resident report

Young driver reportedly struck the King Arthur barriers

Witness report
Redacted community roadway photo showing traffic-calming barriers and vehicles on King Arthur
Permissioned community exhibit. The visible plate area was irreversibly blurred; no person is identified.

A witness report says a young driver struck the traffic-calming barriers and lost one or more tires, with possible additional vehicle damage.

Resident report

Accord observed stopped near the guardrail with an apparent flat tire

Witness photo
Redacted community photo of a silver sedan stopped beside the King Arthur guardrail
Permissioned community exhibit. The occupant area and incidental identifying material were irreversibly blurred.

A witness photo shows a silver Honda Accord stopped along King Arthur near the guardrail with its trunk open and an apparent flat or blown tire.

Resident report

Audi rim and tire damage reported after curb contact

Second-hand resident report with permissioned photo
Close-up permissioned community photo of damage to an Audi tire and rim
Permissioned community exhibit. It contains no visible face, plate, name, or address.

A second-hand community report says an Audi struck a King Arthur curb and sustained rim and tire damage.

Resident report

Red car reportedly lost a tire after striking the Lady De Vance turn barrier

First-hand resident report
Redacted community photo of a red car during a roadside tire change
Permissioned community exhibit. The person was irreversibly blurred before publication.

A first-hand report says a driver turning right from Lady De Vance Lane onto King Arthur did not see the new barrier, struck it, and lost a tire. The same report says another driver encountered the barrier shortly afterward.

Resident report

Two tires reportedly ruined at King Arthur and King Mark Drive

First-hand resident report; date not established

A first-hand account says a 2022 Lincoln Corsair struck a curb extending into the lane, ruining two tires and requiring a flatbed tow. The date was not supplied in the underlying incident table.

Resident report

Lexus rim and tire damage reported after curb contact

First-hand resident report; date not established

A first-hand report says a Lexus contacted a King Arthur curb during an early-morning commute, bending or breaking the rim and requiring a new tire. The account says the driver swerved slightly to avoid a possible collision.

Resident report

Driver reported striking a King Arthur project barrier

First-hand resident report

A first-hand community submission says the driver struck a project barrier on King Arthur.

Resident report

Car reportedly disabled after striking a curb-out at Enchanted Hills

First-hand resident report

A first-hand report says a car struck a curb-out at King Arthur and Enchanted Hills, damaging front and passenger-side tires and leaving the vehicle undrivable.

Resident report

Driver claimed about $1,600 in damage after barrier contact

Petition-based resident claim
Permissioned close-up community photo of a damaged vehicle tire
Permissioned community exhibit. It contains no visible face, plate, name, or address.

A petition-based account says a driver hit a King Arthur barrier and could not exit the bike lane safely, with approximately $1,600 in claimed vehicle damage.

Resident report

Range Rover reportedly required pickup after barrier contact

Witness report

A witness entry says a black Range Rover struck a concrete barrier at King Arthur and Enchanted Hills and required pickup because of extensive front-passenger-wheel damage.

Resident report

RAV4 reportedly required flatbed pickup after barrier contact

Witness report

A witness entry says a white Toyota RAV4 struck a King Arthur concrete barrier and required flatbed pickup for front-passenger-wheel damage.

Resident report

Tire replacement reported after barrier contact at King Arthur and King Mark

First-hand resident report

A first-hand community entry says a driver struck a concrete barrier and replaced a tire.

Resident report

Front passenger tire reportedly failed after barrier contact

First-hand resident report

A first-hand community entry says a driver struck a King Arthur concrete barrier and sustained a flat front-passenger tire.

Resident report

Yukon rim damage reported at both Enchanted Hills exits

First-hand resident report

A first-hand account says a black GMC Yukon contacted concrete bump-outs at both King Arthur and Enchanted Hills exits and sustained a scratched rear rim.

Resident report

Infiniti SUV flat tire reported near Morgan LeFay and Old Denton

Witness report

A witness entry says a white Infiniti SUV struck a concrete barrier while westbound near Morgan LeFay and Old Denton and sustained a flat tire.

Resident report

Rear tire and rim damage reported at the Enchanted Hills entrance

First-hand resident report

A first-hand entry says a vehicle struck a concrete bump-out at King Arthur and the Enchanted Hills entrance, tearing the rear passenger tire and scratching the rim.

Resident report

Civic reportedly immobilized after striking an Enchanted Hills bump-out

Witness report

A witness entry says a black Honda Civic struck a concrete bump-out near the King Arthur and Enchanted Hills exit, sustained undercarriage damage, and became immobile. Police were reportedly called.

Near-miss / hazard

Commercial vehicle reportedly confused by the Old Denton lane setup

Witness hazard report
Redacted community photo of vehicles navigating the lane setup at the neighborhood exit onto Old Denton
Permissioned community exhibit. All visible plate areas were irreversibly blurred before publication.

A witness report says a commercial vehicle traveled alongside a Jeep in the right-turn lane while leaving the neighborhood, creating a conflict before vehicles entered Old Denton traffic. No collision or damage was reported.

Resident report

Range Rover tire and rim damage reported near Lady of the Lake

Resident account

A public resident account says a driver turning right from King Arthur toward Lady of the Lake did not see a concrete roadway feature and struck it. The account describes tire and rim damage to a black Range Rover.

Resident report

Concrete block reportedly found in the travel lane

Near-miss or hazard report

A public comment says a resident's husband encountered a concrete block sitting directly in a King Arthur travel lane. No collision or vehicle damage was reported.

Resident report

Small SUV reportedly struck a block turning from Queen Peggy onto King Arthur

Witness account

A public witness comment describes a small SUV striking the first concrete block while turning right from Queen Peggy onto King Arthur toward the shops. The witness noted that the block sits close to the corner.

Resident report

Company truck reportedly struck an island with both passenger-side tires

Witness account
Permissioned community close-up showing two reportedly damaged company-truck tires
Permissioned community exhibit. Incidental interface text was irreversibly blurred; no face, plate, name, or address is shown.
“I just witnessed a company truck get damaged due to both front and rear tires hitting the island bump on the road.”

A public community post says the author witnessed a company truck's front and rear passenger-side tires contact a roadway island.

Resident report

Unspecified accident seen en route to a neighborhood pool party

Resident observation
“Today, we saw an accident on the way to a neighborhood pool party.”

A resident wrote that the household saw an accident while traveling to a neighborhood pool party. The post supplied no location, vehicles, injuries, police report, or causal detail for this first event.

Resident report

Visitor's tire reportedly failed at King Arthur and Enchanted Hill

Resident account with a photo
“Another driver at KA and Enchanted Hill … popped her tire after visiting a friend's house.”

In the same public comment, the author described encountering a driver at King Arthur and Enchanted Hill whose tire had popped after visiting a friend.

Resident report

Driver reportedly wrecked at King Arthur and Morgan LeFay

Resident account with a photo
“Lady at KA and Morgan LeFay tonight at 4:26 pm. She said she had driven this route so many times before, but has never wrecked.”

A follow-up comment identified a driver at King Arthur and Morgan LeFay and said the driver reported never having wrecked on the familiar route before.

Resident report

Two separate incidents reportedly seen within a few hours

Aggregate eyewitness claim; the two underlying events are not individually documented
“A few days ago I saw 2 separate incidents within a few hours.”

A commenter reported seeing two separate incidents within a few hours but supplied no date, location, vehicle details, photographs, or report numbers. They cannot responsibly be broken into two distinct timeline records without more evidence.

Resident report

Damaged separators counted by a resident

Resident count
Community close-up photo of a chipped concrete bike-lane separator with loose concrete fragments
Community photo showing visible chipping and loose concrete at one separator.
“52 of 161 bump outs already struck and damaged.”

A community post supplied a precise damage count. The photograph shows one visibly chipped concrete separator with loose fragments.

Resident report

Cyclist fall reported near Enchanted Hill

Resident account
“When I walked up he was on the ground for some time with dirt on his shoulder.”

A resident described finding a cyclist down near the Enchanted Hill bump-out.

Resident report

Drivers reportedly move into opposing lanes

Repeated resident observation
Redacted community context photo of vehicles navigating around a brick traffic-calming island
Permissioned context photo. Vehicle identifiers were irreversibly blurred.
“Cars swerving into oncoming lanes.”

Residents described drivers moving around installed features rather than following the intended channel. Public Council speakers also raised navigation and clearance concerns.

Public comments, organized by theme

Quotes from concerned voters

Anonymous excerpts from public Facebook posts and Change.org petition comments. These are personal accounts and opinions—not independently verified incident findings or proof that a commenter is a registered voter. Expand a theme to read the quotes; every excerpt links to its public source.

Safety and visibility9 public comments

This needs to be fixed! I almost got hit turning right on Old Denton because a car got into the bike lane to turn!

Anonymous · Change.org petition comment

Who thought this was a good idea? And how on earth did this pass a safety inspection?

Anonymous · Change.org petition comment

I was almost killed losing control of my car after hitting these concrete barriers.

Anonymous · Change.org petition comment

I’m actually concerned what will happen on Halloween in the dark with all the traffic and new to the area drivers.

Anonymous · Public Facebook comment

Cars swerving into oncoming lanes. Hit one at speed… you lose control.

Anonymous · Public Facebook post

I live on KA and have endured damage to my property—a car hit my tree… flames caused damage to my house and yard.

Anonymous · Public Facebook comment

I worried about children playing in our driveway because so many cars would speed by carelessly.

Anonymous · Public Facebook comment

They are painted white and low to the ground. No one is expecting them.

Anonymous · Public Facebook comment

I’m glad they did something as it was 100% necessary.

Anonymous · Public Facebook comment
Vehicle damage and close calls7 public comments

My tire slashed on that barrier and would have caused a terrible accident.

Anonymous · Change.org petition comment

I just hit one of those concrete blocks. It took out two of my tires.

Anonymous · Public Facebook comment

There is a massive truck that’s stuck on Lady of the Lake and King Arthur.

Anonymous · Public Facebook comment

Today, we saw an accident on the way to a neighborhood pool party.

Anonymous · Public Facebook comment

On way home we came across another driver at KA and Enchanted Hill who popped her tire after visiting a friends house.

Anonymous · Public Facebook comment

She said she will never visit this friend again because of this thousand dollar mistake.

Anonymous · Public Facebook comment

She had driven this route so many times before, but has never wrecked.

Anonymous · Public Facebook reply
Design and neighborhood impact7 public comments

I feel the final outcome of the King Arthur traffic calming project significantly over-corrected in its effort to bring down the average auto speed.

Anonymous · Change.org petition comment

The bike lanes are great, leave them without the barriers. Lanes are just too tight in some areas, reflectors not effective.

Anonymous · Change.org petition comment

The concrete barriers are an eye sore and definitely take away from the clean and classic look of what Castle Hills is suppose to reflect.

Anonymous · Change.org petition comment

It is just unnecessary, causes more harm then good.

Anonymous · Change.org petition comment

Those bumps are a serious hazard and need to be removed ASAP.

Anonymous · Public Facebook comment

There are houses facing the street on the section of KA heading to Josey, so I’m not sure how they are going to do that.

Anonymous · Public Facebook comment

No slide indicated that a physical barrier would be placed as protection for the bikers.

Anonymous · Public Facebook reply
Accountability and next steps6 public comments

Surely data will support that more harm than good has been done. It’s ok to make mistakes, but now it’s time to come to the table to find a better solution.

Anonymous · Change.org petition comment

Visitors to our neighborhood wouldn’t know what to do and might get the city’s attention quicker.

Anonymous · Public Facebook comment

A few days ago I saw 2 separate incidents within a few hours.

Anonymous · Public Facebook comment

We need signs indicating if someone damages their vehicle to call the Lewisville non-emergency line. Visitors wouldn’t know what to do.

Anonymous · Public Facebook comment

True waste of money. But to spend money to fix it again would be crazy too.

Anonymous · Public Facebook comment

The additional cost does have an impact to residents and should be communicated as part of transparency.

Anonymous · Public Facebook reply

Public Statements from the City Council

Straight from the City Council

The complete project-related Facebook record located in the reviewed public material, presented chronologically with source context. Open any statement to read it.

Early enforcement request and review of King Arthur
“A few months ago I was contacted by residents with concerns over people disregarding stop signs and speeding on King Arthur Blvd. I asked the city for an enhanced police presence and they responded immediately. They have also been providing me with a monthly review so I can monitor its progress. … The City is also conducting a review of King Arthur as a whole with the intent to find ways to slow traffic and ensure drivers obey the stop signs. Traffic calming measures take many forms; however, it's only fair to note that any structural change will be an expensive and difficult undertaking. I will work with residents to find the proper funding should the need present itself.”

This is the earliest project-related statement located in the captured Facebook record. Kelly described resident complaints, increased enforcement, a City review, and possible structural traffic-calming measures.

Find the Dec. 2022 Facebook post
Announcement of the neighborhood traffic-calming meeting
“We have been in Castle Hills for 25 years. And for 25 years there have been concerns about the traffic on King Arthur. The long timers here may even recall the nickname ‘Cooper's Speedway’ … City staff has been looking at options and are ready to present traffic calming ideas to the neighborhood. To that end, there will be a community meeting on Thursday, Nov 7th 6:30PM–8:00PM at LISD TECC East … to talk about traffic calming options on King Arthur.”

Kelly announced the November 2024 public meeting and characterized King Arthur traffic concerns as decades old. The entry uses the meeting date because the Facebook capture did not expose a reliable post date.

Find the 2024 public-meeting post
Construction-award agenda notice
“For as long as we’ve been residents of Castle Hills, there’s been concern over speeding and safe, multi-model [sic] transit along King Arthur. … The City has an excellent plan to address some of these issues. … Part of Monday’s consent agenda is the approval of a bid award to start the traffic calming project. The construction period is just over 3 months.”

Kelly previewed the consent-agenda construction award and described the project as responding to long-running speeding and multimodal-safety concerns. The official award occurred April 6, 2026.

Find the construction-award Facebook post
Description of the coming design
“Traffic calming work on King Arthur begins this summer, funded through a bond package approved before annexation. The project includes slimmer roads, raised crosswalks, bump-outs, and buffered bike lanes. The City has worked with HOAs, nearby schools, and residents to shape the design.”

In this pre-construction post, Kelly summarized the physical design and said the City had worked with HOAs, schools, and residents. The available capture did not expose an unambiguous calendar date, so the entry does not invent one.

Find the pre-construction Facebook post
Enforcement data and traffic calming as behavior modification
“This graphic shows there have been 317 traffic stops since March 1st in the beats that comprise CH … That's about 4 stops per day. … I’d assert the problem is not a lack of enforcement, but instead enforcement does not have the efficacy we would like it to have. If the ends are better drivers, and if punitive efforts such as tickets do not produce the results we would like, we need [to] think about other behavior modification tools such as the traffic calming project on King Arthur. … Combined tools such as enforcement and traffic calming together will help.”

Kelly argued that enforcement alone was not producing the desired behavior and presented the King Arthur project as a complementary tool. The post described the data as covering the prior 75 days, placing it in mid-May; the capture did not expose an exact date.

Find the enforcement-data Facebook post
Response to claims that residents were not told
“I’ve seen several posts/comments surrounding the traffic calming project on King Arthur … ‘nobody told us about this’. I … checked on communication efforts. … 1. Direct communication to all HOAs and Property Manager (over a year ago) and schools and LISD. … 2. HOA meetings … 3. Social media … 4. Newsletter … 5. Direct mail … 6. Public meeting with signs on King Arthur … 7. Email … We received emails in response to these efforts and dozens of people attended the public meeting. … Having this context, I’d ask that in fairness, the people posting ‘no one told us’ go back and edit or remove that statement. … Now—we’ve gotten past the shouting—it’s a good time to see if there are tweaks or solutions to some of the concerns while maintaining the integrity of the project.”

Kelly listed seven asserted communication channels, rejected the claim that there had been no notice, and said the City could consider tweaks while preserving the project. This is retained as his public account; it is not treated as independent proof that every resident received notice.

Find the June 24 Facebook post
Personal response after driving the installed work
“OK—I’ve been out of town for the past week and wanted to see the progress on King Arthur personally before I poke my head up. … I can’t always give the answer you want, but I’m here for both of those conversations. … What I’m actually most concerned about [is] the theme of ‘nobody told us’. … Here are some of the ways both the city in general and me specifically attempted to convey this change was coming … 1. City posting to web site 2. Agenda items in open meetings 3. Feedback meeting at Independence 4. Various bond meetings … 5. Posts to this FB group 6. Posts to my personal councilman page 7. Article in Castle Hills magazine. … What other methods could be employed to keep residents informed of proposals and projects that could affect the fabric of communities in our city?”

This separate late-June post followed Kelly's own drive through the work. He again defended prior outreach while asking residents to suggest additional communication methods. The capture did not expose an exact date, so it is not assigned one.

Find the late-June communication post
Explicit statement of his vote and support
“People deserve to know where their elected officials sit. I voted for the KA project. I support the KA project. … I absolutely recognize and am disappointed when government doesn't communicate well. That said, I get frustrated with the sentiment of ‘no one told us’ when I repeatedly posted on social media, HOA presentations were given, postcards mailed, signs posted, and newsletters provided. … I continue to assert that conceptual designs are just that—conceptual. I agree that concrete was not on the concepts—nor were other items. Sometimes things present as a project unfolds and adjustments are needed. … I worked with the HOA to delay issuing violations for parking over sidewalks/blocked sidewalks until the project completed. I've walked the project with staff, addressed several resident concerns, and I drive it almost daily. … The first step is always to check with residents directly impacted. … This project has been several years in the making—not knowing anything about it until the project was underway says as much about the reader as the author. It's not a ‘nobody told me’ rather ‘I wasn't interested or looking for information until it impacted me.’ … Lastly—I was trying to show empathy to those with concerns by stating I was open to listening to their concerns and solutioning together. That should not have been confused with my lack of support for the project.”

This is the statement the prior page omitted. Kelly expressly said he voted for and supported the King Arthur project, defended the communication record and design changes, and said openness to adjustments should not be read as opposition.

Find the July 1 Facebook statement
Response to a request for data and incident documentation
“Thank you for a dispassionate and data driven ask regarding a pretty emotional topic. It’s very, very much appreciated.”

Kelly posted this reply in the public thread where residents were collecting King Arthur incident information. It is included because it addressed how project concerns should be documented.

Open the July 23 public comment
Claim that the project would extend to Josey Lane
“This update of extending the project to Josey is 100% false. I’m going to assume the best in people and think this is just a misunderstanding. To that end, I’m going to request you provide the documents that, somehow, I haven’t seen or remove this inaccurate update.”

Kelly posted this after residents asked whether King Arthur traffic calming would continue to Josey Lane. In a later comment he distinguished the regional trails vision from the traffic-calming project.

Open the Aug. 2 public comment
Regional trails map versus the King Arthur project
“This is not traffic calming—it’s connecting trails from across all of DFW. The trails project design for the part our city plays has not been completed—last I looked it was about 30%. … This trails connectivity vision dates back as least a decade—at least 8 years prior to the first communications about the traffic calming project.”

Kelly said the NCTCOG map was an aspirational regional network, not a City construction page, and urged residents to subscribe to City newsletters and participate when a local design is presented.

Open the Aug. 2 trails comment
Public-input opportunity and timing of objections
“It was an input meeting—not a ‘this is the way it is’ meeting. For those that attended, there was ample discussion and attentive listening by staff. … But the facts are there was lots of opportunity along the way. … To what advantage was it to wait until taxpayer resources were spent and then show up for a conversation?”

This was Kelly's reply to criticism of the public-engagement process. It presents his position that residents had meaningful opportunities to participate before construction.

Open the public-input reply
Budget and ADA work
“Good news is the project was largely on budget—especially for a 6 figure 2+ year project. There’s a lot of confusion and misinformation about ‘over budget’ as there was a second project added for ADA ramp compliance. It made fiscal sense to do both at the same time. I’ve strongly advocated reviewing the council agenda.”

Kelly characterized the ADA work as a second project coordinated with traffic calming and encouraged residents to review Council agendas. The City's own June 2025 memo and later bid documents should be used to test that characterization and the unreconciled ramp counts.

Open the budget and ADA reply

Show up

Upcoming Council meetings.

Meeting information changes. Confirm the agenda and start time on Lewisville's official calendar before attending.

Called special budget meeting8:00 AMLewisville City Hall
Regular City Council meeting7:00 PMLewisville City Hall

Who represents Lewisville

City officials involved in the calming project.

Engineering staff developed and administered the project; the Mayor and City Council govern citywide and authorized the engineering and construction actions. Lewisville elects every Council place at large. Official minutes show both project actions were approved unanimously among members present: 6–0 for the June 2025 engineering amendment and 5–0 for the April 2026 construction award.

Mayor and City Council

Citywide elected officials

Project and City staff

Engineering and administrative contacts

Archived official Mayor and Council data

Straight answers

Frequently asked questions.

01Is this effort truly non-partisan?+

Yes. This effort is led by residents who affiliate with both major political parties, along with many independents. The MKAGA logo draws inspiration from presidential campaign themes associated with both a previous Democratic president and the current president.

02Why did Lewisville pursue traffic calming?+

The official deck cited a history of speeding concerns and stop-sign running, 85th-percentile speeds of 31–36 mph on a 25 mph corridor, and roughly 4,000 vehicles per day. It did not identify the original complainants, state how many complaints were received, or document a signed petition for the installed design.

03What did the City's crash review show?+

The official presentation stated there were no reported speed-related crashes on the corridor from 2020 through 2024.

04Did residents vote on the final design?+

We found a November 2024 input meeting, but not a binding resident referendum or a published vote on the final design. The construction award later appeared on the City Council consent agenda.

05Are there residents that support the calming project?+

Yes. At least 40 unique residents are documented as supporting the installed design. In a July 10 Facebook poll, 38 people selected “Nailed it! Love the bike lane, narrower lanes and additional signs.” J.D. and K.G. made separate comments explicitly supporting the installed work and do not appear among those 38 voters. P.K., who is included among the 38 poll voters, separately stated that he voted for and supports the project. This records self-selected Facebook participation, not a representative neighborhood survey. The Mayor and City Council, acting as a body, authorized the engineering and construction actions. The recorded Council actions were approved 6–0 in June 2025 and 5–0 in April 2026, unanimously among members present. Those votes document official approval of the project actions; they do not prove that every current member personally endorses every as-built detail.

06What is known about cost—and what could come next?+

Official records show a $675,000 FY2023-24 budget. Some planning estimates exceed $900,000; the $938,020 figure is an arithmetic pre-bid comparison combining the $850,000 construction estimate with $88,020 in authorized engineering—not a current contract amount or final paid cost. Known design and construction authorizations total $529,967.17, while final paid cost is not established.

07How was construction bid and who won?+

Lewisville used competitive sealed solicitation 26-33-C. Two bids were opened January 21, 2026: Quick Set Construction at $420,902.07 and Gibson & Associates at $535,685.13. Staff recommended Quick Set as the lowest responsive, responsible bidder; Council authorized $441,947.17 including contingency.

08Can the City Council reconsider the project?+

Residents can request a new engineering review and ask a councilmember to place modification or removal on a future agenda. That is different from automatically forcing a repeat of the prior contract vote.

09Can residents recall the mayor or a councilmember?+

In general, reducing speeds on King Arthur has broad neighborhood support, but the installed method is disputed and whether the measured outcome was achieved remains unclear. Most prefer to work with our elected officials, and a recall should be considered only as a last resort. Current petition participation suggests support to organize such an effort, but no official recall petition has been created. Charter Article VI creates an office-specific process. A petition must have at least 150 valid signatures and at least 30% of votes cast for that office at its latest regular municipal election. Place 6 received 1,640 candidate votes in the May 3, 2025 contest, so 30% is 492. The Charter also contains affidavit, petition form, timing, certification, election and turnout provisions. Under the current three-year cycle, the next regular election is May 1, 2027 for Mayor and May 6, 2028 for Place 6.

10Can Castle Hills un-annex from Lewisville?+

Potentially, but not through a simple neighborhood vote. Lewisville is a home-rule city. Under Lewisville Charter §1.04, removing inhabited territory requires a petition signed by a majority of qualified voters living in the proposed area, an accurate metes-and-bounds description and a plat. Even then, City Council may—but is not compelled to—disannex by ordinance if it finds the territory unsuitable or unnecessary for City purposes. A separate Texas Local Government Code §43.141 route exists only when a majority of property owners can prove a qualifying failure to provide services required by the applicable annexation service plan or agreement; if the City refuses a valid petition for 60 days, signers may seek relief in district court. The 50-voter petition-and-election process in §43.143 applies to general-law municipalities, not Lewisville. Any viable proposal must also resolve boundaries, police/fire and utility service, infrastructure, debt, taxes and any applicable refund. This is a difficult municipal-law process, not a simple petition campaign.

11Is King Arthur a traffic-calming project or an ADA-accessibility project?+

It is a traffic-calming and street-safety project with a pedestrian-accessibility component. The City scope includes crosswalks and ADA-compliant curb ramps. A June 2025 memo described 24 new or reconfigured ramps, while the later bid schedule lists 23 curb-ramp units; because the records do not reconcile those figures, neither is a definitive installed count. The 100% plans also mark at least five accessible on-street bays: three along the residential portion of King Arthur and two by Castle Hills Village Shops. They are public street spaces, not spaces assigned to the adjoining houses. Their locations are not visually random: the marked bays appear beside proposed curb ramps, pedestrian refuges, or sidewalk connections, where an accessible route can be provided. But the reviewed City record does not explain the selection rationale for each location, why particular homes front them, or why the plan appears to show five when its cover states 158 added spaces and federal Table R211 would ordinarily call for six among 151–200 marked spaces. Federal PROWAG R211 requires accessible spaces when on-street parking is marked, but includes an exception for parking designated exclusively as residential parking. The plans do not label these spaces resident-only, so a residential street by itself does not resolve whether that exception applies. Lewisville's ADA Transition Plan remains a separate citywide program.

12What other city projects that impact Castle Hills are being planned?+

The only documented future City project currently listed here is Castle Hills Trails Corridor I. Lewisville authorized a $59,500 schematic-design effort for a proposed 12-foot trail from Windhaven Parkway east to the utility easement and north toward the sports fields, with possible wayfinding, trailheads, furniture and shade. The action authorized schematic design, not a construction award, and the scope says the alignment and amenities remain subject to site analysis, easements, stakeholder review and public input.

13Do other cities ever change street-safety projects after installation?+

Yes. Culver City voted in February 2024 to remove substantial portions of its Move Culver City lane-reallocation project. That official Council record supports the point that an installed street design can be revised after operational review, public pressure, and political reconsideration.

14How do I stay up-to-date with what the City of Lewisville is doing?+

Subscribe to the City of Lewisville’s email newsletters, check upcoming City Council meetings and agendas, and follow the Castle Hills Community Facebook group for neighborhood discussion and shared updates.

15How can I get involved?+

There are several practical ways to help:

  • Document concerns: Document concerns and report them in the Facebook group.Facebook group
  • Legal Advice: If you're a lawyer, help identify and research legal avenues that could be used to solve the identified problems.
  • Engineers: Help us understand the best practices and guidelines for traffic-calming projects that are safe and implemented appropriately, and ways to remedy the issues identified.
  • Speakers: Volunteer to speak at City Council meetings until the identified issues are resolved.Council meeting calendar
  • Residents: Sign the petition and post questions or concerns in the Facebook group.Petition Facebook group
  • Volunteers: Spread the word, point neighbors to the petition, Facebook group and website, and help with outreach such as handing out flyers.

Sources, records and action links

Resource library.

Every source and destination linked throughout the page is collected here by topic. Key official documents are also preserved as local read-only copies.

Take action

Community comments

Project records

01
Archived · Official 2024 project presentationSpeed data, crash review, project history, proposed treatments, budget and schedule
02
Archived · City funding-source extractOfficial snapshot identifying $675,000 from the General Fund and $250,000 from the Castle Hills PID fund; funding is not final spending
03
Archived · October 2024 traffic-count summariesSix City-provided summary pages covering both directions at Polser–Morgan, Lake Avalon and Lady Carol
04
Archived · TxDOT CRIS aggregate query, 2016–2026Date- and segment-bounded aggregate output reporting two crashes; not a record of every strike, near miss or non-reportable incident
05
Official King Arthur project page and FAQCurrent City scope, project status, FAQ and stated 6–9 month evaluation approach
06
Archived · Official FY2023-24 budget workshop$675,000 King Arthur traffic-calming budget recommendation from General Fund fund balance
07
Archived · Construction staff memoTwo-bid process, recommendation and 5% contingency
08
Archived · Official bid tabulationAll unit prices · Quick Set $420,902.07 · Gibson $535,685.13
09
Archived · Quick Set vendor bidExecuted unit-price schedule and bidder certifications
10
Archived · Signed construction agreementQuick Set agreement, contract safeguards and bid exhibits
11
Archived · Engineering-amendment memo$620,000 to $850,000 estimate change and $88,020 design authorization
12
Archived · Signed engineering amendmentLJA scope, added ADA ramps, survey and design services
13
Live API record · Construction award 26-4500$441,947.17 authorization to Quick Set Construction
14
Live API record · Engineering amendment 25-4101$38,400 LJA amendment and project plans
15
Archived · June 2, 2025 Council minutesEngineering amendment approved 6–0 among members present as part of the consent agenda
16
Archived · April 6, 2026 Council minutesConstruction award approved 5–0 among members present as part of the consent agenda
17
Archived · 100% King Arthur construction plansAugust 2025 plan set, including barrier-free curb-ramp details and detectable warnings
18
Archived · supplied 95% King Arthur plan file76-page interim review set used only for a document-stage comparison; roadway title blocks themselves say 100% Submittal
19
Archived · Lewisville ADA Transition Plan updateSeparate citywide accessibility-barrier evaluation and prioritization program

Future Castle Hills planning

Comparable project processes

Elections, annexation and Council

01
Archived · 2022 Lewisville election resultsPatrick Kelly's first Place 6 election · 2,114 to 788
02
Archived · 2024 Lewisville election resultsMayor TJ Gilmore · 3,000 votes in a contested election
03
Archived · 2025 Lewisville election results69,162 registered voters · Patrick Kelly 1,640, unopposed
04
Archived · 2025 precinct reportPrecinct-level registration and vote results; precincts do not yield an exact Castle Hills boundary count
05
Archived · Mayor and City Council dataOfficial profiles and at-large Council structure
06
Lewisville Charter · Article IICity government and the Place 6 annexation trigger
07
Lewisville Charter · Article VIOfficial recall provisions
08
Lewisville Charter §3.01Three-year terms for the Mayor and Council
09
Lewisville Charter §5.01Regular election held on the first Saturday in May
10
Lewisville Charter §1.04Home-rule contraction of City boundaries
11
Castle Hills annexation overviewBackground on the November 15, 2021 annexation
12
Patrick Kelly · Castle Hills residency statementPublic statement saying his family has lived in Castle Hills for 25 years
13
Pre-annexation Castle Hills GIS boundaryOfficial City of Lewisville ArcGIS source layer
14
Texas LGC §43.141Disannexation petition for qualifying failure to provide services
15
Texas LGC §43.142Home-rule municipal disannexation
16
Texas LGC §43.143Petition-and-election route limited to general-law municipalities
17
Texas LGC §43.148Tax and fee refund provisions after disannexation

Public Statements by the City Council

Meetings and public comments

01
Official July 20 Council videoIndexed Visitors Forum and resident statements
02
Official July 20 meeting recordLewisville Legistar meeting page for the July 20, 2026 City Council meeting
03
Official July 20 meeting agendaOfficial City Council agenda PDF
04
Official July 20 meeting transcriptOfficial Swagit transcript with timed testimony
05
July 20 speaker · first King Arthur speaker at 39:19Timestamped official meeting video; full name is unclear in the official transcript
06
July 20 speaker · J.W. at 43:10Timestamped official meeting video
07
July 20 speaker · K.S. at 45:26Timestamped official meeting video
08
July 20 speaker · J.S. at 47:17Timestamped official meeting video
09
July 20 speaker · J.F. at 49:00Timestamped official meeting video
10
Official Aug. 3 Council videoVisitors Forum includes nine residents speaking about King Arthur
11
Official Aug. 3 meeting recordLewisville Legistar meeting page for the Aug. 3, 2026 City Council meeting
12
Official Aug. 3 meeting agendaOfficial City Council agenda PDF
13
Official Aug. 3 meeting transcriptOfficial Swagit transcript with timed testimony
14
Aug. 3 speaker · C.M. at 32:23Timestamped official meeting video
15
Aug. 3 speaker · R.V. at 33:38Timestamped official meeting video
16
Aug. 3 speaker · K.S. at 36:44Timestamped official meeting video
17
Aug. 3 speaker · T.C. at 38:35Timestamped official meeting video
18
Aug. 3 speaker · J.K. at 41:59Timestamped official meeting video
19
Aug. 3 speaker · C.H. at 44:48Timestamped official meeting video
20
Aug. 3 speaker · J.W. at 47:34Timestamped official meeting video
21
Aug. 3 speaker · M.D. at 51:13Timestamped official meeting video
22
Aug. 3 speaker · J.D. at 55:10Timestamped official meeting video
23
Lewisville meeting calendarCurrent agendas, packets, minutes and video
24
City of Lewisville e-newslettersOfficial email subscriptions for City news and updates
25
Aug. 19 Special Called Council Meeting announcementCity staff announcement for the King Arthur Boulevard traffic calming discussion at 6:00 p.m.

Contractor and legal references

Community-source materials

01
Facebook poll · 38 “Nailed it” votesSelf-selected July 10 poll supporting the installed bike lane, narrower lanes and additional signs
02
J.D. · installed-project support statementPublic comment saying the installed intervention appeared to have achieved its intended purpose
03
K.G. · necessary-work support statementPublic comment describing the installed work as necessary notwithstanding aesthetic objections
04
Community incident timeline20+ reported incidents during the first two months of installation
05
Redacted community incident ledgerPermissioned, privacy-safe reproduction of 24 incident reports and two near-miss or hazard reports; names, private channels, identifiers, and the unsupported police-only row were removed
06
Community photo · chipped concrete separatorInspected and metadata-stripped resident photo; broader incident counts remain unverified
07
Community photo · curb extensionInspected and metadata-stripped resident photo illustrating the installed road geometry
08
Facebook discussion · tire and rimSearch the Castle Hills Community group for the quoted resident report
09
Facebook discussion · damaged barriersSearch the Castle Hills Community group for the reported separator count
10
Facebook discussion · cyclist fallSearch the Castle Hills Community group for the Enchanted Hill report
11
Facebook discussion · lane movementSearch the Castle Hills Community group for reports involving oncoming lanes
12
Facebook discussion · Range Rover near Lady of the LakeSearch the Castle Hills Community group for the reported tire-and-rim incident
13
Facebook discussion · concrete block in travel laneSearch the Castle Hills Community group for the reported roadway hazard
14
Public post · company truck tire contactEyewitness post about both passenger-side tires contacting an island
15
Public comment · pool-route and Enchanted Hill reportsOne comment describing two separately stated July 26 events
16
Public reply · King Arthur and Morgan LeFayFollow-up report identifying a second location and time
17
Public comment · two unspecified incidentsAggregate eyewitness claim retained as one entry because the events lack individual details