← Back to NASA Technology Projects
Prediction of Safety Incidents, Year 1
Completed
TRL 3 (started at 1, targeting 3)
Description
Safety incidents, including injuries, property damage and mission failures, cost NASA and contractors thousands of dollars in direct and indirect costs. This project seeks to define, develop and test an algorithm(s) that will use hazard identification data as input to predict when and where there is a high probability of a safety incident occurring so that resources and attention can be appropriately matched based to the priority of concern.
Benefits
NASA /SSC and other centers will benefit from this project through bringing additional value to data already collected and in informing future data collection needs. While this pilot study will be based on facilities, the resulting algorithm will also be relevant to programs and projects which collect similar data based on program hardware. These algorithms could have value for prediction of facility safety issues well beyond NASA into commercial environments as well and help optimize expenditure of resources for safety in a variety of facilities.
Details
| Technology area | Air Traffic Management and Range Tracking Systems > Traffic Management Concepts |
| Program | Center Innovation Fund: SSC CIF (SSC CIF) |
| Lead organization | Stennis Space Center, Stennis Space Center, MS |
| Start date | 2017-10-01 |
| End date | 2018-09-30 |
Project contacts
Listed on TechPort itself — the most direct way to ask about this specific project.
How to get involved
This is early/mid-stage (TRL 3) — the most realistic path in is NASA SBIR/STTR, which funds small businesses and research institutions to develop technology aligned with NASA's needs (equity-free, phased funding). Check whether a current SBIR/STTR solicitation topic overlaps with this project's technology area, or contact the project directly (above) to ask.
None of these are guaranteed paths for this specific project — TechPort itself doesn't have an "apply" button. Reaching out to the contact(s) above with a specific question is usually the fastest way to find out what's actually open.