Performance reports
A performance report freezes the current analysis into a single HTML file you can email, archive with the aircraft's paperwork, or hand to a client. Everything is embedded inline (styles, charts, the power diagram, even the logo), so the file needs no internet connection and opens in any browser exactly as saved.
Generate one whenever a design milestone is worth keeping: the report captures the build as it stands on the bench at that moment.
Downloading a report#
On the Builder page, open the Build menu and choose Download report (HTML). The report is computed from the build currently on the bench and downloads immediately.
The same menu also offers Download report (PDF) for a print-ready document.
What the report contains#
The report opens with the build's summary line (motor count and prop size, bus and battery counts, total pack energy) and a row of stat cards for the headline numbers:
- All-up weight in grams
- Thrust-to-weight, tagged with its rating (underpowered, adequate, good, very agile/overkill)
- Hover endurance and Cruise endurance in minutes
- Hover current in amps
- Power loading in g/W
- Max speed in km/h, tagged with what limits it (thrust-ltd, power-ltd, or model ceiling) when the forward-flight model is active
- Disc loading in g/cm²
Below the cards sits the animated power-distribution diagram: batteries flow into buses, then into the motors and the regulator rails, then out to each load. Wire thickness scales with current, the same diagram shown at the top of the Builder's readout.
Charts#
The report embeds the same SVG charts the Builder draws:
- Mass breakdown: frame, each battery, each component, and other payload.
- Hover power split: prop hover power against auxiliary pack-input power.
- Flight bus current vs limits: hover and wide-open-throttle current against the flight pack's continuous and burst ratings.
- Flight endurance vs flight-pack capacity: hover and cruise endurance swept across pack capacity from 0.4 to 2.0 times your pack, with pack mass scaled along, and your actual capacity marked. This is the chart that answers "would a bigger battery actually help".
- Thrust-to-weight vs flight-pack capacity: the same sweep for TWR, showing what the extra mass costs.
- Prop power required vs airspeed, with the cruise speed marked, when the forward-flight model is active. See Forward flight and VTOL cruise.
Tables and checks#
Three tables follow: Power buses (energy, endurance, and continuous utilization per bus), Performance detail (thrust, RPM, currents, throttle band, air density, pack energy, cruise range, and the wing and transition figures for a VTOL build), and Auxiliary power rails (each rail's output current against its regulator rating, and its load and pack-input watts).
The report ends with the Checks list, the same pass, warn, and fail lines the Builder shows: ESC headroom, pack continuous and burst limits, rail ratings, prop clearance, and the rest. Values the model estimated rather than measured are tagged est, and if max thrust is an estimate the report carries a warning to enter a measured or datasheet value for trustworthy TWR and throttle figures.
Reports are snapshots
A report does not update when the build changes. For a comparison you keep working with, save the build to the library instead and use its history; see Build history and organizing.