UT Pesticide Applicator study materials
UT Pesticide Applicator study resources

Diagnosing a Declining Block Before You Spray

UT Pesticide Applicator · Put your knowledge to work in context.

All case studies

Diagnosing a Declining Block Before You Spray

A Utah grower calls you about a 15-acre alfalfa field that is thinning in irregular patches. Stands look sparse in low areas, some plants are yellowed with stunted growth, and a few dead plants have darkened roots when dug. The grower has already bought a broad-spectrum soil insecticide and wants you to apply it this week - the field was alfalfa last year and the year before. Soil is a silt loam, and the low areas stay wet after irrigation. The grower says the neighbor's field 'looks fine' and is convinced the problem is insects. Your budget allows one diagnostic visit before any application.

1. How do you structure the diagnostic visit, and what are the leading candidate causes you need to rule in or out?

Read the worked answer

Structure the visit around pattern, plant, and soil - before touching a sprayer.

  1. Map the pattern. Irregular patches concentrated in low, wet areas point toward soil-borne or drainage-related problems, not a uniform insect infestation. Sketch the field and note where the bad areas sit relative to drainage and irrigation.
  2. Dig plants at the margin of a bad patch - the transition zone is where living and dying plants show the most diagnostic symptoms. Compare to healthy plants from a good area.
  3. Examine roots and crowns. Darkened, rotted roots with a brown vascular discoloration suggest root/crown disease. Look for insect feeding injury (root scarring, chewed nodules, larvae in soil) separately.
  4. Sample soil from both bad and good areas for texture, drainage, and any nematode assay if warranted.
  5. Check the stand history. A field in alfalfa for multiple years carries autotoxicity and disease-build-up risk; the grower's rotation history matters.

Leading candidates to rule in/out:

  • Poor drainage / waterlogging in the low areas (consistent with the pattern and wet soils).
  • Root and crown diseases (the darkened roots and dead plants).
  • Autotoxicity from alfalfa following alfalfa (thinning, poor establishment).
  • Insects - still possible, but the pattern and symptoms do not point there first.
  • Nutrient or salinity issues in the low spots.

2. The grower insists on the insecticide. What is your professional and legal position, and what would you do?

Read the worked answer

Professional position: Applying an insecticide before confirming an insect problem is poor practice. It costs money, may not address the cause, and can disrupt beneficials - and if the real cause is drainage or disease, the field will keep declining and the grower will blame the application.

Legal position: The label governs. A soil insecticide has labeled target pests and a labeled use site. Applying it to alfalfa for a pest you have not confirmed is a use inconsistent with the labeling if the target is not among the labeled pests or the situation does not match the label's directions. Even where the site is labeled, you are responsible for applying only as directed.

What to do:

  • Do not apply this week. Tell the grower plainly that you will not spray until the cause is identified, and explain why - this protects the crop, the grower's money, and your license.
  • Complete the diagnostics (root/crown inspection, soil samples, pattern map). If a pathogen is confirmed, an insecticide is the wrong tool and a fungicide or cultural fix may be indicated.
  • If an insect is confirmed, match it to the label's target list and follow the labeled rate and timing.
  • Put your recommendation in writing so the record shows you advised against the premature application.

Refusing a client's request when the diagnosis doesn't support it is part of the job.

3. The grower says, 'The neighbor's field is fine, so it can't be the soil.' How do you handle that reasoning?

Read the worked answer

The comparison is weaker than it looks. Neighboring fields differ in ways that directly affect the candidate causes:

  • Drainage and topography. Your low areas stay wet; the neighbor's field may be higher, better drained, or irrigated differently. Waterlogging is site-specific.
  • Stand age and rotation history. Your field has been alfalfa multiple years; the neighbor's may be younger or in a different rotation. Disease build-up and autotoxicity are history-dependent.
  • Soil variability. Even within one farm, silt loam areas can differ in depth to a restrictive layer, organic matter, and salinity. 'The neighbor's is fine' says nothing about your field's low spots.
  • Management differences. Variety, seeding date, fertility, and irrigation scheduling all differ.

How to use the comparison productively: it is actually a useful clue. If the problem tracks your low, wet areas and not the neighbor's field, that supports a site-specific cause like drainage or soil-borne disease over a field-wide pest outbreak. Point this out to the grower - it strengthens the case for diagnostics rather than weakening it.

Bottom line: a neighboring field is not a control. The right comparison is bad areas vs. good areas within the affected field, sampled the same way.