Why Small Planes Crash (The 100-Year Design Flaw Nobody Fixed)

Main ideas / concepts / lessons

• Traditional airplane design starts from risk modeling of functions

  • The design process typically evaluates each airplane function and estimates what catastrophe could occur if that function fails during flight.
  • The FAA approves designs that limit catastrophic risk to a very small threshold: 10⁻⁶ probability.
  • This threshold is framed as equivalent to being “catastrophe-free” 24/7 for over 100 years.

• Accidents are often caused by human error, not purely mechanical unreliability

  • The subtitles emphasize that “every one of these was pilot error,” illustrating that even when planes are well-built, pilots can still make inputs that become dangerous under stress.

• Training and experience do not straightforwardly reduce fatality risk

  • The “obvious answer” proposed is to train pilots more / rely on more hours / more checklists.
  • However, the speaker claims data shows a counterintuitive pattern:
    • 0–100 hours pilots show the lowest fatality rate: 11.9%.
    • 500–2500 hours pilots have the highest probability of dying, representing 19% of all fatalities.
    • 10,000+ hours pilots do not fare much better either.
  • A possible explanation mentioned: many accidents in the lowest-hours category involve a student pilot flying with a certified instructor.

• General aviation fatal accidents are framed as having four “buckets”

  • The video states: “All these fatal general aviation accidents fall into four buckets,” though the subtitles do not list the buckets.

• A company’s proposed solution: shift safety focus to the human-machine interface and automation

  • Skytron’s philosophy (as described in the subtitles) is to design with:
    • Human safety systems
    • Simplified controls
    • Full envelope protection (automation that prevents dangerous out-of-bounds conditions)
    • Automatic terrain avoidance
    • Automated twin-engine handling
  • The critique is that current designs may optimize part reliability, but not the most unreliable aspect—human operation.

• Regulatory and design shift toward “car-like” flying

  • The FAA began funding a project inspired by NASA’s concept.
  • The concept question: Can redesigning intuitive flight controls make flying as safe and simple as driving?
  • A study is referenced where fly-by-wire plus a radically simplified display helped:
    • People with little or no piloting experience
    • Gain confidence to climb, cruise, and descend within about 1 hour
    • Without stalling.

• “Mosaic in 2025” is mentioned as enabling updated design philosophies

  • Mosaic is described as revising outdated regulations, allowing aircraft to be designed around these safer, simplified-control ideas.

• Skytron’s approach includes building a cockpit test lab (“Woodbird”)

  • Skytron says they start in the cockpit and built a human-in-the-loop lab called Woodbird to test “ultimate human-machine relationship” and to pressure test their concepts.

• Simulator and cockpit testing to empower inexperienced pilots

  • Woodbird is used to bring future Skytron pilots in to:
    • Fly a simulator for the first time
    • See if new pilots can achieve a level of control comparable to professionals.

• Automated flight control behavior aims to reduce the consequences of pilot mistakes

  • The airplane is described as assuming the pilot will be human (imperfect), rather than expecting perfection.
  • Example behavior: in a potentially dangerous situation, the plane automatically nudges the aircraft back in the right direction (to prevent stalls / dangerous outcomes).

• Control system concept: “computer-defined” control feel, less manual yaw/pitch/roll

  • The subtitles describe control laws designed by a person named Lucas, producing a feel “radically different than a traditional airplane.”
  • Instead of a conventional pilot-driven multi-axis control approach, the system can make flight feel more like a video game (as described in the subtitles).

• Fail-safe display philosophy

  • If “both computers go down,” the system should still provide at least one minimal display set:
    • airspeed, altitude, heading, and targets.

• Overall vision

  • The cockpit should be engineered to prevent human error and empower pilots.
  • The aspirational analogy: like the personal automobile, a safe personal airplane would let people travel easily—“as safe as a car.”
  • The video ends by returning to experimentation: identify which features matter most and keep testing via Woodbird.

---

Methodology / approach (detailed bullet list)

Airplane design safety approach (as described)

• Assess every airplane function for the risk/catastrophe potential if it fails in flight.
• Seek FAA approval by meeting a catastrophic-risk threshold:
  • target probability ≤ 10⁻⁶ (described as “catastrophe-free 24/7 for over 100 years”)
• Recognize that meeting mechanical reliability goals may still fail if the human element (pilot inputs under stress) remains a key failure mode.

Human-centered design approach (Skytron)

• Start the design in the cockpit (human-machine relationship first).
• Use human-in-the-loop testing:
  • Build Woodbird to prototype and validate design theories.
  • Bring in “brand new” pilots to test simulator performance quickly.
• Implement cockpit and controls features intended to reduce or neutralize human error:
  • simplified controls
  • full envelope protection
  • safety automation such as terrain avoidance
  • automated engine handling (twin-engine)
• Use radically simplified displays and fly-by-wire/control laws to make flight tasks more intuitive.
• Build robustness:
  • define minimal fail-safe information to show during computer failures (airspeed/altitude/heading/targets).
• Pressure-test assumptions:
  • evaluate control ergonomics (e.g., right-handed pilot using left hand for secondary tasks)
  • evaluate whether new pilots can achieve safe control outcomes quickly.

---

Speakers / sources featured (from the subtitles)

• FAA (Federal Aviation Administration) — regulatory authority mentioned
• NASA — agency whose concept is referenced
• Lucas — named individual who designed “control laws” for the airplane’s control behavior
• The narrator / Skytron speaker(s) — multiple “man talking…” segments (not uniquely identified by name in the subtitles)
• Skytron — the company presenting its design philosophy (treated as a source/entity in the subtitles)