Yellow Patches in No-Till Corn: Sorting Cause Before the Tank

Start by ruling causes in or out with evidence, not with a product. The pattern is the biggest clue - damage is patchy and edge-associated, not uniform across the field.

• Pattern: edge/creek-side plus old manure lanes points to soil variability, drainage, compaction from manure equipment traffic, or pH/nutrient banding - not a field-wide pathogen or insect.
• Roots: stubby, brown-tipped roots with no leaf lesions fit root pruning. Candidates are rootworm feeding, herbicide carryover from last year's soybean program, anhydrous ammonia or sidedress knife injury, compaction, or waterlogging. Wash roots from both good and bad areas and compare side by side.
• History: pull last year's herbicide records and check the rotation interval on the label for the soybean product used versus corn. Dry falls slow breakdown of soil residuals, so a carryover injury is plausible even where the interval was technically met.
• Soil: pull paired samples (bad patch vs. good patch) for pH, P, K, and compaction; dig a spade to the depth of the brown tips.
• Nematodes/other: if roots stay stubby after washing and no larvae are present, sample for root-lesion nematodes before assuming anything else.

Do not let a product decision run ahead of the diagnosis. Today's answer to the grower is a scouting and sampling plan with a date, not a chemical order.

No, on both counts.

• Insecticide: 0.4 larvae per plant at V5 with larvae already in the root system is not a rescue situation. Larvae inside the root are largely protected from a foliar spray, and rootworm management is decided before or at planting (traited hybrids, soil insecticide, rotation) or as adult management for next year. A rescue foliar insecticide at V5 buys yield protection you cannot measure and costs money plus selection pressure.
• Fungicide: zero foliar lesions and no disease history in the field means a preventive fungicide at V5 is spending money on a problem that is not present. It also adds a tank-mix partner with no agronomic reason, raising the odds of antagonism, phytotoxicity on stressed plants, and a re-entry interval that ties up the field.
• The "neighbor did it" argument is not data. Different hybrid, different field history, different disease pressure. Adjacent fields are not replicates.

A defensible middle path: leave an untreated check strip through the worst and best parts of the field, apply nothing but the labeled herbicide, and re-scout in 7-10 days. If the patches recover as soils dry and warm, the cause was environmental; if they stay stunted, you have a treated/untreated comparison and a real reason to dig deeper.

Agree on the objective, disagree on the tool, and put the disagreement in writing.

• Reframe around dollars: what does he expect the tank-mix to return, and how will he know? Without a check strip there is no way to attribute any yield gain to the product.
• Offer the diagnostic work as the deliverable this week: paired soil samples, root washes, herbicide history review. That gives him something moving forward and keeps you as the trusted advisor rather than the person who said no.
• If he still wants to spray, confirm he is inside the label on rate, timing, and tank-mix compatibility, note your recommendation in the file, and make sure the pass does not conflict with the herbicide's re-entry interval or crop stage restrictions.
• Resistance management: whatever is driving the weed program on this farm, a tank-mix added for no pest reason still counts as an application. Repeated use of the same insecticide mode of action (especially a pyrethroid for rootworm adults) selects resistant populations, and repeated same-group fungicides select resistant pathogens. If a spray does become necessary later, rotate site of action and record the group number.

Recordkeeping: write down the scouting counts, the diagnosis reasoning, the recommendation, and the grower's decision. That record is what separates a professional recommendation from a liability if the field disappoints.