Tuesday, March 10. 2009
Flying in San Diego, CA
Ok, I know, I don't update this very often. But, it has actually been a long time since I've had a flying "Adventure." What with flying under the hood every few months to keep my instrument rating current, and all that jazz, I just don't fly that much any more.
Anyway, on Friday, March 6, 2009, my brother-in-law, who my wife (his sister) and I raised since he was 9, graduated from the Marine Corp basic training at the Marine Corps Recruit Depot - San Diego. We flew out to San Diego (commercially, of course) the prior Wednesday so that we could attend the Family Day activities Thursday morning.
I decided to rent an airplane and go do some sight seeing. Since I would be flying in some of the busiest and complex airspace in the country, I also decided to rent a CFI.
The process started about three weeks ago, when I put out a query to my local flight club asking for recommendation. It took less than a day before I received word recommending a particular fellow named Jean-Jacques Bellier who flew with the Armed Forces Aero Club. I made a few phone calls and arranged to meet Monsieur Bellier at Montgomery Field at 4:00pm Thursday.
When he arrived, he handed me the keys to a 172, a fuel cup, a dip tube gauge, and told me to do the preflight while he de-briefed the student that he had just flown with. I spent a little extra time doing the preflight since I wasn't as familiar with the history of that plane as all the others I flew; it took me about 15-20 minutes. I awaited his return in the left seat.
When he came back out, he told me that I would be unable to be the left-seater because of the AFAC's insurance requirements, and I could not act as PIC. So, he would be legally responsible for the flight and act as sole PIC. But he assured me that I would be handling the controls...from the right seat! That'd be a first for me. I've "Flown" from the right side, but never done any takeoffs or landings sitting on the wrong side. This would be a new experience.
We spent about 10 minutes talking about our route, which had special significance in order to avoid the SUA's surrounding Montgomery (MYF). So, I read him the checklist items, he started it up, pulled us out of the cramped parking spot, and turned control over to me once we were on the yellow line.
We started out at Gibb's Flying Service, listened to ATIS, got ground clearance (Mr. Bellier handled the radios for the entire flight since he knew all the magic words and numbers.), and we taxied to runway 28R, the largest of the three runways at MYF at 4577 feet. After doing a flawless run-up, we were cleared for takeoff on a westerly departure without any delay.
First order of business was to climb above Traffic Pattern Altitude, then point our nose westward to Mt. Solidad, and toward the coastline. The floor of SAN's Class B lies above at 4800 feet, and there's a segment of airspace north of Mt. Solidad where Mirimar Marnine Corps Air Station and SAN's Class B's overlap, with a slice of freedom between 3200 and 6800, so we needed to be above 3200 to enter it, and we were climbing to 4500 on a northwestly route. We flew a few miles offshore, following the coastline as far north as Carlsbad. We could see about 20 miles offshore the USS Nimitz doing flight ops before circling back toward the southeast, again along the coast. We entered the same slot of airspace, but this time followed an established VFR corridor further south, which brought us over the eastern end of SAN, near the North Island Naval Air Station, Coronado Island and the famed Hotel del Coronado, then southeast to Chula Vista and into the pattern at Brown, which is about a mile from the Mexico border and Tijuana.
At Brown, we did four Touch and Goes, then headed back out at 4500 to go through the corridor, back over the Bay (and again the USS Ronald Reagan in port), to head back to MYF. The routing and the way airspace works makes one have to lose about 3000 feet of altitude in just a few miles to avoid busting the Class B. That was a bit of a trick, but was easily accomplished by flying a long downwind after we had been cleared "Left Downwind for 28R." However, before turning base, we were told to land on 28L, which is the 2nd shortest runway at 3401 feet. Two feet shorter and it'd be the shortest...
28L has no PAPI or VASI, is short and narrow, so I came it a bit low and fast, but was able to correct without issue. We were back in our stall about 20 minutes before deep dark.
What a fun afternoon!!!
Saturday, September 22. 2007
Oh, what JOY!
I tell you what.
There is NOTHING more satisfying than to take your child for their very first flight, and to watch their eyes positively pop wide open when the wheels depart the ground.
Such as it was for me and my daughter tonight.
Lexie, who's only 3, adopted her daddy's love of aviation while I was studying for my instrument rating. She would curl up with me in my recliner and watch my Sporty's Instrument Pilot DVDs. She even knows her phonetic alphabet better than she does the regular one! Boy, won't that be a trip when she enters kindergarten and says "... X-Ray, Yankee, ZULU!"
At any rate, I had planned to go out tonight to get some Night Stop and Goes before TKI shuts down for the fall for surface rehabilitation (the runway will be closed for about 2 months, and the Texins fleet will be relocated to Sherman, TX, which is about an hour away from me.)
She looked at me with big brown eyes and said, "Daddy, I want to go flying, too!!!" I thought about it for a while, and decided that if one of her uncles (who are 12) would sit in the back with her, I could manage.
I half anticipated she'd freak out as we began to roll out, and was fully prepared to abort the takeoff. But when I glanced over my shoulder after rotating and stabilzed climb, and saw her nose pressed to the rear window, and a big grin reflecting with each strobe flash, I knew we were golden.
I did two stop and goes, then departed the pattern toward the city lights. She was bedazzled. I could hear her squealing "Look at that!!!" at just about every possible thing she saw. We flew around Plano and Murphy for about 10 minutes, then headed back in for our final full stop.
When I turned off on the taxiway, she asked, "Daddy, can we take off again??"
She's hooked. Just like her dad.
Tuesday, September 4. 2007
Nice Long IFR Cross Country
I started to title this one "First IFR Cross Country," but of course, it wouldn't be, since I did several during the training. But during those, I had an instructor aboard. And this one wasn't solo, because I had two of my kids with me. And, it's too long to call this entry "First IFR Cross Country as an Instrument Rated Pilot (But Not Solo.)" Nuf said?
At any rate, I once again decided to fly up to Branson, MO over this long weekend, and this ~300nm flight was to be filed IFR, even though the weather outbound was VMC.
I filed: ADS TEX9.MLC RZC HARKS PLK (Addison Airport to Taney County Regional via Texoma9 Departure, McAllister Transition, to Razorback VOR, to HARKS intersection, Direct) at 7000 feet. Had lots of vectoring out of the area (in fact, I never actually flew much of the departure route at all.) Before reaching MLC, I was given "Direct..." all the way to the destination airport. Ultimately, I was given a visual approach, with no vectors needed to find the airport.
We arrived about 30 minutes after sunset Friday Evening, making this my first nighttime arrival to PLK. And as expected, since this was a holiday weekend, the field was CROWDED. My dad arrived at the airport a while ahead of me to stake out a parking spot, one of only a handful remaining. Two other birds arrived right after me, and probably filled them up.
We spent Saturday and Sunday in the area (including a trip back to the airport to pay for fuel and tiedowns) and left early Monday Morning.
The trip out was quite different weatherwise than in. In fact, we were IMC due to poor visibility for the majority of the trip, including some clouds along the red river.
Coming into the DFW area, I came back to VMC when told to descend to 6,000. ATIS at ADS was reporting "Better than 5000, 5." The approach controller was giving me vectors.
He never told me to expect a certain approach. IE, never heard "Expect the ILS 15 approach at Addison," or, "Report field in site."
I DID receive, "Maintain best practical speed. Turn right heading 280 for the beginning of the ILS."
So, I'm flying merrily along on a heading of 280, 115kts IAS, altitude 2000, and hear "Turn left heading 180, maintain 2000 until established on the localizer, cleared ILS Runway 15 approach."
So, I start my turn. I'm maybe 1 mile outside the FAF, and the needle comes off the peg. Mind you, it's a 100 degree left turn for the vector, or a 130 degree turn for the inbound course, and the needle is moving fast. I'm also using a fully-coupled Autopilot, so of course, it overshoots the turn to 180 to try to re-intercept the localizer.
Then I hear:
"348ME, approach clearance canceled. Turn right heading 180."
"Right Turn, 180. Sorry, that turn was just too much too late."
"Oh, I could have sworn that a Cessna could turn faster than that..."
"I was on autopilot which uses standard rate turns. By the way, field in site. Request visual approach."
"Oh!! Okay, cleared visual approach runway 15. Contact tower on 126.0..."
I thought it very weird that they'd be vectoring me for the ILS when the visibility was VMC. I also found it surprising that they'd give me such a huge turn that close to the approach course...
Oh well... The flight was fun. Autopilots are AWESOME. ![]()
Wednesday, August 8. 2007
Flying a Glass Cockpit
I had the wonderful opportunity to fly a C172SP with Garmin G1000 avionics for the first time yesterday, with an outfit called Lone Star Flyers, out of Addison Airport (ADS).
I came across this business searching the web for something totally unrelated, and while exploring, saw that they rent their airplanes to outsiders as long as the pilots are appropriately rated, and have a checkout flight with one of their instructors.
Given that the cost to rent their planes is about the same as what I pay at TFC, and given that Lone Star's planes are MUCH newer and better equipped, I decided I'd go ahead and take a checkride with them, if nothing else but to have a Plan B in my pocket if TFC's planes were unavailable.
One of the planes on their rental list is N18563, which has a G1000 panel. For only $20/hr more than the standard SPs, I figured it'd be interesting to see how those avionics worked. Plus, getting checked out in the G1000 is automatically good for checkout in the NON-G1000 planes (but, of course, not vice versa.)
So, I arranged to meet with one of their instructors at 7:30PM to get checked out. Below are my impressions of the G1000.
We agreed that the flight should take plus under Simulated Instruments (what's the point of NOT doing that, if you expect to fly their equipment in IFR), with particular focus on using the Autopilot for the approaches, and the G1000 being just a "brief" highlight.
Before taking off, Torrey (the CFII) programmed the Integral GPS with DIRECT HQZ, and observed that the course line went through a corner of the floor of the DFW Class B. We took off at 8:45ish, and headed EAST, hand flying to the north of the DIRECT route to avoid Class B corner.
The G1000 made this a peice of cake. Since it knew our altitude, and given it was set to only showed the sectors of Class B that were active at our altitude, there was little involved in the navigation. The MFD also had our heading shown using a typical HSI presentation, but also showed a nice little green dotted arrow pointing WELL off the left side of the nose, indicating our actual TRACK. Of course, the wind was so strong (30kts) there was little doubt visually what the wind was doing, but up in the right hand corner of the screen, the actual winds were displayed! Ordinarily, one would have to use the whiz-wheel or the GPS computer applications to calculate the winds aloft. The G1000 does this in real time.
After a while, we were on our way direct to PQF (the NDB that represents the Initial and Final Approach Fixes for the ILS Runway 17 approach.) All I had to do was keep the green arrow superimposed on the purple DIRECT COURSE line, and crosswinds were automatically compensated. When we overflew the NDB, we turned outbound for the procedure turn, as the ILS Localizer display had become active.
Frequency selection was also a peice of cake. I never mastered all the shortcut steps, but Torrey demonstrated that it took about 5 clicks and a few twirls of knobs to preload the frequencies for the CTAF and ILS into the standby frequency windows, and I then simply toggled them into the active. All I had left to do was confirm against the approach plates that the frequencies were correct (the G1000 even decodes the IDENT for you by displaying the letters IHQZ next to the frequency!)
Once turning inbound on the procedure turn, Torrey showed me how to engage the Approach Mode of the autopilot (Altitude-> ARM. Heading Mode->ACTIVATE. Approach Mode->ARM) then took my hands and feet off the controls.
On intercepting the localizer, the plane gently banked into the approach course and absolutely NAILED the intercept. We flew for about 4 or 5 more minutes until the Glideslope Bug came active, dropped down the rail, and BLINK, the AP announciated APPROACH, the trim wheel whirred to intercept the glideslope, and all I had to do was pull the throttle back to about 1900 RPM to avoid rocketing down the approach.
The "needles," (or bugs) never left center by more than a half dot at the most. It was an impressively accurate descent, especially considering the roiling air going through a sheer boundary (30kts aloft, 10G15 on the ground). When reaching DA, I looked up to see we were right down the centerline. I was told to disconnect the AP and fly the rest of the way down by hand.
If we had executed a MISSED, I could have set the GPS and Autopilot to fly the entire missed approach procedure, including the hold. Now, of course, the Autopilot needs guidance, so it's not going to execute the missed unaided. The PILOT must execute the missed, load the altitude and heading for the initial segments to get to the safe turning altitude, before engaging the GPS tracking, but it's still quite a burden saver.
On the way down, we got a TRAFFIC ALERT from the TCAS. Another pilot was in the vicinity, and we allowed ourselves to get a bit close. Nothing dangerous, mind you, but the TCAS function the G1000 was always watching and squawked "TRAFFIC. TRAFFIC." into the intercom. Looking at the map, we could see where to look.
After a touch and go, we headed further out of town and did some basic airwork (as part of the checkout regime) including Slow Flight, Stalls, emergency procs, etc. etc, then headed back into Addison.
Calling approach, we asked for vectors for the ILS. All I had to do was twist a few knobs as new vectors were assigned, and in short order, we were once again attached to the localizer and glideslope all the way to the runway, disconnecting the AP when we were about 75 feet above the deck.
So, impressions flying IFR: Piece of cake. The information you get from the "Six Pack" are all there, and in a much more condensed area of space. This makes scanning a dream, with less fatigue since ones eyes don't have to cover so much real-estate. The instruments, being INSTANT reacting, can be a bit dodgy. I found myself fighting the airspeed tape early on because the gusts were obvious. All the other basics were intuitive.
The NAVIGATION was slightly more complex than just looking at two CDIs and a pair of needles, but not much more so. I couldn't figure out if it was possible to view BOTH CDIs simultaneously, or just one.
All in all, it was awesome. I can't wait to get more time in this plane.
Saturday, August 4. 2007
What Fun!
It isn't every day that one gets to introduce youngsters to aviation, and today I had the opportunity to take my two nieces, ages of 8 and 12, along with their father (my brother-in-law) up on a quick out-and-back.
We took off from McKinney around 11:15AM or so, and flew northwest to Celina (so I could see if the man I pay to mow my property is actually doing it!), then south to Prosper Texas, over Deion Sanders' estate, then out to Lake Lavon, and back. All told, we were airborne for a little over a half hour, which was apparently just the perfect duration, considering the light turbulence.
I think both gals had a good time; hopefully it's a memory that will stick with them for a good long while!
Friday, July 20. 2007
Got my Class III Medical renewed yesterday....
Looks like I'm good for another year!
You folks without waivers have no idea how good ya have it... ![]()
Saturday, June 30. 2007
My first solo IFR flight in IMC
A year! Wow. So, what have I been doing in that time? Well, if you've been reading the flight log, you'll know that I've been working on my instrument rating, had a child, broke my arms, and all kinds of other distracting things. But, no longer!
I earned my instrument ticket in June, and today was my first SOLO IFR flight in Actual Instrument Conditions (IMC).
The weather was perfect for the trek; a relatively low overcast (around 1100 to 2000 feet AGL) and no thunderstorms yet, so I booked a two hour block of time in 3NB, filed a Round Robin Flightplan between McKinney and Mesquite Metro.
The only weird aspect of this flight, I guess, was when the McKinney controller said, "733NB cleared to McKinney as filed. Fly runway heading, climb and maintain 2000..." Of course, I had filed for DESTINATION of TKI, but it's still weird hearing them clear you to where you're presently sitting...
So, I took off. 2000 wasn't good enough to get into the clouds, so I asked for higher and was given 3000. Into the clouds I went, and was handed off to the next controller. I intercepted the localizer fairly quickly (about 20 miles away) and, enjoying the LACK of view, was disappointed when I was cleared for the approach so soon, which implied that I needed to descend to the appropriate altitude to begin the approach. The next 15 minutes or so were all VMC, so the arrival wasn't very interesting...
I did a touch and go at Mesquite, called the approach controller back, and was given 3000 back to McKinney. To get a little more experience, I requested the FULL ILS at McKinney (which would include an outbound course, a time procedure turn, etc.) and was told it'd be doubtful given the amount of IFR arrivals at TKI that would conflict.
During the rest of the flight, the controller spent what seemed like 10 minutes trying to call an unresponsive airplane. Ultimately, he called ME and asked ME if I could call him. I tried, no success. I told the controller if he gave me relative positions, I'd keep my eyes out for him, in case there were problems. At this point, I started my approach at TKI, and the guy finally called the controller and anounced he'd lost his radios and was now on his handheld.
About 1/3 of the approach to TKI was made IMC, and the clouds broke around 1800, but the visibility was poor enough that the airport wasn't visible until about 5 miles away.
What a cool day!
Thursday, June 14. 2007
The Checkride
Whoo-hoo!
It's DONE!
It really was touch and go, with bad weather in the offing. There were some significant storms developing west of us, but they weren't moving very quickly, but all the same, I was anxious as to whether or not the flight would be scrubbed (similar to my Private checkride.) But no, the weather stayed distant until shortly AFTER my ride! Can't ask for more than that!
So, this is how it went.
I had to meet the examiner, "Smitty," at 10:00ish at Addison Airport. So, I left early (around 8:30) to take a chance that we could start early.
Alas, THAT wasn't to be, as I met up with Smitty promptly at 10:00. I think he spent the first 15-20 minutes just telling interesting stories and lessons while he was reviewing my paperwork and applications. I guess I didn't realize that the verbal portion of the test had already begun until I noticed he had asked three different regulatory questions about my currency, experience, etc.
He asked questions about instrumentation, spending a lot of time on the static system. One question I remember was "Pretend you don't have an alternate static source, and that you didn't do a good preflight, and left your main static port nonfunctional. And you take off. What do you expect to go wrong, what will you see that tells you there's a problem, and then what do you do?"
I answered that airspeed won't indicate properly after taking off, but it will during rollout. VSI will stay at or near 0. Altimeter will stay at or near field elevation. Declare an emergency, circle and land.
"Ok, but what if you're in the clouds already. What do you?"
[ guessed at breaking the VSI glass. He said it was right. Then he told me a joke about a Navy pilot-in-training who did exactly that, and was washed out of flight school despite the fact that that procedure was in the emergency checklist. Why? Because he was in VFR conditions when it happened. Can't believe that's true, but seems like he's been around long enough to know!
He showed me some weather maps and asked me to describe what I saw (Highs, lows, fronts, radar returns, etc.)
He then reviewed my assigned Cross Country Flight Plan from Houston's Hobby airport (HOU) to McKinney (TKI).
I had used the Preferred Route as published in the A/FD (V477 CQY) to get the route of HOU IAH V477 CQY.DUMPY2, NO SIDS (because the only applicable SID had an MEA of FL180) at 8,000 feet, 2 hours 40 minutes, no alternate since weather indicated VFR, etc.
"Pretend that it's February, and your forecast said there was a cold front north of the area, heading south, but that it's not expected to be in the destination until three hours after your ETA. Current METARs are fairly benign, 1000 foot overcasts, temperatures in the high single digits. So, you launch.
"What do you do if that cold front beats you to your destination, you start accumulating ice due to freezing rain, and your destination ATIS now reports moderate freezing rain?"
You turn around! Descending won't help if the rain is freezing at the surface. Climbing won't help because you'll not be able to land.
Similar questions about vacuum failure and electrical failures followed. All of these were dotted with stories about real occurrences. He also stressed quite hard the fact that you have to IDENTIFY radio stations, and DOUBLE CHECK radials and all that stuff, showing magazine articles and NTSB reports of crashes that were the result of said mistakes.
All of this took about an hour and a half.
Then it was time for flying.
He gave me a rundown on what to expect, but didn't give any details just yet. He mentioned we'd head out on a VOR radial to an intersection of his choosing and hold, followed by this and that. I told him that during my flight planning, I saw a NOTAM that indicated CVE VOR/DME out of service effective from June 14th, 2007 at 08:00 AM CDT - June 14th, 2007 at 03:00 PM CDT. His response: "Oh my. Well. I have to figure out plan B then." So he buried his head in a JeppChart for a few minutes, and told me we'd use Maverick instead. He was amazed I'd caught that NOTAM.
So, we headed out to the plane. He told me to "abbreviate" my preflight as much as I was comfortable with, to try to beat the weather which wasn't looking too good. I didn't. I did the whole thing! We climbed in, and I got my "Clearance,":
N733NB Cleared to TKI via on departure, left turn heading 090 to intercept the Maverick 074 radial to TRISS intersection, Direct Bonham VOR, Direct McKinney..."
So we took off (I forgot the ATIS, but he gently reminded me before we taxied) and I went into the "clouds" pretty quick. I turned 090, and then he started giving me vectors which quite quickly showed we'd never get to the radial before getting to TRISS, so he had me pick a course to intercept. We got to the radial about 8 miles from TRISS, and I turned to follow it.
Then he had me "Hold Southwest on the Maverick 074 radial 27 DME. Expect further at [10 minutes later]."
I got my chart, and charted the hold. He said, "No need to look there, it's not on the chart." I said, "It is now!" he just laughed.
When we got to the fix, I turned outbound and started my timer. While turning inbound, I had a simulated vacuum system failure. Called "Departure," "733NB Declaring an emergency due to vacuum failure, no gyros." "733NB, turn left heading 360, expect VOR/DME A approach at McKinney, you will be number one when you arrive. Maintain 2500"
He asked me to make the turn using just the compass (I had to, since I was already in a turn at the time) and asked what heading I would be looking for to roll out. [30 degrees].
He gave me a few vectors and asked for a TIMED turn on the first one, then Pilot's Choice for anything else. So I set up for the VOR approach and SUPER double checked everything OUT LOUD. The VOR/DME-A approach was done partial panel with no problems, did a touch-and-go on 17, and I got my instruments back.
Next I was told to expect vectors for the GPS-17 approach. I started programming the GPS and was entirely freaked out by the fact that it would let me select DIRECT TKI, but when going to Airport Page 8 to select the approach, all the listed approaches were ADDISON! I tried three times. I think he noticed me struggling, because he kept giving me other things to do in the interim.
Ultimately I had to say "Smitty, this ain't gonna work. I can't seem to get the GPS to let me pick the right approach."
I really thought he'd send us back to Addison and end the ride at that point, but he said, "OK, fine, we'll do the ILS here and try the GPS at Addison."
So he vectored me for the ILS and told me, "don't even look up. Go missed at DA and do it exactly as published." I so advised the tower, and in we went. At 800 feet, he said GO MISSED, so I climbed out to 1500 on the localizer, then climbed and turned to FLUET via the ADF on up to 2400. Smitty called the tower and said something about halfway to Fluet, and tower responded "Ok, Smitty, I know what you're up to. No observed traffic, proceed at your discretion."
Huh?? Now I was worried something weird was about to happen... See, Smitty has been around a long time. It seems like EVERY controller knew him by voice, and must have also known what he was planning.
So, before we got to FLUET, he had me turn on rough course to Addison and asked to take the controls while I was to copy down the ATIS. As I was writing down the ATIS info, he said, "YOUR AIRPLANE!!" When I looked up, we were in a dive, and a steep left turn. What a surprise! I was NOT expecting that, but that "unusual attitude" recovery went well.
Then he told me to set up for the GPS approach, while he took the controls and contacted ATC. Out of the corner of my eye I could see he was covering the instruments again, so I was expecting the next unusual attitude, this time a hard climbing turn. We were at 40 knots when he told me to recover.
He explained that the reason he does those that way is because it's usually distractions that get people into trouble and necessitate an unusual attitude recovery. Good lesson.
I finished programming the GPS. Thankfully it fully complied this time. Approach gave us "Own Nav to Addison." Smitty thought that rather odd, but didn't argue. He just gave me vectors instead.
The GPS approach went well (it's actually less complex than McKinney's.) He told me to expect to transfer controls to him on reaching 1100 feet, and BEFORE the MAP, and that he would land the plane. So, on leveling out, we did just that. He said he HATES the GPS approach for Addison because it annoys the neighbors. After all, at 1100, you're only a few hundred feet above rooftops! He actually climbed back up to Pattern Altitude (1700 feet) and did a normal landing from there.
I taxied in, shut down, and it was done!
Of course, even though it's only a 20 mile flight, I HAD to file IFR back to McKinney. Why? WHY NOT!
So, to wrap it up, going in to my check ride, my experience had totaled:
- 255 Day Landings
- 49 Night Landings
- 67 Instrument Approaches
- 156 hours ASEL
- 4.5 hours in a Flight Training Device
- 18.1 Hours Night Flying
- 1.6 Hours ACTUAL Instruments
- 49.2 Hours SIMULATED Instruments
- 91.4 Hours Training Time
- 48.8 Hours Solo
- 119.7 Hours PIC
- 56.7 Hours Cross Country
- 32.9 Hours SOLO Cross Country
- 51.0 PIC Cross Country
- 13.9 Hours Night PIC
- 19.0 Hours IFR-Filed Time (Not Necessarily IMC)
So, what's next?
THE COMMERCIAL rating, OF COURSE!
Not yet written...
I haven't yet "officially" started this training, as right now, it's all about acquiring the minimum experience required, which includes:
| At least 250 hours of flight time as a pilot | Need 87 more |
| 100 hours in powered aircraft, of which 50 hours must be in airplanes. | Complete! |
| 100 hours of pilot-in-command flight time | Complete! |
| 50 Hours ASE or AME PIC | Complete! |
| 50 Hours Cross Country (10 hours ASE or AME) PIC | Complete! |
| 10 Hours Instrument Training (5 in ASE) | Complete! |
| 10 Hours COMPLEX Aircraft Training | (Not Started) |
| One Cross Country > 2 Hours Day VFR > 100 nm straight-line distance | Complete! |
| One Cross Country > 2 Hours Night VFR > 100 nm | Incomplete. |
| One SOLO Cross Country > 300 nm total, landings at 3 different points, one leg > 250nm | Incomplete. |
| 5 hours Night VFR, with 10 Takeoffs/Landings at an airport with an operating tower | Complete! |
So, as you can tell, asside from just the total hours, the main things to accomplish are:
10 Hours in COMPLEX Aircraft (this would also yield the Complex ASEL Endorsement)
A Night VFR Flight of 2 hours and 100 nm away from the point of departure (shouldn't be too difficult.)
One LOOOONG SOLO Cross Country (I've ALMOST completed that several times!
But that last long-haul solo I took was only 208 nm distance to the longest
leg.) The one time I did fly that long of a leg, was TKI-HRO-MLC-TKI
(TKI-HRO=250.8nm!), but it wasn't SOLO since I had my kids with me. ![]()
Tuesday, June 12. 2007
That's That! (Final Lesson)
Well, that was that!
Tonight was my (I HOPE!) Final instruction ride for the Instrument Rating.
We went out to practice some more steep turns, unusual attitudes, holds, compass turns, timed turns, and all the other things that have given me fits for the last year.
Amazingly, all went pretty well!
My checkride is scheduled for Thursday morning. I can't wait.
As I write this, my coffee table is strewn with all the preparatory materials for the exam (flight plans, logs, charts, books, etc. etc)
I can't wait to put this behind me. It's been almost a year to the day that I started this. What I hoped would only take four to six months turned into a year. Eeek. I hope not a day longer!!!
Friday, June 8. 2007
Spit and Polish
My checkride is scheduled for next Thursday! (That's June 14, if you're keeping score.)
So, I wanted to go out an do some "Spit and polish" work. We flew to Addison, this time stopping to see where the Designated Examiner's office was. On the way out, we did some steep turns, unusual attitudes, partial panel unusual attitudes, timed and compass turns (I really need to practice this!!), and did a VOR approach with a circle to land.
Aside from the fact that the DME is screwed up, I thing everything is ready to go!
One more practice flight on Tuesday evening, and then .....
Thursday, June 7. 2007
Phase Check
Tonight I had a "Phase Check," with our chief flight instructor, Richard. I also wanted to learn the most efficient way to use the GPS to make approaches, and Richard is quite an expert at using the KLN-89b. We did several GPS approaches, some partial panel work, and finished off the evening with an ILS approach.
All went pretty well, considering that the winds were horrible and the air was roiled with turbulence. In fact, heading north, I broke my ground-speed record with just shy of 150 kts on the GPS (about a 50 kt tailwind.)
So now it's official. He says I'm ready for my FAA Check ride!
Tuesday, June 5. 2007
ANOTHER Hiatus!
UGH UGH UGH!!! Another long break. This time, my eldest daughter had a case of bronchopneumonia which had her hospitalized for over a week.
So, a little more brush up and practice was on the menu for tonight.
We flew to Addison to make an ILS approach there, and on the way out did some partial panel work, and did some holding.
Back at McKinney, we did a few more GPS approaches and called it a day.
Friday, May 18. 2007
More GPS
The goal for tonight was to get more knowledge of the GPS installed in 3NB, and to practice a few GPS approaches. We were able to get three GPS approaches in, and practiced the missed approach for each set us up for the approach in the other direction, so somewhat efficient practice.
We spent a little over an hour and a half at this.

