Flying in Florida: Part 2

One day after I got to fly in Florida for the first time, I was scheduled to go up again with the same instructor — this time for a very different experience!

I finished up with the business conference I was at (my reason for being in Florida in the first place) and headed over to FA83, otherwise known as Orlando North Air Park.

FA83
Orlando North Air Park (FA83)

Yesterday’s flight had me cruising around with the downtown Orlando skyline in view… today’s setting couldn’t have been more different. FA83 is located in Zellwood, FL which is a pretty rural area. I put blind faith in my rental car’s GPS and it eventually paid off. I turned into the airport and… had no idea where to go. It was just a long road with hangers on the left and farm fields on the right. I didn’t see any runways or anything, so I just started down the road figuring I’d find something airport-like at the other end.

The road to... nowhere?
The road to… nowhere?

I eventually found the hangar for Van Anda Aviation, which is the FBO at FA83 and who I was renting today’s plane from. My CFI texted me that he was running late (hah! now we were even!) so I chatted up the Van Anda guys for a bit. It was my first real “hangar talk” — I guess I’m getting closer to being a real pilot now!

We were flying N12933 today, a C172M. This was a carbureted model, very similar to the one I fly in CT (same model, but this one was a 1973 versus the 1975 back home). While the plane was similar, the airport was not — this was an uncontrolled, private field that felt like it was in the middle of nowhere! It also had a shorter and narrower runway than I was used to — 50 feet wide and 2,600 feet long (with the runway extending as a turf strip an additional 1,400 feet). This was going to be interesting!

N12933

OK — so we get her preflighted and we’re off to the races. My instructor handles the radio work today since he knows I’m going to be a bit overloaded with the different environment. We take off and start flying a pattern.

One convenient thing about this area is that there are plenty of straight lines to use to gauge your ground track! Here’s a satellite picture from Google Maps — you can see there are lots of options to keep your pattern lined up (the runway is aligned horizontally and located a little left and below the center of the picture — under the vertical column of white hangars). There wasn’t a lot of wind today, but I still found the ground references helpful.

FA83 overhead view
FA83 overhead view

After yesterday’s work on landings, I thought I was going to kill it today. Turns out that was not the case at all. My first approach I turned on to final and everything was wrong. I was way too high, too fast, and the runway didn’t look right at all. Some of this was not being used to the sight picture of a narrow runway, some of it was because I wasn’t managing the plane properly.

We flew a lot of patterns. My landings pretty much all sucked. I porpoised some, I banged on the nosewheel some, I just couldn’t get the roundout and flare keyed in on this runway. My CFI took the controls to show me the approach and what it should look like and that helped a bit. One thing I liked about this instructor was he let me make mistakes like bouncing the plane. Then I had to fix the mistake — just like I would if he wasn’t in the plane! That took me a couple times to realize — the last time I porpoised I quickly hit the throttle and turned it into a go-around instead of trying to force the plane down when I had way too much energy.

We also visited a nearby grass strip — that was pretty wild! Talk about a different sight picture, now there was no real “runway” to speak of, just a nice flat patch of grass! I did a landing there and my CFI showed me the soft field takeoff technique, where you assume the ground is muddy and you want to prevent getting the nosewheel stuck. You never stop moving, and you keep pressure off the nosewheel by pulling aft on the yoke. You get the plane into ground effect and then pitch the nose down to keep it there and build up speed until you can start a normal climb.

Soon it was time for a full stop landing, so I got us on the ground and we headed back to the tie-down spot. I was disappointed with my performance during this flight, but my instructor told me not to be — after all, I had been given a ton of new variables to work with. I appreciated the positive attitude and I know he’s right, but it’s still a little frustrating to continue to struggle with what I feel are pretty basic tasks.

With that, my time boring holes in the skies of Florida had come to an end. I settled up my bill and headed to Orlando International (MCO) to catch my commercial flight back home.

I did remember to record today’s flight — click below to check out the CloudAhoy debrief.

CloudAhoy flight - 03/08/2017

Flight time today: 1.5 hours
Total flight time to date: 29.3 hours
Total takeoffs to date: 101
Total landings to date: 97

Flying in Florida: Part 1

I was scheduled to head down to Florida on business and I decided it would be fun to try and take a flight lesson with an instructor down there. After making a few calls, I scheduled two lessons during my trip with a local CFI who had been recommended to me.

My first lesson was flying out of Orlando Executive (KORL). Executive is a Class Delta airport in close proximity to downtown Orlando and Orlando International (KMCO) — it actually sits right under one of MCO’s Class Bravo shelves.

KORL

I was pretty nervous heading to my lesson as I had never flown with anyone besides my instructor back home. The ridiculous Orlando traffic (thanks to I-4 construction) certainly didn’t help my stress level. I would up being 20 minutes late, for which I apologized profusely! Way to make a good first impression.

I had spoken to the instructor on the phone and told him where I was at with my flying and that I wanted to work on landings. We sat and spoke for a bit before heading out to the plane and briefed how the lesson was going to go. We were planning on staying in the pattern and working exclusively on landings and pattern management.

We headed to the plane and did the preflight check. The plane was a 172R model — this model is fuel injected instead of carbureted, so the engine startup was slightly different. No big deal, though, and soon we were taxiing to the runup area.

I was having trouble steering the plane to the left — I would be pushing the rudder pedal all the way in and the plane would barely be turning to the left. I had to use the left brakes more than usual to keep the plane where I needed it. I should’ve mentioned this right away to my CFI but I thought it was more a pilot/technique issue than anything mechanical! More on that later.

We took off from runway 7 and started our pattern work. It was nice having some different scenery to look at! Our downwind leg took us directly towards the Orlando skyline which was pretty cool. I didn’t take this picture, but this is pretty close to our view on downwind (we were lower and more to the left).

Orlando, FL skyline

I really enjoyed flying with this CFI! He had a good teaching style and he shared the same views on flight instruction that my CFI back home does — namely, all of the information you need to fly the plane is available out the window. He emphasized this by failing almost all of my instruments. I had to climb out to pattern altitude with no altimeter, and when I thought I was there we would check and see how I did. I was coming in consistently low by 500-1,000 feet, but that wasn’t bad considering I was in a new environment for the first time.

We went over energy management techniques to help keep the plane at the right speeds while flying the pattern. We also did a lot of landings! I had one where it felt like everything clicked and I definitely feel like I’m getting closer to “getting it”. I also had some lousy ones, so I’m not there yet!

We also trained on some stuff that was new to me — using slips to lose altitude quickly and simulated engine outs on takeoff (where I had to then manage my energy to land the plane smoothly without nosing it into the runway). I also got a bunch of crosswind work — the winds weren’t as strong as they’ve been back home, but there was a decent crosswind so I worked on holding a proper ground track and keeping the plane lined up on final.

All in all, it was a great experience and I’m really happy I did it. I got to see some cool planes at the airport (the new HondaJet looks very nice!) and got a great view of a Learjet landing while I was in the pattern.

Taxiing back to the ramp I again had some trouble with that left turning, so I mentioned it to my CFI. He took the controls and agreed something felt off and he would mention it to the aircraft owner. I realized then I should’ve mentioned this as soon as I noticed it — what if they thought my wonderful landings had caused the issue?!?

We had a great talk after the lesson — we discussed the flight and flying in general. The instructor had some kind things to say about my flying and level of experience overall. According to him, I’m on track and right where I need to be.

Extra bonus today — the second page of my logbook is now full! On to page 3!

Flight time today: 1.5 hours
Total flight time to date: 27.8 hours
Total takeoffs to date: 89
Total landings to date: 85

A wacky, windy day

I was certain we wouldn’t be going up today. The forecast wasn’t too bad when I left my house (6kts at DXR), but it was supposed to kick up pretty bad as the day wore on. I was going to skip the lesson, but decided to head to the airport because I had some questions for my CFI on my cross country plan and needed to pick up a textbook I had on order.

I got to the airport and was surprised when my CFI said we’d be doing some flying! He wanted to practice some maneuvers since I would soon be flying with another CFI and I would be tested on things like stall recoveries and steep turns.

We preflighted the airplane and climbed in. He told me my first task was to fly him to Dutchess County (POU) and pretend he wasn’t in the plane. I could use whatever resources I wanted to get us there. I felt a surge of excitement — here it was, the first simulation of what it would be like flying solo!

Solo flight

 

I took off and used the Carmel VOR to point us in the right direction. It was real choppy at 3,000 feet, so we climbed to 4,500 to get some smooth air. We were planning on practicing landings at POU as the winds were pretty calm (only 3kts). Turns out everyone else had the same idea and when we got there we found the pattern was a bit crowded.

We asked for a right base to runway 6 which would have made sense given the direction we were coming from. The controller gave us the approval, then rescinded it a couple minutes later because he had traffic coming from the opposite direction. He told us to join a downwind for runway 6, which meant we had to fly out of our way into a strong headwind. That killed some time.

I got established in the pattern and was on final when the tower told us to go-around. A plane had landed a few minutes before us and had not fully cleared the runway yet. It was good to get some go-around practice, in a real-world scenario to boot! We worked our way back around the patter and the winds were starting to get stronger near the surface. We came in for a pretty crappy landing and my instructor decided we’d head back — conditions were not improving.

We departed and headed back to Danbury. The turbulence was kicking us around so we climbed to 5.500 feet to escape it. To be honest, the winds were really putting me behind the plane — they weren’t even that strong, but I was constantly working to keep the plane flying straight and level as gusts knocked us up, down, and sideways. If I had truly been flying solo I would’ve been really nervous.

We scratched the plan to work on maneuvers since it was getting pretty crappy out and we set ourselves up for a long final into runway 35. As we were getting established and coming down to pattern altitude, the winds were getting a bit crazy. My instructor took the plane and took us in for the landing. I just sat there and watched in awe. He was completely focused, constantly working the throttle and ailerons to battle the winds as we came into the valley before the runway. There are some wicked updrafts and downdrafts caused by the terrain on that approach, so you really have to be on top of your game!

He brought us in for a nice landing, and right before touchdown a gust almost knocked us off the runway path. My CFI expertly fought the plane back and got us on the ground. It was pretty impressive to watch. He apologized for taking the landing away from me, but I had no problem with that…I told him, “I’m really glad you know what the hell you’re doing because I’d probably be dead right now if I’d tried that landing.” Eventually I’ll be able to deal with that kind of stuff, but I know for certain I’m not there yet.

Click the picture below to see the CloudAhoy debrief for this flight.

CloudAhoy flight - 03/04/2017

Flight time today: 1.3 hours
Total flight time to date: 26.3 hours
Total takeoffs to date: 75
Total landings to date: 71

 

More crosswind landing practice

I didn’t think I’d be flying today. When I went to bed, it was windy as hell out and weather reports were showing gusts up to 30kts. I went to bed early anyway, crossing my fingers.

When I woke up, the weather briefing was optimistic. It was currently blowing only 6kts at DXR…the forecast called for much stronger winds as the day progressed, but it looked OK for my 8am lesson so I headed out to the airport.

My instructor agreed it was mild enough to head out and get some practice, although he told me, “you’ll be working today!” I hate it when he says that!

He wasn’t wrong…from the moment we took off, I was working my butt off trying to keep the plane flying the lines I wanted. We started off working the pattern for runway 26, but it wasn’t long before the controller switched the airport to runway 35.

Crosswind landings
Crosswind landings – they’re no joke!

Here I was hoping to get some practice on my roundout and flare, and now I had to practice a whole other set of procedures! Crosswind landings are certainly a different ball game than calm wind landings. Not only is lining up with the runway centerline harder, but it just feels wrong, as you are coming in with one wing lower than the other to compensate for the wind.

It was a good practice day, but one of those lessons where it feels I couldn’t do anything right. I got blown off centerline after takeoff because I wasn’t crabbing enough into the wind. I wasn’t managing power well enough to compensate with the strong updrafts and downdrafts caused by the surrounding terrain. My pattern legs were sloppy because I was misjudging the wind. I wasn’t keeping the aileron input in after landing — as my instructor loves to say, “the wind doesn’t stop once you land!”

Even with all of the problems, I got a few good landings in and some more experience with the tricky runway 35 approach. At one point we were on final and my instructor was talking about engine failure. “Would we be able to glide to the runway from here?” I asked. “Let’s see!” he replied, as he pulled the throttle to idle. Spoiler alert: we made it.

Next time around, he requested a short approach and pulled the throttle while we were on downwind. I headed right towards the runway at best glide speed and once we got over some tricky hills I dumped the flaps to get down in a steep approach. It wasn’t perfect, but it was some great experience with emergency management.

The winds started blowing faster and we saw some snow clouds closing in on the airport, so we called it a day. It was getting a bit too much for me and my low experience level. When we landed, my instructor told me I would have to fly with a different instructor soon for a checkride, a school policy when a pre-solo student racks up 25 hours. We decided we’d keep tomorrow’s appointment as-is, but next weekend I’d schedule with a different CFI.

I remembered to record the ride on CloudAhoy — click the image below to see the details.

CloudAhoy flight - 03/04/2017

Flight time today: 1.2 hours
Total flight time to date: 25.0 hours
Total takeoffs to date: 72
Total landings to date: 68

Too windy for me

Yesterday, my instructor told me if the weather sucked I was to skip my lessons until I had my cross country flight plan completed. I woke up today and checked the weather…it was a relatively nice day out with high ceilings and good visibility, but there were some gusty wind reports that gave me pause. We hadn’t talked about exactly what kinds of weather constituted “sucked” so I decided to head to the airport just in case…after all, it was a beautiful, clear day, and maybe these winds weren’t that bad, right?

Windsock

I should’ve stayed home! I got there and as soon as I got out of my car I knew the drive had been in vain — the winds almost slammed my car door shut on me as I tried to get out! Sure enough, when I went inside my CFI told me we wouldn’t be flying in 35mph gusts, so I turned around and went back home.

Cross country planning

I had a premonition that we wouldn’t be flying today when I encountered IMC while driving to the airport. There was a low layer of fog which made the drive in pretty interesting. Sure enough, when I got to DXR, my instructor said we’d be doing some ground school today and going over cross country planning.

I was pretty excited about this, since, as my instructor says, this is why you fly…to get somewhere! He told me my mission was to fly from DXR to Groton, CT (GON), about 65nm away. Then we would head to Windham (IJD), an untowered airport about 25nm north of Groton. Finally, we would head home to DXR, 63nm to the west.

We sketched out the flight plan on my sectional and looked at considerations like airspace we’d be passing through, safe altitudes across the trip, and any obstacles we might have to content with. My CFI showed me how to use my E6B flight computer to calculate the proper headings, and then he showed me how to use the E6B to factor wind forecasts into the equation and come up with a wind correction angle (WCA) for each leg.

E6B flight computer
E6B flight computer

I was told we would not have any more ground school until I came up with a full flight plan for the cross country. I’ll be posting about this process in more detail as I work through it. Even though I haven’t soloed yet, this made me feel like I was really on my way to a major milestone in my training!

The infamous DXR runway 35 approach

I was nervous about today’s lesson.

After the mistakes I made yesterday, I was hoping for a calm day to just work on my landings. I normally try and schedule my lessons for 8am, before the winds start kicking up. Today I was forced to take a 12pm lesson and the METAR was showing winds out of the north at 8kts gusting to 15kts.

Now, those aren’t particularly strong winds, but when you are a low-time student really trying to focus on the pattern procedural flow and landing timing, anything above dead calm will mean a higher workload. Not only was I not getting the glass smooth day I’d been hoping for, but winds from the north also meant Danbury would be using runway 35.

I’ve only flown runway 35 once, and it was before I was doing my own landings. The approach to 35 has a bit of a reputation — due to noise abatement procedures you come in on a rather long final approach which has you flying into a valley between two large hills. According to my CFI, the sun will hit one hill and not the other, causing an updraft on one side and a downdraft on the other and creating a bit of a turbulent vortex in the valley. There is also a pond you fly over right before reaching the runway (you can see it in the below image) which makes its own contribution to the mishmash of air currents during the approach. My instructor claims he knows a couple of commercial-rated pilots who won’t land DXR when 35 is active.

DXR's runway 35 approach
DXR’s runway 35 approach

The image above is from a YouTube video showing the approach — there are a few videos like this and watching them will give you a good idea of the terrain involved. The shot above is from after you are already in the valley — you can’t really see the size of the hills to the left and right, but they are intimidating!

I preflighted the plane and met up with my instructor, who laughed and said, “You’ll be having some fun today!”

“I think our definitions of fun are a little different,” I replied.

So, wonderful — a new approach and pattern to learn, and a challenging one at that. I resigned myself to the fact that I’d be working hard today.

After waiting a bit for the line guys to top off our tanks, we started up and taxied out to runway 35. There is a NOTAM for this runway:

ACFT USING RWY 35 ARE NOT VISIBLE FM THE TWR DESCENDING BLO 1300′ ON BASE LEG TIL APCHG 1/2MI FINAL DUE TO NATURAL TERRAIN.

That means we have to keep an eye on traffic in case the tower doesn’t see an approaching aircraft, so when doing the runup we position the plane so we can watch the final approach path.

We took off without incident and my instructor gave me some pointers on where to turn for the pattern. We did a few laps around the airport — it was challenging, as maintaining altitude required constant attention to the throttle. At one point during downwind I was concentrating on maintaining speed, getting my flaps setup, and calling tower, when my instructor asked, “Hey, how are we doing on altitude?” I took a look at the altimeter and realized we were 300 feet above pattern altitude. Whoops!

And that was just downwind. Turning on to final, we battled the updrafts and downdrafts to keep ourselves on a good descent path. The wind was pretty much straight down the runway so I wasn’t battling too much of a crosswind component, but it was still a challenge bringing the plane down at the right rate. I was constantly adding and removing power to try and stay in a stable approach.

I did a few landings — they weren’t great but I felt they are getting ever-so-slightly better. The fifth landing was a bit dicey as the winds starting kicking more and I started getting behind the plane a bit. My instructor called the lesson at that point — he felt it would be unproductive to continue and I would just get overly fatigued. It was about 20 minutes before we would’ve normally stopped the lesson, but I didn’t mind — I had gotten a taste of this interesting and challenging approach and didn’t want to get to the point where I was making stupid mistakes (like yesterday).

One thing I do like about this approach is the long final leg. I felt like it gave me more time to get aligned with the runway and control the descent. I’d like to request this approach one day when winds are calm so I can get some more experience flying it without battling the crazy wind.

And there’s the rub, right? I know to be a pilot I will need to be prepared for any situation — the winds won’t always be calm, the conditions will not be perfect, and I’m still going to have to get the plane down safely. I understand the experience I gained yesterday and today is very valuable — but at the same time, it is frustrating since I’m trying to perfect my landings. I just want some time to work on final approach, roundout, and flaring with as few distractions as possible. Once I have a comfort level landing in calm conditions, I will welcome the challenge of upping the difficulty and tackling winds and thermals. Right now, though, it is a bit overwhelming.

I was able to record today’s flight with CloudAhoy — click the picture below to check it out. Note the elongated pattern due to the extended downwind to avoid overflying the Lake Waubeeka community (which has a bit of an interesting history) on base.

CloudAhoy flight - 02/18/2017

I’ll be doing some pattern work in my home simulator during the upcoming week… it won’t help me with getting the feel of the plane down, but it might help me manage cockpit workflow a little better.

Flight time today: 1.0 hours
Total flight time to date: 23.8 hours
Total takeoffs to date: 64
Total landings to date: 60

Beat up by the crosswinds (and first trip to OXC)

Some days you fly the plane, some days the plane flies you…

Today started off promising. It was another unusually warm day (60° F!), a bit overcast but ceilings well above where I needed them to be, and a little wind. DXR was reporting surface winds of 7kts, and today’s destination, Waterbury-Oxford (OXC), was around 4kts. I didn’t think that would be any kind of challenge — we’ll come back to that in a minute.

My instructor was still in the air when I got to the airport, so I went out to preflight the plane. Everything looked good, and I even managed to get an action shot of me testing the fuel!

Testing fuel during preflight
I love the smell of 100LL in the morning!

When my CFI arrived, we briefed our flight plan. This would be my first trip to OXC — it’s only about 17nm from DXR, so it wouldn’t take us long to get there. We planned to use pilotage to find our way, following I-84 and the Housatonic RIver as our landmarks. We got into the plane and started her up, and that’s where the day started getting away from me.

First off, I forgot to start CloudAhoy before the flight, so I have no recording of the day’s events. Not the end of the world, but annoying. Next, while taxiing out to runway 26, the plane got away from me a bit when I got uncoordinated on the rudder pedals/brakes. We headed right for a snowbank before my CFI took control and got us back on track. Embarrassing, and I don’t have any excuse — not sure how I got mixed up but it’s a reminder to be extra diligent during ALL phases of flight, especially those on the ground.

We took off uneventfully and headed over to OXC. Cruise was ok, kept my altitude at 2,500 feet and pointed the plane in the right direction. Radio calls went well and soon we were inbound for a left base to runway 36. Oxford only has one runway (18/36) and the airport is up on a hill, so wind is often a factor. I was about to find out what that meant.

KOXC

We came in for the first landing and I was focused on the review I did yesterday of how to gauge the roundout and flare height. What I was totally unprepared for were some kicking crosswinds! ATIS said the winds were out of 300° at 4kts, but my instructor (and the windsock) indicated they were blowing stronger than that. Now I had to deal with an unfamiliar airport, crosswind technique (which I haven’t had much practice with at all), AND trying to figure this flare height thing out!

We did a full stop landing so I could get a sense of the airport and taxiway layout, then headed back to runway 36 for some touch and go’s. We made a few circuits around the pattern and it got progressively harder for me to keep the plane lined up on final. I’m not used to the concept of landing on one wheel with the wings tilted, so I kept wanting to straighten the plane out before touching down. I needed quite a bit of help on some of these landings.

I was a little better with my approach altitude, but I was still keeping it too high for some of our approaches. I need to learn better power management — something my instructor has been on me for. I have zero finesse when it comes to the throttle and knowing when to add a touch of power or when I need to back it off more to compensate for a too-low descent rate.

Eventually the winds were got a touch too nasty, so we headed back to DXR. We used pilotage again, and we practiced an engine out emergency. My CFI asked where I would go if the engine quit. I looked around — there weren’t a ton of great options, but I spotted some fields that looked like they would work. “OK,” he said, as he pulled the throttle to idle. “Get there!”

I set up for best glide speed of 80mph and he showed me how the wind was slowing us a bit too much so we would actually be better gliding with a bit more speed. We headed towards the fields and would have just cleared some trees and been able to put it down. I got my engine back at the last second and we resumed our trip back to DXR.

We did a couple laps of the pattern at DXR and here’s where things really started falling apart for me. I kept making stupid mistakes. Here’s the ones I remember:

  • On downwind, I added 10° of flaps and instead of returning the flaps switch to “neutral” I put it back to “up” and took the flaps right back out.
  • On a go-around, I thought, “take out 6 seconds (20°) of flaps” — however, that’s when you have flaps fully extended. Instead of bringing the flaps back 10° like I should have, I took them completely out.
  • Same go-around, after taking the flaps out I instinctually pitched the nose down. I guess I was thinking I needed to build up speed, but that’s the wrong thing to do. I should have immediately started climbing.
  • Turning on to final, I was completely uncoordinated, putting left rudder into the turn when I needed right rudder.
  • I kept over-banking my turns in the pattern — this has been a habitual problem for me.
  • I kept pulling back on the elevator and raising the nose when I should’ve been using power to gain altitude, not elevator.
  • When my CFI asked the tower to shoot me a light gun signal so I could see what they look like, I let the nose creep up while I was looking outside for the signal. This was because the plane wasn’t properly trimmed.

Not a shabby list for a few loops around the airport! They were all stupid things that I should know better than to do. And they are all things that could get me in serious trouble if I didn’t have someone in the plane watching over my shoulder. If there was any saving grace, it is that all of these mistakes were likely due to fatigue after the intense workload of the earlier crosswind landings. Even so, it underscored that I have a lot more work to do and that I am definitely not ready to solo yet. It also earned me a review of go-arounds on the next lesson since my CFI was not happy with my performance today.

Our time was up at this point, but my instructor would’ve stopped the lesson there regardless of what time it was — I was showing too many signs of fatigue to continue. I would’ve had no problem with that — as it was, my mind was reeling and I was ready to stop for the day. One silver lining — I did remember to use the “pizza slice” to look for my flare height on this flight. Unfortunately, it didn’t help much with everything else that was overloading me today!

I left feeling a bit down on myself, but tomorrow is a holiday so I have the day off and another lesson booked. If nothing else, this has steeled my resolve to study up tonight, mess around on my sim, and absolutely kill it tomorrow.

Flight time today: 1.5 hours
Total flight time to date: 22.8 hours
Total takeoffs to date: 59
Total landings to date: 55

Another trip to POU

Today we had a beautiful day for flying — the temperature picked up to around 55° F and started to melt some of the snow that’s been sticking around since last weekend. The wind was calm and the skies were clear, as evidenced by this quick shot I took of a low-wing airplane doing pattern work.

Plane in the pattern at DXR
Plane in the pattern at DXR

My CFI decided we would be heading out to Dutchess County (POU) again. We had an uneventful taxi and takeoff from runway 26 and I flew a right downwind departure to the northwest.

We wound up doing a total of 10 touch and go’s at POU on runway 24. I find I get pretty task-saturated in POU’s pattern — a combination of different radio calls than I’m used to and not being very familiar with the landscape. I’m not proficient yet at picking out landmarks and visualizing my pattern on the fly, so I needed a little coaching from my CFI on when to start my turns. I find I keep making the mistake of not paralleling the runway on downwind — I tend to creep in towards the runway which shortens my base and increases the workload even more.

I kept coming in high on final, so we practiced some steep descents with full (40°) flaps. Since there was no wind I was doing better at tracking the centerline, but I continue to have big issues with the roundout and flare. I’m not able to judge my distance well and keep flaring way too high. The first landing I did was actually pretty good — I saw my instructor kept his hands off the yoke and it was a moderately smooth touchdown. The rest of them, well, they were a bit harder and I needed some assistance to keep us off the nosewheel.

After our time at POU was done, we departed and tracked directly to the Kingston VOR. From there, we flew the 150° radial back to DXR where I entered right downwind for runway 26. I thought I would nail this landing as I’m more familiar with the landscape, but again I was high on approach and bad on the flare.

At least something clicked into place for me — my instructor keeps telling me to look down the side of the plane when going into the roundout and flare. I couldn’t get this through my head — when trying to judge the flare height I was so concentrated on what I was doing with the yoke that I never shifted my vision to the side. Reading the landing chapters in Rod Machado’s How to Fly an Airplane Handbook made some things more clear, and I realized I need to be looking out the “pizza slice” of the windshield — the triangle made by the left side of the cowling, the right side  of the window post, and the horizon. My instructor had told me this (minus the pizza reference) but it kept slipping my mind. Hopefully the time I spent after the flight studying and reviewing this will help me with tomorrow’s lesson.

All in all, it wasn’t a terrible flight. It was a beautiful day, and I was very happy with the cruise portion of the flight, where I kept my altitude of 3,000 feet almost perfectly the entire way to POU. That meant I had the plane trimmed properly and was able to correct for minor deviations. The landings are still shaky, but I know that will settle down with time. I also realized my instructor isn’t strictly counting our takeoffs and landings! I tracked the flight with CloudAhoy and was able to go back and see exactly how many pattern trips we made. Although we had a total of 11 takeoffs and landings, my logbook shows 7 each. No worries there, I don’t really care and I was actually wondering how the heck he managed to keep track of all of them during a busy lesson.

Click the image below to view today’s flight:

CloudAhoy flight - 02/18/2017

Flight time today: 1.7 hours
Total flight time to date: 21.3 hours
Total takeoffs to date: 52
Total landings to date: 48

Winter strikes again!

Well, the forecasts held up and we received a nasty mix of sleet, rain, and ice pellets overnight into the morning. I knew last night there was a 99% chance the lesson would be scrubbed. Sure enough, I got the call this morning telling me the airport and flight school were being closed.

All in all, I’ve had pretty good luck with the weather this winter, so I can’t complain about a cancelled lesson once in awhile. The good news — we only have another few weeks of winter! Hopefully I will be soloing in some beautiful spring weather!