Editorial Policy

We report on what is happening in flight simulation: releases, updates, announcements, previews and events. Every news article is based on a source that we can point to, and we follow these rules:

1. Named sources. We link to the original announcement, whether it is a developer’s website, forum, social media post or Discord server. If a company sent the information directly to us, we say so.
2. Facts from the source. Features, prices, dates and compatibility come from the developer or the store, not from guesswork. If something is not confirmed, we say that it is not confirmed.
3. Rumours and leaks. We do not present speculation as fact. If we report on unconfirmed information at all, it is clearly labelled as such.
4. Our own words. We do not copy press releases. We rewrite the information and add the context that helps you understand why it matters.

We choose what to cover based on what is interesting to our readers, not on who advertises with us.

Our Originals, including editorials, guides and interviews, give our writers space to share their own views and experience. These articles are published under the author’s name and represent the opinion of the author, which may differ from the opinion of other team members. They are kept in their own sections of the site, so you can always tell them apart from news.

Our editorial team decides what we publish. Advertisers, partners and developers do not. Paying for an advertisement does not buy coverage, a review or a kinder tone. Paid articles are rare, are never reviews, and are always clearly marked. You can read more about how we earn money in our Advertising & Monetization Transparency document.

Members of our team who have a personal or business relationship with a developer do not cover that developer’s products. If such a relationship cannot be avoided, we disclose it in the article.

We make mistakes. When we do, we fix them openly:

1. Corrections. If an article contained a factual error, we correct it and add a note explaining what was changed.
2. Updates. If new information arrives after publication, we add it and mark the article as updated.
3. Small fixes. Typos and formatting issues are fixed without a note.

We do not quietly delete articles to hide an error. If you spot something wrong, please tell us through the contact form, on our Discord server, or at hello@fsnews.eu.

Screenshots and images in our articles come from the developers, from our own team, or from sources that allow us to use them. We credit the source where it is known. If we have used your work and you would like it credited differently or removed, get in touch and we will sort it out.