Fungicide Applied Disease Spreads Resistance vs Misdiagnosis Decision Tree

Why this matters

A fungicide that fails to stop a spreading disease has only a few possible explanations, and they lead to opposite actions. If it is the wrong diagnosis, more of the same fungicide will never work, no matter how much you apply. If it is fungicide resistance, switching to a different mode of action stops it, but staying in the same FRAC group makes it worse and breeds resistance across your whole route. If it is an application error, the chemistry was fine but never reached the target. Mislabeling a misdiagnosis as "resistance" leads to expensive program-wide rotations that solve nothing; mislabeling resistance as "the disease is just bad this year" burns the customer's turf and your reputation. This tree separates the three.

Symptom presentation

• Disease symptoms (patches, rings, blight, mycelium) continue to advance days after a fungicide application that should have arrested them.
• New infection centers appear, or existing margins keep moving outward.
• Sometimes partial response (some areas check, others do not), which is itself a clue.

Quick checks

1. Re-confirm the diagnosis from scratch. Do not assume the original ID was right. Get a lab confirmation if not already done. The single most common reason a fungicide "fails" is that the disease was misidentified or the problem is not a disease at all (insect, abiotic, salt, drought, wilt).
2. Check the product against the disease. Pull the label and confirm the fungicide is actually labeled for and effective against the diagnosed pathogen. A broad-spectrum is not universal; some products have gaps (a contact with no systemic uptake will not stop an established root pathogen).
3. Verify the application. Rate, water volume (carrier), spray pressure, and especially whether it was watered in or left on the leaf as the disease required. Curative versus preventive timing matters: most fungicides are far weaker once disease is established.
4. Note the FRAC group and the recent spray history. Repeated single-site (FRAC 11 QoI, FRAC 3 DMI, FRAC 7) applications without rotation is the resistance setup.

Isolation tree

Branch on the re-diagnosis first.

• Re-diagnosis shows a different or non-fungal cause -> misdiagnosis. Examples: dollar spot treated as brown patch, or chinch-bug damage / fertilizer burn / dog urine / drought sprayed as disease. The fungicide could not work because the target was wrong. Switch to the correct control (right fungicide, insecticide, or cultural fix). This is the most common branch; rule it out before ever invoking resistance.
• Diagnosis confirmed correct, product labeled for it, application correct, but no response in a population that previously responded -> probable fungicide resistance. Strongest where a single-site mode of action (FRAC 11, 3, 7, or benzimidazole FRAC 1) was used repeatedly without rotation. Confirm: did the SAME product/group work last year and stop working after repeated use? Partial response (the area treated last with a new group checks, the area on the old group does not) supports resistance. Switch to an unrelated FRAC group with a different target site, and adopt a rotation/tank-mix program.
• Diagnosis correct, product correct, but applied wrong -> application error masquerading as failure. Sub-branches: rate too low; carrier volume too low to penetrate the canopy for a foliar disease or too low/not-watered-in for a soil-borne disease; sprayed under high heat or onto wet foliage causing poor coverage; tank-mix antagonism or wrong water pH degrading the active; nozzle/calibration delivering less than intended. Confirm by recomputing the actual delivered rate and reviewing technique. Correct the technique and re-treat.
• Diagnosis correct, product and technique correct, conditions overwhelming -> the disease pressure exceeds what a single application can hold (continuous leaf wetness, infected thatch reservoir, high nitrogen pushing succulent growth for brown patch, or a curative attempt on a disease that needed preventive timing). Combine cultural correction (water timing, mowing, nitrogen) with a properly timed program rather than chasing it chemically alone.

Confirming diagnosis

For misdiagnosis, a turf diagnostic lab assay is definitive and cheap insurance before any rotation decision. For resistance, the field signature is: confirmed pathogen, correct labeled product applied correctly, prior efficacy of that mode of action, repeated solo use of a single-site group, and loss of response, often with response restored by switching FRAC groups. True resistance confirmation requires a lab sensitivity assay, but the field history is usually sufficient to act. For application error, recompute the delivered rate and coverage and look for the response when corrected.

Remediation

• Misdiagnosis: stop the wrong product, apply the correct control for the real cause.
• Resistance: rotate to a different FRAC group/target site, tank-mix a multi-site (contact) partner with the at-risk single-site product, never apply the same single-site group back to back, and limit total seasonal applications of any one group per the label and FRAC guidelines. Re-confirm the pathogen.
• Application error: correct rate, carrier volume, watering-in, timing, and calibration, then re-treat.
• Overwhelming pressure: integrate culture (mowing, nitrogen balance, irrigation timing to minimize leaf wetness, dew removal) with a preventive-timed program.

References

• Fungicide Resistance Action Committee (FRAC), "FRAC Code List" and turf resistance-management guidelines.
• Penn State Extension, "Fungicides for Turfgrass Disease Management" and resistance guidance.
• University of Wisconsin Turfgrass Diagnostic Lab, disease identification and fungicide-failure troubleshooting.
• US EPA, FIFRA pesticide labeling and use requirements, 40 CFR 156.