2,098,129Injury reports 132,232Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

Ephrata, PA —

OSHA Injury Report: GSM Roofing (Total Company)

Injury · Other recordable case

At a glance

On , an injury at GSM Roofing (Total Company) in 345 South Reading Rd, Ephrata, PA 17522 resulted in other recordable case. Employee was roofer in roofing contractors.

Watch GSM Roofing (Total Company) — free Get an email when a new federal OSHA severe-injury report for GSM Roofing (Total Company) is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
GSM Roofing (Total Company)
Parent company
GSM Roofing
Street
345 South Reading Rd
City
Ephrata
State
PA
ZIP
17522
On-site location
Rooftop

What was the outcome?

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

Before the incident

Opening a tube of caulk with a pocket knife.

What happened

He was cutting towards his thumb and the knife blade cut through the tip of the tube and into his finger.

Injury or illness

Laceration to thumb requiring stitches.

Object or substance involved

Pocket knife.

Summary line

Laceration to right thumb while using a pocket knife to open tube of caulk.

Employee and industry

Job description
Roofer
SOC code
47-2181 — Roofers
NAICS code
238160 — Roofing contractors
NAICS vintage
2012
Avg employees
101
Total hours worked
195578
EIN
232553249
Establishment ID
928320
Employer case #
1

When (timing detail)

Date of incident
Shift started
6:00
Time of incident
15:40
Filing year
2024
Submitted
27JAN2025:19:51:00

More injuries at GSM Roofing (Total Company)

View GSM Roofing (Total Company)'s full OSHA safety record →

More injuries in this industry (NAICS 238160)

More injuries in PA

POTTSVILLE, PA—

WM 7030

CONNELLSVILLE, PA—

WM 5379

DUNCANSVILLE, PA—

WM 4348

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.