ASAP | INCIDENT | FATIGUE REPORTING

As part of our overall safety goals, JSX has established a system for our Crew Members to voluntarily identify and report safety and operational concerns. The collected information is reviewed and analyzed to facilitate early detection and improved awareness of operational deficiencies and adverse trends. This information is used to identify the root causes and determine appropriate remedial actions, which are then monitored for effectiveness. The overall process promotes collaboration between crewmembers, and company leadership for the early identification of hazards and to maintain a proactive approach regarding safety concerns and corrective action recommendations.

• Aviation Safety Action Program (ASAP) – Pilots | Mechanics
• Incident Reporting Program – All Crew Members
• Fatigue Program – Pilots | Inflight | Mechanics

NOTE - If your report involves a possible fatigue issue, you must also file a fatigue report inclusive of your original report. If a fatigue report is the only report needed, no additional reporting is needed.

JSX fosters a voluntary, cooperative, non-punitive environment for the open reporting of safety concerns. Through this reporting, all participants have access to valuable safety information that might not otherwise be obtainable. This information is analyzed, and corrective action is developed, to help resolve safety issues and possibly eliminate deviations from the federal aviation regulations (FARs).

Any safety report may result in disciplinary action when the event involves any of the following: criminal activity, substance abuse, controlled substances, alcohol, or intentional falsification, and must not appear to involve an intentional disregard for safety or reckless conduct.

When you observe a safety problem or experience a safety-related event, you should note the problem or event and describe it in enough detail so that it can be evaluated by your Safety Team.

At an appropriate time during the workday (e.g., after the trip sequence or near the end of your shift), complete and submit electronically the web-based report Form for each safety problem or event.

(1) Within 24 hours after the end of the flight sequence for flight crewmembers, or the end of the duty shift for employees other than flight crewmembers, absent extraordinary circumstances.

For example, if the event occurred at 1400 hours on Monday and a pilot completes the flight sequence for that day at 1900 hours, the report should be filed no later than 1900 hours Tuesday. Non-flight crew covered employees must submit a report within 24 hours of completion of the duty shift for the day of the occurrence.

(2) Within 24 hours of having become aware of possible non-compliance with the FARs, provided the following criteria are met: If a report is submitted later than the time period after the occurrence of an event stated in paragraph (1) above, all available information will be reviewed to determine whether the Crew Member knew or should have known about the possible noncompliance with the FARs within that time period. If it is determined that the Crew Member did not know or could not have known about the possible noncompliance with the FARs until informed of it, they will be directed to the appropriate reporting platform.

The JSX Safety Team maintains a database that continually tracks each event and the analysis of those events. The JSX database is structured to share needed safety information and still maintain anonymity.

ASAP Event Review Committee (ASAP ERC) – Pilots | Mechanics

The ERC conducts a 12-month review of the participating company's ASAP database with emphasis on determining whether corrective actions have been effective in preventing or reducing the recurrence of safety-related events of a similar nature. That review includes recommendations for corrective action for recurring events indicative of adverse safety trends.

"WHEN IN DOUBT, FILL IT OUT."