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

Princeton, MN —

OSHA Injury Report: Crystal Cabinet Works, Inc.

Injury · Days away from work

At a glance

On , an injury at Crystal Cabinet Works, Inc. in 1100 Crystal Drive, Princeton, MN 55371 resulted in days away from work. Employee was customs Set Up Technician in kitchen cabinets (except freestanding), stock or custom wood, manufacturing.

Where did this happen?

Establishment
Crystal Cabinet Works, Inc.
Parent company
Crystal Cabinet Works, Inc.
Street
1100 Crystal Drive
City
Princeton
State
MN
ZIP
55371
On-site location
Custom Cabinets

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
5
Days restricted or transferred
3

Before the incident

Employee was a 2x2 panel on a cart setting up for the builders

What happened

Employee bent over to pick a pen that dropped onto the floor

Injury or illness

Back pain in middle back area

Object or substance involved

Hand Tools Non Powered

Summary line

pain middle back from bending over to pick up a pen

Employee and industry

Job description
Customs Set Up Technician
SOC code
51-9061 — Inspectors, Testers, Sorters, Samplers, and Weighers
NAICS code
337110 — Kitchen cabinets (except freestanding), stock or custom wood, manufacturing
NAICS vintage
2022
Avg employees
522
Total hours worked
1037298
EIN
410828559
Establishment ID
1108288
Employer case #
338037

When (timing detail)

Date of incident
Shift started
6:00
Time of incident
8:00
Filing year
2025
Submitted
11FEB26:18:12:00

More injuries at Crystal Cabinet Works, Inc.

View Crystal Cabinet Works, Inc.'s full OSHA safety record →

More injuries in this industry (NAICS 337110)

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 2025. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.