Citizen Portal
Sign In

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

Get email alerts on the Master Planning topic

No spam. Unsubscribe anytime.

Beta Technologies outlines a flexible 'adaptive campus' master plan for South Burlington airport area

South Burlington Development Review Board · June 17, 2026
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

Beta presented a sketch master plan to create an adaptive, phased campus across roughly 100 acres at the airport, proposing triggers for infrastructure, 10% civic‑space targets, and limited minor‑amendment flexibility; board and staff requested further detail on public access, triggers, and coordination with DPW and the airport.

Beta Technologies presented a sketch master plan and subdivision concept that would create an adaptive campus across about 100 acres near the South Burlington airport. The company said the shift reflects a strategy to internalize more of its supply chain — including motors, batteries and larger composite parts — and to coordinate infrastructure delivery (roads, pump station, possible substation) with development triggers. "We're gonna go from just assembling planes to assembling structures here, to building our motors here, to building batteries here," a Beta presenter said.

Beta proposed defining development ranges rather than fixed building footprints, with an infrastructure implementation plan to align transportation and utilities with growth. The plan sets civic space at 10% of buildable area and asks for flexibility to allocate or reallocate civic space across development areas as projects advance. Board members and staff probed whether civic spaces must be publicly accessible, what constitutes a minor vs. major master‑plan amendment (applicant asked for a 10% buffer for small additions), and how future phasing triggers would be enforced. Staff recommended applicants provide more specific narratives in the master plan describing when private vs public infrastructure would be used and how the city’s projects would be coordinated with Beta’s infrastructure schedule.

Public commenters and board members raised connectivity and traffic concerns related to aviation and cargo access routes; the applicant said it would continue coordination with the airport and DPW, and that some parcels are held by the airport under long ground leases while others are owned or under purchase agreements by Beta. The board did not act on the sketch plan at this meeting and asked for more specific trigger language, phasing details, and clarifications on civic‑space public access and obligations for future owners.