Contact
Questions, bug reports, and especially corrections to aeronautical data.
chiptang211 gmail com
Reporting something that looks wrong
Data errors are the most useful thing you can send. If something does not match the official source, please include:
- The airport or route involved.
- What you saw, and what you expected.
- Roughly when — so it can be matched against the data cycle in force at the time.
- A screenshot if you have one.
- Whether you were on the website or the iOS app, and online or offline.
If something is unsafe, report it to the source too. Charting and procedure errors should go to the FAA as well as to me — I can fix how this app displays the data, but only the FAA can fix the data itself.
Corrections to the written material
The 75 pages under Learn and the how-to guides are as welcome a target as the data, and a different kind of error lives in them: a technique described in a way the FAA handbooks do not support, a regulation cited to the wrong section, a number that belongs to one airplane presented as if it were universal, or a maneuver written as solo practice when it is one an instructor demonstrates.
Those are worth reporting even when you are not certain. Name the page and quote the sentence, and say what you believe the correct answer is and where it comes from — a handbook chapter, an AC, or the section of 14 CFR. Corrections that change what a page teaches are made against the source and the page says who wrote it, so they get routed to the right person rather than patched over.
Feature requests
Welcome, though the bar is deliberately high for anything that adds clutter to the map. Requests that come with a description of the situation you were in when you wanted the feature are much more likely to get built than requests that name the feature alone.
Security
If you find a security issue, please email rather than filing it publicly, and give a reasonable window to fix it before disclosing.