Step by step

  1. Open ChatGPT, Claude or Gemini

    The free version works, on the web or in its app.

  2. Attach the checklist

    Use the attach button (paperclip or +) and choose your aircraft's checklist, usually a PDF; other documents work too.

  3. Copy the prompt and paste it

    Tap “Copy prompt” below, paste it in the chat with the checklist and send it.

  4. Save the XML on your phone

    If the AI gives you a .xml file, download it and save it on your phone, for example in Downloads. If it can't create files, copy the whole answer, from <?xml to </aircraft>, paste it into a text editor app and save it with the .xml extension.

  5. Import it into the app

    In the app, go to Aircraft › + › Import XML file and choose the file you saved.

  6. Review the checklist in the app before using it

    Compare it with the flight manual and the aircraft's official checklist. Why this matters.

The prompt

Copy it as is. It includes the format the app understands and rules so the AI does not make up data.

Prompt for the AI
Convert the checklist in the attached document into XML to import into an Android checklist app.
If you can create files, deliver it as a downloadable .xml file. Otherwise return ONLY the XML, with no explanations or code blocks.
If it is too long for one answer, split it and wait for me to say "continue".

Format:
<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<aircraft>
    <name>Model and registration</name>
    <comment>Short general info (optional, one line)</comment>
    <checklist_group>
        <name>GROUP NAME</name>
        <color>red</color>                  <!-- optional -->
        <checklist>
            <name>CHECKLIST NAME</name>
            <comment>Short note (optional)</comment>
            <read>false</read>
            <task>
                <name>ITEM</name>
                <result>ACTION OR VALUE</result>
                <comment>Item note (optional)</comment>
                <color>amber</color>        <!-- optional -->
                <state>BLANK</state>
            </task>
        </checklist>
    </checklist_group>
</aircraft>

How the app shows things (important):
- A checklist <comment> is shown in full on the checklist card, so keep it SHORT
  (max ~60 characters, e.g. "POH 4-5" or a one-line subtitle). Never put long text there.
- A task <comment> is shown in a dialog behind an (i) button and keeps line breaks.
  Long text goes there, with paragraphs separated by a blank line.
- Valid colors: red, amber, blue, green, grey.

Rules:
- Groups as in the document, e.g. REFERENCE, NORMAL PROCEDURES, EMERGENCY PROCEDURES
  (<color>red</color>), ABNORMAL PROCEDURES (<color>amber</color>), PERFORMANCE.
- Each procedure is a checklist; each "item ... action" line is a task.
- Use the same language as the document. Copy values, speeds and RPM exactly;
  do not invent or fill in data that is not in the document.
- Join lines that the document breaks mid-sentence. Drop figure/diagram garbage text.
- Introductory text and NOTEs before the first step: one task at the start,
  name "NOTE", result "READ", the text in its <comment>.
- Every WARNING or CAUTION: its own task in the place where it appears,
  name "WARNING" or "CAUTION", result "READ", text in <comment>,
  color red for WARNING and amber for CAUTION.
- NOTEs or explanations that come after a step go in that step's <comment>.
- Memory items: start the task comment with "MEMORY ITEM".
- If a procedure has sub-cases or conditions ("If it does not start", "After deployment",
  "Main gear / Nose gear"), split it into separate checklists named
  "Procedure – Sub-case". Do not leave empty checklists.
- If a step has no action, add a suitable one (PERFORM, CHECK, MONITOR, INSPECT).
- Convert data tables into tasks (e.g. name "VNE", result "200 KIAS"; name "4,500 ft",
  result "23.5 IN HG"). Put the source page in the checklist comment, not in each task.
- A checklist with only text: one task "NOTE" / "READ" with the text in its comment.
- Escape &, < and >. state always BLANK and read always false.

XML format

Each file holds one aircraft with four nested levels:

aircraft › checklist_group › checklist › task

aircraft
The aircraft. It is the root of the file.
checklist_group
A group of checklists: normal procedures, emergency procedures, performance, reference…
checklist
A procedure: before starting, before takeoff…
task
Each line of the checklist: the item and what to do.

Inside each one:

name
The name: model and registration, group, procedure or item.
comment
Optional note. In a checklist it is shown on its card, so keep it short (e.g. the POH page); in a task it opens with the (i) button and can be long: cautions, warnings or notes.
color
Optional, only in checklist_group and task: red, amber, blue, green or grey. For example, red for emergency procedures and warnings, amber for abnormal procedures and cautions.
result
Only in task: the action or value (SET, 2,300 RPM, CHECK…).
read
Only in checklist: whether the checklist has been read. In a new file, always false.
state
Only in task: BLANK unchecked, DONE done. In a new file, always BLANK.

Example

<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<aircraft>
    <name>Example aircraft XX-XXX</name>
    <comment>Only to show the format</comment>
    <checklist_group>
        <name>NORMAL PROCEDURES</name>
        <checklist>
            <name>BEFORE TAKEOFF</name>
            <read>false</read>
            <task>
                <name>Parking brake</name>
                <result>SET</result>
                <state>BLANK</state>
            </task>
            <task>
                <name>Flaps</name>
                <result>AS REQUIRED</result>
                <comment>See takeoff table</comment>
                <state>BLANK</state>
            </task>
        </checklist>
    </checklist_group>
</aircraft>

Download full example XML

Tips and common problems

  • The AI cuts the answer short. If the checklist is very long, type “continue” and join the parts in order.
  • The app shows an error when importing. Ask the AI: “Validate that the XML is well-formed and fix it”.
  • Scanned PDF. PDFs that are images work worse. If you can, use a PDF with selectable text.
  • Another language. You can ask the AI to translate the checklist into another language.

Review the checklist before you fly

A checklist generated by an AI may contain errors. The pilot is responsible for checking it against the flight manual (POH/AFM) and the aircraft's official checklist before using it.

The app is an aid and does not replace the official documentation.

Get Aviation Checklist

Get it on Google Play