Returning backspin

I'm having problems returning halflong relatively high bouncing (say 2 inch above net height) backspin balls, that don't or barely clear the table end.
These balls are typically the result of weak pushing rallies, where both playesr are hesitant to start an offensive return.

My personal habit is to make a kind of mini-loop above the table, but many times I find out I can't execute enough vertical back- and forward swing to generate the required racket head speed, thus ending up in the net.
I wonder whether I could execute a more shallow forward swing by taking the ball earlier, or should execute a flick above the table.

what would be my options and which of those is considered best?

Thanks for the tip. I'll experiment a little more with the racket angle.

As for the second part of your reply, this question is really about those balls that don't clear the table end.

Due to my current training profile / mindset, my automatic reaction on the relative high balls is to execute some kind of mini-loop/spindrive , but I wonder whether this is the right choice.

NextLevel wrote: I would say it is more a matter of anticipation and you should be ready to forehand flick or use a backhand loop over the table. Only back up when you expect your opponent to attack (or you have left the ball too high) as your opponent pushing a high short ball usually gives you a lot of time to recover.

You made some good points NL, thanks.

First of all with regards to anticipation, during last week’s competition my mental attitude was a bit shaky after having been exposed to my opponent’s brutal offensive (lefty) power but also having witnessed his very weak defensive pushing capacity.

Having trained BH-over-the-table-loop only on short low services and full BH loops on long balls, I “choose” the incorrect technique on these medium /half high pushes. I tried to do a full loop without having enough space above the table to do so, resulting in a swing that was too shallow and a contact point that was too high/late, thus no racket head speed.

Funny though I realized the problem straight after the match, I haven’t come up with this solution of creating more head speed by doing some more wrist bending and perhaps even contacting the ball on the side (Banana!) until now. Again I think I’ve connected the Banana return too much too service return without ever training this during a push rally (it’s always service-long push –full topspin. Typical Pavlov example.

Definitely include this in my training this week.

Edited by Hopper - 09/21/2015 at 9:46am

You can also force his hand or bait him into trying to loop an backspin ball.

Edited by suds79 - 09/21/2015 at 10:29am

The difference between a "push" and a "dig".
http://tabletennis.about.com/od/Intermediate-Table-Tennis/fl/Stop-Pushing.htm

Also I've learned that a ball that's at the end of the table and a little high, but not beyond the table can be looped with a regular forehand/backhand loop. Very important to stay close to the table.

Almost always against a player who pushes a lot - you can trick them into pushing deep by pushing deep yourself. Sounds like deep to the backhand and then pivot for a loop would have been perfect. This is also my favorite thing to do in table tennis. It'll stop working against quality attackers, tho.

Lastly - good question! We have too much equipment discussions and not nearly enough coaching discussions. Problem solving is what makes table tennis addictive to me.


Edited by wilkinru - 09/21/2015 at 12:17pm

Thanks Wilkinru and Geardaddy for many more excellent views on this topic.

Pushing untill receiving a long ball was exactly what did work against my opponent but I was a little too much off guard to succesfully FH loop on this long ball.

Also love Geardaddy's comment on flat hit smash. Absolutely a great feeling when executing correctly, but uptil now I keep this one for the trainingsessions and still don't dare to use this in competition.
I know.....it's a little weak but believe me; my risk profile is al ready a bit on the high side and although learning a lot, I also loose quite some points by unforced errors, for which my team has to make up (which they fortunately do a lot of times)