Fort Worth, TX —
OSHA Injury Report: Say Operations LLC
Injury · Job transfer or restriction
At a glance
On , an injury at Say Operations LLC in Fort Worth, TX 76116 resulted in job transfer or restriction. Employee was delivery Associate in courier services (i.e., intercity network) (except establishments operating under a universal service obligation).
Where did this happen?
- Establishment
- Say Operations LLC
- Parent company
- Say Operations LLC
- Street
- 3700 San Jacinto Dr
- City
- Fort Worth
- State
- TX
- ZIP
- 76116
- On-site location
- 4905 E County Road 60 Midland Texas 797055
What was the outcome?
- Outcome
- Job transfer or restriction (code 3)
- Type
- Injury (code 1)
- Days restricted or transferred
- 7
Before the incident
A dog jumped a gated fence and charged at the employee while she was setting a package down When the owners came out after the employee yelled another dog came out of the house and bit the back of her leg
What happened
A dog jumped a gated fence and charged at the employee while she was setting a package down When the owners came out after the employee yelled another dog came out of the house and bit the back of her leg
Injury or illness
Bite Sting insect or animal Leg Right Thigh
Object or substance involved
dog
Summary line
Bite Sting (insect or animal) Leg Right Thigh dog Bitten or stung
Employee and industry
- Job description
- Delivery Associate
- SOC code
- 43-5021 — Couriers and Messengers
- NAICS code
- 492110 — Courier services (i.e., intercity network) (except establishments operating under a universal service obligation)
- NAICS vintage
- 2022
- Avg employees
- 103
- Total hours worked
- 170519
- EIN
- 872145733
- Establishment ID
- 1472566
- Employer case #
- 18
When (timing detail)
- Date of incident
- Shift started
- 7:45
- Time of incident
- 15:40
- Filing year
- 2025
- Submitted
- 16FEB26:19:50: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.