Inspired Flight IF800 remote operations: an open-autopilot Blue UAS workhorse for LiDAR and survey crews

The Inspired Flight IF800 Tomcat is a US-built quadcopter that carries up to 3 kg of sensor for up to 54 minutes, on a CubePilot Cube Orange+ running ArduPilot Copter. It is on the Blue UAS Cleared List, and programs that need a heavier, longer-flying Blue aircraft for LiDAR, mapping cameras or EO/IR inspection look at it alongside the IF1200 and Freefly's Astro. The open autopilot is the IF800's main difference from closed enterprise drones. You get standard MAVLink, standard ground stations and documented failsafes. You also take on configuration choices that a closed system would make for you, and those choices decide how safe a long or remote flight is.

How an IF800 is flown

Inspired Flight's IF800 page does not describe LTE or a cloud flight-control path, and there is no dock. In practice the IF800 is a field aircraft: a pilot on site flies it, and a remote team supports the flight. A team that wants to supervise an IF800 over a network would need its own MAVLink-over-IP setup, validated with Inspired Flight and covered by its approvals.

The failsafes an operator owns

On a closed drone, the maker decides what happens when the link drops. On ArduPilot, much of that is a parameter. ArduPilot lists radio, battery, GCS, EKF, dead-reckoning, vibration and terrain-data-loss failsafes, plus crash check, parachute and an independent watchdog. Two details matter most for remote and long-range work:

Splitting the work: field pilot and remote team

With several crews working at once, the remote side is where one-to-many actually happens: one planner and reviewer supporting several field pilots. The aircraft side stays one pilot per aircraft unless an FAA waiver allows more, since 14 CFR 107.35 bars one person from acting as remote pilot for more than one aircraft at a time.

Planning a LiDAR or corridor mission

Heavy-lift survey flights fail quietly: the aircraft flies fine and the dataset is unusable. A planning standard prevents that. For each job, the mission package should fix the target point density or ground sample distance and derive altitude, speed and line spacing from it; set overlap and cross-lines for LiDAR calibration; place launch and landing points with clear approaches; mark where the aircraft will be farthest from the pilot and what the link margin is there; and state the battery plan, including the reserve at which the pilot ends a line early. The remote planner builds it, the field pilot reviews it on site against what they can see, and both sign off before the first takeoff.

Airspace and observers belong in the same package. Long corridor jobs tempt crews to let the aircraft drift beyond what the pilot can see. Under Part 107 that needs a waiver, and any waiver comes with its own conditions on visual observers, altitude and traffic detection. Where observers are used, the plan names their positions along the corridor, how they talk to the pilot, and the phrases they use to call traffic or a hazard.

Latency and range

Herelink's listed 110 ms video delay is low for a long-range link and fine for flying survey lines and framing inspection shots from the field. That number is for the radio link only. Anything relayed to a remote viewer over the internet adds its own delay and can only support observation and comment, not control. Our latency guide covers where those limits fall.

Data from an IF800

Agree the deliverables before the first flight: point cloud format and density, orthomosaic resolution, thermal export, and how each file is tagged by site, asset and mission. On an open platform the payload often comes from a third party, so the delivery standard has to come from the program, not from the aircraft maker.

IF800 or IF1200?

The IF1200 is the heavier sibling: up to 8.6 kg of payload, a 24.9 kg maximum takeoff weight, up to 43 minutes of flight and a higher wind rating of 12 m/s sustained and 15 m/s gusts. It flies on the same Cube Orange+ autopilot, with dual Here3 GNSS. The IF800 carries less, 3.0 kg, but flies longer, up to 54 minutes, and is easier to transport and launch. For a single survey LiDAR or a mapping camera, the IF800 is usually enough. For heavy LiDAR, dual payloads or windier sites, the IF1200 is the one to look at. For a lighter Blue UAS mapping aircraft, compare the Freefly Astro.

What a good IF800 pilot watches for

Regulatory notes, as of October 2026

UAV Coach lists the IF800 and IF1200A on the Blue UAS Cleared List in its August 2026 check, and Inspired Flight shows Blue UAS, Green UAS and NDAA marks on the IF800 page and says its aircraft are engineered, assembled and supported in the US. For BVLOS corridor work, the FAA's Part 108 rule has been at OIRA since July 10, 2026 with no firm publication date, per PickDrones, so programs still fly under individual waivers. None of this is legal advice.

Switching a crew from a closed drone to the IF800

Pilots coming from DJI or other closed systems usually know how to fly; what they need is the platform. On the IF800 that means learning the Herelink and GS-ONE workflow, ArduPilot flight modes and what each failsafe will do, how the payload is powered and controlled over the Pixhawk Payload Bus, and how PilotGo and Elevate record the work. Budget training flights with the real payloads before production, and run lost-link and low-battery drills until the responses are automatic. Our remote drone pilot careers page describes the skills we look for.

How RoboPilots works with IF800 programs

Your field crews fly the aircraft on site. We train a dedicated remote group of Part 107 certified pilots and planners on your IF800s, your payloads, your failsafe standards and your site types, and the same group stays on your program.