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

Perrysburg, OH —

OSHA Injury Report: R & J Trucking Toledo Terminal

Injury · Job transfer or restriction

At a glance

On , an injury at R & J Trucking Toledo Terminal in 3480 Genoa Road, Perrysburg, OH 43551 resulted in job transfer or restriction. Employee was mechanic in general freight trucking, local.

Where did this happen?

Establishment
R & J Trucking Toledo Terminal
Parent company
R & J Trucking, Inc.
Street
3480 Genoa Road
City
Perrysburg
State
OH
ZIP
43551
On-site location
R & J Trucking Toledo Terminal shop

What was the outcome?

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

Before the incident

Working on a roll off [REDACTED].

What happened

He was using a grinder to cut off the D ring of a roll off cable when the blade caught something causing it to jump. He lacerated his right forearm because the grinder turned in his hand when it kicked back.

Injury or illness

right forearm laceration from a grinder

Object or substance involved

Grinder

Summary line

laceration of right forearm from grinder.

Employee and industry

Job description
Mechanic
SOC code
49-3031 — Bus and Truck Mechanics and Diesel Engine Specialists
NAICS code
484110 — General freight trucking, local
NAICS vintage
2022
Avg employees
20
Total hours worked
67669
EIN
431336167
Establishment ID
998322
Employer case #
13

When (timing detail)

Date of incident
Shift started
7:00:00.000
Time of incident
13:00:00.000
Submitted
30JAN24:18:01:00

More injuries at R & J Trucking Toledo Terminal

View R & J Trucking Toledo Terminal's full OSHA safety record →

More injuries in this industry (NAICS 484110)

More injuries in OH

LEWIS CENTER, OH—

WM 2725

EASTLAKE, OH—

WM 1863

Source

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