Showing posts with label flight planning. Show all posts
Showing posts with label flight planning. Show all posts

Sunday, September 10, 2000

Dual: First Cross-Country (ORH-PSF-ORH)

This was my first official dual cross-country (greater than 50 nm from home). It was a good one, with a lot of points to remember, so I better write it down while it’s still fresh in my mind. The cross-country planning went pretty well – I got all the airport info (just PSF and ORH, 64 nm, no third leg this time), estimated based on 90 knots airspeed, and did approximate calculations with zero winds. When I called 1-800-WXBRIEF and got the standard weather briefing with winds aloft, the 3000’ and 6000’ winds were both 6 knots, and the interpolated direction for 4500’ was 25° -- so not much wind and a gorgeous day all the way around (I actually called for a briefing at 8:30 am and was told ORH-PSF was “VFR not recommended” due to low ceilings and fog, so I briefly considered flying to Concord, NH instead – but when Mario arrived, I called again, and PSF was clear, so we stayed with plan A – I should have called the Pittsfield ASOS weather phone line directly – when I did later, it was clear).

The first big problem was that the plane wouldn’t start (it was N47261 – plan was for 661, but it was in the shop for a new engine). The battery was dead – someone had flown a night flight with the alternator light on, apparently (you should look for this and cycle the alternator half of the master switch in this plane). We spent half an hour trying to hand-prop the plane, and it finally turned over (with help from Bob Karman and another CFI, Bill – Mario hates hand-propping but he was the one who finally did it after maybe 20 tries). So we were off at 10:30 a.m. Next challenge was getting to runway 11 – only two taxiways were open (construction), so back-taxi on runway was required, slowing everything down. We back-taxied only part way (tower said expedite, traffic on base!), then turned around and did a short-field take off (stay on brakes, 10° flaps, full power, release brakes). We flew left base and departed downwind to the west (magnetic compass heading 297° according to my nav log). My timer and yoke mount worked well, as did the knee board with my nav log and sectional chart. Mario had his GPS mounted but I could not see the screen – he cheated a couple of times, confirming or correcting my assumed positions (though it was really pilotage, holding a heading, timing, and VOR for 90% of the flight).

Once clear of ORH air space, climbing up to 4500’ cruise altitude (west-bound, even thousands plus 500) we called Bridgeport radio (122.2) to activate the flight plan I had filed on the phone (a first for me). Then we called up Bradley Approach (119.0) and requested flight following (yet another first for me – we were near Tanner-Hiller airport and reported this). Good thing I had recorded all those frequencies on my nav log! They gave us a squawk code and new frequency, which I wrote down and entered (only advantage of 261 is the dual-frequency radio, so you can queue up the next needed frequency). Flight following showed its value very soon, over the Quabbin Reservoir – they called out traffic at our altitude, crossing in front of us, 3 miles – we looked but Mario and I could not see the traffic (I missed my chance to say “no joy” on the radio!). Bradley said “if you don’t have a visual, suggest you expedite descent to 4000 feet” – Mario said “my airplane” and dived us down there pretty fast. We then looked up and saw a 172 passing left to right, just about where we had been, maybe ½ mile away. Close one! We had a good view of Westover ARB to our SW at this point.

I had easily spotted Spencer Airport and the Quabbin south dam, and my next check point was Amherst, Mass – but we also had to avoid Northampton airport, just 4 nm away, due to parachute activity (jumpers away at 8500 feet). I diverted a bit north of my planned track and flew right over the UMass campus – I spotted Becky’s dorm area and took a quick picture.

We had trouble spotting the airport, which is right at a bend in the (Connecticut?) river. I spotted what I thought was the airport, though it looked like a dirt strip (www.airnav.com says it’s asphalt, 14/32, 3500 x 50 feet, oh well).

On the outbound leg, I tended to gain altitude up to 4600 feet or so, but Mario reminded me that holding the planned 4500 and planned heading are especially important with flight following – you must report any altitude changes. Visibility was pretty good from 4500’ though there was a lot of low haze. Our next check point was Albert Airport, a small private strip in the Berkshires. I never saw it, but as a backup, I tuned in the Chester VOR and established that I was on the expected 022° radial. I also spotted a carrot-shaped lake with a dam at its S end about 10 nm SE of our position and noted this on the chart (distinctively shaped lakes or lakes with dams and radio towers seem to be the best landmarks).

Now we were only 17 nm from Pittsfield, and I spotted a large town just over a hill with a radio tower – the chart confirmed that this was Pittsfield, and I spotted the airport just to the SW of the town, but very faint. I think Bradley terminated our flight following at this point, and I tuned in the ASOS to get winds and altimeter setting for PSF. I then called up the CTAF (122.7) and gave our position, requesting the active runway. It was 26 with right traffic. As we got closer, we could see the reason for right traffic – two hefty mountains that would be right in the way of a left pattern for 26 and 32. I swung to the NW, passing over downtown Pittsfield and a high, wooded mountain ridge to enter the pattern on a 45° to the downwind (TPA 2200 feet). With reminders from Mario, I called my position on each leg to Pittsfield traffic (which was nil at that point). I lined up and made a rather long, sloppy touch-and-go, climbing up over the hills that seemed to pop up rather quickly off the west end of the runway. Climbed back to TPA, then turned right to take up my course.

At this point I tuned in and called Bridgeport Radio (Flight Service Stations are called “something Radio” in flight) to close my flight plan to Pittsfield. Two strange things – I got Burlington FSS, and there was a mix-up on whether I had filed out and back (I had not, though I thought I did when I told the weather briefer that I was coming right back, only a momentary stop at PSF – Burlington FSS closed my flight plan for me). So we flew back without a flight plan, but we contacted Bradley on the last-used frequency (good thing I wrote it down!) and resumed flight following.

I got the Bradley guy a little annoyed when I made several course changes over the next few minutes, trying again to swing a little north and avoid the parachuters around Northampton. He had to call me out several times to other planes because my course was changing. We also missed one or two calls for us – bad move – but we were busy and Mario was telling me stuff. We again flew over UMass and I tried to take another couple of pictures, but Mario got annoyed with this, because we also were trying (and failing) to spot an airplane that radar had told us was nearby (our 11 o’clock, climbing through 4500 – we were at 5500’ on the way home, as high as I have ever flown on my own).

Again I got my main checkpoints (Amherst, Quabbin dam) and we soon spotted ORH, a little patch of white just below the haze line to the east. We got Bradley’s OK to switch frequencies briefly to monitor ATIS, then we shortly asked to discontinue flight following so I could call up the tower. We requested a straight-in approach from around 10 miles out (since my return heading was 109 and runway 11 is 110), another first for me. We were told to report 3 mile final (Spencer airport is a good reference for this, it’s about 4 nm west of ORH). It was hard judging my descent from that far out, and I needed to keep my speed up because of following traffic. Tower said to land long (to avoid long taxi on runway) and turn left at taxiway Bravo, way down at the far end of 11, “no delay” due to following traffic (a 172 I think – the C152 is always the slowest thing in the pattern). I tend to land long anyway, so this was no problem!

All in all, a pretty good flight. I did most things right, kept track of my position, flew the airplane well (held 90 knots cruise and was right on 5500’ on the trip home). Now I’m ready for a three-leg cross-country next Sunday in Los Angeles (EMT-F70-CNO, El Monte, French Valley, Chino). Some things to keep in mind for future flights:
• For making minor course corrections when your hands are busy elsewhere (writing notes, tuning radio, etc.), the rudder pedals do a real nice job – smoother than yoke corrections! Of course you have to be trimmed well for this to work.
• It’s important to hold the planned course and altitude if you are on flight following – you want to be a predictable target.
• Call the local weather at the destination to get current conditions, don’t just rely on the weather briefer.
• If you want there-and-back flight plans, you have to tell the briefer this, it isn’t automatic, even if you tell them you are just doing a touch an go.
• Remember sunglasses, especially for the LA flight next weekend!

Time: 2.2 dual, 0.0 solo, TT TBD hrs, C152 at ORH

Sunday, August 06, 2000

Dual: Mini-Cross Country

There have been a lot of days when I've been outside, looked at the sky and thought, "what a gorgeous day -- I wish I were flying!" Well Saturday was one of those days, and I WAS flying. Blue skies with a scattering of puffy white fair-weather cumulus. A little bumpy here and there, but nice. This was all-dual, 1.7 hours C152 with Mario.

I used the airport directory and NY sectional chart to do most of the pre-flight planning for a mini-cross-country, flying ORH to ORE (Orange Muni, just N of the Quabbin) to FIT (Fitchburg, along Rt. 2, over Gardner -- even saw the Gardner VOR) and back over Sterling to ORH. I hoped to detour E to fly over West Boylston and the Wachusett Rsvr., but the first part of the flight took longer than expected. Even though it was too short to be an official cross-country, I figured it would be good practice to get all the info, mark up the chart, fill in the forms, and all that. Then on the flight, following the chart, looking for visual checkpoints, finding and approaching unfamiliar airports, etc. -- just like a real x-country. It's purely a "local" flight for Mario, but I never flew into any of these airports, so it was authentic to me! Total ground distance was only 68 NM, but flying around to properly enter the patterns probably doubled that!

Mario was impressed with my flight planning -- I even got the weather and winds aloft at 3000 feet (only 6 kts at 20 degrees) but I didn't complete the corrections in my navigation log. It was harder than I expected to follow the chart on my lap while juggling 6 or 7 frequencies (ORH's 120.5, ASOS and CTAF for ORE and FIT, CTAF for Gardner when we overflew the airport at 3000 feet, ATIS for ORH, back to 120.5). I also had to look for check point landmarks, plan my entry to each pattern, and fly the airplane! I forgot a lot of stuff along the way, but Mario said I did OK.

Things to note:
• Frequency congestion is a big problem -- 3 or 4 area uncontrolled airports use 122.8 as CTAF, including ORE, and it was very noisy. It took a while to figure out that 32 was the active runway, and it took me even longer to figure out how to enter the downwind at 45 degrees for this since I was approaching the airport on the runway heading! A straight-in approach is bad form at uncontrolled fields (people need to see where you are before you just show up on final). I ended up doing a big circle around the airport which took a long time.
• Watch altitude and airspeed! I climbed to 3300 or descended to 2800 a few times from my planned 3000 (not a normal VFR cruise altitude, but OK for less than 3000' AGL). I should have cruised faster on some legs -- 100 knots maybe. Pitch, power, trim! I should try using the rudders more for slight corrections to course (due to bumps or my wandering attention). If the airplane is trimmed well, it won't climb or drift so much when I'm fiddling with the radios. With flight-following on future x-countries, ATC will expect you to stay at your planned altitude.
• I need to practice forward slips at altitude! I came in high into FIT and Mario told me to do a forward slip. I aggressively pushed full right rudder as he had done earlier, and rolled left at the same time, but I pulled back on the yoke! BAD MOVE. Perfect cross-control set-up for a spin at maybe 1000 feet AGL. People die this way. Fortunately the C152 is forgiving and Mario caught it in time. I need work on this!
• I did OK finding the airports, though I didn't hold my planned magnetic course very well, and I didn't re-adjust the directional gyro to the whiskey compass until I passed Gardner and realized the heading could not be right if I were heading right for FIT (which I was). I got a few of my checkpoints, missed others.
• Over-flying Sterling is a bad plan due to glider traffic there – we stayed further west, passing just east of Mt. Wachusett. We saw two gliders well above us to the SE. There were also "parachuters away at 9500 feet" over ORE. These things made Mario a bit nervous. I was not worried (big sky theory, or maybe just naive?).
• GET ATIS! Before calling ORH on return I forgot to get ATIS until Mario hinted that I had forgotten something. I also need to review arrival and departure plans. It would have been nice to know the active runways before I got so close to ORE and FIT. I wish N67661 had a better radio (one with a button to toggle between active and standby frequencies -- then you can tune in the next one when you have a free moment and just flip it in when needed -- 261 has this but it climbs like a dead dog, so I'll stay with 661 when I can).
• I need a knee board for flights like this -- juggling the loose chart and the other paper where I had written the TPA and CTAF info was distracting. This is a small taste of cockpit management -- I could see this being VERY important on longer x-countries. I need a timer too -- and maybe bifocals! The text on the sectional is small and looking at my watch is distracting, but I need to be timing the legs of the flight, and restarting the timer at each leg!
• On departure, from uncontrolled fields, you need to climb straight out to TPA and depart on a 45 degree turn (R or L) from there. Then turn to heading when you are at least 500' above TPA. At a controlled field, if you get "right turn approved," you can turn to course any time, though you usually should clear the end of the runway first (but OK if you are not at TPA yet).
• Photos were cool since it was such a clear day, BUT... it IS distracting, even when I say "your airplane" for the shot. PLUS I need a point-and-shoot camera with telephoto. The wide-angle Samsung doesn't cut it.
• TRIM, TRIM, TRIM! Both for cruise and for pattern/approach. Trim for the speed I need! I don't do this enough, and I'm not consistent on altitudes because of this. I also play too much with the power, which is bad because it messes up your speed (and trim), which you are counting on to meet your flight plan. There are a lot of things to keep in mind up there!
• Need to practice VOR intercepts and localization in Fly! or X-plane -- I used the Gardner VOR (GDM, 110.6) one time to figure out where were along the first leg (since I couldn't find the Barre race track, my second check point), but I was awkward with it. Another thing to juggle!

There's more I'm sure but I need to get back to work here. I've scheduled my first totally solo flight for tomorrow (8/8) at 5 pm, to practice pattern work on my own at ORH, if the weather is OK and cross-wind is less than 4 knots. This is followed by an hour of ground time with Mario to plan a longer cross-country together. I need to do some prep for this tonight!

Time: 1.7 dual, 0.0 solo, TT 30.6/0.5 hrs, C152 at ORH

Thursday, August 03, 2000

Supplemental: Cross Country Pre-Planning

I'm starting to think seriously about cross-country flying, which will also help me prepare for the written test (charts, plotter, wind, etc.). I scheduled a lesson with Mario for 9:30 am Saturday and left him a voice mail suggesting we do a "mini-cross-country" as a change of pace from all the pattern work. I roughly planned this last night, deciding to fly to Orange (ORE) then to Fitchburg (FIT) and back to ORH. This is a total of 68 nm which should be 0.85 hours (51 minutes) if average ground speed is 80 knots. I picked out check points too. This should be pretty educational for local area familiarization -- pass near a couple of the nearby western airports, over Barre (which shows a race track on the sectional), near the north tip of the Quabbin and into ORE. Then east over Gardner Airport (and VOR, GDM) and into Fitchburg, finally SSW over Sterling, west of the Wachusett, over Holden (possible detour to West Boylston), and into ORH. With landings, this could be up close to 1.5 hours. I think it's a good intro to cross-country flying.

I also found my old Los Angeles VFR terminal area chart and thought about that cross-country on September 17. I think I'll plan to go down to French Valley, which is in the SE corner of the LA terminal chart, near Lake Elsinore, uncontrolled, about 55 nm SE of EMT. Then I'll see if we can stop at Chino on the way back to EMT -- that would be cool to land there myself!