Allura Xper FD Allura Xper FD10 (REF 722026)Recalls & reported problems

Summary

The FDA's MAUDE database contains 2,015 adverse event reports that list this exact device (DI 00884838054189), received between Nov 22, 2017 and Sep 30, 2026 — classified as 2 deaths, 6 injuries, 2,007 malfunctions.

The most frequently reported specific device problem is “Activation Failure” (1,053 reports).

23 FDA recall records name this device's identifier, 22 still open.

Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event, and counts can't be used to compare devices or estimate failure rates. What reports can and can't tell you · How this data works · Data updated Oct 18, 2026.

Recalls naming this device

1. Jun 29, 2026Class IIOpen, Classified

   Firmware issue potentially leading to loss of geometry movements.

   Z-2928-2026 · Root cause: Software design · Recall details · FDA record ↗

2. Jun 17, 2026Class IIOpen, Classified

   Potential Loss of imaging functionality, loss of motorized movement, or loss of data due to unauthorized Hard Disk Drives.

   Z-2891-2026 · Root cause: Under Investigation by firm · Recall details · FDA record ↗

3. Apr 30, 2026Class IIOpen, Classified

   It was identified that HDDs used in the PCs of Azurion and Allura systems may show a decrease in performance as they age, particularly beyond six years of service. Issues with an HDD may, depending on the specific system PC in which the affected HDD is installed, result in loss of imaging functionality. Additionally, in Allura systems, this may lead to loss of motorized movement, or loss of data. In some cases, a system restart may temporarily restore functionality.

   Z-2259-2026 · Root cause: Under Investigation by firm · Recall details · FDA record ↗

4. Apr 28, 2026Class IIOpen, Classified

   The deaeration hose in X-ray tube cooling units type CU3101, manufactured between February 2016 and May 2020, may degrade over time, potentially resulting in oil leakage. Oil leakage may affect the cooling performance of the X-ray tube. When the oil flow drops below a certain threshold, the system automatically switches to low-dose fluoroscopy and displays the message Low load fluoroscopy flavor selected: Tube cooler problem . This condition cannot be resolved by restarting the system.

   Z-2228-2026 · Root cause: Component design/selection · Recall details · FDA record ↗

5. Mar 3, 2026Class IIOpen, Classified

   Philips has identified instances where X-ray imaging may not be initiated or may occur intermittently when using the wired foot switch.

   Z-1661-2026 · Root cause: Device Design · Recall details · FDA record ↗

6. Dec 15, 2025Class IIOpen, Classified

   Philips has identified that in a limited number of impacted systems the drip tray beneath the cooling unit was not installed under previous field corrections, or evidence of the implementation was not adequately documented. If it is not installed, there is a potential for coolant liquid to contact electrical components. This could lead to electrical short-circuits, which may trigger system fuses and result in system shutdown.

   Z-1073-2026 · Root cause: Other · Recall details · FDA record ↗

7. Sep 3, 2025Class IIOpen, Classified

   Systems may not perform as intended due to the deterioration of certain internal components (the CMOS battery, hard disk drive, and/or power supply unit). If this deterioration occurs, motorized movements of the system will become unavailable. Manual movements of the stand (longitudinal, transversal and rotational for ceiling mounted systems and rotational for floor mounted systems) and table longitudinal movements remain available. Imaging (X-ray) functionality remains available.

   Z-2623-2025 · Root cause: Device Design · Recall details · FDA record ↗

8. Sep 3, 2025Class IIOpen, Classified

   The BIOS battery may deplete faster than initially anticipated during the design phase. When the battery is depleted, the start-up process of the system will be halted, and the system will not start. No user messages are shown before the battery is low on power or depleted.

   Z-0002-2026 · Root cause: Device Design · Recall details · FDA record ↗

9. Aug 1, 2025Class IIOpen, Classified

   Philips Azurion and Allura systems configured with a 1 Phase Uninterruptible Power Supply (UPS) have the potential of shutting down and/or not starting up, if power to the system is lost.

   Z-2503-2025 · Root cause: Under Investigation by firm · Recall details · FDA record ↗

10. Aug 1, 2025Class IIOpen, Classified

    Potential that a component (air baffle) may be missing in some Nehalem FlexVision-2 PCs that are part of the Allura Xper series.

    Z-2504-2025 · Root cause: Under Investigation by firm · Recall details · FDA record ↗

11. Jun 30, 2025Class IIOpen, Classified

    Potential for temporary loss of imaging (X-ray) functionality due to software issue.

    Z-2189-2025 · Root cause: Software design · Recall details · FDA record ↗

12. Jan 13, 2025Class IOpen, Classified

    Possibility of the patient falling from the table related to the mattress used on the patient table.

    Z-1142-2025 · Root cause: Under Investigation by firm · Recall details · FDA record ↗

13. Jan 13, 2025Class IIOpen, Classified

    Potential safety issue with the AD7 and AD7X patient tables (both tilt and non-tilt versions) part of the Philips Allura and Azurion systems. During manual repositioning of the patient tabletop, a finger can get entrapped between the longitudinal guiding rails and the tabletop. This may result in an injury of the finger, applicable for operators and service personnel

    Z-1077-2025 · Root cause: Device Design · Recall details · FDA record ↗

14. Nov 11, 2024Class IIOpen, Classified

    Potential safety issues in Allura Xper R7.6- R8.1 systems where the Lifetime Extension (LTE) kit is not installed in a timely manner. Root cause is under investigation, but the recall reason is listed as for systems over 10 years of life with LTE kits are experiencing propeller motor clamping bolt and x-ray tube locking bolt breaks. If this happens, it may cause erratic C-arm movements and potential collision with patients or bystanders, or detection of a false collisions and subsequent blocked movement of the c-arm. Movement may also cause image noise and black area on the x-ray image, and possible need to expose the patient to additional unnecessary radiation during re-examination.

    Z-0676-2025 · Root cause: Equipment maintenance · Recall details · FDA record ↗

15. Aug 22, 2024Class IIOpen, Classified

    Potential Detachment of the Cable Hose Carrier (due to broken plastic and/or bolts) which May Result in Parts Falling and/or Part of the Cable Hose Dropping, and result in injury.

    Z-3166-2024 · Root cause: Device Design · Recall details · FDA record ↗

16. Jan 2, 2024Class IIOpen, Classified

    Disk Bay may not perform as intended. System may stop functioning and imaging may not be possible, resulting in delay of procedure.

    Z-1151-2024 · Root cause: Process design · Recall details · FDA record ↗

17. Jan 2, 2024Class IIOpen, Classified

    Dual In-Line Memory Modules (DIMMs) may not perform as intended. System may stop functioning and imaging may not be possible, resulting in delay of procedure.

    Z-1156-2024 · Root cause: Process design · Recall details · FDA record ↗

18. Jan 2, 2024Class IIOpen, Classified

    Framegrabber card may not perform as intended. Monitor may show no viewports, or show one or more viewports may show no image, a distorted image, or a frozen image. Switching between viewports on the monitor may not be possible. Issue may result in delay of procedure.

    Z-1144-2024 · Root cause: Process design · Recall details · FDA record ↗

19. Nov 3, 2023Class IIOpen, Classified

    Ceiling mounted L-arm contains a rotation cover that may potentially be susceptible to falling if a collision between the L-arm and other hospital equipment (i.e., an operating light) were to occur result in injury or potential sterility issues due to the cover becoming loose

    Z-0558-2024 · Root cause: Device Design · Recall details · FDA record ↗

20. Jun 12, 2023Class IIOpen, Classified

    The bolts supporting the FlexMove Carriage may become loose and/or break, and cracks may appear in the suspension rail of the FlexMove Carriage.

    Z-2283-2023 · Root cause: Component design/selection · Recall details · FDA record ↗

21. Feb 2, 2022Class IIOpen, Classified

    Due to a software defect, the Philips StentBoost Live R2.0 might not process X-ray images of the current run and instead show an image processed in a previous run. The image shown could be from the same patient or from a different patient.

    Z-0874-2022 · Root cause: Under Investigation by firm · Recall details · FDA record ↗

22. Nov 24, 2021Class IIOpen, Classified

    Due to a leak in the detector cooling system, cooling liquid may leak outside the drip tray of the chiller. If this occurs the liquid may drip onto electrical components in the R cabinet located in the technical room, which could lead to damage to the system and potentially cause thermal events such as a burning odor, smoke or fire.

    Z-0724-2022 · Root cause: Process control · Recall details · FDA record ↗

23. Nov 19, 2021Class IITerminated

    Set screws securing the two gliding rods of the Extra Monitors (called 7th and 8th monitor) mounted on the Monitor Ceiling Suspension (MCS) can come loose, the Extra monitors might disengage from the Mounting Ceiling Suspension structure and fall down, may lead to patient, user or service engineer harm that may require medical intervention.

    Z-0416-2022 · Root cause: Other · Recall details · FDA record ↗

Most reported problems

Recent adverse event reports

The 25 most recent of 2,015 reports, in the reporter's own words as published by the FDA.

• MalfunctionSep 30, 2026Radiation Output Failure

  It was reported to Philips that the system was unable to perform exposure.The system was in clinical use at the time of the event. No harm to the patient or user was reported.Philips has started an investigation of this complaint.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 50942746 ↗
• MalfunctionSep 28, 2026Radiation Output Failure

  It was reported to Philips that the system was unable to emit X-ray.The system was in clinical use at the time of the event. No harm to the patient or user was reported.Philips has started an investigation of this complaint.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 50911262 ↗
• MalfunctionSep 25, 2026Radiation Output Failure

  It was reported to Philips that the system displayed an alert indicating ¿Low load fluo flavor selected: Tube rotor problem,¿ impacting imaging.The system was in clinical use at the time of the event. No harm to the patient or user was reported.Philips has started an investigation of this complaint.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 50893322 ↗
• MalfunctionMay 29, 2026Radiation Output Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM WAS UNABLE TO PRODUCE X-RAYS. THE SYSTEM WAS IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25328202 ↗
• MalfunctionMay 22, 2026Positioning Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM¿S C-ARM WAS UNABLE TO PERFORM GEOMETRY MOVEMENTS. THE SYSTEM WAS IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25253433 ↗
• MalfunctionMay 22, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT SYSTEM WAS UNABLE TO BOOT UP. THE SYSTEM WAS NOT IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25252290 ↗
• MalfunctionMay 21, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM WAS UNABLE TO BOOT UP. THE SYSTEM WAS OUTSIDE OF CLINICAL USE AT THE TIME OF REPORTED EVENT. NO HARM WAS REPORTED TO PHILIPS. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25238422 ↗
• MalfunctionMay 19, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT THE FLEXVISION MONITOR WAS UNABLE TO TURN ON. THE DEVICE WAS IN CLINICAL USE AT THE TIME OF REPORTED EVENT. NO HARM WAS REPORTED TO PHILIPS. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25216559 ↗
• MalfunctionMay 18, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT SYSTEM WAS UNABLE TO POWER ON. NO HARM WAS REPORTED TO PHILIPS. THE DEVICE WAS NOT IN CLINICAL USE AT THE TIME OF REPORTED EVENT. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25197477 ↗
• MalfunctionMay 14, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM UNABLE TO BOOT, STALLING AT 00:00. THE SYSTEM WAS NOT IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25168713 ↗
• MalfunctionMay 12, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM'S WAS UNABLE TO BOOT, PREVENTING A FULL SYSTEM BOOT. THE SYSTEM WAS IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25146234 ↗
• MalfunctionMay 11, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM WAS UNABLE TO BOOT UP. THE SYSTEM WAS OUTSIDE OF CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25134395 ↗
• MalfunctionMay 8, 2026Positioning Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM Z ROTATION GEOMETRY MOVEMENT WAS NOT AVAILABLE. THE DEVICE WAS IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25122026 ↗
• MalfunctionMay 8, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM'S HOST COMPUTER WAS UNABLE TO BOOT, PREVENTING A FULL SYSTEM BOOT. THE SYSTEM WAS NOT IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25120789 ↗
• MalfunctionMay 7, 2026Radiation Output Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM WAS UNABLE TO PERFORM EXPOSURE. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25110547 ↗
• MalfunctionMay 5, 2026Radiation Output Failure

  IT WAS REPORTED TO PHILIPS THAT X-RAY ACQUISITION COULD NOT BE PERFORMED DUE TO A DISK FULL ERROR. THE SYSTEM WAS IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25084502 ↗
• MalfunctionApr 29, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT DURING THE PROCEDURE, THE SYSTEM AUTOMATICALLY SHUT DOWN, WHICH COULD INDICATE AN ISSUE WITH BOOTING. THE SYSTEM WAS IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25034446 ↗
• MalfunctionApr 28, 2026Positioning Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM'S GEOMETRY MOVEMENTS WERE UNAVAILABLE. THE CUSTOMER PERFORMED REBOOT, BUT THE ISSUE PERSISTED. THE PROCEDURE WAS COMPLETED IN ANOTHER ROOM. THE SYSTEM WAS IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25011486 ↗
• MalfunctionApr 27, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM WAS UNABLE TO BOOT. THE SYSTEM WAS NOT IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 25002075 ↗
• MalfunctionApr 14, 2026Positioning Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM'S GEOMETRY COMPUTER WAS UNABLE TO BOOT, PREVENTING GEOMETRY MOVEMENTS. THE DEVICE WAS IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 24875587 ↗
• MalfunctionApr 7, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM'S HOST COMPUTER WAS UNABLE TO BOOT, PREVENTING A FULL SYSTEM BOOT. THE DEVICE WAS IN CLINICAL USE AT THE TIME OF THE EVENT. NO HARM TO THE PATIENT OR USER WAS REPORTED. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 24800525 ↗
• MalfunctionMar 30, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT UPON RESTARTING THE SYSTEM, IT TOOK AN EXTENDED AMOUNT OF TIME TO REBOOT, DELAYING THE PROCEDURE. THE DEVICE WAS IN CLINICAL USE AT THE TIME OF REPORTED EVENT. NO HARM WAS REPORTED TO PHILIPS. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 24712561 ↗
• MalfunctionMar 10, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM WAS UNABLE TO BOOT UP. THE DEVICE WAS OUTSIDE OF USE AT THE TIME OF REPORTED EVENT. NO HARM WAS REPORTED TO PHILIPS. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 24556890 ↗
• MalfunctionMar 6, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM WAS UNABLE TO BOOT UP. THE DEVICE WAS OUTSIDE OF USE AT THE TIME OF REPORTED EVENT. NO HARM WAS REPORTED TO PHILIPS. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 24528851 ↗
• MalfunctionMar 2, 2026Activation Failure

  IT WAS REPORTED TO PHILIPS THAT THE SYSTEM WAS UNABLE TO BOOT UP. NO HARM WAS REPORTED TO PHILIPS. PHILIPS HAS STARTED AN INVESTIGATION OF THIS COMPLAINT.

  Patient problems: No Clinical Signs, Symptoms or Conditions

  MAUDE report 24484252 ↗