Sometimes the Supreme Court hands down a decision that doesn’t just split along predictable ideological lines. It flips the script entirely. That’s exactly what happened in Hencely v. Fluor Corp., where a 6–3 majority allowed a wounded U.S. soldier’s lawsuit against a military contractor to proceed.

And yes, if you did a double take when you saw that Clarence Thomas wrote the majority opinion—and was joined by several liberal justices—you’re not alone. This wasn’t about left vs. right. It was about something more fundamental: where the line is between necessary protection for wartime operations and basic accountability when things go wrong.

At its core, this case forces us to confront a tough but unavoidable question: Should private contractors operating alongside the military be treated like extensions of the government or like independent actors responsible for their own mistakes?

The Court didn’t fully resolve that question. But it made one thing very clear: the answer is not “automatic immunity, no questions asked.”

Accountability Doesn’t Stop at the Battlefield

There’s a reason the majority’s reasoning resonates, even beyond legal circles. It taps into a pretty basic instinct about fairness and responsibility.

The lower court had effectively adopted a broad “combat zone shield,” treating the mere fact that something happened in a war zone as enough to block a lawsuit. That approach might sound practical on paper, but it creates a dangerous incentive structure in reality. If contractors know they’re protected no matter what, the pressure to rigorously follow safety protocols and oversight procedures starts to erode. And in environments as volatile as military bases in active conflict zones, even small lapses can have catastrophic consequences.

The majority opinion, led by Clarence Thomas, pushed back on that logic. It emphasized that immunity shouldn’t be based on geography alone. Instead, it should hinge on conduct, specifically, whether the contractor was acting under the direction of the military or going beyond (or even against) those directives.

That distinction is crucial. In this case, the allegations against Fluor weren’t that it faithfully executed a risky military order. They were that it failed to follow the military’s own rules, particularly regarding supervision and security protocols. If those allegations are true, then the contractor wasn’t acting as an arm of the government. It was acting independently, and potentially negligently.

Allowing the lawsuit to proceed doesn’t mean Fluor is guilty. It simply means the company doesn’t get to avoid scrutiny altogether. And that’s a big deal. The Court is essentially saying: you don’t get legal immunity just for showing up to the battlefield. You have to earn it by staying within the scope of what the military actually authorized.

From a policy standpoint, this creates a healthier system. It preserves protection for contractors who are genuinely carrying out military directives, while still allowing accountability when those contractors cut corners or fail to meet basic standards. That balance isn’t only reasonable, but necessary if we want to avoid turning wartime contracting into a liability-free zone.

A Lawsuit Waiting to Happen in Every War Zone

Of course, the dissent didn’t raise its concerns just for dramatic effect. There’s a real worry here that the Court may have opened the door to something far messier than it intended.

War zones aren’t controlled environments. They’re chaotic, fast-moving, and often governed by imperfect information. Contractors operating in these settings are already dealing with extreme uncertainty, limited resources, and constantly shifting threats. Expecting them to operate with the same level of clarity and precision as a domestic business is, at best, optimistic and, at worst, unrealistic.

The dissenting justices, including John Roberts, warned that allowing these kinds of lawsuits to move forward could have ripple effects that extend far beyond a single case. Once courts start entertaining claims tied to wartime conduct, it invites second-guessing of decisions made under intense pressure and in rapidly evolving situations. What looks like negligence in hindsight might have seemed like a reasonable judgment call in the moment.

There’s also the broader strategic concern. If contractors face increased legal exposure, they may become more risk-averse or demand significantly higher compensation to offset that risk. That, in turn, could make it more difficult and more expensive for the military to carry out operations that rely on private support. In extreme cases, contractors might even refuse to operate in certain environments altogether, leaving gaps that the military isn’t equipped to fill on its own.

And then there’s the issue of judicial overreach. Courts aren’t designed to manage military operations. When they start adjudicating cases that hinge on battlefield realities, there’s a risk that they step into territory where they lack both expertise and constitutional authority.

So, while the majority sees this as a measured rejection of automatic immunity, the dissent sees something more concerning: a gradual erosion of the boundary between civilian courts and military decision-making.

Drawing a Line Between Oversight and Overreach

What makes Hencely v. Fluor Corp. so compelling isn’t just the legal outcome. It’s the deeper tension it exposes.

On one hand, accountability is a cornerstone of any functioning system. If a contractor’s negligence contributes to a deadly attack, it feels almost self-evident that there should be some avenue for redress. Closing the courthouse doors entirely sends a troubling message, not just to victims, but to anyone operating in high-stakes environments: that certain contexts place you beyond the reach of the law.

On the other hand, war isn’t an ordinary context. It’s governed by a unique set of pressures and constraints that don’t translate neatly into legal standards developed for peacetime disputes. Trying to impose those standards too rigidly risks distorting both the law and the reality it’s trying to regulate.

The Supreme Court didn’t pretend this tension doesn’t exist. Instead, it drew a line that’s imperfect, but arguably necessary. The key idea is that not all wartime conduct is created equal. There’s a meaningful difference between actions taken under direct military command and actions that deviate from or ignore those commands.

By focusing on that distinction, the Court avoided two extremes. It didn’t grant blanket immunity, which would effectively remove any check on contractor behavior. But it also didn’t throw open the floodgates to unlimited liability. The ruling is narrower than critics suggest. It simply allows certain claims to be heard, rather than dismissed outright.

Still, this is a line that will be tested. Future cases will have to wrestle with where exactly “authorized conduct” ends and independent action begins. And as those cases unfold, the balance between oversight and overreach will remain a moving target.

A Sensible Reset with Real-World Consequences

In the end, the Supreme Court’s decision in Hencely v. Fluor Corp. feels less like a radical shift and more like a course correction.

The idea that contractors should be completely shielded from liability simply because they operate in a war zone was always a bit too convenient. It prioritized efficiency and legal simplicity over accountability, and it did so in a way that risked eroding trust in both the system and the institutions involved.

By rejecting that blanket approach, the Court reintroduced a measure of common sense: immunity should depend on behavior, not just context. If a contractor is doing exactly what the military tells it to do, then yes, there’s a strong case for protection. But if it’s acting outside those bounds—especially in ways that allegedly increase risk—then it should at least have to answer for that conduct.

That said, this isn’t a cost-free decision. The dissent is right to point out that there could be unintended consequences. Increased litigation risk may change how contractors operate, how much they charge, and even whether they participate in certain missions at all. Those are real concerns that policymakers and military leaders will need to address moving forward.

But on balance, I believe the Court got this one right.

Because a system that allows for some accountability, even in difficult and dangerous contexts, is ultimately stronger—and more just—than one that offers immunity with no questions asked.

And if that means a few more legal battles down the road? That’s probably a price worth paying.