Fieros. I know I'm going to be sorry... but one last time, I'm going to weigh in on this subject. (Having been the first to throw the BS flag a month or two back when this first came up.)
And FWIW, I've owned a few Fieros myself, so I'm not shooting in the dark. Here's the chain of events involved in
legally changing the brakes on an '84-87 Fiero to those from an '88... which was the only reason for putting the early and late cars on the same spec line, right? If someone finds a hole in this sequence, I'll gladly step back, but I believe the following is 100% correct.
- The brakes from the '88 won't bolt to the early front suspension without
modification of the calipers or suspension upright, or both. The '88 suspension assembly was a complete redesign with zero parts commonality to the early cars; including the hubs, the rotors, the calipers, the uprights, the a-arms, and even the suspension pickup points.
- Okay then, let's change the entire front suspension assembly, crossmember and all. Oops! The '88 spaceframe was changed to accomodate the new crossmember, so to stay legal (no modifications, remember?) we'll have to literally cut (this is NOT a bolt-on subframe) the entire front end off an '88 and weld it to our '87. Now there... that didn't take long, did it?
- Uh-oh. We've now got our vented brakes and better calipers on the front end, but we've just "...created a model", because the back end of the car is still carrying the '87 engine cradle, suspension, and brakes. But Hey! We've got this '88 cradle laying around, which includes the struts and brakes, and...
- Oh, no! You guessed 'er, Chester... they changed the rear spaceframe components as well (with
relocated strut towers, among other things), so the only way to keep the car IT legal is to cut the entire rear end off an '88, etc, etc.
Yessir... combining these two cars onto the same spec line makes all kinds of sense.
As I said back in July, this is bad precedent, as
they really are two different cars from an IT ruleset perspective. And this has nothing to do with any alleged performance enhancing combinations that may or may not be possible. IMO (and it's just that... an opinion) there is just a lot of potential here, unintentional as it may be, to create an IT compliance monster that will negatively influence other classification decisions over the long haul.