Stuck in Eugene

Author: John Kelly  |  Category: time building

Yesterday I flew to Eugene with a friend I promised I would take flying sometime.  Little did he know this would be more of an adventure than he signed up for.  The flight there was fantastic.  We flew IFR, because it had been a little while since I had been “in the system” and even the the weather was pretty good VFR weather, I like to keep current on at least IFR operations, even if it’s not necessarily in IMC.

Well, we arrived in Eugene, stretched at FlightCraft for a bit, watched the Seahawks kill the Rams, then went out to begin our trek home.  Before takeoff, I do what’s called a runup.  This is where you do your last minute checks to make sure all the radios and avionics are set, and you also runup the engine to about 3/4 power(1700 rpm in my case) and check the magnetoes.  The Cessna 172 engine has a dual magneto system for reliability and efficiency.  Each magneto supplies the spark for a spark plug on each of the cylinders.  So each cylinder has two spark plugs.  Well during the runup procedure you check the left magneto and the right magneto, to make sure that each side is working properly.  Because of the redundancy, you would probably never know if one went bad unless you manually shut one side off.  Well in switching to the right side, the engine lost between 200 – 250 RPMs and began shaking vibrantly.  The POH (Pilots Operating Handbook) for this aircraft states, “RPM drop should not exceed 125 RPM on either magneto or show greater than 50 RPM differential between magnetos”. This can sometimes be “normal” when you have a carbon fouled spark plug.  To clear the carbon fouled plug you would increase power and lean the mixture.  This, in effect, would burn off the carbon or oil that has contaminated the plug.  Well I did that a few times, and the right side magneto never got better.  The left side however was running like a champ.  I was very bummed, but I opted to taxi back and call the owner to see if he had any other ideas.  After talking to him and some other pilots in the area, we all agreed that there was something wrong with the airplane, most likely a bad magneto.  So we had to find ourselves a ride home.  I was waiting for the Lear 31 pilots that I was talking to, to offer a ride on their way back to Spokane, but that didn’t happen. lol.

My friends wife came down and picked us up and took us back to SLE.  We left Salem for a quick flight to Eugene and back at 3pm.  I got back to SLE at 9pm.  What a day.

Right now the plane is getting looked at and I will keep you all posted on the cause of the problem.

Cross Country Flight in the Twin

Author: John Kelly  |  Category: flight school, ground school

Why do I always start out my posts with an apology for taking so long to post. grrr

So I have been taking the required cross-country flights for my commercial certificate this last few weeks while studying for my oral and practicing the single-engine commercial maneuvers in the club plane.  It’s keeping me pretty busy, but I love it.

I took a day VFR cross country to Yakima, which was fun.  Rather uneventful though.  I took my night VFR cross country to Paine Field in Everett, WA.  That was a lot of fun.  It has been a while since I have done any night flying.  It seams like every airport that remotely gets any traffic in the northwest is doing something to their runways/taxiways.  All the airports I was picking for my destination had runway/taxiway closures.  Paine had it’s two longer runways closed and left the shorter(3000 feet) runway open.  3,000 feet is the minimum Hillsboro Aviation will allow their Seminoles to fly into, and it’s the minimum I’d probably fly into as well in a twin.

We left hillsboro enroute for Paine with all the weather and NOTAMS and feeling very confident and excited about the flight.  Once we got within distance to pick up the ATIS report, we tuned in and listened to the long list of NOTAMS confirming that we are allowed to land on the planned runway.  However they mentioned something I wasn’t told when I called Flight Service about the flight.  The ATIS threw in at the end, “Pilot Controlled Lighting Inoperative”.  Now we both hear that thinking, uh, does that mean we can’t turn the lights on?  We radioed Seattle Approach asking if they could find out if the lights were on.  They replied that they believed the lights were on.  So we decided to continue with the flight and told Approach that if we didn’t see any lights we’d be coming back with intentions to land somewhere else, probably Boeing  Field.  Long story short, we were clicking the mic, trying to get the lights on, and I don’t know if they turned on from the mic clicking or if they were always on, but I didn’t see them til we were right over the top of the runway.  We landed, closed and opened our new VFR flight plan, and were off enroute to hillsboro.  That flight was fairly uneventful, just chatted with my flight instructor on the way back.

Ok back to studying. :-)