model analysis user risk: medium
FDR Analysis Program for Commercial Airlines
Act as an Aviation Data Analyst to design a Flight Data Recorder (FDR) analysis program for commercial airlines that analyzes data from multiple aircraft types, generates comprehen…
- Policy sensitive
- Human review
PROMPT
Act as an Aviation Data Analyst. You are tasked with developing a Flight Data Recorder (FDR) analysis program for commercial airlines. The program should be capable of generating detailed reports for various aircraft types. Your task is to: - Design a system that can analyze FDR data from multiple aircraft types. - Ensure the program generates comprehensive reports highlighting key performance metrics and anomalies. - Implement data visualization tools to assist in interpreting the analysis results. Rules: - The program must adhere to industry standards for data analysis and reporting. - Ensure compatibility with existing aircraft systems and data formats.
OPTIONAL CONTEXT
- aircraft types
- FDR data formats
ROLES & RULES
Role assignments
- Act as an Aviation Data Analyst.
- The program must adhere to industry standards for data analysis and reporting.
- Ensure compatibility with existing aircraft systems and data formats.
EXPECTED OUTPUT
- Format
- code
- Constraints
-
- adhere to industry standards for data analysis and reporting
- ensure compatibility with existing aircraft systems and data formats
SUCCESS CRITERIA
- Design a system that can analyze FDR data from multiple aircraft types.
- Ensure the program generates comprehensive reports highlighting key performance metrics and anomalies.
- Implement data visualization tools to assist in interpreting the analysis results.
FAILURE MODES
- May produce generic analysis without specifying industry standards.
- Might overlook compatibility with specific aircraft data formats.
CAVEATS
- Missing context
-
- Programming language
- Specific aircraft types and FDR data formats (e.g., ARINC 717)
- List of key metrics and anomalies
- Sample FDR data
- Output format for the program and reports
- Ambiguities
-
- Does not specify programming language or implementation details (e.g., code vs. design document).
- Unclear what constitutes 'key performance metrics and anomalies'.
- Vague on 'industry standards' without naming them (e.g., ARINC).
- No definition of 'comprehensive reports' or visualization tools.
QUALITY
- OVERALL
- 0.50
- CLARITY
- 0.85
- SPECIFICITY
- 0.45
- REUSABILITY
- 0.20
- COMPLETENESS
- 0.40
IMPROVEMENT SUGGESTIONS
- Add 'Implement in Python using libraries like Pandas, Matplotlib, and Plotly.'
- Specify 'Support Boeing 737, Airbus A320; handle ARINC 429/717 formats.'
- List examples: 'Metrics: altitude, speed, engine parameters; Anomalies: exceedances, deviations.'
- Require 'Output: Jupyter notebook with code, sample analysis, and interactive dashboards.'
- Define success: 'Report must flag anomalies with 95% accuracy on validation data.'
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR MODEL
- Travel Website SEO UX CRO Auditormodelanalysis
- Multi-Dimensional 5 Whys Root Cause Guidemodelanalysis
- Lazy AI Email Detectormodelanalysis
- Visual Media Cinematic Forensics Analyzermodelanalysis
- AI Computer Vision Algorithm Analyzermodelanalysis
- Comprehensive Repository Bug Audit and Fixermodelanalysis
- Codebase Pattern Skill File Generatormodelanalysis
- DeepThinker-CA Recursive Thinking Analyzermodelanalysis
- Unified Image Style Extractormodelanalysis
- Bug Risk Analyst for Code Changesmodelanalysis