Open Checklists

Free checklists for every type of aircraft and pilot.

Takedown and corrections

Designed before it was needed, which is the only time it can be.

If you hold rights in something here

Write to the address on the contact page. Tell us which file, and what your claim is. You do not need a lawyer and you do not need to use any particular form of words.

What happens

  1. We acknowledge within 72 hours and tell you what happens next.
  2. We unpublish first and argue afterwards. On a good-faith claim the file comes off the site and out of the bundles immediately. The cost of a checklist being unavailable for two weeks is low; the cost of a contested file staying up is not. Nothing is destroyed — the project's history is public, so unpublishing is reversible.
  3. We assess it against the project's published rights rules.
  4. We record the outcome publicly: what was claimed, what was decided and why. That log is how the project learns where the line actually is, and it makes every later claim cheaper to handle.
  5. We notify the contributor, who may respond. Their contributor warranty is what makes this a matter between you, the project and them, rather than the project alone.
  6. We fix the class, not just the instance. If one file was wrong about its source, others from the same contributor and the same document are suspect too.
  7. Nothing is restored silently. A restoration gets its own public log entry.

If you have spotted an error

That is a different and more common thing, and it is the mechanism this project runs on. Every file has a content hash, so a report can be tied to the exact version you were reading. File a report saying what the file says, what it should say, and what you checked against.

A confirmed transcription error or stale item automatically costs that file its verification badge — the tooling refuses to let a file keep a review claim over content now known to be wrong. You do not have to argue anyone into it.

See contribute for how to file one.

If you are a manufacturer or type club

We would rather work with you than around you. The project can do something your own PDF distribution cannot: mark every derived copy stale the day you publish a new revision, and tell anyone holding an old one that it is out of date. Every file records the revision it came from and links to you as the canonical source. If you would prefer a file removed, say so and it goes — but the offer to keep your revisions propagating stands either way.