Jump to content

Bad Luck; Nuked Driveshaft = Cut Fuel Lines

Blue15

Recommended Posts

Blue15 Enthusiast

Blue15

Posted
Posted

Hell of a first post. Anybody ever had this happen? I get a reward right lol? 

 

Well, I got to going too fast and my driveshaft decided to grenade itself. Had no freaking clue this was a thing. (Definitely not the first looking online.) I always thought the driveshaft looked beefy. Turns out, it's a damn 6ft long beer can :fume:. Well, in the process of when that happened, some freaking how, the back half of the driveshaft reached up, bent the protective fuel tank shield down, and perfectly sliced my fuel supply lines. Looks like they were cut with clippers. Carnage pics below.

 

Does anybody have access to a drawing/schematic of the fuel lines around the tank with part numbers? I'm a 2015 Silvy LT Double Cab with 5.3. I'm coming up empty online. There's definitely 2 lines running on top of the tank that are cut. I'm hoping they are not too long and have some disconnects nearby where I can just swap in a new line. If it's a super long line, might be towing to the dealer to fix. I've got a new 2 piece steel driveshaft from Performance Driveline on order so this doesn't happen again :driving:, but gonna wait till that gets here before I start unbolting stuff. May just take the bed off the truck and inspect everything. 

 

82VBb2Bl.jpg

 

LVdzClhl.jpg

 

vkszXzel.jpg

Arch Angel Enthusiast

Arch Angel

Posted
Posted

Yah damn what was it speeds lol I've had my 17 up to over 95 mph and no issues

Sent from my Pixel 2 XL using Tapatalk

1SLOW1500 Senior Enthusiast

1SLOW1500

Posted
Posted

Very common. Speed in mph and shaft speed will kill them. Very thin. Anyways you are lucky could have been worse. Damaged bed and cut into the tank. Anyhow the past on the fuel are cheap. And now for the hard part. 

Dive shaft you can get stronger ones but there are pros and cons. Best one is the small diameter 2 piece shaft. It will have a bolt in or weld in crossmember. It will allow for lifts and lowered truck. Rated at 600+ hp and better with ribration issues. Enjoy

aseibel Senior Enthusiast

aseibel

Posted
Posted

please post your gear ratio and ground speed when this happened so we can show this thread to others when they want to remove the speed limiter in their trucks.

Bikemobile Enthusiast

Bikemobile

Posted
Posted

Interesting, police package tahoe is limited at 120 mph. I’ve ran it 120 for a few miles without a problem. I wonder what the difference is. 

Blue15 Enthusiast

Blue15

Posted
  • Author
Posted
4 hours ago, aseibel said:

please post your gear ratio and ground speed when this happened so we can show this thread to others when they want to remove the speed limiter in their trucks.

3.42 gears, was in the 95 - 100 range. (I do have the speed limiter turned off.) Starting vibrating like crazy, let off... boom. I thought my damn exhaust had come undone. Yeah, not quite :sigh:

 

I have no way to prove this, but a week or 2 ago, I ran over something big and metal (looked like a big metal door almost) in the dark on the way home. Tons of construction where I live so God knows what it was. Super loud though, I just assumed it hit my Corsa muffler. Got under the truck to check and everything was fine, but I didn't really think to inspect the driveshaft. And if there was damage, it could have been spun where it was on top and wouldn't have seen it anyway. So again, no way to prove since it's trashed now, but this was the first time I drove the truck at high speeds since then. I just wonder if there was damage/crack and it broke loose. I have 2 other high powered LS cars so I kinda forget to slow down when I'm in the truck. 

 

So anybody got the 411 on those fuel line part numbers? I may be swinging by the dealer tomorrow to see if they can pull something up. Thanks!

jackgraves Enthusiast

jackgraves

Posted
Posted

Stock Driveshafts are Junk. Especially if you mod your truck with Cam and stall converter and Gears. You can't even run it on the Dyno safely and get true HP rating because you usually need to be at 125+MPH. Stock Driveshaft critical speed is 105-110. If you keep pushing stock Driveshafts past this sooner or later that weak piece of S..T is gonna GRENADE 

Gagliano7 Enthusiast

Gagliano7

Posted
Posted

I wish i could see pics but i am restricted at the moment. When i was searching for e-85 conversion there was a thread with fuel lines. I will see if i could find it.

KARNUT Senior Enthusiast

KARNUT

Posted
Posted

I just read an interesting article in msn. Top 50 speeding tickets in Texas. The usual suspects and surprisingly amount of motorcycles. In the top ten at 150 mph a 2013 f-150. Way down was a 2008 Chevy at 137. I guess ford doesn’t have the exploding drive shaft. I’ve been fast west of San Antonio on interstate 10. Can’t imagine hanging on to a truck going that fast.


Sent from my iPhone using Tapatalk

300 Blackout Enthusiast

300 Blackout

Posted
Posted

Do you have a 2wd truck? If so your driveshaft is a bit longer (less stable). Perhaps it was damaged last week. I replaced mine as preventative maintenance with a 5” diameter 1/8” thick aluminum one. Still have the stock one in my garage. Your two piece should solve the problem. Not sure how to fix the gas lines but I’m hopeful it won’t be too hard for you.

Can you look into the severed ends of your driveshaft and let me know if there is cardboard sandwiched between two layers of aluminum? I’ve seen other photos of this type of construction but can’t see any cardboard in your photos. Good luck with the repair, glad you weren’t hurt.

  • 4 months later...
triplexbullies Enthusiast

triplexbullies

Posted
Posted

My 2018 driveshaft pops every time there is a change in the torque. GM replaced it once and it still pops. The service manager says it's that there are several beer cans going on. The main shaft has sleeves pressed in to each end and welded. He says it's the sleeves moving inside of the main shaft, yet, they're welded... I am waiting on mine to grenade before GM decides what to do with it.

 

Also according to my service manager the HDs have the cardboard in them to reduce noise. 

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...