Flight Simulation Checklist Viewer. Available at https://checklist.eparker.me
Displays .csv files as checklists, with the functionality for:
- Different checklist groups (Before Start, Landing, etc)
- Items that require waiting/monitoring/confirming a certain item has been met, or that should be emphasised in the checklist
- Normal checks (Possibility to add item-by-item checking off in the future)
Checklists should be in the .csv file format, with one line per item. The file name should be the ICAO code of the aircraft (eg. PC9.csv). If there are multiple aircraft applying to one checklist, list all with a + between ICAO codes (eg. A320+A321.csv).
To identify the start of a new group, the first column of the line should be -GROUP-, and the second the title/name of the group (eg. Before Start, Landing, etc). These will begin a new block/group within the checklist, and the title will be coloured red and italicised.
To identify an item that should be emphasised, the first column of the line should be -INFO-, and the second the content (eg. Wait until NG is 90%, Check 3 Greens, etc). These will span across the width of the row, and will be italicised.
To identify a normal checklist item, the first column of the line should be the item (eg. LDG Gear Lever, COMM1, etc), and the second the state that is required (eg. DOWN, Tuned, etc).
It is also preferred that items that have an explicit value required (eg. ON, OFF, etc) are in upper case, and other items in sentence case (eg. As Required, Guarded, etc).
If you have any aircraft that aren't included here, you can simply make a checklist file for it, and attach the file to an issue. If you cannot create a checklist yourself, you are also able to request a checklist be made, by creating an issue.
If there is an error in a checklist, or you have a suggested alteration to a checklist, please either make a merge request with the fix, or create an issue.