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

Queensbury, NY —

OSHA Injury Report: Great Escape Theme Park, LP

Injury · Other recordable case

At a glance

On , an injury at Great Escape Theme Park, LP in 1172 State Route 9, Queensbury, NY 12804 resulted in other recordable case. Employee was maintenance Landscape in amusement parks (e.g., theme, water).

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

Where did this happen?

Establishment
Great Escape Theme Park, LP
Street
1172 State Route 9
City
Queensbury
State
NY
ZIP
12804
On-site location
Carousel Plaza Midway

What was the outcome?

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

Before the incident

Cutting hedges with a hedge trimmer

What happened

Timming hedges and left hand holding the trimmer slipped past the guard

Injury or illness

Laceration to left index finger while using a hedge trimmer and his hand slipping past the guard

Object or substance involved

Hedge Trimmer

Summary line

Left index finger Laceration

Employee and industry

Job description
Maintenance Landscape
SOC code
37-3011 — Landscaping and Groundskeeping Workers
NAICS code
713110 — Amusement parks (e.g., theme, water)
NAICS vintage
2022
Avg employees
283
Total hours worked
340364
EIN
133943322
Establishment ID
1291167
Employer case #
25-030096

When (timing detail)

Date of incident
Shift started
6:58
Time of incident
13:55
Filing year
2025
Submitted
28JAN26:15:06:00

More injuries at Great Escape Theme Park, LP

View Great Escape Theme Park, LP's full OSHA safety record →

More injuries in this industry (NAICS 713110)

More injuries in NY

KINGSTON, NY—

WM 6201

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.