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

Bellingham, MA —

OSHA Injury Report: Gruntastic Logistics Corp

Injury · Other recordable case

At a glance

On , an injury at Gruntastic Logistics Corp in 351 Maple Street, Bellingham, MA 2018 resulted in other recordable case. Employee was delivery Driver in trucking, general freight, local.

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

Where did this happen?

Establishment
Gruntastic Logistics Corp
Parent company
Gruntastic Logistics Corp
Street
351 Maple Street
City
Bellingham
State
MA
ZIP
2018
On-site location
Road

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

Getting into the van

What happened

EE was getting back into their truck while holding an amazon bag after delivering a package when EE missed the first step to the truck causing [REDACTED] left shin to hit the second step resulting in a scrape scratch on EE 's left shin.

Injury or illness

Shin scrape

Object or substance involved

Side step

Summary line

Scraped [REDACTED]

Employee and industry

Job description
Delivery Driver
SOC code
53-3033 — Light Truck Drivers
NAICS code
484110 — Trucking, general freight, local
NAICS vintage
2012
Avg employees
98
Total hours worked
183456
EIN
850828962
Establishment ID
994443
Employer case #
WCAEG0320

When (timing detail)

Date of incident
Shift started
9:45
Time of incident
13:30
Filing year
2025
Submitted
10FEB26:15:36:00

More injuries at Gruntastic Logistics Corp

View Gruntastic Logistics Corp's full OSHA safety record →

More injuries in this industry (NAICS 484110)

More injuries in MA

Uxbridge, MA—

C40

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.