Raw chicken in a ready-to-eat sandwich (H-1149-2026) — only 26 of 1,408 records are marked as finished
A sandwich meant to be eaten as it comes was recalled after raw breaded chicken patties were used in it by mistake. Its status is one of the few marked as terminated: among the records held here, 98.2% remain on ongoing.
Recall overview (primary data)
- ClassificationClass I (most serious)
- Product typeFood
- Recalling firmFresh & Ready Foods LLC
- ReasonRaw breaded chicken patties were inadvertently used in the ready to eat Burger Chicken Fillet sandwich. Raw breaded chicken patties pose a risk of foodborne illness due to the potential presence of Salmonella.
- DistributionDistributed in OR and WA.
- Recall initiated2026-06-25
Key points
- Raw breaded chicken patties were inadvertently used in a sandwich built to be eaten without cooking.
- Distribution covers Oregon and Washington, the quantity is 377 units, and sale was to employees in workplace breakrooms rather than retail.
- The status is terminated. Of the 1,408 records this site holds as of 2026-09-04, only 26 show a finished recall: 15 terminated and 11 completed.
- The remaining 1,382 (98.2%) are ongoing; not one of 288 drug records is finished and only one of 779 device records is completed.
- Ongoing does not necessarily mean continuing danger, and nothing in the record separates that from a status never updated.
1The premise of eating it as it comes
A sandwich is built to be eaten without cooking. What the stated reason records is that a product built on that premise had raw breaded chicken patties used in it by mistake. Raw chicken can carry Salmonella, which is why it is normally cooked through before eating. Put it into a product that assumes no cooking, and that step simply disappears.
Distribution covers two states, Oregon and Washington, the quantity is 377 units, and the record notes sale not through retail but to employees in certain workplace breakrooms.
2Records mark beginnings, rarely endings
Records showing that a recall has finished number 26 in total. Everything else remains ongoing. Break it down further and every finished record belongs to food. Not one of the 288 drug records is finished, and among 779 device records exactly one is marked completed. The sensible reading is not that drug and device recalls never end, but that their ending is rarely reflected here.
3What separates completed from terminated
The two mark different stages. A firm finishing its work and an authority finishing its oversight happen separately. Within the records held here, though, both are rare enough that reading the status field to learn whether something is now safe is, in practice, not available.
4How to read a record that has not finished
Ongoing does not necessarily mean the danger continues. It can mean the recall work is genuinely still running, or it can mean the status was never updated. Nothing in the record distinguishes the two. So the status field is safe to use in one direction only: if it says finished, it finished. From the absence of that mark, neither continuation nor completion can be concluded.
Why it matters
The status field can be read in one direction: a mark of finished means finished, while its absence supports no conclusion at all. Within these records 98.2% remain ongoing and not one drug recall is finished. With nothing in the record to separate continuing work from an un-updated status, one-directional use is the only safe use.
FAQ
What separates terminated from completed?
Does ongoing mean it is still dangerous?
Why are so few records finished?
Sources (primary)
Source: openFDA (U.S. FDA, CC0 public domain). Data is provided as-is and must not be used for medical decisions. Verify the latest and exact details with the official FDA recall information. This site is not endorsed or certified by the U.S. FDA.
- FDA recall information (official)
- openFDA (data provider)
- Recall number: H-1149-2026