Wednesday, August 8, 2012

My Revised 2013 Indycar Schedule Prediction

With time comes new information on tracks that will/won't be on the 2013 Indycar Schedule. With that in my mind, I decided to revisit my last schedule. I made some edits, and here is what I came up with (orange = confirmed race, red = confirmed date):

3-31 St Petersburg
4-7 Barber
4-21 Long Beach
4-28 Sao Paulo
5-26 Indianapolis
6-2 Belle Isle
6-9 Pocono
6-15 Milwaukee
6-22 Iowa
7-7 Toronto
7-14 Edmonton
7-28 Vancouver
8-11 Sonoma
8-18 Fontana
9-1 Baltimore
9-8 Mid-Ohio
9-22 Michigan (MIS)
9-28 Texas (TMS)
10-6 Houston


So, lets address some things after looking at my schedule:

1) The Canadian Triple Crown is there, with Toronto, Edmonton, and Vancouver as the three races in Canada. Having some kind of triple crown would be nice to see.

2) I hope Indycar can work something out to have two races in Michigan. It may dilute the market, but it's not like Belle Isle draws 150K people, only a fair 30K attend Belle Isle. You could manage to hold both races in my opinion.

3) Pocono should be spectacular if it gets on the schedule! Fast and flat, a perfect Indycar track.


4) No Phoenix? I don't think a date early in Indycar's season would work for Phoenix based off of the fact Nascar has a race there in March. And it just doesn't fit anywhere in the ladder half of the schedule.

5) I just do not see how it is possible to get close to a 50-50 split between ovals and road courses. There are too many road courses that want to host Indycar and not enough realistic options for ovals.

6) The most important part of the schedule (other than the 500) would be the bringing back of the old Triple Crown of Indianapolis, Pocono, and Michigan.

Have an opinion? Let me hear your thoughts.

-Matthew Hickey

1 comment:

  1. I know they are still out of the question due to the fear-mongering after Dan left us, but Kentucky, Kanas, and Chicagoland are still viable oval options. Drop the shitty street circuits like Baltimore, St. Pete and Belle Isle, and add them in.

    ReplyDelete