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

Silver Spring, MD —

OSHA Injury Report: Berkel Shoring Washington DC

Injury · Days away from work

At a glance

On , an injury at Berkel Shoring Washington DC in 2431 Linden Lane, Silver Spring, MD 20910 resulted in days away from work. Employee was laborer in foundation, building, poured concrete, contractors.

Watch Berkel Shoring Washington DC — free Get an email when a new federal OSHA severe-injury report for Berkel Shoring Washington DC is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Berkel Shoring Washington DC
Parent company
Berkel & Company Contractors, Inc.
Street
2431 Linden Lane
City
Silver Spring
State
MD
ZIP
20910
On-site location
job site

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
118
Days restricted or transferred
137

Before the incident

installing lagging boards

What happened

EE reported his L side of his back was hurting.

Injury or illness

back sprain

Object or substance involved

handling lagging boards

Summary line

Back sprain

Employee and industry

Job description
Laborer
SOC code
47-2061 — Construction Laborers
NAICS code
238110 — Foundation, building, poured concrete, contractors
NAICS vintage
2012
Avg employees
174
Total hours worked
351452
EIN
480650969
Establishment ID
951493
Employer case #
1

When (timing detail)

Date of incident
Shift started
8:00
Time of incident
8:30
Filing year
2024
Submitted
31JAN2025:17:34:00

More injuries at Berkel Shoring Washington DC

View Berkel Shoring Washington DC's full OSHA safety record →

More injuries in this industry (NAICS 238110)

More injuries in MD

COLUMBIA, MD—

WM 5228

RANDALLSTOWN, MD—

WM 3804

CATONSVILLE, MD—

WM 2248

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.