1 / 18

JHSAT Status: Data Analysis, Safety Recommendations, and Engaging with International Community

This report provides an update on the data analysis conducted by the JHSAT team, including the progress made in processing accidents and identifying safety recommendations. It also highlights the importance of engaging with the international community to reduce helicopter accidents worldwide.

dha
Download Presentation

JHSAT Status: Data Analysis, Safety Recommendations, and Engaging with International Community

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JHSAT Status September 25, 2006 Mark Liptak FAA ANE-110Jack Drake HAI

  2. JHSAT Status Data Analysis Engaging with the international community Offering near term safety recommendations

  3. Data Analysis

  4. Data Analysis: The JHSAT team is currently processing 190 accidents The accident data has been downloaded from the NTSB (~4000 files) For each accident the JHSAT performs the following: reconstruct the sequence of events identify what went wrong and why it went wrong assign an appropriate problem statement identify appropriate corrective action(s) score findings based on validity, importance, ability and usage The team has currently completed 90 of 190 accidents

  5. JHSAT currently working process areas highlighted in yellow CharterDevelopment EstablishTeam Select Data Set ReviewNTSBDocket Data DevelopEventSequence Identify InterventionStrategies ScoreProblemValidity &Importance ScoreInterventionAbility/Usage Assign StdProblem Statements IdentifyProblems(what/why) Yes TechnicalReview&Expert Validation Conflicts? Prioritize byOverallEffectiveness ReportResults No IHST JHSIT

  6. Data Analysis: To date the accidents analyzed have covered a wide spectrum of helicopter types and operations. We expect to be able to offer a comprehensive set of safety recommendations based on the analyses to the IHST and JHSIT. The data has not been ranked by the JHSAT yet. This will be accomplished as a final step prior to review with experts in the affected recommendation areas.

  7. Engaging with the international community

  8. Engaging with the international community The preceding slide shows worldwide accident trends for the last 26 years. The criticality of working with the international community to reduce worldwide rates is readily apparent since the US accounts for only 35 to 40% of accidents on an annual basis. The JHSAT team is developing contacts and coordinating this activity. Matt Rigsby from FAA-ASW will be acting as the contact point for identifying overseas and military partners. Any entity that possess large helicopter accident datasets that could be processed by the JHSAT method should be considered. EASA and Canada moving toward partnering with us in this process. On-going efforts to identify other partners from Asia, South America, Oceania, etc.

  9. Engaging with the international community A structured approach will be used to manage the analytical and implementation work sponsored by the IHST. Key attributes: All recommendations will be data driven Regional ownership - Data is owned and analyzed by those most familiar with it. Safety recommendations will be implemented by teams most familiar with local needs. JHSAT and JHSIT lead teams will be responsible for training/coaching regional teams, measuring the results of the safety recommendations and implementation effectiveness.

  10. IHST Safety Initiative Analysis, Implementation and Metrics Management Structure IHSTExecutive Committee Need to maintain a strongcommunication/feedback loopbetween IHST – JHSAT - JHSIT Process development usingUS NTSB datarepresents 48% ofworldwide fleet JHSAT Lead Group Measure Accident Reductions Effectiveness Measure Implementation Effectiveness JHSIT Lead Group JHSAT sends recommendations to JHSIT Canada JHSAT EASA JHSAT JHSAT/JHSITcross-talk Canada JHSIT EASA JHSIT Region X, Y, Z JHSIT Others? US/CAN/EASA/X,Y,Z Implementation Results US/CAN/EASA Consolidated Recommendations Regions X, Y, Z defined as those pockets of operation not ableto staff a full JHSAT team and are willing to work implementation of US/CAN/EASA findings to benefit their fleets

  11. JHSAT Lead GroupAnalysis of International Data Matt Rigsby is JHSAT POC Seeking data rich partners Preliminary discussions with: Canada EASA (CAA-UK, France BEA) Brazil (contacted, no reply) NZ (contacted, no reply) Australia Chile Canadian Military USN Near-term: bring Canada on-line as a test case Consider EASA next Interim Goal: have Canada/EASA present status at the 2007 IHSS Symposium in Montreal Demonstrate that this is an international effort, and it has momentum Engaging with the International Community IHSTOutreach/MarketingEmerging Fleets Somen is the IHST POCIdentify emerging/high growth markets Develop strategy to: Foster participation Benefit from IHST knowledge base Candidates: China India CIS? JHSIT Lead GroupImplementingRegional Solutions JHSIT will also have international partner management responsibilities: custom tailored regional solutions coordinated with JHSAT coordinated with IHST

  12. Potential Barriers: JHSAT: Variation in dataset quality, definitions, etc, around the world may make use of a standardized JHSAT approach more difficult. Military data may not be available.Lack of fleet hours will complicate ability to measure results. Regional teams may be difficult to staff with sufficient level of expertise representing manufacturers, operators and regulatory interests. JHSIT:Regional operations and regulations may make some implementation actions difficult.

  13. Coordinating JHSAT US and International Efforts US CivilDataset Selection (1/2 of helicopters Worldwide) JSAT ProcessUnderstandingRefining Expert Review/Validation JHSAT Analysis TechReview 1Q 07 May-Dec 06 Jan 07 Jan 07 May/June 06 First SetUS MitigationRecs Mar/Apr 06 FCAA & Military Partners conductJHSATanalyses on their accident data Train FCAA & Military Partners in JHSATProcess MitigationRecsFCAA & Mil IdentifyFCAA &MilitaryPartners 1Q 08 MitigationRecs - Global Sept 06 TBD 07 TBD 06/07 TBD 07 IHST JHSAT is now working to bring EASA and Canada into the process

  14. Offering near term safety recommendations

  15. Offering near term safety recommendations The JHSAT has identified important recommendations from a series of existing helicopter safety reports. (listed on the next slide) The team is currently drafting narrative statements that give background and context to the recommendations. These recommendations will be submitted to the IHST in November so that the JHSIT will have several well founded general recommendations to work with. The JHSAT plan to issue its full set of analytical results by the end of 1Q07.

  16. JHSAT is reviewing the recommendations of the following reports: NASA - U.S. Civil Rotorcraft Accidents, 1963 Through 1997 NASA - Analysis of US Civil Rotorcraft Accidents from 1990 to 1996 and Implications for a Safety Program NASA - ASRS Rotorcraft Incident Study - Draft Data Summary Aviation Safety Reporting System NASA - Helicopter Accident Analysis Team AMPA - A Safety Review and Risk Assessment in Air Medical Transport CRS - Report for Congress - Military Aviation Safety OGP - Safety Performance of Helicopter Operations in the Oil and Gas Industry - 2000 Data TSB Canada - Lessons Learned from TSB Investigation of Helicopter Accidents (1994 - 2003) Bell Textron - History of Helicopter Safety Other NTSB and international reports may be considered.

  17. Please forward questions to Mark Liptak, JHSAT co-chairperson. This document was prepared in September 2006

More Related