Medical devices, healthcare technology and the business of care
FDA RECALL RECORD · Z-0376-2026

Model: CT 5300; Product Code (REF): 728285; Software Versions: 5.1.0.X & 5.1.1.X; Recall

Model: CT 5300; Product Code (REF): 728285; Software Versions: 5.1.0.X & 5.1.1.X;

FDA recall Class II

Ongoing

FDA lists this Class II recall for Model: CT 5300; Product Code (REF): 728285; Software Versions: 5.1.0.X & 5.1.1.X;. Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-0376-2026
Recall classification
Class II
Enforcement status
Ongoing
Initiation date
Sep 25, 2025
FDA report date
Nov 5, 2025
Quantity in commerce
165 units
Distribution
See key details
FDA cause
Under Investigation by firm

What is being recalled?

Model: CT 5300; Product Code (REF): 728285; Software Versions: 5.1.0.X & 5.1.1.X;

Affected model & UDI checker

Search the exact identifiers published for Z-0376-2026.

The lookup covers structured identifiers listed on this page. A full UDI may also contain lot or serial information; a GTIN match alone does not check those conditions.

Affected products

Model / catalog numberProductLot scope reportedUDI / GTIN
Not specifiedModel: CT 5300; Product Code (REF): 728285; Software Versions: 5.1.0.X & 5.1.1.X;Check source notice00884838113237
FDA code information

Product Code (REF): 728285; UDI-DI: 00884838113237; Serial Numbers: 800031, 800073, 800070, 35064, 35056, 35043, 35029, 800084, 800083, 800076, 800063, 800058, 800048, 800040, 800039, 800038, 800034, 800033, 800028, 800026, 800021, 800018, 800015, 800011, 800010, 800078, 800071, 35078, 35068, 35048, 35036, 800023, 800008, 800004, 800001, 35073, 35069, 35067, 35058, 35051, 35044, 35034, 35031, 35027, 35019, 35015, 35009, 35001, 800065, 35062, 35042, 35040, 35022, 35016, 35059, 800081, 800062, 800003, 35081, 35065, 35061, 35057, 35053, 35052, 35045, 35041, 35035, 35008, 800005, 35006, 800041, 35080, 800056, 35070, 35033, 35021, 800079, 800077, 800069, 800055, 800054, 800053, 800052, 800007, 800002, 35079, 35071, 35063, 35055, 35046, 35017, 35011, 35007, 35002, 800075, 800045, 800044, 800043, 800029, 800027, 800025, 800024, 800016, 800013, 800009, 800051, 800042, 800061, 800046, 800030, 800019, 800014, 800006, 800074, 800066, 35054, 35018, 800060, 800059, 800072, 35032, 35023, 35003, 800080, 800047, 35039, 35038, 35004, 76001, 35077, 35066, 35060, 35030, 35025, 35013, 35012, 35010, 35037, 35082, 35072, 35005, 35026, 800057, 800067, 800037, 800036, 800032, 800020, 35076, 35075, 35074, 35050, 35049, 35047, 35028, 35024, 35020, 35014, 800050, 800049, 800082, 800064, 800022, 800017, 800012;

View the original FDA recall notice

Why was this product recalled?

Issue 1: The potential for unintentional continued gantry/couch movement when a specific button series is used requiring use of manual stop. Issue 2. When performing a helical/Axial scan with ORI (Dose Right index)/ DOM (Dose Modulation), the WED (Water Equivalent Diameter) value might set itself to zero, and this may lead to an insufficient dose setting after the surview. If operator misses the insufficient dose and the WED value in User Interface and continues with the subsequent helical/Axial scans, then the obtained images will be noisy due to low dose setting. Issue 3: Due to a software failure, the ECG wave file is not saved. As a result, the cardiac offline image reconstruction fails due to the missing ECG wave file, and the user might rescan the patient. Issue 4: This issue is software fault in which the patient orientation will be changed to NULL under specific random scenarios resulting in radiation being delivered from the wrong orientation (surview scan) or in the wrong position (clinical scan) and will generate incorrect and undiagnosable surview/clinical images. Patients may be rescanned for surview and/or clinical images. Issue 5: During scanning, the preview image display is not consistent, the images are not arriving at a fixed rate, skipping images from time to time during scanning. The obtained images might not support making the clinical diagnosis and the user might decide to re-scan the patient. Issue 6: If a user presses the left and middle/right mouse buttons together or afterwards in a short time, both commands are executed and an incorrect auto ROI is created. This ROI coordinates won t be assigned as the object is empty. As a result, the threshold of contrast level will not be reached in the UI and this will prevent the system from automatically triggering the subsequent clinical scan. There is potential safety risk identified for additionally tracker shots and/or rescan of a patient when the clinical scan is not triggered. This issue only affects the manual ROI process.

These are potential consequences described in the source. The recall reason does not establish how many injuries or incidents occurred.

What actions did PHILIPS MEDICAL SYSTEMS take?

On September 25, 2025, ELECTRONIC PRODUCT RADIATION CORRECTION/URGENT MEDICAL DEVICE CORRECTION letters were sent to customers. Actions to be taken. - Follow the instructions within the letter on the use of the systems with updated recommendations. Complete and return the provided response form. Circulate the notice to all users of the device, retain the letter and post it in a visible place likely to be seen/viewed. Actions by recalling firm: Philips will contact you to schedule a time for a Philips Field Service Engineer (FSE) to visit your site and install the solution to resolve the issue (reference FCO72800841). Philips will, without charge bring the product into compliance with each applicable Federal standard in accordance with a plan to be approved by the Secretary of Health and Human Services. On September 29, 2025 updated ELECTRONIC PRODUCT RADIATIONCORRECTION/URGENT MEDICAL DEVICE CORRECTION letters were sent to customers to notify of incorrect UDI numbers provided in the initial letter.

Read the manufacturer action recorded by FDA

Recall timeline

  1. Recall initiated by firm

  2. FDA notice posted

  3. FDA classification recorded

  4. FDA enforcement report date

Related FDA submissions

No submission number with an exact verified relationship is linked in the retrieved recall notice.

FDA’s notice explicitly links the submission numbers shown here. Read each filing for its own recorded device and scope.

Source and update history

  1. FDA enforcement data

    First stored snapshot of this source.

  2. FDA device-recall notice

    First stored snapshot of this source.

The history starts with the versions held by MedtechLedger. Earlier source changes are not reconstructed. Official dates and recorded status come from FDA; page summaries describe the source information.

Our data sources and methodology