Get a Quote

Submit
Insecticide Mode-of-Action Groups: Building a Resistance Rotation Plan
Time : Nov 03, 2026
Insecticide Mode-of-Action Groups: Building a Resistance Rotation Plan

Two insecticides can carry different brand names yet expose a pest population to the same mode of action. When control declines, replacing one with the other may continue the selection pressure rather than provide a meaningful rotation. The practical starting point is to identify every active ingredient and its current Insecticide Resistance Action Committee (IRAC) classification, then organize eligible treatments around pest generations and locally recommended application windows.

A workable resistance plan therefore rotates effective modes of action, not packaging, suppliers, or formulation types. It also checks local susceptibility, application quality, label restrictions, and nonchemical controls before assigning products to a schedule. Without those checks, even a sequence of different group numbers can fail because the selected products do not control the target life stage or reach the pest.

Start with an active-ingredient map, not a product list

Build an inventory for the specific crop, target pest, and production location. Record active ingredients separately from trade names, including every component of a premix. Use the current IRAC classification together with the locally authorized product label; classifications and registrations can change, and a classification alone does not establish permission to use a product.

The distinction between chemical family and mode-of-action group matters. Different chemical families may act at the same biological target. Conversely, products described broadly as biological insecticides do not necessarily share one mechanism. Classify the actual active ingredient rather than inferring its group from marketing terminology.

Example active ingredients IRAC classification Rotation implication
Lambda-cyhalothrin and deltamethrin 3A: sodium channel modulators Switching between them is not a change of mode-of-action group.
Imidacloprid and thiamethoxam 4A: nicotinic acetylcholine receptor competitive modulators Different active ingredients still share the same subgroup.
Spinosad and spinetoram 5: nicotinic acetylcholine receptor allosteric modulators, Site I Treat both as the same rotation group.
Chlorantraniliprole and cyantraniliprole 28: ryanodine receptor modulators A brand or active-ingredient change does not create a new rotation group.

These examples explain classification, not product suitability. Registration, target spectrum, crop safety, and resistance status must be checked independently. Do not automatically treat different lettered subgroups within one numbered group as independent rotation options; use current IRAC guidance and relevant local recommendations before relying on that distinction.

Establish which options still work locally

A technically different mode of action is useful only if the target population remains sufficiently susceptible. Start with recent field records, regional resistance alerts, and reliable susceptibility testing where available. Separate confirmed resistance from an unexplained control failure: poor coverage, incorrect timing, rainfall, unsuitable water, or reinfestation can produce similar symptoms.

For each candidate, assess the pest species and life stage actually present. A material effective against exposed young larvae may not rescue an infestation dominated by protected older larvae. Likewise, activity against one sucking pest does not establish activity against another species occupying the same crop.

  • Retain: registered options with suitable target activity and credible evidence of local efficacy.
  • Restrict: options with uncertain susceptibility, limited supporting records, or application constraints that need resolution.
  • Exclude from the planned sequence: options with confirmed resistance that makes field control unreliable, or uses not permitted by the local label.

Record the evidence behind each decision. “Worked previously” is weaker than a dated observation identifying the pest, treatment timing, application conditions, and post-treatment assessment. Where laboratory results are available, confirm that the tested population and method are relevant to the field decision.

Build treatment windows around pest biology

A rotation window is a defined period during which a selected mode of action may be used under the applicable resistance-management guidance. It is not necessarily one spray, one calendar month, or one crop stage. Window length should reflect the target pest’s generation time, local development conditions, residual exposure, and any specific label or regional instructions.

The central objective is to avoid exposing successive pest generations to the same mode of action. Where guidance permits multiple applications within a window, remain within both the label limit and the recommended group-specific limit. A rotation plan never authorizes extra applications or shorter intervals.

  1. Identify the treatment trigger. Use scouting and locally established action thresholds where available, rather than assigning compulsory sprays to calendar dates.
  2. Define the first window. Select an effective group appropriate to the dominant pest stage and document its permitted application limits.
  3. Choose the following window. Move to another effective group, checking for known cross-resistance and restrictions on returning to the previous group.
  4. Account for continuing exposure. Include seed treatments, soil applications, transplant treatments, and long-residual foliar applications where they affect the target pest.
  5. Review the crop boundary. Consider successive plantings, neighboring host crops, volunteers, and crop residues that may sustain the same pest population.

A new planting does not necessarily reset resistance risk. Mobile pests can move between fields, while overlapping crops may expose successive generations to the same chemistry. Coordinate treatment histories across the relevant production area where practical, especially when several fields function as a continuous host resource.

An illustrative sequence—not a spray recommendation

Suppose a leaf-feeding pest has locally effective, registered options in Groups 28, 5, and 6. A planning sheet could assign Group 28 to the first justified treatment window, Group 5 to the next, and Group 6 to a later window. Each transition depends on pest development, monitoring, and applicable guidance—not simply elapsed time.

This sequence is unsuitable if one group lacks activity against the present pest stage, has unreliable local efficacy, or conflicts with label restrictions. It also needs revision if a premix introduces an active ingredient from a group reserved for a later window. The group sequence is a planning framework, not evidence that three treatments are necessary.

Premixes and rescue sprays can break an otherwise sound plan

For a premix, enter both group numbers in the treatment record. A mixture containing Groups A and B followed by Group B is not a clean switch away from previous selection pressure. Likewise, alternating A+B with A+C repeatedly exposes the population to A.

Mixtures are not automatically resistance-management tools. Their value depends on factors including whether each component independently controls the target pest at the authorized rate, whether resistance already affects either component, and whether their effective exposure periods overlap. A component included mainly for another pest should not automatically count as protection against resistance in the primary target.

After an apparent failure, do not immediately repeat the same group under another brand. First verify application records, pest identity, life stage, and the product’s expected speed of action. Some treatments suppress feeding or development before mortality becomes obvious. Where intervention remains justified, choose an effective alternative group within label requirements and document why the rescue treatment was needed.

Keep formulation performance separate from mode of action

Coverage, dispersion, foam, and equipment behavior can affect delivered exposure, but improving those properties does not change an active ingredient’s IRAC group. Water quality, agitation, nozzle condition, spray volume, and canopy penetration should therefore be investigated alongside susceptibility when performance is inconsistent.

For formulation teams evaluating foam-control materials, Silicone Oil (Dimethyl Silicone Oil, Polydimethylsiloxane, PDMS) CAS 63148-62-9 is relevant as a material used in defoaming applications, not as a substitute insecticidal mode of action. Its available viscosity grades require formulation-specific selection. General-purpose PDMS should not be assumed to perform like a modified organosilicone spreading adjuvant, and neither tank-mix suitability nor pesticide-use authorization follows from the material’s identity.

Any proposed use needs compatibility, storage-stability, foam-control, application-performance, and crop-safety evaluation as applicable. Request grade-specific specifications and safety documentation. A successful formulation adjustment may resolve a delivery problem, but it does not demonstrate that resistance has been reversed.

Turn technical documentation into release criteria

Before approving an insecticide for the rotation, assemble a product dossier that connects the commercial material to the field-use decision. At minimum, verify active-ingredient identity and concentration, formulation type, current local registration and label, IRAC classification, batch quality documentation, and safety data. Supplier documentation supports identity and quality assessment; it does not by itself establish local biological efficacy.

Extract operational limits into the treatment sheet rather than leaving them buried in attachments: maximum applications, seasonal quantity limits, retreatment intervals, preharvest and reentry intervals, and relevant restrictions protecting pollinators or other nontarget organisms. Include application-method limitations and any specific resistance-management language. Where documents conflict, resolve the discrepancy before release instead of selecting the least restrictive statement.

Use monitoring to decide whether the plan needs changing

Record a pretreatment pest assessment and reassess at a timing appropriate to the product’s action and the pest’s development. Keep sampling methods consistent enough to distinguish treatment response from sampling variation. Record surviving life stages, fresh damage, beneficial organisms, and evidence of immigration; a single observation of live insects is not sufficient to diagnose resistance.

Repeated unexpected survival after correctly executed applications warrants a structured investigation and, where available, susceptibility testing through a qualified laboratory or local advisory service. Preserve the treatment history, including all active ingredients and exposure dates. Do not compensate with higher-than-label rates or unauthorized mixtures.

Leave room for no-spray decisions. Biological control, sanitation, host-free periods where feasible, exclusion, and other crop-appropriate measures can reduce the number of chemical selection events. Update the rotation when monitoring changes the treatment need, when a group loses dependable efficacy, or when registration conditions change—not merely because a new brand becomes available.

Next page:Already the last