Air65 PID Tune: The Three Published 65mm BetaFPV Tunes
Short version: there are three published 65mm BetaFPV cards in the tune database — the stock Air65 II Champion tune, and two RyFly tunes on VCI Spark 0702 29000KV with different props. Pick the card that matches your motor and prop, not the one that matches your frame. Apply it with props off, fly one pack, and check motor temps before you fly a second.
To find them on the database page, tick Frame 65 and Brand BetaFPV. Every card has a copy-paste CLI export.
The three cards
| Tune | Combo | P / I / D roll · pitch | Notes |
|---|---|---|---|
| Stock | Air65 II Champion, stock motor/prop | 36/61/27 · 37/64/29 | Factory CLI, April 2026. Rates ACTUAL, rc_rate 7, srate 58/58/50, expo 0. |
| RyFly | VCI Spark 0702 29K · Gemfan 1219S | 54/77/38 · 62/89/52 | D floor R36/P49, TPA 60, FF off, RPM filter on bidir DSHOT300. |
| RyFly | VCI Spark 0702 29K · HQ 31mm | 61/110/41 · 67/121/51 | D floor R41/P51, TPA 60, FF off. Same filter config as the 1219S tune. |
Both RyFly cards run the same rates: ACTUAL, rc_rate 4, srate 74/74/70, expo 56. Yaw D is 0 on all three, which is correct and not an omission.
One naming trap. On Betaflight 4.2–4.5 the D floor is d_min_<axis> and the
value in the table above is the ceiling, d_<axis>. On the 2025.x and later
date-versioned releases those names moved: d_<axis> is the floor and
d_max_<axis> is the ceiling. Same two numbers, swapped labels. Paste the
card's CLI rather than typing parameter names from memory, and check that your floor is
below your ceiling before you save.
Applying one without cooking motors
- Props off. Paste the diff into the CLI,
save, let it reboot. - Props on, hover at knee height for thirty seconds. Listen for a hot, buzzy oscillation — that is too much D for your build, and it is audible before it is visible.
- Land and touch the motors. Warm is normal. Too hot to keep a finger on means back the D ceiling off by 5 per axis and fly it again.
- Fly one full pack before you decide anything. First-thirty-seconds impressions are mostly rates.
- Change one thing per pack. Two changes and a better flight tells you nothing.
If your combo is not on a card
The analog daily driver behind the bench numbers — 25.42 g all-up, 3:53 cruise — runs VCI 0702 PRO DB 30000KV with Gemfan 31mm triblades. That is a different motor from the Spark 29K on the two RyFly cards, so none of the published tunes is that build's tune. Rather than publish numbers I have not flown on it:
# VCI 0702 PRO DB 30000KV · Gemfan 31mm — daily driver
# diff not published yet. This block fills in when the tune is flown,
# logged, and added to the tune database as its own card.
For any unlisted combo, start from the nearest card by motor KV and prop size, drop the D ceiling 10–15%, and fly it. A higher-KV motor on the same prop wants less D, not more. Then put the log through the blackbox analyzer — it will tell you whether the noise you are hearing is motor noise, prop wash, or a D-term that is fighting the filter stack.
Before the first pack
Load the rates into the browser sim with your real radio so your thumbs already know what srate 74 and expo 56 feel like. Check thrust-to-weight for your actual motor, prop and pack in the calculator — a tune fights a bad prop choice and loses.
Starting points only. Motor KV, prop brand, pack C-rating and frame stiffness all change how a tune responds. Gear links marked /go/ are affiliate redirects to parts I fly; they cost you nothing extra and do not change what gets recommended.