New glasses

I got new glasses on Tuesday. I had reading glasses before, but I hardly ever wore them because until recently I didn’t need them unless the light wasn’t very bright. There were only two times I really felt the need – when I was reading in bed, and when I was trying to plug something into the back of a computer. Plus they gave me horrible eye strain if I looked through them at distant things. My eye doctor recommended that I get those no-line multi-focus lenses, because then I could keep them on all the time and they’d be there when I needed them, plus there would be one part of the lens that was good for up close stuff and another part that would be good for computer screens.

Ok, two days on, here are my impressions:

  1. They do fulfil the promise of something I could keep on all the time, so they’re handy when I need them.
  2. There are some things that don’t fit the multi-focal glasses paradigm of “close things are down low, far things are up high” – the one I notice most is the wing mirror on my car.
  3. I’ve got to learn to ignore them, because I think I stare when I’m looking through them. A few hours and my eyes get really dry.

Also, I was walking into work yesterday and I thought something was wrong with my iPod – there was a large dark area on the screen. A little while later, sitting at my desk I looked and was releived to see it was no longer there. And then l saw it again on the way out to the parking lot. That’s when I realized that the clip-on sunglasses that came with the glasses are polarized. D’oh!

Hating re-routes, part II

I woke up this morning at was shocked to find it was raining. This was a total surprise to me, as I thought the forecast was for more sun. This was a huge disappointment, because I’d decided that I’d prevent New York controllers from giving me a half hour ground hold or re-routing me all over hell’s half acre by flying VFR.

Fortunately, while it was raining all over most of southern and eastern New York and New Jersey, it was all layered stratus clouds so no thunderstorms. So it would be IFR, but flyable IFR. That’s good.
Continue reading “Hating re-routes, part II”

LazyWeb: Slow DNS lookups on MacBookPro?

Vicki complains that sometimes she can’t ssh into my Linux box (foo.xcski.com) from her MacBookPro. This morning she said it was happening again, and when I looked on her system “host” and “dig” couldn’t get an address for it, while at the exact same time, my Powerbook got the right address just about instantaneously. A few minutes of poking around and not doing much, it suddenly started getting results again, and she was able to ssh in.

We have exactly the same DNS settings – two DNS servers, 192.168.1.1 is the local one that knows how to find *.xcski.com servers, and 192.168.1.254 is the DNS server on the wireless router which probably just redirects to the ISPs DNS servers.

I’ve never had any problems with DNS lookups on my Powerbook. So why is she getting these problems?

Friday’s lesson: Don’t make your weather decision without looking at the sky

I nearly didn’t make the flight up to Toronto for the Pilot Blogger weekend. There wasn’t anything on the radar, and the TAF (Terminal Aerodrome Forecasts) were talking about a 40 percent probability of isolated thunderstorms, which is pretty normal for this time of the year. But at decision time, the METAR (current conditions) at Rochester were:

KROC 131554Z 25011G17KT 10SM BKN037TCU BKN070 22/12 A2993 RMK AO2 SLP132 TCU SE CB DSNT N T02110111

Now, I’m not great at reading all the “RMK” (remark) part of the METAR, and that’s where the scary stuff was. All I know is that “TCU” means “Towering Cumulus” and “CB” means “thunderstorms”. And I went to the decoded report on DUATs, and it said that the “TCU”s were in all quadrants. So I thought I’d be flying IFR, dealing with the extreme turbulence of TCUs while out over the lake, and thought that wasn’t a good situation to be in. So I told people I’d be driving instead.

And then I walked outside. One odd thing about Rochester is that the airport is south of the I490 highway, and there is frequently a real difference in the lake-affected weather up north of I490 and the mainland-affected weather south of it. So I walked outside and looked up and north to see scattered clouds and bright sunshine, and then looked south towards to airport to see some of the TCUs the forecast was talking about, but mostly to the south of the airport. And suddenly realized that if I were to depart VFR, I could dodge the TCUs until I was in the lake-effected weather, and have no problems following the lakeshore around to Toronto.

I haven’t done a VFR flight into Canada in a while, so I had to dust off those old memories. But I managed to get all the appropriate paperwork all done, and didn’t cause any international incidents. (Not so on the flight home – as I type this I realize I forgot to close my flight plan, so I’m calling right now. Can I just mention for the record that I wish US controllers would open and close flight plans the way Canadian ones do?)

When I took off, as soon as I got turned over to departure control, there was a gigantic rain shaft about 5 miles in front of me, and I was about to tell him I was going to turn north because of it when he pointed it out to me and gave me a vector. But 5 miles later I was at 3,000 feet in sunshine, mostly smooth air, and I could see across the lake.

The lakeshore is a lovely flight, and Toronto gives me flight following around, but requires me to stay out of their airspace, which means descending into mild turbulence and staying lower than I’d really like to. But the flight was fun and I’m really glad I got to fly.

Hey, you know those distractions? They’re very distracting.

I thought I had no problems with distractions. After all, I’m a highly trained and experienced pilot, and when I was a student pilot my instructor had spent a fair amount of time making me deal with distractions. But today I was taking some friends out flying, and just as we were leaving the class C airspace I noticed a bit of a strange noise – and I looked over and realized the door wasn’t latched at the top. I unlatched the bottom to try and get it re-shut, but it wasn’t possible to get it closed. I slowed the plane to 80 knots and tried to get the passenger to close the door, but he couldn’t do it. Unlike the club’s other aircraft, the Lance doesn’t have a strap you can yank on to pull the top of the door closed, so neither of us could get it properly latched.

Now you and I both know there is nothing wrong with having the door open except for the breeze and noise, and the potential for having your charts whisked out of your hand at a bad time. But I didn’t want to do a two hour scenic flight with all that noise and wind, especially not with people who’d never flown before.

Fortunately, Ledgedale Airpark was about a mile off my right wingtip. So I told Rochester departure that I’d be making a landing there, and did a 180 degree turn to enter the pattern. But I was having a terrible time in the pattern. The winds at Ledgedale down low were gusty as hell. But I can’t blame the horrible pattern I flew entirely on the gusts – my speed and glide slope control was ridiculous. I heard the stall horn a few times, I got the “Landing Gear Unsafe” light a few times before I put the gear down as I horsed the throttle around overcorrecting altitude and speed excursions. I was so low on final I had to put in full throttle so I wouldn’t touch down a dozen feet short. And then my landing was, to put not too fine a point on it, a bit firm. I must have let the door distract me. And that’s not good.

I guess it’s time to spend some time with an instructor re-learning how to deal with distractions.