Access Official Technical PDF

Share Summary:LinkedInEmail

Solar energy system permitting is not only a question of whether panels can be installed. Local rules may also determine which zoning districts allow a project, who reviews the application, what site information is required and how equipment must be maintained or removed. A 2019 proposal from the City of Belfast, Maine, offers a detailed example of how a municipality sought to organize these decisions for projects ranging from residential installations to large ground-mounted arrays.

The proposal was intended to establish standards for solar system design, installation, operation, maintenance and abandonment. It covered systems of different sizes and mounting configurations, while assigning additional requirements to projects in shoreland and flood zones. The document describes proposed amendments and a public review process; it should not, by itself, be treated as confirmation of the rules currently in force.

How Belfast’s proposed solar energy system permitting was structured

The framework linked permitting requirements to three main factors: system scale, mounting type and location. It defined small-scale systems as occupying less than 20,000 square feet, with a stated nameplate capacity of about 125 kW or less. Medium-scale systems were defined by a footprint of at least 20,000 square feet but less than four acres, and a nameplate capacity of 125 kW to 1 MW. Large-scale systems were defined as occupying at least four acres and generating 1 MW or more.

Those definitions distinguished projects by physical footprint as well as rated output. Roof-mounted systems could fall into any size category, while ground-mounted systems could be small, medium or large. The proposal also defined pole-mounted and off-grid systems, along with terms such as solar access, glare and rated nameplate capacity. For project teams, clear definitions matter because a classification can determine which review path and standards apply.

Review pathways depended on project type and zoning district

Under the proposal, small- and medium-scale systems—whether roof-mounted or ground-mounted—and large roof-mounted systems generally required building and electrical permits from the Code Enforcement Officer. Large ground-mounted systems followed a more involved route: they required a site plan permit reviewed by the Planning Board. The Board was expected to consider preliminary and final plan requirements together in a single review.

Permitted uses were identified district by district in the zoning code. In many districts, smaller systems and large roof-mounted systems could receive Code Enforcement Officer review, while large ground-mounted systems went to the Planning Board. The proposal included exceptions. For example, certain large systems in residential districts inside the bypass area were limited to property owned or controlled by the City or Regional School Unit 71. Some uses were listed as prohibited in specific districts.

Location introduced additional checks. In designated shoreland districts, systems had to meet both the solar provisions and applicable shoreland standards; the proposal prohibited them in Resource Protection and Stream Protection districts, with a limited roof-mounted exception for a residence. Flood-zone rules also differentiated between roof- and ground-mounted installations and among designated flood areas. Applicants would therefore need to establish the zoning and environmental overlays affecting a parcel before settling on a design.

Large ground-mounted projects required broader application information

For a large ground-mounted system, the proposed application requirements extended beyond basic equipment and site layout. Applicants were asked to provide information including:

  • The system owner and operator, their qualifications, and relevant lease and easement arrangements.
  • The energy to be produced, its intended buyer, and the proposed grid connection, including responsibility for operation and maintenance of the connection.
  • Panel configuration, major components, construction schedule, operations and maintenance plans, and an emergency management plan.
  • Financial capacity, vegetation management, buffering measures and a decommissioning plan.
  • Evidence of applications for required non-City permits before the Planning Board issued a site plan permit.

The proposal gave the Planning Board latitude to decide which general site-plan submission items were relevant to a solar project. That approach recognizes that review needs are not identical across project types, while still requiring information on ownership, technical arrangements, site management and end-of-life responsibilities.

Design, safety and operating obligations

Dimensional standards addressed height and setbacks for ground-mounted systems. For example, a ground-mounted system less than 50 feet from a property line could not exceed 16 feet in height at maximum tilt; systems at least 50 feet from a property line could reach 30 feet. Setbacks also varied by project scale and yard location. Shoreland projects were subject to the applicable structure setbacks in the shoreland provisions.

All covered installations were expected to meet the applicable photovoltaic-system requirements of the latest editions of NFPA 1 and the National Electrical Code (NFPA 70), as cited in the proposal. Electrical connections required inspection and approval by the City’s Code Enforcement Officer or Electrical Inspector before operation. A connection to the public utility grid also required the utility’s inspection and approval. The standards called for regular maintenance to keep systems operating safely and as designed.

For medium- and large-scale ground-mounted projects, the proposal called for reasonable efforts to place utility connections underground, subject to site conditions and utility-provider requirements; utility transformers could remain above ground if required by the provider. Large projects also faced review of fire safety, visual buffering and glare. Where airport operations could be affected, the Planning Board could require a glare analysis and consider its findings in deciding whether to approve an application or impose conditions.

Decommissioning was part of project planning

The proposed rules treated removal as a planning responsibility, not an issue to defer until a facility stopped operating. A large-scale system that was abandoned or failed to produce power for 12 consecutive months was generally considered abandoned. The owner or operator would need to submit a removal plan, remove system components within 150 days of the applicable discontinuation date, dispose of waste according to applicable requirements, and stabilize and revegetate the site as needed.

The proposal also called for a performance guarantee equal to 150% of estimated removal costs, in a form acceptable to the City. The guarantee was intended to help ensure that funds would be available if an abandoned system was not removed by its owner or operator. A community donation option and a process to request reactivation were also described, subject to Planning Board review.

Practical considerations for project teams

Belfast’s proposal shows how municipal solar zoning can connect land-use decisions with electrical safety, utility coordination, emergency planning, visual impacts and decommissioning. For developers and technical teams, the practical sequence is to confirm the applicable zoning and overlays, classify the system by scale and mounting type, identify the reviewing authority, and build the required technical and operational documentation into project planning.

For municipalities, the example highlights the value of defining thresholds and review responsibilities while addressing the full operating life of a project. Because the Belfast document describes proposed amendments from 2019, anyone assessing a project must verify the current ordinance and permitting requirements with the relevant authorities. The broader lesson is that effective solar energy system permitting depends on aligning equipment design, site constraints and long-term responsibilities from the outset.

Access Official Technical PDF

About The Author