• Blog Entries

    • By Destino in ES Coverage
         1
      Good afternoon Redskins fans!  I have once again been invited to sit in the relative comfort of the press box and shout my thoughts into the void via this blog.  As you watch the game today and see the rain  pour relentlessly from the heavens, know that I am safe and dry.  Know also that @Spaceman Spiff is out there somewhere, cold and unappreciated, rolling around in the muck trying to capture that perfect picture.  Maybe say a little prayer for his health (or laugh, whatever, I’m not judging you).  Also, be sure not to miss the pictures he posts on this site after each game.     
       
      Before we get into today's Redskins game, I want give some thanks for more positive occurrences in DC sports.  Congrats to the Washington Mystics for winning their first championship.  Congrats go out to the Washington Nationals as well for reaching the world series.  These two teams (along with the Caps) are working hard to change the sports related mood around this town, and we're all happier for it. 
       
      Lets move now into less cheerful topics, namely your Washington Redskins!  Yow know things are going bad, and I mean really dang bad, when your team has gone through three quarterbacks and two coaches and your not even half way through the season.  Today's fresh hell comes in the form of a specter of the our recent past coming to smirk at our misfortune.  Im talking of course of Kyle.  Kyle's spent the week assuring everyone that he isn’t holding a grudge, while very obviously holding a grudge.  “Everything else.”  You know what I’m talking about. 
       
      If all he brought to town were his hurt feelings we wouldn’t have a problem.  Sadly, he’s arrived with an undefeated football team that the NFL says we have to play this week.  This feels entirely unfair. 
       
      My generic key to the game:  Run the ball and stop the run.  The team (spoiler alert: 49ers) that does this today will win.   
       
      Redskins Inactives  
      QB Colt McCoy  
      S Deshazor Everett  
      CB Josh Norman  
      RB Chris THompson  
      LB Josh Harvey-Clemons 
      G Wes Martin  
      TE Vernon Davis  
       
      49ers inactives  
      QB CJ Beathard 
      WR Deebo Samuel  
      CB Ahkello Witherspoon  
      FB Kyle Juszczyk 
      T Mike McGLinchey 
      T Joe Staley 
      DL DJ Jones 
       
      1st Quarter Update
      Redskins 0 – 0 49ers
       
      Callahan wasn’t playing around when he said he wanted to run the ball.  That first drive was all runs, and looked great... right up until they tried to pass the ball.  Hopkins missed the relatively short fied goal, because of course he did.     

      Maybe Quinn isn’t a good choice to be returning punts?  Consider it.    
       
      That second Redskins drive looked more like what we’ve come to expect from this offense.  Run for negative yards, pass dropped, and an unsuccessful screen pass.  A quintessential Redskins three and out. 

      Passing yards this quarter:  Redskins 3. 49ers 9.  Are you not entertained?! 
       
      Half Time Update
      Redskins 0 – 0 49ers 
       
      How happy are you to spend your Sunday afternoon watching this game?  Consider that some people paid money, to sit in a poncho, in the rain, to watch this game. 
       
      It’s now time for those half time adjustments that our beloved skins do so well.  It’s unlikely the second half mirrors the first. 
       
      3rd Quarter Update 
      Redskins 0 – 3 49ers  
       
      Good news, this game will not end in a 0-0 tie.  Those half time adjustments have kicked in as expected and the 49ers have found a way onto the scoreboard in this messy throwback game.  The Redskins have decided to spend the second half collecting holding penalties and sadness.  Mercifully, only one quarter remains. 
       
      End of Game Update 
      Redskins 0 – 9 49ers 
       
      Callahan hasn’t spent much time as the head coach of the Washington Redskins, but he’s already proven that his team can waste 2nd half timeouts like a veteran.  It makes little sense to adopt a strategy that shortens the game when your team is losing, and it makes even less sense when your team is short on time outs.  I’m not really sure what the thinking as late in this game.    
       
      Next week Kirk Cousins!   
       
       

Archived

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

Mark The Homer

Engine Turning the Wrong Way -- Counter-Clockwise

Recommended Posts

lol

I don't know. If I was reading this thread, I'd probably doubt it too. All I know is what happened. I was there. I saw it. I heard it.

If

a) the truck is moving forwards with

B) the tires turning forward and

c) the clutch pedal is completely out and

d) the transmission is in reverse,

I don't see any other possibility except the engine's crank was turning in the opposite direction -- unless the clutch plate was shot. But it's new and perfect.

So, if we agree with that, plus I tell you the ignition was on, AND the pistons were firing (and I know this because I heard them), then the engine running. Granted, it was being forced to run as I went down the hill, but I heard the engine, and it was running, and not all that badly. No backfires, no violent or even mild shaking or shuddering. It sounded a little differenet, a little odd, but that is all.

Then, when I reached the bottom of the hill and disengaged the clutch, the engine shuddered mildly, and the RPMs (as I listened) slowed down. And then it stopped after about 10 seconds or so. To me, that counts as "running." It wasn't running well, but it was running.

Upon restart, it ran MUCH better, and did not stall. But there was a new hiss which I didn't hear seconds earlier.

Impossible or not, there is absolutely no doubt in my mind that the engine ran backwards. I was there.

Share this post


Link to post
Share on other sites

my feeling is that chomerics is both right and wrong at the same time. I believe he's right that the engine won't run backwards, meaning it won't fire and idle correctly. What I imagine happened is that the weight of the car on the hill overpowered the push of the gear since it sounds like you weren't hitting the gas pedal (same as how a car on a hill in gear without the parking brake on can roll away). In that case, the engine would be spinning backwards, yes, but not running backwards. It's the same idea as pop starting a car that won't start. If you pop start a car that has no spark, it'll seem like the engine is running for a short time, but it's running because the wheels are turning the tranny and the tranny is turning the engine.

What I imagine happened is that, by easing the clutch out in reverse thinking you were in first, gravity overpowered the clutch and tranny and took you down the hill in gear. The engine may have burned off some residual fuel in the meantime as the crank was still turning so the spark plugs would have still fired, but that doesn't mean it was running per se. In this case, I think the transmission was driving the engine instead of the other way around. It died when you came to a stop because the transmission was no longer turning the crankshaft.

Share this post


Link to post
Share on other sites
I thought they only did that in the Southern Hemisphere.

I think water going down a drain does that in the Southern Hemisphere...not an engine.

Share this post


Link to post
Share on other sites
I think water going down a drain does that in the Southern Hemisphere...not an engine.
Hmm ... but have you considered the fact that Australians drive on the left side of the road?

As far as the original subject of the post, I think DCsportsfan nailed it - the engine may have been turning backwards, but it wasn't "running" backwards. The wheels were turning the camshaft backwards, so the spark plugs would still fire and the fuel would still go into the engine (with the air running the wrong way) so it might feel like it was running, but the engine wasn't really "running" because there's no way it could keep itself going with the timing completely wrong.

Share this post


Link to post
Share on other sites
As far as the original subject of the post, I think DCsportsfan nailed it -
Yes. I think so.

The only thing to add or remind is, the ten seconds after I reached the bottom of the hill and disengaged the clutch:

The engine was running on its own -- backwards. < --- that's really what I'm talking about in this thread.

Share this post


Link to post
Share on other sites
my feeling is that chomerics is both right and wrong at the same time. I believe he's right that the engine won't run backwards, meaning it won't fire and idle correctly. What I imagine happened is that the weight of the car on the hill overpowered the push of the gear since it sounds like you weren't hitting the gas pedal (same as how a car on a hill in gear without the parking brake on can roll away). In that case, the engine would be spinning backwards, yes, but not running backwards. It's the same idea as pop starting a car that won't start. If you pop start a car that has no spark, it'll seem like the engine is running for a short time, but it's running because the wheels are turning the tranny and the tranny is turning the engine.

What I imagine happened is that, by easing the clutch out in reverse thinking you were in first, gravity overpowered the clutch and tranny and took you down the hill in gear. The engine may have burned off some residual fuel in the meantime as the crank was still turning so the spark plugs would have still fired, but that doesn't mean it was running per se. In this case, I think the transmission was driving the engine instead of the other way around. It died when you came to a stop because the transmission was no longer turning the crankshaft.

Actually, it looks like you got it. I can buy the engine firing a few times in reverse due to residual fuel in the cylinder, and also running backwards. I can't agree that the engine will run in reverse, but I will buy that it will fire a few times and buck the car. . .which is what appeared to happen. Not having been there, it is hard to tell what happened from a description, but I believe it happened like you said, it makes perfect sense. :)

Share this post


Link to post
Share on other sites

I have a question about the whole thing, as I don't know anything about engines -

Nearly every Sunday, I hear Darrell Waltrip, when describing a NASCAR racer who has turned the car around, wonder aloud whether or not he "spun that engine backwards." Is that a mistaken description, or is it a mechanical possibility?

If DW's statement is accurate -

1: Mark's event is totally possible in the way described. The difference between the two situations is minimal: one is geared forward traveling backwards, one is geared backwards traveling forwards. The theory should apply across both situations.

2: The vehicle should be able to run for a very short period of time until it stalled, as is proven by in-car recordings during the races. I imagine this would be because there would be residual fuel and air left over by the time the next spark in the now backwards series came around, but that's just a guess.

Share this post


Link to post
Share on other sites
I have a question about the whole thing, as I don't know anything about engines -

Nearly every Sunday, I hear Darrell Waltrip, when describing a NASCAR racer who has turned the car around, wonder aloud whether or not he "spun that engine backwards." Is that a mistaken description, or is it a mechanical possibility?

I believe he just meens the car wasn't running to well, but he now has it turned around and is performing the way he needs it too.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.