Not a good flight

I went flying today. The “mission” was to deliver Paul P out to Batavia to pick up N9105X from its annual. The secondary missions were to see if the Lance, N43977 was still holding a charge from my flight two weeks ago, and could start itself, and also to get a bit of practice for my upcoming BFR.

I jumped in, hit the master, the fuel pump and moved the mixture up to prime, and hit the crank as quickly as I could. The Lance turned nearly two blades before the battery died, without catching. We hooked up the pre-heater cart battery same as last time, and as I discovered last time I needed to turn on the battery master to get both the cart battery and the Lance battery involved before it would turn over. It started pretty easily, but it sounded like it wasn’t hitting on all cylinders at first. It idled as I finished my pre-flight and office set-up and Paul P put away the pre-heater cart, by which time it was as smooth as ever.

The ceiling was at 2600 ft. Not a great day for buzzing around. Flew out to Batavia and while we’re on the CTAF I hear somebody calling in giving their aircraft type as “Boeing”. Oh, those Stearman pilots, I think, they love to confuse people with that “Boeing” call in. But then I heard him say “B-17 taxiing across the runway”. B-17??? I couldn’t believe it. But sure enough, out in the distance I could see something huge and green moving around on the airport. After we landed, Paul identified it as “Memphis Belle”.

Because of the difficulty we’d had with starting 977, I did something I’ve never done before, and would never do with a non-pilot – I let Paul out of the plane without shutting it down. Even though Paul is a pilot, I still kept my hand on the mixture in case I saw him walking towards the front of the plane. Everybody makes mistakes, and that one has killed even experienced pilots in the past.

The idea was that I’d fly around doing my stuff, and he’d call on the CTAF or text my cell phone if he had trouble and needed me to come pick him up. But the low ceiling was putting a damper on my fun – I didn’t particularly want to to steep turns 500 feet below a solid cloud deck, nor did I want to do stalls that close to the ground. I flew up north, because the cloud deck looked a bit holey-er up there. I got to the lake shore, and after buzzing up and down the shore sight seeing a big I found a hole and flew up over the clouds into severe clear at 3,500 feet. I did some steep turns, but for some reason I was starting to feel queasy. I wonder if that’s because I couldn’t see the ground? I hadn’t heard Paul on the CTAF, but in the course of my travels I’d gotten 20nm away from Batavia and had been down low at some points so maybe I hadn’t heard it.

I decided to head back to Batavia to see if I could see 05X on the ramp or in the pattern. I overflew the airport at 2100 feet, barely 500 feet below the solid ceiling, and didn’t see 05X anywhere around. My airsickness was getting pretty bad, so I turned on the autopilot and the altitude hold and opened the vents. In spite of the fact that the original plan was to wait until I’d heard from Paul P or until 13:00, I decided to head home in spite of the fact that it was only 12:40.

Almost immediately after checking in with Rochester approach, I heard 05X being told to extend his downwind, so I knew that I’d missed him on the CTAF. Good thing he didn’t need my help. I was given another long vector way around the runway 22 approach corridor, and eventually told to enter a left base for runway 25 and contact the tower. In spite of the fact that I was 15nm out, I was cleared to land. I made a nice greaser of a landing, and managed to get home without throwing up, although I made a bit of boo-boo by not taxing over the hold short line before doing my after landing checks. I blame the airsickness.

Because of how crappy I felt, I decided to deal with the faulty battery problems next weekend. And maybe schedule my BFR for some time after I can go out and practice without getting sick.

I’m now home, and of course the clouds have all broken up and instead of a broken layer at 2500 AGL like when I was flying, I’m now looking at one tiny little cloud at 3000 AGL and other than that, “clear and a million”. Sigh.

Hours of boredom punctuated by minutes of terror?

I’ve heard commercial flying described as hours of boredom punctuated by minutes of sheer terror. Private flying, on the other hand, especially in winter, sometimes seems like hours and hours of work on the ground punctuated by a few blissful minutes in the air.

Yesterday, we had two missions in mind – we needed to get the Archer N9105X out to Batavia for its annual, and I wanted to investigate a month old report (but not a formal squawk) that the Lance was impossible to start. I’ve been meaning to look into that but the weather has either been low clouds and snow or high winds and bitter cold, so I haven’t been inclined to go to the airport. And neither has anybody else it seems – there has been almost no flying of club aircraft this winter. Not like last year when it seemed like every weekend was a good one for flying.

It’s a bit of a problem when you want to get two aircraft ready for flight but you’ve only got one pre-heater cart.

I should mention that we’ve got the coolest pre-heater cart in existance. It’s got the standard propane bottle, battery and Red Dragon heater, some fancy ductwork to duct the heat from the heater into the cowling of the aircraft you’re trying to heat. But it’s also got an electrical panel so you can plug it into the wall to keep the battery charged up, and it’s also got a connector for a Piper External Power plug so you can use the pre-heater cart to jump start airplanes.

Anyway, only having one of them is sub-optimal when you’re trying to get two planes ready at the same time. Especially when you’re dubious about starting both of them and jump starting an aircraft requires one person at the controls and another person to remove the external power plug and stow the pre-heater cart once it’s going. So this is what we did:

First I pre-heated the Lance. I dragged it out of the hangar (man, that plane is heavy compared to an Archer) and into the sunshine so that it would hopefully not get totally cold soaked while we pre-heated the Archer. Paul P is very new as the Maintenance Coordinator for the Archer and he had an email from the previous one saying that if you hooked up the external power with the battery master on, it would actually charge the internal battery, so we did that while pre-heating it.

Once it was pre-heated and had been on this “charge” for a while, we decided that we’d try to jump start the Lance, and then once it was running, Paul P would try to start the Archer and if that didn’t work I’d idle the Lance for a while to warm it up and recharge the battery, then shut down and jump start him. But it didn’t work like that – the Lance wouldn’t crank at all, even with the external power. The prop wouldn’t move far enough to kick through the compression of one cylinder. Ok, time for plan B. I’ll have to deal with the Lance later, but right now we’ve got to get that Archer moving.

I moved the pre-heater over to start pre-heating the Dakota while Paul was to get the Archer started and go ahead. We knew the Dakota wouldn’t be a problem starting because he flew it two days ago. But unfortunately, Paul didn’t know the first rule of winter starts, which is you start the damn thing as soon as you get the pre-heater off it, and then you do the cockpit preparation. Instead, he must have sat there for 10-15 minutes with the fin strobe going, which meant that marginal battery was using power to spin gyros and the engine was getting colder. No doubt he also had the radios going and was getting the ATIS and contacting clearance as well. So by the time he tried to start, he got one good spin, but it didn’t catch that time, and it didn’t have enough juice for a second spin. So once again, it was disconnect the pre-heater cart from one plane and drag it over to another. I jump started him, and he left almost immediately after, which confirms my suspicions that he’d used battery power to get ATIS and his departure clearance.

Anyway, the Dakota was warm enough, so I dragged it out of the hangar and started it. No problems starting, and I did my pre-flight cockpit preparation with the engine running and left. It’s kind of amazing that the Dakota has almost the same engine as the Lance, (it’s got an O-540 de-rated to 235 horsepower while the Lance has an IO-540 (the I stands for fuel injection) at the full 300 horsepower) but the Dakota turns over so easily while the Lance is a hard cranker even at the best of times.

I got to Batavia while Paul was just finishing up talking to Jeff Boshart about the squawks on the Archer, so I had almost no shut-down time there. We got up and going again, and I put on my foggles and flew an ILS for practice. It’s still nice how much more situational awareness you’ve got with the Garmin 530 there – Paul pointed out that we were heading to a cloud bank in a mile or two, but I pointed out on the 530’s screen that we were just opposite the FAF and we’d get turned 90 degrees very shortly. And sure enough, we got the turn almost as soon as I finished speaking.

When we got back, I discovered that although there hadn’t been any bookings for the Dakota early in the morning when I’d booked the Lance for the ferry flight, when we made the quick decision to take it, somebody had already booked it. D’oh! I guess I should have checked. He was waiting for us when we got there, and he was surprisingly good natured about it.

Anyway, after we got back, I decided that as Maintenance Coordinator I needed to do something about the Lance. I grabbed the battery tester and battery charger from the line shed and decided to try to charge it up. That’s when I discovered I had to remove 18 screws from an external access panel, and two screws from the forward baggage compartment floor, and 4 quarter turn fasteners on the battery cover just to get access to the battery. Before I started, the hygrometer was showing 0% charge – none of the balls were floating at all. After an hour or so, the hygrometer was showing 25% charge. Progress of a sort, anyway. I figured that the guy with the Dakota should probably be getting back soon, so I started pre-heating the Lance again as well as charging it.

The Maintenance Coordinator for the other Archer (39Z) showed up – he’d been planning to fly, but had gotten delayed so he wasn’t going to fly but wanted to check out the plane on the ground. I prevailed upon him to help me jump start it, and he agreed so I put the battery charger away, put back all those damn screws, and then disconnected the pre-heater heater pipes and hooked up the jump start cables. I jumped in the plane and tried, and dammit, it still wouldn’t crank with just the power from the pre-heater cart battery. However, the POH says that if you flip on the battery master, you get the power of the external power battery and the internal battery, so I tried that and it actually started. Woo hoo. Did my cockpit preparation with the engine running, and away I went.

I took it for an hour flight to charge up the battery. It was a great day for it, sunny and the air was still and smooth. I buzzed around the Finger Lakes, and practiced flying a DME arc using just the DME instead of that horrible “turn 10 twist 10” method they teach when you’re an IFR student. Works pretty well, although you really need good situational awareness to make it work. At one point, just for the hell of it I tried a steep turn – of course that’s the only time in the whole flight that Rochester Approach felt the need to point out some traffic. And boy was he confused trying to give me a clock heading.

The Lance has a graphic engine monitor which also shows you some other facts, like the outside air temp and the oil temp. One of the things it shows you is the voltage level. Early in the flight I switched it to showing the voltage level and it was a nice 13.6 volts. Then I turned off the alternator master, and it quickly dropped to about 10.5 volts. Near the end of the flight I did the same experiment and this time the voltage only dropped to about 12.3 volts, so I think that proves that the battery was charging.

Afterwards, every muscle in my body was complaining about all the pushing and pulling of aircraft out of hangars, running back and forth to the line shed to get appropriate keys and tach books and battery chargers and the like, and pushing the start cart around, and just standing in the freezing cold waiting for batteries to charge and engines to warm up.

I was at the airport from about 10am to about 5:30pm. In that time, I flew for nearly two hours. The work to reward ratio isn’t what I would call optimal, but I’d do it again in a minute.

No, that’s not good either

I wrote about some work I’ve been doing on the Waypoint Generator in Rants and Revelations » Getting there, still some collateral damage. In that, I said I wanted to do some more testing. Well, I did. I reloaded the entire DAFIF dataset. The test took 4 straight days to run, and that’s not including losing a day or so when my router lost its mind. And what this test told me is that the new algorithm for eliminating duplicate points is overzealous.
For instance, it classified two Canadian airports, CYEE Midland/Huronia and CNL8 Wyevale/Boker Field, as being the same. They’re actually nearly two nautical miles apart.

I was calling points the same if the types matched and they’re within 0.05 degrees latitude and 0.05 degrees longitude of each other. Unfortunately that is just about 3 nautical miles in the north/south direction, which this test has shown is too wide a net.

The problem is that I want to spot duplicates when a waypoint changes id, AND when they update the coordinates. I’ve seen places where they’ve updated the coordinates by half a degree, especially in the case of user-entered data.

I think what I’m going to have to do is trust that the coordinates aren’t going to change a whole bunch at the same time the id changes. So what I’ll do is call something a duplicate if it’s within 0.05 degrees if the ids match, but within 0.01 degrees if the ids don’t match. That’s less than a nautical mile, and it would be pretty odd to find two airports within a nautical mile of each other. (A lot less odd to find heliports or reporting points, unfortunately.)

Damn, this means another multi-day test run, unfortunately.

Are you a pilot who blogs, or a blogger who flies?

I got an email today from “IFR Pilot” (who also signs off as Darrell) cc’ed to a bunch of other pilot-bloggers proposing that we all have a fly-in and get to know each other. After a few massively cc’ed exchanges where people seemed enthusiastic about the idea, I set up a mailing list so that other pilot-bloggers could find this list and sign up. If you are in that category, you can sign up at this link.

A lot of the people on “IFR Pilot”‘s list were people I’d never heard of, so I can see I’m going to be adding a whole bunch of new blogs to my RSS reader.