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

BALTIMORE, MD —

OSHA Injury Report: LOG BALTIMORE_1558112

Injury · Days away from work

At a glance

On , an injury at LOG BALTIMORE_1558112 in 900 E FAYETTE ST RM 505, BALTIMORE, MD 21233 resulted in days away from work. Employee was mOTOR VEHICLE in mail and Parcel Delivery.

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

Where did this happen?

Establishment
LOG BALTIMORE_1558112
Parent company
US Postal Service
Street
900 E FAYETTE ST RM 505
City
BALTIMORE
State
MD
ZIP
21233
On-site location
Highway

What was the outcome?

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

Before the incident

Driving

What happened

PVS driver was driving to his station and hit a bump in the road. He felt a pain in his lower back. When he exited the tractor the pain became more intense.

Injury or illness

Back including spine and dorsal vertebrae-Center- Sprain Strain Twist

Object or substance involved

Driving

Summary line

Sciatic nerve damage

Employee and industry

Job description
MOTOR VEHICLE
SOC code
9999 — Uncoded
NAICS code
491110 — Mail and Parcel Delivery
NAICS vintage
2022
Avg employees
102
Total hours worked
169573
EIN
417600000
Establishment ID
1212737
Employer case #
353753

When (timing detail)

Date of incident
Shift started
23:00
Time of incident
18:00
Filing year
2024
Submitted
10FEB2025:19:18:00

More injuries at LOG BALTIMORE_1558112

View LOG BALTIMORE_1558112's full OSHA safety record →

More injuries in this industry (NAICS 491110)

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 2024. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.