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

LONDONDERRY, NH —

OSHA Injury Report: FedEx ZMAN G MANCHESTER 31

Injury · Days away from work

At a glance

On , an injury at FedEx ZMAN G MANCHESTER 31 in 44 INDUSTRIAL DRIVE, LONDONDERRY, NH 3053 resulted in days away from work. Employee was package Handler in courier and Express Delivery Services.

Where did this happen?

Establishment
FedEx ZMAN G MANCHESTER 31
Parent company
FEDERAL EXPRESS CORPORATION
Street
44 INDUSTRIAL DRIVE
City
LONDONDERRY
State
NH
ZIP
3053
On-site location
VAN PRE UNLOAD

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
2

Before the incident

CARRYING PACKAGE DOWNSTAIRS

What happened

Employee was carrying a package down a 3 step set of stairs on end of van line and felt a pop snap like sensation in their right hip

Injury or illness

Sprained Right Hip Fall on same level Stairs

Object or substance involved

Stairs

Summary line

Employee was carrying a package down a 3 step set of stairs on end of van line and felt a pop snap like sensation in their right hip

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
385
Total hours worked
247759
EIN
710427007
Establishment ID
1367483
Employer case #
265668

When (timing detail)

Date of incident
Shift started
1:00
Time of incident
3:45
Filing year
2024
Submitted
28FEB2025:01:23:00

More injuries at FedEx ZMAN G MANCHESTER 31

View FedEx ZMAN G MANCHESTER 31's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in NH

CLAREMONT, NH—

WM 1975

MANCHESTER, NH—

XNH

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.