Jump to content

Harvick WINS!!

Kansas Kid

By Kansas Kid
in The Off-Topic Bar

Recommended Posts

Zane Senior Enthusiast

Zane

Posted
Posted

Man, its really amazing. Look at these statistics.

Since Dale Sr's passing every race has been at caution at lap 3.

Kevin Harvick won on his 3'rd Winston cup race

3 drivers related to dale Sr have won this year so far

Neat huh?

Heres the race cap from Nascar.com

Harvick scores emotional, historic victory over Gordon

By Marty Smith, Turner Sports Interactive

March 11, 2001

5:32 PM EST (2232 GMT)

 

HAMPTON, Ga. -- It was only fitting that rookie Kevin Harvick won his first NASCAR Winston Cup Series race on Sunday in the Cracker Barrel 500 at Atlanta Motor Speedway -- it being his third career race and all.

No individual in history has ever won his first race so quickly. Dale Earnhardt wouldn’t have it any other way.

Driving the same car that Earnhardt drove to Victory Lane here in a photo finish last year, Harvick fended off a furious last lap charge by Jeff Gordon to win by a mere six thousandths of a second.

 

Unofficial Results

 

 

 

“I didn’t really know if we could do it because the car was so tight,” said an emotional Harvick in Victory Lane. “I think somebody was watchin’ over us today.”

 

Harvick and Gordon reach the finish line.  

 

 

The win marks Richard Childress’ 70th as a car owner, and somehow, despite all the glorious victories by Earnhardt, this one ranks somewhere up top.

“I just kept praying for Dale to help us out,” said Childress through teary eyes. “He gave us the help we needed.”

Did he ever. Over the final two laps, Harvick was engaged in a five-car, door-to-door, bumper-to-bumper battle with Dale Jarrett, Jerry Nadeau, Dale Earnhardt Jr., and Gordon.

Several times over the final two laps, the pack of cars went three-wide. It was at one of those moments when Harvick made the move that sent him to Victory Lane quicker than any driver in NASCAR’s 52 years.

 

Crew members poured from the pits to congratulate Winston Cup's newest winner.  

 

 

“He made the move that won the race,” said Gordon, who took over the points lead with his runner-up finish. “Harvick was working the bottom but his car was real real tight. I thought me and (Earnhardt Jr.) were going by him at one point.

“Then Jarrett and (Nadeau) got side-by-side and Harvick went right by them on the inside. When he did that, it got jumbled up big time. You had to fill any gap you had and try to take advantage of it. He did that very well.”

Gordon wasn’t so bad himself. He utterly dominated the early portion of the race, stealing the lead from Harvick on lap 18 to lead 118 of the first 150 laps. However, while leading on lap-143, Gordon’s No. 24 Chevrolet ran out of gas, leaving him a lap down.

He was saved a bit, however, when eight cars, including pole-sitter Dale Jarrett, Rusty Wallace and Earnhardt, Jr., were all sent to the end of the longest line for pitting too early. Subsequently, Gordon restarted a lap down in 26th position.

Gordon slowly worked his way up through the field before the motor let go in Mark Martin’s No. 6 Ford, one of three Roush Racing motors to fail on the day. Subsequently, Gordon returned to the lead lap.

From there, he restarted in 13th position and went on to his third top-5 in the first four races.

“There was a higher power watching over us today that wanted to see that outcome,” said Gordon, who now leads the points race by 37 points over Jarrett. “I’m a racer and I want to win, but there’s no team I’d rather finish second to than that one. I’m happy with those results.”

Like his Hendrick Motorsports teammate, Nadeau was quite impressive Sunday. He was mired deep in the field early after getting together with Michael Waltrip on the second lap. That sent him spinning down the frontstretch and into the infield grass. He managed to keep the car out of the wall, and on the strength of solid pit stops worked his way through the field and back into the top-5.

Shortly thereafter, Nadeau was the beneficiary of Dave Blaney’s misfortune. Blaney dominated the middle portion of the event, but a loose lug nut on the left rear tire of his Dodge forced an unscheduled pit stop for new tires. Following the stop, he returned to the race a lap down in 22nd position. It only got worse from there for Blaney.

After Martin’s blown motor forced the day’s fifth caution period with 93 laps remaining, Blaney pitted for tires yet again, only this time when he returned the track the left rear tire fell off, shredding the sheet metal on the left-rear quarter panel of his Dodge. NASCAR impounded the wheel for further inspection.

Nadeau led until the weather began to cool and overcast skies began to form. Jarrett swiped the lead from Nadeau with 60 laps remaining and led until Matt Kenseth hit the wall to bring out the caution. Nadeau passed him back on the restart, and led until Sterling Marlin’s motor let go with 25 laps remaining.

From there, it was time for the shootout. Jarrett was in the lead on the final restart, with Nadeau, Harvick, Earnhardt Jr., and Gordon. What ensued will go down in the history books as one of the most exhilirating finishes in NASCAR history. Sadly, Earnhardt Jr., wasn’t a part of it. He cut a right front tire late in the race to finish 15th.

Even so, he was pleased with the outcome.

“I’m real happy for Richard (Childress),” Earnhardt Jr., said. “It makes me feel good to go home tonight knowing that those guys got a win.”

 

MountaineerTom Senior Enthusiast

MountaineerTom

Posted
Posted

That was awesome!  I was hoping Jr. would win it but I was pulling for Harvick too.  He's impressed me so far, with all the pressure he must be under.  This just tops it off.  Kinda erie how similar the end of the race was compared to last year.

Kansas Kid Senior Enthusiast

Kansas Kid

Posted
  • Author
Posted

I got to admit I was kind of disappointed in the finish.  I thought Jr. had a car good enough to win, and nobody was going to try harder then him.  He is an Earnhardt after all, and you know how bad they want to win.

Guess if it wasn't for bad luck, that guy would have no luck at all....

Bill89 Enthusiast

Bill89

Posted
Posted

I was at the edge of the seat.  Well actually the flor the wife was sleeping on the couch.  Until I woke her to watch the last five and very interesting laps.  As some of you know I am a Gordon fan. Sr. was my second.  I am very plessed with the outcome.  It was a good finish.  If Gordon has to loose, then let it be Harvick.  My wife and I just said when the race started that we wanted Harvick to win one soon.  

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,770
    Total Members
    8,960
    Most Online
    Paul8556
    Newest Member
    Paul8556
    Joined

  • Who's Online   4 Members, 0 Anonymous, 592 Guests (See full list)

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...