Functional Programming in Aviation
summary
Shows concrete results: a Haskell logbook with lenses that compiles to PDF/HTML and lives in Git for audits, a weight‑and‑balance generator that produces vector diagrams (Diagrams) for real flights, and a $200 SDR receiving ADS‑B that picks up live traffic at ~15–20 nm and SSHes telemetry home. Cites a striking statistic — VFR into IMC fatal average 178 seconds — and one real map error that misread terrain elevation leading to controlled flight into terrain; warns certification adds “three zeros” to cheap hardware.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:36The Queensland Functional Programming Lab
- 3:53Logbooks
- 11:16Aeronautical Data Information
- 11:26Civil Aviation Safety Regulations Section 175
- 14:03Electronic Maps
- 14:40Map Projections
- 17:57Controlled Flight into Terrain
- 19:14Vfr
- 22:56Principles on Weight and Balance
- 32:06Automated Traffic Collision
- 35:20Cost of Avionics
- 38:11Traffic Collision Avoidance
- 39:03Questions
- 53:04Set the Barometric Pressure on the Altimeter
related talks
01h 14mFunctional Programming in F#: Fad or Fabulous?
46mFunctional programming in F# Fad or Fabulous
58mKeynote: Why Functional Programming Matters
56mFunctional Programming with JavaScript
54mQ & A Session With Functional Conf Speakers
41mFunctional programming: Give it a chance!
39mFunctional Programming And the Real World
49mFunctional Programming Essentials