
Avionics Failure Analysis Assistant
Systematically diagnose avionics failures with compliance-ready root cause analysis
What You Can Do
You can systematically diagnose avionics system failures by organizing failure symptoms into decision frameworks that consider hardware, software, and environmental factors simultaneously. The skill generates failure logic trees, maps cross-system dependencies, and produces defensible root cause analysis reports that meet FAA/EASA certification requirements. This transforms ad-hoc troubleshooting into a repeatable, auditable methodology that accelerates fault isolation and supports occurrence reporting.
Features
Builds hierarchical decision trees that systematically eliminate failure hypotheses based on symptoms and test results
Visualizes interdependencies between avionics subsystems (power, navigation, communication, display) to identify hidden failure propagation paths
Generates certification-compliant reports with failure modes, contributing factors, and preventive actions aligned with FAA/EASA standards
Ranks failure scenarios by probability and testability to focus troubleshooting efforts on high-likelihood causes first
Structures investigation of non-repeatable failures by categorizing environmental triggers, operational modes, and failure thresholds
Translates diagnostic logic into step-by-step troubleshooting procedures for field maintenance manuals
Evaluates whether identified failure modes pose risks across the aircraft fleet and recommends service bulletins or airworthiness directives
Example Output
Example 1: Navigation Signal Loss Investigation
Input: GPS receiver intermittently loses signal lock during specific flight phases
Output:
- Failure Tree: Signal loss → Receiver hardware fault (10% probability) | Antenna connector degradation (45%) | Software state machine error (30%) | Environmental interference (15%)
- Dependencies mapped: Power distribution → Receiver bias → LNA gain → Signal processing
- Root cause (most likely): Intermittent connector corrosion in antenna feed, triggered by thermal cycling
- Recommended action: Service bulletin requiring connector inspection and replacement
Example 2: Autopilot Disconnect Event
Input: Autopilot disengaged unexpectedly during cruise, crew unable to re-engage for 3 minutes
Output:
- Failure logic: Disconnect command → Hardware actuation fault (5%) | Software watchdog timeout (60%) | Communication link interruption (25%) | Sensor anomaly (10%)
- Cross-system analysis: Flight control computer ↔ Autopilot module ↔ Inertial reference system ↔ Air data computer
- Root cause: Latching relay stuck in autopilot disconnect path due to manufacturing defect in batch 2024-Q1
- Compliance action: Airworthiness directive requiring relay replacement and functional test procedure
What's Included
- SKILL.md: Core instruction file with failure analysis methodology
- Failure Logic Tree Template: Decision tree framework for organizing failure hypotheses
- Cross-System Dependency Mapping Worksheet: Structured format for documenting system interdependencies and failure propagation paths
- Root Cause Analysis Report Template: FAA/EASA-compliant documentation format with sections for failure modes, contributing factors, and corrective actions
- Troubleshooting Procedure Checklist: Step-by-step format for converting diagnostic logic into field maintenance instructions
Who It's For
- Avionics Engineers — Diagnosing complex system failures and documenting root causes for certification and fleet management
- Flight Test Engineers — Investigating anomalies and failures discovered during development and qualification testing
- Maintenance Planning Specialists — Creating troubleshooting procedures and technical documentation for field maintenance teams
- Quality Assurance/Reliability Engineers — Analyzing design robustness and assessing fleet-wide risk from identified failure modes
- Accident/Incident Investigators — Conducting technical analysis of avionics failures in occurrence investigations with defensible methodology
Best For
- Post-event root cause analysis of in-service failures and field observations
- Intermittent fault investigation requiring systematic elimination of possibilities
- Compliance documentation for occurrence reports (AIRs, SIRs) and airworthiness directives
- Maintenance manual development and troubleshooting procedure creation
- Design robustness validation during development and pre-certification analysis







