Leading Edge
Working draft // Companion to the rules proposal

Acro Move Library

Every move a wingsuit acro team can fly, described in one common language, and every execution fault a judge can deduct for. The list is built from first principles so nothing is missed, then checked against 17 recent FAI free routines.

Prepared by Jack Peploe, Acro representativeStatus Working draft for competitor and judge reviewOctober 2026
Part 01 // The language

How moves are described

A move list built by watching video only captures moves someone has already flown. To cover every possible move, this library describes each move by the same six elements. Any move, flown or not yet invented, is a combination of them.

ElementOptions
WhoPerformer A · Performer B · both in turn · both together (synchronised) · both mirrored · camera
ActionRoll (180°, 360°, 540°, 720°) · transition · orbit · carve · loop · change position · take or hold a grip
PathNone · over partner · under partner · around partner · through (between partner and camera)
OrientationStart and end for each flyer: normal (belly to earth) · inverted (back to earth) · side (knife-edge) · steep
PositionSide by side · echelon · trail · stack · face to face
ContactNone · grip taken at the end · grip held throughout. Grip types: hand-hand, hand-foot, hand-opposed-foot, foot-foot, double, shoulder/stacked, face-to-face

Every move in the library has a code (for example R6, barrel roll over partner) and a completion standard: what a judge must see for the move to count. The compulsory sequences A to O are combinations of these moves. Each sequence has its own entry in the library, listing the moves it is built from.

Part 02 // Try it

Move builder

Combine the elements to describe any move. The builder writes the move in plain words, shows whether it matches a move already in the library, and flags combinations that would be new.

Part 03 // The list

Move library

The first full list, in nine families, starting with the 15 compulsory sequences and their synchronised versions where they exist from Addendum A (as animated on the Leading Edge competition library) and the three new sequences proposed in the rules proposal. Each sequence lists the moves it is built from. Seen in video shows how many times each move was identified in the 17 free routines. Click it to list every file and timestamp. "Not seen" means not seen in this footage, not that it isn't flown. Element marks basic building blocks (a transition over or under, a half roll, a hand grip). They are listed so sequences and routines can be described precisely, but they would not count as Key Moves on their own. Draft tier is a starting point only. Difficulty will be refined with competitors and judges, and shared with judges as guidance to help them understand what makes a move hard.

CodeMoveWhoCompletion standardSeen in videoSynchronised?Draft tierUsed in · Built from

Part 04 // Check it

Review by video

Every move identified in the footage, in time order, with the file name and the timestamp in that file. Open the file in any video player and jump to the time. Confidence shows how sure the review was: low usually means the move happened between frames or the camera angle hid the direction.

TimeCodeMove and what was seenConfidence
Part 05 // Deductions

Execution faults

Every way a move or routine can go wrong, grouped by what goes wrong. Each fault has a code, a fixed deduction and a description of what the judge sees. Distances are in wingsuit spans (WS, about 2 m). Heading is always measured between the performers: a pair turning together is not a fault.

How often shows how often the fault appeared across the 17 routines reviewed. Camera faults stand out: in 14 of 17 routines the camera lost one or both performers in the last seconds of working time.

CodeFaultHow a judge sees itHow oftenDeduction

Counting rules

Sequence definitions from FAI Competition Rules – Wingsuit Flying, 2026 Edition, Addendum A. Video review of free routines supplied for this work.