Sky Team Complete Guide: How to Land, Communicate, and Know When Turbulence Is Worth It

Sky Team is for exactly two players who like compact cooperative puzzles, repeated attempts, and the strange intimacy of solving under communication limits. It is superb for couples and regular gaming partners because each landing becomes a shared vocabulary. It is a poor fit if either player hates dice, wants constant table talk, or feels personally blamed when a cooperative plan fails.

The box contains a substantial sequence of airports and modules, so do not buy Turbulence on day one. The base game already teaches traffic, kerosene, wind, ice, and asymmetric pilot abilities. Your first purchase should be the plane, not the weather report.

Each pilot rolls four dice behind a screen. Once both are rolled, conversation stops: partners alternate placing one die at a time into cockpit spaces. Blue and orange dice must jointly keep the axis balanced and the engines in a safe band; those two systems require attention every round. Other dice clear traffic by matching radio numbers, extend flaps and landing gear, or concentrate coffee into modifiers.

After all eight dice are placed, resolve the board, descend one altitude step, and advance toward the airport according to engine speed. The team wins only by arriving with traffic cleared, the plane level, landing gear and flaps properly deployed, and speed under control. The design is communication through preparation: discuss priorities before rolling, then read each other’s placements.

Imani’s approach briefing: solve what can still fail, not what merely looks untidy. Axis and engines demand attention every round; traffic can become immediately fatal; gear, flaps, and brakes are deadlines. That hierarchy is the cockpit.

The placement itself is the message. Committing a constrained die early can warn your partner; leaving a flexible space open can invite them to solve the dangerous instrument. The strongest pairs do not communicate more. They waste fewer placements saying the same thing.

The first crash is treating gear and flaps as “later” until later has no legal die. The second is balancing the axis with two perfect dice while traffic remains untouched. The third is spending coffee to improve a merely comfortable action, leaving no flexibility for the final placement. The fourth is forgetting that engine totals determine movement, so an otherwise tidy cockpit overshoots the airport.

A fifth mistake is emotional: narrating the postmortem as one player’s error. Reconstruct the sequence instead. Ask which earlier placement removed the rescue route. Most final-die disasters began two actions earlier, when a flexible space was consumed or a deadline was ignored.

Play the introductory airports until both partners can land without constantly rereading the cockpit. Then add one concept at a time. Modules are not just difficulty knobs; they change the rhythm of what must be solved. Wind changes movement math, ice pressures brakes, kerosene creates a shared resource countdown, and asymmetric abilities change who can absorb which burden.

Do not select scenarios only by the number printed beside them. Pick the module your pair is curious about, read its one-page rule together, and run the airport twice. A first attempt teaches the new system; the second reveals whether you actually like it.

Turbulence earns its place after the base campaign is fluent because its modules change priorities rather than rescue a tired game. If the original cockpit still produces crashes and delighted accusations, congratulations: the expansion can remain safely on the runway.

Set up the first airport before inviting them over. Sit side by side or at a slight angle so both can read every dial. Teach the cockpit without screens, run one practice round with open dice, then reset and play correctly. During the debrief, celebrate the piece of communication that worked before discussing the crash.

If analysis anxiety appears, agree on a pre-roll checklist: axis, traffic, speed, deadline. That gives the silent phase a shared foundation. Stop after two or three attempts, even after a near miss. Sky Team is best when the next landing feels irresistible, not when the eighth retry turns partnership into shift work.

Advanced pairs stop treating instruments as separate chores and begin pricing flexibility. A six that can satisfy axis, engine, or a permanent switch should not be committed before a more constrained die. Coffee is not merely a modifier; it is stored option value. Radio is not housekeeping; it can determine which engine total is safe because traffic and movement share a deadline.

Before rolling, divide actions into forced, flexible, and deferrable. After rolling, place forced dice early when they reveal useful information and flexible dice late when they preserve rescue routes. Watch placement order as carefully as value. A partner who fills a low axis slot with a medium die may be asking you to keep your high die for engines. None of this requires a secret code. It is the natural language of scarcity, and it is why the same cockpit can remain compelling after both players know every printed rule.