Power by county
Blount, TN: data center power outlook
Blount, Tennessee is served through an area outside an organized wholesale market, and the figures below describe the public grid around a prospective data center site there. Blount carries 63 mapped substations within its boundary, and the highest reachable grid access is 500 kV. Service in Blount spans 8 utilities, with CITY OF ALCOA UTILITIES, CITY OF LENOIR - (TN), DUKE ENERGY CAROLINAS, LLC among those mapped.
Grid position at a glance
- Serving utilities
- CITY OF ALCOA UTILITIES, CITY OF LENOIR - (TN), DUKE ENERGY CAROLINAS, LLC, FORT LOUDOUN ELECTRIC COOP, KNOXVILLE UTILITIES BOARD, MARYVILLE UTILITIES, SEVIER COUNTY ELECTRIC SYSTEM, TENNESSEE VALLEY AUTHORITY
- ISO / market
- NON_ISO (Not in an organized wholesale market)
- Highest grid access
- 500 kV
- Substations in county
- 63
- Industrial retail rate
- 6.7¢/kWhState-level EIA-861 industrial average. The map colours by this, not by a per-county rate.
- Per-utility rates in county
- 7 of 8 serving utilities: 4.9 to 14.4¢/kWhLowest to highest industrial rate among the utilities serving this county (EIA-861 Sales to Ultimate Customers). A spread, not the county’s rate, and it covers only the serving utilities that report one.
- Interconnection queue
- None on record
- Proposed generation
- None on file (EIA-860M)Units filed with EIA as planned or under construction (Form EIA-860M). Declared intent from the federal inventory, not the interconnection queue and not guaranteed capacity.
- Grid carbon intensity
- 641 lb CO2/MWh
- Water withdrawals
- 16 Mgal/dAll uses, freshwater. Water already withdrawn locally, not water available for a new load.
- Construction labor near site
- 40,725 employed in construction within ~120 km (38 of 41 counties reporting)A large build needs hundreds of skilled construction workers on site for one to three years. A county with few of them within commuting range means bussing crews in, per diem, and housing, which is real cost and schedule risk. This counts people employed in construction within about a 120 km drive (BLS QCEW), summed across nearby counties. It is not labor known to be available: most are already committed to other projects, and no public data reveals who is free.
Grid conditions in Blount
The material below frames Blount, Tennessee for a prospective large load, drawing only on public sources. Grid access in Blount extends to 500 kV, a high-voltage line class. The mapped layer packs 63 substations into Blount, a dense spread of options.
Blount, Tennessee is not inside an organized market, which leaves interconnection to the utility and bilateral contracts. For Blount, the rate shown is the state industrial average of 6.7 cents per kWh (EIA-861), a state figure and not a county-specific one. Beneath that state average, the utilities serving Blount that report an industrial rate span 7 of 8 serving utilities: 4.9 to 14.4¢/kWh, shown as context and never as the county rate.
No interconnection-queue project is on record for Blount, Tennessee in the covered feeds, which reflects either genuine quiet or a queue not yet ingested. Blount, Tennessee has no EIA-860M generation on file, which reads as zero rather than as a gap. Blount sits under a balancing authority that eGRID puts at 641.018 lb CO2 per MWh.
Blount withdrew 15.76 million gallons per day for all uses in the USGS 2015 data, which counts demand, not headroom. About 40,725 people are employed in construction within a 120 km commute of Blount (BLS QCEW), which frames staffing distance rather than free labour.
For Blount, treat this as screening-grade county context useful for narrowing a search rather than settling a site. Taken together, the figures for Blount, Tennessee describe the grid around a prospective site, drawn from public data with their gaps left visible on purpose. To move past screening in Blount, Tennessee, a specific address needs its own interconnection study, which this page does not attempt. The figures for Blount, Tennessee refresh as their public datasets do, and the exact sources and dates sit in the source log below this section.