VFRnav Checklist File Format
Short name: VFRCL
Version: 1.0
Status: Feb 2026
1. Purpose
The VFRCL format is intended for the simple exchange of flight checklists for use in VFRnav.
It is text-based, human-readable, versionable and allows structured checklists with metadata, colors and subheaders.
2. General properties
- Text file (UTF-8)
- Line-based
- Order of entries is significant
- Blank lines are allowed and ignored
3. Comments
Comments start at the beginning of the line with:
; Kommentar
# Kommentar
Exception:
##denotes a subheader (see section 6)
4. Metadata
Metadata is defined with @:
@key = value
4.1 Global metadata
Global metadata appears before the first section and applies to the entire file. Valid global metadata: @format, @lang, @aircraft, @author
Examples:
@format = vfrnav checklist v1
@lang = de
@aircraft = C172
@author = Hermann
4.2 Section metadata
Metadata defined within a section applies only to that section.
Valid metadata for sections: @color
Examples:
@color = #E0E0FF
5. Sections
Sections define major parts of the checklist.
Syntax
[Name der Sektion]
Example:
[Vorflugkontrolle]
6. Subheaders
Subheaders serve the visual and logical organization within a section.
Syntax
## Titel der Unterüberschrift
Example:
## linkes Hauptfahrwerk
- Subheaders always belong to the current section
- They do not have their own metadata
7. Checklist items (Items)
Checklist items consist of label and value.
Syntax
Bezeichnung = Wert
Example:
Fahrwerk = Sichtprüfung
Rules
- Separator is the first
=in the line - Whitespace around
=is ignored - Labels may appear multiple times
- Order is preserved
- Values may contain special characters
8. Multiline values
Multiline content can be defined using a pipe symbol |.
8.1 Escape sequence (minimal)
Verbrauch = 16 L bei 170 km/h | 13 L bei 150 km/h
9. Colors
Sections can optionally have a color.
@color = #RRGGBB
10. Validity rules
- Metadata (
@...) apply until the next applicable scope - Items outside of sections are invalid
- Subheaders outside sections are ignored
- Parser is tolerant of unknown
@keys
11. Minimal example
@format = vfrnav checklist v1
@lang = de
@aircraft = C172
[Vorflugkontrolle]
@color = info
## Rumpf
Rumpf = Sichtprüfung
Antennen = OK
[Start]
@color = warning
Gashebel = Vollgas
Drehzahl = prüfen
12. Backward compatibility
- New metadata may be added
- Unknown metadata must be ignored
- Structure and syntax of v1 remain stable