Build log

Progress published as it happens.

Entries go up as work is completed — including the tests that did not go as planned. No entries have been published yet; the first arrives with Aircraft 001.

From the bench

Where the hardware stands today.

Photographs of actual work in progress. These airframes have not been flight-tested yet; results will be published here as testing begins.

AI-generated concept rendering of the SPRIG-120C mini quadcopter with motors, FPV camera, flight controller, and LiPo battery on a laser-cut birch frame
AI concept rendering: the mini SPRIG-120C we intend to build from the laser-cut frames — 2.5 mm birch, 2.5 in props. Not a completed or tested aircraft.
Laser-cut SPRIG-120C frame plates laid flat before assembly, with a basswood bottom plate
Feasibility cut by Robert Anthony Art: how long does a frame take on portable machinery, and is it practical? The bottom plate is basswood. Next: expert component review, then a recut.

Planned series

What we will publish first.

Planned

Building RAPD Aircraft 001

Assembly of the first non-soldered 450 mm kit, filmed end to end.

Planned

Registering a Physical Build in the Tracker

Turning real components into tracked records with history.

Planned

Testing One Component at a Time

Isolating variables so results mean something.

Planned

Designing a 450 mm Wooden Frame

Experimental material work with honest weight and strength data.

Planned

What Failed and What Changed

Publishing failures alongside the design responses they caused.

Planned

Moving From Parts to a Complete Frame

Bringing validated components together into a full airframe.

Entry template

Every entry answers the same questions.

A repeatable structure keeps results comparable across builds and makes the log useful to engineers, not just followers.

  • Objective
  • Aircraft or part involved
  • Configuration / version
  • Hypothesis
  • Test method
  • Result
  • Failure or unexpected behavior
  • Maintenance action
  • Next change
  • Photos / video
  • Safety notes

We do not publish sensitive operational details, private customer data, unsafe testing instructions, or personally identifying operator records.