Connect with us

Indianapolis, IN

East Indy data center faces resident backlash as plan is delayed

Published

on

East Indy data center faces resident backlash as plan is delayed


If there’s one topic that can compel multiple people to shout an expletive into a microphone in a church sanctuary, it’s data centers.

Company executives from Atlanta-based DC BLOX, the latest developer looking to build a data center campus in Indianapolis, made their pitch on April 27 at Downey Avenue Christian Church in Irvington, the east-side neighborhood near which three proposed facilities would sit. The sanctuary was packed with close to 200 people, including residents who came to speak vehemently against the idea, union laborers who showed up to support it and many more who came to listen.

“It’s not popular to be in the data center business right now. It’s really popular to go online, on social media especially, and hate on data centers,” DC BLOX Senior Vice President of Sales David Armistead said to the room before public comment. “But what I will tell you is not all data centers are the same, and not all data center companies are the same. And if there’s a data center that was irresponsible and they’re getting a lot of hate, then that’s well-deserved.”

Advertisement

Armistead’s remarks did little to comfort residents who criticized the plan for several reasons, among them: the company’s intention to seek tax breaks; the air and noise pollution more than three dozen backup diesel generators could cause; and the data centers’ proposed location just south of Irvington Community Elementary School.

“I think you should pay your fair share of taxes, just like every small business in the community pays taxes from the day they open their door,” William Moser, an east-side resident, told the company leaders.

While most kept their comments civil, one woman told the DC BLOX representatives that “every single one of you are disgusting.”

Before the meeting, the company decided to postpone its May hearing before the Metropolitan Development Commission hearing examiner to take more time to gather feedback. The use variance request required for the data center — which needs final approval by the full MDC but not the Indianapolis City-County Council — is now set for an initial hearing June 11.

Advertisement

What to know about DC BLOX data center

DC BLOX wants to build a data center campus with three buildings encompassing more than 400,000 square feet in an industrial park just east of Irvington, at 305 Fintail Drive. The company aims to complete the initial facility, the smallest at 80,000 square feet, within two years of city approval and the two larger buildings by 2030.

All told, Armistead said, the three facilities would cost upward of $2 billion to build and use close to 80 megawatts of energy — enough to power tens of thousands of homes. DC BLOX says the data center will employ 35 “high-wage” permanent staffers and up to 600 construction workers during the buildout.

The buildings would sit on part of a 150-acre site where a longstanding Ford automotive parts factory operated until 2007. After the plant was demolished, the site rebranded as the Thunderbird Commerce Center in 2021 to attract logistics and manufacturing firms.

Advertisement

The site’s anchor business is beverage retailer and distributor Monarch Distributing, which moved into a roughly 500,000-square-foot facility in 2024. The data center buildings would be just north of where Monarch sits, closer to the Pennsy Trail.

How DC BLOX deals with energy, pollution concerns

The company’s proposal aims to mitigate some of the common fears about data centers, particularly related to energy use.

For one, the facilities won’t initially be used to power artificial intelligence, the force driving much of the data center boom. DC BLOX says it will house data for regional network communications and local clients like banks, hospitals, universities and governments.

What’s more, the first building will cool computer equipment with a waterless system similar to those big-box stores use. The next two facilities would use a closed-loop system, a less water-intensive method that will pull water only from municipal provider Citizens Energy Group — not from natural aquifers.

In case of rare emergencies or mechanical issues, the company says it will dispose of leaking water in line with state regulations and not flush it into the city’s wastewater system.

Advertisement

DC BLOX also says it will pay for all costs associated with a new electricity substation that could be needed to power the three facilities. The company cites an AES Indiana statement that promises new data centers will cause “no negative impact to existing customer rates” because AES will be able to spread out new infrastructure costs over a larger amount of electricity sold.

Armistead said Monday night that although DC BLOX would not be legally bound by proposed city regulations on data centers that could take effect this summer, the company plans to adhere to most of them anyways. DC BLOX also won’t sign non-disclosure agreements as part of its negotiations, representatives said.

“I see this as a way to extend technology into an area where it hasn’t existed before,” Armistead said, “to allow the community to participate in this high, high- growth sector of our U.S. economy.”

The company says it aims to host another community forum in City-County Council District 20, where the data center is technically located, in the coming weeks. Irvington sits just to the west in District 14.

District 20 Councilor Michael-Paul Hart, whose opposition helped to kill a Google data center in his district last fall, told IndyStar in an April 22 phone interview he remains “neutral” on the DC BLOX proposal.

Advertisement

He said residents should “take the time to show up and make sure that they’re getting all questions asked and answered.”

“Anything we want in a commitment is still completely plausible, because it still takes a vote, and that’s from the MDC,” Hart said. “So if there are valid points that need to be made, there are still members of that body who are going to listen and can approve these things. And that’s where the convincing has to happen.”

Email Indianapolis City Hall Reporter Jordan Smith at JTSmith@indystar.com. Follow him on X @jordantsmith09 and Bluesky @jordanaccidentally.bsky.social.





Source link

Advertisement

Indianapolis, IN

Amazing Unsers: The Family That Made Indianapolis History | Heroes Of The 500

Published

on

Amazing Unsers: The Family That Made Indianapolis History | Heroes Of The 500


Amazing Unsers: The Family That Made Indianapolis History | Heroes Of The 500

At the Indianapolis 500, some winners become legends.

The Unsers became a dynasty.

Their family story at Indy began in 1958, when Jerry Unser became the first of the clan to qualify for the 500.

It was an early sign of what was to come, but also a reminder of racing’s danger and cost.

Advertisement

The Unser name would rise with glory, but it would always carry grief, sacrifice, and the weight of expectation.

Bobby Unser pushed the family legacy forward with his 1968 Indianapolis 500 victory, a bold and defining win that helped plant the Unsers firmly in Speedway history.

Then Al Unser took that standard even higher. His wins in 1970 and 1971 showed rare control, speed, and consistency, and helped turn the family’s success into something larger than a hot streak.

It became tradition.

RELATED | Heroes Of The 500

Advertisement

EXTERNAL | Unser Family Created Unmatched Legacy of Speed, Success at Indy

By the time Al Unser Jr. won the 1992 Indianapolis 500, the moment felt bigger than one race.

His emotional triumph made him the first second-generation driver to win Indy, connecting father and son in one of the event’s most meaningful chapters.

The family’s nine total victories across four decades remain one of the most powerful records in race history.

For the Unsers, Indy was never just a track.

Advertisement

It was pride, pain, and family.



Source link

Advertisement
Continue Reading

Indianapolis, IN

Alexander Rossi suffered injuries to his finger, ankle in crash; what it means for Indy 500

Published

on

Alexander Rossi suffered injuries to his finger, ankle in crash; what it means for Indy 500


play

Alexander Rossi underwent procedures on his right ankle and a finger on his left hand following a crash during Monday’s Indianapolis 500 practice at Indianapolis Motor Speedway, Ed Carpenter Racing announced Monday night.

Rossi, who is slated to start second in Sunday’s Indy 500, crashed into the wall in Turn 2 at practice after losing control of his No. 20 Ed Carpenter Racing Chevrolet. After slamming into the wall, Rossi’s car made contact with Pato O’Ward’s No. 5 Arrow McLaren Chevrolet and Dale Coyne Racing’s Romain Grosjean crashed while trying to avoid the incident. O’Ward and Grosjean were released from the IMS infield medical center. Conor Daly’s car also suffered damage in the crash.

Advertisement

After spending more than 90 minutes inside the medical center, Rossi was transported to a local hospital for further evaluation, eventually leading to the procedures. Per ECR, Rossi will be evaluated throughout the week with “the full intent of participating in the final practice on Friday, May 22 and the 110th running of the Indianapolis 500 on Sunday, May 24.

ECR will move to a backup car for Rossi’s entry, which will not cost the entry its spot on the starting grid. If Rossi is unable to drive the car Sunday, the entry will move to 31st on the grid, starting ahead of Caio Collet and Jack Harvey, whose cars failed post-qualifying technical inspections for illegal Energy Management System (EMS) covers.

If Rossi doesn’t recover in time for the race, ECR must find an IndyCar-approved replacement. ECR’s reserve driver is Hunter McElrea, who has only driven in one IndyCar race, on the streets of Toronto in 2024. McElrea would be an Indy 500 rookie who hasn’t gone through the Rookie Orientation Program (ROP), which the four Indy 500 rookies in this year’s field completed at the Indy 500 open test in late April. Rule 4.3.2.9.8 would require McElrea to go through an ROP but IndyCar could allow him to do one this week. It seems unlikely, however, that IndyCar would approve a rookie who hasn’t been on an oval in an Indy car if Rossi were not available.

ECR could turn to veterans who have been in the Indy 500 recently but don’t have a seat this year if Rossi doesn’t recover. Notable drivers from last year’s Indy 500 who aren’t in this year’s race include Devlin DeFrancesco, Robert Shwartzman, Callum Ilott and Marco Andretti. Per IndyCar Rule 4.3.2.9.7, Andretti — who retired after last year’s race — would need to complete a refresher test, but the other three drivers wouldn’t because they have driven on an IndyCar oval since last year’s Indy 500. Ilott has been at IMS throughout the month, including Monday, however a source tells IndyStar that Ilott’s team, Prema Racing, would need to grant him permission to drive for another team while Prema’s IndyCar program is on pause.

Advertisement

Rossi will look to heal in the next six days and be on track for the Indy 500. Rossi is a decade removed from winning the Indy 500 as a rookie in 2016, and should he drive and start on the front row, he could be in contention for his second victory.

Zion Brown is IndyStar’s motorsports reporter. Follow him at @z10nbr0wn. Get IndyStar’s motor sports coverage sent directly to your inbox with our Motor Sports newsletter. Subscribe to the YouTube channel IndyStar TV: IndyCar for a behind-the-scenes look at IndyCar and expert analysis.



Source link

Advertisement
Continue Reading

Indianapolis, IN

Indianapolis 500 Qualifying Sees Former Winner on Pole

Published

on

Indianapolis 500 Qualifying Sees Former Winner on Pole


Indianapolis 500 Qualifying is generally an entire weekend affair. If teams are lucky, they run both Saturday and Sunday. If unlucky, they will wait to run again in later practice sessions, tethered to their positions behind the first 4 rows.

This year, however, after changing the qualifying format the first time, Saturday ended before it even began. The first day of qualifying was rained out, leaving the 33-car grid to run 3 sessions to set the grid on Sunday. The new Top 15 qualifying format – scrapped.

The new Indy 500 Qualifying Format resembled that of a road or street course track on the IndyCar calendar. All 33 drivers ran one at a time, banking their 4-lap average. This was followed by the Top 12 and Fast 6.

Advertisement

Ultimately, Alex Palou achieved his second Indianapolis 500 Pole Position alongside former Indy 500 winner, Alexander Rossi and Penske’s David Malukas.

First Session Qualifying Results

The first session saw all 33 cars race for the fastest 4-lap average speed – a session that went without incident on a very hot, sunny day in Indianapolis. This session set grid positions 13-33 prior to the two sessions that will set the front of the grid.

Advertisement

Josef Newgarden Indy 500 Qualifying | Via Penske Entertainment, Joe Skibinski

There were a few interesting trends coming out of the first session of the day. First, and most notably, is that no other car on the grid could hold a candle to the average speed of Meyer Shank Racing’s Felix Rosenqvist, who set a 232.599 average.

On the other side of the coin, Penske’s Josef Newgarden (two-time winner), and all three Andretti cars – Kyle Kirkwood (2nd in 2026 Championship), Marcus Ericsson (former winner), and Will Power (former winner) – all did not make the Top 12. Both of Newgarden’s teammates made the Top 12, with Newgarden over 1mph off their pace.

Position

Driver / Team

Advertisement

Avg. Speed

13.

Sato/ RLL

230.995

14.

Advertisement

Carpenter/ ECR

230.829

15.

Castroneves/ Meyer Shank

230.811

Advertisement

16.

Rasmussen/ ECR

230.705

17.

Armstrong/ Meyer Shank

Advertisement

230.701

18.

Ericsson/ Andretti

230.667

19.

Advertisement

Lundgaard/ McLaren

230.661

20.

Power/ Andretti

230.279

Advertisement

21.

Siegel/ McLaren

230.213

22.

Foster/ RLL

Advertisement

230.212

23.

Hunter-Reay/ McLaren

230.202

24.

Advertisement

Newgarden/ Penske

230.165

25.

Grosjean/ Dale Coyne

229.791

Advertisement

26.

Kirkwood/ Andretti

229.607

27.

Legge/ HMD – AJ Foyt

Advertisement

229.456

28.

Schumacher/ RLL

229.450

29.

Advertisement

Harvey/ Dreyer Reinbold

229.207

30.

Rahal/ RLL

229.017

Advertisement

31.

Hauger/ Dale Coyne

228.982

32.

Abel/ Abel

Advertisement

228.169

33.

Robb/ Juncos

226.572

Advertisement

Top 12 Qualifying Results

During one of the hottest parts of the day, the Top 12 drivers went out with one question in mind – could any driver touch the speeds that Felix Rosenqvist put in earlier today? And could Felix Rosenqvist replicate his results?

Advertisement

Felix Rosenqvist Meyer Shank Racing Indianapolis 500 Qualifying | via Penske Entertainment, Joe Skibinski

The answer in this session was a ‘yes’ and ‘no’. Rosenqvist again topped the session with significant performance drop offs plaguing drivers like Veekay over the course of their 4-lap averages.

Advertisement

Position

Driver / Team

Avg. Speed

7.

Advertisement

Simpson/ Chip Ganassi

230.883

8.

Daly/ Dreyer Reinbold

230.712

Advertisement

9.

McLaughlin/ Penske

230.577

10.

Collet / AJ Foyt

Advertisement

230.539

11.

Dixon / Chip Ganassi

230.347

12.

Advertisement

Veekay/ Juncos

229.585

Daly and McLaughlin, both favorites for pole, fell at this hurdle and will start together on Row 3. They are still ones to watch next weekend during the race.

Advertisement

Fast 6 Qualifying Results

Straight out of the gates, ECR’s Rossi – a former Indianapolis 500 winner exactly one decade ago – set the fastest 4-lap average significantly faster than his speed in the prior two sessions.

Advertisement

Alexander Rossi ECR Indianapolis 500 Practice | via Penske Entertainment, Amber Pietz

Advertisement

However, the biggest disappointment of the session was Felix Rosenqvist, who was significantly faster in the prior two sessions, coming in 4th, approximately one mph slower than the full grid and Top 12 sessions.

Position

Driver/ Team

Avg. Speed

Advertisement

1.

Palou / Chip Ganassi

232.248

2.

Rossi / ECR

Advertisement

231.990

3.

Malukas / Penske

231.877

4.

Advertisement

Rosenqvist / Meyer Shank

231.375

5.

Ferucci / AJ Foyt

230.846

Advertisement

6.

O’Ward / McLaren

230.442

Advertisement

When the ‘floodgates’ opened for Palou, he put out one of the fastest laps of the day, followed by precise consistency that he is known for. The pole-to-win conversion rate is currently ~20%, so the odds are stacked against Palou. As the reigning Indianapolis 500 champion, the only question on people’s minds is if Palou can two-peat… and Palou thinks he can.

Add us as a preferred source on Google



Source link

Continue Reading
Advertisement

Trending