Reply by Robert

  • Advertise with us

Posted on Kickback Incident on Table Saw

View Robert's profile


3533 posts in 1985 days

#1 posted 03-17-2015 11:33 AM

Ocelot – I’ve been doing this a while as I’m sure a lot of others.

1. I know I’ll catch hell for saying this, but I’m going to say it.

Get rid of that thing you called a guard.

The only thing it guards is the company against a lawsuit. IMO its worse than not having one at all. If you had been able to see your work, maybe you could have stopped the cut and avoided the whole thing. My old Xactasaw has a similar piece of junk splitter and I have never used it once from day 1. You need something right behind the blade. Unless you can retrofit a riving knife, use can either make your own or get something like the MicroJig splitter system.

2. You should be using zero clearance inserts. Make or buy several of them. f you go with the Microjig or a homemade splitter you need one anyway, and one for angled cuts, one for a dado blade, etc.

3. Try using a different push stick than what you show. I think push sticks are actually dangerous unless you’re really minding the store. They work ok but not for short pieces because they tend to put pressure at one point. Plus you need to use two of them so you don’t have one hand free to do a quick shut down. A simple 2×4 with a small heel on the end works much better, but if you’re paranoid about getting your fingers within 6” of a blade make it a 2×6. There’s plenty of demos out there on making these.

4. Last but not least, check the slot/blade/fence for parallel just to rule out that possiblity.

IMO If you could have seen your work, had a decent splitter and used a different push stick, this might not have happened. That being said, ripping short or thin stock are two of the highest risk operations.

Who said the most important safety device in the shop is between our ears?

-- Everything is a prototype thats why its one of a kind!!

DISCLAIMER: Any posts on LJ are posted by individuals acting in their own right and do not necessarily reflect the views of LJ. LJ will not be held liable for the actions of any user.

Latest Projects | Latest Blog Entries | Latest Forum Topics