At nearly every airfield I visit: Some pilots stick to paper others go fully digital—but too often, checklists are neglected, outdated, or inconsistent between media types. The result? Pilots improvise their own procedures—distracting, inconsistent, and unsafe.
That’s why I built checklists: a modular toolkit to author once in YAML and generate both printable PDFs and ForeFlight checklists.
Less media break, more safety!
Hej I’m Sophie, a private pilot and a bit of a checklist nerd. After seeing too many wrinkled and outdated checklists in the cockpits, I decided to bring some engineering love to this topic.
That's how the first iteration of checklists, based on preamble.inc, was born some years ago. It ultimately evolved into a this YAML centric toolkit, and yes, you could use it for stage management, groceries or coffee brewing as well. 🙃
"YAML may seem ‘simple’ and ‘obvious’ when glancing at a basic example, but turns out it’s not. The YAML spec is 23,449 words; for comparison, TOML is 3,339 words, JSON is 1,969 words, and XML is 20,603 words."
https://www.arp242.net/yaml-config.html
Garmin Pilot and Avionics support is already on the roadmap to extend compatibility further.
- replies
- 0
- announces
- 0
- likes
- 0
@sophie
Is there a possibility to distinguish follow-up checklists/items (done by heart, then checked after, they are usually boxed, as in the example) from read & do items?
In some Non-Normal-Checklists you have a memory-item part, and the rest is read & do. E.g. cabin altitude warning puts on oxygen masks and establishes the emergency descend by memory and then continues with troubleshooting of the outflow valve/packs in the read & do part.