Start here
Project factsPower & gridAir & generatorsCommunityResearch Pass · $11.99Submit a correction or source →Explore all topics
Claim checker
These ratings address the statement—not the person who made it. “Unsupported” means the reviewed record does not establish the claim; it does not mean a future event is impossible.
Confirmed, with important operating context.
The submitted application lists 766 critical emergency generators and 16 support emergency generators. It describes them as backup equipment for interruptions in electrical service, not as the planned everyday power supply.
Confirmed as combined backup nameplate capacity.
The application states approximately 464 MW at SBN520 and 1,655 MW at SBN750. Nameplate backup capacity is not the same thing as expected simultaneous routine generation.
Confirmed as rounded storage capacity.
Adding the listed belly tanks and 26 bulk tanks produces 5,466,277 gallons of storage capacity. Storage capacity does not establish annual fuel consumption.
Confirmed.
The application proposes six buildings at SBN520 and twenty at SBN750.
Those estimates are now outdated.
The opposition website’s published estimate predates Amazon’s July 2026 air application. The submitted application identifies 26 buildings and an exact proposed inventory of 782 generators: 766 critical units and 16 support units.
Operation can be consequential, but “continuous” is not supported.
Amazon’s application describes the diesel fleet as emergency backup. Generator noise and exhaust occur when engines run for emergencies, testing, maintenance or other allowed operation. Cooling and other mechanical equipment may operate routinely, but that is not evidence that the diesel engines will run continuously.
The phrase is real; the conclusion omits how the category works.
The application says uncontrolled potential emissions would exceed major-source thresholds. It requests controls and emission limits intended to keep limited potential emissions below applicable thresholds. If IDEM issues those conditions in a federally enforceable permit, they become legal operating limits—not voluntary paper promises. They remain proposed until IDEM acts.
The submitted Hobart application requests a FESOP, not Title V.
Amazon requests a New Source Minor PSD/Emission Offset construction approval and a Federally Enforceable State Operating Permit. IDEM’s current table lists public notice for a New Source FESOP Minor PSD/Emission Offset review but does not list proposal to U.S. EPA. EPA’s separate objection and citizen-petition process applies to certain Part 70/Title V permits.
The 97% figure is not supported by Amazon’s Hobart application.
For its potential-to-emit calculations, Amazon uses 68.6% as the conservative filterable-PM control efficiency. The application lists manufacturer options ranging from 68.6% to 75.6% for filterable PM and says the final control-system selection had not been made.
Confirmed as a potential-to-emit calculation.
The application expressly says uncontrolled potential emissions of NOx, CO and VOC appear greater than major-source thresholds. Potential-to-emit is a regulatory worst-case calculation, not a forecast of expected annual emissions.
Confirmed as a transmission planning record, not current delivered service.
MISO’s February 2026 planning record identifies a new Hobart 345-kV load addition, related transmission work and a March 2027 expected in-service date. The record documents the planned grid pathway; it does not mean the full data-center load is already connected or operating.
Not supported by the current project record.
Lebanon involved an explicit, separate temporary natural-gas generation proposal. The project records reviewed show emergency diesel backup, an approved NIPSCO service contract, GenCo generation resources and a MISO transmission project. No reviewed project filing establishes a plan to use the 782 diesel generators as Lebanon-style bridge power.
Federal rules distinguish emergency and non-emergency operation.
The federal emergency-engine rule has no hourly ceiling during a genuine emergency. It generally allows up to 100 hours per engine for maintenance and testing, with a restricted 50-hour non-emergency subset counted inside that 100. The application also proposes combined emission caps and hour-meter records. Ordinary bridge generation does not automatically become emergency operation.
A limited stormwater technical review exists; a unified review is different.
The October 21, 2025 construction-stormwater technical review found the mass-grading plan adequate for the minimum City stormwater and IDEM construction-stormwater requirements and required a Notice of Intent. The review expressly says it does not cover every other local, state or federal permit. It is therefore evidence of review—not proof that every environmental question has been resolved.
It is not a Hobart-specific acoustical study.
The linked 2022 report models sites in Northern Virginia. Its author describes it as a basic predictive analysis and says the results are not exact. It can identify questions worth testing, but it does not use the Hobart campus layout, equipment plan, barriers, terrain or receivers and cannot establish Hobart neighborhood sound levels.
The duration is real, but the shorthand blurs distinct incentives and payments.
The approved agreements provide a 10-year, 100% real-property abatement for each eligible building and a separate 35-year, 100% exemption for qualified enterprise IT equipment in each eligible building. That local Hobart IT exemption is distinct from Indiana’s separate state data-center sales and use tax exemption program. The community agreement also schedules $175 million in contributions and separate per-building impact payments. Some scheduled contributions may be reduced by annual impact payments, and the schedule alone does not prove every payment has already been received.
The Hobart local IT exemption is 35 years; a separate state program can have a longer term.
Hobart Resolution 2026-04 provides a 35-year, 100% exemption for qualified enterprise IT equipment in each eligible building. Indiana separately offers a state data-center sales and use tax exemption program that may run up to 50 years for qualifying investments over $750 million. The state program’s maximum term should not be relabeled as Hobart’s local agreement.
They are estimates, not an unconditional hiring guarantee, but accountability exists.
The project-wide Statement of Benefits estimates more than 400 permanent Amazon positions at $37.44 per hour, plus contractor positions. The agreement says the City cannot compel the investment or jobs. It also requires annual compliance reporting, allows job and wage information requests, and permits abatement denial for a demonstrated material failure to substantially comply, subject to reasonable-nearness, force-majeure, cure and appeal provisions.
That is a land-use judgment, not a self-proving factual conclusion.
The scale is industrial in ordinary language, but Hobart’s zoning ordinance addresses data centers in the M-1 Light Manufacturing district. Whether this use belongs at the location is a policy opinion residents and officials may debate; it is not established merely by labeling the project “heavy industrial.”
No. The reviewed orders do not declare the project illegal; the only final merits ruling identified confirmed the City’s ERA and real-property tax-abatement actions.
On February 18, the court denied the residents’ tax/ERA petition and confirmed the Common Council’s ERA designation and real-property abatements. On March 26, a different court dismissed or barred the first-fill-permit challenge because the plaintiffs had not exhausted the City appeal process and had not timely filed the administrative record; it expressly did not reach the requested preliminary injunction. Reconsideration was denied April 13. Later fill-permit and site-plan claims remain pending, so the record is favorable to the City on the issues already decided but is not a blanket ruling on every project approval.
No. One petition ended in a final trial-court ruling favorable to the City, while two related judicial-review matters remain active.
The February 18 order denied the tax/ERA petition and confirmed the ERA designation and real-property abatements. The March 26 order disposed of the first-fill-permit challenge on procedural grounds, and the April 13 order denied reconsideration. But the original case continued with amended claims and dispositive-motion briefing, and a third case filed June 8 challenges the May 7 site-plan approvals. On July 28, the court granted consolidation of those two active matters. Consolidation changes how the cases proceed; it does not decide their merits.
The approved contract contains specific exit and customer protections.
Cause 46322 describes a 15-year customer contract, an ultimate-parent guaranty, pre-operation and early-termination payments, and required IURC notice if specified termination events occur. The default allocation places project-related electric and transmission upgrade costs on Amazon or GenCo. Those protections materially reduce cost-shift risk, but they are not a promise that every imaginable future cost can never be proposed; a later allocation would require a docketed proceeding and a customer-benefit showing.
The current approved record does not support that attribution.
NIPSCO’s current multi-step base-rate increase was approved in Cause 46120 in June 2025, with the final step tied to 2025 plant balances. The IURC’s 2026 affordability presentation identifies the principal drivers as previously approved solar, storage and delivery-system investments. The Hobart Amazon contract and GenCo resources were approved later, in June 2026, under separate orders that assign project-related costs to Amazon or GenCo. At Amazon’s projected full load ramp, Cause 46322 estimates residential bill credits of about $7 per month, or $82 per year. A customer’s bill can still change because of usage, fuel factors and other riders, so a bill increase alone does not identify its cause.
High-confidence probability: qualifying project-review costs are developer-reimbursable, but final payment proof is pending.
Hobart Municipal Code Chapter 155 requires a developer seeking covered land-use or financing actions to execute a project-specific reimbursement agreement and deposit funds for actual attorney, engineering, technical, financial, advertising and recording costs. The 2026 fee schedule repeats that framework, and City minutes show reimbursement agreements being used on other developments. That creates a high-confidence probability that qualifying data-center review costs were covered by reimbursement arrangements. It does not, by itself, prove that every reported invoice, the cited $205,000 total or the City’s defense of the resident lawsuits was reimbursed. The Amazon-specific agreement, deposit records and payment ledger are still needed.
The billion-dollar figure is a long-term revenue projection—not a realized or guaranteed net return.
Mayor Huddlestun has described projected payments of $102 million in 2026, $43 million in 2027, $40 million in 2028 and about $50 million per year after full buildout. He separately projected approximately $1.5 billion in additional revenue over 35 years. The approved community agreement supports a $175 million contribution schedule and separate per-building impact payments, but future totals depend on construction, occupancy, assessments and contract conditions. The reviewed public record also does not independently establish the cited $205,000 legal-cost total.
The webinar described an expected average—not a legal maximum.
Amazon’s Hobart data center project page says backup generators run an average of less than 12 hours per year, mostly for testing. That statement describes Amazon’s operating experience or expectation; it does not replace the federal runtime categories. Genuine emergency use has no federal hourly ceiling, while maintenance and testing generally fall within a 100-hour allowance that includes a restricted 50-hour non-emergency subset.
This is an Amazon projection presented in the webinar.
Amazon said the campus is expected to average 14 million gallons annually and use outside-air cooling about 98% of the year. The webinar did not provide the underlying hydraulic model or an independently reviewed operating record, so the figures should remain labeled as company projections until supporting records are published.
The low-50s figure is a modeled design target, not a measured result.
Amazon’s acoustical consultant said the site was designed for low-50-decibel sound at the property line under conservative summer assumptions. Hobart’s adopted ordinance establishes a 65-decibel property-line maximum, but the webinar did not publish the complete Hobart acoustical model, receiver assumptions or post-construction measurements.
No specific independent Hobart health study was identified.
During the Q&A, the moderator asked about independent environmental and health studies. The response described Amazon’s assessments, permitting, monitoring and agency oversight, but it did not name a completed independent Hobart health-impact study. That does not prove harm; it identifies an evidence gap.
Help keep the record current
Send the claim or application page, your supporting source and a short explanation. Corrections are reviewed before publication.