MotorBytes covers drones, motorcycle tech, electric vehicles, and the gadgets that tie them together. This page explains how the coverage gets made: where the facts come from, who checks them, and what happens when we get one wrong.
How we research
MotorBytes is a research-based publication. We don’t fly every drone or ride every motorcycle we write about, and we won’t pretend otherwise. Articles are built from primary documents: manufacturer spec sheets and manuals, regulator filings and rulemaking from the FAA and EASA, recall databases, and reporting from established outlets. Where real-world experience matters, things like actual range or firmware quirks, we draw on documented owner reports and long-term reviews, and the article says so. Buying guides follow the same rule: a recommendation has to trace back to documented specs and owner feedback, not vibes.
Sourcing and attribution
Every specification, price, and date is checked against a named source before publishing, and that source is linked in the text where the claim appears. You won’t find “studies show” or “experts say” here. If we can’t name the source, the claim doesn’t run. Prices and rules change fast in this space, so time-sensitive claims carry a date (“as of June 2026”) instead of quietly going stale.
How we use AI tools
Drafts may use AI assistance. Every fact in a published article is verified by a human against the named sources above before it goes live. We don’t publish raw model output, and we never let AI invent quotes, benchmarks, or owner anecdotes. The research, the judgment calls, and the responsibility for errors stay with us.
Independence
No manufacturer pays for coverage on MotorBytes, and none sees an article before it publishes. Press access, review units, and ad spend buy exactly nothing in our articles. If we ever use affiliate links, they’ll be disclosed in the article where they appear, not buried on a separate page.
How to report an error
Send the article URL and the claim you believe is wrong through our contact page. We check it against the original source and fix what needs fixing. Substantive corrections are noted in the article itself, with a date; we don’t silently rewrite history. Most correction reports get a reply within 2–3 business days.