Project ideas from Hacker News discussions.

Qantas Airbus A380 engine failure in 2010 (2023)

📝 Discussion Summary (Click to expand)

1. Engineering safety design & lessons from uncontained engine failure
- “When a disk breaks, it's an uncontained engine failure. A 20 kg disk fragment flying at Mach 1 goes through everything. Airframes are designed so that no single fragment can destroy all redundant systems at once in this zone (flight controls, fuel lines, and hydraulic systems). Jet fuel cannot be stored in the wings in this zone.” – u1hcw9nx
- “When the fragments of the IP turbine disk passed through the wing and belly of the A380, they caused considerable secondary damage … the left wing fuel tank, which sprang a leak.” – Usefulcat (quoting the Aviation Herald article)
- “good engineering design (the astonishing degree of redundancy built into the A380 proved just enough to prevent catastrophe)” – libraryofbabel

2. Manufacturing quality‑control and oversight failures
- “Investigators also criticized the culture within the Hucknall facility … identifying signs of complacency and widespread procedural non‑compliance. A paperwork review showed that the required signatures were missing from 131 out of 138 retrospective concessions issued between 2009 and 2011…” – chasil
- “That's an oversight failure as much as a failure of that plant.” – jacquesm
- “The oversight was at the plant.” – NetMageSCW

3. Pilot/crew response and procedural work‑arounds that averted disaster
- “Check Captain Evans was able to fix the problem by manually entering their actual landing weight, overriding the program’s assumption of a maximum landing weight.” – ahartmetz
- “When calculating the landing distance, the software applied a generic ‘operational coefficient’ … the coefficient was applied a total of 9 times … However, Check Captain Evans … overridden the program’s assumption… and lo and behold, … they could just barely land …” – exceptione (quoting the investigation report)
- “human troubleshooting under pressure in the cockpit by some smart people with vast experience who remained calm throughout.” – libraryofbabel


🚀 Project Ideas

Engine Health Monitoring & Predictive Maintenance for Turbine Engines

Summary

  • Real-time collection of temperature, vibration, and pressure sensors across turbine stages.
  • AI-driven anomaly detection to flag early signs of disk or bearing degradation.
  • Core value proposition: Prevent uncontained engine failures by enabling proactive maintenance before catastrophic damage.

Details

Key Value
Target Audience Airlines, MROs, engine OEMs
Core Feature Streaming sensor analytics with anomaly detection alerts
Tech Stack Python (PyTorch/TensorFlow), Apache Kafka, InfluxDB, Grafana, Docker/K8s
Difficulty Medium
Monetization Revenue-ready: SaaS subscription per engine per month

Notes

  • Addresses amelius' suggestion: "the whole failure could have been prevented with a bunch of temperature sensors spread throughout the engine, and a good anomaly detection system."
  • Provides actionable insights that could have caught the turbine disk fatigue before fracture.
  • Enables data-driven maintenance culture, reducing reliance on manual inspections and paperwork compliance.

Wiring Routing Safety Verifier for Aircraft Design

Summary

  • Checks electrical/hydraulic wiring routes against engine disk burst containment zones and other hazard zones.
  • Flags insufficient redundancy or routing through high‑risk cones.
  • Core value proposition: Ensure compliance with safety regulations early in design, avoiding costly rework and hazardous configurations like the Qantas A380 wing wiring issue.

Details

Key Value
Target Audience Aircraft systems engineers, CAD/PLM designers (CATIA, Siemens NX, etc.)
Core Feature Automated hazard‑zone intersection analysis and redundancy verification
- Tech Stack C++/Python backend, Qt or WebGL front‑end, integration via CATIA add‑in or STEP/IGES importer
Difficulty High
Monetization Revenue-ready: Per‑seat annual license or project‑based fees

Notes

  • Directly responds to sam1714's observation: "wing wiring was routed through the engine disk burst axes … with insufficient redundancy."
  • Would have caught the routing error during A380 development, preventing the post‑landing engine shutdown problem.
  • Encourages discussion on safety‑by‑design and provides a tangible tool for HN’s aerospace‑savvy audience.

Robust Aircraft Performance Calculator (Landing/Takeoff Distance)

Summary

  • Computes takeoff and landing distances while correctly applying operational coefficients only once per failure set.
  • Handles multiple simultaneous system failures without double‑counting penalties.
  • Core value proposition: Eliminates the software bug that led to an over‑conservative landing‑distance estimate on Qantas 32, giving pilots reliable performance data under abnormal conditions.

Details

Key Value
Target Audience Flight planners, dispatchers, pilots, aircraft performance engineers
Core Feature Failure‑aware performance modeling with configurable coefficient logic
Tech Stack Rust for core calculations, WebAssembly for UI, React/TypeScript frontend, optional cloud API
Difficulty Medium
Monetization Revenue-ready: Subscription tier for airlines/Dispatch centers; free tier for hobbyists

Notes

  • Mirrors the issue highlighted by exceptione: the landing‑distance software applied the operational coefficient repeatedly, producing an unusable “no result.”
  • A correct calculator would have allowed the crew to trust the computer’s output, reducing workload during the emergency.
  • Offers a concrete example of how rigorous software engineering can improve flight safety, a topic that resonates with HN’s technical community.

Read Later