FDA Records Class II Recall of 212 Photera 600 3-D Phototherapy Units
An FDA enforcement report dated 22 July 2026 lists a nationwide recall by Daavlin Distributing Company over an incorrect UV sensor gain setting affecting calibrated output.
Was this report accurate and useful?
Sources
- https://api.fda.gov/food/enforcement.json?search=recall_number:%22Z-2744-2026%22
- https://www.fda.gov/safety/industry-guidance-recalls/recalls-background-and-definitions
- https://support.phothera.com/support/solutions/articles/158000403004-phothera-600
- https://www.phothera.com/product/phothera-600-3d/
- https://www.phothera.com/product/phothera-600-lt/
- https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/9162078
Revision history
- Version 67 Aug 2026, 13:17current
Re-verified against the FDA enforcement record; no change to the facts, added full source links for the enforcement report, classification definition and manufacturer product pages.
- Version 57 Aug 2026, 12:26
Replaced the regulatory-code device description with the manufacturer's own product and support descriptions of the Phothera 600-3D, and cited those pages.
- Version 47 Aug 2026, 08:22
Added a paragraph explaining what the device is and how it is supplied, sourced to eCFR and FDA 510(k) records.
- Version 37 Aug 2026, 02:53
Removed the two paragraphs of product-category background not drawn from the enforcement record; added a note that the record does not state corrective actions.
- Version 26 Aug 2026, 23:17
Corrected the product description to the enclosure-style unit documented in the reference sources, added who holds the devices and how they are supplied, and added the supporting source URLs.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.