DJI T100 Customizable Flight Tutorial: How to Create a Custom Flight Path

🇺🇸 U.S.A. FIRST — DJI Agras T100 Customized Flight Mode & Waypoint Planning

Standard automatic routes are ideal when an agricultural drone can cover a field with evenly spaced parallel passes. Real operations, however, are not always that simple. Multicrop interplanting may require the aircraft to follow selected crop rows without treating the neighboring crop. Aquaculture sites may require a deliberate route around ponds, embankments, aerators, pumps, nets, access roads, or other infrastructure. Irregular treatment zones may also require the operator to decide exactly where every application segment begins, ends, and turns.

The DJI Agras T100 Customized Flight Mode gives the operator direct control over the mission geometry. Instead of asking the controller to generate a conventional back-and-forth route across the entire block, the operator places custom route waypoints in sequence, identifies obstacles on a high-definition aerial survey map, protects those obstacles with adjustable margin areas, and determines whether material should be applied along each outgoing route segment.

This Ares Acres tutorial expands DJI’s short training workflow into a complete field-planning guide. It explains how to enter Customized Flight Path planning, use crosshair point marking, create obstacle boundaries, understand the default 1.5-meter obstacle margin, prevent route conflicts, edit and delete waypoints, control application by route segment, set estimated operation width, and verify the complete mission before saving or flying.

Ares Acres supports DJI Agras operators with agricultural aircraft, OEM replacement parts, diagnostics, technical education, and field-operation resources. For T100 equipment and support, explore the DJI Agras T100, DJI T100 Parts, DJI Agras Parts, DJI Accessories, the Ares Acres Product Catalog, or contact Ares Acres.

Prefer to watch instead of read? The video above demonstrates DJI’s core Customized Flight Mode workflow. This written guide adds the planning logic behind each step so the route is not merely accepted by the controller—it also reflects the crop, application area, obstacles, and real operating environment.

---

What You’ll Learn

• What Customized Flight Mode does on the DJI Agras T100.
• When a custom route is more useful than a standard automatically generated route.
• How customized flight paths support multicrop interplanting and aquaculture operations.
• How to enter Route Mode and select Customized Flight Path.
• How to add a route with crosshair point marking.
• How to choose and draw an obstacle type on a high-definition aerial survey map.
• What the red obstacle-margin region means.
• How the default 1.5-meter obstacle margin affects route planning.
• Why a route cannot be saved when it crosses an obstacle margin.
• How to place operation waypoints in the correct sequence.
• How to move or delete an incorrect waypoint.
• How to control application on the segment leaving each waypoint.
• How estimated operation width affects estimated area and application amount.
• How to inspect the programmed route before saving and flying.
• Which common planning mistakes create gaps, overlap, unsafe transitions, or invalid routes.

Quick Answer: How Do You Create a Custom Flight Path on the DJI Agras T100?

The most important concept is that a customized route is built segment by segment. Each point influences the next leg of the mission. Point order, obstacle geometry, application state, and operation-width estimates all need to be reviewed together before the route is saved.

Why Customized Flight Mode Matters

Most route planning tools begin with a field boundary and generate repeated parallel lines inside it. That approach is efficient for uniform fields, but it may not represent a job where only selected rows, bands, lanes, shorelines, or treatment zones should be followed.

Customized Flight Mode allows the digital route to reflect the real treatment plan. That can be useful when:

• two or more crops are interplanted in alternating rows or strips;
• only one crop or selected band requires treatment;
• an aquaculture property contains multiple ponds with irregular geometry;
• infrastructure divides the usable route into narrow operating corridors;
• the aircraft must follow a deliberate sequence around obstacles;
• some transit segments should not apply material;
• a conventional grid route would create unnecessary overlap or enter non-target areas;
• the operator needs to build a route around an irregular feature rather than fill an entire polygon; or
• a specialized application plan requires manual control over the order of flight segments.

Customized planning does not eliminate the need for field inspection, agronomic judgment, calibration, or pilot supervision. It gives the operator more control, which also means the operator assumes more responsibility for the geometry and sequence of the route.

Standard Route vs. Customized Flight Path

Planning method	How the route is created	Best suited for	Main operator responsibility
Standard Route Mode	The system generates repeated operation lines within a planned field boundary.	Uniform fields where systematic coverage is required.	Verify spacing, heading, boundary distance, obstacles, and application parameters.
Customized Flight Path	The operator places waypoints in sequence and defines the desired route segments.	Interplanted crops, aquaculture, irregular corridors, and selective treatment patterns.	Verify every point, turn, segment, obstacle margin, and application state.
A-B Route	The operator establishes reference points and the aircraft follows a repeated line pattern.	Straight, repeatable passes where a full field polygon may not be necessary.	Establish accurate reference points and maintain a safe operating corridor.
Manual or Manual+	The pilot directly controls the aircraft, with different levels of route assistance.	Spot work, edge work, or situations requiring immediate pilot control.	Maintain spacing, heading, altitude, application control, and obstacle clearance in real time.

If a normal parallel route can cover the job accurately and safely, it may remain the simpler planning method. Customized Flight Mode is most valuable when the operation genuinely requires deliberate waypoint geometry or different application behavior across individual segments.

Key Terms in the Customized Flight Workflow

Term	Meaning in this workflow	Why it matters
Customized Flight Path	A route whose waypoint sequence is planned directly by the operator.	The operator determines the mission geometry rather than relying only on an automatically filled field.
Crosshair Point Marking	A map-planning method in which the map is dragged beneath a fixed crosshair to place points.	It supports precise placement on a high-definition survey map.
Obstacle Boundary	The operator-defined outline of an obstacle or restricted feature.	It tells the planner where the obstacle is represented on the map.
Obstacle Margin	The protected region surrounding the obstacle boundary, displayed in red in the tutorial.	A custom route cannot cross this region and still be saved.
Route Waypoint / Boundary Point	A selected point that directs the sequence and shape of the custom route; the source tutorial refers to these selectable path points as boundary points.	Each point determines where the aircraft goes next.
Outgoing Segment	The route leg between the selected waypoint and the next waypoint.	Application can be enabled or disabled for this segment in the demonstrated workflow.
Estimated Operation Width	A planning value used to estimate covered area and material demand along the custom route.	An incorrect value can distort the displayed area and application-amount estimates.

Before Planning: Build an Accurate Operating Picture

DJI’s tutorial demonstrates obstacle placement on a high-definition map after aerial surveying. That is important because custom waypoints are only as reliable as the map and field information used to place them.

Before opening the planner, inspect or survey the site and identify:

• the exact target crop rows, strips, ponds, lanes, or treatment zones;
• the boundary between target and non-target crops;
• poles, wires, trees, windbreaks, buildings, fences, and towers;
• pumps, aerators, pipework, nets, docks, and other aquaculture infrastructure;
• roads, paths, embankments, ditches, waterways, and drainage features;
• workers, animals, vehicles, and frequently occupied areas;
• possible takeoff, refill, battery-change, and landing locations;
• terrain changes that may not be obvious in a two-dimensional map;
• the intended application sequence;
• segments where application must be off; and
• a safe Return-to-Home path.

Do not treat old satellite imagery as current ground truth. A newly installed wire, temporary irrigation system, seasonal net, parked vehicle, moved aerator, or changed crop boundary may not appear on the map. Aerial surveying can improve planning detail, but the site still needs physical verification.

Before launch, pair route planning with the DJI Agras T100/T50 Pre-Flight Safety Tutorial and inspect the aircraft, propellers, motors, payload system, landing gear, batteries, controller, positioning status, and operating area.

Step 1 — Enter Route Mode

From the DJI Agras operating interface, enter Route Mode. Route Mode is the planned-operation environment used to create, edit, save, and execute structured missions.

If you need a broader introduction to field creation and task execution, review the DJI Agras T100 Route Mode Field Planning & Task Execution Tutorial. The present article focuses specifically on the custom-waypoint workflow.

Before continuing, verify that you are working with the correct team, field, aircraft, payload configuration, and map. Starting in the wrong field record can create route confusion later, especially when several nearby plots look similar from above.

Step 2 — Select Customized Flight Path

Inside Route Mode, select Customized Flight Path as the planning or operation type.

This selection changes the planning logic. Instead of defining only the outside boundary and allowing the app to fill the interior with parallel lines, you will directly define the path the aircraft is expected to follow.

Plan the intended sequence before placing points. Ask:

• Where should the first operation segment begin?
• Which crop row, pond edge, or treatment lane should be followed first?
• Where should the aircraft turn?
• Which legs are active application legs?
• Which legs are transit-only?
• Where should the mission finish?
• Can the final position support a safe refill, battery change, landing, or return transition?

A few seconds spent defining the sequence can prevent a route that later requires extensive editing.

Step 3 — Click Add

Click Add to begin creating the customized route.

At this stage, avoid placing points immediately until the correct point-marking method and map layer are confirmed. Make sure the displayed high-definition map corresponds to the current field and that visible landmarks align with the real operating area.

Step 4 — Select Crosshair Point Marking

Choose Crosshair Point Marking.

In this method, the crosshair remains the placement reference while the operator drags the map beneath it. The point is added at the crosshair location. This can offer more deliberate placement than tapping approximately on a small feature with a finger.

For accurate crosshair planning:

1. Zoom to a level where the obstacle or intended path is clearly visible.
2. Keep enough surrounding context on screen to understand the route direction.
3. Drag the map slowly beneath the crosshair.
4. Confirm the crosshair is on the intended location before recording the point.
5. Recheck the newly created geometry after every significant turn or boundary change.

Excessive zoom can hide nearby context; insufficient zoom can make precise placement difficult. Use a scale that allows both accuracy and situational awareness.

Step 5 — Choose the Obstacle Type

Before drawing the obstacle, select the appropriate obstacle type offered by the planning interface.

Obstacle classification helps organize the map and may affect how the feature is represented in the planner. The exact options and labels can vary with aircraft, app version, firmware, payload, and region, so use the current controller interface as the authority for the available choices.

The obstacle should represent the real feature—not merely a convenient shape. If a tree line, equipment area, pond structure, or building occupies a larger footprint than it first appears to on the map, outline the full relevant area.

Step 6 — Mark Obstacles Within the Block

Using the high-definition aerial survey map, drag the map beneath the crosshair and mark obstacles located inside or near the planned operation block.

Place obstacle points in sequence so the resulting boundary follows the actual feature. A simple isolated feature may need only a basic shape. A long windbreak, irregular structure, or clustered equipment area may require additional points to represent it properly.

Obstacles Commonly Relevant to Multicrop Fields

• trees and windbreaks;
• utility poles and overhead wires;
• irrigation pivots, pipes, and risers;
• field buildings and grain structures;
• fences, gates, and equipment staging areas;
• drainage ditches and waterways;
• tall neighboring crops; and
• roads or regularly occupied access lanes.

Obstacles Commonly Relevant to Aquaculture Sites

• aerators and their supports;
• pump houses and intake equipment;
• electrical service poles and wires;
• nets, cables, and suspended lines;
• docks, platforms, and feeding systems;
• pond embankments and narrow levees;
• vehicles and work areas; and
• trees or structures along the water’s edge.

Some hazards—especially thin wires, cables, nets, or temporary equipment—may be difficult for onboard sensing systems to identify consistently. Represent known hazards during planning and supervise the operation rather than assuming the aircraft will detect everything in real time.

Step 7 — Understand the Red Obstacle-Margin Region

After the obstacle boundary is created, the tutorial shows a red region outside the obstacle boundary. This red area represents the obstacle margin.

The obstacle boundary and obstacle margin are related but different:

• the obstacle boundary represents the feature itself; and
• the obstacle margin represents the protected planning area around that feature.

In the demonstrated workflow, the obstacle margin has a default value of 1.5 meters and can be adjusted as needed.

Do not interpret the default value as a universal clearance recommendation for every obstacle or job. A suitable margin depends on the obstacle, map accuracy, positioning conditions, aircraft behavior, wind, route speed, payload, terrain, crop canopy, application requirements, and applicable operating rules. A thin wire, tall tree, building, moving vehicle area, or location with uncertain mapping may require a different planning decision than a low, isolated feature.

Step 8 — Adjust the Obstacle Margin When Needed

Review the default margin around every obstacle and adjust it when the operating environment requires a different protected area.

Consider:

• whether the survey map aligns precisely with the real feature;
• whether the obstacle has branches, cables, arms, or components extending beyond its visible center;
• whether wind could move the aircraft or vegetation toward the route;
• whether the planned turn requires additional room;
• whether the aircraft will approach the obstacle directly or pass alongside it;
• whether the obstacle is fixed, flexible, temporary, or moving;
• whether people or vehicles may enter the area; and
• whether a legal, label, property, or agronomic setback is larger than the displayed planning margin.

An obstacle margin is a planning control, not a promise of physical clearance. The pilot remains responsible for deciding whether the route is appropriate for the actual site.

Step 9 — Place Route Waypoints in Sequence

After obstacle planning, select the route points sequentially to create the customized operation flight path.

Point order matters. The controller connects each waypoint to the next one, creating a chain of flight segments. If the points are selected out of order, the route may double back, cross itself, make an unnecessary turn, enter a non-target crop, or approach an obstacle from the wrong direction.

A Practical Waypoint Sequence

1. Select a clear and logical first operation point.
2. Follow the first target row, lane, pond edge, or treatment band.
3. Place a waypoint where the route must turn or where application behavior must change.
4. Add the next point in the actual order the aircraft should fly.
5. Continue until every required operation segment is represented.
6. Inspect the entire line from start to finish before saving.

Use enough points to describe the route accurately, but avoid unnecessary point density. Every extra point creates another segment or turn that must be inspected.

Step 10 — Keep Every Segment Outside the Obstacle Margin

The DJI tutorial states that the flight path cannot cross the obstacle-margin range. If a route line crosses the red margin area, the plan cannot be saved.

This is an important validation rule. A waypoint may appear to sit outside the red region while the straight segment connecting it to the next point cuts through the margin. Inspect the full line between points—not only the points themselves.

If the plan will not save because of a margin conflict:

1. Locate the route segment entering the red region.
2. Confirm that the obstacle boundary and margin accurately represent the real site.
3. Move the relevant waypoint or add an appropriate intermediate waypoint so the route remains outside the protected area.
4. Do not shrink a necessary margin merely to force the route to save.
5. Reinspect the new turn geometry and application state.

The correct solution is the route that respects the real hazard, not simply the fastest way to clear the controller warning.

Step 11 — Move an Incorrect Waypoint

Click a route waypoint to modify its position.

Waypoint movement is useful when:

• the point was placed slightly off the target row;
• the outgoing line enters an obstacle margin;
• the turn is too close to a boundary;
• the route clips a non-target crop;
• the segment does not align with a pond edge or treatment lane; or
• the point order is correct but the geometry needs refinement.

After moving a point, inspect both the segment entering that waypoint and the segment leaving it. One correction can improve one leg while unintentionally creating a problem on the other.

Step 12 — Delete an Unnecessary Waypoint

Double-click a waypoint to delete it.

Delete a point when it creates an unnecessary turn, was added in the wrong sequence, duplicates a nearby point, or makes the route less clear. Once the point is removed, the planner will connect the surrounding route geometry differently, so review the new line before continuing.

Do not use deletion without checking the result. Removing one waypoint can cause a newly connected segment to cut across an obstacle margin, non-target crop, pond feature, property boundary, or other restricted area.

Step 13 — Set Application Behavior for the Next Segment

The demonstrated workflow allows the operator to choose whether the next flight path leaving a selected waypoint performs application.

Think of this as an outgoing-segment control:

• select a waypoint;
• identify the next connected route leg; and
• decide whether the equipped application system should operate along that leg or remain off.

For a spraying setup, this means deciding whether the next segment is an active spray leg. For a spreading setup, it means deciding whether the next segment is an active spreading leg. It should not be interpreted as changing the physical aircraft from spraying equipment to spreading equipment in the middle of the same flight.

Typical Application-On Segments

• the length of a target crop row;
• a selected treatment band;
• an approved pond or aquaculture treatment lane;
• a perimeter segment that is part of the application plan; or
• another route leg where the intended material should be delivered.

Typical Application-Off Segments

• a transition between target rows;
• a crossing over a non-target crop;
• a turn outside the desired treatment band;
• a connection around an obstacle;
• a transit leg near a road, building, embankment, or work area; or
• any segment where the product label or operation plan prohibits application.

Review every segment individually. A geometrically safe route can still produce an agronomic or compliance problem if application remains enabled across a non-target area.

Step 14 — Open Flight Path Settings

Open the Flight Path Settings page to review the parameters used for the customized route.

This page is where the tutorial demonstrates the estimated operation width setting. Treat this as part of mission estimation and planning—not as a substitute for selecting the correct nozzle, flow rate, feeder settings, altitude, speed, droplet size, swath validation, or material calibration.

Step 15 — Set the Estimated Operation Width

Enter an estimated operation width that reasonably represents the effective width expected for the current aircraft, payload system, material, application settings, and operating environment.

The tutorial explains that this value affects:

• the estimated operation area; and
• the estimated application amount.

If the estimated width is too large, the controller may overstate the area associated with the custom path and distort the material estimate. If it is too small, the displayed area and application amount may be understated.

Estimated Width Is Not the Same as Verified Effective Width

Actual effective application width can vary with:

• flight altitude;
• flight speed;
• wind speed and direction;
• nozzle or feeder configuration;
• droplet size or particle characteristics;
• application rate;
• crop height and canopy structure;
• turn behavior;
• terrain; and
• the specific spray or spreading system installed.

Use field calibration, product-label requirements, test passes, catch testing or other appropriate verification methods, and the current DJI operating documentation to establish real application performance. The estimated-width field helps the controller calculate planning estimates; it does not guarantee coverage by itself.

Step 16 — Review the Estimated Area and Application Amount

After entering the estimated operation width, compare the controller’s estimated area and application amount with the real job plan.

Ask:

• Is the estimated area plausible for the total length of active route segments?
• Were transit-only segments excluded from application where required?
• Does the estimated application amount align with the planned rate?
• Is the tank or hopper capacity appropriate for the task or expected refill sequence?
• Does the route include accidental duplicate coverage?
• Are any target rows or pond sections missing?

A surprising estimate is a reason to inspect the route, not merely accept the number. The cause may be an incorrect width, an application-state error, duplicated geometry, a missing segment, or a route that does not match the intended treatment pattern.

Step 17 — Save the Customized Flight Path

When obstacle boundaries, margins, waypoint order, application segments, width estimates, and route geometry are correct, click Save.

If the route cannot be saved, inspect obstacle-margin conflicts first. Then verify that the route contains valid point geometry and that no required setting is incomplete.

Saving completes the planning stage; it does not complete the operational safety review. Reopen or preview the task and inspect the complete programmed mission before takeoff.

How to Review the Custom Route Before Flight

Trace the route from the first waypoint to the last as though you were manually flying every segment.

Route Geometry

• Does the mission begin in a logical location?
• Are the points connected in the correct order?
• Does any segment cross itself unnecessarily?
• Are turns wide and clear enough for the actual environment?
• Does the route remain inside the intended operating area?
• Does every segment remain outside every obstacle margin?

Application Logic

• Is application enabled on every intended treatment segment?
• Is application disabled for turns and transit legs where necessary?
• Does the route avoid treating a neighboring crop, road, building, embankment, or work area?
• Are the application rate and payload settings appropriate for the material and crop?

Positioning and Map Alignment

• Does the high-definition map match current field conditions?
• Are RTK or GNSS status and expected positioning accuracy acceptable?
• Has the operator physically confirmed obstacles and boundaries?
• Are thin, temporary, moving, or recently installed hazards accounted for?

Mission Safety

• Is the takeoff and landing area clear?
• Is the controller link suitable throughout the operating area?
• Is the Return-to-Home path safe?
• Are workers and ground crew outside the operating zone?
• Are weather, wind, visibility, and lighting conditions acceptable?
• Can the operator maintain required oversight and intervene if necessary?

For high-precision positioning workflows, see the DJI Agras T100 D-RTK 3 Tutorial. For controller-screen orientation during the mission, review the DJI Agras T100/T50 Remote Operation View Tutorial.

Example 1 — Multicrop Interplanting

Imagine a field planted in alternating bands of two crops. Only one crop requires the planned application.

A conventional route that fills the entire field could carry the aircraft repeatedly across both crops. A customized route can instead follow the selected target bands while application is disabled during the transitions between them.

A practical planning sequence may be:

1. Survey and verify the crop-row locations.
2. Mark irrigation equipment, poles, trees, and other obstacles.
3. Place waypoints along the first target band.
4. Disable application on the turn or transition to the next target band.
5. Enable application on the next approved band.
6. Repeat the pattern through the field.
7. Confirm that no application segment crosses the neighboring crop.
8. Review the estimated width, area, and material requirement.

This workflow is only appropriate when the route, aircraft position, effective width, drift management, product label, and agronomic plan can maintain the required separation. A custom line on a map does not by itself prevent off-target movement.

Example 2 — Aquaculture Route Planning

Aquaculture properties often contain geometry that is very different from a conventional row-crop field. Several ponds may be separated by narrow embankments, service roads, pumps, electrical equipment, aerators, nets, or work platforms.

Customized Flight Mode can help the operator place a deliberate path around or across the approved treatment zones while keeping application off during unsuitable transitions.

A practical planning sequence may be:

1. Create or load a current high-definition survey map.
2. Verify pond edges, embankments, infrastructure, cables, and occupied work areas in person.
3. Mark obstacles and confirm their protected margins.
4. Place route waypoints in the exact intended operating sequence.
5. Enable application only on approved treatment legs.
6. Disable application along connecting or infrastructure-adjacent transit segments.
7. Confirm that the route does not enter any red obstacle-margin region.
8. Review wind, visibility, return route, and emergency landing considerations.

Aquaculture products and treatment programs can have specialized requirements. Follow the applicable product label, water-use rules, environmental requirements, and site operating procedures.

Example 3 — Irregular Selective Treatment Corridor

A field may contain a narrow infestation band, disease corridor, drainage edge, or selected row set that does not justify treating the entire block.

The custom planner can be used to trace that corridor directly. The operator can create active application legs along the target zone and non-application legs between separated sections.

The route should still be inspected for:

• tight turns that create overlap;
• short segments that cause repeated application transitions;
• nearby non-target vegetation;
• obstacles along the edge of the corridor;
• map offset or positioning uncertainty; and
• whether the treatment width is appropriate for the narrow target.

Decision Table: Should You Use a Customized Flight Path?

Scenario	Likely approach	Reason
Uniform rectangular field requiring full coverage	Standard Route Mode	Automatically generated parallel passes are usually simpler.
Alternating crop rows where only selected rows require treatment	Customized Flight Path	The operator can define the target lines and disable application during transitions.
Several irregular aquaculture ponds with fixed infrastructure	Customized Flight Path	Waypoints and obstacle margins can represent a deliberate operating sequence.
Straight repeated passes without a complete field polygon	Consider A-B Route	An A-B pattern may be faster to establish.
Small spot treatment requiring continuous pilot judgment	Manual or Manual+ may be appropriate	Direct control can be more suitable than building a full waypoint mission.
Irregular corridor with known obstacles	Customized Flight Path with careful obstacle planning	The route can follow the corridor while staying outside protected margins.
Map is outdated or the site has not been inspected	Delay final route planning	Custom points based on inaccurate site information can create an unsafe mission.
Route requires an extremely tight pass beside wires or people	Redesign or avoid the route	A saved route is not proof that the operation is safe.

For alternative operating methods, see the DJI Agras T100 A-B Operation Mode Tutorial and DJI Agras T100 Manual & Manual Plus Tutorial.

Segment Planning Table: Application On or Off?

Route segment	Typical application state	Verification question
Along the center of an approved target row	On, if consistent with the operation plan	Does the effective width remain within the target area?
Turn between two target rows	Often off	Would continued application create overlap or treat a non-target area?
Transit around an obstacle	Off	Is the aircraft clear of the margin, and is material delivery disabled?
Connection between separate ponds or treatment zones	Usually off unless specifically approved	Does the connecting ground or water belong to the treatment plan?
Selected aquaculture treatment leg	On only when approved for the specific program	Are label, rate, environmental, and site requirements satisfied?
Route beside a road, building, worker area, or neighboring property	Usually off or route redesigned	Is the segment itself appropriate, even without application?
Duplicate return along an already treated line	Usually off unless deliberate	Would application create excessive overlap?

Common Customized Flight-Path Mistakes

1. Selecting Waypoints Out of Sequence

The controller connects points in the order selected. A single misplaced point can make the route double back or cut across the site.

2. Checking Only the Waypoints, Not the Connecting Lines

Two points may sit outside an obstacle margin while the segment between them crosses the red region. Review complete route legs.

3. Shrinking an Obstacle Margin Just to Make the Route Save

The margin should represent the real planning need. If the route conflicts with a necessary protected area, redesign the route.

4. Treating the Default 1.5 Meters as a Universal Safe Distance

The tutorial shows a default planning value, not a guarantee suitable for every obstacle, map, aircraft state, wind condition, or legal requirement.

5. Forgetting to Disable Application During Transitions

A safe transit line can still cause off-target treatment when spray or spreading remains active.

6. Assuming Estimated Width Equals Actual Coverage

The width entry affects planning estimates. Real coverage must be verified for the specific system, settings, material, crop, and conditions.

7. Using Too Few Waypoints

An oversimplified path may cut across a curved crop row, pond edge, obstacle margin, or non-target zone.

8. Using Too Many Waypoints

Unnecessary points can create excessive turns, short segments, confusing application changes, and a route that is difficult to audit.

9. Relying Only on the Aerial Map

Even a high-definition survey map may not show a new, thin, temporary, moving, or vertically significant hazard.

10. Assuming Obstacle Sensing Replaces Planning

LiDAR, vision, radar, and other safety systems can assist the operator, but they do not remove the responsibility to map hazards, maintain clearance, supervise the aircraft, and intervene when necessary.

11. Saving Without Reviewing the Estimate

An unexpected area or material estimate can reveal a width error, duplicated route, missing application toggle, or incorrect segment.

12. Confusing Segment Application Control With Payload Conversion

The application choice governs whether the equipped spray or spreading system applies material on that route leg. It does not physically change one payload system into the other during flight.

Troubleshooting Customized Flight-Path Planning

Problem	Likely cause	What to check
Route cannot be saved	A path segment crosses an obstacle-margin region	Inspect every line against the red region, then move or add waypoints as appropriate.
Route unexpectedly doubles back	Waypoints were selected out of sequence	Trace the point order, delete the incorrect point, and rebuild that section.
Moving one point creates a new conflict	The incoming or outgoing segment now enters a margin	Inspect both connected route legs after every edit.
Deleting a point makes the route cut through an obstacle	The surrounding points were connected directly	Restore the required geometry with a correctly placed waypoint.
Material is applied during a transition	Application remained enabled for the outgoing segment	Select the preceding waypoint and review the next-segment application setting.
A target segment does not apply material	The outgoing segment was set as non-application	Review the waypoint that begins the affected segment.
Estimated area appears too high	Width is overstated, geometry is duplicated, or too many segments are active	Verify operation width, route overlap, and application-state settings.
Estimated application amount appears too low	Width, rate, active-route length, or application state may be incorrect	Compare the route settings with the real treatment plan and calibration.
Obstacle does not match its real footprint	Boundary points were placed inaccurately or the map is misaligned	Recheck the survey, physically verify the feature, and redraw the boundary.
Route follows the map but not the real crop row	Map offset, poor point placement, or field changes	Re-survey or correct the waypoints after ground verification.
Turns are awkward or too tight	Waypoints are too close or placed without considering aircraft movement	Simplify or reposition the turn geometry and review available clearance.
Correct options are missing from the interface	App, firmware, aircraft, payload, or regional interface differs	Verify the current DJI Agriculture app, controller, firmware, and documentation.

Ares Acres Recommended Customized-Route Workflow

1. Define the exact target crop rows, pond zones, or treatment corridors.
2. Confirm the product, material, rate, payload, and applicable operating restrictions.
3. Survey the site and physically inspect current conditions.
4. Identify obstacles, non-target areas, transitions, takeoff points, and Return-to-Home paths.
5. Complete the aircraft and payload pre-flight inspection.
6. Enter Route Mode and select Customized Flight Path.
7. Click Add and choose Crosshair Point Marking.
8. Select the appropriate obstacle type and mark the full obstacle geometry.
9. Review the default 1.5-meter red margin and adjust it based on the real site.
10. Plan the route sequence before adding operation waypoints.
11. Place waypoints in the exact order the aircraft should fly.
12. Confirm every connecting line remains outside every obstacle margin.
13. Move or delete inaccurate points and recheck all affected segments.
14. Set application on or off for every outgoing route leg.
15. Enter a defensible estimated operation width.
16. Compare the estimated area and application amount with the job plan.
17. Save the customized route.
18. Reopen or preview the mission and trace it from start to finish.
19. Confirm positioning, weather, airspace, ground-crew separation, and emergency procedures.
20. Begin only when the complete mission makes operational sense and remain ready to pause or intervene.

Related DJI Agras Operator Academy Tutorials

• DJI Agras T100 Route Mode Field Planning & Task Execution
• DJI Agras T100/T50 Remote Operation View Tutorial
• DJI Agras Remote Controller Activation Tutorial
• DJI Agras T100 D-RTK 3 Tutorial
• DJI Agras T100 A-B Operation Mode Tutorial
• DJI Agras T100 Manual & Manual Plus Tutorial
• The DJI T100 Spreading System Tutorial
• DJI Agras T100/T50 Pre-Flight Safety Tutorial

FAQ: DJI T100 Customized Flight Mode

What is Customized Flight Mode on the DJI Agras T100?

It is a Route Mode planning workflow that allows the operator to create a deliberate flight path by placing route waypoints in sequence instead of relying only on an automatically generated parallel route.

What types of operations is a custom flight path designed for?

DJI’s tutorial identifies multicrop interplanting and aquaculture as example scenarios. It may also be useful for other irregular or selective application routes when the operator needs direct control over waypoint order and segment application.

How do I begin creating the route?

Enter Route Mode, select Customized Flight Path, click Add, and select Crosshair Point Marking.

Why should I use an aerial survey map?

A current high-definition survey map can provide greater detail for placing obstacles and route points than generic or outdated imagery. It still needs to be compared with current field conditions.

How do I mark an obstacle?

Choose the obstacle type, move the high-definition map beneath the crosshair, and place points around the feature so the obstacle boundary represents its real footprint.

What is the red region around an obstacle?

The red region is the obstacle-margin range surrounding the obstacle boundary. It represents an area the custom path cannot cross if the plan is to be saved.

What is the default obstacle margin?

The official tutorial demonstrates a default value of 1.5 meters. The margin can be adjusted as needed. The default should not be treated as a universal safe clearance for every operation.

Why won’t my custom route save?

The first item to inspect is whether any route segment crosses a red obstacle-margin region. Also review point geometry and required route settings.

Can I move a route waypoint?

Yes. Click the waypoint to modify its position, then inspect both the incoming and outgoing route segments for new conflicts.

How do I delete a waypoint?

The demonstrated workflow uses a double-click to delete an unnecessary waypoint. Review the replacement line created between the surrounding points.

Can I turn spraying or spreading off for only one part of the route?

The tutorial shows that the operator can choose whether the next path leaving a waypoint performs application. Review each outgoing segment so application is active only where intended.

Can the aircraft switch from spraying hardware to spreading hardware during the route?

No. Segment application control should be understood in relation to the payload system currently installed. It can control whether that equipped system applies material on a segment; it does not convert the aircraft between physical payload systems in flight.

What does estimated operation width do?

It affects the controller’s estimated operation area and estimated application amount for the customized route.

Does the estimated width guarantee my actual swath?

No. Actual effective width varies with the application system, settings, material, altitude, speed, wind, crop, and other field conditions. Verify real performance through appropriate calibration and testing.

Should application remain on during turns?

Only when that behavior is deliberate, appropriate for the target, and consistent with the product label and operation plan. Many custom routes will require application to be disabled during selected turns or transitions to prevent overlap or off-target treatment.

Can I rely on obstacle avoidance instead of drawing obstacles?

No. Onboard safety systems assist the pilot, but known obstacles should be represented during planning and verified at the site. Some thin, temporary, moving, or visually difficult hazards may not be detected reliably.

What should I check immediately before flight?

Confirm route order, obstacle margins, application state for every segment, width and material estimates, aircraft health, payload configuration, battery status, positioning, weather, controller link, takeoff area, personnel separation, airspace, and Return-to-Home path.

Final Takeaway

The DJI Agras T100 Customized Flight Mode is built for missions where the operator needs more control than a conventional field-wide route can provide. Multicrop interplanting, aquaculture, selective treatment corridors, and irregular operating lanes can all require a waypoint sequence that reflects the actual treatment plan rather than a generic grid.

The workflow is straightforward: select Customized Flight Path, use crosshair marking, map the obstacles, evaluate the default 1.5-meter red margin, place operation waypoints in sequence, keep every connecting line outside the protected region, edit the geometry, choose application behavior for each outgoing segment, set the estimated operation width, review the area and application estimate, and save.

The quality of the mission depends on the decisions behind those clicks. A strong custom route accurately represents the site, keeps application inside the intended treatment zones, preserves clearance from real hazards, and remains understandable from the first waypoint through the final segment.

---

Complementary DJI T100 Equipment & Operator Resources

A custom route is only one part of a reliable agricultural drone operation. Before deploying the mission, verify that the aircraft, power system, payload, controller, positioning equipment, and replacement components are ready for field use.

• DJI Agras T100 Aircraft — explore the T100 platform and complete-system options.
• DJI T100 Parts — browse model-specific OEM replacement components.
• DJI Agras OEM Parts — search the broader agricultural-drone parts catalog.
• DJI Agras Accessories — review operational accessories and supporting equipment.
• Ares Acres Product Catalog — search aircraft, parts, power-system equipment, and field-support products.
• Ares Acres Technical Support — contact our team for component identification, aircraft support, or T100 equipment questions.

What Is Ares Acres?

Ares Acres is a U.S.-based agricultural robotics company focused on DJI Agras aircraft, OEM parts, operator support, diagnostics, and technical education. Our growing DJI Agriculture Tutorials library is designed to help owners and operators understand the systems they use in the field—not simply purchase them.

Need DJI Agras T100 Parts or Support?

Explore the DJI Agras T100, browse DJI T100 Parts, search the complete DJI Agras Parts catalog, or contact Ares Acres for help identifying the right component or system for your operation.

Operational note: DJI Agras interface labels, menu structure, route validation, obstacle-margin behavior, estimated-width calculations, and available functions can vary by aircraft, controller, DJI Agriculture app version, firmware, payload, and region. Always verify the current interface and applicable DJI documentation before flight. Follow product labels, environmental requirements, local application rules, FAA requirements, airspace restrictions, and all other applicable operating requirements. Aerial maps, route planning, RTK/GNSS, LiDAR, vision, radar, and obstacle sensing are assistance systems and do not eliminate the operator’s responsibility to inspect, plan, supervise, and intervene throughout the mission.