Jump to content

Accident today brought me to the forum!


Recommended Posts

Posted

Thanks for opening the thread, I recently purchased my dream truck a mint mint 1 owner crew cab 04 body style z71 1500. Today we had an inch of snow and people were slamming into each other like bumper cars. I was almost home when some 19 year old kid came flying through the intersection and slammed into the rear cab and bed on the passenger side. Was hit with such velocity the truck did a full 180 and ended up facing oncoming traffic. No injuries and the kid didn't say much but sorry I'll call my mommy. The truck faired much better than his little Mazda 6, my question is this: is it possible to have frame damage with this type of collision? The truck is making a weird vibration while in 4wd that wasn't there before. All gaps seem fine and the brunt of the impact was basically the rear axle. What should I make sure the body shop doesn't overlook? Any advice? thanks in advance. post-140381-0-91362100-1425108180_thumb.jpgpost-140381-0-33111900-1425108195_thumb.jpgpost-140381-0-95036600-1425108205_thumb.jpgpost-140381-0-23303100-1425255305_thumb.jpgpost-140381-0-79364400-1425255324_thumb.jpgpost-140381-0-20166000-1425255342_thumb.jpgpost-140381-0-78607800-1425255362_thumb.jpgpost-140381-0-07444000-1425255387_thumb.jpgpost-140381-0-50775200-1425255405_thumb.jpg

post-140381-0-91362100-1425108180_thumb.jpg

post-140381-0-33111900-1425108195_thumb.jpg

post-140381-0-95036600-1425108205_thumb.jpg

post-140381-0-23303100-1425255305_thumb.jpg

post-140381-0-79364400-1425255324_thumb.jpg

post-140381-0-20166000-1425255342_thumb.jpg

post-140381-0-78607800-1425255362_thumb.jpg

post-140381-0-07444000-1425255387_thumb.jpg

post-140381-0-50775200-1425255405_thumb.jpg

post-140381-0-91362100-1425108180_thumb.jpg

post-140381-0-33111900-1425108195_thumb.jpg

post-140381-0-95036600-1425108205_thumb.jpg

post-140381-0-23303100-1425255305_thumb.jpg

post-140381-0-79364400-1425255324_thumb.jpg

post-140381-0-20166000-1425255342_thumb.jpg

post-140381-0-78607800-1425255362_thumb.jpg

post-140381-0-07444000-1425255387_thumb.jpg

post-140381-0-50775200-1425255405_thumb.jpg

post-140381-0-91362100-1425108180_thumb.jpg

post-140381-0-33111900-1425108195_thumb.jpg

post-140381-0-95036600-1425108205_thumb.jpg

post-140381-0-23303100-1425255305_thumb.jpg

post-140381-0-79364400-1425255324_thumb.jpg

post-140381-0-20166000-1425255342_thumb.jpg

post-140381-0-78607800-1425255362_thumb.jpg

post-140381-0-07444000-1425255387_thumb.jpg

post-140381-0-50775200-1425255405_thumb.jpg

Posted

Yes, your drive line could be bent/damaged. Tell the shop. They'll inspect and repair if necessary. The body shop can check frame alignment.

 

You were smart getting pics. Be sure to send them to the ins co.

 

Get yourself checked out too. You may feel fine, but have serious injuries that won't show for days.

Posted

thanks guys, got checked out today had slight bruising but thankfully nothing major. Will have the body shop make sure and check the driveline. Hopefully no frame damage!

Posted

My 2004 was hit on both sides during separate accidents. It pushed the fenders in, but because of the empty space between the fenders and the bed walls, all it did was just bend them. No frame damage. I was rear ended by a guy I knew who was in high school and was stoned. He has some of his dope smoking buddies with him and it was raining. He ended up hitting me with such force that his motor went through his dash board in his '94 Dodge Neon. The bumper was crushed, the bumper brackets were trashed and the bed's mounts were screwed up enough that the bed actually slid into the back of the cab and dented it. He got nailed with all types of tickets and fines on top of the cost to fix my truck.

 

In all of the wrecks it has been in, no frame damage, just body damage. Not sure how fast he was going, but even after getting hit in the rear several times, my '04 was still solid like a rock. So chances are you don't have frame damage, but anything is possible. Post some more pictures of the damaged area.

 

Did the Mazda actually hit your wheel? If so it could have shifted things and therefore they are slightly out of alignment.

Posted

Brandon,

 

Glad you got some justice with the dope kid, this guy was 19 and would seem to be that he was on his phone or something as it really didn't appear that he tried to stop until he was about 10 yards out. By then was too late on a solid sheet of ice. Accidents happen but it was just negligence on his part, literally speeding on ice and not paying attention.

 

As I was moving at about 15-20 mph the majority of the impact was on the wheel...therefore the axle took the hit. The ice probably worked out in minimizing damage as the energy was able to move freely on the slippery surface. Insurance adjuster is coming Monday, I have done research and it looks like I need to appy for a diminishing value claim. This truck was a 1 owner no accidents, now it will have an accident on its record scarying any buyers if I do decide to sell or trade.

 

Attached is some more pictures of the damage.

Archived

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

  • Latest Articles

  • Posts

    • 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. 😄
    • 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
    • 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.
    • 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.
    • 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...