Is your method covered — and to what depth?

Aircraft- and system-level failure conditions with project-configurable classification schemes and probability objectives, flight phases, effects, crew response and compensating provisions. Conditions link to their source functions; existing registers arrive through a spreadsheet import wizard with row-level validation.

Interactive tree editor over a computation engine with two independent cut-set solvers — MOCUS and a from-scratch ROBDD — auto-selected by tree size and required to agree. Unavailability models for fixed, exponential, repairable and dormant events with periodic-test intervals, five importance measures, beta-factor CCF. Exports a DOCX report with tree diagrams and an XLSX workbook carrying cut sets, importance rankings and the audit log as its own sheet.

Reliability logic as dependence diagrams per failure condition — the notation many programmes file alongside or instead of fault trees — quantified and synchronised with the FHA so the failure condition and its diagram cannot drift apart.

Worksheet FMEA in the 23-column format working analysts actually use — failure modes with rates and sources, local and end effects, detection, compensating provisions — with each mode linkable to the fault-tree basic event it feeds.

Losses, hazards and constraints per the STPA Handbook, an interactive control-structure editor, unsafe control actions across the four UCA types, and loss scenarios that derive design requirements — with hazards linked back to FHA failure conditions.

Common mode, zonal and particular-risk analysis per ARP4761A, recorded as structured checklist items in the standard's own taxonomy and linked to the failure conditions and analyses they qualify.