Amusement Ride Safety and Accident Database

Columns

• acc_id: Integer. A unique identifier assigned to each accident record.
• acc_date: Datetime. The specific date when the accident occurred.
• acc_state: String. The abbreviation of the U.S. State where the incident took place (e.g., NJ, CA).
• acc_city: String. The U.S. city location of the accident.
• fix_port: String. Indicates whether the device was a fixed site machine (F) or portable (P).
• source: String. The origin of the accident information, such as state safety divisions.
• bus_type: String. The classification of the facility, such as an amusement park or water park.
• industry_sector: String. The general business sector of the device involved.
• device_category: String. Broad grouping of devices, for example, coasters or water slides.
• device_type: String. Specific type of ride or device (e.g., Coaster - steel, Go-kart).
• tradename_or_generic: String. The manufacturer's model name or the generic type of the ride.
• manufacturer: String. The company that manufactured the ride involved in the incident.
• num_injured: Integer. The total count of individuals injured in the event.
• age_youngest: Float. The age of the youngest person affected by the accident.
• gender: String. The gender of the injured party.
• acc_desc: String. A brief textual narrative describing the accident.
• injury_desc: String. A short description regarding the nature and severity of injuries sustained.
• report: String. A URL link to the official accident report, if available.
• category: String. Classification of the injury mechanism (e.g., impact, fall).
• mechanical: Boolean. Indicates if the accident was caused by a mechanical malfunction (0 or 1).
• op_error: Boolean. Indicates if the accident resulted from an operation error (0 or 1).
• employee: Boolean. Indicates if an employee error contributed to the incident (0 or 1).
• notes: String. Additional remarks or observations regarding the accident.
• year: Integer. The year extracted from the accident date for temporal analysis.

Distribution

Usage

• Safety Protocol Analysis: Identify common causes of accidents to improve safety standards in amusement parks.
• Risk Management: Assess the frequency of mechanical versus human errors to tailor training and maintenance schedules.
• Historical Trending: Analyse accident data over decades to observe improvements or declines in ride safety.
• Predictive Modelling: Use factors like device type and age of rider to predict potential high-risk scenarios.
• Regulatory Review: Assist policy makers in understanding which states or device categories require stricter oversight.

Coverage

License

Who Can Use It

• Data Analysts looking for clean datasets to practise cleaning or visualisation techniques.
• Safety Inspectors requiring historical data to benchmark current safety performance.
• Academic Researchers studying public safety, engineering failures, or leisure industry standards.
• Journalists investigating amusement park safety records and trends.

Dataset Name Suggestions

• Amusement Ride Safety and Accident Database
• Saferparks Historical Accident Records
• US Theme Park Incident Log (1986-2009)
• Roller Coaster and Ride Injury Data

Attributes