Open Source RoboticsRobots, software & learning

MiniHawk-VTOL

Robot / hardware build

3D-printed tricopter/flying-wing VTOL with two tilting front motors and a fixed rear motor, tuned on ArduPlane; STL/3MF artwork and parameter files are licensed CC BY-NC-SA 4.0 and native CAD is withheld. [1]

Build & first use →Official websiteUpstream build guideBill of materials

For
Experienced R/C and ArduPilot builders able to print large PLA parts, build linkages and tune VTOL transitions [1]
Cost
No current cost yet. Upstream bill of materials [1]
Source rights
Some licenses are unresolved. Includes noncommercial terms. Review licenses
Unknowns
host computer, operating system not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware
License
CC BY-NC-SA 4.0 (noncommercial) · license not fully assessed for firmware · Details by part

Requirements · Research details and dates

On this page

Overview

MiniHawk-VTOL is a 3D-printed tricopter and flying-wing hybrid by Steve Carlson that takes off and lands vertically. Two front motors tilt for forward flight and yaw control; a fixed rear motor is used only in hover. Four servos drive the motor tilt and the elevons. The README presents it as a common, accessible testbed for R/C, FPV and UAV experimentation. It suits experienced R/C builders who are prepared to tune a VTOL in ArduPlane, not first-time pilots. [1]

Is this for you?

Use cases
  • VTOL and UAV experimentation
  • FPV flying

[1]

Known limitations
  • Pre-hotfix Version 2.0 nacelles and tilt mounts are flagged as buggy and potentially dangerous
  • Native Inventor CAD withheld; STL/3MF plus one STEP hatch file in the archive
  • Aerodynamics and stability still under analysis per README
  • Noncommercial CC BY-NC-SA 4.0 terms
  • Parts table filenames partly differ from files in the archive

Source-review boundaries; no build or flight performed.

[1] [5] · Editorial assessment

What you need

Dependencies
  • ArduPlane (ArduPilot) firmware; Betaflight VTOL fork used earlier

[1]

Tools
  • FDM printer (build height 330 mm allows one-piece nose and wings)
  • Soldering station
  • Pliers, side cutters, sandpaper, hobby knife, hand drill
  • Cyanoacrylate glue, hot-melt glue, tape

[1]

Skills
  • Large-part FDM printing
  • Soldering
  • R/C linkage and servo setup
  • ArduPlane VTOL configuration and tuning

Derived from documented tools and steps.

[1] · Editorial assessment

Hardware & parts

Upstream bill of materials [1]

Hardware configuration

Tricopter / flying-wing (plank) VTOL: two tilting front motors plus a fixed rear hover motor, four servos for tilt and elevons

[1]

Actuators
  • Two 2207/2306 ~2300-2600 kV front motors (max 29 mm bell)
  • One 2207/2306 ~2000 kV rear motor
  • Two HS-65HB elevon servos and two HS-5065MG tilt servos (or equivalents)
  • Three 4S 40 A+ ESCs

[1]

Controller

ArduPlane-compatible flight controller with 3 motor and 4 servo outputs (mRo PixRacer Pro, Matek F405-WING or F765-WING)

[1]

Sensors
  • Optional pitot probe (MS4525D0 in parameter notes) and GPS

[1]

Power

4S 1300-1500 mAh LiPo (about 160 g), 60C or better; UBEC for servos if not built into the flight controller

[1]

Dimensions

Wingspan 800 mm, length 520 mm, wing area 15.6 dm^2, all-up weight about 1000-1200 g with PLA

[1]

Assembly & first use

Open the upstream getting-started guide [1]

  • Use the v2.0.99 release or current master STLs, not pre-hotfix Version 2.0 files
  • Print parts with the per-part slicer settings
  • Build airframe, linkages, servos and electronics following the development-branch build sequence
  • Load and adapt the ArduPlane parameter file for the chosen flight controller
  • Follow the staged flight-test sequence from hover PIDs to transitions

Editorial source-navigation sequence, not a reproduced or safety-qualified procedure.

[1] [3] [4] · Editorial assessment

Assembly

README build steps date from Version 1.0; author recommends the development-branch build sequence and an animated assembly video for Version 2.

[3] [4]

Calibration

Staged tuning: hover PIDs, weight and balance (26-30 mm from wing leading edge), elevon trim, AUTOTUNE, then transitions above 50 m; airspeed ratio calibration noted.

[1]

Cost

No current, complete configuration-specific build cost has been established for this profile.

Rights, cost and gaps

The README licenses the design, documentation, images and artwork CC BY-NC-SA 4.0, which does not grant commercial-use rights. It says the ArduPilot and Betaflight configuration files likely fall under GPL-3.0. The pinned archive holds STL and 3MF files plus one STEP file for the hatch; the native Autodesk Inventor models are withheld. No price or BOM total was identified, and announced Version 2.1 and 2.2 releases were not found in the release list. Nothing was printed, built or flown for this profile. [1] [2] [3] [5]

3D preview

Preview not available yet. Design-source links are available. A configuration-matched assembly and its file-level reuse scope have not yet been reviewed for a hosted preview.

Project notes

Which files to build from

This profile pins release v2.0.99, "Version 2.0 - Hotfix and 2.1 Preview". Its README carries a critical warning dated 22 February 2022: the original Version 2.0 nacelle arms and motor tilt mounts are buggy and can cause yaw and transition problems, even dangerous behaviour, and the old Version 2.0 zip files should not be used. The v2.0.0 release notes had already listed tilt-servo torque and temperamental transitions as known issues. In a March 2022 master-branch update the author said the current STLs and the hotfix zip are safe to build, and recommended the development-branch build instructions, because the main README's steps still show Version 1.0. [1] [2] [3] [4]

The parts table in the pinned README also lags the files. It names MH7_Nacelle_SideA, MH7_TiltMount and MH7_ControllerTray, but the archive contains MH7_Nacelle_A/B and MH7_TiltMount_A/B files, with and without bearings, and MH7_AvionicsTray files. Match parts against the archive and the parts tree rather than the table. [1] [5]

Components, size and setup

The README lists an 800 mm wingspan, 520 mm length and an all-up weight of about 1,000–1,200 g in PLA, with the airframe alone a bit over 460 g. Components include two front 2207/2306 motors of about 2,300–2,600 kV (bell diameter under 29 mm), a rear motor of about 2,000 kV, three 4S 40 A or larger ESCs, a 4S 1300–1500 mAh battery, HS-65HB elevon servos and HS-5065MG tilt servos, a carbon spar and Du-Bro linkage hardware. The flight controller needs three motor and four servo outputs, for example an mRo PixRacer Pro or a Matek WING board. A printer with a 330 mm build height allows one-piece nose and wings. [1]

ArduPilot is the recommended firmware. The README supplies an ArduPlane parameter file from a PixRacer Pro build and says other boards need adaptation. It warns that plugging servos into ESC outputs that use DShot or OneShot can burn them out. Tuning is staged: hover PIDs, weight and balance, a hand-launched forward flight, AUTOTUNE, and transitions attempted only after climbing to at least 50 m. The README also says aerodynamics and stability remain under analysis. [1]

What we checked

Source research only; no printing, physical build, configuration or flight test performed. No affiliate links added.

Not yet established

  • Requirements: operating system, host computer

Updates

Upstream last updated
Jun 19, 2022 [2]
Latest release
Feb 23, 2022 [2]
Profile updated
Oct 5, 2026
Sources last checked
Oct 5, 2026
Next review
Nov 5, 2026
Reviewed revision
155725981e0dfdfeed773ed461fca9238d611d7d (release v2.0.99 "Version 2.0 - Hotfix and 2.1 Preview", published 2022-02-23); MH7 Version 2 airframe with post-hotfix nacelles · repository

Source files and licenses

Printable artwork, documentation and configuration are public under CC BY-NC-SA 4.0 (noncommercial) with native CAD withheld; covered as source-available, not unrestricted open hardware.

LayerAvailability / license
mechanical designavailable · CC BY-NC-SA 4.0
STL, 3MF and a STEP hatch file; README license section covers design and artwork under CC BY-NC-SA 4.0 (noncommercial). Native Autodesk Inventor part and assembly files are withheld. No separate LICENSE file in the archive. [1] [5]
electronicsnot found · License not fully assessed
Purchased flight controller, ESCs, servos and receiver; no custom electronics design files identified. README gives component list and connection guidance. [1]
firmwareavailable · License not fully assessed
ArduPlane parameter files and a Betaflight CLI file, not firmware source. README says these configuration files likely fall under GPL-3.0 because both projects are GPL-3.0; that is an upstream expectation, not a confirmed grant. The linked Betaflight VTOL fork was not preserved. [1] [5]
documentationavailable · CC BY-NC-SA 4.0
README license section covers documentation and images under CC BY-NC-SA 4.0 (noncommercial). [1]

No separate host software; flight software is third-party ArduPilot or Betaflight.

No learned models used.

CFD pose geometry is part of the mechanical files; no dataset is distributed.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

  • S001 MiniHawk-VTOL README at release v2.0.99
    Description, critical nacelle warning, FAQs, metrics, components, parts table, ArduPlane guidance and license statement.
    Revision, date & where cited

    Steve Carlson (StephenCarlson) · github.com · revision 1557259 · README.md at (tag v2.0.99) · Accessed Oct 5, 2026


    Used for: Overview, Is this for you?, What you need, Hardware & parts and 5 more
  • S002 Repository release metadata (v2.0.99 and v2.0.0 notes)
    Selected hotfix release, dates, popularity signals, v2.0.0 known issue on tilt servos.
    Revision, date & where cited

    Steve Carlson (StephenCarlson) · github.com · Release v2.0.99 -> ; GitHub release API bodies · Accessed Oct 5, 2026


    Used for: Cost, Which files to build from, What we checked
  • S003 Master-branch README, 18 March 2022 update
    Author states current STLs are safe to build and recommends development-branch build instructions.
    Revision, date & where cited

    Steve Carlson (StephenCarlson) · raw.githubusercontent.com · README.md at master commit 3dc854bc22d3 (three README-only commits after v2.0.99) · Accessed Oct 5, 2026


    Used for: Assembly & first use, Cost, Which files to build from
  • S004 Development-branch README (build sequence)
    Build sequence intro referencing printed parts, slicer settings and 3MF files.
    Revision, date & where cited

    Steve Carlson (StephenCarlson) · raw.githubusercontent.com · README.md at development commit e0564c093419 (June 2022) · Accessed Oct 5, 2026


    Used for: Assembly & first use, Which files to build from
  • S005 Pinned archive file inventory
    Lists STL/3MF/STEP and configuration files actually present, including new A/B nacelle files.
    Revision, date & where cited

    Steve Carlson (StephenCarlson) · github.com · revision 1557259 · Archive members under stl-SourceFiles, 3mf-Implementations and cfg-Config at · Accessed Oct 5, 2026


    Used for: Is this for you?, Cost, Which files to build from, Source files and licenses

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history

2026-10-05 — Initial intake from release v2.0.99 plus master and development README snapshots (Growbotics comparison lead verified against upstream).