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

Provo, UT —

OSHA Injury Report: Ambia Energy, LLC

Injury · Days away from work

At a glance

On , an injury at Ambia Energy, LLC in 5132 N 300 W Ste 200, Provo, UT 84604 resulted in days away from work. Employee was field Operations Manager.

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

Where did this happen?

Establishment
Ambia Energy, LLC
Parent company
Ambia Energy, LLC
Street
5132 N 300 W Ste 200
City
Provo
State
UT
ZIP
84604
On-site location
559 Straube Avew Baden, PA 15005

What was the outcome?

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

Before the incident

He was inside the customers home trying to connect WIFI to the Solar Inverter

What happened

He Rolled his ankle on last step of outside stairs and went head first down a flight of stairs. He didn 't remember any hand rails to grab a hold of

Injury or illness

Ankle

Object or substance involved

Walking down the stairs

Summary line

He Rolled his ankle on last step of outside stairs and went head first down a flight of stairs. He didn 't remember any hand rails to grab a hold of

Employee and industry

Job description
Field Operations Manager
SOC code
9999 — Uncoded
NAICS code
238210
NAICS vintage
2022
Avg employees
174
Total hours worked
212994
EIN
863160318
Establishment ID
1181076
Employer case #
5

When (timing detail)

Date of incident
Shift started
7:00
Time of incident
0:00
Filing year
2024
Submitted
04MAR2025:21:51:00

More injuries at Ambia Energy, LLC

View Ambia Energy, LLC's full OSHA safety record →

More injuries in this industry (NAICS 238210)

More injuries in UT

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.