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

PORTLAND, OR —

OSHA Injury Report: Point S Tire Portland

Injury · Days away from work

At a glance

On , an injury at Point S Tire Portland in 6102 N Marine Drive, PORTLAND, OR 97203 resulted in days away from work. Employee was driver in general warehousing and storage.

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

Where did this happen?

Establishment
Point S Tire Portland
Parent company
Tire Factory Inc
Street
6102 N Marine Drive
City
PORTLAND
State
OR
ZIP
97203
On-site location
Inside Box of Delivery truck

What was the outcome?

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

Before the incident

Unloading Tires

What happened

while trying to lift a heavy tire off the floor of cargo box felt pain in lower r side

Injury or illness

Lower Back Strain

Object or substance involved

Lifting of tires

Summary line

while trying to lift a heavy tire off the floor of cargo box felt pain in lower r side

Employee and industry

Job description
Driver
SOC code
53-3032 — Heavy and Tractor-Trailer Truck Drivers
NAICS code
493110 — General warehousing and storage
NAICS vintage
2022
Avg employees
85
Total hours worked
176800
EIN
464237082
Establishment ID
1240470
Employer case #
1

When (timing detail)

Date of incident
Shift started
8:00
Time of incident
11:00
Filing year
2024
Submitted
10FEB2025:15:48:00

More injuries at Point S Tire Portland

View Point S Tire Portland's full OSHA safety record →

More injuries in this industry (NAICS 493110)

Rancho Cucamonga, CA—

087-RCDC

MATTESON, IL—

WM 6504

COLDWATER, MI—

WM 6043

More injuries in OR

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.