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

Long Beach, CA —

OSHA Injury Report: Long Beach Container Terminal LLC

Injury · Days away from work

At a glance

On , an injury at Long Beach Container Terminal LLC in 1171 Pier F Ave, Long Beach, CA 90802 resulted in days away from work. Employee was lasher in loading and unloading services at ports and harbors.

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

Where did this happen?

Establishment
Long Beach Container Terminal LLC
Parent company
Long Beach Container Terminal LLC
Street
1171 Pier F Ave
City
Long Beach
State
CA
ZIP
90802
On-site location
Afloat, Deck, Container Operation

What was the outcome?

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

Before the incident

unlashing

What happened

Alleged sprain strain spasm in back

Injury or illness

sprain strain spasm in back

Object or substance involved

Lashing poles

Summary line

sprain strain spasm back

Employee and industry

Job description
Lasher
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
488320 — Loading and unloading services at ports and harbors
NAICS vintage
2022
Avg employees
1091
Total hours worked
1590612
EIN
454649289
Establishment ID
1083528
Employer case #
135549

When (timing detail)

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

More injuries at Long Beach Container Terminal LLC

View Long Beach Container Terminal LLC's full OSHA safety record →

More injuries in this industry (NAICS 488320)

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.