MegaDock is a 6,900 lb installation with a robotic launch-and-recovery system, climate control, hardwired networking and an electrical load that can reach roughly 18 kW. It can store five F10 aircraft and launch or recover them without a runway or crew at the site. That changes the engineering problem. A long-range drone program built around this system is no longer mainly an aircraft purchase. It is a small piece of remotely operated site infrastructure.
That distinction matters for utilities, public-safety agencies and other operators considering persistent remote coverage. The aircraft determines what can fly. The dock, communications, power, maintenance plan and regulatory approval determine whether it can keep flying.
Robotic recovery is the enabling feature
Fixed-wing aircraft are attractive for long corridors and large search areas because their aerodynamic efficiency can support more range and endurance than a comparable multirotor. Recovery is the awkward part of unattended operation. A conventional fixed-wing aircraft may need a runway, net, parachute, belly-landing area or people on site.
Skydio's answer is Robotic Takeoff and Landing, or RTOL. MegaDock uses a robotic arm to launch and recover F10. Skydio says an aircraft can be airborne about 20 seconds after a launch command. Between missions, aircraft are stored and charged inside the climate-controlled enclosure.
The dock can hold five F10s. Skydio describes a configuration in which three can operate while two remain at the dock. This makes fleet availability a more useful metric than the endurance of one aircraft. For a repeated patrol or response mission, the operational question becomes whether another charged aircraft can take over before the first must return.
That is closer to designing a service than planning a sortie.
The installation requirements are substantial
MegaDock is not a box that can simply be placed on a roof next to an Ethernet jack.
With its fenced launch-and-recovery area, Skydio specifies a footprint of 14.5 by 20.75 ft and a height of 9.5 ft. Total weight is listed at 6,900 lb. The technical specifications call for 10 ft of clearance around the installation for HVAC operation, cargo-door access and maintenance. The site must also meet a stated level requirement.
Electrical requirements are closer to industrial equipment than to a conventional drone charger: 200 to 240 V AC, a dedicated 100 A breaker and a published peak load of 18.033 kW. MegaDock has no built-in battery backup. Skydio tells customers that sites requiring backup power should provide a generator or battery system upstream.
Networking is similarly explicit. The dock requires hardwired Cat6 Ethernet. Skydio's published recommendations scale from 130 Mbps for one aircraft to 400 Mbps for five, with lower stated minimums. The vendor recommends sizing the connection for the eventual fleet rather than the initial deployment.
These numbers shift site selection upstream in the procurement process. A theoretically ideal launch point can be a poor installation site if utility power is expensive to extend, the network path is fragile, flood exposure is unacceptable, maintenance access is awkward or backup power cannot support the required duty cycle.
Availability is a system calculation
Skydio's F10 technical specification lists a maximum flight time of 120 minutes and a 10-to-90% charge time of 45 minutes. Its current F10 FAQ describes "up to two hours total mission time" as about 90 minutes of flight paired with a 30-minute charge cycle. Those two public descriptions are not identical, so an operator sizing a real deployment should obtain the mission-profile and charging assumptions behind the numbers rather than treating a headline endurance figure as a duty-cycle guarantee.
Wind and weather add another boundary. The F10 specification lists a 27 mph launch/landing wind limit and IP55 protection. MegaDock itself is rated for much higher survival winds when anchored, but that does not mean aircraft can launch in those conditions. Infrastructure survival and flight availability are separate requirements.
The same distinction applies to power and networking. A dock may remain physically intact during an outage while being unable to dispatch an aircraft. A working internet connection may still be unsuitable if the upstream path cannot sustain the required service or if a local failure removes both command connectivity and media transfer.
For a serious remote program, availability should therefore be modeled across the whole chain: aircraft readiness, charged-aircraft count, robot availability, HVAC, site power, backup power, network connectivity, cellular coverage along the route, weather and remote-operations staffing.
5G extends reach, but it does not erase communications engineering
F10 uses Skydio Connect SL in the 2.4 and 5 GHz bands for launch and landing, while the published specifications describe Connect 5G as providing range wherever cellular coverage is available.
That architecture is sensible for a long-range aircraft because a local radio link cannot economically provide uniform coverage across every intended corridor. It also means the operational envelope inherits the strengths and weaknesses of the cellular network.
The FAA's proposed BVLOS framework makes communications coverage an explicit operational concern. Its fact sheet says operators would identify their operating boundaries and ensure adequate communications coverage, with procedures for loss of communications. The proposal is not yet the final rule, but it shows why "has 5G" is not a complete communications case.
A route survey for this class of system should be interested in more than a carrier coverage map. The relevant questions include service at operating altitude, handover behavior, dead zones, congestion, fallback behavior and what the aircraft does when the wide-area link disappears.
Autonomy does not remove the operating approval
The product is clearly designed for missions that can extend well beyond a pilot's direct visual range. Current U.S. Part 107 rules still generally require the drone to remain within sight unless the operator has the necessary authorization. The FAA continues to describe more complex operations as requiring additional certification or approval while its broader BVLOS rule remains proposed.
This is an important procurement boundary. A 30-mile-radius aircraft and an unattended dock do not themselves confer permission to use that radius.
The proposed BVLOS rule would create a more scalable framework covering operating approvals, aircraft manufacturing, separation, security, reporting and record keeping. It also contemplates access-controlled launch sites and communications-loss procedures. Those details align closely with the operational problems a permanently installed system must solve, but operators should plan against the rules and approvals that actually apply when they deploy.
Maintenance now includes HVAC and a robot arm
MegaDock's maintenance model is another clue that this category is becoming facilities infrastructure.
Skydio says customers inspect the dock and aircraft every six months or when prompted by a health alert. Skydio performs annual service. Specialized third parties may handle HVAC, garage-door and robot-arm work that falls outside normal aircraft maintenance.
The dock's technical specification lists a five-year service life and annual service frequency.
For an operator accustomed to maintaining batteries, propellers and airframes, this adds different failure domains and contractors. A fleet manager may need to coordinate an electrician, network team, facilities staff and specialized mechanical service before an aircraft technician touches the drone itself.
That also changes spares strategy. Keeping a spare aircraft at the site cannot recover availability from a failed robotic arm, failed HVAC system, severed network link or site power fault. Redundancy has to be placed where failures can actually occur.
The useful comparison is no longer drone versus drone
F10's 100 mph maximum speed, 30-mile claimed radius and visible/thermal payload will attract specification comparisons with other aircraft. Those comparisons still matter, especially once independent operational data is available.
For docked long-range operations, they are incomplete.
A better comparison includes the installed system: how many aircraft a site can support, dispatch latency, recharge behavior, site power, network requirements, backup options, maintenance responsibilities, weather limits, communications architecture, regulatory path and the cost of keeping the service available.
Skydio has made that systems problem unusually visible because MegaDock is physically large and its infrastructure requirements are published. The underlying lesson applies beyond one vendor. As civilian drones move toward unattended BVLOS inspection and response, the aircraft becomes one replaceable part of a distributed operating system.
That is the real significance of MegaDock. It makes fixed-wing autonomy look less like a drone accessory and more like something a facilities engineer, network architect and aviation operations team have to design together.