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

BRYAN, TX —

OSHA Injury Report: FedEx ZBRY G BRYAN 778

Injury · Other recordable case

At a glance

On , an injury at FedEx ZBRY G BRYAN 778 in 8011 N STATE HIGHWAY 6, BRYAN, TX 77807 resulted in other recordable case. Employee was package Handler in courier and Express Delivery Services.

Where did this happen?

Establishment
FedEx ZBRY G BRYAN 778
Parent company
FEDERAL EXPRESS CORPORATION
Street
8011 N STATE HIGHWAY 6
City
BRYAN
State
TX
ZIP
77807
On-site location
VANLINE CATWALK

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

UNLOADING BELT

What happened

Employee was taking package off of the belt and walked backward off the catwalk hitting her left knee and left leg

Injury or illness

Bruised Left Lower leg Fall on same level Pit Catwalk

Object or substance involved

Pit Catwalk

Summary line

Employee was taking package off of the belt and walked backward off the catwalk hitting her left knee and left leg

Employee and industry

Job description
Package Handler
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
492110 — Courier and Express Delivery Services
NAICS vintage
2022
Avg employees
169
Total hours worked
111062
EIN
710427007
Establishment ID
1367194
Employer case #
142834

When (timing detail)

Date of incident
Shift started
4:15
Time of incident
6:00
Filing year
2024
Submitted
28FEB2025:01:22:00

More injuries at FedEx ZBRY G BRYAN 778

View FedEx ZBRY G BRYAN 778's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in TX

AMARILLO, TX—

WM 4464

VICTORIA, TX—

WM 4194

FORT WORTH, TX—

WM 3005

ARLINGTON, TX—

WM 2977

SAN ANTONIO, TX—

WM 1803

Source

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