Safety Incidents OSHA Severe Injury Reports · 2015–2025
2,098,129Injury reports 132,232Establishments Most recent incident 2025-12-31

St. Paul, MN —

OSHA Injury Report: Double Dragon Foods

Injury · Days away from work

At a glance

On , an injury at Double Dragon Foods in 121 Maryland Avenue West, St. Paul, MN 55117 resulted in days away from work. Employee was kitchen in grocery stores.

Watch Double Dragon Foods — free Get an email when a new federal OSHA severe-injury report for Double Dragon Foods is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Double Dragon Foods
Parent company
Double Dragon Foods
Street
121 Maryland Avenue West
City
St. Paul
State
MN
ZIP
55117
On-site location
Kitchen Department

What was the outcome?

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

Before the incident

Employee was holding a plastic bag that had breadsticks in it and used a knife to cut it open

What happened

Employee cut the bag too fast and cut her left ring finger with the kinfe

Injury or illness

Laceration to left ring finger

Object or substance involved

knife

Summary line

Laceration to left ring finger from knife

Employee and industry

Job description
Kitchen
SOC code
35-2021 — Food Preparation Workers
NAICS code
445110 — Grocery stores
NAICS vintage
2022
Avg employees
54
Total hours worked
80014
EIN
412014456
Establishment ID
502682
Employer case #
1

When (timing detail)

Date of incident
Shift started
7:29:00.000
Time of incident
8:30:00.000
Filing year
2023
Submitted
23JAN24:20:45:00

More injuries at Double Dragon Foods

View Double Dragon Foods's full OSHA safety record →

More injuries in this industry (NAICS 445110)

AMARILLO, TX—

WM 4464

ALBUQUERQUE, NM—

WM 3385

More injuries in MN

BROOKLYN PARK, MN—

WM 1864

OAK PARK HEIGHTS, MN—

WM 1861

Source

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