FDA posted 12 recall records for "Ventilator, Continuous, Facility Use" (product code CBK) on October 20, 2026. It had posted none for this device type in the eight weeks before. All 12 records belong to a single recall from one firm, Ventec Life Systems, doing business as React Health, and all cite the same internal connector.
What moved
The records run from Z-0122-2027 to Z-0133-2027 and share FDA recall event 99835. FDA classified each one Class I, its most serious category. Every record gives the same reason: the ventilator's internal flow transducer cable connector may disconnect from the internal board, potentially resulting in a system reboot and interruption of ventilation therapy.
So the spike is one recall filed product by product. FDA keeps a separate record for each model and regional variant, which turned one engineering issue into 12 entries on the same day.
The 12 records
- Z-0122-2027: VOCSN+Pro, model PRT-00490-001, 4,369 units
- Z-0123-2027: VOCSN+Pro (Japan), model PRT-00490-100, 325 units
- Z-0124-2027: VC+Pro, model PRT-00900-001, 1,534 units
- Z-0125-2027: VC+Pro (Japan), model PRT-00900-100, 606 units
- Z-0126-2027: VOCSN, model PRT-01100-000, 1,532 units
- Z-0127-2027: VOCSN (Japan), model PRT-01100-100, 100 units
- Z-0128-2027: VCSN+Pro, model PRT-01184-000, 4,368 units
- Z-0129-2027: V+Pro, models PRT-01185-000, PRT-01185-001 and PRT-01185-002, 39,568 units
- Z-0130-2027: VC, model PRT-01098-000, 930 units
- Z-0131-2027: VC (Japan), model PRT-01098-100, 180 units
- Z-0132-2027: V+ Pro Emergency, model PRT-01201-000, 30,120 units
- Z-0133-2027: V*Home, model PRT-01444-000, 25,112 units
The records list 108,744 units in commerce. Read that as an upper bound. FDA's V+ Pro Emergency record notes units converted to V+Pro model numbers, so some units may appear in two records. Every record covers all serial numbers. All 12 list distribution across the US including Puerto Rico, and eight also list Japan and China.
The firm acted five weeks earlier
Ventec sent an urgent recall notice by certified mail on September 17, 2026. FDA issued an Early Alert on September 23. The classified records posted on October 20. A team that watches only the weekly recall feed saw this event more than a month after customers were notified.
What FDA's Early Alert adds
The recall records name the connector. The Early Alert explains it. The connector can partly or fully unseat, which cuts communication with the internal flow transducer board and causes reboots and repeated System Fault 10 alarms. Dropping the device or another substantial impact can cause it, and the alert says the issue affects all VOCSN configurations.
As of August 12, 2026, the firm reported no serious injuries or deaths. The alert reports no reboots during active ventilation and calls the probability of one remote. FDA lists the cause as under investigation by the firm.
The alert's recommended steps include keeping backup ventilation ready, setting the ventilator on a flat, stable surface or securing it, running the checkout procedure after any drop and shipping devices only in Ventec-approved packaging.
Why the count matters for RA/QA teams
A recall count measures records, not problems. Twelve records here describe one failure mode on a shared internal assembly, spread across a product family and its regional variants. Trending by record count would show 12 problems where the market faced one.
The pattern is not new for this firm. openFDA's enforcement data lists three earlier Ventec Class I recall events, started in January 2024, February 2025 and March 2026, which makes this the fourth since January 2024.
The failure mode is mechanical: a connector that loses retention under shock. Connector seating, strain relief and board-level interconnects show up across powered devices, and drop sensitivity matters most for devices that travel with patients.
What to do with this
A regulatory team should group recall records by FDA event number before trending volume, so one event filed per model counts once. Teams with portable ventilators or similar internal interconnects should check whether their complaint data would catch a drop-linked connector pattern across model variants.