Today's lesson was kind of a landmark. I admit it freely: I was apprehensive about the lesson; it's been a really tough road and while I have the deepest respect for my instructor, we've had our issues with each other at times and I've been pretty frustrated, even to the point of thinking about delaying my training.
Well, today ended up being fantastic. We took off out of PAO as usual, I got my IFR clearance, did my runup, etc as usual, and John complimented me on my readback, which served its intent of helping me relax prior to takeoff. We were sent on our normal route, and climbed up into the clouds at 1500', which was a real thrill, but not as much as popping out of the clouds a couple of hundred feet later into a bright, beautiful sky. WOW! What a phenomenal experience -- I just felt so lucky at that moment, to be one of the few people who can do that (well, almost).
I flew really well; totally relaxed, and the flight was totally smooth. My approach at Salinas was very good, and I remembered to start my time at the final approach fix and my procedures during the missed approach were in the right order, though John handled the radio for me, which was helpful. He also later pointed out that I used the wrong minimum altitude: I'd heard the ATIS say that the active runway was 31, and I even wrote it down, but I didn't connect the dots and realize that I'd need to use the "circle-to-land" minimums since the approach was for runway 13. Ah, well, lessons learned -- this is the advantage of not being afraid to fail. I'm actually learning!
I configured for the approach at Watsonville on the way to the holding pattern at MARNA -- mostly. There's usually plenty of time to do this, but because of shifting winds I had to spend more time on aircraft control, so I got to finish the configuration during the hold, which is something I should practice anyway. The hold itself was a bit sloppy, and John later said (correctly) that it was the worst part of my flight today, but that it was still OK. I just need to review the holding pattern procedures so I know what to do when, and not struggle so much with having to think through every step. Not rocket science, at least not in a piston aircraft!
My approach at Watsonville was good as well. John said I was chasing the needle a little, which may be true, but it was only a little. I had trouble with the radio when getting the clearance into Watsonville; I had trouble with that on Wednesday as well. I think it's just a matter of getting a lot of information quickly, something that will come with practice.
Then came Palo Alto, which was also good, and had the added bonus of charging through a giant cloud in the middle of the approach. It was fun, and we were relaxed enough to joke about it as John grabbed the dash with both hands just as we were about to dive into the cloud, but it actually did distract me enough to put me off course and force me to correct. But I did correct, quickly, so no harm, no foul.
All in all, it was a great flight! I made a few mistakes, but they were mistakes that I can learn from. I am starting to think that maybe I can really do this after all. John has taken my request for more positive reinforcement to heart, and has been doing a great job of it -- today, in particular, there was one moment where I did start getting just the slightest bit tense, and he instantly said, "You're doing great." Just like that, I was calm again; in fact, I only realized that had happened a while later. So, kudos to him for adjusting his approach to something that works for me -- that's the mark of a great instructor.
BTW: here's a link to today's flight. I'm not sure how long that link will work, but it's pretty cool; you can see the approach to SNS, the hold at MARNA (a little racetrack after departing SNS), the approach to WVI and the trip back to PAO.
Friday, June 29, 2007
Wednesday, June 27, 2007
Update on Instrument Training
I suddenly realized that I haven't been writing here, and it's not been for lack of flying, but more for lack of time to write about it. Also, it's not been the most pleasant experience sometimes. I've basically been taking two training flights a week, doing an approach at Salinas and one at Watsonville each week. I've been really struggling getting the procedural stuff in my head (5 T's, 5 A's, etc). In addition, it's been very hard for me to stay calm in the cockpit, and the tension just makes things worse.
There have been so many factors. For one thing, it's really hard. It's hard to think about what to do at any given point on an approach, it's hard to remember those things as you're passing that point, it's hard to not stress out about the whole thing, it's hard to do all -- or even some -- of these things without compromising control of the aircraft.
The thing is, I can do it. I know I can do it, and John knows I can do it, and in a simulator, I CAN do it. But in the plane, it's a different story. Why? John and I had a talk last week about it, after a lesson in which I was tense through all the approaches and eventually just lost track of what I was supposed to be doing, which is what has been happening. John said I didn't have enough confidence in my own flying, that it was clear that my instincts were generally telling me to do the right things, but that I didn't trust it, and I showed that by hesitating and tensing up. This is basically true, so the question is, what can be done about it? It's not so much that I doubt my ability, it's that I don't know if I'm doing something wrong so I overthink it.
When I was getting my PPL, my instructor Sergey would constantly be saying random positive things: "Nice job." "Beautiful approach!" "Good call" for a radio call. Or sometimes just "Good job, good job.." even if things weren't perfect but just to relax me. After thinking about this last week, I told John about this this morning, and he understood -- it's not about ego or not being able to take criticism, it's about reassurance IN the cockpit environment that things are going OK and I'm not about to kill us. I can take criticism, for sure -- Sergey would criticize too, sometimes to the point where I would have trouble taking it, but he was always very positive about the positive things. So today John tried to be more praiseful in the plane. I think it worked -- it was a great lesson! Not that I did everything right, by any stretch; on the contrary I made more and bigger mistakes than I've made in a while, BUT I kept the radio the whole way, I owned the flight and I felt comfortable making those mistakes. I was more relaxed than I've been in a long time (in a plane). So, I think we're on the right track. We're going to try it again on Friday and hopefully it'll be a similar flight (without the potentially death-inducing errors).
On a side note, last weekend I flew for the first time outside of California. I was visiting relatives in Fort Lauderdale, FL, and I went to NS Aviation at North Perry Airport (KHWO). It was a little weird; there was a big problem since I didn't have proof of insurance with me and had to get AOPA to fax it over, but after a couple of hours I got it sorted out. The instructor, Alan, looked like he was about 19, and when I asked how long he'd been instructing, he said, "2 weeks." Um...O-kay! However, Alan was truly excellent. He had many great suggestions for me, and delivered them in such a way that they were very easy to understand and take in. He grilled me on airspaces and aerodynamic stuff, and we went out and did stalls and steep turns, which was great.
My intent was to fly my cousins' kids around on a subsequent day, but that never happened because of the thunderstorm activity in the area -- not anything I want any part of!
There have been so many factors. For one thing, it's really hard. It's hard to think about what to do at any given point on an approach, it's hard to remember those things as you're passing that point, it's hard to not stress out about the whole thing, it's hard to do all -- or even some -- of these things without compromising control of the aircraft.
The thing is, I can do it. I know I can do it, and John knows I can do it, and in a simulator, I CAN do it. But in the plane, it's a different story. Why? John and I had a talk last week about it, after a lesson in which I was tense through all the approaches and eventually just lost track of what I was supposed to be doing, which is what has been happening. John said I didn't have enough confidence in my own flying, that it was clear that my instincts were generally telling me to do the right things, but that I didn't trust it, and I showed that by hesitating and tensing up. This is basically true, so the question is, what can be done about it? It's not so much that I doubt my ability, it's that I don't know if I'm doing something wrong so I overthink it.
When I was getting my PPL, my instructor Sergey would constantly be saying random positive things: "Nice job." "Beautiful approach!" "Good call" for a radio call. Or sometimes just "Good job, good job.." even if things weren't perfect but just to relax me. After thinking about this last week, I told John about this this morning, and he understood -- it's not about ego or not being able to take criticism, it's about reassurance IN the cockpit environment that things are going OK and I'm not about to kill us. I can take criticism, for sure -- Sergey would criticize too, sometimes to the point where I would have trouble taking it, but he was always very positive about the positive things. So today John tried to be more praiseful in the plane. I think it worked -- it was a great lesson! Not that I did everything right, by any stretch; on the contrary I made more and bigger mistakes than I've made in a while, BUT I kept the radio the whole way, I owned the flight and I felt comfortable making those mistakes. I was more relaxed than I've been in a long time (in a plane). So, I think we're on the right track. We're going to try it again on Friday and hopefully it'll be a similar flight (without the potentially death-inducing errors).
On a side note, last weekend I flew for the first time outside of California. I was visiting relatives in Fort Lauderdale, FL, and I went to NS Aviation at North Perry Airport (KHWO). It was a little weird; there was a big problem since I didn't have proof of insurance with me and had to get AOPA to fax it over, but after a couple of hours I got it sorted out. The instructor, Alan, looked like he was about 19, and when I asked how long he'd been instructing, he said, "2 weeks." Um...O-kay! However, Alan was truly excellent. He had many great suggestions for me, and delivered them in such a way that they were very easy to understand and take in. He grilled me on airspaces and aerodynamic stuff, and we went out and did stalls and steep turns, which was great.
My intent was to fly my cousins' kids around on a subsequent day, but that never happened because of the thunderstorm activity in the area -- not anything I want any part of!
Sunday, May 20, 2007
Cost Splitting And Mentorship
Today was a brand new experience for me. I answered an ad on Craigslist where a former and future flying student wanted to ride along with a private pilot to re-familiarize herself with the cockpit environment prior to jumping back into lessons and paying instructor rates. Great idea, really, so I answered the ad, and we had our flight today.
I won't use real names here, again; you never know how people will feel about their stories being on the internet for anyone to read, not that it's all that interesting, but you never know...Jessie brought a friend of hers from Ireland, Sean. It was his birthday, so we thought we could kill several birds with one stone by flying to Petaluma for lunch, having her do some simple turns and aircraft control along the way, and give him a nice view of San Francisco and the Golden Gate on the way.
We met up at the Caltrain station and drove over to the airport, picked up the keys, created a flight plan and headed out to the plane. The preflight went smoothly, and we got in and listened to ATIS. I called up PAO ground and requested a straight out departure -- at which point the controller informed me that no Class Bravo transitions were being granted at the moment.
Interesting. Now what? I told him I'd go the coastal route; he offered to hand me to Norcal to see if maybe they'd give me a high transition (instead of the usual low transition where the handoff is handled by San Carlos Tower). I declined and said we'd just take the coastal route; it sounded easier.
But as we were on our takeoff climbout, we saw some puffy clouds out over Half Moon Bay. It was hard to tell whether there were more clouds out there, so as we turned left and climbed, I figured I'd just give Norcal Approach a call and see whether I could get the transition. They did indeed give it to me, and vectored me up to basically the Sausalito VOR. It worked out well, since the Golden Gate ended up on the right side, where Sean was sitting. We got out over San Pablo Bay, and Jessie took the controls for a little bit and did a few turns. After she was satiated (at least temporarily) I took the controls back and headed for Petaluma.
The pattern at Petaluma was quite busy; there was a plane on every leg of the pattern at any given time. I crossed overhead high, about 2000' above TPA, because I already knew that 29 was the active runway. I kicked out very wide of the right pattern to give myself time to come in perfectly and to give everyone else time to adjust to my entry. I called the 45 entry, and just as I was turning to the downwind, another aircraft called downwind as well but they were on a departure climbout. We saw them late, but they were above us. The rest of the pattern was fine, and on final I ended up in a pretty significant crab for the crosswind. The landing was...not great; I had too little airspeed and leveled off high, so I came down a little hard, but it was OK. I definitely should've realized I needed more airspeed; I had only 20 degrees of flaps because of the wind, I had a third person in the plane, and I had a nice long runway. My landing was actually a very good short field landing! Not that it needed to be..
Lunch at the 29er Diner was really good. I had french toast, and it was excellent! Conversation with my flying companions was very nice; we talked about flying but also other stuff. After about an hour or a little more, we headed back to the plane (which was 739TW, by the way), and headed out. We took off and headed out for San Pablo Bay again. This time Jessie took quite a bit more time, setting up standard rate turns, trying to maintain her altitude while turning. She did well, and for me, it was my first experience with kind of doing a very tiny tiny bit of teaching. And I enjoyed it! It gave me the rough idea that I could actually do it -- I was encouraging, I had ideas for things she could do from the right seat that wouldn't exceed my comfort zone.
We then came back toward SFO. I was expecting another high transition, but he gave me 2000' or below. So I descended, and immediately started hitting some mild turbulence. The ride was basically slightly rough the rest of the way; not a huge deal, and my passengers seemed to enjoy it. We got a nice relatively low pass off the Golden Gate, over the city and in a very cool turn of events they sent us over mid-field at SFO as a 777 took off below us! That was awesome.
Coming into Palo Alto, they gave us the numbers: Wind 270 at 10 gusting 22. 10 gusting 22??? Um..OK. So I made left traffic, set up a very good pattern, and came in again with 20 degrees of flaps. My approach was good, and I leveled with a little extra airspeed. I ballooned a little, gave it a bit of power, re-leveled, and squeaked the landing beautifully. Jamie even applauded.
Everyone seemed to have a great time! I definitely did. I guess flying actually can be a way to meet some new folks and go on some new adventures. There's a little bit of added pressure, since I feel responsible and all that, but even that's kind of nice to cultivate. It's kind of like the first baby step toward being a commercial pilot of some sort. Very cool feeling!
I won't use real names here, again; you never know how people will feel about their stories being on the internet for anyone to read, not that it's all that interesting, but you never know...Jessie brought a friend of hers from Ireland, Sean. It was his birthday, so we thought we could kill several birds with one stone by flying to Petaluma for lunch, having her do some simple turns and aircraft control along the way, and give him a nice view of San Francisco and the Golden Gate on the way.
We met up at the Caltrain station and drove over to the airport, picked up the keys, created a flight plan and headed out to the plane. The preflight went smoothly, and we got in and listened to ATIS. I called up PAO ground and requested a straight out departure -- at which point the controller informed me that no Class Bravo transitions were being granted at the moment.
Interesting. Now what? I told him I'd go the coastal route; he offered to hand me to Norcal to see if maybe they'd give me a high transition (instead of the usual low transition where the handoff is handled by San Carlos Tower). I declined and said we'd just take the coastal route; it sounded easier.
But as we were on our takeoff climbout, we saw some puffy clouds out over Half Moon Bay. It was hard to tell whether there were more clouds out there, so as we turned left and climbed, I figured I'd just give Norcal Approach a call and see whether I could get the transition. They did indeed give it to me, and vectored me up to basically the Sausalito VOR. It worked out well, since the Golden Gate ended up on the right side, where Sean was sitting. We got out over San Pablo Bay, and Jessie took the controls for a little bit and did a few turns. After she was satiated (at least temporarily) I took the controls back and headed for Petaluma.
The pattern at Petaluma was quite busy; there was a plane on every leg of the pattern at any given time. I crossed overhead high, about 2000' above TPA, because I already knew that 29 was the active runway. I kicked out very wide of the right pattern to give myself time to come in perfectly and to give everyone else time to adjust to my entry. I called the 45 entry, and just as I was turning to the downwind, another aircraft called downwind as well but they were on a departure climbout. We saw them late, but they were above us. The rest of the pattern was fine, and on final I ended up in a pretty significant crab for the crosswind. The landing was...not great; I had too little airspeed and leveled off high, so I came down a little hard, but it was OK. I definitely should've realized I needed more airspeed; I had only 20 degrees of flaps because of the wind, I had a third person in the plane, and I had a nice long runway. My landing was actually a very good short field landing! Not that it needed to be..
Lunch at the 29er Diner was really good. I had french toast, and it was excellent! Conversation with my flying companions was very nice; we talked about flying but also other stuff. After about an hour or a little more, we headed back to the plane (which was 739TW, by the way), and headed out. We took off and headed out for San Pablo Bay again. This time Jessie took quite a bit more time, setting up standard rate turns, trying to maintain her altitude while turning. She did well, and for me, it was my first experience with kind of doing a very tiny tiny bit of teaching. And I enjoyed it! It gave me the rough idea that I could actually do it -- I was encouraging, I had ideas for things she could do from the right seat that wouldn't exceed my comfort zone.
We then came back toward SFO. I was expecting another high transition, but he gave me 2000' or below. So I descended, and immediately started hitting some mild turbulence. The ride was basically slightly rough the rest of the way; not a huge deal, and my passengers seemed to enjoy it. We got a nice relatively low pass off the Golden Gate, over the city and in a very cool turn of events they sent us over mid-field at SFO as a 777 took off below us! That was awesome.
Coming into Palo Alto, they gave us the numbers: Wind 270 at 10 gusting 22. 10 gusting 22??? Um..OK. So I made left traffic, set up a very good pattern, and came in again with 20 degrees of flaps. My approach was good, and I leveled with a little extra airspeed. I ballooned a little, gave it a bit of power, re-leveled, and squeaked the landing beautifully. Jamie even applauded.
Everyone seemed to have a great time! I definitely did. I guess flying actually can be a way to meet some new folks and go on some new adventures. There's a little bit of added pressure, since I feel responsible and all that, but even that's kind of nice to cultivate. It's kind of like the first baby step toward being a commercial pilot of some sort. Very cool feeling!
Friday, May 18, 2007
I Am Above Such Petty Games.
This entry really isn't about flying, though I will talk about it. No one reads this crap anyway, right? So I can vent all I want.
My new motto is, "I am above such petty games." Let's face it: Most of humanity is not above such petty games. You all know what I'm talking about. We live in a culture where we glorify the failure of others (exhibit A: almost all of pop culture, such as American Idol and most sitcoms), we have so little going on in our own lives that we get overly involved in the drama of other, sometimes fictitious people (pretty much every reality show, and the current stupidity at my office), we obsess about totally insignificant things and completely ignore problems that are real and huge, like global warming, oil and gas depletion, overcrowding, famine, and poor decisions regarding foreign policy (and this isn't a political statement; everyone across the spectrum pretty much agrees at this point that there has been some poor decision making). Currently there are many aspects of my life in which people feel they have some say over how I conduct my affairs, and in some cases have decided to express their opinion via petty games.
So, as of this moment, I am above such petty games. One way to be above things (and I mean literally, here, I have not lost my humility as a pilot -- believe me, instrument training keeps you humble!) is to have a propeller and wings, preferably attached to a hunk of metal (or plastic) with comfy seats. Today I flew N21705, a Cessna 172SP brand new to the fleet -- in fact I believe I was the very first renter! Actually that is kind of scary. I ended up doing an extra long preflight. It needed fuel, so I had to call for fuel. It had one of those really annoying covers, so I had to deal with that. It had the wrong type of fuel collection jar (the one in the plane would've fit a Piper aircraft just fine) so I had to change that out. My 10 minute preflight routine took 25 minutes, which isn't a big deal if you're flying 2 hours away but kind of is if you're on a lunch break.
She flew nicely to Livermore (except for one really scary cough from the engine just over the Sunol hills), I had lunch and came home through a little bumpiness. Very well behaved on landing, and very stable in the air, plus a nice GPS. Probably a keeper!
I've been continuing my IFR training. On Wednesday I decided with help from my Mom that the objective was not to focus more on the attitude indicator, or not chase needles, or leave the plane alone in level flight, but to just have fun. I'm paying for the training, I'm working as hard as I can at it, so instead of obsessing about it, I should just enjoy the process and let it happen. We flew to Salinas and Watsonville; one cool thing about Salinas is that I executed a "circle to land" procedure pretty much flawlessly. Next lesson is Monday; before then I'll be taking some strangers to Petaluma with me on Sunday. That should be interesting...
Anyway. I'm kind of in a grumpy mood (as if you couldn't tell). Only stuck at work for a couple of hours more, and then I can go home and be not only above, but far away from such petty games.
My new motto is, "I am above such petty games." Let's face it: Most of humanity is not above such petty games. You all know what I'm talking about. We live in a culture where we glorify the failure of others (exhibit A: almost all of pop culture, such as American Idol and most sitcoms), we have so little going on in our own lives that we get overly involved in the drama of other, sometimes fictitious people (pretty much every reality show, and the current stupidity at my office), we obsess about totally insignificant things and completely ignore problems that are real and huge, like global warming, oil and gas depletion, overcrowding, famine, and poor decisions regarding foreign policy (and this isn't a political statement; everyone across the spectrum pretty much agrees at this point that there has been some poor decision making). Currently there are many aspects of my life in which people feel they have some say over how I conduct my affairs, and in some cases have decided to express their opinion via petty games.
So, as of this moment, I am above such petty games. One way to be above things (and I mean literally, here, I have not lost my humility as a pilot -- believe me, instrument training keeps you humble!) is to have a propeller and wings, preferably attached to a hunk of metal (or plastic) with comfy seats. Today I flew N21705, a Cessna 172SP brand new to the fleet -- in fact I believe I was the very first renter! Actually that is kind of scary. I ended up doing an extra long preflight. It needed fuel, so I had to call for fuel. It had one of those really annoying covers, so I had to deal with that. It had the wrong type of fuel collection jar (the one in the plane would've fit a Piper aircraft just fine) so I had to change that out. My 10 minute preflight routine took 25 minutes, which isn't a big deal if you're flying 2 hours away but kind of is if you're on a lunch break.
She flew nicely to Livermore (except for one really scary cough from the engine just over the Sunol hills), I had lunch and came home through a little bumpiness. Very well behaved on landing, and very stable in the air, plus a nice GPS. Probably a keeper!
I've been continuing my IFR training. On Wednesday I decided with help from my Mom that the objective was not to focus more on the attitude indicator, or not chase needles, or leave the plane alone in level flight, but to just have fun. I'm paying for the training, I'm working as hard as I can at it, so instead of obsessing about it, I should just enjoy the process and let it happen. We flew to Salinas and Watsonville; one cool thing about Salinas is that I executed a "circle to land" procedure pretty much flawlessly. Next lesson is Monday; before then I'll be taking some strangers to Petaluma with me on Sunday. That should be interesting...
Anyway. I'm kind of in a grumpy mood (as if you couldn't tell). Only stuck at work for a couple of hours more, and then I can go home and be not only above, but far away from such petty games.
Wednesday, May 09, 2007
ILS Approaches
Today's lesson was both kind of fulfilling and somewhat frustrating. I showed great improvement in some fronts. I had much better situational awareness, and I even flew a holding pattern all by myself. En route, I did a lot better with maintaining my altitudes and headings.
We started with the VOR 29R approach at Stockton. This is the same one we'd been flying the last two times out, and I think I did..OK. I had better awareness, overall, but I still didn't really know exactly what to do ahead of time -- staying ahead of the airplane, they call it. I'm having the same problem with this as I do with cooking: I read the recipe (or brief the approach), but can't remember it and have to keep referring back to it for every single step. Maybe what I need to do is commit to memorizing recipes before cooking. It might be the same skill.
The same goes for missed approach procedures. There's no time to think about the missed approach procedure and have to look it up when you're a couple of hundred feet off the ground, potentially in a high traffic environment, unable to see the ground. I have to memorize the first couple of steps of the missed approach before I get on the approach.
THEN there's the ILS approach. I did terribly on this; I was all over the place and John had to say something every couple of seconds (not his fault, I was just that far behind -- Airspeed. Altitude. Heading. Airspeed. Relax your grip. Glideslope. Watch the attitude indicator. Heading.) It was so frustrating that after flying the missed (at least I knew the first step this time) I channeled my frustration into that perfect holding pattern. John said nothing; I think he sensed my frustration and helpfully let me get myself through it while safely in my excellent holding pattern.
Basically, the deal is this: 1. I'm far too controlling on the yoke. I need to let the aircraft go, let it do its thing, which in general is to fly stably. This is especially true on the approaches, where not only am I too overcontrolling but 2. I need to fly the attitude indicator and not chase needles. I started doing this toward the end, in en route flight, to great effect. Attitude indicator is my friend. 3. I need to memorize my gaits. I'm making too many power adjustments (related to the overcontrolling) to unknown RPMs.
Friday morning, I'll try doing those three things, and that's all. And we'll see how it goes from there.
We started with the VOR 29R approach at Stockton. This is the same one we'd been flying the last two times out, and I think I did..OK. I had better awareness, overall, but I still didn't really know exactly what to do ahead of time -- staying ahead of the airplane, they call it. I'm having the same problem with this as I do with cooking: I read the recipe (or brief the approach), but can't remember it and have to keep referring back to it for every single step. Maybe what I need to do is commit to memorizing recipes before cooking. It might be the same skill.
The same goes for missed approach procedures. There's no time to think about the missed approach procedure and have to look it up when you're a couple of hundred feet off the ground, potentially in a high traffic environment, unable to see the ground. I have to memorize the first couple of steps of the missed approach before I get on the approach.
THEN there's the ILS approach. I did terribly on this; I was all over the place and John had to say something every couple of seconds (not his fault, I was just that far behind -- Airspeed. Altitude. Heading. Airspeed. Relax your grip. Glideslope. Watch the attitude indicator. Heading.) It was so frustrating that after flying the missed (at least I knew the first step this time) I channeled my frustration into that perfect holding pattern. John said nothing; I think he sensed my frustration and helpfully let me get myself through it while safely in my excellent holding pattern.
Basically, the deal is this: 1. I'm far too controlling on the yoke. I need to let the aircraft go, let it do its thing, which in general is to fly stably. This is especially true on the approaches, where not only am I too overcontrolling but 2. I need to fly the attitude indicator and not chase needles. I started doing this toward the end, in en route flight, to great effect. Attitude indicator is my friend. 3. I need to memorize my gaits. I'm making too many power adjustments (related to the overcontrolling) to unknown RPMs.
Friday morning, I'll try doing those three things, and that's all. And we'll see how it goes from there.
Monday, May 07, 2007
Nice Refreshing Flight
Sunday seemed like just as nice a day as Saturday seemed like but was not. My friend Kindra wanted to go flying, so I checked the weather; there was definitely some wind but nothing like the gustiness reported for Saturday. Plus, it was the second warm day in a row, so theoretically there would be less turbulence. I was still concerned about taking a passenger up after Saturday's experience; if I'd had a passenger on Saturday I'm pretty sure they would've tossed their cookies -- in fact if I had been a passenger on Saturday, I'm pretty sure I would've lost it.
We didn't have much time, so we just decided to do a real bay tour over San Francisco and the Golden Gate and all that. We got 236SP out of SQL; it wasn't very busy and I got my squawk code for the class B transition almost instantly. 236Sp is a nice plane, very well taken care of and relatively new -- that's the problem with the Cherokees; they're all from the early '80s. So we preflighted, I wavered a little bit on the decision to go because of the wind, then decided we could always turn back if we wanted to.
So we took off, called up SFO tower, got our clearance through their airspace, and after crossing the airport, where I would ordinarily turn and head straight for the bridge, I got vectored directly over downtown SF. I tend to stay away from this area, just because I'm not sure where I can and can't go yet, but I'm learning! It was very cool; we saw the Transamerica building and Coit Tower, and of course the whole marina. We went up toward San Pablo Bay, twisting to get better views of Treasure Island and Alcatraz. I was holding 2000' exactly, in stark contrast to the previous day's sudden deviations of 200' or more. We flew back down, over the Golden Gate, and then took the coastline down to Ano Nuevo. That was new; I had to do some concentrating to not bust SFO's airspace since I was out of it, and there's a small area where it comes down to 1500' but mostly it starts at 2100'.
We turned around and came back over Crystal Springs, and into San Carlos where the controller helped me out by putting me in front of a plane doing pattern work, but of course this also resulted in my having to maneuver a bit more steeply than I would've liked. My landing was my best in a really long time -- winds were 320 at 10, nearly right down the runway and pretty strong, so I went with 20 degrees of flaps. I held it off for a really long time, and touched down very smoothly!
Next instrument lesson is Wednesday; I'm going to try to fly before then, maybe a quick cross country to someplace like Modesto or Salinas or Monterey.
We didn't have much time, so we just decided to do a real bay tour over San Francisco and the Golden Gate and all that. We got 236SP out of SQL; it wasn't very busy and I got my squawk code for the class B transition almost instantly. 236Sp is a nice plane, very well taken care of and relatively new -- that's the problem with the Cherokees; they're all from the early '80s. So we preflighted, I wavered a little bit on the decision to go because of the wind, then decided we could always turn back if we wanted to.
So we took off, called up SFO tower, got our clearance through their airspace, and after crossing the airport, where I would ordinarily turn and head straight for the bridge, I got vectored directly over downtown SF. I tend to stay away from this area, just because I'm not sure where I can and can't go yet, but I'm learning! It was very cool; we saw the Transamerica building and Coit Tower, and of course the whole marina. We went up toward San Pablo Bay, twisting to get better views of Treasure Island and Alcatraz. I was holding 2000' exactly, in stark contrast to the previous day's sudden deviations of 200' or more. We flew back down, over the Golden Gate, and then took the coastline down to Ano Nuevo. That was new; I had to do some concentrating to not bust SFO's airspace since I was out of it, and there's a small area where it comes down to 1500' but mostly it starts at 2100'.
We turned around and came back over Crystal Springs, and into San Carlos where the controller helped me out by putting me in front of a plane doing pattern work, but of course this also resulted in my having to maneuver a bit more steeply than I would've liked. My landing was my best in a really long time -- winds were 320 at 10, nearly right down the runway and pretty strong, so I went with 20 degrees of flaps. I held it off for a really long time, and touched down very smoothly!
Next instrument lesson is Wednesday; I'm going to try to fly before then, maybe a quick cross country to someplace like Modesto or Salinas or Monterey.
Saturday, May 05, 2007
Oh. My. God.
The only thing I can say about today is that it was difficult. It was not fun, I don't even think it was educational, it was just difficult. And annoying -- difficult and annoying. Holy crap.
My plan was to go to Nancy's Diner at Willows (KWLW) Airport. It's a 24 hour diner, and I thought it'd make a great midnight destination, so I wanted to scope it out in daylight hours. Today looked beautiful; no clouds anywhere, and good visibility. It started out a little bit windy, but not a big deal.
I took off straight out from PAO, contacted SQL tower like a pro, got cleared through SFO's class B, and was on my way. During the transition, I hit quite a bit of turbulence passing SFO. Didn't think too much of it, I just figured that once I climbed to my cruise altitude, 6500, everything would be fine. As I got out over the bay, I started my climb and held it at 4500 by the time I got to SGD VOR. It was not any smoother, but it was manageable. At this point I noticed that I was having a lot of trouble with keeping the plane at a constant altitude. I'd set it up, and suddenly the engine sounded like it was racing, the RPMs were 100 higher than before, and I was climbing. So I'd reduce it, re-trim it get it all set up again, and a few minutes later, it would be descending, airspeed decreasing and power down by 50 RPM. I never did figure this out; it could have been an effect of the strong and shifting wind, but I don't know.
I continued climbing to 6500, and it got a little more manageable. I was starting to wonder whether I was still on flight following, because I'd heard nothing at all from the controller in about 40 minutes, but as I passed the Maxwell VOR I got switched to a new frequency. Shortly thereafter I began my descent and made left traffic for runway 34 at Willows. The approach was bumpy, but again, nothing too concerning.
I had lunch at Nancy's, which was really good, and only $7.50 including tip for 2 eggs, excellent hash browns and toast. I'm going back soon!
Then the fun started. I got back into N81034, got all set up, went to start, and...nothing. After a few more attempts I realized that every time I tried to start I lost electrical power entirely. Great. I'm stuck in Willows, and kind of need to be home at some point in the near future....so I called the club. They were pretty much useless; I guess maintenance doesn't work on the weekends? I don't know, but eventually I found someone at the airport who knew how to jump start an airplane. I was so clueless, but luckily the guy knew more than me. "12 or 24 volts?" he asks me, like I'm supposed to know..I probably AM supposed to know, but you know..in any case, the POH had all the answers, and he quickly figured out exactly how to get it done. It's just like jump starting a car, pretty much, and it did work, so after careful examination of the alternator gauge, and making sure it wasn't on 0 (it was close, but not 0), off I went. I was very nervous about whether the alternator was working -- I know I didn't leave the master switch on, even though that's the simplest explanation. I have no other explanation. I started out with the GPS (which I was only using as a comm device; it was pretty old) and the DME off to save electrical power, but as I flew it made its way back so I turned the additional equipment back on.
I took off and headed back south. Everything seemed to be in order as I climbed to 5500 and got flight following from a friendly controller. But then I started really getting knocked around by turbulence. And it just kept getting worse! I climbed to 7500, and it pretty much didn't help at all. I crossed SGD VOR at 7500, getting knocked all over the place, just trying to maintain a wings level attitude, which was actually somewhat challenging at times. When I had the Golden Gate in sight, I started a descent (hesitantly) and got handed off to a new controller. That controller told me to cross the Coliseum at or above 3500. What?? I told her that was inconvenient from my present location north of the Golden Gate. She cleared me through Class B at or below 2000. OK, that's better.
SFO Tower had other ideas, though. Instead of the usual transition at 2000 west of Highway 101, he routed me over Candlestick Park and to mid-span San Mateo bridge, at or below 1500. This was not comfortable -- it's the widest part of the bay, and I was still getting destroyed by turbulence. Losing 100 feet suddenly at 6500 is not a big deal. Losing 100 feet suddenly at 1500 feet IS a big deal, at least to me. About half way to the bridge, SFO Tower must have sensed my consternation, and gave me a new altitude of "at or below 1000." Bloody hell. OK, so now I'm at 1000...UNH! I mean, 850 feet above the water with no hope of any sort of emergency landing should anything go wrong with my engine, which, by the way, was still shifting somewhat erratically by 50-100 knots, not that I had any time to be concerned about that since I kept worrying that I would end up upside-down due to some jolt of turbulence.
Finally I was talking to PAO tower, and got the numbers at Palo Alto: Wind 310 at 20 knots. 20 knots, but right down the runway, thank goodness. My landing was bad, but safe -- level too high, balloon, add power, releveling, balloon again, add a little power, level too high, land flat. But safely. I taxied to my parking row and crawled out of the plane, and sat on all fours on the wing for a minute, breathing deeply, really glad to be on the ground.
And now I'm totally exhausted. I did a few things well; I did a good job maintaining my altitude for the most part, given the circumstances, and I did a very good job tracking VORs and courses. Fuel management was good. I did not keep track of the time elapsed on my trip; that wasn't so good. I did deal with an unexpected situation reasonably well, swallowing my pride and asking questions. My radio work was excellent, with the possible exception of the controller who told me to fly to the Coliseum. And I got 3.1 hours of cross country time. And a good breakfast. All in all, a decent bit of experience. Just no fun.
Update: There were definitely PIREPs of moderate turbulence all around the area, and a few of severe turbulence. Also, a Cessna made an emergency landing on a road in Newark, CA after losing its engine and electrical system, allegedly because of turbulence. I'm not sure how that works; I suppose a bad enough hit could shake something loose, but engine AND electrical? That's some bad luck. Apparently though the pilot showed some incredible airmanship to get the plane down on the street that had high tension electrical wires on either side of it, so I'm sure he'll call it even.
I now know my fears were justified when flying at 900' over the middle of the bay in this stuff.
My plan was to go to Nancy's Diner at Willows (KWLW) Airport. It's a 24 hour diner, and I thought it'd make a great midnight destination, so I wanted to scope it out in daylight hours. Today looked beautiful; no clouds anywhere, and good visibility. It started out a little bit windy, but not a big deal.
I took off straight out from PAO, contacted SQL tower like a pro, got cleared through SFO's class B, and was on my way. During the transition, I hit quite a bit of turbulence passing SFO. Didn't think too much of it, I just figured that once I climbed to my cruise altitude, 6500, everything would be fine. As I got out over the bay, I started my climb and held it at 4500 by the time I got to SGD VOR. It was not any smoother, but it was manageable. At this point I noticed that I was having a lot of trouble with keeping the plane at a constant altitude. I'd set it up, and suddenly the engine sounded like it was racing, the RPMs were 100 higher than before, and I was climbing. So I'd reduce it, re-trim it get it all set up again, and a few minutes later, it would be descending, airspeed decreasing and power down by 50 RPM. I never did figure this out; it could have been an effect of the strong and shifting wind, but I don't know.
I continued climbing to 6500, and it got a little more manageable. I was starting to wonder whether I was still on flight following, because I'd heard nothing at all from the controller in about 40 minutes, but as I passed the Maxwell VOR I got switched to a new frequency. Shortly thereafter I began my descent and made left traffic for runway 34 at Willows. The approach was bumpy, but again, nothing too concerning.
I had lunch at Nancy's, which was really good, and only $7.50 including tip for 2 eggs, excellent hash browns and toast. I'm going back soon!
Then the fun started. I got back into N81034, got all set up, went to start, and...nothing. After a few more attempts I realized that every time I tried to start I lost electrical power entirely. Great. I'm stuck in Willows, and kind of need to be home at some point in the near future....so I called the club. They were pretty much useless; I guess maintenance doesn't work on the weekends? I don't know, but eventually I found someone at the airport who knew how to jump start an airplane. I was so clueless, but luckily the guy knew more than me. "12 or 24 volts?" he asks me, like I'm supposed to know..I probably AM supposed to know, but you know..in any case, the POH had all the answers, and he quickly figured out exactly how to get it done. It's just like jump starting a car, pretty much, and it did work, so after careful examination of the alternator gauge, and making sure it wasn't on 0 (it was close, but not 0), off I went. I was very nervous about whether the alternator was working -- I know I didn't leave the master switch on, even though that's the simplest explanation. I have no other explanation. I started out with the GPS (which I was only using as a comm device; it was pretty old) and the DME off to save electrical power, but as I flew it made its way back so I turned the additional equipment back on.
I took off and headed back south. Everything seemed to be in order as I climbed to 5500 and got flight following from a friendly controller. But then I started really getting knocked around by turbulence. And it just kept getting worse! I climbed to 7500, and it pretty much didn't help at all. I crossed SGD VOR at 7500, getting knocked all over the place, just trying to maintain a wings level attitude, which was actually somewhat challenging at times. When I had the Golden Gate in sight, I started a descent (hesitantly) and got handed off to a new controller. That controller told me to cross the Coliseum at or above 3500. What?? I told her that was inconvenient from my present location north of the Golden Gate. She cleared me through Class B at or below 2000. OK, that's better.
SFO Tower had other ideas, though. Instead of the usual transition at 2000 west of Highway 101, he routed me over Candlestick Park and to mid-span San Mateo bridge, at or below 1500. This was not comfortable -- it's the widest part of the bay, and I was still getting destroyed by turbulence. Losing 100 feet suddenly at 6500 is not a big deal. Losing 100 feet suddenly at 1500 feet IS a big deal, at least to me. About half way to the bridge, SFO Tower must have sensed my consternation, and gave me a new altitude of "at or below 1000." Bloody hell. OK, so now I'm at 1000...UNH! I mean, 850 feet above the water with no hope of any sort of emergency landing should anything go wrong with my engine, which, by the way, was still shifting somewhat erratically by 50-100 knots, not that I had any time to be concerned about that since I kept worrying that I would end up upside-down due to some jolt of turbulence.
Finally I was talking to PAO tower, and got the numbers at Palo Alto: Wind 310 at 20 knots. 20 knots, but right down the runway, thank goodness. My landing was bad, but safe -- level too high, balloon, add power, releveling, balloon again, add a little power, level too high, land flat. But safely. I taxied to my parking row and crawled out of the plane, and sat on all fours on the wing for a minute, breathing deeply, really glad to be on the ground.
And now I'm totally exhausted. I did a few things well; I did a good job maintaining my altitude for the most part, given the circumstances, and I did a very good job tracking VORs and courses. Fuel management was good. I did not keep track of the time elapsed on my trip; that wasn't so good. I did deal with an unexpected situation reasonably well, swallowing my pride and asking questions. My radio work was excellent, with the possible exception of the controller who told me to fly to the Coliseum. And I got 3.1 hours of cross country time. And a good breakfast. All in all, a decent bit of experience. Just no fun.
Update: There were definitely PIREPs of moderate turbulence all around the area, and a few of severe turbulence. Also, a Cessna made an emergency landing on a road in Newark, CA after losing its engine and electrical system, allegedly because of turbulence. I'm not sure how that works; I suppose a bad enough hit could shake something loose, but engine AND electrical? That's some bad luck. Apparently though the pilot showed some incredible airmanship to get the plane down on the street that had high tension electrical wires on either side of it, so I'm sure he'll call it even.
I now know my fears were justified when flying at 900' over the middle of the bay in this stuff.
Real Airplane, Real IMC
I had two lessons last week; I've managed to create enough time in my life (and in my brain) to step up the lessons which really helps me feel like I'm on a path toward a goal. John has been great as an instructor, and as I found out, much more tuned into the touchy feely stuff than Sergey. That's both good and bad; it forces me to deal with it, which is good, but sometimes before I'm ready, which is bad. Anyway, this'll make a lot more sense in a bit..
On Tuesday, we went up for my first actual instrument approaches. I was really nervous. I still don't know why, I think it has to do with feeling like I was being tested. This isn't John's fault, it's purely a creation in my own head -- I'd been on a simulator a lot, and I felt like how I responded in an airplane was a test of how well I'd learned and how much I'd studied. We decided to fly to Stockton (KSCK) and do the VOR 29R approach.
Basically, I did far more poorly than I would've imagined. I couldn't even read back the clearance, I couldn't maintain my altitudes, I got completely lost and by the time we were doing the approach I basically had no idea what was going on. Not a good feeling, and John was doing his best to try and help me out but there was really nothing he could do -- I had psyched myself up so much that I couldn't think clearly, and that's a bad thing especially when flying IFR. The flight did accomplish a few things, though -- for one, I was able to see how the system worked, to learn where I would fall behind the most and what would present the greatest challenge.
After the lesson John basically asked me what was going on -- I think he knew that something was wrong, and I felt bad that I couldn't explain it to him because I didn't really understand yet. So, I tried to convince him that it wasn't going to be an ongoing problem, and that everything would be fine. I was also trying to convince myself, which went less well...
So I thought about it for a while, and realized that I was just putting too much pressure on myself to do something that I've only just started training for. By Friday's lesson, I was feeling very calm about the whole thing. Who cares if I mess up? I have an instructor sitting there. If I sound like an idiot to ATC, so what? I hear a lot of people WITH their ratings sounding questionable to ATC. They're used to it, they get paid to do it, they'll roll their eyes, say "stupid rookie" and move on.
Friday was just amazing, in every way. For one thing, there was weather! There were actual clouds, with PAO at a ceiling of 1500'. I was calm, I read back the clearance (almost) correctly, I took a few chances and learned. Takeoff was uneventful, until the ceiling got closer and closer, and I had to fight all my "avoid the clouds" instincts to force myself to keep climbing! I turned right heading 060 as instructed and just before we penetrated the cloud layer, I said to John, "I'm not sure how I'm going to react to this." He said, "Don't look outside." Ah. Brilliant!! So I didn't, and I flew (in my estimation) extremely well. John had taken over the radio work, except for simple heading or altitude instructions. I held my altitudes, I held my headings, I stayed mostly coordinated.
I did, however, lose my situational awareness. Once ATC starts vectoring me to places, I lose track of where I am. I could not picture how to enter the holding pattern at Stockton, which is the entry to the approach. Once John told me, I kind of figured out where we were, but this is clearly something that will need work. That's OK, though, I just need to work at it -- I know I can do it.
I also could not copy our clearance back to PAO when we were in the missed approach holding pattern near SCK. Holding itself is a ton of work! I managed to do that OK, but just to drill myself I tried copying the clearance too, and did not get very far.
On the way back, we used the GPS and the autopilot for some of the flight, which helped ease the workload considerably. I did lose my location again once we got vectors, but not as bad as the other end of the flight, probably in part because I'm so much more familiar with the area.
Anyway, it's been a great week, and I'm looking forward to the next time!
On Tuesday, we went up for my first actual instrument approaches. I was really nervous. I still don't know why, I think it has to do with feeling like I was being tested. This isn't John's fault, it's purely a creation in my own head -- I'd been on a simulator a lot, and I felt like how I responded in an airplane was a test of how well I'd learned and how much I'd studied. We decided to fly to Stockton (KSCK) and do the VOR 29R approach.
Basically, I did far more poorly than I would've imagined. I couldn't even read back the clearance, I couldn't maintain my altitudes, I got completely lost and by the time we were doing the approach I basically had no idea what was going on. Not a good feeling, and John was doing his best to try and help me out but there was really nothing he could do -- I had psyched myself up so much that I couldn't think clearly, and that's a bad thing especially when flying IFR. The flight did accomplish a few things, though -- for one, I was able to see how the system worked, to learn where I would fall behind the most and what would present the greatest challenge.
After the lesson John basically asked me what was going on -- I think he knew that something was wrong, and I felt bad that I couldn't explain it to him because I didn't really understand yet. So, I tried to convince him that it wasn't going to be an ongoing problem, and that everything would be fine. I was also trying to convince myself, which went less well...
So I thought about it for a while, and realized that I was just putting too much pressure on myself to do something that I've only just started training for. By Friday's lesson, I was feeling very calm about the whole thing. Who cares if I mess up? I have an instructor sitting there. If I sound like an idiot to ATC, so what? I hear a lot of people WITH their ratings sounding questionable to ATC. They're used to it, they get paid to do it, they'll roll their eyes, say "stupid rookie" and move on.
Friday was just amazing, in every way. For one thing, there was weather! There were actual clouds, with PAO at a ceiling of 1500'. I was calm, I read back the clearance (almost) correctly, I took a few chances and learned. Takeoff was uneventful, until the ceiling got closer and closer, and I had to fight all my "avoid the clouds" instincts to force myself to keep climbing! I turned right heading 060 as instructed and just before we penetrated the cloud layer, I said to John, "I'm not sure how I'm going to react to this." He said, "Don't look outside." Ah. Brilliant!! So I didn't, and I flew (in my estimation) extremely well. John had taken over the radio work, except for simple heading or altitude instructions. I held my altitudes, I held my headings, I stayed mostly coordinated.
I did, however, lose my situational awareness. Once ATC starts vectoring me to places, I lose track of where I am. I could not picture how to enter the holding pattern at Stockton, which is the entry to the approach. Once John told me, I kind of figured out where we were, but this is clearly something that will need work. That's OK, though, I just need to work at it -- I know I can do it.
I also could not copy our clearance back to PAO when we were in the missed approach holding pattern near SCK. Holding itself is a ton of work! I managed to do that OK, but just to drill myself I tried copying the clearance too, and did not get very far.
On the way back, we used the GPS and the autopilot for some of the flight, which helped ease the workload considerably. I did lose my location again once we got vectors, but not as bad as the other end of the flight, probably in part because I'm so much more familiar with the area.
Anyway, it's been a great week, and I'm looking forward to the next time!
Friday, April 27, 2007
Instrument Training Continues
I've only actually been in an airplane once in the last three weeks or so, and probably twice in the last six weeks. I went up on Tuesday to just make sure I remembered how to land, which I did, mostly, so I did five landings and called it an evening. In the mean time, I've had 3 or 4 more simulator lessons, working on navigation, en route planning and transition to approach procedures for IFR flight. This stuff is hard -- there is so much to think about, even straight and level flight is a challenge for me, so adding navigation, radio work, getting ATIS in a timely fashion, transitioning to approach, actually flying the approach, and thinking about the missed approach procedure is pretty overwhelming.
However, in today's lesson, in the last 15 minutes or so I really felt like I got into a rhythm with it a little bit. That was a surprising relief. I think it's all about preparation -- if the radios are set, if you know where you're going and exactly what to do when you get there, then things are OK. The "what to do" section is mostly about the five T's: Turn, Time, Twist, Throttle, Talk. Turn the plane to the appropriate new heading (or, since in many cases you'll be following a course, turn in the general direction of the new course), set the timer, twist the OBS of the nav aid to whatever it needs to be set to, adjust throttle once established on the course, if necessary, and talk to the controller if required. It seems so simple, but it really isn't. At least, not yet.
Transitioning to approach is again all about preparation. Before calling up the approach controller at the destination, you have the five A's (I guess that makes sense, since for you bio geeks out there, A and T are reciprocal): ATIS, Altimeter, Avionics, Approach Briefing, Airspeed. Get the ATIS at the destination, set the altimeter accordingly, [select which approach to use based on the ATIS], set the avionics for the selected approach, brief the approach, and have a plan for when to reduce airspeed. Pretty intense.
Flying the approach is also pretty challenging, at least in the simulator. In VFR flight it doesn't really matter whether you can set up a constant rate of descent to get you to a certain altitude at a certain point. Approaches are exactly that, and since there are almost no references to adjust against, the consistency is important.
So, given my comfort level at the end of today's lesson, John has opted to have us try it out in an actual airplane this coming Tuesday! I'm very excited but I really feel like I need to study, kind of a lot.
By the way, the book we're using is by Peter Dogan; I can't remember the exact title, but so far it is excellent.
However, in today's lesson, in the last 15 minutes or so I really felt like I got into a rhythm with it a little bit. That was a surprising relief. I think it's all about preparation -- if the radios are set, if you know where you're going and exactly what to do when you get there, then things are OK. The "what to do" section is mostly about the five T's: Turn, Time, Twist, Throttle, Talk. Turn the plane to the appropriate new heading (or, since in many cases you'll be following a course, turn in the general direction of the new course), set the timer, twist the OBS of the nav aid to whatever it needs to be set to, adjust throttle once established on the course, if necessary, and talk to the controller if required. It seems so simple, but it really isn't. At least, not yet.
Transitioning to approach is again all about preparation. Before calling up the approach controller at the destination, you have the five A's (I guess that makes sense, since for you bio geeks out there, A and T are reciprocal): ATIS, Altimeter, Avionics, Approach Briefing, Airspeed. Get the ATIS at the destination, set the altimeter accordingly, [select which approach to use based on the ATIS], set the avionics for the selected approach, brief the approach, and have a plan for when to reduce airspeed. Pretty intense.
Flying the approach is also pretty challenging, at least in the simulator. In VFR flight it doesn't really matter whether you can set up a constant rate of descent to get you to a certain altitude at a certain point. Approaches are exactly that, and since there are almost no references to adjust against, the consistency is important.
So, given my comfort level at the end of today's lesson, John has opted to have us try it out in an actual airplane this coming Tuesday! I'm very excited but I really feel like I need to study, kind of a lot.
By the way, the book we're using is by Peter Dogan; I can't remember the exact title, but so far it is excellent.
Thursday, April 05, 2007
Instrument Lesson...In An Airplane!
Today I had an experience bordering on monumental in terms of my flight training. I went with my instructor John on our first instrument flying lesson in an airplane, rather than the simulator. First off, I haven't been in a plane for almost three weeks, and there was a long break before that too so I was not feeling great about my piloting and communication skills. But once I got into the cockpit, once again, it all just came back. I didn't even hesitate on my radio calls -- mostly because I didn't want to, in front of an instructor that had never seen me fly before. I know I'm being evaluated, there's no avoiding that, and in the end it can only help me to be at my best so that the suggestions I get are not things that I already know I should have done.
We took a left Dumbarton departure out toward the coast, and as I was climbing up to altitude, John had me put on the dreaded "view limiting device," also known as the "hood." We then spent the next 1.5 hours doing various maneuvers, including the different patterns that we'd practiced in the simulator. Except for one thing, it was actually much easier in the airplane, but that one thing was rudder control. The turn coordinator was kind of out of whack; the ball was always off to the left no matter what.
It was interesting really experiencing disorientation and vertigo. At least five times through the flight, I would have sworn that the plane was doing one thing, and the instruments disagreed with me (but agreed with each other). Trusting the instruments is truly an effort. Clearly it's worth it. The other really shocking thing was having to land the airplane after taking the hood off at about 400' above the ground on final approach. I felt like I'd been dropped into the cockpit of an airplane on final from some totally unrelated context, like sleeping, or working or something. Just boom: Land this plane, NOW! It's surprising, especially since I knew it was coming; it's not like I couldn't hear the radio calls.
But, my landing was good, as was the rest of my flying. It was really fulfilling; John even complimented me afterwards, saying my flying was excellent, my control of the aircraft on the ground and in the air were excellent. On my landing he even gave me a "nice job" even though I leveled off too high, and my second level-off at the appropriate height was a bit slow -- still, I did land nice and soft, which is the important thing.
It was a great lesson -- exhausting, but a lot of fun, a real workout and the kind of thing I can tell will get at least somewhat easier with time and lots of practice.
We took a left Dumbarton departure out toward the coast, and as I was climbing up to altitude, John had me put on the dreaded "view limiting device," also known as the "hood." We then spent the next 1.5 hours doing various maneuvers, including the different patterns that we'd practiced in the simulator. Except for one thing, it was actually much easier in the airplane, but that one thing was rudder control. The turn coordinator was kind of out of whack; the ball was always off to the left no matter what.
It was interesting really experiencing disorientation and vertigo. At least five times through the flight, I would have sworn that the plane was doing one thing, and the instruments disagreed with me (but agreed with each other). Trusting the instruments is truly an effort. Clearly it's worth it. The other really shocking thing was having to land the airplane after taking the hood off at about 400' above the ground on final approach. I felt like I'd been dropped into the cockpit of an airplane on final from some totally unrelated context, like sleeping, or working or something. Just boom: Land this plane, NOW! It's surprising, especially since I knew it was coming; it's not like I couldn't hear the radio calls.
But, my landing was good, as was the rest of my flying. It was really fulfilling; John even complimented me afterwards, saying my flying was excellent, my control of the aircraft on the ground and in the air were excellent. On my landing he even gave me a "nice job" even though I leveled off too high, and my second level-off at the appropriate height was a bit slow -- still, I did land nice and soft, which is the important thing.
It was a great lesson -- exhausting, but a lot of fun, a real workout and the kind of thing I can tell will get at least somewhat easier with time and lots of practice.
Friday, March 30, 2007
Bay Tours and Instrument Training
The last few weeks haven't seen much time for the skies, which is unfortunate given how absolutely beautiful the weather has been. Two weeks ago I started my instrument training with John Otte. We began work on the simulator and did some basic maneuvering and pattern following, and getting to understand the different "gaits" of an airplane. Basically, it seems that for a given airplane, there is a specific configuration that will yield a certain result. So, an approach descent will occur at a certain RPM and flap setting, reducing the need for guesswork. Pretty handy tool! We also worked on developing my "scan" of the instruments -- basically the idea is to be able to glance at all six instruments at the right time depending on what you're doing to evoke the right response from the airplane and find and correct any errors. It's much, much harder than it sounds.
It was a great first lesson; John is a very good instructor and has a great, relaxed manner about him that keeps me from getting too tense or too down on myself. I had another lesson with him last Friday, where I was too exhausted to do much of anything but we managed to get some good simulator time in anyway before I crashed it into the ground (that's a big advantage of a simulator!), and another one this morning where I felt like I made some major strides in keeping things under control. I actually felt kind of comfortable for a few moments while stabilized in a turn or in straight and level flight, which is a good feeling. We also did some partial panel out work (meaning, some of the instruments are not working), which was a big challenge -- especially holding altitude with no attitude indicator (the trim on the simulator does not work at all like that on a real airplane). So on Tuesday we will be heading into the skies for a flight in an actual airplane!
Speaking of actual airplanes, the last time I flew in one of those was about two weeks ago. On both Saturday and Sunday I went on a bay tour, with two different co-workers. I did the same route each time; the first time was more kind of random and guessworky. I actually very nearly missed my turn toward the west to return home, but saved it by deciding at the right moment to have the GPS locate Tracy Airport, and seeing that I was just flying past it. The second time involved an initial departure toward the coast only to see that it was totally cloudy, so I turned and transitioned back through PAO's airspace and on the same route as the day before, but tighter, since it was more familiar.
It's kind of funny to note my co-workers' responses when I get my pilot face on. Things are official, and important -- the passenger brief is important, and I think for a moment they're not sure if I'm kidding when I explain how the seat belt functions. Hey, it's in the regs! Then when I start talking on the radio I think there's a moment of "Hey, he actually knows what he's doing!" It's pretty fun for me to see that, for people who know me in one context to get to know me in a totally different context. On a day to day level, I'm not really that much of a "take-charge" type of guy, but in the pilot's seat, I'm in command -- it's one of the many things I really enjoy about flying. And there's probably a life lesson in there somewhere, about recognizing appropriate moments to take command of a situation.
Instrument training will resume next week, and I'm hoping to go flying this weekend in the sunshine!
It was a great first lesson; John is a very good instructor and has a great, relaxed manner about him that keeps me from getting too tense or too down on myself. I had another lesson with him last Friday, where I was too exhausted to do much of anything but we managed to get some good simulator time in anyway before I crashed it into the ground (that's a big advantage of a simulator!), and another one this morning where I felt like I made some major strides in keeping things under control. I actually felt kind of comfortable for a few moments while stabilized in a turn or in straight and level flight, which is a good feeling. We also did some partial panel out work (meaning, some of the instruments are not working), which was a big challenge -- especially holding altitude with no attitude indicator (the trim on the simulator does not work at all like that on a real airplane). So on Tuesday we will be heading into the skies for a flight in an actual airplane!
Speaking of actual airplanes, the last time I flew in one of those was about two weeks ago. On both Saturday and Sunday I went on a bay tour, with two different co-workers. I did the same route each time; the first time was more kind of random and guessworky. I actually very nearly missed my turn toward the west to return home, but saved it by deciding at the right moment to have the GPS locate Tracy Airport, and seeing that I was just flying past it. The second time involved an initial departure toward the coast only to see that it was totally cloudy, so I turned and transitioned back through PAO's airspace and on the same route as the day before, but tighter, since it was more familiar.
It's kind of funny to note my co-workers' responses when I get my pilot face on. Things are official, and important -- the passenger brief is important, and I think for a moment they're not sure if I'm kidding when I explain how the seat belt functions. Hey, it's in the regs! Then when I start talking on the radio I think there's a moment of "Hey, he actually knows what he's doing!" It's pretty fun for me to see that, for people who know me in one context to get to know me in a totally different context. On a day to day level, I'm not really that much of a "take-charge" type of guy, but in the pilot's seat, I'm in command -- it's one of the many things I really enjoy about flying. And there's probably a life lesson in there somewhere, about recognizing appropriate moments to take command of a situation.
Instrument training will resume next week, and I'm hoping to go flying this weekend in the sunshine!
Sunday, March 04, 2007
The last six weeks
Prior to this weekend, I flew only once in the last six weeks, thanks to the weather (days of very low visibility, followed by days of rain, followed by my vacation to Mexico, followed by days of rain) and my schedule (work...work....). That flight was February 14, and all I did was take a Cessna out into the pattern and do 3 landings, at Palo Alto. The great thing was, the landings were very good, right out of the gate! This was a first, after three weeks off, having my landings not deteriorate at all. So that was exciting.
The next time I flew after that was yesterday. There was some excitement on my way down to San Carlos; as I left home and got on the freeway, I watched as the usual complement of jets made their way in on final approach to SFO's runways 28. One of them was quite far off to the left (from its perspective) out over Highway 101, and banking rather steeply to the right. A moment later I looked again and it had leveled its wings and begun a climb. I watched as it retracted its landing gear. It's always interesting to watch a commercial jet do a go-around; it's a great reminder that it's a good tool for all of us!
When I got to San Carlos, I ran into my alternate instructor from my PPL, and he was going on about an incident he'd seen happen the previous day. Here is a link to the story. Basically according to my instructor, the pilot, an elderly gentleman who's known at SQL for not really being able to see very well, ended up pretty far out on final approach at 100' and hit some power lines. He somehow maintained control, told the tower he'd hit something, did a low pass so the tower could check out his gear, and proceeded to freak out once all the way around the pattern before landing safely with some relatively minor damage to the plane. Crazy stuff! We ended up talking about my approach toward instrument training, and he had a few suggestions for instructors who might suit my style, so I plan to start pursuing that soon.
For the actual flight, I took Warrior N81020 out of San Carlos and just flew down the coast. I was initially going to do some pattern work, but my instructor recommended I take the plane down the coast and enjoy the weather, so I did, and it turned out to be a great suggestion. Actually before I took off, during preflight I noticed that one of the landing gear struts was inflated way more than the other. When I sat in the plane, I was tilted noticeably to the left. I had read the squawk sheet, and it had said the right strut was low -- I guess whoever pumped it up did not hold back, because it was very high now. I got out the POH and looked to see if there was a range of acceptable inflation, or just a minimum. Turns out it was just a minimum, which both sides met, so finally I decided to just go. It was nice to just fly the plane, concentrate on holding altitude, and look out the window. Pattern work is great, but it's a lot of work. This was a nice "it's good to be a pilot" flight. My landing back at SQL would've been fine if the runway were about 5 feet higher. As it was, I dropped it a touch harder than most would prefer. After that, the landing gear struts were nice and even!
I did want to try to work on my landing technique, which, while it may not have suffered after the initial 3 weeks off, seemed to have gone downhill after the subsequent 3 week break. So I went out again today, in N298CA, a 172SP out of PAO. Things were very busy in the PAO pattern, so I asked for a right Dumbarton and instead was granted a right crosswind. "You can ask for that any time," the controller said. How weird...so why would I ever want to take a right Dumbarton? It is easier to stay out of SJC's airspace when following the bridge, but really. I took the right crosswind (with a very nice takeoff) and went out to Livermore. They were using runways 7 instead of the usual 25, which was new for me. It was very busy there too, so I did one landing, taxied back and took off again for Palo Alto.
Back at PAO, I ended up doing 3 laps in the pattern. They were long laps as the controller struggled to get many departures out in between each landing. On my final lap, he had me extend my downwind out to Shoreline Amphitheater (which I'd done on the previous lap as well) and proceeded to line up two departures in front of my arrival. I'd slowed down considerably; basically any time my pattern gets extended I slow down as much as I'm comfortable with, usually no more than 80 knots on downwind with 10 degrees of flaps out. As I was on final, the controller decided he would try to get a third plane out. Here's where the new position and hold regulations come into play. He put the plane in position and hold, so I did not have a landing clearance, and here I was on a relatively short final. He said to me, "Cessna 8CA, one more aircraft holding in position for departure." I replied, "8CA, roger," but I must have sounded a bit apprehensive, because his reply was, "It's making me a little uneasy too." By this time I'd already decided that this was a good opportunity to try a short field landing, so my flaps were fully extended and I was at 60 knots. "I'm keeping it real slow," I told him, and he thanked me.
My short field landing was terrible, though I managed to rescue the landing itself for a soft touchdown, but it was time to terminate. Hopefully I'll be getting more practice in more regularly over the next few weeks!
The next time I flew after that was yesterday. There was some excitement on my way down to San Carlos; as I left home and got on the freeway, I watched as the usual complement of jets made their way in on final approach to SFO's runways 28. One of them was quite far off to the left (from its perspective) out over Highway 101, and banking rather steeply to the right. A moment later I looked again and it had leveled its wings and begun a climb. I watched as it retracted its landing gear. It's always interesting to watch a commercial jet do a go-around; it's a great reminder that it's a good tool for all of us!
When I got to San Carlos, I ran into my alternate instructor from my PPL, and he was going on about an incident he'd seen happen the previous day. Here is a link to the story. Basically according to my instructor, the pilot, an elderly gentleman who's known at SQL for not really being able to see very well, ended up pretty far out on final approach at 100' and hit some power lines. He somehow maintained control, told the tower he'd hit something, did a low pass so the tower could check out his gear, and proceeded to freak out once all the way around the pattern before landing safely with some relatively minor damage to the plane. Crazy stuff! We ended up talking about my approach toward instrument training, and he had a few suggestions for instructors who might suit my style, so I plan to start pursuing that soon.
For the actual flight, I took Warrior N81020 out of San Carlos and just flew down the coast. I was initially going to do some pattern work, but my instructor recommended I take the plane down the coast and enjoy the weather, so I did, and it turned out to be a great suggestion. Actually before I took off, during preflight I noticed that one of the landing gear struts was inflated way more than the other. When I sat in the plane, I was tilted noticeably to the left. I had read the squawk sheet, and it had said the right strut was low -- I guess whoever pumped it up did not hold back, because it was very high now. I got out the POH and looked to see if there was a range of acceptable inflation, or just a minimum. Turns out it was just a minimum, which both sides met, so finally I decided to just go. It was nice to just fly the plane, concentrate on holding altitude, and look out the window. Pattern work is great, but it's a lot of work. This was a nice "it's good to be a pilot" flight. My landing back at SQL would've been fine if the runway were about 5 feet higher. As it was, I dropped it a touch harder than most would prefer. After that, the landing gear struts were nice and even!
I did want to try to work on my landing technique, which, while it may not have suffered after the initial 3 weeks off, seemed to have gone downhill after the subsequent 3 week break. So I went out again today, in N298CA, a 172SP out of PAO. Things were very busy in the PAO pattern, so I asked for a right Dumbarton and instead was granted a right crosswind. "You can ask for that any time," the controller said. How weird...so why would I ever want to take a right Dumbarton? It is easier to stay out of SJC's airspace when following the bridge, but really. I took the right crosswind (with a very nice takeoff) and went out to Livermore. They were using runways 7 instead of the usual 25, which was new for me. It was very busy there too, so I did one landing, taxied back and took off again for Palo Alto.
Back at PAO, I ended up doing 3 laps in the pattern. They were long laps as the controller struggled to get many departures out in between each landing. On my final lap, he had me extend my downwind out to Shoreline Amphitheater (which I'd done on the previous lap as well) and proceeded to line up two departures in front of my arrival. I'd slowed down considerably; basically any time my pattern gets extended I slow down as much as I'm comfortable with, usually no more than 80 knots on downwind with 10 degrees of flaps out. As I was on final, the controller decided he would try to get a third plane out. Here's where the new position and hold regulations come into play. He put the plane in position and hold, so I did not have a landing clearance, and here I was on a relatively short final. He said to me, "Cessna 8CA, one more aircraft holding in position for departure." I replied, "8CA, roger," but I must have sounded a bit apprehensive, because his reply was, "It's making me a little uneasy too." By this time I'd already decided that this was a good opportunity to try a short field landing, so my flaps were fully extended and I was at 60 knots. "I'm keeping it real slow," I told him, and he thanked me.
My short field landing was terrible, though I managed to rescue the landing itself for a soft touchdown, but it was time to terminate. Hopefully I'll be getting more practice in more regularly over the next few weeks!
Sunday, January 21, 2007
What a weekend!
I'm exhausted. In the last three days, I've logged 5.5 hours of flight time. Hopefully no "real" pilots read this blog, because I just lost all credibility with them, but seriously, the flying was great but it wore me out.
First, Nirmala and I went to visit her parents down in Lompoc. Lompoc is right next to Vandenberg AFB, which makes it a little tricky to maneuver in without breaking military airspace, which is pretty much always a bad idea. We flew down on Friday, and back today, taking 1.9 hours down and 2.2 hours back. The flight down was absolutely great -- the weather was beautiful, and we had a strong tailwind so we got down there in 1:40, which is not only incredible, but also exactly what was predicted by my flight plan. It amazes me how accurate the planning process can be! The one thing I missed was the turn to head for Lompoc, but ATC caught me (yet another advantage of flight following): "4335K, confirm your destination is Lompoc." "Affirmative..." (turning to the right)
The flight back was a little harder. Most of it was fine, and I managed to get the autopilot to work for part of the time, but once we got into the Bay Area, it was really busy, and pretty turbulent. We got knocked around pretty good coming over the hills from Watsonville. My approach to landing at SQL was pretty rough, but the landing itself was quite good (the one at Lompoc was a bit hard due to a high flare).
Then, I took the same plane out to Petaluma tonight -- my band Hookslide was opening for Tower Of Power at the Mystic Theater in Petaluma, so I thought it'd be a great opportunity to fly up. So off I went, and it was a decent enough flight except, again, for the turbulence, especially close to Petaluma. Oh, and I ended up waiting 40 minutes for a cab! The flight was only 40 minutes; I could have driven and gotten there quicker! I was so upset.
The flight back was again turbulent after takeoff, but smoothed out as I approached San Francisco. I did the Class B transition well (the outbound one as well), and came in for landing at San Carlos. The tower was closed, so I decided to head for runway 30 after coming overhead and totally failing to see the windsock. I set up, made for the runway, flared, leveled off, and....OUCH I hit the nosewheel first -- holy cow, I've never done that before. It wasn't too bad, but it was not good. The Cherokee requires more force on the yoke than the Cessnas, and I think I really needed to manhandle the plane into a nose up attitude at that point, and didn't.
Anyway, I logged 5.5 hours total, 4.1 cross country. That gives me 10.6 hours for the month, and the month isn't over yet! Very exciting.
First, Nirmala and I went to visit her parents down in Lompoc. Lompoc is right next to Vandenberg AFB, which makes it a little tricky to maneuver in without breaking military airspace, which is pretty much always a bad idea. We flew down on Friday, and back today, taking 1.9 hours down and 2.2 hours back. The flight down was absolutely great -- the weather was beautiful, and we had a strong tailwind so we got down there in 1:40, which is not only incredible, but also exactly what was predicted by my flight plan. It amazes me how accurate the planning process can be! The one thing I missed was the turn to head for Lompoc, but ATC caught me (yet another advantage of flight following): "4335K, confirm your destination is Lompoc." "Affirmative..." (turning to the right)
The flight back was a little harder. Most of it was fine, and I managed to get the autopilot to work for part of the time, but once we got into the Bay Area, it was really busy, and pretty turbulent. We got knocked around pretty good coming over the hills from Watsonville. My approach to landing at SQL was pretty rough, but the landing itself was quite good (the one at Lompoc was a bit hard due to a high flare).
Then, I took the same plane out to Petaluma tonight -- my band Hookslide was opening for Tower Of Power at the Mystic Theater in Petaluma, so I thought it'd be a great opportunity to fly up. So off I went, and it was a decent enough flight except, again, for the turbulence, especially close to Petaluma. Oh, and I ended up waiting 40 minutes for a cab! The flight was only 40 minutes; I could have driven and gotten there quicker! I was so upset.
The flight back was again turbulent after takeoff, but smoothed out as I approached San Francisco. I did the Class B transition well (the outbound one as well), and came in for landing at San Carlos. The tower was closed, so I decided to head for runway 30 after coming overhead and totally failing to see the windsock. I set up, made for the runway, flared, leveled off, and....OUCH I hit the nosewheel first -- holy cow, I've never done that before. It wasn't too bad, but it was not good. The Cherokee requires more force on the yoke than the Cessnas, and I think I really needed to manhandle the plane into a nose up attitude at that point, and didn't.
Anyway, I logged 5.5 hours total, 4.1 cross country. That gives me 10.6 hours for the month, and the month isn't over yet! Very exciting.
Wednesday, January 17, 2007
Instrument Written Test -- Complete!
Last weekend, I made it through the rest of the King Instrument DVDs. Now, these DVDs are excellent; however, by "excellent" I mean that they present the information needed for test preparation in a very clear, concise and memorable manner. In the end, though, it's still studying for a test, and therefore pretty painful. So I just powered through the rest of the DVDs and called it quits.
Incidentally, these DVDs had a problem on my computer (Windows XP) where any attempt to watch a second video clip would cause the application to crash hard. This is of course problematic, because the course is structured in such a way that you have to watch a video clip, then answer questions, then watch another video clip. I had been quitting the application after answering questions, before the next video clip, and restarting it. What a pain! I tried getting a new DVD drive, but to no avail. Finally I ended up downloading a codec pack from freecodecs.com, and somehow installing that fixed whatever the problem was. I guess the biggest reason to put this info in here is just in case someone else has that problem and manages to type the right search words into their favorite search engine.
Anyway, so I finished the DVDs, fixing a technical problem along the way. Monday morning, I was feeling pretty good about myself, so I took a practice exam: 2 wrong, 97%. Pretty good! Later on Monday, I had to go down to the flying club to do some paperwork for a Piper Warrior checkout. I told my instructor about my result, and asked him for an endorsement to take the exam, which he gave me. This saved me a lot of time; my other option was to get the endorsement from King, but to do that, I would have had to take three practice exams, mail or fax the results to them, and have them mail me the endorsement. So, with my endorsement, I reserved the club's CATS testing room, and called up CATS testing: "I'd like to take the instrument airplane exam." "When?" "Tomorrow at 8:30 am." "Sure, no problem."
So Tuesday morning, after scraping ICE off my car window (I know, I know, what am I complaining about...but I live in the San Francisco Bay Area!! This is NOT normal!!!), I got to the club only five minutes late (the 20 minute drive took 55 minutes, thanks to traffic), and started the test in the unheated room. I went through the questions at a pretty deliberate pace, but it still took me about an hour and five minutes. There was one question I kept vacillating on; the rest, I either knew or I had no idea. I submitted the results, and...97%, I missed 2 again! At least I'm consistent...
Based on the codes they gave me, I could guess at the questions I missed. One was, when does the pressure altitude equal the true altitude? I chose "when the atmospheric pressure is 29.92" but the correct answer was "in standard atmospheric conditions." This is the question that I spent a long time deliberating on -- I have the unfortunate ability to justify anything in my head, so I basically justified the wrong one with faulty logic. The bottom line? Temperature DOES matter. The other question had to do with what services were available on a given ILS frequency, and it came down to whether it has TACAN or not. I believe I said it did, whereas it did not. I have not yet looked up how to determine that, but I figure I'll be learning that in my flight lessons.
About flight lessons -- I'm not really sure how to handle this. Sergey is only instructing part time now, as is his first recommendation. And I'm still toying with the idea of doing a 9-day course, though it seems less appealing now than it did before. We shall see; it should be a fun process no matter what!
Meanwhile, weather permitting, we'll be flying out to Lompoc to see Nirmala's parents this weekend, and then back up to Petaluma on Sunday for a show, opening for Tower Of Power. Sweet!
Incidentally, these DVDs had a problem on my computer (Windows XP) where any attempt to watch a second video clip would cause the application to crash hard. This is of course problematic, because the course is structured in such a way that you have to watch a video clip, then answer questions, then watch another video clip. I had been quitting the application after answering questions, before the next video clip, and restarting it. What a pain! I tried getting a new DVD drive, but to no avail. Finally I ended up downloading a codec pack from freecodecs.com, and somehow installing that fixed whatever the problem was. I guess the biggest reason to put this info in here is just in case someone else has that problem and manages to type the right search words into their favorite search engine.
Anyway, so I finished the DVDs, fixing a technical problem along the way. Monday morning, I was feeling pretty good about myself, so I took a practice exam: 2 wrong, 97%. Pretty good! Later on Monday, I had to go down to the flying club to do some paperwork for a Piper Warrior checkout. I told my instructor about my result, and asked him for an endorsement to take the exam, which he gave me. This saved me a lot of time; my other option was to get the endorsement from King, but to do that, I would have had to take three practice exams, mail or fax the results to them, and have them mail me the endorsement. So, with my endorsement, I reserved the club's CATS testing room, and called up CATS testing: "I'd like to take the instrument airplane exam." "When?" "Tomorrow at 8:30 am." "Sure, no problem."
So Tuesday morning, after scraping ICE off my car window (I know, I know, what am I complaining about...but I live in the San Francisco Bay Area!! This is NOT normal!!!), I got to the club only five minutes late (the 20 minute drive took 55 minutes, thanks to traffic), and started the test in the unheated room. I went through the questions at a pretty deliberate pace, but it still took me about an hour and five minutes. There was one question I kept vacillating on; the rest, I either knew or I had no idea. I submitted the results, and...97%, I missed 2 again! At least I'm consistent...
Based on the codes they gave me, I could guess at the questions I missed. One was, when does the pressure altitude equal the true altitude? I chose "when the atmospheric pressure is 29.92" but the correct answer was "in standard atmospheric conditions." This is the question that I spent a long time deliberating on -- I have the unfortunate ability to justify anything in my head, so I basically justified the wrong one with faulty logic. The bottom line? Temperature DOES matter. The other question had to do with what services were available on a given ILS frequency, and it came down to whether it has TACAN or not. I believe I said it did, whereas it did not. I have not yet looked up how to determine that, but I figure I'll be learning that in my flight lessons.
About flight lessons -- I'm not really sure how to handle this. Sergey is only instructing part time now, as is his first recommendation. And I'm still toying with the idea of doing a 9-day course, though it seems less appealing now than it did before. We shall see; it should be a fun process no matter what!
Meanwhile, weather permitting, we'll be flying out to Lompoc to see Nirmala's parents this weekend, and then back up to Petaluma on Sunday for a show, opening for Tower Of Power. Sweet!
Sunday, January 14, 2007
Hey, hey, where ya goin'?
Last TuesdayI met up with Sergey to get checked out in the Piper Warrior, mostly to try to save some money. It's the same plane as the Archer, but less powerful and cheaper. The 172SPs are much more expensive than either one; for that reason I'm thinking of doing my IFR training in a Warrior.
At my request we landed at San Jose, which is in Class C airspace. I just wanted to go over the operations and takeoff clearance stuff; it had been a long time since we'd done that in lessons. That lesson was totally great; I made two excellent landings (no winds in a Warrior means about as easy a landing as there could be), and it was great to see Sergey again.
So today, I put my refreshed knowledge to the test, and went on a trip to Monterey. Monterey is a Class C airport, about 60NM from San Carlos. I wanted to build on everything I have been doing: Flight following, cross countries, all that good stuff. I originally wanted to do the transition through Palo Alto, Moffett and San Jose, but the route over the hills seemed much more direct.
I took a Woodside departure out of SQL and after crossing the 280 freeway made a left. Over SLAC, I hesitated: I was not sure about which of my three route options were the best (over the hills, through San Jose, or coastal). So I circled twice and had a look around. There were a few clouds over the hills, so I wanted to avoid the most direct route (despite the fact that it was almost certainly not a problem; I just finished reading about standing lenticular clouds over mountains meaning heavy turbulence and I got paranoid). The San Jose route at this point would've been strange, since I'd have to fly toward Palo Alto, get transition clearance, make a right turn and then continue the flight. Not impossible, just unconventional. Meanwhile, the coast looked absolutely beautiful, so I turned and headed west for the ocean.
Once on the coastline, I called Norcal Approach for flight following, and set my altitude at 5500. I had a really easy time holding my altitude today; I was on the button with it. I was told at some point early on to make right traffic runway 28R, so I kept that in mind as I followed the coast. As I passed abeam Watsonville, I began my descent, and a few minutes later was told to fly heading 150 to intersect the right base for 28L. Cool, I get to land on the BIG runway!
I descended to TPA just as I entered what would've been a normal base leg. Unfortunately the TPA was 1500' AGL (above ground level), which is not something I'd dealt with before -- usually it's 800' to 1000'. So I had to make a pretty rapid descent on final; I even employed a forward slip for the first time. But I wasn't too worried since I had a gigantic runway in front of me and a decent headwind. My landing, after the somewhat abrupt leveling off process, was smooth and centered.
I taxied back and got my takeoff clearance, and flew back up the coast at 4500'. I stayed with Norcal Approach, but I think they lost me at some point. I heard, "Cessna 610SP, Norcal Approach." I answered: "Approach, Cessna 610SP." That happened twice, then a third time with a different controller. After the third time, I called them: "Norcal Approach, Cessna 610SP." They responded: "Cessna 610SP, go ahead." I didn't know what to say. "0SP, Making contact, I think I lost radio contact a few minutes ago." They responded with "Radar service terminated, squawk VFR." Um...OK, apparently I blew it, but I'm not really sure how (if anyone reading this has a clue for me, I'd gladly take it).
I tuned my VOR to Woodside and chose radial 240 after consulting the charts and seeing that crossing that radial put me under the 4000' shelf of SFO's class B airspace. I turned inward and crossed the hills just in time to put me at the south tip of the Crystal Springs Reservoir. I called up SQL tower, came in and landed...decently. There was a bit of a crosswind, which I corrected for well, but leveled off high at first. But I corrected and touched down pretty softly.
All in all, it was a good flight. What I didn't do was plan out checkpoints and time my progress, as I should be doing. It was a short enough flight that it didn't really matter, but I need more practice doing that. I guess it's time to take some longer flights where it does matter!
At my request we landed at San Jose, which is in Class C airspace. I just wanted to go over the operations and takeoff clearance stuff; it had been a long time since we'd done that in lessons. That lesson was totally great; I made two excellent landings (no winds in a Warrior means about as easy a landing as there could be), and it was great to see Sergey again.
So today, I put my refreshed knowledge to the test, and went on a trip to Monterey. Monterey is a Class C airport, about 60NM from San Carlos. I wanted to build on everything I have been doing: Flight following, cross countries, all that good stuff. I originally wanted to do the transition through Palo Alto, Moffett and San Jose, but the route over the hills seemed much more direct.
I took a Woodside departure out of SQL and after crossing the 280 freeway made a left. Over SLAC, I hesitated: I was not sure about which of my three route options were the best (over the hills, through San Jose, or coastal). So I circled twice and had a look around. There were a few clouds over the hills, so I wanted to avoid the most direct route (despite the fact that it was almost certainly not a problem; I just finished reading about standing lenticular clouds over mountains meaning heavy turbulence and I got paranoid). The San Jose route at this point would've been strange, since I'd have to fly toward Palo Alto, get transition clearance, make a right turn and then continue the flight. Not impossible, just unconventional. Meanwhile, the coast looked absolutely beautiful, so I turned and headed west for the ocean.
Once on the coastline, I called Norcal Approach for flight following, and set my altitude at 5500. I had a really easy time holding my altitude today; I was on the button with it. I was told at some point early on to make right traffic runway 28R, so I kept that in mind as I followed the coast. As I passed abeam Watsonville, I began my descent, and a few minutes later was told to fly heading 150 to intersect the right base for 28L. Cool, I get to land on the BIG runway!
I descended to TPA just as I entered what would've been a normal base leg. Unfortunately the TPA was 1500' AGL (above ground level), which is not something I'd dealt with before -- usually it's 800' to 1000'. So I had to make a pretty rapid descent on final; I even employed a forward slip for the first time. But I wasn't too worried since I had a gigantic runway in front of me and a decent headwind. My landing, after the somewhat abrupt leveling off process, was smooth and centered.
I taxied back and got my takeoff clearance, and flew back up the coast at 4500'. I stayed with Norcal Approach, but I think they lost me at some point. I heard, "Cessna 610SP, Norcal Approach." I answered: "Approach, Cessna 610SP." That happened twice, then a third time with a different controller. After the third time, I called them: "Norcal Approach, Cessna 610SP." They responded: "Cessna 610SP, go ahead." I didn't know what to say. "0SP, Making contact, I think I lost radio contact a few minutes ago." They responded with "Radar service terminated, squawk VFR." Um...OK, apparently I blew it, but I'm not really sure how (if anyone reading this has a clue for me, I'd gladly take it).
I tuned my VOR to Woodside and chose radial 240 after consulting the charts and seeing that crossing that radial put me under the 4000' shelf of SFO's class B airspace. I turned inward and crossed the hills just in time to put me at the south tip of the Crystal Springs Reservoir. I called up SQL tower, came in and landed...decently. There was a bit of a crosswind, which I corrected for well, but leveled off high at first. But I corrected and touched down pretty softly.
All in all, it was a good flight. What I didn't do was plan out checkpoints and time my progress, as I should be doing. It was a short enough flight that it didn't really matter, but I need more practice doing that. I guess it's time to take some longer flights where it does matter!
Saturday, January 06, 2007
Two Niner Diner
We flew from SQL up to Petaluma to have brunch at the Two Niner Diner this morning. The weather was absolutely beautiful; the winds over the last couple of days have pushed all the pollution off probably into the central valley or someplace. Yesterday the visibility was amazing; I could see Mt. Diablo from Palo Alto as if it was right next to me. Today was not quite as amazing, but still very good.
I booked N35583, a Cessna 172SP out of San Carlos. We got to the airport around 10:00, and went out to preflight. Nice looking plane; great interior and very nice GPS. Things were going fine, until...why is no fuel coming out of the front bottom fuel drain? Hmm. I tried again, and again. All the other drains were fine, but this one refused to budge. I saw that if I held the collecting jar in, liquid started coming out, one drop at a time. I held it there for a while, and looked at it. It was hard to tell, but it didn't really look blue. I threw out the sample and tried again. Same result. So my best theory is that there was ice in the lines, or at least water (though I don't know why water wouldn't have just flowed out).
So we got N236SP instead. Other than the oil being really low (I refilled), it looked fine, so I contacted ground and asked for a Bravo transition to Petaluma. After I taxied to runway 30 and did my runup, I was still waiting for a squawk code. Eventually I pinged SQL ground and asked if I should stay with them and wait, or go to tower. They came back with a code right away; I guess they'd just forgotten about me.
We took a straight out departure, and for once the voyage through Class B was totally uneventful. The eventfulness happened just above the Golden Gate, when Norcal Approach gave me a traffic alert, and then advised a 500' descent and 40 degree left turn ASAP -- naturally I complied. Score another one for flight following!
The rest of the trip out to Petaluma was smooth and scenic, other than not being able to see any of the traffic to which Norcal was alerting me. My pattern entry was good, but by the time I was turning base (early, at that), there were two other planes on downwind, so I was feeling a tad rushed. The early base turn led to a high approach, but full flaps and idle power got me down in time. I leveled off slightly high, but no big deal, just not the smoothest landing ever.
The food at Two Niner Diner was quite good! We shared a veggie omelette, which came with potatoes and coffee cake. The omelette was excellent; the eggs were really thin and properly cooked (i.e. not overcooked), and the vegetables were properly done and really flavorful. The rest of the food was pretty good (not amazing, but definitely not disappointing) as well.
A few clouds had started to develop by the time we headed back. One of them forced us to go around it, but nothing too traumatic. I contacted Oakland Center as soon as my ascent was complete (hooray for me!), and they routed me back through SFO's airspace. This time I got sent over midfield of SFO, which was a new view for my travel-mate Nirmala. Back at San Carlos, there was a mild crosswind, so I took the opportunity to practice all the crosswind technique I'd learned last summer. And, voila, probably my nicest crosswind landing ever! Smooth touchdown on the upwind wheel, nose pointed straight down the runway, right on the center line. It helped that the crosswind was really mild, but it was enough that my approach was crabbing in.
The only downside to the journey is that since I took off from San Carlos instead of Palo Alto, the distance to Petaluma does not quite qualify for cross country time. But that's alright; today was about having an enjoyable experience, not necessarily being goal oriented.
I booked N35583, a Cessna 172SP out of San Carlos. We got to the airport around 10:00, and went out to preflight. Nice looking plane; great interior and very nice GPS. Things were going fine, until...why is no fuel coming out of the front bottom fuel drain? Hmm. I tried again, and again. All the other drains were fine, but this one refused to budge. I saw that if I held the collecting jar in, liquid started coming out, one drop at a time. I held it there for a while, and looked at it. It was hard to tell, but it didn't really look blue. I threw out the sample and tried again. Same result. So my best theory is that there was ice in the lines, or at least water (though I don't know why water wouldn't have just flowed out).
So we got N236SP instead. Other than the oil being really low (I refilled), it looked fine, so I contacted ground and asked for a Bravo transition to Petaluma. After I taxied to runway 30 and did my runup, I was still waiting for a squawk code. Eventually I pinged SQL ground and asked if I should stay with them and wait, or go to tower. They came back with a code right away; I guess they'd just forgotten about me.
We took a straight out departure, and for once the voyage through Class B was totally uneventful. The eventfulness happened just above the Golden Gate, when Norcal Approach gave me a traffic alert, and then advised a 500' descent and 40 degree left turn ASAP -- naturally I complied. Score another one for flight following!
The rest of the trip out to Petaluma was smooth and scenic, other than not being able to see any of the traffic to which Norcal was alerting me. My pattern entry was good, but by the time I was turning base (early, at that), there were two other planes on downwind, so I was feeling a tad rushed. The early base turn led to a high approach, but full flaps and idle power got me down in time. I leveled off slightly high, but no big deal, just not the smoothest landing ever.
The food at Two Niner Diner was quite good! We shared a veggie omelette, which came with potatoes and coffee cake. The omelette was excellent; the eggs were really thin and properly cooked (i.e. not overcooked), and the vegetables were properly done and really flavorful. The rest of the food was pretty good (not amazing, but definitely not disappointing) as well.
A few clouds had started to develop by the time we headed back. One of them forced us to go around it, but nothing too traumatic. I contacted Oakland Center as soon as my ascent was complete (hooray for me!), and they routed me back through SFO's airspace. This time I got sent over midfield of SFO, which was a new view for my travel-mate Nirmala. Back at San Carlos, there was a mild crosswind, so I took the opportunity to practice all the crosswind technique I'd learned last summer. And, voila, probably my nicest crosswind landing ever! Smooth touchdown on the upwind wheel, nose pointed straight down the runway, right on the center line. It helped that the crosswind was really mild, but it was enough that my approach was crabbing in.
The only downside to the journey is that since I took off from San Carlos instead of Palo Alto, the distance to Petaluma does not quite qualify for cross country time. But that's alright; today was about having an enjoyable experience, not necessarily being goal oriented.
Tuesday, January 02, 2007
Tracy and back again
We went out for a simple, short flight to Tracy and back in Cherokee 4319D. But no flight is without its share of adventure, and this was no exception. We left San Carlos at about 4:15, and when we got to Tracy, the pattern was busy. A C150 in front of me decided to do a 360 to get out of the way of myself and the Cirrus behind me. I thought about getting out of the way too, as the Cirrus was pretty close behind me, but then just decided that as long as I don't dilly dally my way through the pattern, it would be fine. It was, and it was my nicest touchdown ever in a Cherokee. And I got off at the first taxiway, which was a good thing -- as I cleared the runway, I looked back and the Cirrus was about 2 seconds from touching down.
Getting out of the airport was another challenge. Everything was locked up! It seemed like there was no way out, but then we found a gate where there was a button to open it for pedestrians to exit. OK, great, but how would we get back in? We figured out that Nirmala, my travel companion, was actually small enough to squeeze through the closed gate. So after a nice time at our friends' place, we broke back into the airport and went back to the plane.
We took off into the beautiful night sky, and just admired the lights from above. Traffic was so light that even I wasn't worried. We touched 4500' and immediately began our descent to get under SFO's Class B airspace above us -- it seemed like as soon as we got to cruise altitude we could actually see San Carlos off in the distance. Then, of course, there was a complication: The panel lights decided they were going to flicker on and off in the most annoying possible fashion. Now, I had two flashlights with me. One was decidedly too bright, and the other was on its last legs (I have a cool LED white/red flashlight coming that I ordered a couple of weeks ago, but for some reason it's not here yet). So I ended up having to perform the landing without having a clear read on my airspeed indicator. It wasn't that hard, it was just an additional challenge. But, it was probably my second best touchdown in a Cherokee! Finally Nirmala is convinced that I can land!
Also, I'm making significant headway in the King Instrument DVD course. I am through the section about instrument approaches, which was probably the biggest and most foreign section to me. Martha King does a great job explaining all the concepts -- I haven't taken the test yet, but so far I highly recommend this course!
My next step in flight training will hopefully be to go land and take off from a Class C airport, so I get familiar with takeoff clearances and all that. Minor thing, I could probably figure it out, but it's also a good way for me to audition instructors for further training.
Getting out of the airport was another challenge. Everything was locked up! It seemed like there was no way out, but then we found a gate where there was a button to open it for pedestrians to exit. OK, great, but how would we get back in? We figured out that Nirmala, my travel companion, was actually small enough to squeeze through the closed gate. So after a nice time at our friends' place, we broke back into the airport and went back to the plane.
We took off into the beautiful night sky, and just admired the lights from above. Traffic was so light that even I wasn't worried. We touched 4500' and immediately began our descent to get under SFO's Class B airspace above us -- it seemed like as soon as we got to cruise altitude we could actually see San Carlos off in the distance. Then, of course, there was a complication: The panel lights decided they were going to flicker on and off in the most annoying possible fashion. Now, I had two flashlights with me. One was decidedly too bright, and the other was on its last legs (I have a cool LED white/red flashlight coming that I ordered a couple of weeks ago, but for some reason it's not here yet). So I ended up having to perform the landing without having a clear read on my airspeed indicator. It wasn't that hard, it was just an additional challenge. But, it was probably my second best touchdown in a Cherokee! Finally Nirmala is convinced that I can land!
Also, I'm making significant headway in the King Instrument DVD course. I am through the section about instrument approaches, which was probably the biggest and most foreign section to me. Martha King does a great job explaining all the concepts -- I haven't taken the test yet, but so far I highly recommend this course!
My next step in flight training will hopefully be to go land and take off from a Class C airport, so I get familiar with takeoff clearances and all that. Minor thing, I could probably figure it out, but it's also a good way for me to audition instructors for further training.
Saturday, December 30, 2006
Oroville!
Today I did the longest flight I've ever done. It was great! I planned a flight last night from San Carlos (SQL) to Oroville (OVE), a non-towered airport about the same latitude as Fort Bragg. My flight plan took me out of SQL, over the Sunol Golf Course, and then north over the 680 freeway, basically staying between Mt. Diablo on the right and the 4000' shelf of SFO's B airspace on the left, at 4500'. I had planned an early departure, around 9:00 am, but when I checked the weather in the morning, there was a lot of fog everywhere except in the Bay Area. I waited, and by 10:30 things were looking more clear (9SM visibility at the destination, pockets of 6 and 7 in between) and I figured as the day went on, things would clear up.
So I took off. The flight up was good, but again I had the same experience I did on my previous longest cross country (to King City, back almost a year ago), where I kept thinking about calling up Norcal Approach for flight following and then not doing it. I kept thinking about it, and I did keep switching frequencies and listening in, but I didn't call in for a long time. What finally persuaded me to call in was when I was coming up on the Williams VOR, and it seemed like there was a lot of traffic in the vicinity, so I called in finally. I found the airport without a problem, and there were other planes in the pattern so I used the same active runway as they did, 30. My touchdown was smooth and on the center line -- I couldn't have been happier with it! I taxied over to transient parking and tied down.
Turned out everything was closed at the airport! I called a cab, and asked to be taken to "a diner for lunch," so the driver took me to a local place that advertised breakfast for $1.99. That can't be good...but the Gardenburger I had was actually very good. After lunch I cabbed it back to the airport, and was in the air at 3:05pm.
Now, the visibility was a bigger issue. I was travelling primarily westbound for the first leg, right into the sun, and I couldn't see much at all. I got flight following right away, and it was a good thing, because there was another Cessna coming on the same route the opposite direction at the same altitude. The controller had me descend 500' to avoid him, and I never saw him. I decided based on the visibility, and my guess that it'd be clearer toward the coast, to abandon my plan and instead fly toward the Scaggs Island (SGD) VOR, and then to Sausalito and take an SFO Class B transition -- this also seemed to be what the controllers were expecting, and it was a shorter path, so I went with it.
The middle of the trip, between the Williams and SGD VORs, was actually stressful enough that I got out my portable GPS to verify what I was reading on the VOR indicator. The plane's GPS was out of commission, and the plane had no DME, so I really wanted some better indication of my position. The portable worked great, and I found my way OK. They cleared me through Class B automatically, and I flew it perfectly (though I did miss one instruction from the tower; I'm sure the jet pilots were rolling their eyes at my amateurish performance!). The SFO controller transferred me to the San Carlos tower, and I came in and landed again really smoothly and on the center line!
All in all, this was a really good flight. I think this really establishes my personal minimums for flight visibility -- 10SM for comfort, 6SM in a pinch and with flight following. Nothing less. Improvising in the air is always exhausting and difficult, and I think I did it pretty well this time. I changed my route, but I had my backup route in mind, and it was actually an easier route. I read the charts, made sure I had obstacle clearance and all that, and of course having flight following helped a lot. My landings in the Cessna were really good, which I'm really happy about!
On another note, I've been studying for the instrument written test. I tried reading the Jeppesen book, and learned a lot, but just didn't have the ability to visualize some of it. Also, the chart-reading sections are confusing because they teach you the FAA chart stuff as kind of a secondary step to teaching their own charts. Their charts do seem like they might be better, but the test is going to use FAA charts, so I don't want to confuse myself. So I ordered the King DVDs and have been working through them. They're quite good, and are really good about making me feel like I'm learning something. Whether I am or not, I guess we'll find out!
So I took off. The flight up was good, but again I had the same experience I did on my previous longest cross country (to King City, back almost a year ago), where I kept thinking about calling up Norcal Approach for flight following and then not doing it. I kept thinking about it, and I did keep switching frequencies and listening in, but I didn't call in for a long time. What finally persuaded me to call in was when I was coming up on the Williams VOR, and it seemed like there was a lot of traffic in the vicinity, so I called in finally. I found the airport without a problem, and there were other planes in the pattern so I used the same active runway as they did, 30. My touchdown was smooth and on the center line -- I couldn't have been happier with it! I taxied over to transient parking and tied down.
Turned out everything was closed at the airport! I called a cab, and asked to be taken to "a diner for lunch," so the driver took me to a local place that advertised breakfast for $1.99. That can't be good...but the Gardenburger I had was actually very good. After lunch I cabbed it back to the airport, and was in the air at 3:05pm.
Now, the visibility was a bigger issue. I was travelling primarily westbound for the first leg, right into the sun, and I couldn't see much at all. I got flight following right away, and it was a good thing, because there was another Cessna coming on the same route the opposite direction at the same altitude. The controller had me descend 500' to avoid him, and I never saw him. I decided based on the visibility, and my guess that it'd be clearer toward the coast, to abandon my plan and instead fly toward the Scaggs Island (SGD) VOR, and then to Sausalito and take an SFO Class B transition -- this also seemed to be what the controllers were expecting, and it was a shorter path, so I went with it.
The middle of the trip, between the Williams and SGD VORs, was actually stressful enough that I got out my portable GPS to verify what I was reading on the VOR indicator. The plane's GPS was out of commission, and the plane had no DME, so I really wanted some better indication of my position. The portable worked great, and I found my way OK. They cleared me through Class B automatically, and I flew it perfectly (though I did miss one instruction from the tower; I'm sure the jet pilots were rolling their eyes at my amateurish performance!). The SFO controller transferred me to the San Carlos tower, and I came in and landed again really smoothly and on the center line!
All in all, this was a really good flight. I think this really establishes my personal minimums for flight visibility -- 10SM for comfort, 6SM in a pinch and with flight following. Nothing less. Improvising in the air is always exhausting and difficult, and I think I did it pretty well this time. I changed my route, but I had my backup route in mind, and it was actually an easier route. I read the charts, made sure I had obstacle clearance and all that, and of course having flight following helped a lot. My landings in the Cessna were really good, which I'm really happy about!
On another note, I've been studying for the instrument written test. I tried reading the Jeppesen book, and learned a lot, but just didn't have the ability to visualize some of it. Also, the chart-reading sections are confusing because they teach you the FAA chart stuff as kind of a secondary step to teaching their own charts. Their charts do seem like they might be better, but the test is going to use FAA charts, so I don't want to confuse myself. So I ordered the King DVDs and have been working through them. They're quite good, and are really good about making me feel like I'm learning something. Whether I am or not, I guess we'll find out!
Friday, December 22, 2006
Practice
I flew a new (for me) Cherokee Archer out of PAO today, N81034. I've tended to shy away from the planes with "all numbers" call signs for some reason; I think I was afraid the call signs would be less identifiable by me in the air. No such problems today, and it turns out the plane was really, really nice! Nothing fancy, or anything, it was just totally solid and flew really well.
I took off out of PAO at about 4:30pm and stayed in the pattern for two landings. Both landings were excellent -- nice and soft, I remembered to look down the end of the runway (unlike last Friday). So I decided to head out to SQL. There I got a straight in landing clearance, but the controller (who's not the best, frankly) then got overloaded with 610SP in the pattern wanting a short approach and a King Air coming in faster than he'd thought. He made both me and the SP do a left 360, which for me was a little uncomfortable right over 101 between PAO and SQL at 1000'. But oh well. I came in and landed again very well, and taxied back.
I stayed in the SQL pattern for two more landings. I became steadily more precise both on holding pattern altitude and on following the VASI glide slope. I tried leaving the power on for the third landing, since it was getting dark, but I think that just served to confuse me and land a little harder. After the third landing I took a right downwind departure back towards PAO, and came in and landed again with the power on and again less smoothly than before. But still, pretty well.
All in all, a good day/night of practice!
I took off out of PAO at about 4:30pm and stayed in the pattern for two landings. Both landings were excellent -- nice and soft, I remembered to look down the end of the runway (unlike last Friday). So I decided to head out to SQL. There I got a straight in landing clearance, but the controller (who's not the best, frankly) then got overloaded with 610SP in the pattern wanting a short approach and a King Air coming in faster than he'd thought. He made both me and the SP do a left 360, which for me was a little uncomfortable right over 101 between PAO and SQL at 1000'. But oh well. I came in and landed again very well, and taxied back.
I stayed in the SQL pattern for two more landings. I became steadily more precise both on holding pattern altitude and on following the VASI glide slope. I tried leaving the power on for the third landing, since it was getting dark, but I think that just served to confuse me and land a little harder. After the third landing I took a right downwind departure back towards PAO, and came in and landed again with the power on and again less smoothly than before. But still, pretty well.
All in all, a good day/night of practice!
Tuesday, December 19, 2006
Nighttime In Modesto
I returned to Modesto for the first time since the Satanis....I mean, Stanislaus County Fair last August, in 610SP, a nice 172SP out of San Carlos. I thought I'd kill several birds with one stone by stopping at Palo Alto on my way back to San Carlos.
Things went well! I took off from SQL with a left crosswind departure off of runway 12, and proceeded over the mountains. I decided I really wanted to try to fly headings that I'd precalculated and not rely on the GPS, as much as possible. Once I got clear of Sunol Golf Course, my first waypoint, I tuned the VOR to Modesto, and went straight for it. Well...almost. Turns out hills are kind of scary at night, and even though I was at 5500 feet, and knew for a fact that I was not anywhere near any of the hills, I still kind of veered around the hills.
My landing in Modesto was good; I did need the GPS to track my distance from the airport on my way in, though, since either there was no DME or I couldn't figure out where it was. One mystery yet to be solved. I taxied back and took off on a straight out departure, and this time at 4500 feet decided I would fly directly to Sunol (using the GPS). I looked at my chart and saw that the minimum safe altitude was 4200, so I was safe by at least 600 feet including the 300 built into the MSA. So I did it, flew straight to Sunol, uneventfully, and then made for Palo Alto.
That landing was pretty crunchy. Nothing too bad, I just hit a little hard. No bouncing, though, so it couldn't have been too bad. I taxied back and made straight out for San Carlos, where I got a straight-in for 30. Decent landing there.
So, I'm now night current for 90 more days, I've added some cross country time to my total, and I think I've bumped my Cessna 172 currency as well. A good night!
Things went well! I took off from SQL with a left crosswind departure off of runway 12, and proceeded over the mountains. I decided I really wanted to try to fly headings that I'd precalculated and not rely on the GPS, as much as possible. Once I got clear of Sunol Golf Course, my first waypoint, I tuned the VOR to Modesto, and went straight for it. Well...almost. Turns out hills are kind of scary at night, and even though I was at 5500 feet, and knew for a fact that I was not anywhere near any of the hills, I still kind of veered around the hills.
My landing in Modesto was good; I did need the GPS to track my distance from the airport on my way in, though, since either there was no DME or I couldn't figure out where it was. One mystery yet to be solved. I taxied back and took off on a straight out departure, and this time at 4500 feet decided I would fly directly to Sunol (using the GPS). I looked at my chart and saw that the minimum safe altitude was 4200, so I was safe by at least 600 feet including the 300 built into the MSA. So I did it, flew straight to Sunol, uneventfully, and then made for Palo Alto.
That landing was pretty crunchy. Nothing too bad, I just hit a little hard. No bouncing, though, so it couldn't have been too bad. I taxied back and made straight out for San Carlos, where I got a straight-in for 30. Decent landing there.
So, I'm now night current for 90 more days, I've added some cross country time to my total, and I think I've bumped my Cessna 172 currency as well. A good night!
Subscribe to:
Posts (Atom)
Posts
