2,042,423Injury reports 130,778Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

Keasbey, NJ —

OSHA Injury Report: US Beverage Packers, LLC

Injury · Days away from work

At a glance

On , an injury at US Beverage Packers, LLC in 1 Arizona Way, Keasbey, NJ 8832 resulted in days away from work. Employee was production Operator in iced tea manufacturing.

Where did this happen?

Establishment
US Beverage Packers, LLC
Parent company
US Beverage Packers, LLC
Street
1 Arizona Way
City
Keasbey
State
NJ
ZIP
8832
On-site location
Line 2 Global Shrink

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
7

Before the incident

IW was removing a heavy roll of plastic film from a machine. They needed to lower it and place it on top of a pallet on the floor.

What happened

IW 's fingertip was below the film roll when they put it down causing it to be crushed against the pallet.

Injury or illness

Crush injury causing swelling to tip of left ring finger.

Object or substance involved

Roll of plastic film approximately 60lbs.

Summary line

Swelling of tip of left ring finger due to putting down a heavy film roll on top of it.

Employee and industry

Job description
Production Operator
SOC code
51-9111 — Packaging and Filling Machine Operators and Tenders
NAICS code
312111 — Iced tea manufacturing
NAICS vintage
2022
Avg employees
354
Total hours worked
697211
EIN
611745111
Establishment ID
1066384
Employer case #
33

When (timing detail)

Date of incident
Shift started
22:30
Time of incident
3:03
Filing year
2025
Submitted
17FEB26:19:56:00

More injuries at US Beverage Packers, LLC

View US Beverage Packers, LLC's full OSHA safety record →

More injuries in this industry (NAICS 312111)

More injuries in NJ

SECAUCUS, NJ—

WM 3520

RIVERDALE, NJ—

WM 3443

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2025. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.