On This Page
What the dock actually automates
Treat the system as several connected parts: aircraft and payload, landing
enclosure and charger, site power and communications, flight-management
software, and the people responsible for operation and maintenance. Skydio's
Dock for X10 FAQ describes this combination
of remote flight software, site preparation, training, and servicing. The
enclosure alone is not the operating capability.
A typical workflow accepts a mission, checks readiness, opens the enclosure,
launches the aircraft, executes the route, recovers the aircraft, and prepares
for another flight. The exact division of responsibility varies. DJI's
wayline-management documentation,
for example, documents interfaces for issuing, executing, canceling, and
reporting the progress of flight tasks. An interface to request a mission does
not establish who is authorized to release it.
Ask the supplier to identify which decisions are automatic, which require a
remote pilot, and which require a person at the site. Include launch approval,
weather changes, an obstructed landing area, loss of communications, and return
to service after maintenance. Specify the alternate recovery location and who
can reach a stranded aircraft. Record the supported aircraft, payload, firmware,
and software configuration together so that a later component change does not
silently invalidate the demonstration.
For U.S. operations under Part 107, the FAA identifies
beyond-visual-line-of-sight flight and one pilot operating multiple small
aircraft as activities requiring relief from the relevant rules. A dock purchase
is not that relief. Have the operator identify the applicable approval and its
staffing and operating conditions before using remote supervision or multiple
docks in the business case. See the FAA's
Part 107 waiver guidance.
Check the site and the full mission cycle
The installation survey should cover the landing approach, nearby obstructions,
mounting and service access, electrical supply, drainage, environmental
exposure, and network paths. Obtain a site-specific drawing and name the party
responsible for each preparation task.
Skydio's
Dock for X10 operational-readiness guide
calls for a minimum 20 Mbps upload and download per dock, with 100 Mbps in each
direction preferred, and latency below 100 ms. These are that system's
requirements, not a universal dock standard. Test the proposed site connection
while other users and workloads are active. The publication's explanation of
drone bandwidth for control, video, and payload data
helps separate the traffic that must remain timely from files that can transfer
later.
Separate standby protection from flight limits
A closed enclosure's weather resistance does not describe the aircraft's ability
to launch, land, or collect useful imagery. Skydio's
technical specifications
distinguish X10 operation in precipitation up to 0.25 inches per hour from dock
standby protection at 4 inches per hour. They also identify a 12 m/s
launch-and-landing wind limit. These are manufacturer ratings for that system,
not permission to operate in every combination of those conditions.
Ask for separate limits for storage, charging, launch, flight, and recovery.
Establish how the operator checks conditions along the route as well as at the
dock, and what happens when conditions deteriorate before the aircraft returns.
Include contamination and cleaning requirements for a dusty, coastal, or
industrial site rather than treating the weather rating as a maintenance
exemption.
Measure readiness for the next useful mission
DJI lists a 27-minute Dock 3 charging time measured from 15% to 95% with the
aircraft powered off at 25°C. Its
support specifications also state
that backup-battery operation after a power outage does not support aircraft
charging or air conditioning, among other functions. Neither figure establishes
continuous mission availability.
Have the supplier demonstrate the interval between two representative missions,
including recovery, thermal management, charging, checks, and any transfer that
blocks the next launch. Identify which activities overlap. Do not add every
duration as though they occur in sequence, or assume every activity runs
concurrently. Then determine what is still possible during a site power outage
and what requires restoration or a visit.
Specify the data you will accept
Write the deliverable before selecting the camera or software package. For
recurring visual inspection, define the asset identifiers, views, timestamps,
and detail that must be visible. For temperature-based work, request
measurement-capable thermal files and the settings needed to interpret them. For
mapping, specify the coordinate reference, required accuracy evidence, and
export format. These are proposed purchase requirements; have the supplier
demonstrate the exact output in your own receiving software.
A useful data handover should distinguish original captures, processed products,
and operational records. Request sample files, the mission identifier that joins
them, retention and deletion rules, and the method for recovering an incomplete
upload. A dashboard screenshot is insufficient to prove that your team can
retrieve and reuse the underlying data.
There is a practical reason to test the result separately from successful
flight. A
2026 field study of marine-megafauna surveillance
compared remotely operated, pre-programmed dock missions with locally piloted
flights. Reviewing recorded footage found animals missed during live observation
in both groups. The remote missions were supervised by a pilot; this was not a
test of autonomous AI detection. Its coastal findings do not predict industrial
defect detection, but they illustrate why collecting video and finding the
target are separate outcomes.
For your trial, choose representative targets and have the person who will use
the result assess the output. Agree the minimum visible detail, acceptable
measurement error where relevant, and delivery deadline before flying. Include
known difficult cases and record missed targets, unusable captures, and repeat
flights. The
six levels of drone-inspection evidence
can help establish whether the job requires a visual observation, a measurement,
or stronger support for a decision.
Make the integration demonstration do real work
DJI's Cloud API overview identifies
MQTT, HTTPS, and WebSocket as underlying protocols for connecting supported
systems to third-party cloud platforms. That describes an integration route. It
does not establish that a particular enterprise application already has a
working connector.
Require the demonstration to begin in your business application and finish in
its normal work queue. For example, a maintenance request should lead to an
authorized mission, an identifiable set of captures, and a result attached to
the correct asset. Agree how duplicate requests, cancellation, delayed files,
and rejected missions appear to the operator. Check the purchased software tier
and supported versions, including any separately licensed connector.
Treat the control path and the data-export path as separate requirements.
Establish who can create, approve, alter, and stop missions; how permissions are
removed; and which actions remain in an exportable audit log. Ask where imagery,
telemetry, and backups reside, who can access them, and what happens to stored
data and flight capability if a subscription ends.
For interrupted connectivity, ask for a documented state sequence and a
supervised demonstration using the supplier's approved procedure. It should show
the operator's alert, the aircraft's configured response, file retention, and
the conditions for resuming service. Two network connections deserve credit for
resilience only after their shared dependencies and failover behavior have been
examined.
Compare lifecycle cost per usable result
Request quotations against the same mission, staffing arrangement, contract
term, and deliverable. Separate the aircraft and dock from installation,
software, integration, data processing, and service. Keep scheduled maintenance
distinct from fault recovery and clarify who pays for travel, access equipment,
shipping, replacement units, and excluded damage.
The servicing arrangement matters because the system remains physical equipment
at a site. Skydio's FAQ, for example, describes recurring minor and major
service as well as customer tasks such as propeller replacement and light
cleaning. Use the proposed contract's actual scope and exclusions when
estimating costs, rather than assuming remote operation removes local work.
For a chosen ownership period, use this undiscounted comparison:
Total ownership cost = equipment + installation + software and connectivity +
integration and processing + staffing and training + maintenance and recovery +
retirement costs − residual value.
Cost per accepted deliverable = total ownership cost ÷ deliverables that meet
the agreed quality and delivery-time requirements over that same period.
These are budgeting formulas, not quoted market prices. Use one currency and
price basis, state the period, and avoid counting bundled service twice. Include
battery and aircraft replacement where the supplier's lifecycle assumptions
require them. Forecast completed work after weather cancellations, outages,
servicing, and rejected outputs, and show the assumptions separately from
measured trial results.
Compare the dock against the existing way of completing the same job. A
regularly visited fixed facility may justify permanent infrastructure. An
occasional inspection across changing sites may favor a traveling crew or
contracted service. The deciding issue is whether repeated usable results
justify the installation and continuing support burden.
Put these demonstrations in the purchase agreement
Use the table to turn a sales claim into a concrete demonstration. The tests
below are editorial recommendations derived from the cited system documentation
and workflow limitations, not reported product-test results. Set the required
outcomes with the supplier and the people who will operate and use the system.
Scroll horizontally to compare all columns.
Make unresolved demonstration items conditions of acceptance, with
responsibility and a remedy agreed before purchase. Buy when the proposed
configuration can complete the job at the intended site, deliver data your team
can use, and recover from foreseeable interruptions at a cost the organization
can support.
Source notes
Last checked: September 8, 2026.
