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

Beverly Hills, CA —

OSHA Injury Report: 10022 Beverly Hills

Injury · Other recordable case

At a glance

On , an injury at 10022 Beverly Hills in 239 North Crescent Drive, Beverly Hills, CA 90210 resulted in other recordable case. Employee was s CashierCustomer Service TM.

Where did this happen?

Establishment
10022 Beverly Hills
Street
239 North Crescent Drive
City
Beverly Hills
State
CA
ZIP
90210
On-site location
Offsite

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

Driving back to work from community event.

What happened

Team member was driving back to work from a community event when his vehicle was struck from behind by another vehicle. TM 's vehicle then struck the vehicle in from of his. Tm felt pain in neck following the incident.

Injury or illness

Strain Sprain Multiple Injuries

Object or substance involved

Vehicle

Summary line

Team member was driving back to work from a community event when his vehicle was struck from behind by another vehicle. TM 's vehicle then struck the vehicle in from of his. Tm felt pain in neck following the incident.

Employee and industry

Job description
S CashierCustomer Service TM
SOC code
9999 — Uncoded
NAICS code
445110
NAICS vintage
2012
Avg employees
122
Total hours worked
197438
EIN
953096433
Establishment ID
715708
Employer case #
0005772265

When (timing detail)

Date of incident
Shift started
10:00
Time of incident
14:30
Filing year
2024
Submitted
28FEB2025:19:00:00

More injuries at 10022 Beverly Hills

View 10022 Beverly Hills's full OSHA safety record →

More injuries in this industry (NAICS 445110)

AMARILLO, TX—

WM 4464

ALBUQUERQUE, NM—

WM 3385

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.