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

New Hyde Park, NY —

OSHA Injury Report: 2883 - Lake Success

Injury · Job transfer or restriction

At a glance

On , an injury at 2883 - Lake Success in 1400 Union Tpke, New Hyde Park, NY 110401761 resulted in job transfer or restriction. Employee was food and Beverage Expert in discount Department Stores.

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

Where did this happen?

Establishment
2883 - Lake Success
Parent company
Target
Street
1400 Union Tpke
City
New Hyde Park
State
NY
ZIP
110401761
On-site location
Freight-Guest Elevator

What was the outcome?

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

Before the incident

Trailer Unload-SortStock in Freight-Guest Elevator Unloading

What happened

Strain-Sprain - Manual Pallet Jack - Left Back - Lower Strain or Tear

Injury or illness

Strain-Sprain Back - Lower

Object or substance involved

Manual Pallet Jack

Summary line

Strain-Sprain - Manual Pallet Jack - Left Back - Lower Strain or Tear

Employee and industry

Job description
Food and Beverage Expert
SOC code
35-2021 — Food Preparation Workers
NAICS code
452112 — Discount Department Stores
NAICS vintage
2012
Avg employees
248
Total hours worked
325694
EIN
410215170
Establishment ID
1404675
Employer case #
NY2597631

When (timing detail)

Date of incident
Shift started
6:15
Time of incident
6:00
Filing year
2025
Submitted
19JAN26:20:31:00

More injuries at 2883 - Lake Success

View 2883 - Lake Success's full OSHA safety record →

More injuries in this industry (NAICS 452112)

More injuries in NY

KINGSTON, NY—

WM 6201

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2025. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.