As the weekend approached, a flight instructor friend of mine asked if I'd want to split time in an Arrow to enjoy the nice weather. Not one to pass up an opportunity to fly, but also be able to log time toward the instrument rating requirements, I took him up on it. I had been wanting to get out to Hot Springs (HSP) for quite some time. It's a unique airport, being on top of a mountain, and is actually the highest airport east of the Mississippi River. This spot also causes it to be subject to various wind hazards to challenge you on approach. Today, being a windy day, meant that those challenges would be present for my first visit.
Since my friend is based out of Manassas (HEF), I got a break from Leesburg (JYO), and a refresher on the procedures down there. Apart from having to talk to controllers in the tower, and filing a flight plan, it really isn't too different. After departing, we flew directly out to HSP, and I was able to throw the blinders on to log instrument time. Closer to the field, I flew the ILS approach for practice, beginning with a hold for good measure.
Just before landing, the wind started to play games with my approach path and I ended up pretty low. It wasn't the prettiest final approach, but it got the job done. As soon as we exited, we brought the plane back to the runway to head back home. I have been into some pretty unique airports in my years of flying around, but I was not prepared for what I saw as I rolled up to the hold short line. The taxiway comes right up to a sharp drop off, giving you a pretty spectacular view as you prepare yourself to depart.
Once back in the air, I put the blinders back on to log some more time on the way back home. It was a pretty simple flight, but quite a visually memorable one. Of course, it didn't hurt that I was able to log time toward the simulated instrument, and complex requirements.
Hours: Pilot in Command Cross Country (PIC XC): 2.7 - 127.1 (of 50) Actual/Simulated Instrument (Act/Sim): 1.9 - 30.7 (of 40) Dual Complex: 2.7 - 7.7 (of 10) Total Time in Aircraft: 2.7 - 195.8 (of 250)
While I've been planning multiple variations for my long instrument cross country for some time, I never actually got around to flying it. Usually, it came down to an issue where I had other plans for flying, and that meant that there wasn't enough left in the month's flying budget for the longer flight in addition to the extra cost of having a CFI in the right seat. About a month ago, though, I was checking my progress against the requirements of the instrument rating and commercial pilot certificate and noticed that I'm getting rather close to both (as such, those who have read earlier posts here will notice the new additions to the hours section at the end of this post). Given my tendency to plan things out in great detail, I began to plan out the time between now and commercial minimums.
Aforementioned Simulated Aircraft
As one could probably tell, given my lack of updating this blog despite having flown a decent amount, flying the same aircraft that I've been flying for 12 years has been wearing on me. It's not that flying itself is getting boring; it's that one of my jobs allows me to fly simulations of some rather complex aircraft, and in comparison, a Cessna seems rather dull. Luckily, to satisfy my need for something different, the commercial requirements require 10 hours in a complex aircraft, and the school I rent from has an Archer to fit that purpose. In order to get my instrument rating I also need more instrument time, so on top of the new aircraft and a route to satisfy the long instrument cross country, I figured I'd do a significant portion with the blinders on. So, apart from getting to experience something new, I'd be able to maximize my flight dollar by knocking off several requirements in one long flight.
In order to get as much time in the Arrow as I could, while still getting the instrument cross country done, I planned out a flight that somewhat followed the shape of Virginia. This would allow me to depart Leesburg (JYO) and fly a route that provided flexibility for the approaches I wanted to fly. As planned, the routes were KJYO CSN V286 CCV V1 ORF [VOR 23] KCPK - KCPK FKN V266 SBV V136 PIGGS [ILS 34] KROA - KROA MOL V143 HOAGE [RNAV 17] KJYO. I had figured that the initial VOR approach into Chesapeake (CPK) would get the VOR approach out of the way, but also allow for a circling approach at a relatively calm airport if needed (though the forecast showed the wind favoring Runway 23 anyway). After that, Roanoke (ROA) had an ILS, an LDA, and a few RNAV approaches that I could fly, which allowed me to fly the opposite approach - ILS or RNAV - at JYO.
After getting back from my earlier flight, I grabbed the book and checklist to go familiarize myself with the plane for about an hour before the flight. The flight school I had worked at back in 2009 had a fleet of Archers and a couple Arrows that had a similar layout, so it wasn't entirely unfamiliar even though I had never flown them. After coming to grips with where everything was and getting all of my accessories situated - kneeboard ready, blinders readily available, and iPad within reach - Tim met me at the plane and we set off toward CPK.
Potomac TRACON (PCT) cleared us via STILL CSN WAIKS, despite my well-intended filed route. We were cleared to CSN well before getting to the STILL intersection, and it was about that point that I began to see how sluggish the Arrow can be in the summer with full fuel and two people in it. Passing through 5000, PCT asked us if we could give them our best rate to 6000, which we acknowledged, and then joked to each other that we were essentially already giving it to them, despite it being rather paltry. Just prior to reaching CSN, we were given a vector to the southeast, and then direct to CPK. Closer to CPK, Norfolk TRACON sent us to the ORF VOR and cleared us for the approach.
The approach clearance came a little late, which resulted in needing to turn back toward the approach course, but that also allowed me to get rid of some extra altitude, so it wasn't unwelcome. The rest of the approach wasn't bad, and having Tim calling the altitudes and managing the radios made things a lot easier. After switching to the CPK common traffic advisory frequency (CTAF), we were somewhat surprised by the lack of traffic in the pattern as it was such a nice day. After taking the blinders off, I maneuvered for landing and brought the plane in. For my first landing in an Arrow, it wasn't terrible, but managing the heavier controls made things interesting.
After taxiing off the runway and back down to the runup area, we began to set up for the next leg of the flight. Unfortunately, we couldn't raise anyone on the clearance or approach frequencies for a clearance while still on the ground, so we planned on departing VFR and picking up our IFR clearance in the air. While we were on the ground hoping for a response from the controllers, I snapped a picture of the altimeter. I know I've flown to Ocean City (OXB) a few times, which is close to sea level, but I don't think I ever paid attention to how close to sea level the altimeter showed that we were. To me, seeing it so low was novel enough for a picture.
Soon after, we were airborne and flying the noise abatement departure procedure, as there are houses pretty close to the airport on the west side. Tim called for clearance while I maneuvered toward the FKN VOR to begin my planned route. Unlike with PCT earlier, Norfolk cleared us "as filed," which made things easier as I didn't have to write down a full route clearance and set a new flight plan into the GPS. Approaching Suffolk Airport (SFQ), we were vectored away from it in order to avoid parachute jumpers. Later on, after FKN, we were given direct ROA, with a vector around restricted airspace near Blackstone Army Air Field (BKT). Closer to Lynchburg (LYH), we were handed off to Roanoke TRACON, who noticed the remark on the flight plan requesting the ILS or RNAV approach, and were cleared for the ILS approach to Runway 34. I chased the localizer and glide slope more than I would have liked, but I ended up generally where I wanted to be when I took the blinders off, so all was not lost. The landing, too, wasn't too graceful, as I chopped the power a little early and the nose dropped some just prior to touching down.
After we taxied over to Landmark and shut down, Tim gave the line guy the fuel order and I snapped a picture of the plane and walked inside. By then we were pretty hungry, so we grabbed a crew car and set off in search of food, which ended up being Sonic right down the road. That trip turned into another trip as we'd been handed the wrong order and drove off without checking it. After scarfing food, joking a bit with the staff, and settling the fuel bill, we went back out to the plane to head home.
Tim, working the radios again, called for clearance. Like the initial clearance from JYO to CPK, this one was altered, but it was also altered to the point that the whole clearance was just a single fix, so it was a simple change. We were given Runway 34 for departure as well, which meant a relatively immediate turn after departure because of terrain. The Arrow climbed slowly through the now hotter air, though some updrafts off of the terrain assisted at times. The associated turbulence, however, wasn't as welcomed.
The leg home was rather uneventful. We flew right up the eastern side of the Shenandoah Valley, and as soon as we crossed over into the Piedmont we were sent up to the initial approach fix for the RNAV approach to Runway 17 at JYO. The approach went relatively well, but an intermittent GPS position issue knocked my vertical guidance out and I had not caught it. The result was that I was slightly below path for the latter part of the approach. For future approaches, I'll have to be more mindful of the flags. In order to mesh better with traffic in the area, we broke off the approach and circled around to land on Runway 35. This landing was better than the one at ROA, but it'll take me more time to get used to the Arrow.
Rolling out long, we jumped off on the taxiway that put us right near our parking spot, shut down, and put the plane away. Despite the sluggishness in the climb, the Arrow was an enjoyable departure from the norm. In the end, the flight was 5.0 hours, which means that I have another 5.0 hours in it to finish off the commercial requirement. Having knocked out the long instrument cross country, 3.9 combined actual/simulated instrument, and my biennial flight review (BFR), I'd consider it a success. Now all I need to do is rack up 12.8 more hours of instrument time and I can go take care of the instrument rating. Having that will really open up the possibilities for flying days to begin taking a closer aim at the commercial requirements. Along those lines, I need to finish the aforementioned 5.0 hours in a complex aircraft; fly a solo cross country trip with a leg length of greater than 250 nautical miles between JYO and some other airport, stopping at another airport on either the way out, or the way back; and finish up the remainder of the 69.3 hours between what I have now and the 250 hour minimum. So close, yet so far away.
Hours: Pilot in Command Cross Country (PIC XC): 5.0 - 112.0 (of 50) Actual/Simulated Instrument (Act/Sim): 3.9 - 27.2 (of 40) Dual Complex: 5.0 - 5.0 (of 10) Total Time in Aircraft: 5.0 - 180.7 (of 250)
There are some times during the weekend where you simply find yourself with nothing left to do. Granted, this doesn't happen often for me between my day job forcing a lot of my activities to the weekend, my PMDG job contributing to that, PMDG Flight Ops activities (flying around in a DC-3, obviously, usually takes priority over just about anything else), and various other activities like visiting family and keeping the fridge stocked. To be clear, I have nothing against any of those things (besides maybe my day job), but it does mean that I'm rarely simply sitting there trying to come up with something to do.
Luckily, today was one of those days, and I saw an email go out from the school I got checked out with back in April. They needed a pilot to help chase an aircraft from Manassas (HEF) to Stafford (RMN), in order to bring him back from his ferry flight. I immediately called the school to offer to help out and was told to head down to the field and coordinate with the other pilot.
Once there, we waited out some isolated, typical summer storms and set off to RMN. The weather on the way over was still pretty hazy, and there were still isolated rain showers in spots, which was an interesting experience, and offered some pretty cool sights.
On the way back, the other pilot offered to let me log hood time, both to help me get the time, and to help him log time and not just sit there. We were nearly all the way back to HEF when we decided to see if the controller could give us a practice approach to the field, which actually took us all the way back over RMN. It was extra time, though, and time that I needed, so neither of us complained.
After bringing the plane back in and getting it tied down, we added our entries to the logbooks and then headed home. I, of course, stopped by to say good night to the 3 on the way out.
Hours: Pilot in Command Cross Country (PIC XC): 0.0 - 101.4 (of 50) Actual/Simulated Instrument (Act/Sim): 0.7 - 17.8 (of 40)
I've been wanting to get some time under the blinders, along with some approaches in recently. With that in mind, I sent a message to Phil to see if he'd be up for sitting right seat while I attempted to follow imaginary lines in the sky by reference to the instruments inside the airplane alone. The route I came up with was Charlottesville (CHO), a hop over the Blue Ridge Mountains and an approach into Shenandoah (SHD), and then a trek back to Leesburg (JYO). Through all of this, the plan was to just string it all together without getting out of the plane. Luckily, that all went as planned.
Departing JYO, we flew to the Casanova VOR (CSN) and followed the V140 airway to just prior to WITTO, where we were cleared to the HOODE intersection and onto the RNAV Z Runway 21 approach at CHO. After briefly setting the wheels down so that I could log the flight as cross country time, we were vectored to OLAJO and onto the RNAV Runway 23 approach. We flew the missed approach toward GABEL, but Potomac vectored us back toward JYO before we got there to avoid wasting time. Closer to JYO, the controller vectored us in for the ILS Runway 17 approach to round out the flight. Luckily, Phil took a few pictures of the flight as having the blinders on makes for boring imagery and flight narratives.
Here is one crossing the ridge between CHO and SHD:
Hours: Pilot in Command Cross Country (PIC XC): 2.4 - 95.6 (of 50) Actual/Simulated Instrument (Act/Sim): 1.9 - 16.6 (of 40)
Phil and I have had plans to go flying for a while now. Originally, it was a flight back in May, but that got cancelled so I flew out west on my own. I'm pretty sure there were a few plans in between, but more recently we were thinking of helping a friend get home to Upstate New York. Those plans also got cancelled as well, so like the flight back in May, we thought we'd head up to State College, PA. Yesterday, we decided that flight would be a little longer than we would've liked, so we cancelled those plans as well and opted for a challenge instead.
To be honest, that last paragraph reminds me a little of this:
Back in February of 2010, I went for a flight out of Harford County Airport (0W3), right after one of the Snowpocalypse storms. If the 2000' x 40' runway wasn't enough of a challenge, some of the snow plowed off of the runway was piled at the ends. It wouldn't be enough to force pilots to hit a 2000' x 40' target, though. Why not add in a 24' telephone line 500' from the runway, and some giant trees just beyond that? This is also not mentioning that I hadn't flown since August of 2008 prior to that. Despite it being a challenge, I really enjoyed it. I think that was the reason I enjoyed it, actually. It's a challenge.
We started the day early in weather that could only be described as "severe clear." Clear weather, however, makes no mention of temperature or wind. While it wasn't too incredibly cold, it was cold enough to put frost on the wings. The wind only added to the chill at a steady 6 knots. Phil preflighted the plane while I de-iced the wings of our plane, and several other aircraft on the way to put the de-ice bottle back inside. Back outside, I got the interior all set up with Phil. In the last flight narrative, I made fun of myself for the amount of technology I bring with me, but we essentially doubled it this time. Phil had his GoPro, iPad, Dual XGPS150, and the audio setup. I had my Contour, iPad, Garmin GLO, and audio setup as well. Why not?
After starting and heading down to the end of Runway 35, I called Potomac to get my SFRA flight plan activated. Apparently they didn't get it, though, so instead of bothering with Flight Service, Phil and I gave up the plan of a shortcut through the SFRA and just departed north, up and around it. On climb out, my iPad was not agreeing with the Garmin GLO for whatever reason. Phil ended up getting it sorted through cycling the power on both. Once that was all sorted, I threw the blinders on so that we could both log time (and I could continue to chip away at the 40 hour instrument time requirement).
Because we didn't get an SFRA clearance, we flew a route that would hug the outside: DINUW LINSE TAFFI 0W3. In order to log another approach, I flew the RNAV (GPS)-B off of TAFFI.
One of the issues with flying GPS approaches is that you never know whether or not the GPS database in the aircraft is up to date when it comes to renting from flight schools. It all depends on the school, really, but the one I rent from tends to be pretty good about keeping the aircraft up to date. The ever-so-trusty N172DR has a KLN-89B, and looking at the unit, it seems pretty simplistic. If you're a flyer of an aircraft with a simpler-looking GPS, don't discount it too much as a lot of them have some pretty neat features buried in them. Unfortunately, most of the CFIs don't know a lot of the features and normally only show you how to use the Direct-To feature. That's nothing against them, really, as some fleets have different equipment in just about every plane, but it's tough to utilize the tools in front of you if you've never been shown how. If you're not going to be shown the neat features, you might as well go learn them on your own. The KLN-89B actually has a free simulator that's out there on the internet. Unfortunately, I can't find a link from the manufacturer, but I did find a link through Software Informer. If you fly with a different unit, there's probably a free simulator out there somewhere as well. To be honest, the only reason I knew the KLN-89B had a moving map and an approach database was through the simulator in the link.
So, all that to say I was able to load the GPS approach after TAFFI through a little homework. Since the GPS was only going to give me lateral navigation, I flew the approach with step downs. Looking at the track in CloudAhoy, I didn't do too poorly. At the far left, you can see a very subtle bend in the track, which is my turn over TAFFI. After that, the more obvious turn in the middle is SNAZI, where you can see I turned a little more than necessary, and had to adjust closer to the field in order to land on Runway 10. I'll review CloudAhoy in another post, but check out the screen capture in Debrief Mode.
When I began the approach, I checked BWI's ATIS as noted on the approach plate, as there's no weather station on the field. It noted the wind was 040 at 9, meaning a nice crosswind for the approach, but nothing too unmanageable. After the little sidestep at the end of the approach, I brought the plane in for what I thought would be a nice showing of my landing skills. Unfortunately, the weather had other plans. The 9 knot wind wasn't so much of a 9 knot wind as much as it was a gusty 9 knot wind. It wasn't until I landed and checked the weather that I found out how gusty exactly.
In any case, here's the video of me fighting the crosswind down to the runway. Closer in, you can hear Phil say "nosewheel," anticipating me hitting nose first as I bring it in typically flat. I think I managed to hit the mains first, but wound up airborne again. I couldn't get it to settle and the end was coming up quickly, so I went around. Note the telephone line and giant trees at the end that I mentioned earlier, too.
[Video was here until Contour closed down for a bit, and all was lost.]
After going around, I wrapped the pattern back around to try the approach to Runway 28. In the video, you can see that the wind sock shows the wind somewhat favored Runway 10, but the last time I flew here I used Runway 28, so I figured I'd try that.
The second approach wasn't any better than the first, so I went around. The third attempt, however, was good enough to set down. I won't say it looked pretty because it really didn't, but I at least made it down to the ground, despite a gust picking the right wing up slightly, causing me to drag the right wheel while trying to brake. Thankfully, I had Phil to dump the lift by raising the flaps when I called it.
The video picks up on final, and you can definitely see how close you come to the trees and the telephone lines this time around. Contour changed the style of the videos as well. I'm not so much of a fan of the new overlay, but it is what it is. Just make sure not to pay attention to the speed display. It's not very accurate, which you can see as it still displays 70 mph when I'm pulling off the runway.
[Video was here until Contour closed down for a bit, and all was lost.]
As I exit, you can barely hear me coordinating with the aircraft holding short of the runway, who I later joked with about the luxuries of longer runways. Because I don't have any specific audio editing software, or audio hosting for that matter, I made it into a short YouTube clip:
After that departure, we headed back to JYO and I put the hood back on. Closer to Frederick (FDK), I remembered that they now have a tower and that I would need to avoid their airspace, or call them up. I opted for the former by climbing above it. The controller seemed to have his hands full with a couple pilots still adjusting to the relatively new tower, and I didn't feel like adding to his workload. After turning south, I handed the controls over to Phil so he could get in a landing. Compared to my landings, his was nice and smooth.
Here's the evidence:
[Video was here until Contour closed down for a bit, and all was lost.]
After I got home and checked the weather, it turns out that BWI's weather information updated right after I flew the approach. This report matches more of what I felt:
For the non-pilots among us, this is saying that the weather at BWI (KBWI) today, at 1454 UTC (171454Z), had wind from the northeast at 12 knots gusting to 21 knots (04012G21). The rest is sky conditions, temperature and pressure.
Definitely an airport I would return to - wind or not. I loved the challenge.
Hours: Pilot in Command Cross Country (PIC XC): 1.8 - 74.2 (of 50) Actual/Simulated Instrument (Act/Sim): 1.3 - 9.6 (of 40)
There are very few things in the world that I would prefer to do more than flying, so when it comes to what I do on my birthday, an airplane is likely involved at some point. Last year, my friend Jason and I flew down to Bridgewater (VBW) and ended up catching a glimpse of a B-17. This year, I took the day off from work in order to relax and fly. My friend Ashley managed to leave work a little early as well so that we could fly and be back in time for a dinner out with some more of our friends. Unfortunately, the weather didn't have the same plans. Fortunately, a little patience, good company, and a nice pilot lounge ended up working out.
After we arrived at Leesburg (JYO), we grabbed the keys for the plane and walked out to preflight. One of the instructors had just gotten back in and gave us a weather update that there were storms over the ridge heading towards us. Ashley and I had been checking the weather all morning, mostly because the ceilings had been so low the last couple days, but I was definitely aware that the weekend's second front was passing through.
We continued on to the plane to check it while watching the weather. The guy said there was a storm, and I believed him, but a lot can be said for actually seeing the weather. I figured we could at least get our stuff situated in the plane while keeping an eye on the sky. Unfortunately, as can be seen in aviation lore and AOPA magazines all over the place, pilots make bonehead moves and press on despite weather issues. Because I kept walking towards the plane after the instructor had warned me of the storm, I'm guessing he got the feeling I was going to try to beat it, so he walked out, iPad in hand, to show me the latest radar images (the center + is IAD, with JYO's + slightly northwest of it):
What he hadn't seen was the fact that I did actually check the weather, and that the radar loop was still running on my phone, so his concern was understandable. It's nice to see that we'll look out for each other, but there's a sad side to that coin as well: despite all of our training and warnings of "get-there-itis," pilots still give other pilots reason to express their words of caution. I told him my plan was to preflight, watch the weather, and set things up so that as soon as the front passed, we could go. That seemed to restore some of his faith in me, and before he walked back inside we talked some about his iPad's ForeFlight setup.
After we had set up out headsets, my camera, and everything else, the wind picked up and the the rain arrived. Ashley and I retreated to the pilot lounge and watched TV while the storm blew over. I also kept an eye on the weather using ForeFlight's radar overlay and looking out the window. As soon as it passed, though, we walked back out to the plane to give it one more look and set off towards Charlottesville (CHO).
The departure was standard, and as soon as I could, I put the blinders on to log some simulated instrument time. Over Upperville (2VG2), I called Potomac to get flight following, and give Ashley a feel for who to call and when. Before I put the blinders on, I got to see some of the coolest clouds I've seen to date in the low areas and valleys. They're not as obvious in the picture here, but you can see them in the video. Ashley took this picture about half way down to CHO, and you can see the clouds almost seem to be resting right on top of the trees. Storms can be violent, but the clouds and smooth air that were left behind were really nice.
As soon as I got handed off to CHOWE (the radar controller serving CHO), I asked for a practice ILS approach to Runway 3. It had been immediately rejected, but I thought I heard "roger" so I waited to hear back. A new controller stepped in soon after, and after I reported to him that I had the weather information at CHO, I asked again about the approach. This controller came back with a slightly longer answer of "Not approved - can't do opposite direction anymore after DCA screwed it up the other week" (referring to the incident at DCA on 31 July). Since I couldn't try the ILS to Runway 3, I asked for the RNAV GPS Y to Runway 21, which was approved. You can see the tail end of the approach here in the video:
[Video was here until Contour closed down for a bit, and the video was lost.]
The whole approach can be seen in the time lapse video at the end of the post.
After landing and shutting down, I brought Ashley to Timberwood for what was originally going to be dessert or something light, but the delay put us more in the dinner mood, so we got burgers instead. After dinner and the drive back, we were back up in the air to head home.
The flight back was pretty peaceful, and I got more simulated instrument time. Since it was getting dark, and not being able to see terrain is unsettling, I took the blinders off to have extra eyes looking to make sure we were headed in the right direction. Adding to the tense setting, I managed to forget to stop by the rest room before departing CHO. Luckily it wasn't bumpy. You know the rest.
Hours: Pilot in Command Cross Country (PIC XC): 1.7 - 65.1 (of 50) Actual/Simulated Instrument (Act/Sim): 0.9 - 7.5 (of 40)
