FlightBank is run by one person in the UK, so replies are not instant — but every message is read. Expect a response within a few working days.
What to get in touch about
Data corrections
Aircraft type, operator or photo information comes from public databases and is sometimes wrong. If you spot an error, send the hex code of the aircraft if you can — it identifies the airframe uniquely and makes the correction far quicker than a callsign, which changes daily. Our guide on reading the radar explains where to find it.
Receivers and feeding
Questions about building a receiver or contributing coverage. The receiver guide answers most of them, but if your situation is unusual — awkward siting, poor range, an antenna that should work and does not — do ask.
Privacy and data requests
Any request under UK GDPR, including access to or deletion of your data, goes to the same address. These are answered within one month, as set out in the privacy policy.
Corrections to the guides
If something in the guides is wrong, out of date, or misleading, please say so. Aviation is a field where a lot of people know more than we do about some specific corner of it, and corrections are welcome.
Anything operational or urgent. FlightBank is an enthusiast service with no connection to NATS, any airport, airline or air traffic control organisation. We cannot help with flight status, delays, bookings, noise complaints or anything requiring an official response — and we have no ability to act on a safety matter. If something is genuinely urgent, contact the relevant authority directly.