QRouting Software
EN

AviationChecklist · Guide

Convert your PDF checklist to the app

Turn your aircraft's PDF checklist into the app in 5 minutes with the help of an AI: ChatGPT, Claude or Gemini.

Go to the prompt Before you fly

Step by step

  1. Open ChatGPT, Claude or Gemini

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

  2. Attach the PDF checklist

    Use the attach button (paperclip or +) and choose your aircraft's PDF.

  3. Copy the prompt and paste it

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

  4. Save the XML on your phone

    Ask the AI: “Give me the XML as a downloadable .xml file” 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 Menu › Import aircraft (XML) 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 PDF into XML to import into an app.
Return ONLY the XML, with no explanations or code blocks.

Format:
<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<aircraft>
    <name>Model and registration</name>
    <comment>General information (optional)</comment>
    <checklist_group>
        <name>GROUP NAME</name>
        <checklist>
            <name>CHECKLIST NAME</name>
            <comment>Checklist note (optional)</comment>
            <read>false</read>
            <task>
                <name>ITEM</name>
                <result>ACTION OR VALUE</result>
                <comment>Item note (optional)</comment>
                <state>BLANK</state>
            </task>
        </checklist>
    </checklist_group>
</aircraft>

Rules:
- Group into checklist_group as in the PDF (e.g. REFERENCE, NORMAL PROCEDURES,
  EMERGENCY PROCEDURES, PERFORMANCE).
- Each procedure is a checklist; each "item ... action" line is a task.
- Use the same language as the PDF. Copy values, speeds and RPM exactly;
  do not invent or fill in data that is not in the PDF.
- Join lines that the PDF breaks mid-sentence.
- Notes, cautions and "read and do" go in <comment>.
- If a procedure has sub-cases ("if it does not start", "if it persists"), split it
  into several checklists or put the case at the start of the task name.
- If a line has no action, add a suitable one (DONE, CHECK, PERFORM).
- Convert data tables into tasks (e.g. name "4,500 ft", result "23.5 IN HG").
- Escape &, < and >. state always BLANK and read always false.
- If the text is too long for a single answer, split it and wait for me
  to say "continue".

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: cautions, warnings or “read and do”.
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.