The Clubhead Lag is indeed the very slight flex in the Shaft that occurs when the Lag (the resistance of the Sweet Spot inertia to a change in its direction) is Loaded (7-19) -- I like to use the term welded -- against the first joint of the Right Forefinger (#3 Pressure Point) during the Start-Down.
This Clubhead Lag is the very slight -- that's why the darn thing is so illusive! -- Lag of the Clubhead (Sweet Spot) in its desperate attempt to maintain its straight-line relationship with the #3 Pressure Point. It is that Lag -- from Sweet Spot to the #3 -- and the Stress in the Clubshaft that results that is the Clubhead Lag
1. Visually, the shaft bent/stressed, would be clubhead lag?
2. If the left wrist is flat and vertical but the clubhead is behind the hands, would that constitute clubhead lag?
Hi Martee,
1. Yes, if you see a stressed Shaft, you're seeing Loaded LagPressure.
2. Hopefully! But not necessarily. We're talking about 'Right' Timing here.Per 6-F-1, if the speed of the in-line seeking Sweet Spot catches the Thrust ofthe #3 Lag Pressure Loading, then though Thrust is still present and able tomaintain Velocity, the Stressed Shaft is lost for both Hitters (who need it todrive against) and for Swingers (who need it for the wallop of CentrifugalForce). In other words, the Sweet Spot has 'caught up' with the #3 andClubhead Lag Pressure has been irretrievably lost.
So, you could have a visually Flat Left Wrist and still have a very"soft" Impact. When that happens, you will be able to read thewriting on the ball as it floats away:
T - I - T - L -E - I - S - T
By the way, on certain Short Shots, that 'soft' Impact is exactly what you wantto produce. A deliberate throwaway of the Clubhead Lag Pressure without theaccompanying geometric disaster of of the Bent Left Wrist!
PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
ERROR: The request could not be satisfied
504 Gateway Timeout ERROR
The request could not be satisfied.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront) HTTP3 Server
Request ID: Frtvlb6WorYNO019S8T7jgbOlDJkLm-QLH0aJgv2fqMUEYq1Tzw14Q==