SMS Pro Issue Reporting


Loading...

Bermuda Skyport Corporation Ltd. encourages everybody to report all occurrences and safety concerns.

Confidential Reporting:

The purpose of the reporting system is to identify and resolve safety issues by addressing the root causes of incidents so that they do not recur, not to assign blame when something does go wrong.  As such, the names of those reporting will be kept confidential and will not appear on any published material relating to the report (the only exception to this is when required by Regulations to include names of persons involved).

Anonymous Reporting:

To promote confidence in the Safety Management System, reports may be submitted anonymously if desired.  Anonymous Reporting is not applicable for events that are legally reportable (e.g. dangerous occurrence or injury events reportable to the Bermuda Govt Office of Safety and Health or occurrences reportable to the Department of Civil Aviation).

Please note; if you are submitting an anonymous report, please include as much detail as possible to ensure that an investigation may be properly completed.

Nature of Issue/Concern

Full Name:
Email:    

Select Type of Concern
Select Custom Report Type
Select Audit

Bird Strike Reporting Form


Operator
Aircraft Make/Model
Engine Make/Model
Aircraft Registration
Time of Day
Airport Name
Runway Used
Location
Height AGL (ft)
Speed (IAS) (kt)
Flight Phase
Birdstrike Status
Radome
Windshield
Nose (excluding above)
Engine #1
Engine #2
Engine #3
Engine #4
Propeller
Wing/Rotor
Fuselage
Landing Gear
Tail
Lights
Other (specify)
Effect on Flight
Sky Condition
Precipitation
Bird Species
Number of birds seen
Number of Birds Struck
Size of Birds
Pilot Warned of Birds
Person Preparing Report
Reporter Title
Department

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

This report type is not setup, use OLD ISSUE REPORTER

Request Document Change

Document Title: 
Section(s) - Clause(s) or Paragraph(s)
Location of Discovery: 
Request Type:





Description of Issue or Required Change
Reason

Passenger Accident/Incident Report

Aircraft Type
Aircraft Registration
Date of Occurrence:
RadDatePicker
RadDatePicker
Open the calendar popup.
Safari users have to manually input the date in yyyy-MM-dd format (e.g. 2016-01-31), or switch to another browser (e.g. Chrome or Firefox). Leave blank if unknown.
Time of Occurrence

Passenger Name
Telephone number
Address
City
State, Zip, Country
Age
Occupation

Nature of Incident/Injury
Captain
Flight Attendant 1
First Officer
Flight Attendant 2

Ground Assistance Required?
Detailed Description of Occurrence

General Issue Details with Suggested Corrective Action

Provide Short Title of IssueRequired
(Example: Go-around at Las Vegas, Unstabilized Approach)
Describe Issue, including any factors you feel contributed (4000 characters max)Required
Remaining Characters: 4000
How severe or critical is this issue?
Inital Action taken to correct problem or prevent recurrence (1000 characters max)
Remaining Characters: 1000
Suggestions to correct problem or prevent recurrence (1000 characters max)
Remaining Characters: 1000

Where & When Occurred

Location
(Hangar / Runway / Office / Flight 321 / etc.)
Date/Time Occurred
RadDatePicker
RadDatePicker
Open the calendar popup.
Leave date blank if unknown
Safari users have to manually input the date in yyyy-MM-dd format (e.g. 2016-01-31), or switch to another browser (e.g. Chrome or Firefox). Leave blank if unknown.

Notes
Right-click (or double click on mobile devices) to add markers

Markers are draggable

Right-click marker to remove

Click marker to see exact location

Entities Involved

NamePositionPhoneRoleDelete
No records to display.

Add People Involved

Name
Position
Phone
Role
NwdsAttachments
Overview
  • Title:
  • Short Description:
  • Corrective Action:
  • Location:
  • Associated Vendor/Client:
  • Date Occurred:

  • People Involved
    NamePositionPhoneRole
    No records to display.

  • Vehicles Involved
Add Attachments...

Thank you for submitting the issue.
Note: For best results, do not use the browser back button. Use "Previous" button when present.

Quick Report

Provide Short Title of IssueRequired
(Example: Go-around at Las Vegas, Unstabilized Approach)
Describe Issue, including any factors you feel contributed (4000 characters max)Required
Remaining Characters: 4000
How severe or critical is this issue?
Inital Action taken to correct problem or prevent recurrence (1000 characters max)
Remaining Characters: 1000
Suggestions to correct problem or prevent recurrence (1000 characters max)
Remaining Characters: 1000


Issue Reports

The Issue Report (IR) is the principle tool for the SMS and its use is encouraged for the reporting of any issue that may have safety considerations.  A report may be submitted as a reactive part of the SMS following an incident or proactively on recognition of a hazard that presents a risk.  IR are submitted through the SMS Pro at www.bdasafety.com.  A link to the reporting module is also provided on the Bermuda Airport website.

Anonymous Reports

Anybody may submit an anonymous report using the general public and contractor link on the bdasafety.com website.  While a report may be submitted anonymously, contact information is very helpful should there be any follow-up questions.  However there is no requirement to provide name or other identifying information.

Feedback concerning anonymous reports may be found in the Safety Newsletter as appropriate.

Confidential Reports

SMS-Pro offers the facility for the reporter to provide his name and contact information but to submit a confidential report.  In such cases, the identity of the reporter is known only to the SQM.  The architecture of SMS-Pro is such that the identity of the reporter is hidden from all other parties, even during the investigation and subsequent processing phase.

Guidance for Submitting an IR

This data is used for the identification of hazards, safety-related issues for all areas of BDA, both airside and landside or for areas with potential for improvement.  Name and contact details may be provided or the report may be submitted anonymously.  Details will be forwarded to parties outside the OSQ only insofar as it is necessary for investigation.  If any data contained in the report is required to be distributed outside the OSQ it will be de-identified.  The fundamental purpose of an IR is to identify potentially unsafe practices and conditions that exist at BDA.

 Provide Short Title of Issue

A brief description of the event or issue generating the report.

Describe Issue, including any factors you feel contributed

This section addresses why it happened and is the most important part as it allows for the development of corrective actions.  Please include as much information about the issue or concern as possible, including any factors that you believe may have contributed to the event and an estimate of the severity.

Please insert all that apply, adding any other information that you think may be useful.  Particular factors may include one or more of:

1.     DISTRACTION: A very common contributing factor associated with errors of omission.

2.     INTENTIONAL: Any time a rule or procedure was intentionally broken. The circumstances surrounding this decision should be carefully noted.

3.     MEDICATION: Where use of medication may have affected your ability to perform your duties.

4.     FATIGUE: If fatigue contributed to the event it should be noted. This is especially true if it is working pattern induced.

5.     ILLNESS: If illness or injury contributed to the event.

6.     CRM: If a lack of communication contributed to the event.

7.     PERSONAL ISSUES: If personal events or stress contributed to the event (e.g. divorce, death in the family, hospitalization of a loved one, etc.).

8.     PHYSICAL LIMITATION: If any physical limitation contributed to the event (e.g. height, weight, strength, vision, hearing, etc.).

9.     PHYSICAL ENVIRONMENT: Including temperature, humidity, light, darkness, vibration, etc.

10.  DEFECTIVE EQUIPMENT: Including details of the nature of the defect.

11.  TIME PRESSURE: If there was any pressure to make the schedule whether self-imposed or imposed by another individual.

12.  PEER PRESSURE: Any case where a peer urged you to perform in a nonstandard manner.

13.  COMPANY PRESSURE: Any situation where an individual is urged to perform in a non-standard or unprofessional manner.

14.  NOT TRAINED FOR TASK: Any case where an individual is faced with a situation for which there has been no training.

15.  INADEQUATE PROCEDURE: Any case where the procedure called for either did not correct the situation or made it worse.

16.  EXTERNAL PRESSURE: Any situation where an individual is urged to perform in a non-standard or unprofessional manner.

 

Suggestion to Correct Problem of Prevent Recurrence

Please provide any suggestions that you think might help avoid a repeat of the event or that might solve the issue in question.

Where & When Occurred

Provide details of location and date and time of event or when the hazard was identified.

Entities Involved

Please as much information as possible about personnel involved in the event or present at the time.

Attachments

Include photographs or any other attachments that you feel would be useful for analysis of the issue.