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

Lanham, MD —

OSHA Injury Report: Baldor Specialty Food - DC

Injury · Job transfer or restriction

At a glance

On , an injury at Baldor Specialty Food - DC in 4450 Hargrove Drive, Lanham, MD 20706 resulted in job transfer or restriction. Employee was warehouse Associate in private warehousing and storage, refrigerated.

Where did this happen?

Establishment
Baldor Specialty Food - DC
Parent company
Baldor Specialty Food
Street
4450 Hargrove Drive
City
Lanham
State
MD
ZIP
20706
On-site location
Location 409129B03

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
13

Before the incident

Employee was selecting an order and attempted to l

What happened

Employee was selecting an order and attempted to l

Injury or illness

Employee was selecting an order and attempted to l

Object or substance involved

Employee was selecting an order and attempted to l

Summary line

Employee was selecting an order and attempted to l

Employee and industry

Job description
Warehouse Associate
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
493120 — Private warehousing and storage, refrigerated
NAICS vintage
2022
Avg employees
147
Total hours worked
304720
Establishment ID
1316086
Employer case #
202500069

When (timing detail)

Date of incident
Shift started
1:15
Time of incident
1:15
Filing year
2025
Submitted
04MAR26:18:10:00

More injuries at Baldor Specialty Food - DC

View Baldor Specialty Food - DC's full OSHA safety record →

More injuries in this industry (NAICS 493120)

POTTSVILLE, PA—

WM 7030

GAS CITY, IN—

WM 7055

More injuries in MD

COLUMBIA, MD—

WM 5228

RANDALLSTOWN, MD—

WM 3804

CATONSVILLE, MD—

WM 2248

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.