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

Ashburn, VA —

OSHA Injury Report: Loudoun Water

Injury · Days away from work

At a glance

On , an injury at Loudoun Water in 44865 Loudoun Water Way, Ashburn, VA 20147 resulted in days away from work. Employee was assistant Supervisor in water treatment and distribution.

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

Where did this happen?

Establishment
Loudoun Water
Parent company
Loudoun Water
Street
44865 Loudoun Water Way
City
Ashburn
State
VA
ZIP
20147
On-site location
Outside at BRWRF Plant

What was the outcome?

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

Before the incident

Driving to building on plant site.

What happened

Employee was pulling hoses apart and felt muscle pull strain in neck shoulder.

Injury or illness

Strained neck back soft tissue injury.

Object or substance involved

Pulling hoses apart that were stuck together.

Summary line

Neck Shoulder

Employee and industry

Job description
Assistant Supervisor
SOC code
51-1011 — First-Line Supervisors of Production and Operating Workers
NAICS code
221310 — Water treatment and distribution
NAICS vintage
2012
Avg employees
374
Total hours worked
620319
EIN
540716770
Establishment ID
938388
Employer case #
1

When (timing detail)

Date of incident
Shift started
6:30
Time of incident
6:35
Filing year
2025
Submitted
02MAR26:19:29:00

More injuries at Loudoun Water

View Loudoun Water's full OSHA safety record →

More injuries in this industry (NAICS 221310)

More injuries in VA

DANVILLE, VA—

WM 4996

COVINGTON, VA—

WM 2662

MADISON HEIGHTS, VA—

WM 2565

FREDERICKSBURG, VA—

WM 1833

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.