Cricket Farm Die-Off Root Cause Analysis: A Systematic Approach

When a die-off happens on your cricket farm, the instinct is to check the obvious thing, fix what looks wrong, and move on. That reactive approach works sometimes - but farms that conduct systematic root cause analysis after die-off events prevent recurrence in 80% of cases. Those that don't investigate systematically tend to experience the same type of die-off again within two production cycles.

This guide gives you a 5-step die-off investigation framework tied to the data you can collect from CricketOps and your physical records. The goal is to go from "crickets died" to "here's what caused it and here's what I've changed" within 48-72 hours of discovering the event.

TL;DR

• Farms that conduct systematic root cause analysis after die-off events prevent recurrence in 80% of cases.
• A 5-step investigation framework takes you from 'crickets died' to 'here is what caused it and what changed' within 48-72 hours.
• The four most common die-off causes in order of frequency are: temperature excursion, dehydration, ammonia buildup, and disease introduction.
• Per-bin mortality data from the 72 hours before the die-off is the most valuable data for root cause analysis -- this is why continuous logging matters.
• A die-off affecting only one bin points to bin-specific conditions; a die-off affecting multiple bins simultaneously points to a facility-wide cause.
• Corrective actions from die-off investigations must be documented in your FSMA corrective action log if you are a registered food facility.

Step 1: Quantify the Event

Before you can analyze, you need to document. Within hours of discovering a die-off:

• Count and record mortality: How many crickets died? From how many bins? Is this a single-bin event or a facility-wide event?
• Note the timing: When did you first notice? When was the last observation where these crickets appeared healthy?
• Assess the pattern: Is mortality concentrated in one age group (pinheads, juveniles, adults)? One location in the facility? One bin type? Specific bins that were started on the same date?
• Photograph the affected bins: Document what the mortality looks like - do crickets appear stressed before dying, or is death sudden? Are bodies in one location in the bin or distributed throughout?

The pattern of mortality tells you a great deal before you've checked anything else. Age-specific mortality suggests a developmental vulnerability (hydration for pinheads, temperature shock for juveniles). Location-specific mortality suggests an environmental gradient (hot spot, cold spot, ammonia concentration). Bin-type-specific mortality suggests a substrate or equipment issue.

Step 2: Check Environmental Records First

Environmental problems are the most common cause of sudden die-offs on cricket farms. Before you assume disease or contamination, rule out temperature and humidity issues.

Pull your CricketOps environmental logs for the 72 hours preceding the die-off:

• Temperature excursion: Did temperature spike above 95F or drop below 70F in the affected zone? Even a brief excursion can trigger a delayed die-off 12-24 hours later as heat-stressed crickets succumb progressively.
• Humidity excursion: Did humidity drop below 30% for an extended period? Dehydration die-offs are common in dry climates or during winter heating season when indoor humidity drops.
• Ammonia spike: Do you have CO2 or ammonia monitoring? High ammonia from inadequate ventilation kills crickets quickly and often affects the densest/oldest bins first.
• Equipment failure: Did any heating, cooling, or ventilation equipment fail during the period? Check your maintenance logs.

In most investigations, you'll find the answer here. Environmental data doesn't lie, and it gives you a specific, actionable cause to correct.

Step 3: Review Recent Changes

After checking environmental records, review what changed in the 1-2 weeks before the die-off. Changes that commonly precede die-offs:

• New feed or feed batch: A contaminated or nutritionally deficient feed batch is a common cause of widespread die-offs across multiple bins
• New substrate: A new batch of substrate (egg boxes, cardboard) that introduced a pesticide residue or treated wood chemical
• New water source or water treatment: Change in municipal water treatment, well water contamination, or introduction of chlorine in water not previously treated
• New equipment or cleaning chemicals: A new cleaning product or disinfectant that wasn't fully rinsed before use
• New animals: Introduction of outside crickets, egg containers from another source, or any other biological input
• Facility changes: New lighting, new heating equipment, changes to ventilation

If a change correlates temporally with the die-off, it becomes your prime suspect. Investigate that change specifically before moving on.

Step 4: Categorize the Probable Cause

Based on your environmental data and change review, categorize the die-off into one of these cause categories:

1. Thermal stress - temperature excursion above or below survival range
2. Dehydration - humidity failure or water source inaccessibility
3. Toxic exposure - pesticide, cleaning chemical, treated material
4. Pathogen - bacterial or viral infection (requires lab testing to confirm)
5. Nutritional deficiency - feed quality problem or feed interruption
6. Ammonia toxicity - ventilation failure or overcrowding in hot conditions
7. Mechanical - equipment failure leading to environmental collapse
8. Unknown - if none of the above fit, escalate to lab testing

Categories 1-3 account for the large majority of die-offs at farms with no history of pathogen problems. Categories 4-5 become more likely in older operations with dense populations.

Step 5: Implement Corrective Action and Document

For whichever cause category you've identified:

• Implement the immediate corrective action (fix the equipment failure, change the feed, improve ventilation)
• Document the investigation in your CricketOps batch records tied to the affected bins
• Update your preventive controls: what monitoring or check will catch this earlier next time?
• Note the event in your food safety plan corrective action log if you're producing cricket flour

The documentation step is what separates systematic root cause analysis from reactive management. When the next die-off happens, your records from this event will help you identify patterns faster. For ongoing mortality monitoring, see the guide on how to track cricket mortality. For your overall production management framework, see cricket farm management.

Frequently Asked Questions

How do I find out why my crickets died?

Start with your environmental data: pull temperature and humidity logs for the 72 hours before the die-off. Most sudden die-offs trace back to a temperature spike or drop, a humidity crash, or a ventilation failure that created ammonia accumulation. If environmental records look normal, review what changed in the 1-2 weeks before the event - new feed, new substrate, new cleaning products, or new animals are the next most common causes. Collect and document your mortality observations (which age groups, which bins, what pattern) before disturbing the affected bins, as that information helps narrow the cause quickly.

What data should I collect during a cricket farm die-off investigation?

During a die-off investigation, collect: mortality count and affected bin identification, timing of when die-off was first noticed vs last healthy observation, environmental log data for 72 hours pre-event (temperature, humidity, any equipment alerts), photos of affected bins showing mortality pattern and cricket appearance, notes on any changes in the preceding 1-2 weeks (new feed batch, new substrate, cleaning products used, equipment changes, water source changes), and physical samples of any suspected contaminated feed or substrate. If you suspect pathogen involvement, collect dead cricket samples in a sealed bag for potential lab submission. Keep all this documentation in your CricketOps batch records tied to the specific affected lots.

Does CricketOps help identify die-off root causes?

CricketOps supports die-off root cause analysis through bin-level environmental logging, mortality tracking, and batch record documentation. When a die-off event occurs, you can pull the environmental history for affected bins and compare it against the timeline of the event. You can flag affected bins in the system and attach investigation notes directly to the batch record, creating a documented timeline of the event and your response. The system's mortality tracking over multiple production cycles also helps you identify patterns - bins that repeatedly experience higher mortality than others, or die-offs that consistently occur at a particular stage of the production cycle - that point to systemic causes rather than one-time events.

How does CricketOps help track the metrics described in this article?

CricketOps provides bin-level logging for the variables that drive production outcomes -- feed inputs, environmental conditions, mortality events, and harvest results. Rather than maintaining these records in separate spreadsheets, you can view performance trends across bins and over time to identify which operational variables correlate with better outcomes in your specific facility.

Where can I find industry benchmarks to compare my operation's performance?

The North American Coalition for Insect Agriculture (NACIA) publishes periodic industry reports with production benchmarks. University extension programs in agricultural states, including the University of Georgia and University of Florida IFAS, occasionally publish insect farming production data. Industry conferences hosted by the Entomological Society of America and the Insects to Feed the World symposium series are additional sources of peer benchmarking data.

What is the biggest operational mistake cricket farmers make in their first year?

Expanding bin count before achieving consistent FCR and mortality targets in existing bins is the most common and costly first-year mistake. At 5-10 bins, problems are manageable. At 30-50 bins, the same proportional problems represent much larger financial losses. Most experienced cricket farmers recommend holding expansion until you have three consecutive production cycles hitting your FCR and mortality targets.

Sources

• Food and Agriculture Organization of the United Nations (FAO) -- Edible Insects: Future Prospects for Food and Feed Security
• North American Coalition for Insect Agriculture (NACIA)
• Entomological Society of America
• University of Georgia Cooperative Extension
• Journal of Insects as Food and Feed (Wageningen Academic Publishers)

Get Started with CricketOps

The practices covered in this article are easier to apply consistently when they are supported by organized production data. CricketOps gives cricket farmers the tools to track what matters -- by bin, by batch, and over time. Start your next production cycle in CricketOps and see how organized data changes the way you manage your operation.