FS2004 (FS9) Updated Sun, 20 Sep 2026 05:17:23 GMT 6 min read

How do I create and use a custom checklist in FS2004?

By Ian StephensEditor-in-Chief

In short

Create and use a custom checklist in FS2004: set up the .htm file, edit aircraft.cfg, open the kneeboard and fix blank or missing checklists.

To create a custom checklist in Microsoft Flight Simulator 2004 (FS2004/FS9), save a simple .htm document in the aircraft’s folder, set that livery’s kb_checklists entry in aircraft.cfg to the filename without its extension, reload the aircraft, then open the kneeboard and select Checklist.

How do I make an FS2004 checklist file?

The safest method is to copy a working FS2004 checklist, rename it and replace its contents with procedures for the aircraft you fly.

Find the aircraft folder and make a backup. The folder containing the relevant aircraft.cfg is normally beneath Flight Simulator 9\Aircraft\<aircraft folder>\. Copy aircraft.cfg somewhere safe before editing it.
Create the checklist file. Copy an existing file whose name ends in _check.htm, or create a new plain-text file such as myaircraft_check.htm. Enable filename extensions in Windows and confirm it has not become myaircraft_check.htm.txt.
Use simple HTML. FS2004 relies on an old HTML renderer, so basic headings, paragraphs, lists and tables are more dependable than scripts, external assets or elaborate styling. A minimal file can contain <html><body><h1>Checklist</h1><h2>Before start</h2><table><tr><td>Parking brake</td><td>SET</td></tr></table></body></html>.
Identify the livery you use. Open aircraft.cfg in a plain-text editor and find its corresponding [fltsim.x] block. The ui_variation= and texture= entries usually make the correct repaint easier to identify.
Add the checklist pointer. Add or replace kb_checklists=myaircraft_check inside that [fltsim.x] block. The value must match the checklist’s basename, but must not include .htm. Remove duplicate kb_checklists lines rather than leaving conflicting entries.
Cover the other repaints. Several liveries in the same aircraft folder can use one checklist file, but each applicable [fltsim.x] block should contain the correct kb_checklists entry.
Reload the aircraft. Reselect it in FS2004 or restart the simulator. This forces FS9 to read the changed configuration and checklist.

If FS2004 is installed in a protected Windows folder, an editor may deny the save or write to a redirected copy. Check the modified date of the actual aircraft.cfg and checklist beside the aircraft files; editing a copy elsewhere and then copying it back is often clearer.

How do I open and use the custom checklist in FS2004?

Open the kneeboard with the default Shift+F10 shortcut, then select its Checklist tab.

If that shortcut does nothing, use FS2004’s Kneeboard menu command or check whether the keyboard assignment has been changed. For an unfamiliar aeroplane, work through startup items as read-and-do actions; during routine flight, complete a memorised flow and use the list to verify it. Our guide to choosing and using a simulator checklist by flight phase explains the distinction.

The stock kneeboard does not record which items you have completed. Keep each line short enough to scan without losing your place, and divide long procedures into clearly labelled phases.

What should an FS2004 aircraft checklist contain?

A useful FS2004 checklist contains concise, aircraft-specific action-and-result pairs arranged in the order they are performed.

Cockpit preparation or pre-flight
Before start and engine start
Before taxi and before take-off
Climb, cruise and descent
Approach and landing
After landing and runway vacated
Shutdown and securing
Accurate abnormal procedures, if the add-on models the relevant systems

Prefer entries such as “Fuel selector — BOTH” and “Flaps — SET” over paragraphs copied from a manual. A mistake we see constantly is combining a real aircraft checklist with an add-on whose switches, engine logic or available systems differ. Check every item against the model installed in FS2004.

For a worked example of phase-based organisation, examine this A320 checklist arranged from cold-and-dark through shutdown. Its procedures still need to be adapted before being placed in a kneeboard HTML file.

Should speeds and limitations go in the Checklist or Reference tab?

Put ordered procedures in the Checklist tab and stable operating data in a separate Reference document.

`aircraft.cfg` entry	Kneeboard tab	Best use
`kb_checklists=myaircraft_check`	Checklist	Actions performed in sequence by flight phase
`kb_reference=myaircraft_ref`	Reference	Speeds, limits, weights, power settings and operating notes

Create myaircraft_ref.htm beside the checklist and add kb_reference=myaircraft_ref to the relevant [fltsim.x] entries. As with the checklist setting, omit the file extension in aircraft.cfg.

Why is my custom checklist blank or missing?

A blank or missing FS2004 checklist usually means the filename does not match, the wrong repaint block was edited or the HTML is too complex for the kneeboard renderer.

Check the real extension: the file should end in .htm, not .txt, .html or a hidden double extension.
Compare the basename: myaircraft_check.htm must be referenced as kb_checklists=myaircraft_check.
Inspect the selected repaint: changing only [fltsim.0] will not necessarily affect an aircraft selected from another [fltsim.x] block.
Use the correct folder: keep the checklist beside the aircraft.cfg that refers to it.
Remove duplicate settings: leave one unambiguous kb_checklists line in each affected block.
Simplify the HTML: replace Word-generated markup, scripts and complex formatting with a heading and one plain paragraph. Add the remaining content back only after that displays.
Verify the saved files: protected-folder permissions can leave the original files unchanged even though an editor appeared to save them.
Force a reload: close and reopen the kneeboard, reselect the aircraft or restart FS2004 after editing the configuration.

Can FS2004 tick checklist items automatically?

No. The standard FS2004 kneeboard displays an HTML document but does not read cockpit switch positions, recognise completed actions or operate aircraft systems.

HTML checkboxes may appear clickable, but their state is not dependable after reloading the page or aircraft. Complex add-ons may provide a separate panel-based checklist or virtual first officer; changing kb_checklists does not modify those systems.

If the checklist begins with every system shut down, pair it with our practical FS2004 cold-and-dark startup sequence, then adjust the order for the switches and systems modelled by your aircraft.