Longest flight yet gets me over 500 hours

This weekend I made my longest airplane trip to date - from KUZA in SC out to KCFD in TX - about 850 miles. The trip was for our quarterly ForeFlight strategy meeting, where the company gets together to plan out the next 3 months of work.

Leaving KUZA I took off and picked up my IFR clearance in the air. Sometimes, like this time, the Charlotte controller knows what I wanted before I can even ask. After I called in with my tail number he just automatically gave me a transponder code and told me to standby for the clearance. Very nice, makes you feel almost welcomed. :)

I made a fuel stop at KMEI in Meridian, MS. It's a great little towered airport with plenty of young navy pilots stopping in for a break from various practice missions in the area. My stop was a short one - I got the tanks topped off, grabbed a free hot dog and drink, filed my next leg on the iPad via ForeFlight Mobile, and went out to the airplane to blast off again.

The next leg was also uneventful, and after a couple of hours I landed at KCFD. I spent most of the time in the air listening to the radio or the iPhone, talking with controllers, and religiously monitoring the flight plan, fuel situation, and engine health.

I was met by my co-workers at KCFD (GREAT airport) and we started a fun and productive long weekend to hash out company plans.




Friday included some flying in the local area. I got to take up one of our developers while my co-founder got in a quick flight with our CFI support lead. We landed at sunset, coded a bit out on the ramp in the dark, and saw two of our staff off as they departed in a C152 for the night flight home.

The flight home Monday was nice as well. I picked up only a little tailwind for the first leg to KJFX in AL. Found some good turbulence around that airport once I was under 4000' but the airport was easy to get in and out of. It was self-serve fuel, and was easy to work with, even with a 15-20 knot very cold wind trying to freeze me while I worked the pump.




I was cranking up again within 15 minutes of shutting down, and soon I was talking to ATC again on my final, shorter leg home. Had a nice 20 kt tailwind for this leg. There were lots of reports of turbulence in the area near home, and ATC asked me for a few reports on the ride (all smooth at 9000), but the flight was easy and straightforward.

I had gorgeous weather for both flights, and managed to hit 510 total hours of flight time after the trek.

Comments

Anonymous said…
Just stopped by to say how much I enjoy using ForeFlight in my A36.

I have added your link to my Blogroll. Keep up the great work.

RB
December 14, 2010 at 11:09 PM
Unknown said…
Ah, MEI. I was once one of those young navy pilots flying an A-4 out of the NAS. I remember clearly one day, on an IFR flight plan, having to take my own diversion to avoid a commuter airline coming out of MEI. Only after it was no factor did I get a call from ATC.

Now I spend my time in a Cessna 182 It doesn't climb as well but the avionics (G1000) are MUCH better.
December 30, 2010 at 4:47 PM
Post a Comment

Popular posts from this blog

Updating data on the Garmin Perspective system

Image
After changing from the Avidyne system to the Cirrus Perspective (G1000) system, I had to relearn an important part of owning an airplane: how to update all the data the systems use. There's even more data in the Perspective, including AOPA directory data and more charts. In this walkthrough, I make use of the Jeppesen app for Apple OS X: JDM .  It has worked well for me, though I did need to call Jeppesen when I first set this up to get my subscriptions fixed up.  They gave great customer support when I did. The process starts (optionally) by hooking up a ground power unit (GPU).  In the case of the Cirrus, you can certainly do this without it, but I tend to hook it up just to be sure.  The systems draw about 8-10amps while updating, but you won't generally have the power on for long.  One tip I've read: power up the GPU before plugging it into the plane, at least for the one I bought.  That saves the plane from seeing any power spikes that might have occurred when t
Read more

G1000 transistion training - emergencies - final flight

Image
For the final flight in my G1000 transition course we focused on failure scenarios. Not the "engine goes POOF" kind but the avionics kind. Normal situation This picture shows what the 2 Garmin screens show in a normal (non failure) situation. You can see we have 2 screens - the left PFD focusing on flight performance (airspeed, heading, attitude, altitude) and the right screen (MFD) focusing on engine data, mapping, checklists, and everything else. Failed PFD screen In this scenario the screen that is right in front of you (the PFD) has failed. This basically means the screen has gone dark. We simulate that by dimming the screen down to 0% brightness. After darkening the PFD we shot a GPS approach into Rock Hill. When this failure has occured you shift the G1000 into Reversionary mode. That means the info that is normally split across 2 screens is now merged into 1. It actually duplicates the same data on both screens, but since the PFD screen is no longer functioning
Read more

A-10C Standby Compass - Sun Shade

Image
 One of the final items to add to this instrument build (besides the text covers for the lower LEDs) was the sun shade for the AR LED box.  I made this out of thin aluminum sheets , cutting it from a template using some metal sheers .    My template was created by tracing some of the actual artwork from the DCS sim, and then scaling it to the proper size. It turned out ok, not perfect but pretty good.  Primed and painted it and then installed it using 2 of the 4 holes that were already on the LED box 3D print.  I used some heat inserts in those holes to give the screws something to bite, but the holes are really too big for my inserts so had to use some glue to help out.  
Read more