Lumipad ← Back to homepage
Library · Reference

Tuning, honestly.

PID tuning is the most over-discussed topic in the FPV community — endless videos and forum threads chasing perfect tuning. For survey work, the truth is that INAV defaults are usually fine, and the biggest real gains come from filters and mechanical setup, not from PID gain values. This page is the honest version: when tuning matters, when it doesn't, and what actually helps when it does.

Version 1.0 · Updated 05·2026 Author: Lumipad Engineering License: CC-BY-SA-4.0 Languages: EN
~85%
Cohort builds fly fine on defaults
3
Filter changes worth making
P · I · D
The three gain values
10×
Mechanical fixes vs PID gains
How to read this page

Most readers should leave after Section 1.

This page exists because some alumni do encounter tuning issues, and the topic deserves a Lumipad-context reference. But the page also exists to send most readers away. If your drone hovers reasonably, holds position when commanded, and produces usable NDVI imagery, you don't need PID tuning. Section 1 is a diagnostic flowchart designed to confirm that for ~85% of cohort readers; if so, close the page and go fly.

The remaining sections are for the small set of cases where tuning genuinely helps: builds with non-default components, vibration showing up in NDVI imagery, drones that wobble noticeably in flight, or alumni doing demo/exhibition flying that needs sharper response. Mechanical issues come before software ones — Section 2 covers the physical sources that masquerade as tuning problems. Sections 3-6 cover the actual tuning if mechanical inspection didn't fix things.

Section 01 5 minutes · most readers stop here

Do you need to tune?

Five diagnostic questions. If your drone passes all five, you don't need this page — go fly. If it fails one or more, the failure mode points to a specific section below. The questions are ordered roughly by frequency: most "tuning problems" turn out to be answered by question 1 or 2.

Five questions to ask about your drone's behavior:

# Question If yes (drone is fine) If no (where to look)
1
Does the drone hover smoothly when sticks are released? On a calm day, in Position Hold or Angle mode, drone holds position with no visible oscillation or wobble.
Default tuning is fine. Skip the rest of this page.
If oscillating: Section 2 (mechanical) first, then Section 3 (filters).
2
Are NDVI photos sharp at typical survey altitude? Photos taken from 50-100m altitude show crops in clear focus, not blurred or smeared.
Vibration is acceptable; tuning won't help imagery further.
If blurry: almost always mechanical (Section 2). Tuning rarely fixes blurry photos.
3
Does throttle response feel proportional? Small throttle changes produce small altitude changes. No mushy lag, no aggressive overshoot.
PID I and D terms are reasonable for the build.
If mushy: Section 4 (PID I-term too high). If aggressive: Section 4 (D-term too low).
4
Does the drone hold heading without slow rotation? With yaw stick centered, the drone doesn't slowly rotate over 30+ seconds.
Yaw control is good. Move on.
If rotating: motor balance issue (Section 2) before yaw PID issue (Section 4).
5
Are motors cool to the touch after a 5-min flight? Lightly warm is fine; uncomfortably hot indicates the motors are working harder than they should.
Motors operating in efficient regime; tuning isn't urgent.
If hot: oversized prop (parts.html), undersized motor for weight (calculator.html), or PID gains too high causing constant motor correction.

If your drone passes all five questions: close this page, save it for later. Spend the time you would have spent tuning on flight practice or maintenance instead. The cohort program has graduated alumni who never touched a PID value, and their NDVI imagery is excellent. The defaults work.

If your drone fails one or more questions: identify the most-likely cause from the rightmost column, jump to that section, and work from there. Don't read the whole page top-to-bottom unless you genuinely enjoy this stuff — that path leads to over-tuning.

Section 02 ~30 min inspection · the most-skipped step

Mechanical first.

Most "my drone needs tuning" problems are actually mechanical. Loose motor mounting, unbalanced propellers, FC vibration isolation, frame flex — all of these masquerade as PID issues. You cannot tune your way out of a vibrating drone. Sort the mechanical layer before touching software.

Six mechanical sources of "tuning-like" symptoms, in order of frequency:

Source Symptom Diagnostic Fix
A
Unbalanced propellers Most common single cause of vibration in cohort builds.
High-frequency vibration visible in hover; blurred NDVI imagery; warm motors.
Spin each prop on a balancer; sand the heavier blade slightly. Or replace with new props (cheap; ₱80 each for 5"). See propellers.html for procedure.
B
Loose motor mounting screws One of the four motor mount screws not properly torqued.
Asymmetric vibration; drone tilts or wobbles in one direction; screw might back out further during flight.
Check torque on all 16 motor mount screws. Use Loctite blue if vibration persists.
C
FC mounted hard (no isolation) Some FCs are mounted directly to the frame; others use rubber/silicone soft-mounting.
Vibration in BlackBox logs (if you have them); imagery blur; high gyro noise readings in configurator.
Add silicone grommets or O-rings between FC and standoffs. Most modern FCs come with these; verify they're installed correctly.
D
Bent prop Prop is slightly cracked or warped from a previous crash; spinning produces unbalanced thrust.
Single motor seems to "hum" louder than others; vibration concentrates on one corner of the drone.
Replace the prop. Inspect both sides for cracks. Discard rather than try to fix.
E
Bent motor shaft Bell of one motor wobbles slightly when spinning; usually after a crash on hard ground.
Look at motor bell from the side while spinning slowly; visible wobble means bent shaft.
Replace the motor. Don't try to bend back. Cohort budget allows for one motor failure per cohort.
F
Frame flex / cracked arm Carbon fiber frames develop micro-cracks that aren't visible until you flex the frame.
Drone "feels different" after a hard landing; subtle vibration that wasn't there before; visible hairline crack on close inspection.
Replace the affected arm or frame. Don't try to repair carbon fiber with adhesive — the structure needs to be solid.

The 5-minute mechanical check

Before any tuning work, do this quick inspection:

  1. Power off, props off. Hold each motor by the bell and gently wiggle. No play, no clicking.
  2. Spin each motor by hand (gently). Smooth rotation; no scraping; same resistance across all four.
  3. Check all 16 motor mount screws are tight (use a screwdriver, not just by feel).
  4. Inspect each prop for cracks (hold up to light; cracks appear as bright lines).
  5. Look at the FC mounting — soft-mount grommets present and intact.
  6. Flex the frame arms gently in pairs. No creaking, no give.

This takes 5 minutes. If anything is found wrong, fix it and re-fly before considering any software tuning. About 60% of "tuning problems" we see in alumni Slack are solved at this step alone.

If the mechanical inspection passes and the drone still has issues, then software tuning is appropriate. Move to Section 3.

Section 03 The single biggest software-side gain

Filter setup.

If you're going to make one software change to improve flight quality, make it filter setup — not PID tuning. Filters reduce noise in the gyro signal so the FC can respond to real motion without amplifying vibration. Default filter settings work, but small adjustments can produce noticeable improvements with low risk.

Three filter changes worth making, in order:

1. Enable bidirectional DSHOT and RPM filtering. If your ESCs run BLHeli_32 or BlueJay (most cohort 5" builds after the 2025 ESC upgrade), this combination gives the FC RPM telemetry from each motor, which it uses to dynamically filter motor noise frequencies. The improvement is significant.

  1. In the configurator's Configuration tab, enable Bidirectional DSHOT.
  2. In the PID Tuning tab (Filter Settings), enable RPM Filter.
  3. Save and Reboot. Verify on next flight: smoother hover, less audible motor whine, sharper imagery.

2. Adjust gyro lowpass filter. The gyro lowpass cuts high-frequency noise from the gyroscope readings. Default is usually 250 Hz (PT1 filter). For survey work with cohort default props, 200 Hz is often a slight improvement — slightly more filtering at the cost of slightly more lag. Don't go below 150 Hz; that introduces noticeable response delay.

3. Set up dynamic notch filtering. The dynamic notch filter identifies the strongest noise frequencies in the gyro signal and notches them out. Default settings are reasonable. Only change if BlackBox logs show specific resonance peaks not being caught by the default range.

Filter Cohort default When to adjust Adjustment direction
RPM
RPM filter (with Bidirectional DSHOT) Dynamic; filters the specific frequencies generated by current motor RPM.
ON if ESC firmware supports it (BLHeli_32 / BlueJay).
Should always be ON if available. Bigger improvement than PID tuning for most builds.
GLPF
Gyro Lowpass Filter Cuts high-frequency noise from raw gyro readings.
200-250 Hz, PT1 type.
Lower (more aggressive) if motors are warm or vibration visible. Higher (less filtering) only if motors run cool and you want sharper response.
DLPF
D-term Lowpass Filter Cuts noise specifically in the D term, which amplifies high-frequency signal.
Dynamic, 100-200 Hz range.
Default usually fine. Adjust only with BlackBox data showing D-term noise.
DYN
Dynamic Notch Filter Adaptive notch that follows resonant frequencies.
ON, 3 notches, 100-700 Hz range.
Default is fine. Widen the range if you see resonance peaks outside the default in BlackBox logs.

The biggest single change in this section is enabling RPM filtering on builds that support it. Cohort 02 builds before the ESC firmware upgrade ran without RPM filter; the upgrade and filter activation produced visibly sharper NDVI imagery across the fleet. If your build supports it and it's not on, turn it on.

Filter changes are reversible and low-risk. Make one change at a time, fly briefly, observe the difference, and continue or revert. Don't change multiple filters simultaneously — you won't know which one helped or hurt.

Section 04 Concept; procedure in Section 5

PID basics.

What P, I, and D actually do — written for alumni who don't have a control theory background. Understanding what each gain does is more valuable than memorising tuning procedures; a clear mental model lets you reason about specific symptoms and which gain to adjust.

The PID controller adjusts motor outputs to make the drone follow what the pilot (or autonomous mode) commands. Three terms:

P (Proportional) — proportional to current error. If the drone is rolled 10° but the command is for 0°, P-term applies a correction proportional to that 10° error. Higher P = stronger correction = sharper response.

Too much P: the drone overshoots the target, then overshoots back, then overshoots again. Visible as oscillation. Too little P: the drone responds sluggishly; takes too long to reach commanded attitude.

I (Integral) — accumulates error over time. If the drone has a small persistent error (e.g. centre of gravity off slightly to one side), P-term tries to correct but never fully eliminates the error. I-term builds up and adds correction proportional to total accumulated error, eliminating steady-state drift.

Too much I: oscillation that builds slowly over seconds, "hunting" behavior. Too little I: drone drifts slightly off command and never quite reaches the target — small persistent error.

D (Derivative) — proportional to rate of change of error. D-term anticipates: if error is decreasing rapidly, D-term reduces correction (avoiding overshoot); if error is increasing rapidly, D-term increases correction (catching up faster).

Too much D: amplifies high-frequency noise; the drone jitters or gets "hot motors" from constant micro-corrections. Too little D: the drone overshoots more readily; oscillation amplitude is larger.

A practical mental model

Think of P, I, and D as three different drivers:

  • P is the eager driver — sees the error, reacts now, may overshoot.
  • I is the patient driver — notices small persistent errors and quietly corrects them over time.
  • D is the cautious driver — watches how fast you're approaching the target and slows you down before you overshoot.

A well-tuned drone has all three working together. The eager driver gets you most of the way there fast; the patient driver eliminates the small remaining error; the cautious driver prevents the eager one from overshooting. When the drone misbehaves, ask: which driver is wrong?

Each axis (roll, pitch, yaw) has its own P, I, and D gain values. Most tuning happens on roll and pitch; yaw is usually fine on defaults. The configurator's PID Tuning tab shows the values; INAV defaults are reasonable starting points for cohort default builds.

Typical INAV defaults (5-inch SpeedyBee F405 V4 with 2207 motors and 5×4.3×3 props):

  • Roll P: 45 — Roll I: 80 — Roll D: 30
  • Pitch P: 45 — Pitch I: 80 — Pitch D: 30
  • Yaw P: 45 — Yaw I: 80 — Yaw D: 0 (yaw rarely uses D-term)

These numbers are the cohort default and produce flyable drones. If you're going to adjust, start small (5-10% changes), observe the difference, and don't change multiple values simultaneously.

Section 05 Two paths: data-driven vs by feel

Tuning approaches.

Two real approaches to tuning: with BlackBox data (the rigorous path) and by pilot feel (the field-practical path). Both produce flyable drones. The data-driven approach finds slightly better tunes; the by-feel approach is faster and works without specialised equipment. Pick based on your context, not on which is "more correct."

Approach A: BlackBox-driven tuning. The FC records all flight data (gyro readings, PID outputs, RC inputs, motor commands) to an SD card or onboard flash. You analyse the logs after the flight using PIDtoolbox or similar software, see exactly where the drone misbehaved, and adjust gains based on observed data.

  1. Set up BlackBox. Most modern FCs have an SD card slot or onboard flash. In the configurator, enable BlackBox logging at 1-2 kHz sample rate, log only when armed.
  2. Fly a test pattern. Standard test: hover for 30 seconds, then a series of stick inputs (full pitch forward, full roll left, etc.) for sharp PID stress, then back to hover.
  3. Analyse the log. Open in PIDtoolbox. Look at the gyro vs motor traces. Oscillation peaks, noise levels, response timing — all visible.
  4. Adjust based on data. If you see P-term oscillation at 30 Hz, lower P. If you see I-term hunting at 5 Hz, lower I. If D-term spikes are noisy, increase D-term filtering.
  5. Iterate. Fly, log, analyse, adjust. Two to three iterations typically reach optimal tune for the build.

The BlackBox approach finds objectively better tunes. It's also slow — each iteration is a flight session plus 30 minutes of analysis. Useful for partner orgs running fleet-wide tuning standards or for individual alumni who genuinely enjoy the optimisation work. For most cohort alumni, the marginal gain over by-feel tuning isn't worth the time.

Approach B: Tuning by feel. The traditional approach: fly the drone, notice what feels wrong, adjust based on intuition and the symptoms-to-cause mapping in Section 4, repeat.

  1. Hover and observe. Note what feels off. Oscillation? Drift? Mushy response? Aggressive response?
  2. Map symptom to cause. Use Section 4's framework. Oscillation in roll → P too high. Slow drift after stick centred → I too low. Aggressive overshoot → D too low.
  3. Adjust by 5-10%. Small change. Save. Reboot.
  4. Re-fly. Did the symptom change? Better, worse, or same? Continue or revert.
  5. Stop when "good enough". Don't chase perfection. Drone hovers smoothly, holds heading, photos are sharp — done. Save the config.

The by-feel approach reaches "good enough" quickly. Most cohort alumni use it. The drone won't be optimally tuned for racing-style maneuvering, but for survey work the gap is invisible.

Two anti-patterns worth avoiding

  1. Tuning to the "perfect" tune that doesn't exist. There's no single optimal tune; there are tunes that are "good enough for the use case." Stop when the drone meets your needs, not when some forum post claims a number is theoretically optimal.
  2. Chasing changes between flights. Different battery state, different temperature, different wind — each affects how the drone feels. If a tune feels different one day vs the next, it's probably the conditions, not the tune. Don't chase what isn't there.
Section 06 What we ship and why

Cohort defaults.

The canonical PID + filter configurations for cohort default builds (5A, 7A, 10A). These are starting points — flyable out of the box, refined across multiple cohorts, and the foundation that 85% of alumni never need to modify. The configurations are downloadable from the link at the top of this page.

The cohort default tuning history:

Cohort 01 (early 2024): Used INAV stock defaults for the SpeedyBee F405 V4 + 2207 motors. Drones flew acceptably; some alumni reported "mushy" response. No filter optimisation beyond INAV defaults.

Cohort 02 (mid-2024): Slight P increase (45 → 50 on roll/pitch) based on alumni feedback; otherwise stock defaults. Filter settings unchanged. ~60% of alumni found this preferable; ~40% felt the drone was now too aggressive.

Cohort 02 mid-cohort revision (late 2024): Reverted P to 45 (the original stock default) but enabled BlackBox logging on a sample of drones. Analysis showed gyro noise was higher than ideal. Adjusted gyro lowpass from 250 to 200 Hz. Marginal but consistent improvement.

Cohort 02 post-flight (early 2025): ESC firmware upgrade to BlueJay across the fleet. Enabled bidirectional DSHOT + RPM filter. This was the single biggest improvement in cohort tuning history — visibly sharper imagery across all builds, no PID changes required.

Cohort 03 baseline (current): Stock INAV PIDs for the build (P 45, I 80, D 30 for roll/pitch); RPM filter ON; gyro lowpass 200 Hz; dynamic notch ON with default range. Bidirectional DSHOT enabled. Cohort default config dump captures all of this.

The progression is instructive: most of the gains came from filter setup and ESC firmware, not PID gains. The PID values barely changed across three cohorts. This is consistent with what most experienced FPV pilots will tell you — defaults are usually fine if filters and mechanics are right.

Applying the cohort default tuning to your drone:

  1. Download the config dump for your build (5A, 7A, or 10A) from the link at the top of this page.
  2. Connect your FC to the configurator.
  3. Open the CLI tab.
  4. Type diff all and copy the current output to a backup file (your existing config — saved in case you want to revert).
  5. Paste the cohort default dump into the CLI tab.
  6. Type save at the end. The FC reboots with the cohort default tuning applied.
  7. Pre-arm checklist Phase A (fc-setup.html Section 10). Fly briefly to verify behavior matches expectations.

If the cohort default doesn't fly well on your drone, the cause is usually: (1) non-standard components affecting the build's mechanical characteristics, (2) mechanical issues that the previous tune was masking, or (3) a genuine tuning need for your specific build. Work through Sections 2-5 to identify which.

Sharing your tune back. If you've tuned a build that produces noticeably better results than the cohort default, share the config dump in alumni Slack with notes on what changed and why. We periodically incorporate community-validated improvements into the cohort default. Tuning improvements that travel are improvements; tuning improvements specific to your build alone are personal preferences.

Numbers worth knowing

Six tuning reference numbers.

Quick reference for the values that show up across cohort default builds and the typical adjustments worth knowing.

P 45
Roll/Pitch P
Cohort default for 5" build
I 80
Roll/Pitch I
Standard INAV starting point
D 30
Roll/Pitch D
Lower than racing setups
200 Hz
Gyro lowpass
Cohort tuning, slightly tighter than INAV stock 250 Hz
5–10%
Adjustment step
When changing PID values manually
2 kHz
BlackBox sample rate
Cohort recommendation; supports 250-1000 Hz analysis
Real tuning scenarios

Four cases from cohort alumni.

Concrete cases where alumni faced "I think I need to tune" decisions, and what the actual fix turned out to be. Each illustrates the page's broader theme: most tuning problems aren't tuning problems.

"My drone wobbles in pitch on hover."

Cohort 02 alumnus, 5" build

Symptom: visible 2-3 Hz oscillation in pitch when sticks centered. Wanted to lower P. Actual cause: one motor's mounting screws had backed out slightly during flight (mechanical, Section 2). Tightening the screws and adding Loctite blue eliminated the wobble. PIDs stayed at cohort default. Lesson: always check mechanical first, even when the symptom looks PID-shaped.

"NDVI photos are blurry. Maybe D is too low?"

Partner-org operator, 7" build

Symptom: imagery from 80m altitude lacked detail. Considered D-term tuning. Actual cause: bidirectional DSHOT and RPM filtering weren't enabled on this build (it had been built before the cohort ESC firmware upgrade). Enabling them, no PID changes, produced sharp imagery. Section 3 (filters) is where the gain came from. Lesson: filter setup before PID tuning, every time.

"Drone slowly rotates with yaw centered."

Cohort 03 alumnus, 5" build

Symptom: slight clockwise rotation over 30+ seconds with yaw stick centred. Considered yaw I-term. Actual cause: unbalanced propellers (Section 2). Two of the four props had small chips from a previous landing. Replacing all four props with new ones eliminated the rotation. PIDs stayed at cohort default. Lesson: prop balance is more often the cause than yaw PID issues.

"I want sharper response for demo flying."

Alumna doing exhibition flights at trade shows

Legitimate tuning case. The cohort default is conservative, optimised for hands-off survey work. For aggressive demo flying, P was raised from 45 to 55, D from 30 to 35. Verified with BlackBox logs (Approach A in Section 5). Drone became visibly sharper for demo work. Maintained a separate config dump for survey work vs demo work; switches between them depending on the day. Legitimate use of tuning; correct approach.

Frequently asked

Questions worth answering carefully.

Why does the FPV racing community spend so much time on tuning if defaults are usually fine? +

Different use case, different stakes. Racing pilots fly aggressive maneuvers (split-S, power loops, fast cornering) at high speed where small differences in response timing translate to meaningful differences in lap time and crash frequency. They're operating in a domain where 5% better response actually matters.

Survey work is different. The drone hovers, holds position, captures imagery. None of these tasks are timing-critical at the millisecond level. A "perfectly tuned" drone produces imagery indistinguishable from a "default tuned" drone. The community's enthusiasm for tuning is real, but it's optimised for their use case, not ours.

Borrowing the wrong context's tuning advice is a common mistake. Take racing-tuning videos as entertainment; don't apply their conclusions to survey builds without thinking.

Should I be using INAV's "Auto Tune" feature? +

INAV has an Auto Tune mode that flies a programmed sequence and adjusts PIDs based on observed response. It works, but with caveats: it requires significant open space (the drone flies aggressive maneuvers automatically), it can produce more aggressive tunes than you want for survey work, and the result varies based on conditions during the auto-tune flight (wind, battery state).

For most cohort alumni: don't bother with Auto Tune. The cohort default is good. If you specifically want to tune, by-feel adjustment (Section 5 Approach B) is faster and produces more conservative results.

Where Auto Tune does shine: builds where the components are very different from cohort defaults (custom motors, unusual props), and you're starting from a clearly-wrong baseline. In those cases, Auto Tune gets you to a flyable starting point quickly.

What's the role of frame size in tuning? +

Bigger frames need different PIDs than smaller ones. A 5-inch drone responds quickly to motor commands; a 10-inch drone has more rotational inertia and responds slower. The same PID values that produce smooth flight on a 5-inch can produce sluggish flight on a 10-inch.

The cohort default tunes for 5A, 7A, and 10A reflect this. Generally:

  • Larger frames → lower P and D values, higher I values.
  • Smaller frames → higher P and D values, lower I values.

The downloadable cohort default configs already account for this. If you're transferring a tune from one frame size to another, expect to adjust — same gains rarely transfer cleanly.

Does battery state affect how the drone feels? +

Yes, significantly. Fresh batteries provide higher voltage and lower internal resistance; old or near-depleted batteries provide less. The same drone with the same tune feels different at the start of a battery vs the end:

  • Fresh battery: snappier response (more thrust available, less voltage sag).
  • Late in flight: softer response (voltage sag reduces motor output during corrections).

This is normal. Don't tune for one battery state and expect it to feel the same across the full flight. Cohort default tunes are calibrated to feel acceptable across the whole battery cycle, not optimal at any one point.

Older packs (50+ cycles) feel particularly different from new ones. If a drone's behavior degraded gradually, suspect battery age before tune drift.

Can I copy someone else's tune from alumni Slack? +

You can; whether it'll work well depends on how similar your build is to theirs. Tunes transfer cleanly when:

  • Same frame size (5", 7", or 10").
  • Same motor model and KV.
  • Same prop diameter and pitch.
  • Same FC and ESC firmware versions.

If all four match, the tune should transfer with minimal adjustment. If any differ, expect to need to adjust — the tune is optimised for the original builder's specific combination, not yours.

The cohort default tunes published from this page are tested across the full cohort fleet, so they handle the natural component variations within cohort defaults better than a one-off tune from a single alumnus would.

What if my BlackBox logs show specific noise frequencies — what do I do with that? +

If you're at the level of analysing BlackBox FFT plots and seeing specific resonance frequencies, you're in territory beyond what most cohort alumni reach — and frankly beyond what this page covers in depth. The general framework:

  • Resonance peaks below 100 Hz: usually mechanical (frame flex, soft mount issue). Mechanical fix.
  • Resonance peaks 100-300 Hz: prop or motor noise. RPM filter should catch these if enabled; if not, dynamic notch range may need widening.
  • Resonance peaks 300+ Hz: usually motor commutation noise. Increase D-term lowpass filtering or check ESC firmware/protocol.

For more depth on BlackBox interpretation, the BetaFlight community has excellent resources — Joshua Bardwell's tuning videos cover this thoroughly. INAV's BlackBox is similar enough that the BetaFlight resources apply with minor translation.

Is there a "cohort default" tuning workshop or training session? +

Cohort 02 included a half-day tuning session in Week 5 covering Sections 1-3 of this page. Cohort 03 will likely cover the same material with the addition of BlueJay/RPM filter activation. The deeper PID and BlackBox material (Sections 4-6) is left for self-directed alumni follow-up — not all alumni need it.

Partner orgs running their own programs sometimes ask whether they should include tuning in their curriculum. The cohort recommendation: yes, but only at the Section 1-3 level. Mechanical inspection and filter setup deserve curriculum time. PID tuning specifics rarely do.

What's the relationship between tuning and pilot skill? +

For survey work: pilot skill matters far more than tune. A skilled pilot on a default tune produces excellent imagery. An unskilled pilot on a perfect tune still produces mediocre imagery. Time spent flying is more valuable than time spent tuning, by a wide margin, for cohort alumni.

The exception: alumni doing aggressive demo or exhibition flying where stick precision and response timing matter. There, tune and pilot skill compound — a better tune on a skilled pilot's hands produces better results than either alone. But that's a minority use case.

If you're considering whether to spend a Saturday tuning vs flying, the answer for most cohort alumni is fly. The tune is fine.