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

Lansing, MI —

OSHA Injury Report: FPAW LLC- Lansing

Injury · Job transfer or restriction

At a glance

On , an injury at FPAW LLC- Lansing in 735 E Hazel St., Lansing, MI 48912 resulted in job transfer or restriction. Employee was cultivation Tech in hydroponic crop farming.

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

Where did this happen?

Establishment
FPAW LLC- Lansing
Parent company
FPAW LLC- Ascend Wellness Holdings LLC
Street
735 E Hazel St.
City
Lansing
State
MI
ZIP
48912
On-site location
Parking lot

What was the outcome?

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

Before the incident

The employee was walking into work.

What happened

The employee slipped on ice on the sidewalk across from our building.

Injury or illness

The employees right toe and right hamstring. The employee broke his right toe.

Object or substance involved

The concrete pavement caused his toe to break .

Summary line

slipped on ice causing an ankle fracture

Employee and industry

Job description
Cultivation Tech
SOC code
45-2092 — Farmworkers and Laborers, Crop, Nursery, and Greenhouse
NAICS code
111419 — Hydroponic crop farming
NAICS vintage
2022
Avg employees
111
Total hours worked
230880
EIN
841888779
Establishment ID
1119797
Employer case #
1

When (timing detail)

Date of incident
Shift started
7:30:00.000
Time of incident
7:15:00.000
Filing year
2023
Submitted
01MAR24:16:12:00

More injuries at FPAW LLC- Lansing

View FPAW LLC- Lansing's full OSHA safety record →

More injuries in this industry (NAICS 111419)

More injuries in MI

Source

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