Actually, you're fast! I just happened to notice that I had a new version as of yesterday so I re-imported my old data to see if it included you're new work , and it did. And then I actually just logged back in to mention the other data which I just found time to investigate and find missing, and to which you've already responded! (I wasn't sure if I lead you to believe that I only wanted the frequencies earlier, I actually just included the snippet for them because darkm20 had included the whole thing). So:
I cannot speak for all pilots of course, but I can give you some basic info and you can maybe tell me what works from your side. I've just started trying to use Locus in place of a full Aviation GPS in some of the smaller aircraft I fly (I think your interface is hands-down better than what the older GPS offerings have, and I can use it for hiking etc). I have several comments about interface items in general, but I'm not very familiar with Locus yet and I feel that you may have covered many of them in features I've not yet explored so I'll stick with this importing for now.
Looks like you have this already:
These two would be very useful:
One of the nicest things this data is gaining us is the ability to tell if an airport is an option to land at and get fuel. If a pilot is using the aviation charts Locus can read they'll already know if fuel services are available, but it's also nice to overlay these points on a cleaner (Mapquest roads) map at times. If you find in-flight that your fuel gauges are somehow inaccurate, or you've had to alter your flight plan, knowing where you can get fuel is quite convenient (especially since landing to find out wastes so much time and fuel).
Pilots in the us are required to have a current (annual) airport directory with them, the database that we download from for this data is at least nice enough to tell us when something was last updated. This won't meet standards to allow us not to carry the Airport Directory, but knowing that the info is over a year old would be quite helpful (and extra nice if there were some way to highlight the date in red if it were old, but I think this is probably not so useful for generic data importing so may not work so well unless you are converting the data to HTML or similar as you import it).
<navaid:runway designation="09/27" length="3199" width="75" surface="ASPH-G">
Knowing you can get fuel etc is nice, but knowing the length of the runway is just as important in deciding if you should/can land and take back off safely.
Less useful, lower priority from my standpoint:
<navaid:beginning lat="42.775284" lon="-84.735962">
<navaid:ending lat="42.775961" lon="-84.724082">
The problem is that this data is included for the beginning and ending of each runway, useful, but sort of makes you import all of it for only small gains (headings are approximated by runway numbers 09 = approx 90, 27 = approx 270 etc). I suppose if you're willing to import it that's great, but its' not as important as the other stuff. Knowing that a runway has a large slope is nice, but I'm not sure that seeing these numbers will help that be easily noticed anyway.
<navaid:frequency type="MISC" frequency="118.650" name="APCH/PDEP/P"/>
<navaid:frequency type="OPS" frequency="122.700" name="OPNS"/>
<navaid:frequency type="UNIC" frequency="122.700" name="UNICOM"/>
You've already done these (thanks again!). Before landing, and really when in the vicinity, it's customery for VFR pilots to announce their positions on the CTAF or unicom frequency. Airport tend to have more planes around than areas without airports and it help everyone to find eachother. The other frequencies are useful too and I can explain them if you're interested, but you've already imported them in a very useful way so I won't go further for now.
Okay, that' sit for now, out of time. As I get better with Locus I'll try to give you more information about my other ideas where they apply to flying and other hobbies for which maps are useful. I don't see where darkm20 gave you general thought about Locus for aviation, if he's done so already and there is somewhere I can see it I'd be interested to way in and also not to duplicate his work.
As a side note I'm the head of a small software team (3 of us, mostly windows development and our own PLC-like hardware for controls) we'll be working on Android apps for our customers within the next year or so. At which that I become more familiar with Android I'd be happy to help on this project if there is anyway I can be of use. I had actually planned on writing a mapping application which would allow taking a photo of a topo or any to-scale map and then mapping it to gps coordinates, which it appears Locus already does so you've already saved me some work on 1 hobby project anyway!