Houston, TX —
OSHA Injury Report: Leeland Bky
Injury · Job transfer or restriction
At a glance
On , an injury at Leeland Bky in Houston, TX 77023 resulted in job transfer or restriction. Employee was mixer Operator I in commercial Bakeries.
Where did this happen?
- Establishment
- Leeland Bky
- Parent company
- Leeland Baking Company, LLC.
- Street
- 4104 Leeland Street
- City
- Houston
- State
- TX
- ZIP
- 77023
- On-site location
- Scaling800 mixer area
What was the outcome?
- Outcome
- Job transfer or restriction (code 3)
- Type
- Injury (code 1)
- Days restricted or transferred
- 1
Before the incident
The employee was working in the scaling mixing area when he was removing a weigh up from the top of the storage rack when he felt a pain going down the left shoulder and side while lowering it to the cart to move to the mixer The employee had to ask for help from the other employee in the area to lower the container of ingredients
What happened
The employee was working in the scaling mixing area when he was removing a weigh up from the top of the storage rack when he felt a pain going down the left shoulder and side while lowering it to the cart to move to the mixer The employee had to ask for help from the other employee in the area to lower the container of ingredients
Injury or illness
Strain Elbow Left Elbow
Object or substance involved
Tote full of dry ingredients
Summary line
Strain Elbow Left Elbow Tote full of dry ingredients Repetition
Employee and industry
- Job description
- Mixer Operator I
- SOC code
- 51-3092 — Food Batchmakers
- NAICS code
- 311812 — Commercial Bakeries
- NAICS vintage
- 2022
- Avg employees
- 151
- Total hours worked
- 323411
- Establishment ID
- 1435150
- Employer case #
- 78
When (timing detail)
- Date of incident
- Shift started
- 18:00
- Time of incident
- 20:05
- Filing year
- 2025
- Submitted
- 21JAN26:16:55:00
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.