1 / 12

FLIGHT TEST SAFETY DATABASE

FLIGHT TEST SAFETY DATABASE. An Online Resource for Flight Test Safety Planning. Presented to: European Flight Test Safety Workshop Vienna, Austria By: John Hed, Flight Test Engineer FAA Seattle Aircraft Certification Office

hollowaym
Télécharger la présentation

FLIGHT TEST SAFETY DATABASE

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. FLIGHT TEST SAFETY DATABASE An Online Resource for Flight Test Safety Planning Presented to: European Flight Test Safety Workshop Vienna, Austria By: John Hed, Flight Test Engineer FAA Seattle Aircraft Certification Office Date: 11 November, 2009

  2. Outline Description/Goal Background Demo Status Summary & Conclusion

  3. Description/Goal • To develop an interactive web site where we could consolidate flight test safety info in one central location. • Allow testers easy access to a wide range of safety info • Allows user to pick and choose what safety items to use. • Help ‘spread the knowledge’ of flight test safety techniques • There should be no ‘secrets’ out there.

  4. Database Background • Challenges: • Lots of different kinds of flight tests! • By definition, many are quite hazardous. • Nobody wants to see friends get injured or killed. • Test assets are getting too expensive. • Many different test organizations all over the world. • Everyone does safety a little bit differently. • Great deal of ‘corporate knowledge’ out there but not documented and thus ‘dies’ with the owner.

  5. Database Background • 1997 - FAA Order 4040.26A required implementation of a risk management process that: • Identifies hazards • Assess the risks • Identifies/implements mitigating actions • Accept risk at appropriate level • We still found every office did safety differently

  6. Database Background • Solution: • FAA began to develop internal database (2001). • NASA began work on “Flight Test Safety Handbook” with eye towards internet also. • Teamed together to develop an online database. • National Test Pilot School contracted to gather FAA data. • Other groups formed to gather military, development and other data (e.g. Icing, high AOA, propulsion…).

  7. http://pbma.nasa.gov/ftsdb/Home.aspxOn-line Demo Flight Test Safety Database

  8. Database Status & Update • Mostly complete with FAA data input. • Continuing to gather more data: • Military and R&D data • Reference data (videos, experts, test centers, etc…) • Continue with Monthly telecons • Complete with ‘off-line’ input method • Just completed redesign to improve “look and feel” • Continuous debugging and interface improvements • Future: • Incorporate lessons learned. • Populate reference area

  9. Disclaimer • The database IS a wide array of test safety ideas and suggestions • But it is NOT an FAA-mandated solution. • And it is NOT an auto-safety planning device. • The matured hazards, causes and mitigations are necessarily generic. • Your test will have unique problems and will require unique solutions. • The THA database can be an excellent starting point.

  10. Conclusion • Flight testing presents many unique safety challenges. • To meet these challenges we must apply proven safety practices. • Past experience has demonstrated that we are vulnerable to safety risks/hazards (we constantly ‘re-learn old lessons). • To increase safety, we MUST share safety data. • Workshops • FTSDb

  11. WE NEED YOUR HELP ! • PLEASE GO AND USE THE SITE !http://pbma.nasa.gov/ftsdb/Home.aspx • Please Register • So we can track usage. • So we can send you updates. • PLEASE give us feedback. • The good and the bad! • Suggestions for improvements. • Bart Henwood, (barton.e.henwood@nasa.gov), 661-276-5746 • Joe Orwat, (joe.orwat-1@nasa.gov), 661-276-3866 • John Hed, (john.hed@faa.gov), 425-917-6518

  12. Thank You ! Questions ?

More Related