Case study · Engineering

A drone you can take apart in the browser

I spent a year on UAV work at Moscow Aviation Institute's university factories. This is that knowledge made clickable: eight named assemblies, drag to turn it, slide to pull it apart. Every part is generated in code — there is no CAD file behind it and nothing to download.

  • Role: designed and built it
  • Stack: three.js, WebGL, procedural geometry, one HTML file
  • Where it comes from: UAV engineering at MAI, 2023 — STM32, Arduino, ArduPilot
  • Try it: open the viewer full screen
The viewer, running here. Drag to turn it, scroll to zoom, and use the slider to take it apart.

Why build it

A drone is easy to describe and hard to picture. A photograph shows you a shell. An exploded diagram on paper shows you one angle, chosen by whoever drew it. I wanted the thing you can turn over in your hands.

It is also the clearest proof I have of the engineering half of my background. The avionics degree and the year in the factory are two lines on a CV; this is what they actually mean.

Eight assemblies, and what each one does

  • Main frame — the lower shell that carries the arms, the boards and the battery bay.
  • ESC board — the electronic speed controllers that drive the four brushless motors.
  • Flight controller — the processor with the IMU, gyro and barometer that keeps the drone level.
  • GPS and compass — satellite positioning for hover hold and return-to-home.
  • Battery — a swappable LiPo pack that slides into the rear bay.
  • Gimbal camera — three-axis stabilised, so the footage stays level while the airframe does not.
  • Folding arms and brushless motors — four outrunners on arms that fold flat for transport.
  • Propellers — quick-release, pitched for quieter flight.

How it is built

No model was imported. Every shell, arm, board and propeller is built at runtime from primitives and extruded shapes, which is why the whole thing is one 20 KB HTML file instead of a multi-megabyte mesh.

The explode slider interpolates each assembly along its own axis, so parts move the way they would come off the airframe rather than scattering from a single centre point. Hovering highlights a part and names it.

Worth knowing: three.js and its orbit controls are served from this site, not from a CDN. The page keeps a content security policy with default-src 'none', and its one inline script is allowed by hash.

What I'd do differently

The component descriptions live in the same file as the geometry. Splitting them into data would make the viewer reusable for a second machine without touching the rendering code.

← All work