2011 ahfs

[Kent Hanley]

Originally Posted by JRyan

Kent,

I have a question. How can they not refactor altitude runs back to sea level for a horsepower adjustment but then do it for the record?

At a track like Denver you're talking about almost a full tenth difference in some cases. That's an absolute load of BS.
In my ss/na car my Denver index is a 13.10 from a 12.15 sea level index. If I run an 11.89 at Denver you're saying I'd automatically get factored because I'm 1.21 under. But, that only corrects back to an 11.019. That's only 1.121 under not even close to the automatic hit. I'm sorry. That's complete garbage.

Where else in the country is anyone else going to get factored for going 1.12 under the sea level index? The answer, their not! If their going to base hp off the index then I guess you should get the record off the index as well. If not they need to be refactored back to sea level the way the should be.

Rick

Rick ,

I am not saying its right but the old ahfs use to have a sentence or 2 in it saying something like " if you run quicker then 1.40 ( that was the old automatic trigger ) under the sea level index you will be automaticaly factored" it happened to Frank Grossi in gt/aa at Vegas, i think last year when he ran in the 8's.

The ahfs rule that has been in place for the past few months nor does the new proposed ahfs rule have that sentence in it. Plus i heard at vegas this year they hit several combos that ran quicker than 1.25 under the local index. They did retract them later becuase nhra added a sentence that says something like nhra has final decision..

If you re-read the original post it sure doenst say anthing about seperating or recalculating altitude adjusted tracks back to sea level indexes like the old ahfs use too. No one has confirmed this but it sure seemed that is what they are doing. Seeing how we dont see what runs flag a combination we really dont know.

kent