Spruce beetle vs. mountain pine beetle: telling them apart from the air

Get a crown survey back with a block of red-attack on it and the first question from the district isn't "how bad." It's "which beetle." The answer changes the cruise, the salvage window, and sometimes the whole harvest plan, so it's worth getting right before anyone drives out there.
Neither mountain pine beetle nor spruce beetle leaves a signature you can read from color alone. You need the host, the pattern, and the timing together.
Start with what's standing, not what's red
Mountain pine beetle works lodgepole and ponderosa pine. Spruce beetle works Engelmann and white spruce, and it mostly ignores everything else on the slope. That sounds obvious until you're looking at a mixed stand with fir scattered through it and the red crowns could plausibly be either, at a glance, on a screen.
Pull the stand type layer before you call it. Pure lodgepole at mid-elevation, pine is the leading suspect. Spruce-fir up near the subalpine edge, you're probably looking at spruce beetle, especially if the red crowns sit in that narrower, deep blue-green canopy rather than the paler yellow-green of pine. A crown that was never pine can't have mountain pine beetle in it, which sounds like it shouldn't need saying, but it's the single fastest filter available and the one people skip when they're moving fast through a big AOI.
Read the pattern, not just the pixel
This is where the two species actually diverge in how damage shows up on imagery.
Mountain pine beetle runs a one-year life cycle in most of its range, and broods emerge in a tight window in mid to late summer. That synchrony shows up as blocky, contiguous red patches, whole hillsides turning in the same season because the attack was concentrated the year before. If you're seeing solid red polygons with clean edges against green, pine fits that behavior well.
Spruce beetle is messier on purpose. At higher, colder elevations it often runs a two-year cycle, so you get staggered emergence and attack that spreads out over more seasons rather than hitting all at once. The red shows up more scattered, individual crowns and small clusters fading in at different times rather than a block turning together. Spruce also tends to hold needles a little longer after attack before the crown reddens, so what you're seeing in a given month can lag the actual infestation by more than it would in a pine stand. If a flight catches a stand mid-transition, it's worth flagging it as "watch" rather than committing it to a stage, because the next pass might move it further than expected.
Flight timing of the beetle itself matters too, if you're cross-checking against known regional data. Spruce beetle typically flies in late spring to early summer; mountain pine beetle flies later, usually mid-to-late summer. If a crown record has an associated attack date from ground reports, that date alone can rule one species in or out before you look at a single pixel.
Where this gets expensive
Salvage crews that misread species end up scoping the wrong stand type for the wrong equipment, or they sit on a spruce stand waiting for the clean red-to-grey progression a pine crew would expect, and lose volume to blue stain while they wait. Getting host and pattern right before the cruise goes out saves that round trip.
None of this replaces a ground check on a stand that's going to salvage. What it does is narrow the list to the stands worth checking first, and keep a mixed-species unit from getting treated as one infestation when it's really two. A monthly scored layer tracking red-attack through grey-attack across the monitoring area does the repeat-pass part of this for you, so the question when the imagery lands isn't "has this moved" but "how far."
If you're staging this year's salvage list and want that stage-by-stand read without waiting on the next survey flight, that's the gap Bark Beetle Detection is built to close.