<p>Flying machines are the pinnacle of vanilla Minecraft redstone engineering. Unlike most builds that sit stationary, a flying machine <em>moves</em> — propelling itself indefinitely across the sky, ocean, or through a mountain using nothing but pistons, observers, and the sticky properties of slime. It is one of the few mechanical designs in vanilla Minecraft where the machine does something you genuinely could not do any other way. Building one successfully means you understand observer timing, piston mechanics, and block update order — the deepest layer of how Minecraft actually works.</p><p>This guide builds the classic 2-wide flying machine: two parallel piston-observer engine units, cross-triggering each other in a loop. It is the simplest design that actually flies reliably, and it is the foundation for every more complex flying contraption — carpet duplicators, tree farms that walk themselves, and even player-carrying sky ferries.</p>
This is an Advanced build. It demands solid familiarity with at least one of Minecraft’s complex systems — redstone timing, mob AI behavior, or intricate 3D spatial layout. Gather every material before placing the first block, and expect to debug. The payoff in automation, efficiency, or aesthetics is well worth the effort.
| Material | Quantity |
|---|---|
| Slime Block | 8 |
| Sticky Piston | 4 |
| Observer | 2 |
| Redstone Block | 1 |
| Honey Block | 2 |
| Any Block (rider) | 4 |
Total distinct materials: 6. Gather everything listed above before you start — mid-build supply runs break your momentum.
A flying machine works because observers watch pistons extend, which triggers more pistons. The core unit is: Observer facing forward → Sticky Piston behind it facing forward → Slime Block attached to piston head. When the observer detects any block update, it fires a 1-tick pulse powering the piston. The slime block carries any blocks attached to it as the piston extends. A second mirror-image unit provides the return pulse — each unit alternately drives the machine forward by 1 block per tick cycle.
Place a sticky piston on the ground facing north (your travel direction). Attach a slime block to the piston face. Place an observer block behind the sticky piston with its detection face pointing at the back of the piston — when the piston moves, the observer detects the block state change and fires a pulse forward. This observer → sticky piston → slime sequence is the minimal engine unit.
Parallel to your first unit, build a second sticky piston 2 blocks to the right of the first, also facing north. Attach a slime block to its face too. Place an observer behind this second piston also pointing at the piston back. Connect the two units with a slime bridge: attach both slime blocks together by placing a bridging slime block between them. The two observers now cross-trigger each other — unit 1 moving triggers unit 2's observer, and vice versa.
The machine needs an initial trigger pulse to start. Place a redstone block on any exposed face of observer 1 momentarily (you can break it after — just tap it in and out to start the cycle). Once started, the machine is self-sustaining. Attach additional slime blocks on top of the moving slime platform as 'rider' positions — any block touching slime or honey gets pulled along for the ride. This is how you transport chests, armor stands, or players.
Flying machines have no brakes by default — they run until they hit something. Build a sticky piston facing backward, attached to the main slime block cluster, wired to an observer on a short redstone delay timer. When the timer fires, the reverse piston extends outward, adding a block that interrupts the forward engine cycle and halts the machine cleanly. For direction change, build the symmetric mirror design: the same engine pointing south, started with the north machine parked at one end.
<p>The 2-wide design works because of a precise timing relationship between observers and pistons. When a sticky piston extends, it changes block state — the observer watching it detects that change and fires a 1-tick pulse. That pulse powers the adjacent piston, which moves the slime block, which carries the whole assembly forward by 1 block. The second unit fires on the next tick when it detects the first unit's movement.</p><p>Slime blocks are essential because they transfer momentum to adjacent blocks on contact — without slime, each piston would only move itself. The 2-wide layout prevents the two engine units from interfering with each other's timing while still keeping the design compact enough to move as a single rigid body. It is elegant in the way that all great redstone is: maximum function from minimum parts.</p>
Once you’ve completed the base build, try one of these modifications to make it your own:
Extend the slime platform width to 5-6 blocks and add chest blocks as riders. The machine becomes a self-propelled automated cargo sled — load it with your mining haul and send it home to base while you keep working.
Mount the flying machine on the ceiling instead of the floor, with observers facing down. Attach a line of pistons pointing downward with TNT dispensers. The ceiling machine traverses a mineshaft automatically while the pistons detonate TNT in the rock face below.
Replace the rider blocks with a platform of honey blocks on the top face of the slime cluster. Players standing on honey get carried along for the ride. Build two machines facing opposite directions at each end of a transit line — a redstone-timed relay system can park and launch them on schedule.
These are the issues players most often run into with this build:
If you enjoyed this guide, these builds complement it well: