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

Boston, MA —

OSHA Injury Report: 600 Turnpike Yard Location Easton M

Injury · Days away from work

At a glance

On , an injury at 600 Turnpike Yard Location Easton M in 361 Newbury ST Floor 5, Boston, MA 02115 resulted in days away from work. Employee was driver in general freight trucking, local.

Watch 600 Turnpike Yard Location Easton M — free Get an email when a new federal OSHA severe-injury report for 600 Turnpike Yard Location Easton M is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
600 Turnpike Yard Location Easton M
Parent company
Atlantic Freight LLC
Street
361 Newbury ST Floor 5
City
Boston
State
MA
ZIP
02115
On-site location
during his shift

What was the outcome?

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

Before the incident

said his shoulder started hurting during the day

What happened

driver said shoulder started to hurt during his shift while hooking and unhooking trailers

Injury or illness

shoulder injury

Object or substance involved

nothing

Summary line

said his shoulder started to hurt during his shift

Employee and industry

Job description
driver
SOC code
53-3032 — Heavy and Tractor-Trailer Truck Drivers
NAICS code
484110 — General freight trucking, local
NAICS vintage
2022
Avg employees
38
Total hours worked
50700
EIN
863864267
Establishment ID
949551
Employer case #
2

When (timing detail)

Date of incident
Shift started
2:30:00.000
Filing year
2023
Submitted
22FEB24:02:26:00

More injuries at 600 Turnpike Yard Location Easton M

View 600 Turnpike Yard Location Easton M'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 2023. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.