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

Timonium, MD —

OSHA Injury Report: Shop Rite of Timonium

Injury · Days away from work

At a glance

On , an injury at Shop Rite of Timonium in 37 W. Aylesbury Road, Timonium, MD 21093 resulted in days away from work. Employee was appy Manager in grocery stores.

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

Where did this happen?

Establishment
Shop Rite of Timonium
Parent company
Village Super Market, Inc.
Street
37 W. Aylesbury Road
City
Timonium
State
MD
ZIP
21093
On-site location
Appy Department

What was the outcome?

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

Before the incident

The employee was slicing cheese on the appy slicer

What happened

The employee lacerated her right pinkie finger on the lsicer

Injury or illness

Lacerated right pinkie finger (sutures)

Object or substance involved

Appy Slicer

Summary line

Lacerated right pinkie finger

Employee and industry

Job description
Appy Manager
SOC code
41-1011 — First-Line Supervisors of Retail Sales Workers
NAICS code
445110 — Grocery stores
NAICS vintage
2012
Avg employees
106
Total hours worked
177149
EIN
452425228
Establishment ID
341823
Employer case #
1

When (timing detail)

Date of incident
Shift started
8:00
Time of incident
10:45
Filing year
2025
Submitted
17FEB26:13:43:00

More injuries at Shop Rite of Timonium

View Shop Rite of Timonium's full OSHA safety record →

More injuries in this industry (NAICS 445110)

AMARILLO, TX—

WM 4464

ALBUQUERQUE, NM—

WM 3385

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.