My First Solo Cross Country Flight

September 9th, 2009

A lot has happened since I last flew.  I am at the point in my training where my CFI thought I was ready for my first solo cross country flight.  For those of you that aren’t pilots, don’t get excited.  A cross country flight is a flight to an airport further away than 50 nautical miles, not literally across the country.  For my first trip, my CFI thought I should fly to KEVY then to KRJD, and finally back to our airport (KANP).  I think my CFI purposely sent me to two airports where most of the VORs were out of service and the automated weather reporting stations were also down.  It was just more adversity I had to add to the equation of this flight and rather than becoming upset about it, I just thought about how I would overcome it.

I planned the flight and after a few weather cancellations, it looked like it was time for the trip to happen.  The first day my CFI would let me make the trip, I could not sleep the night before.  I self cancelled (OK, my wife made me cancel too) because I did not get a full night of sleep.  Another day my CFI would let me go, there was some haze in the area.  Even though local PIREPs (pilot reports) said it wasn’t that bad, the little voice in my head said I shouldn’t go.  It probably didn’t help that I cut my thumb open on a razor and was taped up like a cartoon character.  Every cancellation made me feel like a little piece of my manliness was stolen from me and the anticipation was really building up.  About a week later a hurricane blew through offshore and cleared up the weather.  The winds changed so that it was blowing across all of the runways I would be landing at.  I decided that I would tackle the crosswinds, but wanted to do it on a day I didn’t have to think about work… so I took the day before Labor Day weekend off and went for it.  I think it is important to note that the night before my flight, my son Aiden decided to give me a little advice:  “Dad, try not to bend the plane tomorrow!”.  Wow, that boosted my confidence.

After all the pre-flight activity, my CFI cleared me to go around 3PM on Friday September 4, 2009.  I called my wife to let her know I would be landing around 4:30PM after I filed my flight plans.  I think I actually took off around 3:45 after my wife finally let me off the phone, which was a little later than I originally planned.  I got up to about 2,000 ft and exited our local traffic pattern.  I then talked to Potomac Approach for our local SFRA clearance protocol.  Each time, I was sure to say “STUDENT PILOT” after my “755SP” call sign so everyone know there was a pretty nervous guy up in the sky that did not have the experience of a full pilot.  The controllers were pretty nice and did talk a little slower than usual to make sure I understood everything they said.

I reached my first checkpoint (the West side of the Chesapeake Bay Bridge) and turned towards Rock Hall, MD, which was my second checkpoint.  Somewhere in the middle of the Bay I looked around the plane, then about 270 degrees around me outside and had a feeling…. it felt kind of like taking myself as a 12 year old boy and plunking me into my 34 year old body and then thinking “Oh my, I’m flying a plane all by myself over the Chesapeake Bay!”  Who would have ever thought?  Most of my life, I was scared to fly.  Now I am flying a plane.  There’s irony for you!

I made my second checkpoint without a problem.  I was looking for my third and fourth checkpoints (some towns and big baseball fields on the Eastern Shore of Maryland) while talking to ATC providing me flight following (traffic advisories).  I looked up and realized that I was at a river (which ended up being the Sassafras River), and if my memory was correct it was my fifth checkpoint!  I could not believe how fast everything (literally) flew by!  I was also happy my dead reckoning navigation was working well because I was exactly where I was supposed to be!  This was about the point where Potomac ATC dropped my flight following and could not hand me off to Philadelphia ATC because they were not responding to them, but was nice enough to provide their frequency.  The controller was really great, he told me everything I needed to do to get on Philadelphia’s frequency.  I knew I was getting decently close to the airport (KEVY) and listened to Philly ATC.  It was much busier than Potomac and not easy to jump in for flight following for the few minutes of flying I had left.  I decided since I was closing in on the airport pretty quickly, I would start reporting my position on the common KEVY frequency.  I did not see the airport, but knew I was getting pretty close pretty quickly.  The Cessna 172SP moves along at a good pace let alone when you’re the only person weighing it down (don’t worry, my CFI isn’t THAT heavy).  At this point in my confusion, I will admit, I looked at the GPS to see where I was.  I cheated, and I feel bad about it.  I couldn’t keep up with everything going on and it seemed like the safest thing to do.  I found that I was nearly on top of the airport in no time.  What I did not expect was that 3-5nm on a map puts things closer than you would think when you are a few thousand feet above them.  For things that close, you have to look down and not straight out your windows.  After I successfully located the airport, I noticed that I did not hear anyone using the airport on the radio.  I decided to overfly the field at a higher altitude than traffic pattern in order to check the winds and to see which runway was in use.  At this point a seaplane flew across my path from left to right in front of me and was climbing higher than I was.  That was very unnerving!  I was trying to concentrate on my landing and this traffic came out of nowhere!  Even though I was on his right and had the right of way, I dropped 500ft and banked to the right just like my CFI once taught me.  Now I was about 500ft above the traffic pattern and looking for the winds… they said runway 35 was active.  I set myself up for the landing and I will admit… it was a pretty good one!  I’ll take the good landings when I get them.

I taxied back to runway 35 and pulled off in the runup area to switch my charts and navigation logs.  After I performed my runup (I figured sitting at idle for a few minutes might warrant it) I waited for the same seaplane I saw before now landing at this airport (he had wheels too).  He landed and cleared the runway, so I made my radio calls and took off towards KRJD.  After I navigated the traffic pattern towards KRJD and departed, I called up Philadelphia ATC for my flight following.  Although I said “STUDENT PILOT”, I think there is an air traffic controller in Philadelphia somewhere that wasn’t happy I was in his airspace.  I had a little trouble communicating with him at first, but we got everything straight and all was good.  Philadelphia handed me off to Potomac and they guided me the rest of the way.  I must have said “STUDENT PILOT” too many times because they even called out the airport to me.  However, I thought he said “Traffic at your 12 o’clock” because I said “Traffic not in sight”.  He said “755SP I said your airport is at your 12 o’clock and there is not traffic at your 12 o’clock”.  I couldn’t help but laugh, say thank you, and tell him I had the airport in sight.  My problem was that the plane was still traveling faster than I expected, plus miles up in the air are really small so you’re usually having to look down more than “out” the window.  That is something I’ve vowed to work on for my next solo cross country.  I’ve flown with my CFI many many times, but this realization came to me on my first solo flight because I had to do everything inside the cockpit.  It could have been worse, so I was still happy.  I remembered thinking that KRJD was the same width as KANP, but was much longer and looked really really tiny from where I was.  I wondered how I was going to get the plane on that runway.  I was duped by an optical illusion that I once read about, but didn’t realize until I actually had it happen to me.

Getting into the pattern after overflying the field at KRJD was not my most admirable moment as a pilot.  Basically, I messed it up.  I don’t know how, exactly, but I messed it up and wasn’t even level or pointing exactly where I wanted to point when I was abeam the numbers.  I thought I could correct it by the time I turned to my base leg for runway 12, but I realized I should just try again because I didn’t think it was correct or safe for me to continue how I was flying.  I called a go around on my base leg.  I think that was a first for me, calling a go around on my base leg when I wasn’t even pointed towards the runway.  I executed my go around and announced on the radio that I would circle around the airport and announce when I was reentering the traffic pattern (correctly).  I’m sure there were people somewhere listening to me on the radio and laughing, but I didn’t care.  I needed to do it right and that was the best way I could think of doing it.  The next time around wasn’t as bad, but I was higher than I wanted to be.  That’s atypical for me because usually I’m dragging it in.  I landed on runway 12, but it wasn’t one of my better landings.  I taxied back to the runup area next to runway 12 to settle my nerves, switch my charts, switch my navigation logs, and get my head on straight.  By the time I took off from KRJD I was supposed to be landing at KANP, so I wondered if my CFI was concerned.  I should have probably text his phone, but I wanted to continue to concentrate on the plane and my flying solely.

I took off and contacted Potomac to get my flight following.  ATC cleared me during my flight following into the SFRA, so that was another radio call out of the way.  I really do love VFR flight following.  I don’t know why people don’t use it more often!  The flight was uneventful other than wagging my wings at some traffic in the area.  There seemed to be more traffic in the area than normal because of the holiday weekend.  Other than overshooting runway 12 a little when I was on my base leg turning final, my landing was pretty good at KANP!  I was glad, because my family (Andrea, Aiden, Madeleine, and Charlotte) decided to come to watch me land.  I was about an hour after I told them I would be back, but I was back!  Nothing was bent, but I was pretty sweaty and nervous.  I was glad it was all done and now I’m excited for my next cross country solo.

I learned a lot from this trip.  I learned how I must pick better visual checkpoints and to expect checkpoints only 10nm apart to come at me really fast.  I also learned that 3-5nm in the air means what your looking for is probably down, and not out a ways.  I think those are all things that will get better as I fly more.  At least, that’s what my CFI told me after my flight.  He said he wasn’t surprised that I used the GPS and actually expected I would.  He said as I become more confident all the multitasking will become easier for me.

I really wanted to kiss the ground after I landed, but I thought that would scare my family too much.  I was glad I was back safely and proud to have logged my first solo cross country flight.  It was something I needed to do, and I finally did it.

I added 2.0 Hobbs hours as the Pilot in Command, Solo, and Cross Country to my logbook with 3 successful landings.

  • Twitter
  • Facebook
  • Delicious
  • Digg
  • Share/Bookmark

Look Ma, forward slips and no flaps all before the 1,000ft markers!

August 19th, 2009

On 8/14/2008 I flew to Easton, MD (KESN) with my CFI to practice some crazier landings before my first solo cross country flight.  We wanted to get in some no flap landings and more practice with forward slips, you know…. “just in case”.  I haven’t been through a no flap landing in quite a while, so it was nice to do them again with my current knowledge base rather than when I was still learning the basics back then.  Keeping the nose up on a no flap landing felt really really weird because with flaps you’d be aiming right at a stall using that pitch.  I couldn’t imagine doing it at night without power because you can barely see the runway in front of you!

My favorite part of this flight was when my CFI took the controls, put me at not-so-normal landing configurations, and said “now land the plane in the first 1000ft”.  Usually he put me really really high (around 1000ft on short final) and I had to add all the flaps, get lined up with the runway’s center line, and forward slip my way down before the 1000ft markers would pass me.  For the record, I made it within the 1000ft markers each time.  However on other landings when he said “put it ON the 1000ft markers” I landed short of them because I thought he was still telling me to land before them.  That was an unfortunate misunderstanding.  Either way, I was happy with my results.  I can put it on the markers when requested.

This day I saw possibly the WORST closed traffic pattern flown by another aircraft.  When we were on a closed traffic downwind leg this aircraft looked like he departed the pattern at a 45 degree angle and was in another city before he turned left to his base leg.  It was pretty unbelievable.  He had to be 4 or 5 nm away from the airport before he turned base, which is traditionally about 1 nm away.  We left Easton after being behind that aircraft a couple of times around the pattern because it was just too painful.  It’s hard to fly the pattern at 80kts wasting your rental time while the guy in front of you wanders off on his own version of a downwind leg.  It seems almost dangerous to me.

This day I logged 1.4 Hobbs hours and 12 landings. Next up, my first solo cross country flight!  Only 8 more hours of solo time, 0.2 hours under “the hood”, a couple of stage checks, and the FAA checkride stand between me and the end of this training!  I’ll be training straight into my instrument rating right after that.

  • Twitter
  • Facebook
  • Delicious
  • Digg
  • Share/Bookmark

I saw in Aiden’s face that he needed to go flyin’…

August 19th, 2009

On 8/12/09 I woke up and got ready for my usual Tuesday morning flight with my CFI.  Things have been busy around the house and work, and I probably haven’t given the Daddy time the kids are used to from me.  When I was getting ready to leave, Aiden asked me if I would build him a paper airplane.  When I looked into his face that morning, I could clearly see he needed to go flyin’ with his Dad.  However, the last time I did touch and gos with him he was confused why we weren’t getting out of the plane to go to the airport’s “plane toy store”.  I had to let him know that this morning we wouldn’t even be leaving our airport and we would continue to take off and land until his Dad was feeling good about the small runway so I could start my solo cross country flights.  He didn’t seem to care that he wasn’t going anywhere, the bottom line was that he got to get in a plane and go out with his Dad.

The touch and gos went well.  I’m really getting comfortable with my skills as a pilot.  I do not really have anything to report other than Aiden loved the forward slips to landing we performed to lose altitude and airspeed.  Anytime we make the plane do something “not normal”, he thinks he’s an instant fighter pilot.  Now when he sees planes land at our airport he yells “Do the forward slip!”

I added 0.9 Hobbs hours with 7 full stop landings in my logbook. So did Aiden.  After we flew I took him out to lunch and he gave me his Jones kid patented thumbs up pose with his “not approved by Mom” milkshake:

7

  • Twitter
  • Facebook
  • Delicious
  • Digg
  • Share/Bookmark

Flyin’ to Jamestown, VA

August 19th, 2009

I am behind three flights in my blog again.  Let’s see if I can get us back up to date.

On 8/9/09 I was able to fly with my CFI to pick up another CFI in Jamestown, VA (KJGG) in the plane the second CFI owns.  The plane was a Cessna 182Q, and I’m still smiling about the extra room it had inside.  I didn’t have to sit shoulder to shoulder with my CFI.  Size wise, if a C-172 is a Chevy Trailblazer, the C-182 is a Cadillac Escalade.  When I sat in the back seat on the way back I couldn’t believe how I could almost stretch my legs all the way out!  The flight both ways was smooth, uneventful, however hazy.  The C-182 had a constant speed propeller which made it a little different than the C-172, but it didn’t have retractable gear so it was not of the “complex” class of airplane.  I also think I’m getting used to adjustable propeller airplanes, along with having a carburetor to worry about (the C-172SP I train in is fuel injected).

I enjoyed watching my CFI and the CFI/Owner splitting the piloting duties on the way back.  One was on the radios and checklists while the other was flying the plane.  I’ve never seen that before and looks to be very useful!

Here are some pictures I took when I was a passenger on the way back:

On the way down I was able to log 1.0 hours of Hobbs time with 1 landing in the C-182.

  • Twitter
  • Facebook
  • Delicious
  • Digg
  • Share/Bookmark

Do you think we would need to call someone if those mortars hit us?

August 7th, 2009

After my last flight on 7/16/2009 I needed to complete my night cross country requirements.  It was difficult to get this done because civil twilight begins at approximately  20:45 local time and the airport closes at 22:00.  My CFI is able to get an extra 30 minute waiver from our airport to make the flight possible, but the time frame is still tight to land at an airport over 50nm away, do two extra night stop and gos, and get back.  Not only that, but we have had storms almost every night in our area that begin just before I needed to take off and dissipated just after I would land.  This occurred for nearly two weeks straight.  I must have planned the cross country flight over 10 times only to call it off after the storms formed.  I even had backup plans to fly to KHGR if the weather was better to the northwest.  On Saturday 8/1/2009 I was finally able to complete my night cross country requirements because the storms were a little further away than previous nights.

We flew from KANP to KSBY.  It was an uneventful flight that I do not have many details for.  The night was not the usual Maryland hot and humid night, there was a nice light coming from the moon, barely any wind, and the visibility was pretty good.  We flew direct from KANP to KSBY.  I was able to get some time under the hood too.  We came into KSBY from the exact direction we needed to make a straight out final to runway 14.  After two (and I’m not exaggerating) flawless stop and gos, we attempted to finish up our last stop and go so we could head back to KANP.  This is where things got weird.  To the right of the left base leg for runway 14 there is a stadium.  It is about 1.5 to 2.0nm from runway 14.  Instead of my usual 1.0nm base leg from the runway, I was a little further out at 1.5nm or so.  This is not normally a big deal.  All the sudden my CFI said “Look at that, they’re shooting fireworks!”  and I saw mortars exploding outside the right side of the plane, at the same altitude we were at (700ft MSL or so).  I could see all the fireworks closer than I ever imagine I would ever see fireworks in my life.  We weren’t in immediate danger, but it wasn’t comfortable for me to be there.  No one warned us and I do not recall any related Notams attributed to this event.  It was just a case of being at the wrong place at the wrong time.

My CFI said “Do you think we would need to call someone if one of those hit us?”.  I said “Yes, and I’m on SBY’s control tower frequency so I would let them know and try to make the safest landing I could”.  He said “No, I meant as in the FAA or NTSB?”.  My CFI was obviously quizzing me on the reporting requirements I learned in ground school.  I said my concern was getting on the ground safely first, and then I would worry about my reporting requirements second.  My focus was a little more immediate than the subject his question addressed.  To answer his question, though, I said I believe it qualified for a phone call to the NTSB but I was unsure if it was an immediate notification or one that could be made days after the event without looking up the specifics.

As I told my CFI, I will never, ever, in my piloting career forget how close those fireworks were to the plane.  I can not accurately describe in words the magnitude of the bright white, pink, and red lights that lit up around us.  I don’t think I will ever look at stadiums on the ground the same way at night again.  Fortunately, my last landing went as well as the first two and we turned back around to KANP in order to get back on the ground before the weather changed.

I added 1.6 total Hobbs hours (at night and cross country), 0.5 hours under the hood, with 4 full stop landings to my logbook.

Next I look forward to some strong crosswind landing practice, becoming more comfortable with the small runway at KANP, and cleaning up odds and ends before my CFI sends me on my first solo cross country flight.  Hopefully I won’t have to wait two weeks for the stars to align again.  I am excited to finish up my training so I can start working on my instrument rating.

  • Twitter
  • Facebook
  • Delicious
  • Digg
  • Share/Bookmark

My first night flight

July 17th, 2009

Yesterday, July 16th, I got to fly at night for the first time.  Since Aiden hadn’t flown with his grandpa this week I brought them both with me.

I find it kind of ironic that my flight training, which has taken nearly 2 years, hasn’t required night flights until mid summer, when the airport closes at 10PM and the sun sets at 8:32PM.  That does not leave a lot of time for night flights!  However, this night we tried to beat the clock and my CFI called the airport owner to get an extra 30 minutes waiver.  Aiden and my father in law came out to preflight the plane with me.  Aiden is apparently on the speed plan when it comes to preflighting an airplane.  He was to the tail of the plane before I was done checking the ailerons!  He cracks me up.  He walks around the plane and calls out the parts and says “check” after seeing them.  “Daddy, tail…check.  Doors…check. Propeller…check.”

We took off and even before I turned crosswind I felt the difference night makes.  I could not see the horizon because it was dark.  I did not know where to “put my nose on the horizon” like my CFI always tells me.  I also could not see out of the corners of my eyes the trees moving by to give me the reassurance of our speed.  I turned crosswind and then turned where I think the downwind was supposed to be (I could not see the creek I normally use for the downwind turn during the day) and headed out over the Chesapeake Bay.  To be honest, I couldn’t even tell when we were over water versus land.  It was that dark.  I could see lights on the boats, but that was about it.  One boat was big and bright enough to look like a plane without its flashing lights on.

Earlier this week I was explaining to my father in law that the backseat passengers were behind the center of gravity in the plane and all of the maneuvers feel exaggerated compared to when you’re sitting up front.  That was why we didn’t do a forward slip on Tuesday’s flight.  I sort of gave my CFI a wink in the dark and repeated what I said about the center of gravity and my CFI offered to show them what I meant.  He wagged the tail of the plane so it felt like we were flying sideways in the dark.  He also pulled up and pushed us down so we were at zero G’s for a few seconds.  Aiden LOVED this!  He thought he was being a fighter pilot.  I think his grandpa thought we were going into the drink.  I laughed and asked if he wanted to go out and do some spins with my CFI, and he politely declined.

We called KESN when we were about 8 out to the North West.  I could not see the airport yet.  Then my CFI said “You should be able to see it now, point it out”.  I laughed, nervously, and said “I don’t see it still”.  Then I pointed to a strip of lights, because he said I would see the runway first.  We headed towards the lights and I realized it was actually a strip mall.  My CFI laughed and turned us towards the runway.  He said he would perform the first landing.  I still could not find the runway when we were on the downwind for a right hand turn (it was out his window).  I finally found the runway on our base turn.  Wow, I did not think night time was going to be so different!

After my CFI performed the first landing, I took over.  I probably looked pretty funny if you could see me in the night because I couldn’t figure out where to put the nose of the plane and I was bobbing around a little.  I also overshot my altitudes and air speeds.  My CFI said “You’re going to have to watch those, I know that’s not something you would let yourself do during the day”.  I think that was a compliment.  I think.

I performed a few landings without any serious problems other than overshooting my bearing, altitudes, and air speeds.  The whole time I hear this little boy’s voice from the backseat saying “Daddy… Daddy… Daddy… Daddy….”.  My CFI said “What’s up bud?”  and Aiden said “Why do we keep landing and taking off?”  I think Aiden thought he was going to a toy store.  Then my CFI laughed and said “that’s realistic cockpit distractions” and I laughed and said “with 3 kids, my whole life is a distraction”.  The nice controller also wanted to show us what the light gun looked like to us since he knew we were training.  It was pretty neat.  Very very bright.  I wonder what the power rating of that light is.

We flew home and my CFI showed me how to use the autopilot to guide me home if I got lost in the dark.  It was really cool.  We flew though some slight rain and Aiden fell asleep for a bit.  We landed, parked the plane, and put it to bed.  This was the latest Aiden’s been up, I think.  He then said he liked the “fighter pilot” stuff we did and I said he could go up for spin training with my CFI when he’s 10, in 4 years.  I don’t know if he’ll remember then, what do you think?

I added 1.1 Hobbs hours of night flight with 5 full stop landings to my log book. My father in law said I seem more confident and a better pilot than the last few times he flew with me.  That’s a plus.  I look forward to my next night flight.

  • Twitter
  • Facebook
  • Delicious
  • Digg
  • Share/Bookmark

Madeleine’s second flight

July 17th, 2009

On July 14th, it was time for my Tuesday morning training flight.  My father-in-law was in town and he likes to go flying when he’s here.  Ever hear of the $100 hamburger?  We go for $250 eggs and $50 toy planes.  So considering the Cessna has four seats my CFI, my father-in-law, and I take up three of them.  I came to a brick wall in my life… I had to choose one child for the remaining seat.  Technically, it was Madeleine’s turn but she does not always seem as into flying as Aiden does.  Plus, she likes to hang out with her grandma and mom and go girl shopping.  I offered the seat to her, partly expecting she would decline it for her brother, but that wasn’t the case.  She said “That seat is for ME!”.  Now I had one sad boy on my hands because he couldn’t go.  Well, we planned it so Aiden could fly with his dad and grandpa on Thursday for his (and his dad’s) first night flight.

On this morning, we decided we would fly to KCGE and have breakfast.  Then we would stop by KESN on the way back to practice some touch and gos, and maybe stop by the airplane toy store to pick up a little something for the kids.  We flew over to KCGE without a problem and Madeleine’s dad made a great landing.  My father-in-law video taped the whole trip (I’ll post the video’s when I have more time).  I enjoyed seeing what it looked like from the back seat after we got back home.  Wait, did I just give away the ending?  Yes, we made it back home in one piece.

I was in shock at the amount of the breakfast Madeleine put away.  The breakfast at KCGE is always huge.  A grown male would have trouble eating it all.  My 4 (almost 5) year old little girl finished the whole thing.  When her grandpa tried to dip his toast in her eggs, she responded with “Get your own eggs, old man!”.  It was cute.  Here’s a picture of her polishing off another slice of toast:

DeedseyFlyingBreakfast

She is wearing her pink “Yes, girls can fly!” t-shirt from Girls With Wings for her second flight.

I have some cute video of her in the plane giving the traditional Jones-kids thumbs up and picking on her grandpa a little too.  I’ll post it once I edit the nearly 40 minutes of video into computer files I can post here.

Madeleine (who we affectionately call Deedsey because Aiden could only say ‘Dee-Dah-La’ when she was born) enjoyed watching a plane practicing touch and gos on the runway right out the window where we sat to eat breakfast.  I began to realize that Deedsey really liked this flying thing.  She didn’t give up her seat, she seemed happy, and I didn’t have to drag her to this outing.  I even saw her smile a few times.  I was proud!

We took off from KCGE and called Easton’s tower to begin the landing (the airports are really close).  The weather was a little bumpy because of the winds and the thermals, and the controller was a little…odd.  He vectored us into an extended right base for a runway that was traditionally left, and he said we were #2 for landing behind another plane at our 9-o’clock.  We looked while on the extended base out the left side of our plane and we saw the #1 plane out of our window.  My CFI grabbed the controls and told the controller we were going to break out of this clearance to come in behind this plane and the controller responded by changing us to #1.  By this time we were coming in a little fast because of the tower confusion and my CFI landed us.  He landed at a higher airspeed without doing a forward slip to slow us down and to lose altitude because he didn’t want to freak out our backseat passengers.  I explained to them the forward slip later in case we ever do it so they won’t have a heart attack, like I did the first time my CFI did it.

Deedsey picked out a P-40 fighter for her brother as soon as we entered the store.  It was really sweet of her.  She always thinks of her siblings first.  At first she was going to pick out a girly pink roller bag with a doll for herself.  I didn’t say anything.  Soon after, she found a Russian Mig snow fighter jet toy she liked better.  I considered that a little victory, and it was her first jet toy.

As we were leaving I asked my CFI if he wanted me to do a couple touch and gos.  He said it was a little bumpy and we should probably just head back home with our passengers.  I was kind of in shock, that’s the first time he’s suggested we go back home and not me!  I was comfortable doing the landings in the bumpy weather.  It must mean I am becoming a little better at this flying thing.

I am also surprised that Deedsey was quiet on the radio because her older brother is a chatter-box.  More on that in the next blog post.

I added 3 landings and 1.5 Hobbs hours to my log book. Deedsey and her grandpa liked the flight and it all worked out well.  No kids were left out of their flying rotation, so far…

  • Twitter
  • Facebook
  • Delicious
  • Digg
  • Share/Bookmark

My first solo at a control towered airport

July 17th, 2009

On July 9th, I was mentally prepared for my solo at KESN, which has a control tower, in N755SP.  The plan was simple:  go to KESN, do a few landings with my CFI in the plane, do at least 3 solo landings, pick him up, and then fly home.  We were off from KANP and headed to KESN as planned.  The plane still pulled very slightly to the right, but it wasn’t a big deal.  We called up Easton’s tower and let them know we were coming.  We performed four (somewhat) flawless landings with my CFI in the plane and parked the plane at the terminal.  This was the first time I’ve been able to talk to ground control which was fun, too.  I got out of the plane for a bit to settle my nerves for my solo.  After a couple sips of water and some walking around, I was ready to get it done.  I figured no matter whenever I did this I was going to be nervous, so I might as well get it done.

I got my clearance from ground control and rolled out to runway 4.  I performed my runup and checked the checklists, everything was good.  I took off and everything seemed to go well.  My nerves calmed down a little bit as I turned crosswind to downwind.  I called the tower to let them know I was mid field and was going to perform a full stop taxi back landings.  They gave me the clearance and I repeated it back.  I made my turns and landed slightly harder than I wanted to, but it wasn’t bad.  I’m just a perfectionist.  I even squealed my wheels a little too when I was stopping on the runway.  On my taxi back to the start of the runway, I remember thinking “well, if I can do that once, I can do that two more times”.  After realizing that, my nerves settled down.  I was cautious, of course, but I wasn’t really scared or nervous as I thought I would be.  My second landing went as well as my first.  I wasn’t exactly on the center line, but it wasn’t too bad.  On my third attempt, everything went pretty well except repeating back the clearance to the tower to land.  He said “755SP you’re cleared to land #2 behind the plane on final” when I was abeam the numbers.  First, the clearance came a little later than the other two and I unfortunately paid more attention to that than noticing I’m a little higher than normal and past the numbers to initiate my landing procedures.  I also could not seem to get the pitch of the plane right on this attempt.  I repeated back the clearance as I configured the plane for the landing and I must have messed it up, because the controller repeated what he said before.  I repeated what he said correctly and I was cleared to land.  The landing went well and the other plane landing in front of me was not a factor.  To this day I’m not sure what I said to mess up the confirmation of the clearance.  I could have said “My name is Keith and I have no idea why I’m in a plane by myself” for all I know.  However, I fixed the confirmation and it went well.

This trip really taught me the power of saying “Student Pilot” after your call sign.  I think the controller takes a little better care of you knowing you’re probably pretty nervous soloing up there.  I also try to limit extra speaking on the radio, but I still try to say “thanks” at the end to let them know I appreciate their help.  I can’t imagine their job is easy and they probably have a lot of not so nice pilots to deal with on a daily basis.

After I went back to the terminal I realized they had a pilot shop with some Hot Wings toy Cessna 172 Skyhawks.  Since I am notorious for being a softy for my kids, I bought them both one.  I picked up my CFI and we went home.  Aiden and Madeleine loved their new “Daddy Planes” and they both slept with them that night.  I love enjoying the rush and sense of accomplishment you get after knowing you just flew by yourself.

This flight added 8 landings, 2 total Hobbs hours, and 0.6 solo/PIC hours to my log book.  The next week’s flights will be with my kids and my father in law.  It will be fun!

  • Twitter
  • Facebook
  • Delicious
  • Digg
  • Share/Bookmark

A bent trim tab, a control tower, oh my!

July 17th, 2009

I’ve been bad at keeping up with my flying blog, so I have 4 posts tonight.  Hold onto your seat as I catch you up on two weeks of flight training.

On July 7th, I accomplished my first serious training at a control towered airport at Easton, Maryland (KESN).  After an uneventful takeoff at KANP in N755SP, we were flying to the Eastern Shore over the Chesapeake Bay.  I noticed the plane kept wanting to pull and roll slightly to the right.  I just added some left rudder with my foot and we moved along.  After my CFI took over near Easton’s runway, I said “It’s pulling a little to the right” and he said “You need to tell me these things when they happen!”.  I was a little shocked, because I’ve spent most of my training thinking everything was weird and any wrong move could lead me to my death.  The plane pulling to the right didn’t seem like a big deal to me compared to other things I had to mentally overcome.  I understood why he wasn’t happy at the time now because he said he was going to have me solo at the towered airport and he didn’t want me to fight the plane.  Oh well, I can solo another day after we got the trim tab flying straighter.

I was doing OK with the calls to the tower, but they weren’t perfect.  On this day, I kept forgetting the four W’s:  Who, Who, Where, What… for example “Easton Tower, 755SP 10 to the North West for touch and gos”.  It was good practice because I think I have near 200 landings at uncontrolled airports, and this was the time to add the extra complexity to my routine.  I also learned that control towered airports may not have you fly the traditional pattern to land.  They may vector you straight in on final or even base.  This was different, and I need to learn how to configure the plane when I’m not in my traditional box (or trapezoid) pattern.  That will take more practice.

We also practiced short field landings.  I’ve done a few of these before at other airports, but I couldn’t seem to get the flow right because it felt like I was going to crash land before the runway started.  I still don’t have full trust in ground effect.  All of the maneuver books I’ve read confused me even more.  I could not visualize what they were saying.  Things like “start your round out earlier” but the airplane being higher in the air in the pictures confused me.  Well, I think I have it figured out now.  Basically, a short landing, from what I can tell, is the same as a normal landing except you just aim your round out much earlier so your wheels touch down earlier on the runway.  You also apply heavier breaking.  That’s it.  Nothing fancy, just use less of the runway.  My CFI suggested that I treat every landing as a short landing and then I would just be used to doing them.  I hear they are the #1 cause of failure when you go for your check ride with the FAA at the time you receive your license.

After we finished the lesson we headed home.  We bent the rudder trim tab a little to compensate for the pull to the right and discussed doing my solo at KESN on Thursday that week.  I added 1.4 Hobbs hours to my log book with 7 landings.

  • Twitter
  • Facebook
  • Delicious
  • Digg
  • Share/Bookmark

It was time to go for a spin…

June 26th, 2009

And by “spin”, I didn’t mean just fly around.  I meant the type of spin where one wing stalls worse than the other and you spiral towards the Earth.  In order for you to understand how I got to spin, you need a little background on my past two flights…

On Wednesday I was excited to fly my old trusty N754SP and get back into the Cessna 172S after spending time in other planes recently.  I’m really excited and anxious to finish my training because I started it back in December of 2007!  Everything leading up to the flight went as planned.  I got my SFRA clearance from Potomac and we were on our way to Runway 30 to leave.  I performed all of my checks and made my local radio call without a problem.  We rolled down the runway and lifted off.  This is where my problems began.

First, my indicated airspeed was about 60kts instead of the 65-67kts I use to climb at Vx, but my sight picture seemed way off.  I wasn’t angled upwards as much as I felt I should have been.  Then, I made my radio call to Potomac (after making my last one to KANP traffic) and messed up my well practiced responses.  I sounded like a tongue tied teenage boy on his first date with a pretty girl.  It was bad.  This has not been a problem before.  Then I got into the pattern at KFME just as two other crazy pilots got there.  Now, I’m fully aware I am a student pilot and not as good of a pilot as many other people out there…. but these guys were crazy!  One entered a pattern directly above us and was reporting he saw us, but was really seeing the Cessna in front of us.  He also had a tail number that was only one number off of ours and it was very confusing.  After we avoided problems with a 360 degree turn to reenter the pattern, the other pilots starting flying patterns that did not even resemble a rectangle.  Now, my patterns usually resemble odd trapezoids.  But my trapezoids looked like perfect traffic pattern attempts compared to what I was seeing outside my window.  For example, one pattern the other pilot flew extended the downwind leg by 3 times the normal length and he was already really far to the left of us (for a right hand turn to runway 10).  We had to pull the power to perform slow flight so he could turn base and final without him colliding into us!  My CFI was visibly and verbally upset at the air shenanigans that was going on around us.  I’ve never seen him that unhappy with other pilots.  He kept telling me to fly the proper pattern that I was already in, and (most of) the problems weren’t coming from me.

On my landings I could not get the airspeed right, which meant I was either coming in too fast or on the wrong glide path.  One landing had a bad round-out so I performed a go-around.  Luckily I’m to the point where I just do it and my CFI doesn’t get involved at all.  He said “Good” because I just performed it without him telling me to.  However, I messed up retracting the flaps properly.  It seemed like anything I did was wrong.  I also noticed that I “baby” the controls because I don’t want to drop a wing and it’s really beginning to frustrate me (more on that below).  We finally left the pattern and headed back to KANP.  I messed up the call to Potomac again.  At this point I think my CFI saw I about had it and he was encouraging me.  I think he was sure to smooth over whatever I did wrong.

When we landed I addressed my soft touch on the controls with him.  I told him I am really worried about putting the plane into an accidental spin when I’m in slow flight (or landing).  He said, “Well, that’s an easy thing to fix.  Come back to the airport 8AM tomorrow and we’ll take up the Cessna 152 for spin training.  You don’t get motion sickness do you?”  Luckily, I don’t.  So after working through my post flight adrenaline and not trying to beat myself up too much about the bad flight, I took care of my paperwork and went home. I really felt like a failure after that flight, but I was at least alive.  I still beat myself up about it.

The next morning I showed up for spin training.  I have to be honest, I was a little scared.  I have 110% trust in my CFI because his experience and skills are amazing in my opinion.  I wasn’t afraid of getting into trouble, but I was nervous nonetheless.  The 152 was definitely different than the 172.  It’s more like climbing into a Pontiac Fiero than it is a mini van.  You lay down more than the 172, in my opinion.  It’s also a lot slower.  A lot.  We flew up to the wildlife refuge area to the Northeast of the Chesapeake Bay bridge and leveled at 4,000 ft.  My CFI showed how the airplane behaved during slow flight and stalls.  He then made me do it for myself.  Then, he showed me an incipient spin but corrected before we got to the full spin stage.  It wasn’t too bad!  Not as violent as I expected.  Then he did the same move but let the full spin develop.  I was surprised that the rotations were so fast.  The spinning didn’t bother me, but the sudden kick of the elevator and the recovery upward pitch made me go a little cross eyed the first couple of attempts.  Now, it was my turn to do the same thing.

My first attempt at a spin really put me at ease about the whole deal.  If you’re not familiar with how it works, you put your plane into a power on slow flight configuration by pitching upwards.  As the airspeed bleeds off you give the yoke a little pull near the stall speed.  At this point both wings begin to stall.  As the wings begin to stall you stand on the rudder in the direction you want to spin (which is the opposite of what you are trained to do in this case).  Spinning to the left is a little easier because the plane already wants to turn left due to the left turning tendencies produced by a propeller.  Once your plane rolls into the incipient spin stage you keep the power in and stay on that rudder until the full spin develops.  In my first attempt I prematurely let off the rudder as the incipient spin occurred and the plane corrected itself with little control from me like this video demonstrates:

(Note that none of these videos are actually of me, as my hands were full at the time. I found good examples on YouTube to get my point across.)

The result of my first spin attempt turned the plane about 180 degrees with very little altitude loss.  I didn’t even have to climb for my second attempt, which resulted in a true full spin.

A true spin looks like this:

It looks like the plane is flying downward, but in reality the wings aren’t producing lift and you’re not really flying until you correct from the spin.  From inside the cockpit, this is what you see.  Notice how fast the rotations occur once everything falls into place.  It was very exciting!

Correction from a spin is not as hard as you would think:  1) pull the power (and carb heat) 2) neutralize the ailerons 3) kick the rudder in the opposite direction of the spin 4) push the yoke forward to get a bite of the air 5) pull out of the dive without stalling the plane again.  In reality I was surprised because the plane I was in (N46961) didn’t make me kick the rudder out much at all to correct the spin.  It was more like having to relax the bad input to get the spin to correct.  My CFI said I may have to correct more in other planes, but the process is still the same.

After about 10 spins, many of which I (purposefully) created and recovered from by myself, I was no longer as nervous about accidentally spinning the plane as I once was.  I am actually interested in doing aerobatics now, which is odd for a guy that used to be scared to fly at all!

On Wednesday I logged 0.9 Hobbs hours with 8 take offs and landings.  On Thursday I logged 1.1 Hobbs hours of spin training.

  • Twitter
  • Facebook
  • Delicious
  • Digg
  • Share/Bookmark