2016-2017 Passenger Tramway Safety Board

PASSENGER TRAMWAY INCIDENTS Pursuant to Rule 23.2 of the Colorado Passenger Tramway Safety Board’s Rules and Regulations, during the operating season, all “passenger tramway incidents” must be verbally reported to the Board, as soon as reasonably possible, but no later that twenty-four (24) hours after the time of such an incident. A written report must be mailed or faxed to the Board, on forms approved by the Board, within five (5) days of such incident.

Name of Staff Member to whom this incident was orally reported:

____________

Date and Time Incident was orally reported:

Please supply the following information: (Use separate sheet if additional space is required)

______

A. Name of Area: B. Name of Tramway:

Lift ID Number ____________

C. Date of incident: D. Failure Code(s) (required - CPTSB Form 141-03): Description:

E. Cause Code(s) (required - see CPTSB Form 141-03): Description:

F. Action taken as a result of this incident, if any:

G. Length of time the tramway was down:

CPTSB Form 139-16

Page 1

2016-2017 Passenger Tramway Safety Board

PASSENGER TRAMWAY INCIDENTS H. Names, addresses and statements of witnesses, if any:

I. Nature and extent of injuries that may have been suffered, including names and addresses of injured:

J. Designate how tramway was stopped: K. Evacuation (yes or no):

If yes, Rope or Evac. Power Unit (R or EPU):

Note: (Evacuation by Rope or Evac. Power Unit - NOT by Diesel Prime Mover) L. Number of affected persons and total time for evacuation (from time tramway first stopped to the end of evacuation): M. Name, title and signature of person reporting: N. Signature of Designated Agent: ____________________________________________________________________________

Submit this form via mail, fax, or email to: Colorado Passenger Tramway Safety Board 1560 Broadway, Suite 1350 Denver, Colorado 80202 FAX: 303-869-0235 EMAIL: [email protected] Telephone numbers are listed herein to aid in compliance with Rule 23.2

CPTSB OFFICE (303) 894-7785 Larry Smith Joyce Young

CPTSB Form 139-16

Office:

Cell:

Location:

(303) 894-7786 (303) 894-7781

(303) 929-3494 (720) 331-8985

Arvada Denver

Page 2

2016-2017 Incident Report Form (CPTSB Form 139-16).pdf ...

CPTSB OFFICE (303) 894-7785. Office: Cell: Location: Larry Smith (303) 894-7786 (303) 929-3494 Arvada. Joyce Young (303) 894-7781 (720) 331-8985 Denver. 2016-2017. Passenger Tramway Safety Board. PASSENGER TRAMWAY. INCIDENTS. Page 2 of 2. 2016-2017 Incident Report Form (CPTSB Form 139-16).pdf.

69KB Sizes 0 Downloads 186 Views

Recommend Documents

2016-2017 Incident Report Form (CPTSB Form 139-16).pdf ...
Whoops! There was a problem loading more pages. 2016-2017 Incident Report Form (CPTSB Form 139-16).pdf. 2016-2017 Incident Report Form (CPTSB Form ...

Automated External Defibrillators – Incident Report Form 8310F3.pdf ...
Automated External Defibrillators – Incident Report Form 8310F3.pdf. Automated External Defibrillators – Incident Report Form 8310F3.pdf. Open. Extract.

RMU Incident Investigation and Report Form
Unsafe Acts. Unsafe Conditions. Management Deficiencies. Improper work technique. Poor workstation design or layout. Lack of written procedures or policies. Safety rule violation. Congested work area. Safety rules not enforced. Improper PPE or PPE no

MSVL HIB Incident Reporting Form 031814.pdf
Page 1 of 2. Marysville School District Harassment, Intimidation or Bullying (HIB). Incident Reporting Form. School: Today's Date: Check One: Non-Confidential Report Confidential Report Anonymous Report. Reporting person – If different than Targete

Google Apps Incident Report
Mar 17, 2014 - Issue Summary. From 8:35 AM to 12:10 PM PT, Google Talk, Google Hangouts (including Chat and Video), Google. Voice, and the Google App ...

Google Apps Incident Report
Apr 17, 2013 - The following is the incident report for the Google services access ... Talk, Google Sync, the Admin panel, and the Cloud Console, and to a ...

Google Apps Incident Report
Mar 19, 2013 - Applications using the Google Drive and Docs APIs also returned errors. ... We thank you for your business and continued support. Sincerely,.

Google Apps Incident Report
Feb 27, 2011 - Google Engineering reverted the storage software update, and halted further deployment. Restoration Process. While analyzing the issue and its root cause, Google Engineering also worked on the process to restore users' accounts. At 6:0

Google Apps Incident Report
Apr 17, 2012 - Prepared for Google Apps for Business customers. The following is the ... Enhance internal documentation for configuration management.

Google Apps Incident Report
This misconfiguration prevented changes to existing customer data for upgraded users. ... Eliminate the need for server restarts to recover from this type of error.

Google Apps Incident Report
At 7:50 AM PT | 16:00 UTC November 15, Google Calendar Engineering brought a system of servers ... your business and continued support during this time.

Form - Parental Permission Form, Wrestling Minimum Weight ...
Page 1 of 1. NEW YORK STATE PUBLIC HIGH SCHOOL ATHLETIC ASSOCIATION. WRESTLING MINIMUM WEIGHT ASSESSMENT. PARENTAL AWARENESS FORM. The appropriate and healthful control of body weight for wrestlers has been a concern of athletes, coaches,. athletic t

Incident Report
Feb 24, 2009 - The root cause of the problem was a software bug that caused an ... we monitor our systems 24 x 7, we have engineers available to analyze.

Google Apps Incident Report
Nov 15, 2010 - Prepared for Google Apps Customers ... Apps customers on November 15, 2010. ... your business and continued support during this time.

Google Apps Incident Report
Feb 27, 2011 - Google Engineering reverted the storage software update, and halted ... better identify this class of bug during the software development cycle.

Google Apps Incident Report
We understand this service issue has impacted our valued customers and users, and we apologize to everyone ... At 6:12 AM PDT, a bug in a thirdparty software update caused a partial failure of a Google network router in ... escalated the software iss

Google Apps Incident Report
Mar 18, 2013 - service disruption was an issue in the network control software. Actions and Root Cause Analysis. At 6:09 AM PT, a portion of Google's network ...

Application Form - NRHA Registration Form - Letchworth Roller ...
Application Form - NRHA Registration Form. CLUB NAME. SEASON. SECTION A - Class of membership ( please check box where appropriate ).

Google Apps Incident Report
Google Drive list. Applications using ... The Google Engineering team conducted an internal review and analysis of the March 21 event. They ... Modify the Drive software to more reliably serve user requests during short periods where overall.

Google Apps Incident Report
Dec 10, 2012 - Actions and Root Cause Analysis. Background: The load balancing software routes the millions of users' requests to Google data centers.

Google Apps Incident Report
Google Apps Incident Report. Google Docs Outage - September 7, 2011. Prepared for Google Apps for Business customers. The following is the incident report ...

Google Apps Incident Report
Google Apps Incident Report. Gmail Outage - September 23, 2011. Prepared for Google Apps for Business customers. The following is the incident report for the ...

ECS Form
Policy No/Certif No. Policy Holder`s Name. Address. Telephone No. Email ID ... for our record, Your banker should be a participant of NEFT/RTGS Facility.

Posting Form
Performs custodial cleaning and light maintenance of school site classroom, multi-use, office, immediate grounds, and related facilities. Custodian I. Notices may ... available at the Human Resources Office and return before: Current Employees: If yo