You are on page 1of 2

Basic Rook Endgames

Submitted by DrDave on Wed, 06/02/2013 - 23:43

We lost on board count to old rivals Teignmouth in the Peter Rooke Cup
at the end of January. One of the last games to finish involved a
simple-looking Rook endgame. Just as it was getting crucial, White,
short of time, found a time-saving blunder:

your web browser and/or your host do not support iframes as required to display the chessboard

So what should the result have been? I discussed it briefly with my


friend Bill Ingham. As is often the way, he fancied his side's chances
to win, and I hoped for a draw, but the discussion showed how vague we
all are about some basic theory. To be fair, some apparently small
differences can change the best obtainable result:

your web browser and/or your host do not support iframes as required to display the chessboard
your web browser and/or your host do not support iframes as required to display the chessboard

So, what was the right result for the Teignmouth game?

Before I answer that, I want to decide: regardless of the right result,


what is the right approach?

You probably know the Philidor and Lucena positions. Philidor showed a
draw, with the defending King having control of the Queening square. The
defender keeps out the attacking King. White can make progress only by
pushing the pawn, the Black shows a draw by sending the Rook a long way
away and playing a flurry of checks.

your web browser and/or your host do not support iframes as required to display the chessboard

The 'Lucena' position, shown by Salvio and attributed to Sciapino, is a


win for the attacking side. With the defending King cut off by at least
two files, the defending Rook has to play the flurry of checks from
across the board. The attacker either makes an escape hatch for the
King, or 'builds a bridge' so that the Rook can step in at the right
moment.

your web browser and/or your host do not support iframes as required to display the chessboard

Please note: sending the Rook a long way away. If the defending Rook is
too close to the attacking King, the King will be able to chase the Rook
away all by itself.
This is the idea of checking distance, and will help us understand less
clear-cut positions.

We all know that the Rook belongs behind the pawn, but that's not true
for every position. For example, in this one, the defending Rook has
checking distance only in front of the pawn.

your web browser and/or your host do not support iframes as required to display the chessboard

How does this help us understand the Teignmouth position? Well, the
defending King doesn't have access to the Queening square, but there may
be checking distance from the side.

your web browser and/or your host do not support iframes as required to display the chessboard

Eagle-eyed readers will have spotted that I cheated: I swapped around


the Rooks, giving the defender one more file's-worth of checking
distance. In a position like the actual game, with the defending Rook on
the b-file, it's not quite enough:

your web browser and/or your host do not support iframes as required to display the chessboard

Now, when Bill and I were playing around with this position, I managed
to persuade him that it might be a draw, because he couldn't escape the
flurry of checks, because he didn't approach the Rook with his King. I
didn't know the theoretical result, but I did know the best thing to
try.

It's very well worth your while to play out these positions against a
friend or a computer, so that if and when it turns up in one of your
games, you won't hesitate to adopt the right approach.

A very useful online resource is this implementation of the Nalimov


tablebases: http://www.k4it.de/index.php?topic=egtb&lang=en which gives
the theoretical best obtainable result from any given simple position.

You might also like