Dulles? Yep.

N65410 - C172S - 1.5 hours

Throughout my training as a student pilot, my instructors always made Dulles (IAD) out to be a looming and ominous land of inevitable doom, should you ever wander in its direction.  To their credit, airspace busts are a big concern around here.  First, Leesburg (JYO) is right under the class Bravo shelves, and second, when I started training we had something called the Washington Area Air Defense Identification Zone (ADIZ), which you didn't want to mess with.  The simple explanation of that is that if you violated that airspace, you had at the minimum a Blackhawk helicopter as a personal buddy to escort you to an airport for questioning.  The ADIZ is now the Special Flight Rules Area (SFRA), which is smaller and somewhat easier to work with (at least out of JYO, since it has a slight exemption), but the issue remains that a lot of the airspace around here is very much less than friendly.

If it looks confusing, it's because it is

Beyond the airspace issue, the airport is busy and should be treated with a healthy amount of respect when flying the smaller stuff.  Class B airports in general are very busy and if you're not on your game, you can cause issues for yourself or other people.  Because Class B airspace is positive control, you're essentially considered an instrument flight rules (IFR) aircraft, where controllers provide you with altitudes to maintain and headings to fly, so you need to be on top of your radio work and your aircraft.  All that said, I can understand why most instructors make it out to be a big deal.  Even if they didn't, most larger airports have ramp and service fees that would drive you somewhere else.



Because I'm stubborn, I like challenges, and my roommate works at Dulles, I went in anyway.

My excuse for the flight was that the Aircraft Owners and Pilots Assocation was having a seminar up in Frederick, Maryland.  I figured I'd fly up there because the trip up Route 15 is particularly painful if you get stuck behind someone slow, and it's just an awkward route from where I live.  From there, it morphed into a Dulles trip because my roommate Mat works the evening shift, and I figured it would be easier for him to escape work if I got the plane first and picked him up straight from work, instead of having him meet me at JYO.

The flight began with a little homework to make sure I had all of my bases covered.  First, I worked at Dulles long enough to know when the busy times were, so I planned to avoid those.  Second, I made sure to talk to contacts at Potomac TRACON (thanks Roscoe) to figure out the best way to get cleared in.  Finally, I made sure to write myself a briefing sheet with airport sketches, frequencies and so on ahead of time to make sure I could keep up with the faster pace because I'd be on my own.

Before departing, I called up Potomac on the RCO frequency (118.5) to get my initial clearance.  Despite a little difficulty with the aircraft's mic jack, I was able to get the controller the proper data.  The initial clearance was to remain outside of the Bravo, contact Potomac on 126.1 (MULRR) after departure and expect an east side transition for Runway 1C.

Once I departed, I called Potomac and was cleared into the Bravo after being identified on radar.  At first, I was given a heading of 090 (due east) and an altitude of 2500'.  Nearing Germantown, MD, the controller had me proceed direct to an airspace fix called TICON, which is down near Dale City, VA.  That put me on a downwind, parallel to Runway 1R, directly underneath the HYPER arrivals.  While on the downwind, I ended up flying over the Wiehle Avenue Metro Station construction, my house, and a few other landmarks around the area.  As I got closer to TICON, the controller had me switch to the final approach controller on 125.8 (IADFE combined with IADFW).  That controller turned me to a heading of 250 (southeast) and advised me that I had an Airbus ahead of me, 500' above, inbound to land on Runway 1C.  When I advised the controller I had the aircraft in sight, he cleared me for the visual approach behind the Airbus, and had me switch over to tower.

Tysons, and another landmark you may recognize at the top right

My old high school

After switching over to tower I was cleared to land, number two behind the Airbus.  I actually ended up flying over my mom's house and my old high school, adding to the list of landmarks.  In order to not be a complete pest, I kept my speed up all the way in.  I crossed the threshold at about 120 knots, and then bled off speed over the 11,501' runway, landing long in order to cut down on taxi time.  Landmark Aviation - IAD is on the north side of the field, so the long landing helped in more ways than one.  The landing wasn't my best, but I managed to exit onto taxiway Y2 as I'd planned, so all was not lost.  I'm sure the passengers on the Airbus that had just exited the runway were entertained by it.  It's not the worst high-speed Cessna landing I've seen, either.  As I exited, tower told me to continue taxiing onto Y and to contact ground for the rest.  Ground had me continue on Y to Landmark, and on the way, I contacted Landmark to let them know I would be there in a few minutes to pick up Mat.

At Landmark, I shut down and ran inside to file a flightplan back out.  When I got back in the plane, I called up Dulles Clearance to get cleared back out of the Bravo and up to Frederick (FDK).  Since I had filed a flight plan, the controller was able to clear me on the spot without a lengthy initial call by me stating who I was, what type of aircraft I was in, and where I needed to go.  The clearance out of the Bravo had me VFR at or below 2500', runway heading after departure, and departure on frequency 125.05 (ASPER).  After I read it back, I managed to blank on ground's frequency (at a Class B airfield, they assume you have your information handy).  Even though I had a spot on my briefing sheet for the frequency, in my excitement on the way in I managed to forget to write it down.  Thanks to technology, I pulled up a diagram on my phone with the information, and was all set.

A 767 to chase me down

Ground had me taxi to Runway 30 initially via Z, short of A, meaning I had to stop before crossing the intersection of Z and A.  After I called short of A, I got cleared a little further to F, where I had to hold to let a Cessna Citation taxi in front of me.  From there, I just followed the Citation to the runway.  There was a United A320 holding in the holding area near Runway 30, waiting on some sort of departure time restriction.  Because I'm me, I popped my window open and waved to the passengers as I taxied by (you can see it in the picture at left, facing away from the camera, in front of the 767).  Shortly thereafter, an Austrian Airlines Boeing 767 joined the line behind me.  As soon as I departed, the tower controller had me turn to a heading of 350 (west of due north) to get me out of the way of the much faster 767 that would be departing behind me.  Thereafter, he had me essentially fly directly above Runway 1L and then contact departure.  I can assure you, there were no comments about the Austrian crew's accent at all during this time.

The departure controller climbed the Austrian flight well west of me, while I stayed below the initial altitude for Dulles, which kept me mainly out of the way.  After I was north of the airport, the controller placed the responsibility of navigation on me to get to FDK, meaning I no longer had to wait for him to provide me headings.  On the way up, I passed over Sugarloaf Mountain.  For as long as the 9nm trip to IAD from JYO took, the trip to FDK was a joke.  The whole trip took me a half hour, covering about 30nm.  Closer in to the field, I called it in sight and the controller dropped me to the airport's advisory frequency.  There were a few people in the pattern, but as I entered the pattern, they had all landed.

After landing, I taxied in to the ramp and attempted to get some direction from Landmark Aviation - FDK on where to park, but they weren't listening to the frequency.  Because of that, I just shut down right in front of the FBO and walked inside to ask inside.  Inside, I was told that the plane should be in the transient spots, which were right next to where I parked, so I dragged the plane over there with a tow bar and help from Mat.

Back inside, the attendant called a cab for us to get over to the conference center.  You'd imagine that, having its headquarters at FDK, the AOPA would just host the event at the airport, but for whatever reason it was at a Holiday Inn in town.  Interestingly enough, I'd been to the same conference center for work training late last year, so I knew exactly where I was headed.  On the way over there, we passed a Fractured Prune donut shop, but it had closed for the day.  I haven't had any since the last time I was at that Holiday Inn, so I'll have to make another trip soon.

We arrived about 20 minutes into the seminar, unfortunately, so Mat and I slipped in and tried to grab the easiest seats available.  The accidents mentioned as part of the seminar seemed to be pretty obvious, and the speaker kept asking for audience input, which got old quickly.  Most of the crowd could have been my grandparents, so a lot of the input got to be long-winded stories of "back in the day."  The guy next to me kept making comments, and his wife apparently didn't know how to whisper, either.  By the first break, I'd had enough of it all, so Mat and I slipped out to grab coffee (luckily, I remembered where they kept it from when I had been there previously) and left.

It got dark, so no pictures.
Here's a picture of my track into IAD instead.

The seminar could have been really good, but the crowd killed it, so I opted to get dinner which I had yet to eat.  Since my boss, Jason, lives in Frederick, I called him to see if he wanted to join us.  It turns out he was at the mall right next to the conference center, so we met up at the Red Robin right there for some food and then headed home.

The way back was uneventful.  Before departing, I followed a Diamond who was going out for some night landings in the pattern.  I flew my signature short field takeoff just to amuse myself and get more altitude quickly to avoid ticking off people living around the field, as it was pretty late when we left.

On the approach into JYO, I was showing Mat how the pilot-controlled lighting worked through clicking the transmit key of the comm radio.  Unfortunately, after I'd set it to high, it wouldn't go back down to low again.  I normally land with the lights on their lowest setting because the lights outline the runway enough, but don't blind you.  With the lights on high, I felt like I was trying to land on a brightly-lit Christmas tree.  Following with the trend of the other two landings, I landed a little too flat.

Where's the video, you ask?  I left the camera plugged in at work.  Genius, I know.  At least I thought to grab a camera.  I'll have to do it again and get it on video.  That would have been my first flight since I got the camera's mount, too.  Oh well.  Next time.

Hours:
Pilot in Command Cross Country (PIC XC): 0 - 50.4 (of 50)
Actual/Simulated Instrument (Act/Sim): 0 - 4.9 (of 40)

From the Ground

One thing I've always loved to do is sit and watch aircraft fly over.  It sounds incredibly boring, and it very well could be provided you're not in the right spot, but if you get the right spot you're set.  My favorite spot, as well as a favorite for many others in the area, is Gravelly Point Park, which is right under the final for Runway 19 into Washington National (DCA).

When I was a kid, my parents used to take me up there to sit and watch the DC9s, F100s, 727s and MD80s land for hours at a time.  The size of the aircraft has gotten a little smaller on average, but going there is still a lot of fun.

My friend Melissa suggested it during the week last week, and it was supposed to be nice out, so I definitely didn't object.  We aimed to get up there at 2:00 because that's when FlightAware's graphs showed the highest arrival rate for the day.  The weather showed that they'd also be in South Ops, meaning aircraft would be landing on Runway 19.

In an attempt to grab better pictures, I preset my white balance, which made for some great pictures when shooting away from the runway, but towards the runway you'll see color washing in some of the pictures that follow.  I tried to correct it in Photoshop (CS2 if you're curious - yes, I know it's old), but it is what it is.

The first aircraft I got a shot of was an AirTran Boeing 717.  Unfortunately, both the airline and the aircraft are nearing extinction.  The airline is being absorbed into Southwest, and the Boeing 717 will likely die with it in the United States (mainland anyway, as Hawaiian will continue to use them), as Southwest has said they will not be keeping them in its fleet.  It's not the prettiest plane, but I'll miss it.  It reminds me of all of the old tail-engined aircraft that used to fly in here all the time.  The Boeing 727 (although a tri-jet, still tail-engined), the McDonnell-Douglas 80s (which still fly here, but not as much as in the past), the Douglas 9s and the Fokker 100s all had tail-mounted engines.  The design of the 717 actually has its roots in the MD90-30 (and was actually named the MD95 until Boeing bought McDonnell-Douglas), which had its roots in the MD80, which all began with the DC9.  Now you know everything you didn't need to know about the 717.

The next shot (that I decided to keep anyway), is a Canadair Regional Jet with Piedmont (flying as US Airways Express) ready to depart Runway 19.  I used to work with these when I worked the ramp at Dulles (IAD) with Independence Air and Air Wisconsin.  Some people will argue they ruined the industry (one guy who said this is mentioned below).  I'd argue they weren't the best choice for Independence.  Others probably have other claims, but you can't argue with the fact that they're just about everywhere, flying regional routes across the globe.  The houses in the background, by the way, are the base houses for Bolling AFB across the river.

Here's one of the old timers for the field.  It's an American McDonnell-Douglas 80.  American and Delta flew them heavily in the past, and there are still some of them around with both airlines.  Delta actually liked them so much that they bought as many of the upgraded MD90-30 version as they could before McDonnell-Douglas went out of business, and then bought a few more recently from airlines in the Pacific region.  I can't say much else about it other than the fact that it's nice to still see a few aircraft around that I grew up seeing.  It's a good looking plane done up in the American polished metal, too.

A few seconds later, I snapped this as it touched down on the runway.  The sky got washed, but I like everything else about it so I kept it around.  The smoke is of course from the wheels going from zero to about 140 miles per hour in less than a second.  Visible to the left of the plane is the Airport Surveillance Radar (ASR), which feeds Potomac TRACON with aircraft positions around the field, and the communications antennas for air to ground radio communications.  To the right, you can see the Runway 19-1 sign (red), with a stop sign next to it (which is for airport vehicles, not the planes).

This US Airways Airbus 319 is similar to the A320 that ended up in the Hudson River a while ago (it's just shorter).  I also worked with a few of these at Independence Air, but not very often.  These are getting more and more popular with the airlines, and have taken over the market for this size of jet.  Where you used to see 737s everywhere, you now see the Airbus 320-series (319, 320, 321).

Speaking of the 737, they're still around.  This one is a Boeing 737-700 flying for United.  To be honest, I like the plane, but the new United livery looks weird to me.  Since United and Continental merged, they kept the United name and used it on the Continental livery so there was a little of both that carried through.  The 737-700 is a newer model as part of the Next Generation (NG) series.  One of the optional upgrades is the blended winglets on the end of the wings that reduce drag and fuel consumption.  The original version of the 737 flew back in 1967.  That itself shows how strong Boeing's hold on that part of the market has been.

Here's another flying with American taxiing to depart, while the United in the last shot is about to lift off.

Controllers here have a reputation for pushing the limits of how many aircraft and take off and land at DCA.  It takes a lot of skill for the controllers both in the TRACON and in the tower at the airport to do that and keep it safe.  Despite that story that came out a while ago where a controller had fallen asleep, on the whole these people are using a skill set most could only dream of having, handling hundreds of lives at a time. These last two shots somewhat capture that, as the A319 (US Airways) is on short final, with one aircraft about to lift off, and one holding short of the runway waiting for it to land.  My friend Melissa is in the foreground.

Here's another CRJ flying with Air Wisconsin (for US Airways Express).  If you look carefully, you can see another CRJ being vectored for the approach, which is called the River Visual Runway 19 Approach and it's somewhat of a legendary approach in the United States.

 

Smaller aircraft going into the airport can land on the other two runways: Runway 15-33 and Runway 4-22.  The aircraft is an Embraer 170 (Shuttle America as Delta Connection) crossing between me and the buildings of Crystal City to land on Runway 15.  To me, the plane looks like the short bus of planes, but I might be influenced to say that because they're a bear to service.  I had to deal with them when I worked at Air Wisconsin.  They need a jet bridge or portable stairs, whereas the other regionals I worked with had stairs built in to the door.  The bag bins were also pretty difficult to work in.  Whining aside, they're pretty successful in sales, so I can't argue with that.

This is another aircraft you don't see much anymore.  Earlier, I mentioned the 737 is a design that's been around for a while.  Since it first came out it went through a few design changes, and the pictured aircraft is part of the series that sported the first major changes.  This aircraft in particular is a Boeing 737-400 flying for US Airways.  The first in the series were the 737-100 and -200.  The pictured generation is the 737-300, -400 and -500 (oddly enough the 737-500 is shorter than the -300 and -400).  The current generation is the 737-600, -700, -800 and -900.

The longer version of the earlier EMB170 is the EMB190, which JetBlue uses in addition to its A320s.  I still think they're weird looking, but this one has a nice tail, and I managed to catch a bird in the shot.

US Airways, in an attempt to break the monotony of the same design across all of its aircraft, has painted some of its aircraft in unique liveries.  Some of them are sports teams like this one, while others are what they call heritage liveries.  The heritage liveries are basically the paint jobs of past airlines (that were at some point integrated into US Airways), on the current planes.  This one (an A319) is painted up in the colors of the Philadelphia Eagles.  Each of US Airways's hub cities has an aircraft painted for its football team.


Earlier I mentioned Delta's love of the MD80s and 90s.  This is definitely an example of that.  Like I said earlier, they're going as far as Asia to pick more of them up because they're no longer in production.

As the Delta plane left, I ran into a local spotter who was equipped with a camera with a giant telephoto lens, a scanner, no less than three binders of information (which I later found out was the flight schedules printed in several sorts), and a bunch of other information to hand out to people interested in the hobby.  For those of you who don't know, spotters are people who take pictures of aircraft or those who log aircraft types and tail numbers as a hobby.  I guess I'm a casual spotter in the picture-taking sense, but some of these guys get serious.  He spots with the WashBalt Spotters group (linked below), so if you're interested in photography and aircraft, it might be something for you.

If you're at all interested in spotting in the area, there are a few web pages that might be of interest to you:
http://washbaltspotters.net/
http://www.spotterswiki.com/index.php?title=Category:Virginia

I used a Nikon D60 with a 200mm lens, and it's decent at DCA, but you're better off with a 300mm if you have one or can afford it, especially at Dulles.

IR PIC XC Complete

N172DR - C172R - 1.7 hours

For those of you scratching your head, wondering what the heck the title is supposed to mean, it means "Instrument Rating Pilot in Command Cross Country Complete."  Basically, in order to get the rating, the FAA wants you to have 50 hours of flight time to destinations more than 50nm (57.5 "regular" miles) away.

After the last flight, I was looking at the numbers and noticing that I was only 1.4 short of the 50 hour requirement, so I figured I might as well put that one out of the way.  At first, I'd assumed that I'd leave a few hours in there for the long cross country, but I just wanted to get it all over with.  That requirement is now out of the way, so all I have to do now is knock out a ton of sim time, along with a ton more time in the aircraft with horse blinders on, and then go take a checkride.  Easy, right?

We'll see how it goes.

Melissa rode along with me again on this milestone trip, and since we were going to be flying later in the day, on a Sunday, we eventually settled on Charlottesville for the trip.  It's shorter, it's easy, I know it, and it's safe.  Originally, I'd planned on departing in time to see the sun set, but by the time we both got ready, got to the airport, and got the plane ready, the sun had dipped below the horizon.  Even though it had disappeared, the sky was still a nice orange, so all was not lost.  Melissa also set up the Contour on the glareshield as I was preflighting, too, so I got the full taxi out, run up, and departure.  It's still in the testing phase, though, so it's still not perfect.  For one, I took 3M Command Adhesive to stick it to the glareshield, so it's still not properly mounted (the mount should be here in a few days), and I haven't tuned the camera settings to my liking.  In any case, there's a good bit of video captured prior to it getting too dark.

On the way down, I talked to the MANNE and CHOEA sectors of the Potomac TRACON, along with Charlottesville Tower of course.  As soon as I checked in with CHOEA, I was given the ATIS info and the arrival runway, which was Runway 3.  Once I was on tower's frequency, I was instructed to make right traffic, and flew over Route 29 to enter on the downwind.  As I entered the pattern, the tower controller, who was working a combined tower and ground, was giving instructions to a Colgan SAAB 340.  As usual, I don't like to be the little plane that gets in the way, I made a closer turn in to the runway, came in a little fast, and bled off the speed over the runway so that I could land, slow and exit the runway quickly.  That all worked out pretty well as I exited right before they called ready for departure.  Given the amount of wind, I'd say it was a pretty good landing.


The camera recorded nearly the whole flight, before it died on right base into Charlottesville.  Oddly enough, it actually split it into two videos.  I'm not sure if that was a file size limitation, or if it somehow got bumped in the turbulence, but it split the file.  Oh well.  Weird things always happen when adapting to new technology.

I took my normal taxi route to the Landmark ramp, which apparently somehow confused the tower controller, as he revised his earlier taxi instructions for Landmark.  It was the same tower controller I always talk to and I was in my normal plane, but I guess he had never paid attention to what I'd done before.  In any case, I made it in, parked and shut down.  The ramp guy parked me right in front of the door to the building (I felt a little first class right about then, no lie), and as I opened the door I was greeted with "the crew car should be here - no fuel?"  Even though our flight school worked out a deal to avoid the ramp fee at Landmark - CHO because the aircraft is based at a Landmark at JYO, I felt like I should give them something for letting me borrow their car all the time, so I had them put some fuel in it.  When I walked inside, Keya met me with similar, in that I knew the drill for taking the car, and we were off.

I haven't yet decided if I like the fact that I've come here so often that I'm recognized and understood or not.  On the one hand, I like being a regular because it's nice to actually develop relationships with people, even if only simple ones, and it's nice to have a go-to.  On the other hand, being a regular means you're also somewhat predictable (evidence in the comments when I got out of the aircraft and walked inside), and I'm not sure I like being predictable like that.  It's not a big deal, really, but it's something I've obviously thought about.

At the grill, Melissa noticed the kid's menus had horses on them, and asked if I wanted to take one to color.  Of course, being an occasional large child, I did.  The hostess made note of the move and gave me a hard time about it as well.  At the table, I colored the horses while Melissa chastized me for my lack of proper shading - with Crayons, mind you - while the server, Chris, got the drinks and took the food order.  Melissa tried to steal my burger twice in the time we were there: once when we were ordering, and once when it came out.  In the end, I managed to end up with my Clint Eastwood burger, despite her efforts.  As we got ready to leave, I decided to finally get the names of the servers I liked and write them down so I can request them next time, which Chris helped with.  As a thanks, we left the drawing.  He said they'd hang it up if we left it, so we'll see what happens with it next time I'm there.

After taking care of the fuel and getting the plane set, we were off again.  Tower got us set up with flight following from Potomac while we were still on the ground, waiting for a US Airways regional jet to land.  As the RJ was exiting, we got the standard on course takeoff clearance, and we were off.  As usual with my departures out of CHO, I made a short field takeoff.  I find them fun and they keep my skill up for if I ever need to do one in the future.  I kinda want to see what it looks like from the ground, though.

The flight back was calmer, though still bumpy in parts.  As we got closer to JYO, I asked Potomac (ASPER), if I could get cleared into the Bravo.  The controller let me know she'd advise me as I got closer, and eventually cleared me in, VFR at or below 5500'.  Keeping it up at 5500' was nice, as we had a 20 knot tailwind, which put us up at about 140 across the ground.  Once we were about 20 miles out I called the field in sight, but she held on to us until we were about 5 out.  From there, I made a non-standard left base entry (nobody was around) and landed on Runway 35.

You know the rest of the story.

Yeah.  That's the runway, and that's the end of the video.

50 hours of PIC XC done.  Now it's just the instrument time, and the long cross country with multiple approaches.

Hours:
Pilot in Command Cross Country (PIC XC): 1.7 - 50.4 (of 50) 
Actual/Simulated Instrument (Act/Sim): 0 - 4.9 (of 40)

Richmond for a Stamp

N6017N - C172S - 2.3 hours

This flight came partially out a need to celebrate the great medical news of a friend, and partially out of my need to go play with my new toy.  In the end, it was a lesson in flexibility, and situational awareness.

From the very start, things were slightly hectic.  Roscoe wasn't going to be able to get back to me about the flight until after I left work, and I didn't want to reserve an aircraft until I was sure I'd be using it.  As I came up out of the Metro after work, I checked in with Roscoe to see what the story was, called the flight school to put the keys to one of the aircraft out in the lock box, and headed home to change and get my flight gear.  When we got out to the airport, the aircraft I had intended to take was down for maintenance, so I took one of the newer 172S models with a G1000, which was a decision that could have saved my life, along with the life of my passenger.

Not much to see.  Night is dark.

After a few minutes of readjusting to the the G1000, we were off.  The departure was normal, and the sky was really clear, with the moon lighting things up.  I didn't set the Contour up until after departure, which you can see in the GPS data on the right side of the image.  The cool thing about it is that you can very clearly see the profile ascent from under the Bravo.  In the future, I'll post a link to the video, but the flight was at night, and the camera didn't pick much up.  Looking at the map, you can see the recording picks up just west of Leesburg and continues all the way down to just north of Richmond.  The profile's first step is 2300, with the next step up 4300, and the final cruise of 5500.  In the end, the recording cut out at just under 42 minutes because of the limited 2GB SD card.  I ordered a 32GB card, so given 21 minutes per GB, the new card should give me about 11 hours, which will far outlast the battery.  If I bump the settings up, the battery and file size will suffer, of course.  I'll work on ways to get audio eventually.  I got flight following from Potomac TRACON on the way down, talking to the MANNE, MULRR and FLTRK (FLaTRocK) sectors.

As we got closer to Richmond (RIC), approach offered both Runways 16 and 20.  I took 20 because the taxi back from 16 would take forever.  The controller pointed the airport's direction out a few times, but I couldn't see a beacon or the airport in general, so I didn't call it in sight.  At about 12nm out, I was able to spot the beacon buried in a mass of airport lighting, and told the controller we had the field.  From there, he has us contact the tower, who cleared pretty far out to land on Runway 20.  Since I hadn't been to RIC before and it was dark, I had the tower controller turn up the runway lights for the runway so I could see exactly where it was (you can hear my request at about 14:08 in this LiveATC archive - you won't be able to hear tower, but you'll hear me).  Once I had a better idea of what I was aiming for, I brought it in on one of my better landings, despite a little choppy air on final.  The tower controller had me roll all the way down to the end of the runway for an easier taxi to Million Air, which was the FBO where we'd be parking.

My friend Mike, who lives around Richmond, met us there to give us a ride into town.  At first we thought we'd grab barbecue, but since we got in so late our options were pretty limited.  We ended up settling on Steak 'n Shake mostly because it was new in Richmond, and because I hadn't been to one since I was 13.  Despite being a chain (and the first chain mentioned in this blog), it was pretty good.  Even if it wasn't stellar, write-home-about-it, best-burger-ever, it hit the spot.  After the quick dinner, we trekked back to the airport to head back home.

Back at Million Air, Roscoe got his Richmond stamp for his Aviation Ambassador passport, I paid for fuel, and we set off for Leesburg.  I haven't flown into a Class C airport since the end of 2005, so I was a little rusty on the radio calls for a departure clearance, but after that I was set.  Holding short of the runway, I had to wait for an Air Wisconsin CRJ to land before I was cleared out.  The departure was pretty standard with a turn to a heading of 270 on climbout and departure with FLTRK (you can hear the departure at about 7:30 in this LiveATC archive).

Signal Mountain - In the way of anything south 

The way back to Leesburg was just a nice as the trip down, but it got interesting closer to Leesburg.  As I was nearing CSN (CaSaNova, a navigation radio down near Warrenton, VA), the controller asked if I was going all the way to CSN or if I wanted to go direct to Leesburg prior to getting there.  Because it was shorter, I advised him I'd be heading towards Leesburg just prior to CSN.  You've probably heard me mention Upperville (2VG2) a lot in my flights, and the reason is that it's a landmark I can use to help me avoid terrain, while still remaining under the Dulles Class B airspace.  Cutting in prior to CSN meant not using that landmark, and changing my game plan.  Because it was non-standard, and I knew there was terrain out there I would be flying close to, I enabled the terrain feature on the nav display of the G1000.  That, and keeping my head up and out probably saved my life.

As I descended to 1300 to get under the final shelf of the airspace, Roscoe and I spotted the radio towers on top of Signal Mountain, along with the silhouette of the mountain itself against the moonlit terrain on the far side.  The heading I was on would've kept me west of the range, but I dodged further west to remain on the safe side (you can see it in the FlightAware image at the top of the post just north of the thick grey line that represents I-66).  After we passed the range, I went direct to Leesburg, and set down on Runway 17.

With the plane back in its spot, we threw the book and keys in the lock box and headed home.  I learned a few things tonight that I won't soon forget.

No longer lacking Southeast destinations 

Hours:
Pilot in Command Cross Country (PIC XC): 2.3 - 48.7 (of 50)
Actual/Simulated Instrument (Act/Sim): 0 - 4.9 (of 40)

Going High Tech

One of my Christmas presents was a gift certificate to REI.  Now, I'm not the biggest outdoorsman out there.  If I spend any time in a store like REI, it's probably to look at the bikes and marvel at how pretty they are.  I'm not saying I didn't appreciate the gift, I'm really just saying I have a tough time spending money certain places, and REI is one of them.  Since Christmas, I've been thinking of what I want to get from there.  Some of my ideas were biking-related.  Like I said, I'm not the biggest outdoorsman, but I'll spend all day on a bike by choice, and a new helmet and gloves would be in order, but I don't need them.  Yes, I know some of you are thinking "man, I'd kill money there in seconds," and I did.

Phil, my pilot friend in the Charlottesville trip back in December, has a GoPro camera that he's taken on a few flights and it seems like it would be pretty cool to have on flights of my own.  It almost happened in a sort of epiphany the other night as I was trying to figure out what to get with this REI card.  I figured GoPro cameras and their ilk are things REI would have, so I checked the site this morning and sure enough, they had them.  As somewhat of a competitor to the GoPro, there's another camera out there called the Contour, which my roommate has.  I figured I'd have a look at both.

When I showed up at the store, they had both the GoPro Hero ($200) and the Contour GPS ($300).  At first, I figured I might as well take the cheaper option, thinking I wouldn't really need the GPS feature.  After thinking it through for a few minutes, though, I thought the GPS tracking would be pretty cool for the flights, so I took the Contour.  The Contour is also much more aerodynamic should I ever work up the courage to mount it externally.



The interface shows both the video and the GPS tracking with Google Maps, which is pretty awesome, no lie.  The days of me trying to grab a screenshot of my FlightAware track are over.  To be honest, I'll probably still include them if my flight gets picked up by the system (so far, only two have), but this will probably steal the spotlight.

The only disadvantage is that these newer smaller cameras use CMOS image processing, which is also commonly referred to as "rolling shutter."  If you're not familiar, and you have an iPhone or other smart phone, try taking a picture of something moving really quickly.  Here's an example from my dad's iPhone on my Luray trip back in October:

That rubbery line with the weird line above it is the prop.  If you YouTube it you'll see how ridiculous how these cameras make props look  Here's a video of it.  It looks pretty ridiculous.  One review said there's a setting on the camera that reduces the effect, but we'll see how it goes.  I'll have to get inventive with how I mount it to avoid too much exposure to the prop.  As boring as it sounds, I think for a lot of the training flights, I may mount it to look more at what I'm doing so I can review what I did and critique it.  Who knows.  We'll see how it goes.  My next flight should be in the next week or so with my dad out to Elkins, so I'll test it out then.

Charlottesville? Twist my arm...

N65410 - C172S - 1.7 hours

On my way out the door with my friends Ashley and Katelyn, I ran into my good friend Roscoe, as he was up at the airport to check out a Sport Pilot Seminar that was going on.  It was just about to start and would go for a few hours, so I told him I'd be glad to come back in a few hours to go on a flight if he wanted to.  He agreed, so I set off for a shopping experience with the girls to kill some time.  In that time, I also sent a message to a buddy who just moved down to the area, Aaron, to see if he'd like to join, which he did.

Still looks new

Back at the airport I was told I by Tim, one of the CFIs, that I should go collect Roscoe from the Landmark hangar where the event was going on.  On the way back from the hangar, we ran into Aaron in the parking lot, so we all ran in to prep for the flight.  The evening's flight would be in one of Av-Ed's newer (in terms of acquisitions) 172S models, N65410.  I've never flown this one before, so I gave it a closer look than I would N172DR or one of the other usual suspects, but it's newer and pretty well taken care of, so everything was in order.

After Roscoe and Aaron climbed in and got situated, I got the plane started and off towards Runway 17 for our southwest departure to Charlottesville.  Since Roscoe works out at Potomac TRACON, I made sure to give them a call as I was heading out.  I called up ASPER (Dulles' north-side departure sector that works JYO departures and arrivals) first, but he dumped me right onto CHOEA (CHarlOttesville EAst).  At this point, I was over Upperville, well north of CHOEA's airspace, but they must've worked something out.  Anyway, after giving me a code and a few more miles for me to get closer to his radar range, he picked me up and I continued on my way to CHO.

Heading down to CHO

As I got closer, the controller asked if I had the weather information for CHO, but because I was out of its broadcast range, I hadn't picked it up yet on my second COM radio.  Just to make sure it wasn't the radio, I told him I was going to jump off of his frequency to check it with my primary radio.  Getting nothing, I went back over to his frequency and told him the situation, which prompted him to rattle off the weather for me.  Of course, as soon as he finished, I picked up the information on the second radio, which was still tuned to that frequency.  Joking with him about it, I also called the field, as I had Piney Mountain in sight.  For those of you unfamiliar with that area down there, Piney Mountain is just north of the airport, and the TRACON actually has one of their radar sites on top of it.  From there, it was straight in Runway 21, contact the tower.  Tower advised me to let him know when I was on a 5nm file, and at that point I was cleared to land.  That landing was probably my best one that day.  I actually got the nose up some, and the stall warning horn went off right as we touched.

I shut down and the ramp guy must've recognized me because he asked if I would be needing the crew car this time.  Inside, the ladies at the counter got my information and made fun of each other for even making me go through the motions because I'm apparently a regular now.  Can you guess where we went with said crew car?  Timberwood Grill, of course.

Locking up in CHO

Roscoe and Aaron both got burgers while I got the crab bisque, half to change it up, and half because I promised a friend I'd cook her dinner when I got home, and I wouldn't live it down if I showed up full.

The flight back was pretty hazy, but it was getting dark, so it wasn't too bad.  The dusk actually made spotting traffic a lot easier, and there was a lot of it.  Before departing, I had tower coordinate flight following for us, and when I was cleared for takeoff I made a short-soft takeoff just because I could, and I find them fun.  After departure, it was CHO's normal "climb on course," so I turned downwind and climbed up out of the pattern heading back to JYO.

As we got closer to JYO, you could start to see some departures out of Dulles climbing above us, though we couldn't hear them on our frequency.  I did, however, hear an arrival check in past Winchester that would eventually pass right over me closer in.  At about that time, the controller also called another aircraft 800' below me, opposite direction, type unknown, which would have been startling, but the plane we were flying had a traffic display in it, and I had noticed the plane on the display a few seconds before.

The rest of the flight was pretty quiet.  The wind had shifted, so I made my way in to land on Runway 35.  The landing was pretty flat, as usual, but not bad.  After we shut down, we all put the plane back in its spot and headed home.

I think one or two more flights will put me right on the edge of the 50 hour pilot in command cross country (PIC XC) requirement.  Some of that time will come as part of a long cross country later on that's a requirement for the instrument rating, so I plan on cutting my cross country flights just short of the 50 hours and picking up some hours in the sim, with some regular flights in between.  I'll probably still make blog entries for the sim time, commenting on what I've learned, but don't expect anything really, truly interesting to happen in those posts.  Don't fret, though, because we all know I can't go too long without actually getting in a plane.

Hours:
Pilot in Command Cross Country (PIC XC): 1.7 - 46.4 (of 50)
Actual/Simulated Instrument (Act/Sim): 0 - 4.9 (of 40)

Breakfast in Luray Part II

N172DR - C172R - 1.3 hours

Last week, when I was out with some of my pilot friends, we started talking about getting back into flying.  My friend Ashley, as you may know by now, has been a good flying buddy on a few of my flights, while her roommate and one of my friends, Katelyn, I haven't yet flown with.  Since it's been just shy of two months and the flight school I rent from requires a flight every 60 days for checkout currency, I figured it would be a good time for both of us to take a flight.

As usual, since I'm somewhat over the idea of trying to think up a destination, I put it off on Katelyn.  She's a pilot, so the idea of having her pick something off of a sectional isn't so unreasonable this time.  In the end she suggested Luray.

The weather was pretty awesome this morning, so I was pretty excited to get up in the air.  Since I'm such an addict, I ended up getting to the airport before the flight school even opened, so I had to sit pretty and wait for someone to show up.  Once it opened, I grabbed the book and headed out to preflight so that the plane would be ready for when the girls showed up.

My usual workhorse, N172DR, was the 'breakfast chariot' for the trip down to Luray.  After I got it all set and ready to go, I went back inside to meet Ashley and Katelyn.  Ashley was going to stay behind and get work done, so I showed her Landmark's crew room, and Katelyn and I went out to go get the flight started.

Upperville - 2VG2

Since she hasn't flown around this area, I described some of the procedures in and out of Leesburg and pointed out some of the landmarks to help in avoiding some of the less friendly airspace.  After crossing my southwest exit point, Upperville, we headed toward Front Royal and down the valley to Luray.

As we were heading down, I tuned in the Luray's common traffic advisory frequency (CTAF), which is a frequency shared by many airports out there because they don't draw enough traffic to justify having their own frequency.  You'll hear calls from all over the place because of that.  One of the calls I heard was from might-as-well-be-Delaware Harford County, Maryland (0W3).  The total distance that call traveled was slightly over 100nm.  Crazy.

With the wind from the south, I made for a straight in approach to Runway 22.  It wasn't my most stellar landing, but it certainly wasn't the worst.  As I was slowing the plane down and getting ready to taxi back to the tie downs, the airport attendant, John, asked what we were up to.  I told him we were headed into town and he met us with the van at the plane to drive us in.

Since Uncle Bucks turned out to be good last time, I figured it was worth another shot.  I'd say it was a good choice, but I was stuffed by the end of it.  After eating, we decided to walk back and get a couple laps around the pattern before heading back to Leesburg.  Unfortunately, by the time we made it back, it was getting close to the time we had to have the plane back home because someone had it after us.

That said, we set off towards Leesburg, this time with Katelyn at the controls as I played navigator.  As we got closer, I called headings and descents to keep us out of Dulles' airspace, and made sure everything was in order.  I also explained how to make the really awkward pattern entry to Runway 17 at Leesburg.  It's a really hectic approach because you really don't have much time to get situated on the downwind before you have to start your base turn.  You're boxed in by the SFRA to the southwest and east, and Dulles tower's airspace to the south, so you have to keep a tight pattern.  All of that worked against her, and the wind that was picking up only made it worse, but she salvaged the landing in the end.

We got in right before we had to have it back at 1230 so Katelyn ran the book in so that the next guy wouldn't be too delayed, while I made sure the plane was in order and locked up.  After taking care of the paperwork, we went over to collect Ashley from the crew room and head out for a little time at the Leesburg Outlets.

Hours:
Pilot in Command Cross Country (PIC XC): 1.3 - 44.7 (of 50)
Actual/Simulated Instrument (Act/Sim): 0 - 4.9 (of 40)