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

Lincoln, NE —

OSHA Injury Report: Lincoln Terminal

Injury · Days away from work

At a glance

On , an injury at Lincoln Terminal in 400 NW 56th St., Lincoln, NE 68528 resulted in days away from work. Employee was driver in general Automotive Repair and Office Duties.

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

Where did this happen?

Establishment
Lincoln Terminal
Parent company
CRETE CARRIER CORPORATION
Street
400 NW 56th St.
City
Lincoln
State
NE
ZIP
68528
On-site location
ROADWAY

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
77
Days restricted or transferred
34

Before the incident

DRIVING

What happened

DRIVER HAD PAIN DUE TO MISSING SEAT SPRING THAT WAS CAUSING PRESSURE TO BACK

Injury or illness

Inflammation - Strain Injury by Misc - Other - Low Back Area

Object or substance involved

SEAT

Summary line

SPRING MISSING FROM SEAT CAUSING ADDED PRESSURE STRESS TO BACK

Employee and industry

Job description
Driver
SOC code
53-3032 — Heavy and Tractor-Trailer Truck Drivers
NAICS code
484121 — General Automotive Repair and Office Duties
NAICS vintage
2022
Avg employees
616
Total hours worked
1127399
EIN
470496288
Establishment ID
1146674
Employer case #
2023342534

When (timing detail)

Date of incident
Shift started
4:00:00.000
Time of incident
6:00:00.000
Filing year
2023
Submitted
21FEB24:21:42:00

More injuries at Lincoln Terminal

View Lincoln Terminal's full OSHA safety record →

More injuries in this industry (NAICS 484121)

More injuries in NE

BELLEVUE, NE—

WM 3154

FREMONT, NE—

WM 776

Scottsbluff, NE—

RWMC

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2023. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.