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

Long Beach, CA —

OSHA Injury Report: GB Remanufacturing, Inc.

Injury · Job transfer or restriction

At a glance

On , an injury at GB Remanufacturing, Inc. in 2040 E. Cherry Industrial Circle, Long Beach, CA 90805 resulted in job transfer or restriction. Employee was order Fulfillment Clerk in assembly line rebuilding of automotive and truck gasoline engines.

Where did this happen?

Establishment
GB Remanufacturing, Inc.
Parent company
GB Remanufacturing, Inc.
Street
2040 E. Cherry Industrial Circle
City
Long Beach
State
CA
ZIP
90805
On-site location
Electronics Department

What was the outcome?

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

Before the incident

Employee was feeling something off with her upper bicep and it became painful to lift a box.

What happened

Employee began feeling pain when she was lifting boxes.

Injury or illness

Rotator cuff tear arthropathy of right shoulder type 1 superior labral anerior-to-posterior (SLAP) tear of right shoulder.

Object or substance involved

None

Summary line

Right shoulder strain

Employee and industry

Job description
Order Fulfillment Clerk
SOC code
43-4151 — Order Clerks
NAICS code
336310 — Assembly line rebuilding of automotive and truck gasoline engines
NAICS vintage
2012
Avg employees
157
Total hours worked
345846
EIN
330208128
Establishment ID
291232
Employer case #
2

When (timing detail)

Date of incident
Shift started
7:00
Time of incident
14:00
Filing year
2024
Submitted
30JAN2025:21:11:00

More injuries at GB Remanufacturing, Inc.

View GB Remanufacturing, Inc.'s full OSHA safety record →

More injuries in this industry (NAICS 336310)

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

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.