Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Land Use Development topic

No spam. Unsubscribe anytime.

Council approves rezoning for Parkside at InView, limits project to 620 units; proffers include traffic studies and historic-preservation MOU

3093054 · April 22, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Newport News City Council voted unanimously April 22 to adopt an ordinance rezoning 350 Yorktown Road for the Parkside at InView development, with proffers that cap residential units at 620 and require developer-funded traffic analyses and a historic-preservation memorandum of understanding.

Newport News City Council voted unanimously April 22 to adopt an ordinance changing the zoning for a 282.3351-acre parcel at 350 Yorktown Road to allow the Parkside at InView development with new proffers, including a cap of 620 residential units, developer-funded traffic-signal analysis and improvements if warranted, and an agreement to protect historic resources on the site.

The change affects property owned by the Economic Development Authority and shifts existing zoning described in the staff report (R-9 mixed use with proffers and P-1 Park) to R-9 mixed use with new proffers. During a presentation, Grady Palmer, identifying his address as 999 Waterside Drive and speaking for the project team, said the proposal is a “very mixed housing, pedestrian connected proposal” that emphasizes homeownership opportunities and “will not exceed 620 residential units.” He told council the property had previously been zoned for about 1,200 units but the project’s proffered maximum is lower.

Palmer described a package of proffers intended to reduce community impacts. He said the developer had included a traffic-impact analysis and would provide the results to the city: “we will do signal analysis of all these signals … and in the event that it’s warranted, then we will perform any improvements that are needed.” He also said the project would include a gated entrance on Crawford Road limited to emergency access only, and a memorandum of understanding among governmental agencies to “preserve and protect historic resources on the property” with signage and reporting obligations.

Nearby residents used the public hearing to press council on traffic and notice. A speaker identifying himself as a resident at 548 Yorktown Road said he has lived less than a half mile from the proposed entrance since 1977 and raised safety concerns, citing heavy tour-bus traffic and a prior school-bus accident at Crawford and Yorktown roads. He said he did not recall receiving timely written information about the project and urged the council to “take a closer look” before approving the change.

A project representative (stating a Suffolk address) told council he and colleagues would be available to answer questions and that detailed materials had been presented to staff and planning. Council members asked follow-up questions about where road widening would occur and who would fund it; staff and the developer said the project would dedicate land for future widening on Yorktown Road but the developer would not build the widened roadway. Councilmember questions about Crawford Road confirmed that the Crawford entrance would be emergency-only.

After the public hearing closed, the council moved and seconded both to close the hearing and to adopt the ordinance. The roll calls recorded unanimous support; the meeting record states “Motion carried 7 0.”

Why it matters: the parcel is large and near key corridors and historic resources. The proffers limit total units to 620 — materially less than prior zoning capacity the developer cited — and include traffic and historic-preservation commitments that the city will need to monitor as the project advances.

Council action and next steps: the ordinance was adopted on April 22 by a 7-0 vote. The developer and city staff indicated additional site-level approvals and traffic/work-permit coordination will be required before construction; council members asked that staff continue to provide details during council deliberation and permitting.

Votes at a glance: the council recorded the ordinance adoption as carried 7-0. The meeting record does not specify the names of the motion mover and seconder for this item.