Monday, December 23, 2013

Instrument Proficiency Check

Redbird SD1000 AATD
Today I was going to get checked out in the C172 w/G1000 that is down at Rainier Flight in Renton, WA.  I’m not a huge fan of the C172, however it is easily one of the nicest aircraft around and I know that since it is nice my wife “might” actually come fly in it with me.  Ever since we sold the Cirrus, both my wife and I have gotten pretty spoiled in what is out there to fly.  This is the closest thing that I can find that kind of fits the bill, so I booked the plane three weeks ago (earliest I could get in it), so that I might be able to get her up in it someday.  Unfortunately the weather was typical crap for this time of year with 500’ OC and mist.  Great day for flying IMC, but unfortunately KRNT doesn’t have any approaches low enough to get back in to (800’ for non WAAS, and 600’ w/WAAS).  Since the weather was solid IMC, it wasn’t a great day for doing a check ride either.  So instead, I asked Jack if we could do some instrument work in the Simulator instead and he said no problem.
The simulator at Rainier Flight is an Advanced Aviation Training Device (AATD), Redbird SD1000.  This is a non-motion unit that has a reconfigurable cockpit and for our purposes my instructor set it up for the G1000 C172.  My goal here was three-fold.  One, I really wanted to try out the Redbird and see how well it worked.  Two, I wanted to reacquaint myself to the G1000, since I hadn’t flown one in about four years,  and three, I wanted to get some IFR practice in and make use of the time.  Since this simulator is a certified AATD and my instructor is a CFII, the time spent in the simulator is log-able for IFR training.  Excellent!
 
 
 
 
 
 
Since this was the first time using this simulator, I wanted to experiment a bit, so I took off from KRNT and flew to KPAE.  Yes, you could “magic move” the plane, but I wanted to see how it felt and get a good feel for the simulator.  I have heard many people complain about the simulator being too sensitive and unrealistic, and I found that it wasn’t bad at all.  It may be a bit sensitive, but nothing outrageous and the system as a whole worked pretty well.  I will say there are some quirks with the programming of the G1000 that are not correct and the knobs are too sensitive with minimal feel, but if you take your time and pay attention it works fine for the most part.  Some functions like bringing up a “direct to” function, does not auto-populate with “K”, which isn’t very realistic, but overall the functions were pretty good.  The KAP 150 autopilot also doesn’t like to hold its altitude, and if you don’t stop the vertical speed rate at “0”, it will blow through the assigned or set altitude.  That was more annoying than anything and it actually hand flies pretty well when you use the trim wheel.
We started off with a published hold at EYWOK for the ILS Y RWY 16R into Paine Field, then shot the ILS.  I screwed up the missed (failed to brief and UNDERSTAND) the procedure, but then unscrewed myself and went back into the hold again.  The second time I shot the approach, I hoped to better fly the missed procedure, but screwed it up a little the second time too (I was a little rusty ;-) ), but salvaged it.  The third approach was an RNAV (GPS) Y RWY 16R.  This approach went fine no issues and we started to wrap it up since we thought there was someone waiting on the sim.  I landed the sim and Jack check the schedule and the sim was not booked after all. 
Since the sim was open, Jack asked me again about my currency and said that if I had the time, we could do some partial panel work and unusual attitude discuss and he would write me off for an Instrument Proficiency Check (IPC).  AWESOME!  I wasn’t planning on this, but it works for me, so I took off again and this time shot the RNAV (GPS) RWY 34L.  Since Jack killed my PFD, I was working crossways off the MFD with other issues and proceeded to shoot the approach.  We had some good discussion about scenarios, whether or not to declare an emergency and other topics and in the process, I noticed the approach didn’t sequence to the next waypoint (RARYO to USDAW).  Not a huge deal, I thought maybe in my talking I forgot to activate the approach.  I went in and activated the approach and the system reset the approach and expected me to go back to RARYO (IAF).  WRONG.  At this point, I declared missed, and came back around for another try.  One option Jack told me was that I could have just punched in vectors to final, and it would have populated the entire approach.  Good idea, just didn’t think of it.  Second time around, I flew the approach with no issues.
Once we finished we had some discussions about unusual attitudes and the IPC was complete.  I wasn’t aware that you could even do it in a simulator, but according to FAA regulation you can.  Obviously as a simulations guy, I had a blast since I love the idea of training in the sim.  You have the ability to do so much that you are really only limited by your imagination as to what you can do.  Next step for me is to get up and fly.  Although my skills are still ok, I definitely need to spend a little time doing some VOR work.  At least now I can fly again in IMC, I just have to find a plane that I’m comfortable in before I go fly it in actual IMC.  Good stuff and I will definitely spend some more time in the sim in the future!

Wednesday, December 18, 2013

Dr. Richard McGlaughlin's BRS Deployment

It's an amazing story.  Why all GA aircraft don't have a parachute is beyond me.  It just makes sense!

http://www.youtube.com/watch?v=BKwMLGxZJ4w&feature=c4-overview&list=UUzzKrtcSbLq28-JuTfYmZDg

Wednesday, November 27, 2013

Aircraft Checkout


So it has been a while since I have flown last.  With the Cirrus sold back in May, I have flown only one time and that was during my biannual flight review/DA40 checkout at Boeing Field.  I was pretty excited about that flight since I had about 35 hours in a DA40 already and I really like the aircraft.  Unfortunately, the flight school at Boeing Field that has the Diamonds treats flying like a self-licking ice cream cone or herpes in that it’s like the gift that keeps on giving (in a negative sort of way).  First off their prices are pretty steep at $180/hr wet, but on top of that there is a $30 “fuel surcharge”, so you’re really looking at $210/hr.  I rented a like new DA40 in Kansas City that was $155/hr.  What irked me even more is that you have to do a checkride to rent the aircraft, a checkride to fly at night, and a checkride to fly IFR.  It doesn’t matter how current you are or how much you fly, they just want to milk more money out of you and I just don’t agree with that.  The planes are decent, but pretty well used and the whole organization made me feel kind of dirty the way they do business, so I continued to look elsewhere. 

As I looked around I came across a really awesome flight school with great aircraft, great prices, great atmosphere, and an ownership attitude that is committed to helping people to fly.  They have a great fleet of aircraft (3x C162s, 1x C172 with steam gauges, 1x C172 G1000, 1x PA28RT, 1x American Champ Taildragger/float plane, and a nice Red Bird Simulator).  Although I have been trying to get scheduled in the C172 G1000 now for over two months, its limited availability due to all the private pilots renting it (very popular) it’s almost impossible to get.  I have had it scheduled twice, but had to cancel due to IFR weather and you can’t do an aircraft checkout in IMC.  My IFR also lapse, so I have to get that current again before I can actually fly in the IFR system again.  I did notice though that the Arrow isn’t flown very much and since I have over 150hrs in an Arrow, I thought that might be the ticket for me.  Hourly price on the Arrow was only $145/hr wet which was also a pretty good deal for a complex aircraft.  Arrows are fairly fast and this one has semi-updated avionics (new GTN750), and a descent useful load that would allow me to fly the family around since this aircraft is available for overnight travel. 

So today I met up with my instructor Jack and we talked a bit, did preflight and went out and did some air work.  Jack is a pretty knowledgeable instructor and pretty laid back, so we got along well.  After flying around a bit and showing me all the landmarks we came in and did three touch and go’s and the checkride was complete.  It was probably the easiest checkride I have done to date, but then again I used to fly an Arrow a lot, so it came back fairly quickly.  One thing that will take some time though is working on my instrument scan.  Being that my last 614 hours have been behind glass cockpits, I find I’m a bit lost going back to steam gauges again.  This of course will come back with more time in the plane, so I’m not too worried about it.
Although the plane is ok, I must admit, my Arrow seemed like it was much newer than this one even though it was 13 years older.  Mine had 2500 fewer hours on it and was really like new inside and out.  The new GPS in this Arrow was pretty awesome and the paint looks great on the plane, but he interior definitely needs some work and all of the systems seem to be real stiff and tough to move.  Rudder, throttle, prop, mixture, yoke all felt real heavy and tough to move.  Maybe I have just gotten used to how easy the Cirrus flies and how responsive it is to inputs, but this thing felt like I was flying a truck.  This particular Arrow being built in 1980 is a PA28RT, a T-Tail and that might have something to do with it too.  I had always heard that they fly a bit different and I would seem to agree with that.  I really noticed it when trying to land in that I seemed like I kept running out of elevator when flaring and had a difficult time getting the nose up.  Jack said that my landings were better than most and had no issues, but to me they just felt crappy, so I will have to work on those a bit to get them perfect.  I guess flying the Arrow again will take some getting used to, but regardless it was really great to be flying again.  I miss the freedom and challenge of flying and I look forward to getting some more time in the Arrow to get familiar with its quirks and then it will be time to do a Instrument Proficiency Check (IPC) and get back my IFR privileges again.  Life is good!

Saturday, September 7, 2013

FSXFlight

I have always been a huge advocate of Simulations and training using Sims and I personally use Microsoft Flight Simulator X (FSX) a lot.  Mainly I use it to keep my instrument skills sharp, to work on emergency decision making (ie engine failures of all sorts), and I also use it to recon new areas before I fly to them on cross countries.  Yes it may not be exact, but it gives me a lay of the land and a little more familiarity on what to expect.  If you are flying in the Pacific Northwest, the Orbx add-on scenery IS very close and makes this process even more realistic, but that’s another story. 

Last week I saw a new “tool” advertised on Facebook that caught my eye called FSXFlight.  This is a program that you download on your computer and it stimulates your iPad using Foreflight or Wings-X either via wifi or cable as you fly in FSX.  It literally acts just like it would if you were flying in your plane and you looked at your iPad and it will show your icon moving across the map – WAY COOL!  It also shows you traffic (if you pay for that feature in Foreflight) and will also warn you to entering the runway just like if you were taxiing in an aircraft.

Although I have been flying with the iPad now for about three years, I am now using it exclusively since I no longer have a beautiful MFD to look at and because potentially I could be flying different aircraft, most of which will have no MFD.  I upgraded my Foreflight to include the geo-referenced charts as well and I find that they are every bit as good as the Jeppesen charts on my CMAX and even better in some ways, since they will overlay over a sectional, or IFR chart on Foreflight (They are also about $1100 cheaper a year too).  Since purchasing FSXFlight, I am now finding all sorts of cool things that my Foreflight would do, that I had no idea.  It’s a great way to test your “resource management” and to truly learn how to maximize the use of the iPad without burning up hundreds of dollars in avgas.  For anyone that uses FSX and Foreflight, I HIGHLY recommend you buy this program (and I have no affiliation with this company, I just really like the product and it's only $19.99).  It’s easy to install (takes 5-minutes and you are up and running), and provides you an extremely valuable tool to train with.  Check out the website and see the demo video for yourself.
http://www.fsxflight.com/
 


Monday, September 2, 2013

The Last Trip

The 9th of May was both a sad and exciting day for me.  This was the first day of a long journey (2,452 NMs) to deliver my “mistress” to her new owner in Hillsboro, Oregon.  The previous night I had the plane topped off with fuel and parked it on the ramp outside of Aero-One Aviation (KDHN) in preparation for my early departure.  I had intended to get up early and be airborne by 0600 to ensure I had plenty of time to navigate any weather and to allow me to get to Fort Collins, CO to visit with some friends.  As I arrived at the airport, I quickly realized that I was going to be stuck on the ground for a while since heavy fog had rolled in and visibility was too low to take off. 

On the ramp at Dothan, AL

Awaiting the fog to lift
After waiting for a little over an hour, a Baron taxied by did its run up and took off.  I could barely see the aircraft as it passed by me on the runway, but the pilot reported that the tops were only at about 50’ now and that the runway visibility was broken.  This looked promising to me, so I jumped in, started her up and taxied to the end of RW 32.  After conducting my run-up, I received my clearance, taxied onto the runway and took off at 07:19am.  Sure enough, I rotated and before I knew it, I was above the fog in perfectly sunny skies!  My first leg of five for this trip was to Shreveport Downtown (KDTN) 495 NMs to the West.  Originally I was hoping to fly a more direct route, however bad weather over Kansas City didn’t support this, so I decided to go to the west before cutting north and try to stay clear of the thunderstorms and try to get behind them.  My flight time to KDTN was 2:53.  This leg was relatively uneventful as I cruised along at 10,000’, however there was a cell moving from west to east towards Shreveport and as I approached the clouds started to build.  The closer I got, the worse it got and about thirty minutes out, I was in the clouds and had to shoot a localizer approach to RW 14.  The approach went fine, but the clouds were almost to minimums which made it important to get gas and get out of there quickly.
Leg one - Dothan to Shreveport
After arriving at KDTN, I got fuel and found out that there was a nice little cafĂ© in the terminal of this airport, so I went in and got a decent breakfast before heading out for Leg 2.  This leg would be to the Northwest to Great Bend Municipal (KGBD), Kansas via the PGO VOR, which I chose as a waypoint to direct me away from the approaching storm.  After quickly eating breakfast and getting fuel, I departed on RW 14 in ever dropping ceilings and did a climbing right turn up into the clouds and direct to PGO.  What was interesting about this is that I entered the clouds at around 500’ and was then in solid IMC up until approximately 9800’ where I broke out just prior to my assigned 10,000’ cruise altitude. 
Just reached cruising altitude
 
Leg two - Shreveport to Great Bend
This second leg of this trip was also fairly uneventful with a flight time of 2:46 minutes and 505NMs.  Only as I reached my destination did things start to change.  About thirty minutes from Great Bend the sky opened up to just broken clouds and the air started to get a little more turbulent, which is fairly normal as the day goes on and the temperatures rise.  As Kansas City Center (KCC) started to bring me down, they told me to expect the visual.  Shortly thereafter is when my communications started to act up.  The lower I got, the more broken KC Center became.  At one point, KCC reported the airport to my 1200 and 15-miles, to which I reported that I was VMC and looking for the airport, however very shortly after that I lost all communications with KCC.  I continued to call to cancel IFR, but didn’t get any response.  At two-miles from the airport I was still at 4000’ and almost on top of the airport.  I had reported that I had the airfield in sight and wanted to cancel IFR, however I had no communications with KCC, so I chopped the throttle and turned to the Southwest and entered a short approach to land on RW 35.  My thought process was that I had already reported that I was VMC and after that call I had reported numerous times that I wanted to cancel IFR, so I figured I would just land and immediately call KCC and report that I was safely on the ground and that I had lost contact with them.  Being that I was VMC, I felt this was a safe move and all would be fine.  However…

Shortly after landing and taxiing in to the FBO, I shut down and the lineman gave me a piece of paper and told me that I needed to call KCC immediately (shit).  I then called KCC and was told that they were "confused as to what my intentions were" and that I broke regulations by doing what I had done.  He did confirm that they had heard me say that I was VMC, but couldn’t understand why we had lost comms.  I was informed that they had great coverage in that area and that there was no reason for me to not be able to talk to them.  I explained my rationale and everything seemed to be ok.  The only thing that I think I could have done better was to squawk 7600 (no radio) on my transponder to let them know that we had lost comms.  Had I done that, it probably wouldn't have been an issue - lesson learned.  I guess I was busy trying to figure out how I was going to lose all the altitude and not overfly the airport.  At the time that was my logic, but now it's just pretty silly and I should have known better.
After my brief discussion with KCC, I took the courtesy car into town and got some lunch.  One of the cool parts of this trip was the fact that this airport used to be a training base for B-29s during WWII.  There was a pretty cool monument on the airfield as well as some of the old buildings and one of the huge hangers still there.  It’s a shame that there isn’t more stuff there to look at, but the fact that I found this accidently is still pretty cool. 
B-29 Memorial
After a late lunch, I departed on my last leg of the day at 1601 for Fort Collins Regional (KFNL), flight time 2:26.  This would be the hardest part of the trip due to weather concerns.  While the clouds were broken at KGBD, I departed VFR in VMC and started my climb up to 10,000’ again.  I called KCC to pick up my clearance in the air and once again, no contact until I was up to 6,000’.  The controller seemed a bit curt with me, but I received my clearance and all was well. 
Leg three - Great Bend to Fort Collins
Shortly after reaching 10,000’ I noticed more and more cells building and I also noticed the cloud layer below me slowly climbing.  Since it was late in the day the build-up was starting to tower, making things a bit more interesting for me and forcing me to ask for a lot of deviations.  I figured that since I was going West altitude would be my friend, so I put on the oxygen cannula and asked for 12,000’ and then eventually 14,000’.  As I climbed and flew west the clouds continued to rise above me.  This would have been fine except for the fact that as I continued west, I started to hear PIREPs of planes picking up ice.  The last thing I wanted to was get stuck at 14k’ or higher and then have to descent through 10,000 feet of solid icy clouds, so while I still had a few holes, I asked to descent to 8,000’ and latitude to deviate both left and right to get through the clouds.  I was cleared to descend and down I went.  I picked my way around and for the most part stayed out of the clouds, however there was one small benign looking cloud that I couldn’t avoid and as I went through and the entire plane instantly had a thin layer of ice on it.  I turned on the TKS anti-ice system and then was out of the clouds before I knew it.  The TKS cleaned up the wings and windshield really well and I continued on.  From that point I took some vectors and then was put on an arrival procedure to Fort Collins Regional Airport.  By the time I got there, it was fairly clear with patches of build-up and I landed without any issues to complete my leg of 367NMs.  Welcome to Colorado, another state off the bucket list.
MFD/NEXRAD appears fairly clear...  Notice how tight the cells are (NOT good).  This is a great example of how NEXRAD can give you a false sense of security!

10 MAY - Day Two
After a great but quick stop overnight to see an old Army buddy, I departed Fort Collins Regional for the 2:26 minute flight to Ogden-Hinckley (KOGD).  The morning was perfect, clear skies and almost no wind, so I knew that flying over the Rocky Mountains would be pretty safe and relatively easy.  After conducting preflight and taxiing to the end of the runway, I called Denver Clearance to pick up my clearance.  Even through KFNL was an uncontrolled airport, it was right next door to KDEN, so you have to call them for your IFR clearances.  My plan was to depart to the north to the Laramie (LAR) VOR and then follow V85 to Medicine Bow (MWB) VOR, then V6 westbound to Ogden at 10,000’ except at Fort Bridger VOR I would have to climb to 12,000’ to clear the mountains.  Being that I have built in oxygen in the Cirrus, I could easily climb higher, but heading west you have lots of wind and I don’t care to wear the cannula if I don’t have to since they are kind of uncomfortable.  From my perspective, even though I was “crossing the mountains” it should be a pretty easy leg to fly…

Leg four Fort Collins to Ogden
I called for my clearance and that is when all the confusion began.  Since this was a busy area, I should have known that I wasn’t going to get what I wanted, but at the time it didn’t dawn on me.  Approach wanted me to depart KFNL and fly south to the DEN VOR, and then to the east before going north.  My clearance was read super fast and after the controller said DEN VOR, I was like WTF.  As I tried to digest this, I asked the controller why I was flying so far south, when I planned direction of flight was north and it would keep me away from the busy Denver airport.  I was told to stand-by and so there I sat with the engine running looking at the beautiful rocky mountains for about 5-minutes.  The controller then came back and asked if I could immediately climb to 16,000’ direct Cheyenne (CYS), to which I replied no and was told to stand-by again (apparently he must have thought I was a Turbo).  Finally after about 5-minutes he came back and said that if I could do immediate climb to 14,000’ direct LAR VOR, V85 to Medicine Bow (MBW), then V6 to Cherokee and to OGD, that would be the closest he could do for me.  I repeated the clearance and blasted off runway 33 at 8:44am to the north and put on the cannula as I climbed. 
Fort Collins

Me with Cannulas
 
 
Crossing the "first" pass
The entire climb was gorgeous with the mountain range off my left wing and the air was cool and smooth.  I couldn’t have asked for a better morning to fly!  As I reached LAR, my clearance got changed again and I was told to follow V4 to OCS, FBR then on to OGD.  I cruised along at 14K for almost two hours taking pictures like a tourist.  I was concerned about flying the mountains, but in all reality, there really wasn’t anything to worry about along that route.  The pass was low and the area really wasn’t all that rugged.  After getting past the first pass, the terrain smoothed out and it was really easy going. 

 
 
 
From 14K, it was REALLY easy going.  Just shy of the mountain range at Ogden, I came down to 12,000’ and shortly thereafter I crossed the mountain range and got vectors to the north trying to get me down from my altitude.  It took me a while to lose all that altitude, but eventually I got directed into the airport to land on RW 21.  Flight time was 2:26 minutes and 442NMs. 
Ogden on the other side of the mountains

Crossing the range

Hill AFB in the distance

Ogden-Hinckley Airport

Over the edge of the Great Salt Lake loosing altitude
The Ogden-Hinckley airport is a busy, but really nice airport.  With the mountains right behind it, this has to be one of the most beautiful areas I have ever flown.  I stopped at Ogden Mountain Valley Aviation to get fuel and to get some food.  Right next door is the terminal (that also has commercial service) and has a restaurant, but I quickly found out that it was way too busy to get any food at and I needed to keep moving so as to keep my timeline.  I ended up having to get a bunch of junk food out of the vending machines and depart.

Leg two - Ogden to Hillsboro
Great Salt Lake
The last leg of my journey started at 11:51 as I departed KOGD for Portland-Hillsboro.  This would be the longest leg of the journey at 643NMs and a flight time of 3:23.  I had originally intended to stop at Boise since that is where my journey with N779WC had begun several years earlier, but I was on a timeline to get the plane to Hillsboro to its new owner, so I just decided not to stop.  This part of the journey was by far the prettiest of the entire flight.  Departing over the Northeast side I flew to BYI VOR via the V101 airway, then V4 to BOI, then V500 to UBG with radar vectors into KHIO.  I flew the entire leg at 12,000’ and enjoyed a spectacular view of Mount Jefferson, Mount Hood, Mount Adams and even a glimpse of Mount Rainier way off in the distance.  It was a beautiful day to fly with only a few scattered clouds and smooth air.   It was a great leg with no issues and I could just take in the beautiful views and continue to take photos like a tourist. 

Mount Hood




As I approached KUBG, Portland Approach gave me vectors to KHIO and things begin to get busy quick.  As I got closer, I tuned in to KHIO tower and noticed that it was an extremely busy airport with a lot of foreign student pilots not only trying to figure out how to fly, but also trying to articulate English for the tower.  At one point, Approach gave me an immediate 90 degree left turn to avoid a PC-12 and then vectors back to the airport.  As I switched over to tower my traffic started going crazy with “bogies” all over and a little uneasiness came over me as there was an awful lot of student traffic everywhere.  I landed without incident in what I would have to say was a perfect landing on RW31 and I taxied over to the FBO to see the new owner standing outside waving.  At that point reality set in that my beloved Cirrus was now someone else’s.   Although this was very sad, I was also excited at the same time because I could tell that the new owner was just as excited as I was the first time I saw N779WC, and I knew that he and his family were in for a special journey and that they would enjoy her just as my family and I have.
Portland, OR

N779WC was a fantastic aircraft for my family and for our travels.  I flew her 619 hours and landed in 39 different states in just over three years.  I learned a lot about true cross country flying, dealing with weather, flying actual IMC, and I learned a lot about myself.  Although the journey wasn’t cheap, I still believe that it was worth every penny!  For those that read this and think “owning a plane is too expensive” in all honesty it really isn’t all that expensive.  There are many variable and there are opportunities for things to be expensive, real expensive.  However if you do the research and by the right plane, its really not all that bad.  However in my opinion you do need to fly more than 100hrs a year to truly make it financially feasible, but then again that depends on what you get for an aircraft.  The shear freedom to be able to take off at a moment’s notice and go wherever you or your family wants to is truly priceless.  I was able to take my family on many trips to more places then I could have ever dreamed.  We did trips that were impossible by car, or just flat out too expensive to do by commercial air.  The freedom to travel without your kids getting molested or radiated in commercial airports was more than enough reason to own a plane in itself.  The experiences you gain as a pilot is invaluable and truly sets you apart from those that just “stay in the area.”  So as you can expect, there will be another plane in this family again and hopefully another Cirrus someday – no question about it!
N779WC in her new home
 

 

 

Sunday, August 4, 2013

FAA Announces Revised Part 23 Regulations

As reported by AVWeb, see link below.  The FAA has released information on how it plans on streamlining the certification and approval process for general aviation aircraft under Part 23.  The idea is that it will allow airplanes to be certified faster and cost less (50% reduction in both) all while allowing for greater safety.  Allegedly this refined process will more easily allow manufacturers to install things like “angle-of-attack sensors, two-axis autopilots, glass avionics, and other important safety-enhancing systems that can aid the pilot”, which in the past has been extremely expensive to do for manufacturers and has driven the cost of new airplanes through the roof. 

While I’m a huge fan of anything that will reduce the costs of GA and help promote more flying, I fear that this will do very little for the consumer and instead provide more profit for the manufacturers.  As a previous Cirrus owner, it kills me to see the fleecing manufacturers provide on parts for their aircraft and all in the name of “certification.”  When a company demands $10,000 (soon to be $15,000, but that’s a whole different story) to repack a parachute, yet the actual manufacturer of the same chute will repack it for $3500, you have to ask yourself why?  Of course, Cirrus has made it so that no one else is allowed to repack the chute because of “certification” reasons, it’s a self licking ice cream cone for Cirrus and one of the reasons I sold my aircraft.  I loved the Cirrus and I think it’s easily one of the safest aircraft on the market, but they have followed the trail of Beechcraft and have absurd markups on all of their parts making owning one for the rich and famous only.  GA will not expand until the prices of the aircraft come down.  Especially in a horrible economy that this moron in charge has created, GA is barely hanging on as more and more manufacturers of planes and parts go out of business.

We can only hope that this new revision of Part 23, will change things for the better of GA, but regardless the results will probably take ten years to see if it actually makes a difference.  The new proposed revision is supposed to be complete by July of 2016.  Fingers crossed…

Friday, May 24, 2013

Cirrus CAPS



The system works and the statistics prove it.  100% when used within the design parameters!  It isn't a gimmick and gives pilots one more option that could save their lives and their passengers in the event that something bad happens.  Great video Cirrus!!

The Next Step

It has been a while since my last post and much has happened pertaining to my Cirrus and flying.  I have had my Cirrus up for sale for the past couple months and have a lot of “lookers” or “tire kickers” and on two different occasions got to the point of taking it in for a prebuy inspection, only to find out the lookers had another aircraft in contract.  I even had one person accuse me of not knowing what I was flying and told me that my aircraft was “not a GTS, because Cirrus didn’t make a GTS in 2004.”  Luckily for me he was an idiot and didn’t pursue the aircraft because he obviously has no clue as to what he was talking about (yes Cirrus made a GTS in mid 2004 and mine was a late 2004).

As of a couple weeks ago, I sold the Cirrus to its new owner in Oregon.  I had a great final flight delivering her and I’ll write a post on that shortly.  It is very sad to see her go, but the time had come for some life changes and we just couldn’t keep her.  I’m positive that there will be another Cirrus in this family again because it truly is one of the best and safest GA aircraft on the market!  It is by far the best plane for the money on the market right now (new or used) and quite frankly I just can’t see ever owning something like a Mooney, Bonanza, Piper, or Cessna because they are all outdated, small and can’t perform like a Cirrus – AND none of them have the safety of the chute!  Not bad mouthing these aircraft because they are all great planes in their own ways, but none of them come close to the total package of a Cirrus for the mission I had.

So now that the plane is gone, what’s next?  Well it’s time to continue my flying education and start seriously working on my commercial and multi ratings.  Both should be extremely fun, but the multi-rating will be tough because not only is it ridiculously expensive, but it’s extremely hard to even find a twin to rent!  What’s even harder is that I’m now really comfortable with “glass” and don’t want to step back into an old antiquated steam gauge cockpit, so my options are very limited if not impossible.  It should be an interesting adventure, but I look forward to pursuing it and I’ll post about it as I go.

Monday, February 4, 2013

States I Have Flown In


I have been extremely busy as of late with work and life, so I haven't had a chance to get on here and post anything cool in a while. So for my first post of the year, I thought I would share with you this map of all the states that I have flown to and landed in to date. Part of my "bucket list" is to land a plane in all 50 states in this great country. If I can pull off all 50 in a Cirrus, that would be even cooler yet, but we'll see. Of all the states so far, all 33 have been with a Cirrus so I'm off to a pretty good start, but Alaska and Hawaii are going to be tough to do but we'll see.

As you look at the map you will see two states surrounded by green that I have apparently missed. The first one is Vermont. Two summers ago, I took my family out to Ft. Drum, NY on business and in the process we attempted to hit all the states we could while we were there. The on the morning that we attempted VT, it was very windy and turbulent and as I set-up to land, my wife was NOT having a good time. Because of this, I aborted and we climbed back up to smoother air and hoped to attempt it another day. Unfortunately due to bad weather and short on time, we never got back up there and had to return home. This summer I once again went back to Ft. Drum, but like the first time the weather turned really bad and I was not able to attempt it safely, so I just came home.

Maryland is the other state that I missed, but this time it was purely due to poor planning. On that same trip last summer, I plotted out a fun route up the east coast both IFR and VFR to ensure that I hit all the states on the coast. It was executed flawlessly and was a fantastic trip. Upon arriving back home and working on my logbook, I noticed that I had picked an airport right on the border of Delaware that was just to the north and NOT IN MARYLAND. I was pissed to say the least, but it was a great adventure and now I will just have to find another excuse to go back and try again!

This summer I move again and this time to the West coast, so WA, OR, CA, NV, UT watch out, I’m coming to get you very soon!