Contribute a checklist

The most valuable file in this library is the one written by somebody who actually owns the aircraft. If you have a heavily modified experimental, or a Part 103 machine that came with no manual at all, nobody else can write your checklist.

The quickest route

1. Open the editor. Start blank, or fork a checklist for the same airframe.
2. Fill it in. It saves in your browser as you go, so you can come back to it.
3. Download the .ocl.json file.
4. Open a pull request adding it to examples/ in the repository, or send it to the address on the contact page.

Automated checks run on every pull request: the schema, the corpus policy rules, and the export contract. You will get told what is wrong rather than left guessing.

What makes a contribution useful rather than noise

• Say what your aircraft actually is. Record the engine, and every modification that matters — swaps, prop changes, panel rebuilds, gross weight increases. This is what makes your file findable by the next person with the same setup, and it is the whole point of the airframe family grouping.
• Say where the content came from. Your own aircraft? A kit manual? A published handbook? "Unknown" is an honest answer and a usable one; a wrong answer is not.
• Do not invent numbers. If you do not know the correct airspeed or RPM, leave it out. An omitted limitation is a gap; a confidently wrong one is a hazard. Files here deliberately omit values rather than guess them.
• Write the wording yourself. Copy the facts — which control, which position, which value, in which order — but do not reproduce a manufacturer's prose, section titles or arrangement.
• Say what you changed, if you forked. The most useful sentence in a derived checklist is the one explaining what the modification forced.

Contributor warranty

By contributing you confirm that:

1. you have the right to submit the content, and doing so breaches no agreement binding you;
2. you have accurately stated the source document and how the content was produced;
3. where you claim public domain status, you state the basis and what you checked;
4. you have not copied wording, selection or arrangement from a copyrighted source beyond what the file declares;
5. you understand the file will be redistributed under the licence it states, and that the project makes no warranty of fitness.

Your name stays attached to the file. That is deliberate: provenance is the point, and a file nobody stands behind cannot be assessed. A pseudonym is fine.

What your file will be marked as

Everything arrives as authored, not reviewed, not airworthy — and that is not an insult, it is accurate. Verification is earned by somebody else comparing your file against its source, or walking it through the cockpit. You cannot claim it by writing it, and neither can anyone else.

Read how to read a file for what the states mean.

Reporting a problem with an existing file

Include the file's id, its content hash from the bottom of its page, the item you are talking about, what it says now, what it should say, and what you checked against. A confirmed error automatically strips the file's verification badge.

What we cannot accept

• Scans or copies of a manufacturer's manual, or files copied wholesale from another checklist site — several forbid it in their terms.
• Flight-simulator documentation. It is copyrighted by the sim vendor and it is not airworthiness data, however convincing it looks.
• Files with no stated provenance at all. If nobody can tell where it came from, nobody can check it.