A French court this month convicted Air France and Airbus of manslaughter in the deaths of 228 people aboard Flight 447, which went down over the Atlantic in June 2009. The BBC covered the verdict in detail. What the coverage doesn't address is the broader pattern the case represents — and what it asks of ordinary people who trust complex automated systems every day.

What actually happened, and why it still matters

Flight 447 didn't crash because of a single catastrophic failure. It crashed because of a sequence: ice crystals blocked the pitot tubes that measure airspeed, the autopilot disconnected, and the human crew then fought the automation rather than the actual aerodynamic problem. The plane entered a stall from which it never recovered.

The system failed to make its own failure legible to the people responsible for catching it.

That phrase is worth sitting with. The aircraft's automated systems were not transparent about what they were doing or why. The pilots had trained extensively on normal operations but were less prepared for the moment automation stepped back and handed them an ambiguous emergency at 35,000 feet in the dark.

Seventeen years later, this pattern has not gotten rarer. It has gotten more common. Automated systems now mediate how we heat our homes, how our financial accounts respond to unusual activity, how medical devices monitor patients, and — increasingly — how workplaces and logistics networks make decisions. The sophistication has increased. The legibility, in most cases, has not.

What this means for a household

No family is going to redesign an Airbus. But the verdict surfaces something practically useful: the question of what you do when a system you depend on fails silently.

A "silent failure" is one where something has gone wrong but no obvious alarm has fired. The heating system that stops working on a cold night. The generator that starts but doesn't actually transfer power. The water filter that clogs but shows no indicator light. The backup battery that registers full charge but can't hold a load.

These are the household equivalents of the pitot tube problem. The interface said one thing. Reality said another.

What we'd actually do

Test your backup systems under load, not just at rest. Plug a space heater into your generator and run it for 20 minutes. Put your UPS battery backup under real draw. Most equipment failures that show up in emergencies were present for months in standby mode. A BBC report from this month notwithstanding, you don't need to be thinking about airplanes — you need to be thinking about what your own systems tell you versus what they're actually doing.

Write down what failure looks like, not just what normal looks like. For each backup system you own (generator, water filter, secondary heat source), take five minutes to list two or three signs that it has silently failed. Most people can describe what success looks like. Almost no one has written down the warning signs short of total breakdown.

Reduce your automation dependency for one critical function. Pick the household system that matters most to you in an emergency — heat, water, food storage, communication — and verify you have a fully manual fallback that requires no electricity and no network connection. Not as a doomsday measure. As a hedge against silent failure.

Get a second opinion on anything you can't directly observe. Carbon monoxide detectors, smoke alarms, and water quality tests exist precisely because human senses don't catch those failures in time. Recent BLS consumer expenditure data consistently shows households underinvest in detection relative to response gear. A CO detector costs less than a single tank of generator fuel.

Practice the handoff. The Flight 447 crew's hardest moment was the transition from automated flight to manual control under stress. You have equivalent handoffs in your household: the moment the power goes out and you switch to backup, or the moment a water main breaks and you shift to stored supply. Run through those transitions out loud at least once a year, not just in your head.

The bigger picture

The manslaughter conviction matters legally for the families of 228 people. What it means analytically is that courts are now holding institutions accountable for designing systems that obscure failure from the humans who must catch it.

That principle does not stay at 35,000 feet. It applies to every layer of infrastructure households depend on. The goal is not to become suspicious of every automated system you use. It is to stay in the loop — to understand, at a basic level, how you'd know when something has gone wrong and what you'd do next.

Durability is not about owning the right gear. It is about maintaining enough situational awareness that you don't find out a system has failed by experiencing its consequences.