Saturday, June 30, 2007

There's got to be a morning after...

Updated: Added pictures.

We scoped things out this morning, and it is just so sad to see 388 helpless on its back.



The wings are a little rumpled, the empennage is not quite straight or solid, ...




Kevin, the mechanic, was out this morning and he figures the insurance adjustor will total it, saying the wings will have to be wholly replaced and that fixing the empennage is a labor-intensive (read: expensive) job. Who knows about water and other damage to the avionics or interior in general. And we just did the annual a week ago! It's a 1968 172 with a current estimated value of $30-34k, so it probably won't take a whole lot of estimated repairs to get to that amount.



John, an instructor who lives to fly and just a super guy, had his tail-dragger parked down a few spaces. His was upside-down also. Kevin explained to us that it didn't flip tail-over-head like ours did, but flipped wing-over-wing, over a neighboring plane, taking out one plane's tail and damaging another to come to its resting point. After snapping the tie-downs. Rumpled wings, shattered windscreen, twisted empennage, ...




(John's plane is the white and blue one on the far right. It had been parked on the other side of the orange 172. The orange plane and the gray-and-yellow one facing the hangars had their tails clipped by it. The plane on the left has some holes in its skin. The plane in the foreground is in much the same condition as ours; this guy restored the interior himself a few years ago, replacing seats, doing the leather upholstery and interior panel coverings himself. So sad.)

Charlie, one of the linemen, said that non-owners were being turned away from the airport today, and that at one point there were ~75 cars stacked up of people coming to gawk. Kevin said there was one resident plane out on the ramp not damaged (out of probably 20); it just so happens to be the one plane that has never, ever moved the entire time we've been associated with the airport. Perhaps it's fused to the pavement.

All of the flight school's single-engine planes were damaged; luckily their twin so far appears to be ok. The handful of planes in the transient parking on the other side of the terminal also seem to have survived.

Friday, June 29, 2007

No words

There's just nothing to be said.



We'd had some storms tonight, and we got a call a little before 10 pm saying our plane had taken some damage. Yeah, I'll say. We'll go back in the morning to see what's to be seen or done. What we could tell in the dark is that the we have a destroyed tail tip, bent propeller, bent wing strut, damaged leading edge of one wing, fuel leaking (around fuel cap, so probably just coming out the vent), various antennae damaged or broken off, left-side door hinge ripped off... Oh, and the interior is soaking wet with 1/2 inch of water pooling at the "top" of the windscreen. And also the tie-downs were still connected to the plane.

As we drove off, the rain began to fall harder, thicker, and with hail.

AWOS appears to have stopped reporting a few hours ago. I guess it took some damage, too. They say four planes are upside-down (we saw two others near us, all high-wings), and several came loose and collided with neighboring planes.

A sad day at JGG.

Thursday, June 21, 2007

New solo pilot

If you have a sec today, stop on by flyaway's training blog to congratulate him on his first solo flight early this morning! He's back on track after having lost his instructor to the airlines, and he's training in the ADIZ, which to a country flier like me sounds like a nightmare! :)

Good job!

Tuesday, June 05, 2007

Gut feelings and random thoughts

My feelings on flying are changing as my gut changes, I'm sorry to say...

I'm ~3/4 of the way through the pregnancy, and certain activities are becoming uncomfortable. Like bending to pick something up from the floor. Like sleeping. Like sitting.

Like spending hours upon hours in airport seats or airline seats.

Our 9-day trip to the Canadian Rockies was really a good trip. We hit Calgary, Banff, Lake Louise, Jasper, Edmonton, and points in-between. I'd have to say that Banff was my favorite; a gorgeous little mountain town in a valley on a river surrounded by lush green mountains capped with snow, a town that's big enough to have interesting eating options but small enough to not be overrun with tourist-y shops. (It does have its share...) I'd really like to go back there when I get my body back so's to take advantage of the vast scope of outdoor opportunities -- hiking, rafting, biking, horseback riding, etc.

But spending 8+ hours in planes plus another 3+ hours in airports (thank you, weather delays) -- one way -- had my back screaming for mercy, and resulted in this policy: no travel longer than ~2 hours after the second trimester!

Beyond that, however, are the physiology management concerns, and this applied also to our flight in the 172 down to Asheville a few weekends ago. Amniotic fluid is pretty important for the developing baby (understatement), and it's cumulative; the recommendation is to drink at least 8 glasses of water per day (in addition to whatever other fluids like coffee or juice might be part of the daily regimen), plus another glass for each 15 minutes of exercise, plus 4 additional glasses on hot days with outdoor activity. That's a lot of intake, and it creates a lot of output, and with a shrinking bladder capacity, frequent breaks are necessary.

I'm not typically a germophobe, but airliner bathrooms really gross me out, as they do most everyone I know. The 6-year-old boy in 15b surely doesn't have the best aim to begin with, so throw in a little turbulence and you've got a situation that's less than ideal for any subsequent passenger. Ick and shudder.

And in a 172, that's an expensive potty break.

So you see where I'm going here. Just bitching about the growing discomforts of flying whilst preggers. I'd guess that it's just as bad for driving nowadays, too, but haven't tested it. Discomforts of traveling.

On another note, United gets mixed reviews from this trip. Our layover was at Chicago O'Hare, and the landings there both on the trip out and coming back were really soft and smooth, so pats on the back for those pilots. On the ORD-YYC leg, they announced that ATC would be tuned in on channel 9 in the armrest audio. That was fun, listening to the busy stuff going on at ORD and the calls in transit. (Note to self: what is "metering?" Some kind of departure load-balancing service?) Sometime at cruise altitude, the captain came on and advised us that he'd be "giving a dissertation" if anyone wanted to listen in on channel 9. He was amusing and talked for probably 20 minutes or so about the FO's experience, his experience, the history of the Boeing 737 (such as we were on), fuel ferrying and consumption/performance trade-offs in a time of high prices, etc. He was pretty cool and sounded very friendly.

Other United issues, though, were unusual and unpolished to me. For instance, during the pre-taxi safety instructions, it appears to be United policy to turn the cabin speakers down way low and to select the crew member with the worst diction and recitation skills to do the announcement. The phrasing of the announcements was bad, too; they seem to have accepted the first draft. The one that seemed very odd to me was the prepare-for-landing announcement: stow carry-ons, tray tables and seat backs in their full upright and locked position, seat belts fastened, and "in the case of an emergency after landing, leave all carry-ons behind"... They had already emphasized that in the case of any emergency all carry-ons should be left behind, so why repeat it for landings? Do they have a history of landing problems? Are they just trying to give the aviophobes a little nudge in the last-minute freak-out direction?

Ok, enough blathering for now, back to work! I'll post a few pics from the trip soon, and promise to be more positive! End communication.

Friday, May 11, 2007

Sleek, but suspicious

I found one of these in the garage this morning. At least, I think it's one of these.

I was pulling out of the garage and saw it peeking its head out. I put the Jeep in park and bounded out to get a closer look -- snakes don't bother me in the least, and this guy looked pretty big and cool. But as I got closer, this new risk-minimizing reflex kicked in: Being preggers, how close is safe to a snake if I don't know whether its venomous? That was kind of a strange wall to hit.

Well, shoot, at least I had the camera in the car. I'll post one of my pictures later, but here's what the guy looks like. I'd estimate that it was between three and four feet long, but it's pretty hard to tell when you can't grab him and stretch him out! Husband thought from the pic I showed him on the camera that he was at least four feet. (Image from the Virginia Department of Game & Inland Fisheries.)

We have lots of lizards around the house, and occasionally they'll hang out in the garage. We've had the good fortune to find nests of baby snakes in the backyard when mulching, and just transplant them farther back in the woods off the back of the property. This is the first time I've seen a snake in the garage. And with a snake this big, I worry about the bunnies living under the porch, adjacent to the garage!

Thursday, May 10, 2007

Ah ha ha ha

One of the non-aviation blogs I really enjoy is Scott Adams' Dilbert Blog. His daily posts are always entertaining, even the political ones or the ones that fundamentally are just stupid.

I'd guess that by using today's post as a metric, we're uncool and all awesomeness must be questioned.

Thursday, May 03, 2007

It's crummy anyway...

We've been cursed/blessed with some stunningly gorgeous days here recently, and yet Husband and I haven't gotten up to fly. Now, we can't even get off the ground if we wanted to!


Her Royal Majesty and the President of the United States are gracing our lil' ol' town for the 400th anniversary celebration at Jamestown this weekend and next weekend. That gray circle around JGG -- our homebase -- is a TFR that lasts through tomorrow sometime and that covers pretty much all of Williamsburg (Colonial and contemporary), and the one just southwest of the airport is right over Jamestown Island. Overflying the island is standard procedure for entering right traffic for 13 down here, and frequently for left 31 traffic as well.

Luckily the weather is really crummy today (even if it does still qualify as VFR), so it's easy to not be mad about not being allowed to fly.

Saturday, April 28, 2007

The Good, The Bad, and The (Plane) Weird

The Good
In my brief time as a pilot, student and otherwise, I've had one flight that really comes to mind as "ideal." It could also be that whole temporal relevance thing -- It was one week ago today! [Read about it in more detail and see pictures here.]

It was a really great flight. The air was mostly smooth, the visibility was good, I had a good landing at a new airport, and everything went right. An easy, fun, peaceful VFR day flight.

The reason for the flight was ideal, too. To celebrate Husband's birthday, we were taking a day trip to a new destination for our first real $100 hamburger run. Good food, good flight conditions, good company, .... Could it get any better?


The Bad
So what's the opposite of that good day? Oh, dear, hands down -- the solo. I don't even want to rehash it to summarize.


The (Plane) Weird
I don't have much first-hand experience with weird things yet, so here are a few flying-related oddball items out there in internetland:
Old airplane designs
Strange aircraft designs, I'm especially confused by the Blohm und Voss BV 141.
Brave helicopter pilot
Airplane coffin

Thursday, April 26, 2007

Well, that explains it...

The Leesburg FSS had some problems last weekend.

When we went up the DelMarVa peninsula for Husband's birthday trip on Saturday, I had used the AOPA RTFP to file a VFR flight plan. At 10:14 am ET I called Leesburg Radio from ~2000' 2 nm north of JGG and opened the flight plan. When we got to GED, I called 1-800-WX-BRIEF to close it, and was on hold for 8 1/2 minutes.

It was the first time I had ever waited more than 2 rings for an answer. When that answer came, it was an automated (Lockheed) system instead of a person, also a first. Then the long hold time as I was assured that my call was important to them and that they were experiencing higher than usual call volume.

And I just figured the skies were crowded on such a gorgeous day!

Saturday, April 21, 2007

Birthday Jaunt

We just got back from Husband's birthday day trip (his birthday is later in the week, but today was irresistible) up to KGED (Georgetown, DE). It was a really nice trip! He did 3 hours of sight-seeing, and I got 3 hours of flight time.

We left JGG by 31 around 10 am, turned west for the noise abatement. I called Leesburg Radio and opened our VFR flight plan, then headed northeast for Mobjack Bay and the narrowest passage across the lower Chesapeake Bay. We got to our target bay-crossing altitude of 7500' a few minutes before running out of land, and up there it was a little chilly even though on the ground it was already in the upper 60s. The air was nice and smooth, and the bay was already thoroughly dotted with boats.

It was a gorgeous, nearly cloudless day with good but not "severe clear" visibility. Once we crossed the bay, I took us down to our cruise altitude of 5500' and pointed us NNE. We'd be overflying Accomack County (MFV, I think), traffic for which is frequently heard all the way down at JGG. We flew along the eastern seashore, Chincoteague and Assateague. We flew just west of Wallops Island, a military field (maybe AF?), and could see the buildings of Ocean City, MD, off at the very edge of the Atlantic Ocean.

It was a super trip, the kind of really good and easy trip that perfectly exemplifies why I learned to fly. Husband is putting up some video he took en route and also of my landing at GED (below). When we landed and were directed to transient parking, three ground crew members came out to help us push back and with chocks, and within moments the fuel truck was there to top us off; great service here.


Landing here for me was pretty neat. It's the first time since finishing training that I've gone to an unfamiliar airport, or gone on an unfamiliar cross-country flight (as PIC). I did the usual preflight prep, checking weather, using RTFP for course plotting and filing the flight plan, checking for TFRs, etc. I had picked out several airports along the way and printed out their kneeboard pages from the AOPA database, including GED's, of course. But actually going to that airport with so little research was neat. The only other time I've really gone to "new" airports was during training, and as a student I was anal (who, me?!?!?!!!) about knowing every available detail about the airport and surrounding area so there would be no surprises. I knew I had everything I needed for the destination, we'd have two GPSs and the sectional, so we were good to go without having to spend two hours planning and analyzing the trip! Approaching the airport, Husband helped me plan our descent from 5500' to pattern altitude of 1050', I executed that and got into the traffic flow with ease. Training apparently worked as it was supposed to have worked, because there were none of the comfortable visual cues of homebase, just the runway to use as a guide for the pattern and everything went just right.

Sussex County Airport (GED) has a nice little restaurant called the Flight Deck. They've got a good-looking menu, and we were both delightfully satisfied with our meals; a ($100) cheeseburger and onion rings for Husband, and broiled flounder with coleslaw and sweet potato casserole for me.

After a nice lunch, we paid for our fuel and headed out to the Delaware Aviation Museum, which is right there on the grounds. Out in the grass between the taxiway and the runway they have a collection of deteriorating Migs. I thought the noses had a neat design.

We then went through the museum, guided by a nice lady name Charlie. It's not a big place, but there are lots of neat artifacts. Apparently, all of the stuff there was collected by Larry, a B-24 (or 25?) pilot who lives in the area. Here are two of the exhibits in there. On the right, those are recon cameras; thank goodness for the tiny digital technologies we have nowadays!

Just before finishing up with the tour, the medevac helicopter pilot who was on waiting duty came in and said a Corsair was in the pattern. We went out to see it land, and it was followed by a P-40. Those things are huge! The wing design of the Corsair is really neat, too.

Departing the airport was easy. We had come in on 22 and departed 4. We turned out to the west, dodged some restricted airspace, stayed well east and south of the DC ADIZ, and picked our way back home. The air was a lot choppier as we came home, and I abandoned our 4500' first choice for cruise and went up to 6500' where it was generally much smoother. I had some of that weird unsettling feeling in the turbulence, which was nothing as far as turbulence goes, but stuck it out (I just annoyed husband with some of the whining...); luckily most of the return trip was smooth! Just some thermals as we move into warm weather...

We landed back at JGG, safe and sound, on 31 around 4 pm. We swapped places so Husband could get a trip around the pattern in before we shut down for the day.

What a nice day! :)


I'm up to 67.1 total hours now. And both takeoffs and both landings were one-handed.

Friday, April 20, 2007

Day trip

Tomorrow we're planning a trip up to KGED for two $100 hamburgers and a visit to the Delaware Aviation Museum, and maybe a nice walk into town. Looks like it should be a beautiful east-coast day for a flight up the DelMarVa peninsula!

In the completely unrelated category of fun with babies in utero, here's a baby-kick indicator on my burgeoning belly.... No fat jokes, please -- I can still see my toes.

Tuesday, April 10, 2007

Refresher flight

Goals:
  • Brief, fun local flight.
  • Takeoff and landing practice.

Flight:
Husband sauntered into my office this afternoon around quarter after five, sat down, looked out the window and said, "Man, looks like a nice day for flying." I've been married to him long enough to know what that means! Ten minutes later we were on our way home to pick up the flight bag and camera.

The plan for the evening would be for me to knock the dust off. It had been a little over three weeks since I flew, and the last flight wasn't good. We were coming back from down South for a family visit, and I had taken off and was going to fly for the first leg. We weren't 500' AGL when some turbulence started kicking us around, and while I've flown in enough chop for it to not be unsettling (hello, checkride?), I was borderline panic-stricken! I could not explain it, but almost immediately I had to pass control over to Husband. It was a terrible feeling then, and really shook my confidence that I would react so strongly, so quickly to conditions that really weren't that bad. I've thought about it so much, and honestly can't come up with anything better than "hormones" as an explanation. Had I been alone, I would have stayed in the pattern, landed and deplaned. (And no, I didn't blog about it; I haven't been able to make sense of it.)

I'll just tell you the ending for this evening's flight first -- it was a good, easy flight with no strange feelings and mostly decent work.

As we rode to the airport, I couldn't help but be apprehensive. The memory of the terrible and inexplicable feelings from a few weeks prior mixed with the knowledge that I haven't had any real practice in about a month left me feeling, well, just apprehensive. I didn't say anything to Husband because my intention was for it to be a good flight and I knew he'd be able to take over at any time should we have a repeat.

Blah, blah, blah... My feelings this, my feelings that. Rant on myself. Ok, stream of consciousness over.

Preflight was good. Husband snapped a few pics of the shiny new 4-hour-old tach. We decided to go to PHF (towered) for two stop-and-go landings. Husband showed me his new leaning technique (throttle to 1500, lean until it starts to drop, enrichen to stabilize it -- this left the mixture rod out about the length of my pointer finger up to the second knuckle). We taxied out to 13 and departed with a nice normal takeoff and a climb just to the west of the power station.

Once we were clear of the power station and at 2600' MSL (clear of Fort Eustis' airspace), we pointed toward PHF. I called them when we were over the dead fleet to let them know where we were and that we had info Quebec. He told me to report a 2-mile left base for 7. I had a bit of confusion making out the airport. I know PHF, but I've never used 7-25, had never approached from this angle, and it was hazy enough that I couldn't quite pick out the V-shaped runways from where we were, so I was a little off-kilter not being able to immediately visualize the approach plan.

Once we passed Fort Eustis and officially entered PHF's airspace, I began my descent, pulling power out for a fairly aggressive sink rate (5 nm from the airport (center) with 2600' to lose). As I turned onto base I called the tower, who cleared me for #2 behind a Cessna on final doing a touch-and-go, then instructed me to make right traffic for the second landing and report midfield downwind. I repeated the clearance, kept the descent, and grinned a teensy bit as a regional jet announced he was ready at 7 to depart. (Typically at PHF, 7-25 is the big plane and commercial traffic runway and 2-20 is the GA runway.) The tower told him to hold for me. The grin wasn't because we were making him wait, but rather that I felt like I was really part of the system, not just some student gumming up the works.

Anyway, feelings again, eh?

I turned final and Husband supplied the requested 20 degrees of flaps. My airspeed was good, holding just under 70 mph and it was a pretty decent landing, despite the wacko visual cues of such an enormous runway. So's to minimize the time on the ground, Husband pulled in the flaps while I brought us to a stop and put the carb heat cold; the rest of the post-landing checklist didn't apply since we were going right back up.

With gradual full throttle, we were on our way again. Shortly we reached 1000' and were at midfield before I knew it. Another call to the tower and we were again cleared #2 for 7 (this time for the option) behind the same Cessna who was doing another touch-and-go. I repeated and stated "cleared for a stop-and-go." This time around I got to do a more standard approach, starting my descent with flaps abeam the numbers and so forth. It should have been a good landing, but alas... I got slow really high and the stall warning came on. I mean, probably 50' up still. Runway 7 is enormous, so missing the numbers by half a mile would still leave plenty of room for lil' 388 to land just fine. I put in a little power and relaxed some back pressure. The horn stuttered off-and-on for the rest of the descent, and we landed quite firmly. It wasn't pretty, but it also wasn't a bouncer. I suppose I'd sum it up as a clumsy landing. Husband instinctively grabbed the yoke, and I told him I had it... actually, my memory could totally be wrong but I think he grabbed it after we touched down. I'll have to ask him about that.

We cleaned up expeditiously and again departed. Straight-out, after listening to an incoming aircraft's call from somewhere out ahead of us, I told PHF I'd like to depart straight-out then return to JGG. He, bored, okayed that. We turned off to go up the peninsula, keeping an eye out for the incoming traffic. After a few minutes, PHF alerted us that the plane should be no factor at 2000' off our right wing. We were at 2600 by then, and Husband picked out the other plane with ease.

He wanted to try a simulated engine loss on takeoff to see what the sight-picture would be for attaining the recommended 80-mph glide for that emergency in that configuration. As we neared a field, I set the trim for takeoff, pitched us up and went full throttle. As we slowed to Vy, we stabilized and then pulled the throttle (and carb heat) out. The nose quickly pitched itself over -- no leaning forward on the yoke from either of us -- and before long we were nearing 100 mph. The training mag articles all emphasize how (1) imperative the response and (2) extreme the nose-down are for an engine failure on takeoff. Perhaps it depends on when during takeoff the failure occurs, because our Vy is 83 mph, and best glide is 80, and it did not require an extreme input from us at all. Had we been climbing at Vx (65), well, I still am not sure since the plane pointed itself down so rapidly.

With that exercise behind us, we returned to 2500' and continued the scan for traffic into the setting sun through the haze (super for perceived visibility) as we approached JGG. Winds were reported to be calm, and an airport advisory indicated to land 31. We overflew Busch Gardens and Husband called out the rides he saw and what they were doing; some folks were down there having a nice (albeit chilly) evening!

At home base we crossed midfield to enter left downwind for 31. I felt way wide, so I brought my downwind in a little tighter, but then my base ended up way short and I overshot final. It wasn't awful, and I'm comfortable maneuvering back to centerline, so I chose not to scrap the landing. I was lined up and doing ~80, whereas 70ish would have been more appropriate for that stage. I pulled the power, and just then the swamp monster gave us a little jab. I put a touch of power back in to get us through it with a little more force and accepted that we'd land long; it was all still well within limits. I was not keeping centerline very well, and part of my effort was diverted to recovering that. As we got down into the runway environment, we were still way fast so I went to idle and tried to fly just over the pavement while bleeding off airspeed. I didn't want to pull back much for fear of ballooning, so I tried to ride it out. Unfortunately, my height judgment is, aside from being rusty and aside from being quintessentially feminine, not spectacular and we flew onto the runway. Not the good kind of "greased it" "flew onto the runway," but rather planted it with resolve onto the runway. The angle was shallow enough that no bounce or ouchy resulted... well, actually, we did have a flicker of a nosewheel shimmy, but nothing like the jaw-rattling shimmies we experienced before the dampener and wheel were replaced.

We rolled out, cleaned up, called for fuel, shut down and went home. As we left the airport, we stopped to snap a few pics of the beautiful sunset.



Despite having two firmer-than-satisfactory landings, all-in-all it was a really good flight. I got more airtime. Husband got to be my passenger and we got to go together. Well, the whole family got to go! And perhaps most importantly, I demonstrated that whatever that panic situation was three weeks ago, it was an isolated event and not some new gonna-be-a-mommy-so-must-eliminate-all-risk subconscious freak-out policy.

Discussion:
  1. Co-pilots: Having a co-pilot, or a pilot-not-flying, is great. It's really good and reassuring to know he's there and can help. Husband is quite talkative in-flight (honey, that's not a complaint!) and it generally helps me to continue learning. He knows the things that irk me, and can tailor his pointers around those!

  2. Power and landings: Landing #2 at PHF saw too little power; we had bookoos of room and a whining stall horn. More power would have stretched out the descent and eased that landing. The landing at JGG had too much power; I had deliberately put it in to get past El Chupacabre but left it in quite longer than I should have, making it an unnecessarily long landing.



Hours logged this flight: 0.9
Hours logged total: ?
Take-offs and landings this flight: 3
Take-offs and landings total: ?
PIC (solo) hours total:: ?

Monday, April 09, 2007

Baby is a boy!

We're growing a son! He's got the right number of arms and legs, a good strong heartbeat, a wicked-cool looking spine (really neat on ultrasounds!), and nicely defined muscles, too, don't you think? :)

Monday, April 02, 2007

News on the ground

The baby-pilot-in-making is now kicking, rolling and punching such that Daddy can feel it, too. Exciting!

Finally!

I never thought I'd get back to it and get it done! The writeup of the second part of my practical flight test.

Tuesday, March 20, 2007

The Killing Zone, killer #1

I've finally made it through the first real chapter in the book. The first few pages cover statistics and give background/justification as to why 50-350 hours of flight time is the range dubbed "the killing zone."

I have to agree with whoever said it a few months back (IFR Pilot? Diary of a Private Pilot?) -- the lack of editing on this book is distracting! Seriously, people, a high school kid with a pen could have done wonders to improve the grammar and flow!

That aside, however, there's good information in there. The first "real" chapter, as I've called it, covers the first major reason why/how pilots die: VFR flight into IMC.

I have to be entirely truthful here. My meager three hours of under-the-hood training showed me that, while I can certainly fly by visual reference to horizon, I trust my instruments more than my own perception and am very comfortable with them. Given that, the idea of flying in clouds has not been intimidating. Before you go yelling and screaming that I'm exactly the kind of pilot who becomes an IMC statistic, my training dictates that clouds ahead warrant a 180 and that's what I'd do. (Hopefully; some of the cited NTSB reports and "survivor" stories describe get-there-itis and other judgment flaws that lead to problems and I assume they were all good and diligent pilots beforehand, too.) In the book, Paul Craig points his finger at me and says my attitude is the reason young (read: inexperienced) pilots die. I'm a young pilot. I don't want to die.

I gleaned several useful points from the chapter that tempered my fearlessness (again, fearless does not equate to disregard of common sense) with regards to flying solely by instrument reference. First, and worst, is the idea of instrument failures and how subtle they can be. The fact that gyros wind down slowly and feed you increasingly incorrect information but at a such an insidiously slow pace that you're willing to continue "correcting" your trajectory to level off or fly straight is terrifying to me. On our plane, the suction gauge is at the very far right of the instrument panel, and while it's part of the standard scan, I could see missing the cue that something was amiss based on its read-out in a time of extra stress. Our plane also has this hideously bright red protrusion from the middle of the instrument panel that lights up when suction is lost; I've seen that at engine startup when the attitude indicator was sad and dead, but with some added RPMs the vacuum system kicks right up. Would it come on promptly at the start of trouble?

I don't know airplane systems well enough to know how to recognize or troubleshoot every problem (or most problems, even). Carb ice, check. Loss of suction, kinda check. Blocked pitot tube or static port? Maybe, but it would take longer for me to catch on to that. This chapter spent several pages discussing how to recognize such failures and what to do about them.

The second item is the physical disorientation. My naivete' says it wouldn't be that bad since it's easy to read and rely on the instruments (barring failures). Husband described his IFR training and how very, very different it is to have foggles on and fake like there are no visual cues to overcome versus actually being in a white-out cloud situation where the body very loudly insists on assessments that just aren't right. To demonstrate, he encouraged me to try to keep reading the book while he stood a foot away yelling at me. The book goes into a little detail about how the ear participates in a sense of equilibrium and how motion affects your perceived sense of stability in three axes.

I'd love to do one of those test simulators, the ones where the statistics for VFR pilots are really bad, like the longest surviving pilot lasted 8 minutes but the average was 20 seconds. I'll take their word for it that it is that deadly; I'm not one to tempt fate. But that is just difficult to believe without firsthand experience. When we finally move up to a plane Husband feels comfortable with for IFR trips, he'll have to take me into the soup to demonstrate...

Monday, March 19, 2007

Technical difficulties over?

Husband suggested it was probably a database issue at Bloglines (the reader I use) that was making it show up funny, and in fact today it's back to normal, so, good, I guess... :)

Sunday, March 18, 2007

Technical difficulties

Something is amiss in the blogger.com world....

If you're subscribed to this blog using the blogspot atom feed, you're probably now seeing posts from a blog called "Great blogs for you to use." Of course if you're seeing those posts, you won't see this one. I haven't determined what the problem is yet but am looking into it. Perhaps it will resolve itself in time.

I recommend updating your blog reader to subscribe to http://feeds.feedburner.com/pilot-in-training instead.

Friday, March 16, 2007

Checkride part 2 part 1

The first installment of my checkride flight finally went up. I hope to finish the rest of it with only another hour or two of work...

In case your feed reader missed it on account of the post being back-dated, it's here.

I'm so sorry for the delay! I'm ashamed that it's been 3 weeks! But yay -- I've been a full-fledged pilot for 3 weeks! :)