Burlingame, CA —
OSHA Injury Report: Torero Logistics Corp
Injury · Job transfer or restriction
At a glance
On , an injury at Torero Logistics Corp in Burlingame, CA 94010 resulted in job transfer or restriction. Employee was delivery Associate in postal delivery services, local, operated on a contract basis.
Where did this happen?
- Establishment
- Torero Logistics Corp
- Parent company
- Torero Logistics Corp
- Street
- 533 Airport Blvd Suite 400
- City
- Burlingame
- State
- CA
- ZIP
- 94010
- On-site location
- 1891 Monterey Dr SAN BRUNO CA
What was the outcome?
- Outcome
- Job transfer or restriction (code 3)
- Type
- Injury (code 1)
- Days restricted or transferred
- 5
Before the incident
The employee stated that he was delivering a package He was looking for a long box and felt a sharp pain in the middle of his back when he lifted it He grabbed the box and as he walked to the home the pain increased He fell to the ground and could not get up
What happened
The employee stated that he was delivering a package He was looking for a long box and felt a sharp pain in the middle of his back when he lifted it He grabbed the box and as he walked to the home the pain increased He fell to the ground and could not get up
Injury or illness
Strain Back Middle Back
Object or substance involved
Large heavy box
Summary line
Strain Back Middle Back Large heavy box Lowering lifting carrying
Employee and industry
- Job description
- Delivery Associate
- SOC code
- 43-5052 — Postal Service Mail Carriers
- NAICS code
- 491110 — Postal delivery services, local, operated on a contract basis
- NAICS vintage
- 2012
- Avg employees
- 57
- Total hours worked
- 118381
- EIN
- 851890612
- Establishment ID
- 999334
- Employer case #
- 153
When (timing detail)
- Date of incident
- Shift started
- 9:30
- Time of incident
- 11:00
- Filing year
- 2025
- Submitted
- 23FEB26:22:26: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.