how automated healthcare fails, how you'd know, and what to do at each tier — every claim sourced, reviewed continuously
Incident
Air France 447: autopilot hands a stalled aircraft back to a crew (non-clinical analogue)
1 June 2009Atlantic Ocean, Rio de Janeiro-Paris flightNon-clinical analogueHuman handoff
Non-clinical analogue. Iced pitot probes caused inconsistent airspeeds, the autopilot disconnected, and the crew did not recognise or recover from a stall.
Sources checked when written 26 September 2026
What happened
NON-CLINICAL ANALOGUE. According to the BEA final report (July 2012), obstruction of the Airbus A330's pitot probes by ice crystals caused a temporary inconsistency in measured airspeeds, which disconnected the autopilot and reconfigured the flight controls to alternate law. The crew's control inputs destabilised the flight path, they did not link the loss of airspeed indications to the relevant procedure, and they did not identify the approach to stall or the stall itself; the aircraft, carrying 228 people, struck the surface of the ocean. The BEA cited an absence of high-altitude manual handling training and of training on the speed-anomaly procedure, task-sharing weakened by startle and incomprehension, the lack of a clear cockpit display of the airspeed inconsistencies, and the crew not taking the stall warning into account.[1,2]
Documented harm
Non-clinical: loss of the aircraft with 228 people on board.
What it teaches
The handback arrives at the worst moment, with the least context, to the people who have practised it least.
If the machine knows its inputs disagree, it must show that plainly at handback.
Manual skills for rare failures must be rehearsed in realistic conditions, not assumed.
Information only, not advice. FailSystems is an aggregation and synthesis of published sources. It is not consulting, engineering, legal, regulatory or medical advice, and using it creates no professional relationship. Health systems are complex and no approach fits every organisation: anything you adopt is your own decision, at your own risk, and should be checked against the current official sources and by qualified people who know your setting. Full disclaimer.
Dealing with an incident right now? This site is a reference, not an incident-response service. Activate your organisation's emergency operations plan and incident command, and:
Power loss, disaster or resource needs: go through your local or county emergency management. They escalate to the state, and the state requests FEMA support; hospitals do not call FEMA directly.
A medical device problem: report it to the manufacturer and to FDA MedWatch.
Outside the US: your national emergency number and national cyber agency (in the UK, NCSC).