Redstone Companion · Learn Open simulator →

Minecraft Flying Machine (Bedrock)

A flying machine moves itself through the air using slime or honey blocks, pistons, and observers. An observer engine keeps pushing and pulling a sticky core so the whole rig glides without support.

Bedrock Edition · Updated 2026-06-02

How does a flying machine work?

A flying machine is a self-propelling rig that drifts through open air with no track or support. The magic comes from sticky blocks — slime and honey — which drag adjacent blocks along when a piston pushes or pulls them. Pair that with an observer “engine” that detects the machine's own motion and re-triggers the pistons, and you get a contraption that pushes itself forward, then pulls its tail along, over and over.

The observer engine

The engine is a loop. An observer watches a block that moves when the piston fires; the moment it moves, the observer pulses, which fires the next piston, which moves another block, which the next observer sees — a chain reaction that keeps the rig in perpetual motion. A leading piston pushes the slime core forward; a trailing sticky piston grabs the rear and hauls it up to follow. Because slime carries everything stuck to it, you can bolt a payload onto the machine and ferry it across the world.

Start it and watch the observer engine push-and-pull the slime core forward continuously. The whole machine glides with no track.
Open full simulator →

Slime vs. honey blocks

Both slime and honey stick to neighbours and get carried by pistons, but they differ in useful ways. Slime is a solid block that conducts redstone; honey is transparent and does not carry signal. Crucially, slime and honey don't stick to each other — builders exploit that to create clean break points, letting one half of a machine slide free of the other. Honey also drags entities standing on it along for the ride, which slime won't.

Key facts

Bedrock vs. Java: speed and observer quirks

Flying machines work on both editions, but Bedrock lacks the zero-tick piston tricks that make some Java machines extra fast, and observers update on a slightly different schedule — so a frame-perfect Java engine may stall or need a tweak on Bedrock. Slime/sticky-block mechanics are also a touch stricter. Build a simple, robust engine first and confirm it loops reliably. Remember there's no quasi-connectivity, so power pistons directly; this simulator follows Bedrock rules.