Fun fact #143.4

Discovered while trying to debug my nav data loading scripts: The Hendersonville Airport (0A7) and the “W.N.C. Museum Airport” (8NC9) are only 0.03 nautical miles apart, but they’re separate airports. I’m not sure if they’re the closest two ever, but they’re certainly pretty damn close. As a matter of fact, I think this picture Hendersonville Airport from the AirNav.com web site listing for Hendersonville shows both runways, the paved one for Hendersonville and the turf one for the museum. I bet there is a story why they didn’t just build a taxiway between them and call it one airport.

I must have left my mind reading device in my other pants

The founder of the flying club is not the sharpest knife in the drawer when it comes to using technology. He just sent an email to the entire club with the subject line “Advertising” and the text “$82,000” followed by his name and a AOL banner. Now, unlike most of the club, I know he’s involved in trying to sell the club’s Lance, so I have a bare inkling of what he might possibly mean, but even I’m scratching my head wondering what the fuck he’s talking about. I wonder if that’s his asking price or an offer we’ve received or the reserve he’s going to eBay it under or what.

Personally, I think that there’s no way in hell we’ll get $82K for a 1977 Lance with a clapped out engine (2480 hours+) and prop and ancient avionics. But I suppose one can live in hope. Looking at Trade-a-Plane I can see a 1976 Lance with less TTAF (Total Time on Airframe) with only 875 hours on the engine and prop, and they’re asking $80K.

“Anticipated Separation”? I don’t like it.

The mission was to get two planes back from Batavia, one of which was the Lance. We tried on Friday and Saturday and Sunday, but the weather didn’t cooperate. The weather was fine today, but only two of us could make it, so we only managed to bring back the Lance.
Continue reading ““Anticipated Separation”? I don’t like it.”

Oh, bugger!

Ok, the big load job just finished, and it appears I was loading the old FAA data, not the data that became current on Wednesday. Also, it appears I have a bug in the code that loads the runways – the old scripts seemed to have taken “U” or “” for the runway end latitudes and longitudes as null, but the new ones are putting those values in as 0. Oops.

I guess I’ll have to run it again – using nohup this time. See you next week.