How Drone Delivery Works: From Order to Handoff

One order, several linked decisions

Imagine a customer ordering a small parcel from a nearby distribution point. The system does not begin by asking only, “Can the drone fly there?” It has to answer a chain of more specific questions: Is the item eligible for aerial transport? Does the aircraft have enough capacity after accounting for its battery and equipment? Is there a safe and permitted route? Can the destination accept a delivery? And what happens if the answer to any of those questions changes before arrival?

That chain connects warehouse processes, flight planning, airspace compliance, aircraft control, customer communication, and proof of delivery. The customer may see a simple status update; the operator manages a mission with distinct checkpoints and decision-makers.

• Order preparation: Verify the parcel, destination, and delivery conditions.
• Mission planning: Check aircraft suitability, route, weather, and airspace.
• Launch and flight: Complete checks, depart, and monitor the aircraft.
• Handoff: Deliver to an approved location or use a defined alternate plan.
• Closeout: Record the outcome, return or recover the aircraft, and review any exceptions.

Each stage can prevent a flight. That is not necessarily a failure of the system: declining an unsafe or noncompliant mission is part of operating it responsibly.

Step 1: Check the order and the parcel

Before a drone is assigned, the delivery system needs reliable information about what is being carried and where it is going. A parcel’s weight matters, but so do its shape, packaging, center of gravity, and method of attachment. A light object with an awkward profile can be harder to carry than a compact parcel of the same weight. A loose strap or poorly secured container can affect the aircraft’s stability or become a hazard.

Operators therefore define what their aircraft and service can accept. A package must fit the aircraft’s payload rating and attachment design, and the aircraft must remain within the applicable operating weight limit. Under Part 107, a small unmanned aircraft generally must weigh less than 55 pounds at takeoff, including everything attached or carried. That limit is not a promise that any aircraft can carry a 54-pound parcel: the aircraft’s own weight, manufacturer limits, battery needs, and operating conditions all constrain the usable payload.

Order eligibility can include conditions beyond mass. The system may reject goods that are prohibited, fragile, temperature-sensitive, or unsuitable for unattended placement. It may also require a customer to select an approved drop point, confirm access, or provide instructions for a secure handoff. These rules reduce the chance that an aircraft reaches the right address but cannot complete the delivery safely.

Packaging is part of the aircraft interface. The parcel may be secured in a compartment, attached to a release mechanism, or lowered using a tether, depending on the aircraft and approved operating procedure. These approaches create different operational questions: Can the package be released without striking a person or obstacle? Is it stable in wind? Can the aircraft depart without dragging or catching the load? The mission plan has to match the actual delivery hardware, not a generic idea of a drone carrying a box.

Step 2: Confirm the destination and handoff

A delivery address is not automatically a usable landing or drop location. The operator needs to know what the aircraft is expected to do at the destination: land, release a package to a designated area, or lower it from above. Each method has its own requirements for clearance, people, obstacles, and customer access.

A suitable delivery point should be identifiable and available when the drone arrives. Trees, overhead wires, parked vehicles, roof edges, and temporary activity can change whether a location is usable. So can people. A planned drop into a private yard, for example, may be unsuitable if the area is occupied, the release zone is too small, or the aircraft cannot approach without crossing an unacceptable hazard.

The customer experience is tied to this operational decision. A notification may explain when to expect the aircraft and where the parcel will be placed. A service might require the customer to collect the package promptly, keep pets or other people away from the handoff zone, or select a different location if conditions change. These instructions are not decorative app copy; they help establish a predictable endpoint for the flight.

Operators also need a fallback. If the aircraft cannot safely deliver, the mission may return to its launch site, divert to an approved location, or be handled through another delivery method. Which option is available depends on the aircraft, route, permissions, and operating procedures. A responsible plan defines the decision before the aircraft is airborne.

Step 3: Build a route that works in real airspace

Route planning is more than drawing a straight line between a depot and a customer. The operator has to consider the aircraft’s performance, obstacles, local airspace, launch and landing sites, weather, and the rules that apply to the particular operation. A route that looks short on a map can be unusable if it crosses a restricted area, passes near an airport, or cannot be monitored as required.

Under FAA Part 107, airspace authorization may be required for operations in controlled airspace. Operators must identify the airspace along the route and obtain the necessary authorization before flying where it is required. They also need to comply with restrictions such as temporary flight limitations and other applicable notices. Permissions for one location or mission do not automatically authorize flights everywhere else.

Weather can change the route’s feasibility even when the airspace is clear. Wind affects energy use and stability; precipitation, visibility, temperature, and gusts can affect aircraft performance and the ability to complete a safe delivery. Operators set limits based on aircraft capability and their procedures. If the forecast or observed conditions exceed those limits, delaying or cancelling the flight is the appropriate response.

Under the ordinary Part 107 visual-line-of-sight rule, the remote pilot in command—or a person serving as a visual observer under the operation’s procedures—must be able to see the aircraft well enough to meet the rule’s requirements. A route extending beyond that visibility is not made legal simply because the drone has GPS, a cellular connection, or an onboard camera. The operator needs the required FAA authorization for a beyond-visual-line-of-sight (BVLOS) operation, commonly involving a waiver of the relevant Part 107 provision, and must comply with the conditions attached to that authorization.

This distinction is central to delivery economics. A short route may fit within a visual operation, while a network designed to serve many neighborhoods from a central launch point may rely on BVLOS authority. The latter can require more extensive safety evidence and operating controls, such as procedures for detecting and avoiding other aircraft, communications, contingency handling, and defined operating areas. The exact requirements depend on the authorization and the operation; there is no single blanket permission that makes every delivery route acceptable.

Step 4: Prepare the aircraft and launch

Before takeoff, the operator confirms that the aircraft is in a condition to fly and that the mission still matches its approved plan. Part 107 includes preflight responsibilities: the remote pilot must assess the operating environment, including local weather and potential hazards, and ensure the aircraft is in a safe condition. In a delivery operation, that general obligation translates into concrete checks around the aircraft, package, site, and mission data.

A preflight sequence can include confirming battery status, inspecting propellers and structure, checking navigation and communication systems, verifying the parcel is secured, and confirming that the selected destination is still available. The remote pilot also needs to establish that required permissions and operational conditions are in place. If the mission depends on a visual observer, that person’s position and communication method should be clear before flight.

Once launched, the aircraft typically follows a planned route using onboard navigation and control systems. The remote pilot or operations team monitors the flight according to the operation’s procedures. Monitoring is not the same as assuming the aircraft will complete the route unaided: the team needs to know what conditions would trigger an intervention, a return, a hold, or a cancellation.

Communications and automation support the mission, but they do not remove the need for accountable oversight. The remote pilot in command remains responsible for the safe conduct of a Part 107 operation, subject to the applicable rules and any specific authorization. A delivery service must define who can make operational decisions, how the team receives relevant information, and how unexpected events are handled.

Step 5: Monitor the flight and manage exceptions

Every flight has uncertainty. A gust can exceed limits, a route can become obstructed, a communication link can degrade, or the destination can become occupied. Good operating procedures treat these as anticipated conditions rather than surprising edge cases.

Before launch, the operator establishes what the aircraft and team should do if the planned mission cannot continue. Depending on the aircraft and authorization, that response may involve returning to the launch point, proceeding to a designated alternate, or making another controlled decision. The right response is operation-specific. An aircraft should not improvise a landing in a busy or unsuitable area simply because it has reached a programmed point in its route.

Battery reserve is one example of how contingencies affect planning. A route needs enough energy for the planned trip and an appropriate margin for expected conditions and operational procedures. Headwinds, a longer-than-expected approach, or a return leg can all change the energy calculation. The planned payload also matters: carrying a heavier load may reduce endurance or limit the range available for the mission.

Operators should record interruptions and anomalies, not just successful deliveries. A rejected landing, unexpected obstacle, aborted flight, or equipment warning can reveal a weakness in route data, customer instructions, maintenance, or mission planning. The details matter: what happened, where, under what conditions, and what action the team took. That information supports trend analysis and corrective action, alongside any reporting required by the applicable rules or authorization.

Step 6: Complete and verify the handoff

Arrival is not the same as delivery. The operator needs a reliable way to establish that the package was released or placed as intended and that the aircraft can leave the area safely. Depending on the service design, completion may be confirmed by a sensor, a release event, a remote operator’s observation, customer confirmation, or a combination of signals.

A useful proof-of-delivery record should distinguish between different outcomes. A package placed at the designated point is not the same as one returned to the depot, left at an alternate location, or not released. Clear records help customer support resolve disputes and help operations teams identify patterns. They also avoid presenting an incomplete mission as a successful handoff just because the aircraft reached the destination coordinates.

Privacy deserves attention at this stage. Cameras and other sensors may be used for navigation, situational awareness, or delivery verification, but operators should define what data they collect, why they collect it, how long they retain it, and who can access it. A delivery system should not gather or store more information than the task requires. Clear notices and careful data controls can help reduce the feeling that a routine parcel delivery has become neighborhood surveillance.

After the handoff, the aircraft may return to its launch site or continue to another approved destination, depending on the service design and authorization. On the ground, staff can inspect the aircraft, recharge or replace batteries, and prepare it for another mission. The fleet’s next flight depends on maintenance and readiness checks, not just the arrival of another order.

What real delivery programs show

Named programs make the regulatory and operational picture less abstract. Zipline, for example, has operated medical and commercial delivery services in multiple countries and has pursued U.S. operations under FAA oversight. Its model illustrates an important point: a delivery company’s aircraft, launch infrastructure, customer handoff, and legal authority are designed as one operating system. The details of a particular service depend on its approvals and operating area, so a program’s existence should not be read as evidence that any operator can copy its routes under ordinary Part 107 rules.

In the United States, commercial carriage can raise questions beyond the basic rules for flying a small drone. Part 107 governs many small unmanned aircraft operations, but it does not by itself grant every company authority to carry property for compensation beyond the limits of its approvals. The FAA has issued air-carrier authority to certain drone delivery operators, including Zipline, under the relevant framework. Operators must understand which rules and permissions apply to their business model rather than treating “commercial drone flight” as one universal category.

That is why a pilot program is useful evidence, but not a shortcut. Its route, aircraft, staffing, customer locations, and authorization conditions may differ from those of a proposed service elsewhere. For logistics teams assessing a partner, the useful questions are specific: What authority covers the operation? What routes and aircraft does it cover? What are the operating limits? Who is responsible for the flight? How are abnormal events handled? And what evidence shows that the handoff process works reliably?

A worked example: a small parcel across town

Suppose a pharmacy receives an order for a compact, non-refrigerated item weighing 1.2 pounds. The fulfillment team confirms the item is eligible, weighs the packed parcel, and checks that the package fits the aircraft’s approved attachment system. The customer selects a marked delivery area at an address within the service area.

The operations team then checks the route, relevant airspace, current weather, aircraft status, and the conditions of the service’s FAA authority. If the route requires BVLOS operation, the company must have the appropriate authorization and comply with its terms; a phone app showing the aircraft’s position is not a substitute. The remote pilot reviews the plan and preflight checks are completed.

During the flight, the monitoring team watches for conditions that require a response. At the destination, the system verifies that the delivery area is suitable and completes the authorized release procedure. If a person or vehicle occupies the area, the aircraft does not simply treat its arrival as success: the team follows its approved alternate or abort procedure. The customer receives a status update that reflects what actually happened, and the mission record captures the outcome.

This example is deliberately modest. Its value lies in showing how small decisions accumulate. A parcel that is too heavy, a restricted route, poor weather, an unavailable drop zone, or missing authorization can each stop the mission. Operational reliability comes from handling those conditions consistently, not from assuming every order will produce a perfect flight.

Questions logistics teams should ask

A drone delivery proposal is easier to evaluate when the discussion moves from broad claims to operational evidence. Ask the provider to explain the complete order-to-handoff process and identify where human decisions enter it.

• Payload: What is the usable payload after accounting for the aircraft and delivery hardware, and how is package security checked?
• Route authority: Which FAA rules and authorizations cover the proposed flights, including controlled-airspace and BVLOS operations where relevant?
• Oversight: Who is the remote pilot in command, what does the operations team monitor, and how are communications failures handled?
• Contingencies: What happens when weather changes, the route becomes unavailable, or the delivery zone is occupied?
• Handoff evidence: How does the service distinguish a completed delivery from an attempted or aborted mission?
• Data practices: What imagery or location data is collected, how long is it kept, and who can access it?
• Service performance: How often are deliveries delayed, rejected, returned, or completed through a fallback method?

These questions help separate aircraft capability from service capability. A drone may be able to carry a parcel over a certain distance in favorable conditions, but a dependable delivery network also needs permission, suitable sites, trained personnel, maintenance, customer processes, and a safe response when the plan changes.

The practical meaning of “from order to handoff”

Drone delivery is a sequence of controlled decisions. The order must fit the aircraft and service; the destination must support a safe handoff; the route must comply with airspace rules and operating authority; and the flight must remain within the conditions established for it. The delivery is complete only when the package outcome is verified and the aircraft’s next action is safe.

For an operator, the central question is not whether a drone can fly from point A to point B. It is whether the entire service can repeat that mission with clear accountability, lawful access to the airspace, reliable contingency procedures, and a handoff customers can trust. FAA Part 107 provides a foundation for many small-drone operations, but visual-line-of-sight limits, airspace permissions, waivers, and any additional commercial authority determine what a particular delivery service may actually do.