Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Use Traffic Mitigation topic
No spam. Unsubscribe anytime.
Council directs staff to talk with Tule developer about possible gate; direction passes 5-2
Summary
By a 5-2 vote, the council directed staff to meet with the Tule development’s developer to explore installing a gate as part of or in lieu of other traffic‑monitoring measures; council emphasized the action was a request to staff, not an approval to build a gate.
The Newcastle City Council voted 5-2 March 4 to direct staff to meet with the Tule (referred to in meeting as “Tool/Tully/Tule”) project developer to explore whether the developer would install a gate or otherwise alter project conditions to address neighborhood traffic concerns.
Council discussion made clear the motion was a request for staff to open talks with the developer rather than a council approval to build a gate. City Manager Pingel said staff would approach the developer with the council’s direction and that the developer could decline to participate; “they can tell us no and go through the regular process,” Pingel said.
Council had earlier voted 5-2 to add the issue to the agenda. At the March 4 meeting, members described the direction as a response to neighborhood concerns and asked staff to pursue discussions that would be consistent with the project’s conditions of approval and the traffic monitoring plan.
Why it matters: The direction could lead to developer‑funded mitigation if the developer agrees, but it does not change project approvals or permit conditions by itself. The council’s action starts a staff‑level discussion and does not bind the developer or staff to a particular outcome.
Next steps: Staff will meet with the developer and report back. Any change requiring physical work, permit amendment, or expenditure would require subsequent formal approval.
