Project River Issues

What the record supports, what remains uncertain, and what evidence would answer the most important questions.

An open question is not a proven harm — and a project claim is not independent verification.

01 · Open

Boundary, Annexation & Land Use

Sources: R02,R03,R04,R05,R06,R21

The legal relationship among the approximately 850-acre campus, prior Frontage Road annexations, the urban-growth boundary, and separate Lower River Road commercial tracts requires parcel-level mapping and legal-document review.

Currently supported

  • Earlier Frontage Road annexation activity is documented in city/county records.
  • The city lists a separate 385.58-acre Lower River Road commercial annexation request.
  • Project River has been publicly tied to annexation and planned-unit zoning.

Questions requiring evidence

  • What exact parcels make up the campus?
  • Which parcels are or were inside the UGB at each relevant date?
  • Which annexations are legally contiguous or qualifying noncontiguous annexations?
  • Which uses are allowed under current zoning versus dependent on new city action?
02 · Open

Energy Design & Biomass Feasibility

Sources: R13,R17,R19

The published concept combines very large gas generation with a 500 MW woody-biomass component. The central technical question is not whether biomass power exists, but whether this specific integrated scale, phasing, feedstock, water-recovery concept, and operating reliability are demonstrated.

Currently supported

  • Developer materials describe up to 1,000 MW gas plus 500 MW biomass.
  • Azure Engineering describes a five-phase project beginning with 100 MW of gas generation.
  • Developer and engineering pages are not a substitute for owner-verified comparable operating references.

Questions requiring evidence

  • Which exact technology vendors and reference plants support the 500 MW biomass design?
  • What is net output after parasitic loads?
  • What fuel moisture and annual tonnage assumptions are used?
  • What happens operationally if biomass is delayed, curtailed, or replaced?
03 · Open

Air Quality & Public Health

Sources: R07,R09,R13,R20,R27,R28

Gas combustion, biomass conversion, wood handling, trucking, and backup systems have different emissions profiles. Project-specific permit-grade inventories and dispersion modeling are needed before local exposure can be characterized.

Currently supported

  • Project materials describe gas and biomass generation.
  • TDEC air-permit processes are separate from city land-use proceedings.
  • Community and advocacy estimates are not final permitted emissions.

Questions requiring evidence

  • What are hourly and annual emissions by source?
  • What controls and monitoring apply during normal, startup, shutdown, and upset conditions?
  • What are modeled concentrations at nearby homes and schools?
  • How will fugitive wood dust and diesel traffic be handled?
04 · Open

Water, Wastewater & Watershed

Sources: R08,R09,R13,R14,R17

The project says it will recover water from biomass drying and use closed-loop cooling. The key unresolved issue is the complete water balance across all phases and operating states, including periods before biomass is operating.

Currently supported

  • Project River says routine operations will not depend on city water.
  • Azure describes closed-loop cooling and dryer-condensing makeup water.
  • Proposed PUD language described by the project does not mean zero outside water under every circumstance.

Questions requiring evidence

  • What are daily, peak, startup, outage, and drought water requirements?
  • Where does initial fill / priming water come from?
  • How are blowdown, treatment rejects, stormwater, and wastewater handled?
  • How does the water system work during a gas-only first phase or biomass outage?

Open detailed Water & Cooling review →

05 · Open

Forestry, Habitat & Feedstock

Sources: R10,R17,R20,R28

At the proposed scale, annual woody-biomass demand and sourcing are consequential. Sustainability depends on the actual material mix, sourcing geography, competing demand, harvest practices, and verified forest growth/removal data.

Currently supported

  • Project and Azure materials describe southern pine / woody biomass.
  • Azure says roughly six million tons of biomass annually.
  • State forest data can provide context but a project-specific procurement plan is still needed.

Questions requiring evidence

  • How much is mill residue, logging residue, thinning, or whole-tree material?
  • What counties and ownership types will supply it?
  • How does added demand compare with net forest growth and existing removals?
  • What chain-of-custody and habitat safeguards will be independently audited?
06 · Open

Traffic, Freight & Road Safety

Sources: R11,R14,R20,R21,R28

Biomass deliveries, construction traffic, workforce travel, heavy equipment, and other industrial logistics could materially affect roads. Published truck estimates should be tested against a route- and hour-specific traffic study.

Currently supported

  • Large biomass volumes imply substantial freight movement.
  • TDOT has a formal traffic-impact-study process.
  • Proposed project conditions have included truck-routing concepts.

Questions requiring evidence

  • How many loaded and empty truck movements occur by hour and phase?
  • What routes, intersections, bridges, and queue-storage areas are affected?
  • How are school, emergency, and commuter travel windows handled?
  • Who funds construction, maintenance, and mitigation if actual volumes exceed forecasts?
07 · Open

Noise, Lighting & Neighboring Property

Sources: R14,R20,R22,R27

Continuous industrial equipment, cooling systems, gas turbines, wood handling, construction, lighting, and traffic can produce effects not captured by a single property-line number.

Currently supported

  • Developer materials describe a quiet-by-design campus.
  • Proposed PUD requirements described by the project include a 60 dB property-line limit and monitoring.
  • Site-specific receptor modeling and long-term measured effects are not yet established in the sources reviewed.

Questions requiring evidence

  • What are modeled daytime and nighttime levels at the nearest homes?
  • Are tonal and low-frequency components evaluated?
  • What lighting contours and viewsheds reach neighboring property?
  • What complaint, monitoring, correction, and enforcement process would apply?
08 · Open

Electricity, Grid & Utility Costs

Sources: R13,R14,R15

The project says most electricity will be produced onsite with a 360 MW grid reservation for backup and peaking. Actual ratepayer exposure depends on executed interconnection, standby, upgrade, and cost-allocation agreements.

Currently supported

  • Developer materials describe up to 1,500 MW onsite generation and a 360 MW grid reservation.
  • A grid reservation does not by itself establish who pays for upgrades or standby capacity.
  • Project-specific utility agreements were not established in the materials reviewed.

Questions requiring evidence

  • What are peak imports and exports under normal and outage scenarios?
  • What upgrades are required and who pays?
  • What standby charges and security arrangements apply?
  • How does the arrangement change if the end user or generation mix changes?
09 · Open

Jobs, Taxes, Incentives & Public Cost

Sources: R13,R15,R21,R22

Project River advertises large investment, employment, and tax-base benefits. These are forecasts until supported by detailed job classifications, fiscal modeling, executed tax/PILOT terms, and infrastructure-cost agreements.

Currently supported

  • Project River describes more than $11 billion in private investment.
  • The project says it will create substantial direct and indirect employment.
  • Its tax-base page says detailed allocation figures were still being finalized.

Questions requiring evidence

  • How many jobs are construction, permanent onsite, forestry, contracted, and data-center roles?
  • What portion is expected to be local versus regional?
  • Are there PILOT, abatement, incentive, or infrastructure agreements?
  • What security protects the public if the project stalls, changes ownership, or closes?
10 · Open

Corporate Experience, Roles & Due Diligence

Sources: R17,R18,R19,R25,R26,R27

Azure Energy, Azure Engineering, and Algorhythm-related entities have been publicly associated with the power project. Corporate age, team experience, project-specific responsibility, and contractual guarantees should be evaluated separately.

Currently supported

  • Azure Engineering lists Project River and describes its engineering scope.
  • Algorhythm’s SEC filing confirms a Sept. 15 transaction involving Azure Energy.
  • Algorhythm says the Azure team has participated in 72 plants / 17.5 GW; that wording describes collective team experience, not necessarily Azure corporate completed projects.
  • A 2024 federal docket confirms a business dispute involving Andrew Thompson and Azure Holding Group; the federal court remanded for lack of jurisdiction and did not decide the merits.

Questions requiring evidence

  • Which legal entity is responsible for Project River engineering, development, construction, commissioning, and performance?
  • Which comparable operating plants can owners independently verify?
  • Who is engineer of record?
  • What warranties, bonds, parent guarantees, or performance obligations apply?
11 · Open

Governance, Transparency & Public Process

Sources: R01,R12,R21,R22,R24,R27

Community debate has focused heavily on timing, annexation, access to records, the sequencing of studies and votes, and whether residents can influence decisions before commitments become difficult to reverse.

Currently supported

  • The city delayed/suspended direct Project River meetings pending engineering review.
  • Two developer-led community meetings occurred in September.
  • Public-record law governs access to existing government records, not creation of new studies.

Questions requiring evidence

  • When did each government body first receive a project-specific proposal?
  • Which studies will be public before land-use decisions?
  • Which developer commitments will become enforceable conditions?
  • What records, consultant scopes, and correspondence can be disclosed before proceedings resume?
12 · Open

Permits, Enforcement & Monitoring

Sources: R07,R08,R09,R14

City zoning and state/federal permits are separate. Project safeguards only become meaningful when mapped to a responsible regulator, measurement method, reporting schedule, and remedy.

Currently supported

  • TDEC maintains separate air and water public-participation processes.
  • A proposed PUD is not a substitute for environmental permits.
  • The reviewed record does not establish a complete final permit matrix for all components.

Questions requiring evidence

  • Which permits are required for each project phase?
  • What studies must be accepted before grading, construction, or operation?
  • Which conditions are continuously monitored?
  • What public data and enforcement remedies will exist after startup?
13 · Open

Future Changes, Substitution & Decommissioning

Sources: R17,R21,R23

Because the project has no confirmed final end user in the reviewed record and the design is phased, material changes could alter impacts. The approval framework should distinguish the reviewed concept from later substitutions.

Currently supported

  • Local reporting says no data-center operator contract had been signed as of the Sept. 1 meeting.
  • Azure describes phased construction.
  • Project-specific impacts depend on the final customer, power mix, equipment, and water system.

Questions requiring evidence

  • What constitutes a material change requiring renewed review?
  • Could additional gas or another technology replace biomass without new land-use review?
  • What happens if no customer materializes?
  • What financial assurance covers decommissioning and site restoration?