Status
The Drone Pilot Brief is standing up a Hardware & Sensor Testing Lab for commercial uncrewed aircraft systems (UAS), sensors, and related payloads.
This page states what the Lab is building toward, how published field audits will be labeled, and how manufacturers can inquire. It is not a claim that DPB already operates a finished independent evaluation authority or a finished testing facility running ASTM, ASPRS, IEC, or NGS-class programs at scale.
Published field audits will meet the site’s Review Methodology. Pages that do not carry those notes are analysis or how-tos, not Lab test reports.
Gate (read first): Review Methodology & Testing Protocol
In short:
- We do not publish a testing protocol we have not used.
- When a hardware or software review runs, the page states what was tested (model, firmware, payload); how it was sourced (purchased, loaned, supplied); how long it was flown or processed; what we measured and what we did not; and whether the unit was returned.
- Loaner hardware does not buy a positive review. Manufacturer claims stay attributed to the manufacturer.
- If a page lacks those notes, it is not a DPB field audit.
Also see: Editorial Standards & Verification Policy
Why a Lab page exists
Commercial procurement still runs on marketing claims and short unboxings. Part 107 operators, survey firms, and utility flight leads need clearer sourcing and measurement notes when DPB publishes hardware or sensor work.
This Lab stand-up exists to make that bar public and enforceable on DPB’s own pages — not to franchise unfinished “benchmark” language as completed Lab output.
Focus areas (building toward)
These are domains the Lab is standing up around. Citing a standard below means we treat it as a reference target when a future field audit uses that standard — not that DPB currently runs a certified ASTM/ASPRS/IEC facility program for every item listed.
1. GNSS and geodetic precision
Field work on differential GNSS, multipath, and correction pipelines (local base vs network NTRIP and related setups). When a field audit ships, it will name the receivers, airframes, firmware, sites, and what RMS or fix metrics were and were not measured.
Reference targets when used: ASPRS positional accuracy classes — only if the audit actually applies them and says so.
2. Radiometric and optical sensors
Thermal and optical teaching and, when audited, measured spot-size / IFOV math, NUC/drift notes, and shutter-readout behavior on named payloads.
Reference targets when used: IEC 62446-3 (PV), ASTM C1060 (where applicable) — attributed and only when the page’s methods match.
3. Flight physics and power
Headwind/crosswind and battery-endurance teaching for mission planning. Field audits in this lane will use named airframes, logged envelopes, and stated limits — not brochure drag coefficients presented as Lab proof.
4. C2, cellular, and Remote ID
Link behavior, latency, and Remote ID broadcast health when DPB has actually measured them on named gear.
Reference targets when used: ASTM F3411 and 14 CFR Part 89 — as applicable law/standard citations, not as a claim that DPB runs a full RF certification lab today.
Related operational analysis (not Lab field audits)
These live pieces are operational analysis and how-tos, not DPB field audits, until they carry full Review Methodology notes. They are not Featured Testing Lab Benchmarks.
They do not currently include the notes a field audit requires: named model and firmware, purchased / loaned / supplied, hours flown or processed, what was measured and what was not, and whether the unit was returned.
- GNSS RTK vs Network NTRIP Benchmark: Real-World Accuracy — multipath / correction-pipeline analysis; not a Lab field audit under current methodology notes.
- Drone Thermal Resolution: 320 vs 640 Radiometric Cores — SSR / IFOV math guide; not a Lab field audit under current methodology notes.
- Rolling vs Global Shutter: Drone Photogrammetry & Cinema — sensor-readout analysis; not a Lab field audit under current methodology notes.
Related house checklist (how-to / SOP, not a certified Lab verification program): DPB Field Benchmark SOP: Pre-Flight Hardware Checklist
When a page later ships with full methodology notes, it may be listed here as a field audit. Until then, analysis stays analysis.
Manufacturer and OEM inquiry protocol
We welcome hardware evaluation inquiries from uncrewed aircraft manufacturers, sensor developers, and payload teams.
Contact (house email only): editor@thedronepilotbrief.com
Send review inquiries, technical packets, and review-unit logistics to that address.
Commitments for evaluations that publish
When DPB publishes a hardware or sensor field audit, the page will follow Review Methodology:
- Editorial autonomy: no paid placement or manufacturer pre-publication approval rights over the review outcome.
- Disclosure: model, firmware, payload; purchased / loaned / supplied; hours flown or processed; what was measured and what was not; whether the unit was returned.
- Loaners do not buy a positive review. Manufacturer claims stay attributed.
Evaluation length and return logistics are agreed case by case. This page does not promise a fixed 30-to-60-day program or universal telemetry/control-monument packages as if that pipeline is already running at full Lab capacity.
If a published page lacks methodology notes, read it as analysis or how-to — not as a DPB field audit.
Page status: Lab standing up. Aligns to Review Methodology (updated 3 Sep 2026) and Editorial Standards. Hub rewrite version testing-lab-hub-standup-2026-09-30-v1.1.