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

Mesa, AZ —

OSHA Injury Report: Banner Rehabilitation East

Injury · Days away from work

At a glance

On , an injury at Banner Rehabilitation East in 1702 S Pierpont Drive, Mesa, AZ 85206 resulted in days away from work. Employee was patient Care Technician in specialty Hospitals.

Where did this happen?

Establishment
Banner Rehabilitation East
Parent company
Select Medical
Street
1702 S Pierpont Drive
City
Mesa
State
AZ
ZIP
85206
On-site location
Room 1129

What was the outcome?

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

Before the incident

Setting up automated wheelchair to get into position to transfer patient

What happened

PCT and RN transferred patient to the toilet at the beginning of shift for pt to self cath. Patient was graded a mod x 2 with slideboard or max x 1 spt. During the second transfer in the morning at [REDACTED] is when I believe the injury occurred as my back was

Injury or illness

Strain or Tear - Right - Lower Back

Object or substance involved

Patient handling

Summary line

Patient Handling - Right - Lower Back - Patient handling

Employee and industry

Job description
Patient Care Technician
SOC code
31-1131 — Nursing Assistants
NAICS code
622310 — Specialty Hospitals
NAICS vintage
2022
Avg employees
265
Total hours worked
373788
EIN
823481322
Establishment ID
1310300
Employer case #
24-083792

When (timing detail)

Date of incident
Shift started
18:00
Time of incident
4:30
Filing year
2024
Submitted
16FEB2025:21:37:00

More injuries at Banner Rehabilitation East

View Banner Rehabilitation East's full OSHA safety record →

More injuries in this industry (NAICS 622310)

More injuries in AZ

SHOW LOW, AZ—

WM 1230

PRESCOTT VALLEY, AZ—

WM 3730

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.