Support & Warranty

DRAFT — wording approved in principle 28 Jul 2026; released with the manual at v1.0. The data-logging requirements below are operative now.

Support

Rocket Fast Drones Pty Ltd — support@rocketfastdrones.com. We are a small, fast-moving team: talk to us early, including before you attempt a repair you are unsure about. When contacting support, include the aircraft serial number (label at the battery power connector), the firmware/manual version, and — for any in-flight issue — the flight logs (below).

Flight data — required configuration

Flight data is how faults are found, fixed, and covered under warranty. Two records exist:

1. Onboard logs — the autopilot logs every flight to its SD card (.ulg files). Do not delete them; after any incident, preserve the card (see the post-crash procedure in Flight Operations).
2. GCS telemetry logs — configure QGroundControl to log and save all telemetry, every flight (Application Settings → enable telemetry logging). If an aircraft is lost or destroyed, the GCS log is the only record that survives — operating without GCS logging enabled may make a warranty claim unassessable.

Any warranty claim requires the relevant flight data (onboard SD logs where the aircraft is recovered; GCS telemetry logs always). RFD analyses the logs to establish the cause of a failure.

Downloading flight logs

• Via QGC: Analyze Tools → Log Download — lists the onboard .ulg files; prefer a USB connection (faster and more reliable than downloading over the telemetry link).
• Directly from the SD card: logs live under /log/<date>/ as .ulg files — copy the whole folder.
• GCS telemetry logs: saved by QGC where its telemetry-logging setting points — include the session’s file when reporting an in-flight issue.
• A file that downloads corrupt usually re-downloads fine — see Troubleshooting #9; card care and formatting: SD Card Formatting.

Warranty (indicative — subject to your sales agreement)

• RFD warrants each aircraft against defects in materials, workmanship, and design for 12 months from delivery, unless your sales agreement states otherwise.
• If the logs show the cause was an RFD defect, RFD will repair or replace at RFD’s cost.
• Not covered: operation outside this manual’s limitations or procedures; pilot/operator error; crash damage from causes not attributable to a defect; force-arming past a failed pre-arm check; non-approved batteries, propellers, parts, firmware or parameter changes; weather beyond the published limits; batteries and other consumables (wear items) after first use; cosmetic wear.
• Claim process: report within 7 days · provide serial number, description, photos, and the flight data above · quarantine the hardware unaltered until RFD advises (no teardown, no repair, no re-flight) · RFD determines the cause from the data and advises the remedy.
• Unauthorised modification, or refusal to provide flight data, voids the claim.

Our warranties operate alongside the Australian Consumer Law: our goods come with guarantees that cannot be excluded, and nothing in this manual limits any right or remedy you have under that law.