Powdery Mildew Resistance Rotation Log: Tracking FRAC Groups Across Your Spray Program

By VitiScribe Editorial·August 8, 2025·Updated September 17, 2025

QoI resistance in powdery mildew is now confirmed in 18 California wine grape counties following insufficient rotation. That's not a theoretical concern from a university extension bulletin. It's a documented failure in actual vineyards where growers used the same mode-of-action group without rotation until selection pressure produced a resistant population. The fungicide stopped working.

Resistance management is the reason FRAC group rotation exists. And rotation only works if you're tracking it. A mental note that you switched products isn't a rotation log. A rotation log shows which FRAC groups you applied to each block, in sequence, across the full season.

TL;DR

QoI resistance is confirmed in 18 California wine grape counties -- not an emerging concern, a current program design requirement
Resistance can develop in a single growing season under high selection pressure in pathogen populations with sufficient genetic diversity, which E. necator populations consistently have
A rotation log must be block-specific, not operation-wide -- resistance builds at the block level where selection pressure from actual applications accumulates
The FRAC rotation alert that matters is the one that fires before a third consecutive same-group application is saved, not after the spray is already in the field
Multi-season records are what enable multi-season resistance management: knowing which groups were applied in prior seasons to a block lets you plan this season's rotation with actual data rather than estimation
Group 3 (DMI) resistance is documented at lower but increasing frequencies in California -- Group 3 products need rotation discipline alongside Group 11, not just as replacement primary materials

Why FRAC Group Rotation Matters for Powdery Mildew

Erysiphe necator, the powdery mildew pathogen on grapevines, has a documented ability to develop resistance to several fungicide classes. This isn't a slow process. Under high selection pressure, resistance can develop in a single growing season in a population with sufficient genetic diversity.

The FRAC system categorizes fungicides by their mode of action, specifically the biochemical target in the pathogen. When you apply the same mode of action repeatedly, you're selecting for individuals in the pathogen population that already have or can develop resistance to that mechanism. Over time, the surviving individuals are the resistant ones, and you've created a population the product no longer controls.

Resistance to FRAC group 11 (QoIs, strobilurins including azoxystrobin, trifloxystrobin, pyraclostrobin) is the most widespread confirmed resistance problem in California wine grape powdery mildew. Group 3 resistance (DMIs, including myclobutanil, tebuconazole) has been confirmed at lower but increasing frequencies. Groups with single-site modes of action, including groups 7 and 9, are also at risk with insufficient rotation.

Rotation between FRAC groups doesn't eliminate resistance risk. It slows selection pressure enough that a useful product remains effective longer. The recommendation from FRAC and UC IPM guidelines is to avoid using the same single-site mode of action more than twice consecutively in a season.

For the full resistance management rotation strategy applicable to California powdery mildew programs, see the fungicide resistance management guide.

What a Rotation Log Looks Like

Most growers who've thought about resistance management know their primary products. What they don't always have is a written, block-specific record of the sequence those products were applied in.

A rotation log that supports resistance management for a Cabernet Sauvignon block through a typical California powdery mildew season might look like this:

|---|---|---|---|---|

| 2 | May 3 | Quintec (quinoxyfen) | 13 | Bloom |

| 3 | May 22 | Luna Experience (fluopyram/tebuconazole) | 7+3 | Post-bloom |

| 7 | Aug 10 | Quintec (quinoxyfen) | 13 | Pre-harvest |

This sequence rotates between multi-site (M), group 13, group 7+3, and U6, with no single-site group repeated consecutively more than once. That's a defensible rotation program.

The same program without records is just a memory. And memories don't tell you what you applied to block 7 in week 14 of last season when you're planning this season's rotation to build on.

FRAC Groups Most Critical to Rotate in California Powdery Mildew Programs

California powdery mildew programs use a relatively predictable set of FRAC groups. The groups where rotation discipline is most important:

FRAC Group 11 (QoIs/strobilurins): Azoxystrobin, trifloxystrobin, pyraclostrobin, and others. Resistance confirmed in 18 counties. Do not use consecutively. In some blocks with known QoI resistance history, use sparingly or not at all.

FRAC Group 3 (DMIs/triazoles): Myclobutanil (Rally), tebuconazole, propiconazole, penconazole. Reduced sensitivity documented. Rotate with other groups and avoid consecutive use.

FRAC Group 7 (SDHIs): Fluopyram, boscalid, penthiopyrad. More recent class with growing use pressure. Resistance development is possible; rotation with non-SDHI groups is important.

FRAC Group 13 (quinoxyfen): Quintec is the primary product. Single-site mode of action with good efficacy. Limit to 2 applications per season per label guidelines.

FRAC Group U6 (cyflufenamid): Torino. Newer mode of action. Follow label guidelines on maximum seasonal applications.

Multi-site (M): Sulfur, copper. No resistance risk because multi-site modes of action affect multiple biochemical targets simultaneously. Use multi-site materials to break up single-site application sequences and reduce overall resistance selection pressure.

For the QoI-specific program adjustments and documentation that accompany confirmed Group 11 resistance, see the QoI resistance management guide.

How VitiScribe Tracks FRAC Rotation

VitiScribe's vineyard spray program for powdery mildew records the FRAC group for every product application automatically when you select a product from the database. You don't look up the FRAC group. It's pulled from the product record and attached to the spray event.

The rotation tracking works at the block level. For each block, VitiScribe maintains the sequence of FRAC groups applied in order. When the same single-site FRAC group is used more than twice consecutively, the system fires an alert before the third application is saved.

This alert fires at record entry, not after the spray is already in the field. That's when it's useful. A resistance rotation alert when you're planning the next spray, not when you're reviewing last season's records, is the alert that changes behavior.

VitiScribe's spray efficacy tracking also links efficacy observations to specific FRAC groups. If you're noting reduced disease control for a product, the system can connect that efficacy observation to the rotation history for that block, which is the data pattern that flags potential resistance development before it becomes a complete failure.

Building a Multi-Season Rotation Strategy

Resistance management isn't just a within-season concern. Some FRAC groups have cross-season persistence in the pathogen population. A strong resistance management program considers what was applied last season when planning this season's rotation.

This is where multi-season spray records become agronomically valuable beyond their compliance function. If you can pull up the FRAC group sequence for every block over the past three seasons, you can plan this season's rotation with actual data rather than estimation.

The blocks with heavy group 11 use in prior seasons are the ones where you want to minimize or eliminate group 11 applications this season regardless of whether you see resistance symptoms. You're managing the population before the problem is visible.

Frequently Asked Questions

How do I track fungicide resistance rotation in my vineyard spray program?

Fungicide resistance rotation tracking requires a block-level record of FRAC group applications in sequence. For each vineyard block, you need to know which FRAC groups were applied, in what order, and how many consecutive applications of each group occurred. This information can be maintained in a spray log that includes FRAC group data for each product applied. A spray log application that pulls FRAC group data from the product database automatically, like VitiScribe, builds the rotation record as a byproduct of normal spray logging. A spreadsheet or paper journal requires you to look up and record FRAC groups manually, which most growers don't do consistently.

What FRAC groups are most critical to rotate in California powdery mildew programs?

The FRAC groups most critical to rotate in California wine grape powdery mildew programs are group 11 (QoIs/strobilurins), group 3 (DMIs/triazoles), group 7 (SDHIs), and group 13 (quinoxyfen). Group 11 is the most urgent because resistance is already confirmed in 18 California counties. Groups 3 and 7 have documented or emerging resistance concerns. Group 13 has label-mandated limits of 2 applications per season. Multi-site materials (sulfur, copper) carry no resistance risk and should be integrated into every program to break single-site application sequences.

How does VitiScribe alert me when I have used the same mode of action too many times?

VitiScribe tracks the FRAC group sequence for each block and compares each new application against the recent application history for that block. When the same single-site FRAC group appears more than twice consecutively in the block's application history, the system generates a resistance rotation alert before the record is saved. The alert identifies the specific FRAC group, the number of consecutive applications, and the block affected. You can override the alert if you have a specific reason (for example, a product with no resistance concern in your region), but the alert creates a moment of deliberate decision-making rather than allowing consecutive applications to accumulate unnoticed.

Why does multi-season FRAC rotation history matter for program planning, and how far back should records go?

Three seasons is the practical minimum for multi-season rotation planning. The resistance population in a block reflects cumulative selection pressure, not just the most recent season's applications. A block that received 4 Group 3 applications last season and 3 the season before has substantially more selection pressure history than a block that received 2 Group 3 applications last season following prior seasons of diverse rotation -- even if this season's planned programs are identical. Pulling three-season FRAC history by block before planning the current season's rotation lets you weight your group allocation toward groups under-represented in recent seasons and away from groups that have carried heavy use. VitiScribe's block history maintains FRAC rotation records across seasons in the same block record view.

How should a spray record document the rationale for overriding a FRAC rotation alert and applying a third consecutive same-group application?

Override documentation should capture the specific reason for the exception: the FRAC group involved, the number of consecutive applications at override, and the agronomic reason (no alternative product was available at the required PHI, no other registered FRAC group was available for the specific target pest, or other specific reason). A note that the override was a deliberate decision rather than an unnoticed error -- "Group 7 third consecutive application approved -- no other registered FRAC group available within required PHI window for this block's harvest date" -- establishes that the rotation alert served its purpose and the decision was made consciously. VitiScribe requires a note field entry before an alert override is saved, creating an automatic documentation step.

What is Powdery Mildew Resistance Rotation Log: Tracking FRAC Groups Across Your Spray Program?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Powdery Mildew Resistance Rotation Log: Tracking FRAC Groups Across Your Spray Program. Target 50-150 words.]

How much does Powdery Mildew Resistance Rotation Log: Tracking FRAC Groups Across Your Spray Program cost?

How does Powdery Mildew Resistance Rotation Log: Tracking FRAC Groups Across Your Spray Program work?

What are the benefits of Powdery Mildew Resistance Rotation Log: Tracking FRAC Groups Across Your Spray Program?

Who needs Powdery Mildew Resistance Rotation Log: Tracking FRAC Groups Across Your Spray Program?

How long does Powdery Mildew Resistance Rotation Log: Tracking FRAC Groups Across Your Spray Program take?

Sources

FRAC (Fungicide Resistance Action Committee)
UC Cooperative Extension Viticulture
UC Davis Plant Pathology
Cornell Cooperative Extension
American Vineyard Foundation

Get Started with VitiScribe

A resistance rotation log that works requires block-level FRAC group sequence records that persist across seasons and alert before problems are repeated -- not an end-of-season report that shows you what went wrong. VitiScribe tracks FRAC groups automatically from the product database at every application entry, fires rotation alerts before third consecutive same-group applications are saved, maintains multi-season block-level rotation history, and connects efficacy observations to rotation patterns that suggest resistance development. Try VitiScribe free and pull up your current FRAC rotation sequence by block today.