Have questions about AeroScope? Need help with the platform? Interested in research collaboration? We are here to help.
For general inquiries, support, and feedback:
We typically respond within 48 hours.
Having trouble with the dashboard, API, or WebSocket connection? Let us know what you are experiencing, including your browser version and any error messages. Screenshots or console logs are always helpful for debugging.
Academic researchers looking for data access, collaboration opportunities, or assistance with using AeroScope for studies. We are happy to discuss your research needs and how AeroScope data can support your work. Include your institution and research topic.
Found a bug? You can report issues directly on our GitHub repository for faster tracking and resolution. Please include steps to reproduce the issue, expected behavior, and actual behavior. GitHub is the preferred channel for bug reports.
Have an idea for a new feature or analysis module? We welcome suggestions from the community. Describe the use case, what you would like to see, and how it would improve your workflow. Feature requests can also be filed on GitHub.
Interested in integrating AeroScope data into your product, or exploring partnerships for joint development? Reach out with details about your organization and how you envision a collaboration.
Questions about data collection, privacy practices, or requests related to your personal data. Please refer to our Privacy Policy first, then contact us if you have additional questions or concerns.
AeroScope is developed as an open-source project. The source code is available on GitHub:
GitHub Repository:
We are a small team and appreciate your patience. Typical response times:
AeroScope is maintained by one researcher, so a note that says what you need tends to get a far better answer than a general enquiry. A few things worth knowing:
| If you are writing about | Please include |
|---|---|
| A bug or wrong data | The aircraft hex or callsign, roughly when you saw it, and your location or the map area. Without an identifier a report usually cannot be reproduced. |
| API or MCP access | What you are building and roughly what request rate you expect. Most read-only use needs no special access, see API docs and MCP. |
| Research or the dataset | What you are studying. The benchmark is CC-BY 4.0 and freely downloadable from the research page without asking. |
| A security issue | Please use the process on the security page and report privately before any public disclosure. |
| Feed attribution or removal | Which network you operate. Attribution changes and removals are actioned, see data sources. |
Replies are best-effort rather than guaranteed, and support is not a paid service. Please do not send anything you would consider confidential.