Flying rook

Flying rook problems ask a rook to visit every square of a board under a modified movement rule. The "flying" restriction changes what counts as a legal step, so familiar chess intuition is not enough. Students must rebuild their sense of which squares are reachable from which, then design a route that covers the whole board without getting trapped.

The mathematical feel is close to a Hamiltonian path: visit every vertex of a graph exactly once, or at least once according to the version of the problem. Students do not need the formal vocabulary on day one. They do need the habits that vocabulary later names: model the board as a network of allowed moves, watch for dead ends, and look for an invariant that explains why some routes fail.

Problems.cc includes an interactive demo for this topic. Students can attempt tours on screen, undo a bad choice, and notice when the remaining squares become disconnected under the flying rule. That feedback is valuable. It helps them see the structure of the search space before they try to describe it in writing.

Intermediate and senior students often meet hard problems that look like "try everything". Flying rook work shows why that instinct is incomplete. Blind search grows quickly, so progress depends on choosing a plan, recognising forced moves, and proving that certain positions leave the rook stranded.

This is excellent training for competition mathematics and for later discrete topics. Students practise reading an unusual definition carefully, translating it into a workable model, and checking completeness rather than stopping at a route that "mostly works". Completeness is the hard part: one missed square, or one illegal jump, breaks the solution.

The topic also builds stamina. A failed tour is not wasted time if the student can say what went wrong. Learning to extract a lesson from a dead end is one of the most useful habits an ambitious maths student can develop.

We teach the flying rook through a climbable sequence. Early problems use smaller boards or gentler constraints so students can complete a tour and feel what success looks like. Later problems tighten the rule or enlarge the board until construction alone needs supporting argument: why this order of squares, why this intermediate landing, why no shorter explanation will do.

In lessons, we ask students to record failed attempts as part of the work, not as scrap. A short note such as "after visiting the corner, the remaining edge squares are unreachable" is already mathematical. Discussion then compares routes and isolates the shared obstruction. Instructors intervene when a student is thrashing without a model, and step back when productive search is underway.

Written reasoning is central. A finished path drawn on a board is a construction; a clear account of why the path is legal and complete is the solution. We also ask stronger students for impossibility variants when a tour cannot exist, so they practise both directions of argument.

Depth before speed remains the rule. The goal is not the quickest tour on the demo. It is a student who can plan, revise, and explain a complete route under an unfamiliar constraint.