Corrections
When we get it wrong
Instajet publishes figures about a market where most numbers circulate without a source attached. Some of ours will be wrong. This page sets out how to tell us, what we do about it, and what we have had to change so far.
Corrections go to corrections@instajet.ai, which is a monitored address kept separate from general enquiries so a correction is never triaged behind a press request.
Process
What happens when you report one
Four steps, in order. Nothing here is aspirational — each step is something an editor does before the next one can happen.
01
You tell us what is wrong
Write to corrections@instajet.ai with the article URL, the specific claim you are disputing, and — where you have one — the source that settles it. The source is not a formality: it is the same check an editor has to run before anything can change, so supplying it is the difference between a correction made this week and one made when somebody has time to research it.
02
We check it against the sources on the article
Every article lists the sources it was written from. The first thing an editor does is read the disputed claim back against those sources. That establishes one of three things: the article misread its source, the source itself was wrong, or the article is right and the report is not.
03
The article is amended, or it is not
If the claim does not hold, the article is corrected in place. It keeps its URL — a corrected article that moves is a corrected article nobody who read the original will ever see — and its modified date updates, which propagates to the sitemap so the corrected version is what gets re-crawled. If the claim does hold, you get a reply naming the source we are relying on, so you can tell us if that source is the problem.
04
The change is logged here
A substantive factual correction is recorded in the log below: what the article said, what it says now, and why it changed. The record is written at the same time as the change rather than afterwards, and it does not expire.
Scope
What counts as a correction
Stated explicitly, because the boundary is where a corrections log gets quietly emptied.
- Logged as a correction
- A figure that was wrong. A claim attributed to a source that does not support it. A name, a date, an aircraft type or an operator that was misidentified. Anything a reader could have acted on and been misled by.
- Not logged
- Typographical fixes, broken links, formatting, and rewrites that do not change a factual claim. These still update the article's modified date, but logging them here would bury the corrections that matter under noise — which is its own way of hiding them.
- Handled differently
- A piece an editor has read and does not stand behind is marked flagged, which is visible on the article itself, rather than being quietly unpublished. Removing a piece from the archive is a last resort and leaves an entry here saying so.
The log
0 corrections on record
Every substantive factual change made to a published article, newest first. Read from the database, not maintained by hand.
Nothing logged yet
No published article has needed a factual correction so far. This section is here before it is needed rather than after, so that when the first entry appears it arrives in a log that already existed. If you have found something that belongs here, the address at the top of this page is the way to say so.
Related
How articles are produced in the first place
The editorial policy sets out where sources come from, where a language model does the drafting, and what an editor has to do before a piece can be marked as checked. Most corrections are traceable to a step in that process, which is why the two pages are written to be read together.
Ownership, funding and the rest of the contact routes are on the contact page.