(PIREP, long) Cherokee 180 from Bay Area to Bishop, CA

[Dave Jacobowitz]

[ summary: lots of plannig, heavily loaded plane. one good, clean
flight in the cool morning air, followed by a less admirable
return flight where density altitude and loading almost bit ]



KPAO -> KBIH -> KPAO Trip PIREP:

The goal here was to do a quick weekend trip to Bishop, California,
to so some rock climbing at Owen's River Gorge, the "Premier Sport
Climbing Area of the Eastern Sierras." There were several challenges
to this trip.

1. equipment was /A IFR Cherokee 180
2. pilot + 4 passenger ( 200#, 160#, 130#, 100# )
3. climbing gear ( 60# )
4. Crossing the Sierras
5. no O2.

As you know, I worked the Internet and the POH pretty hard to plan
this trip, and it kept working out on paper -- but just barely, at
least in my mind. Nothing ever said, "no!" but there were plenty of
potential gotchas, and though I thought I understood them, in hindsight
I think I did not fully respect how they were additive in nature.
(see, high, hot, and heavy at the end of this story. ;( )



Loading the A/C
---------------

With the passengers and gear, and fuel for Bishop, plus my traditional
add'l fuel: destination + alternate + 1 hr, the aircraft was within
five lbs of it's max gross. It was legal, but I'd never flown an
aircraft in that part of the envelope before. CG was not too bad,
however, about midway between fore and aft limits.

Outbound Leg ( KPAO -> KBIH )
-----------------------------

Got up at a 4:45 am to get a briefing, shower and get to the airport.
The briefing, and my examination of the night sky outside my bedroom
window made it clear that we would have to depart IFR, but that the
central valley would be clear. I filed two flight plans, one IFR, one
VFR.

IFR: KPAO -> SJC -> V334 -> SUNOL -> V195 -> ECA
VFR: ECA -> KMMH -> KBIH

At 6:30 my friends and I loaded up, and I picked up my clearance from
the tower just as they were opening for the day. We took off and were
soon climbing through about 750 feet of your basic summer marine layer.
This would be my 0.1 hrs of IMC for the weekend. (Exciting for me
nontheless, as I got to use my rather new IFR ticket!)

Oh, I should mention the takeoff. It was a little interesting. The
acceleration on the takeoff roll was underwhelming, and it took a good
chunk of the runway (2500' at PAO) to get to a rotate speed, this using
the short field takeoff technique. Nevertheless, the Cherokee departed
comfortably from the runway and climbed initially at a healthy 500 ft/min
in the cool morning air.

Before making it onto V195, I cancelled IFR and headed directly to
about the position where V230 (the 23 deg redial of FRA VOR) intersects
with the base of the sierras.

We climbed for a good long while. Though the initial climb rate out
of PAO was good, it soon tapered off considerably, and by the time we
were at 9000 or so, it was about 100 ft/min. what's always interesting
to me abou the high-altitude performance of these aircraft is how the
speed range at which the aircraft will climb is so limited. On Saturday
morning, it was between 80 and 90 mph. Go outside that range, and go down.

So, after I don't know how long, we were cruising allong at 11.5. When
we got close to the Mammoth Pass, I let the aircraft climb again, and there
was some lift to help us. But the time we were over the higher areas of
the pass, the aircraft was at nearly 13000.

The view was awesome. I didn't get to take pictures but the passengers
were happy.

Once past the high terrain, I let the plane descend under power, and
rolled well into the yellow arc (whee!) in the smooth mountain air as
we passed by KMMH (Mammoth) and turned towards Bishop.

The landing at Bishop was easy and pretty routine.

Odd experience after landing though. I had a mentally difficult time
getting the aircraft maneuvered to where I could push it into a tiedown
spot. Basically, there were a few other aircraft on the ramp, incluing
a couple of expensive ones with larger than average wing-spans, and for
some reason, my brain just "would not compute."

I suspect it was partly new airport confusion and potentially partly
hyopxia. Anyway, I think I'll invest in an O2 system if I do much more
mtn flying.



Return Leg ( KBIH -> KPAO )
-----------------------------

Because of a passenger's constraint, we could not return on Monday morning
in similar cool air conditions that we had gone out in. I was not super-
happy with this, but I aquiesced to an early evening departure on Sunday,
around 7pm. I thought that this would be a good compromise between waiting
for the air to cool and not crossing the mountains in the dark.

As PIC, I think this was the biggest mistake of my trip, and I'll be
thinking about it for a good while to come.

I got a briefing, and a 15 minute-old PIREP from a Centurion at 12.5
said the ride through the Mammoth pass was smooth so I felt good about
the crossing.

We took off from BIH rwy 30 at about 7. The wind was light and variable,
and 30 seems to be the calm runway there, and it's the longest. The
density altitude was about 7500. The POH made it clear that I could
comfortably escape in those conditions, so I tried it, and regret doing
so.

It's not that there was an accident. There was none. I used the short-
field takeoff, leaning for best power before t/o, etc, and as in Palo
Alto, the aircraft accelerated at a meandering pace. However, we were
off and climbing in less than half the 7100 ft runway.

The first 100 feet or so, the plane climbed normally, and then... it
would not climb at all.

It was a frightening moment for me, though thankfully not for the
passengers who did not know something was amiss. (Except for the one
passenger up front, a pilot herself, though not current.)

Though there were no thunderstorms in the immediate area, there were
rain streaks visible under clouds that were perhaps 30 miles or more away
(and in the south, opposite of where we were going), and I think the
aircraft was caught in some drafts from them. I don't really know for
sure, though, whether they were related.

In any case, there was maybe a 30 second period when the plane wasn't
climbing, and was only 200 feet off the ground. Eventually, it started
to climb again, though with only about 100 ft/ min, and only in the
narrowest range of airspeeds. I told myself that if took more than
three more minutes to climb to 1000 ft agl, I would return to the airport.

The plane did start to behave a bit better, and, doing large circles
in the (thankfully flat) vicinity north of BIH, we slowly clawed our
way up to about 9000, then headed over to MMH, where we again circled
to about 12.5, and then we flew the pass. I was expecting downdrafts
on the eastern side of the sierras, and so I wanted to have altitude
to spare, and I also approached at a 45 degree angle, to allow for
an out if things went poorly. However, by now, the plane was out of
the hot air, and flying more like it's pitiful (but predictably)
performing regular self. Also, I unexpectedly found lift where I
expected sink -- and I took it to about 13000.

Once over the mountains, we flew direct palo alto. Over Livermore
it became obvious that the sunol pass was not going to work vfr,
so I asked NorCal approach (with whom I was getting vfr flight
following) if I could go off-frequency to air-file IFR to PAO. He
said I could stay with him and get the VOR-DME into PAO. While on
vectors for the approach, we were over San Jose airpot, from which I
could approach PAO VFR, so I cancelled and went in and landed
uneventfully.



what I Learned
--------------

I can cross the Sierras comfortably in an underpowered light
plane. It just takes time and patience to get up there, I want
room to spare, but it's possible. Nice to know.


But the more ominous lesson is to take density altitude, aircraft
performance, and aircraft loading seriously. I had made a classic
"high, hot and heavy mistake" -- and I paid for it. I didn't do so
with my life this time, but the pounding in my heart might have taken
some time off the end!

I flew the airplane at its limits. I flew according to the book
values, and they were actually more or less right, but I did not
leave myself safe latitude for them to be wrong. A random variable
-- some potential downdrafts or other strange winds, for example,
almost turned my barely acceptable climb rate into a descent.

Though the outcome was succesful, I think this flight is more of
the "Never Again" variety. If I had to do the whole thing over
again, I simply would have insisted on a lighter A/C (ie, one
fewer passener) and/or that we wait until morning and fly back
under similar smooth, cool, conditions we flew out in.

Thanks for reading!
Dave J

[Nathan Young]

Glad to hear you made it safely. Probably the best lesson learned is
that the real world performance of a 30 year old plane rarely matches
the numbers in the POH, and that when operating near the edge of the
envelope - there is little margin for error (or Mother Nature).

The takeoff distance charts in the POH for my '71 PA28-180 stop @ 7k
density altitude. Extrapolating above the highest values in the table
give an ~1250ft ground run and ~2800ft to cross a 50ft obstacle.

Also, best ROC @ gross @ 7500ft DA is less than 300fpm. Not much
margin for downdrafts.

-Nathan


On 21 Jun 2004 00:27:36 -0700, (Dave
Jacobowitz) wrote:

>Return Leg ( KBIH -> KPAO )
>-----------------------------
>
>Because of a passenger's constraint, we could not return on Monday morning
>in similar cool air conditions that we had gone out in. I was not super-
>happy with this, but I aquiesced to an early evening departure on Sunday,
>around 7pm. I thought that this would be a good compromise between waiting
>for the air to cool and not crossing the mountains in the dark.
>
>As PIC, I think this was the biggest mistake of my trip, and I'll be
>thinking about it for a good while to come.
>
>I got a briefing, and a 15 minute-old PIREP from a Centurion at 12.5
>said the ride through the Mammoth pass was smooth so I felt good about
>the crossing.
>
>We took off from BIH rwy 30 at about 7. The wind was light and variable,
>and 30 seems to be the calm runway there, and it's the longest. The
>density altitude was about 7500. The POH made it clear that I could
>comfortably escape in those conditions, so I tried it, and regret doing
>so.

[Mike Rapoport]

Glad everything worked out OK. Sounds like you learned the meaning of
"marginal".

If you make this flight again, you might want to consider leaving a "lot" of
fuel behind departing BIH and landing an airport in the Central Valley for
fuel if you need to. Even on calm days there is very little margin in a
fully loaded normally aspirated airplane, particularly on hot days. I have
also had the "why isn't this thing climbing?" experience and didn't like it
very much either.

There are supposedly over 100 planes that crashed in the Sierra that have
never been found...

Mike
MU-2

"Dave Jacobowitz" > wrote in message
om...
> [ summary: lots of plannig, heavily loaded plane. one good, clean
> flight in the cool morning air, followed by a less admirable
> return flight where density altitude and loading almost bit ]
>
>
>
> KPAO -> KBIH -> KPAO Trip PIREP:
>
> The goal here was to do a quick weekend trip to Bishop, California,
> to so some rock climbing at Owen's River Gorge, the "Premier Sport
> Climbing Area of the Eastern Sierras." There were several challenges
> to this trip.
>
> 1. equipment was /A IFR Cherokee 180
> 2. pilot + 4 passenger ( 200#, 160#, 130#, 100# )
> 3. climbing gear ( 60# )
> 4. Crossing the Sierras
> 5. no O2.
>
> As you know, I worked the Internet and the POH pretty hard to plan
> this trip, and it kept working out on paper -- but just barely, at
> least in my mind. Nothing ever said, "no!" but there were plenty of
> potential gotchas, and though I thought I understood them, in hindsight
> I think I did not fully respect how they were additive in nature.
> (see, high, hot, and heavy at the end of this story. ;( )
>
>
>
> Loading the A/C
> ---------------
>
> With the passengers and gear, and fuel for Bishop, plus my traditional
> add'l fuel: destination + alternate + 1 hr, the aircraft was within
> five lbs of it's max gross. It was legal, but I'd never flown an
> aircraft in that part of the envelope before. CG was not too bad,
> however, about midway between fore and aft limits.
>
> Outbound Leg ( KPAO -> KBIH )
> -----------------------------
>
> Got up at a 4:45 am to get a briefing, shower and get to the airport.
> The briefing, and my examination of the night sky outside my bedroom
> window made it clear that we would have to depart IFR, but that the
> central valley would be clear. I filed two flight plans, one IFR, one
> VFR.
>
> IFR: KPAO -> SJC -> V334 -> SUNOL -> V195 -> ECA
> VFR: ECA -> KMMH -> KBIH
>
> At 6:30 my friends and I loaded up, and I picked up my clearance from
> the tower just as they were opening for the day. We took off and were
> soon climbing through about 750 feet of your basic summer marine layer.
> This would be my 0.1 hrs of IMC for the weekend. (Exciting for me
> nontheless, as I got to use my rather new IFR ticket!)
>
> Oh, I should mention the takeoff. It was a little interesting. The
> acceleration on the takeoff roll was underwhelming, and it took a good
> chunk of the runway (2500' at PAO) to get to a rotate speed, this using
> the short field takeoff technique. Nevertheless, the Cherokee departed
> comfortably from the runway and climbed initially at a healthy 500 ft/min
> in the cool morning air.
>
> Before making it onto V195, I cancelled IFR and headed directly to
> about the position where V230 (the 23 deg redial of FRA VOR) intersects
> with the base of the sierras.
>
> We climbed for a good long while. Though the initial climb rate out
> of PAO was good, it soon tapered off considerably, and by the time we
> were at 9000 or so, it was about 100 ft/min. what's always interesting
> to me abou the high-altitude performance of these aircraft is how the
> speed range at which the aircraft will climb is so limited. On Saturday
> morning, it was between 80 and 90 mph. Go outside that range, and go down.
>
> So, after I don't know how long, we were cruising allong at 11.5. When
> we got close to the Mammoth Pass, I let the aircraft climb again, and
there
> was some lift to help us. But the time we were over the higher areas of
> the pass, the aircraft was at nearly 13000.
>
> The view was awesome. I didn't get to take pictures but the passengers
> were happy.
>
> Once past the high terrain, I let the plane descend under power, and
> rolled well into the yellow arc (whee!) in the smooth mountain air as
> we passed by KMMH (Mammoth) and turned towards Bishop.
>
> The landing at Bishop was easy and pretty routine.
>
> Odd experience after landing though. I had a mentally difficult time
> getting the aircraft maneuvered to where I could push it into a tiedown
> spot. Basically, there were a few other aircraft on the ramp, incluing
> a couple of expensive ones with larger than average wing-spans, and for
> some reason, my brain just "would not compute."
>
> I suspect it was partly new airport confusion and potentially partly
> hyopxia. Anyway, I think I'll invest in an O2 system if I do much more
> mtn flying.
>
>
>
> Return Leg ( KBIH -> KPAO )
> -----------------------------
>
> Because of a passenger's constraint, we could not return on Monday morning
> in similar cool air conditions that we had gone out in. I was not super-
> happy with this, but I aquiesced to an early evening departure on Sunday,
> around 7pm. I thought that this would be a good compromise between waiting
> for the air to cool and not crossing the mountains in the dark.
>
> As PIC, I think this was the biggest mistake of my trip, and I'll be
> thinking about it for a good while to come.
>
> I got a briefing, and a 15 minute-old PIREP from a Centurion at 12.5
> said the ride through the Mammoth pass was smooth so I felt good about
> the crossing.
>
> We took off from BIH rwy 30 at about 7. The wind was light and variable,
> and 30 seems to be the calm runway there, and it's the longest. The
> density altitude was about 7500. The POH made it clear that I could
> comfortably escape in those conditions, so I tried it, and regret doing
> so.
>
> It's not that there was an accident. There was none. I used the short-
> field takeoff, leaning for best power before t/o, etc, and as in Palo
> Alto, the aircraft accelerated at a meandering pace. However, we were
> off and climbing in less than half the 7100 ft runway.
>
> The first 100 feet or so, the plane climbed normally, and then... it
> would not climb at all.
>
> It was a frightening moment for me, though thankfully not for the
> passengers who did not know something was amiss. (Except for the one
> passenger up front, a pilot herself, though not current.)
>
> Though there were no thunderstorms in the immediate area, there were
> rain streaks visible under clouds that were perhaps 30 miles or more away
> (and in the south, opposite of where we were going), and I think the
> aircraft was caught in some drafts from them. I don't really know for
> sure, though, whether they were related.
>
> In any case, there was maybe a 30 second period when the plane wasn't
> climbing, and was only 200 feet off the ground. Eventually, it started
> to climb again, though with only about 100 ft/ min, and only in the
> narrowest range of airspeeds. I told myself that if took more than
> three more minutes to climb to 1000 ft agl, I would return to the airport.
>
> The plane did start to behave a bit better, and, doing large circles
> in the (thankfully flat) vicinity north of BIH, we slowly clawed our
> way up to about 9000, then headed over to MMH, where we again circled
> to about 12.5, and then we flew the pass. I was expecting downdrafts
> on the eastern side of the sierras, and so I wanted to have altitude
> to spare, and I also approached at a 45 degree angle, to allow for
> an out if things went poorly. However, by now, the plane was out of
> the hot air, and flying more like it's pitiful (but predictably)
> performing regular self. Also, I unexpectedly found lift where I
> expected sink -- and I took it to about 13000.
>
> Once over the mountains, we flew direct palo alto. Over Livermore
> it became obvious that the sunol pass was not going to work vfr,
> so I asked NorCal approach (with whom I was getting vfr flight
> following) if I could go off-frequency to air-file IFR to PAO. He
> said I could stay with him and get the VOR-DME into PAO. While on
> vectors for the approach, we were over San Jose airpot, from which I
> could approach PAO VFR, so I cancelled and went in and landed
> uneventfully.
>
>
>
> what I Learned
> --------------
>
> I can cross the Sierras comfortably in an underpowered light
> plane. It just takes time and patience to get up there, I want
> room to spare, but it's possible. Nice to know.
>
>
> But the more ominous lesson is to take density altitude, aircraft
> performance, and aircraft loading seriously. I had made a classic
> "high, hot and heavy mistake" -- and I paid for it. I didn't do so
> with my life this time, but the pounding in my heart might have taken
> some time off the end!
>
> I flew the airplane at its limits. I flew according to the book
> values, and they were actually more or less right, but I did not
> leave myself safe latitude for them to be wrong. A random variable
> -- some potential downdrafts or other strange winds, for example,
> almost turned my barely acceptable climb rate into a descent.
>
> Though the outcome was succesful, I think this flight is more of
> the "Never Again" variety. If I had to do the whole thing over
> again, I simply would have insisted on a lighter A/C (ie, one
> fewer passener) and/or that we wait until morning and fly back
> under similar smooth, cool, conditions we flew out in.
>
> Thanks for reading!
> Dave J

[Doug]

>

> Thanks for reading!
> Dave J



Thanks for writing... being a new guy I devour these stories looking to be
a better pilot..

Thanks!

[Dave Jacobowitz]

I agree.

I'd have to say that of the two, my judgment of the
acceptability of the ROC was more the problem, not the takeoff.

For the takeoff, I had extrapolated as you said, and with a
runway that was more than 2x that value, I felt comfortable.
The takeoff was not problematic.

It was the initial climbout that was ... unpleasant. On future
flights, I will examine the ROC more closely and scrub if it's
too low. An alleviating factor at Bishop was lots of flat
terrain upwind of the runway, but that is the exception at
high aiports, not the rule.

-- dave j

Nathan Young > wrote in message >...
> Glad to hear you made it safely. Probably the best lesson learned is
> that the real world performance of a 30 year old plane rarely matches
> the numbers in the POH, and that when operating near the edge of the
> envelope - there is little margin for error (or Mother Nature).
>
> The takeoff distance charts in the POH for my '71 PA28-180 stop @ 7k
> density altitude. Extrapolating above the highest values in the table
> give an ~1250ft ground run and ~2800ft to cross a 50ft obstacle.
>
> Also, best ROC @ gross @ 7500ft DA is less than 300fpm. Not much
> margin for downdrafts.
>
> -Nathan

[Blanche]

Um....1 pilot and 4 passengers? In a cherokee 180? And the passengers
were not little kids under 50#?

[Greg Copeland]

On Mon, 21 Jun 2004 17:39:03 +0000, Doug wrote:

>>
>
>> Thanks for reading!
>> Dave J
>
>
>
> Thanks for writing... being a new guy I devour these stories looking to be
> a better pilot..
>
> Thanks!

Well said! I guess the line starts here! ;)

Cheers!

[Greg Copeland]

On Mon, 21 Jun 2004 21:48:06 -0600, Blanche wrote:

> Um....1 pilot and 4 passengers? In a cherokee 180? And the passengers
> were not little kids under 50#?

I think he counted himself twice. He offered only 4 weights. He said,
"pilot + 4 passenger ( 200#, 160#, 130#, 100# )".

Cheers.

[Thomas Borchert]

Dave,

great story, thanks for relating it. Seems you did everything right -
but with only a small margin.


--
Thomas Borchert (EDDH)

[Blanche]

Greg Copeland > wrote:
>On Mon, 21 Jun 2004 21:48:06 -0600, Blanche wrote:
>
>> Um....1 pilot and 4 passengers? In a cherokee 180? And the passengers
>> were not little kids under 50#?
>
>I think he counted himself twice. He offered only 4 weights. He said,
>"pilot + 4 passenger ( 200#, 160#, 130#, 100# )".

*whew!*

[Chixfly2]

One of my airplanes is a PA28-140 160hp. I finally took the back seats
out to prevent people from saying, "you don't mind flying me, my wife
and kids up to Tahoe for the weekend?".
The PA28 (140/160180) is a two persons + luggage airplane to me and
not a four persons with luggage.




(Dave Jacobowitz) wrote in message >...
> [ summary: lots of plannig, heavily loaded plane. one good, clean
> flight in the cool morning air, followed by a less admirable
> return flight where density altitude and loading almost bit ]
>
>
>
> KPAO -> KBIH -> KPAO Trip PIREP:
>
> The goal here was to do a quick weekend trip to Bishop, California,
> to so some rock climbing at Owen's River Gorge, the "Premier Sport
> Climbing Area of the Eastern Sierras." There were several challenges
> to this trip.
>
> 1. equipment was /A IFR Cherokee 180
> 2. pilot + 4 passenger ( 200#, 160#, 130#, 100# )
> 3. climbing gear ( 60# )
> 4. Crossing the Sierras
> 5. no O2.
>
> As you know, I worked the Internet and the POH pretty hard to plan
> this trip, and it kept working out on paper -- but just barely, at
> least in my mind. Nothing ever said, "no!" but there were plenty of
> potential gotchas, and though I thought I understood them, in hindsight
> I think I did not fully respect how they were additive in nature.
> (see, high, hot, and heavy at the end of this story. ;( )
>
>
>
> Loading the A/C
> ---------------
>
> With the passengers and gear, and fuel for Bishop, plus my traditional
> add'l fuel: destination + alternate + 1 hr, the aircraft was within
> five lbs of it's max gross. It was legal, but I'd never flown an
> aircraft in that part of the envelope before. CG was not too bad,
> however, about midway between fore and aft limits.
>
> Outbound Leg ( KPAO -> KBIH )
> -----------------------------
>
> Got up at a 4:45 am to get a briefing, shower and get to the airport.
> The briefing, and my examination of the night sky outside my bedroom
> window made it clear that we would have to depart IFR, but that the
> central valley would be clear. I filed two flight plans, one IFR, one
> VFR.
>
> IFR: KPAO -> SJC -> V334 -> SUNOL -> V195 -> ECA
> VFR: ECA -> KMMH -> KBIH
>
> At 6:30 my friends and I loaded up, and I picked up my clearance from
> the tower just as they were opening for the day. We took off and were
> soon climbing through about 750 feet of your basic summer marine layer.
> This would be my 0.1 hrs of IMC for the weekend. (Exciting for me
> nontheless, as I got to use my rather new IFR ticket!)
>
> Oh, I should mention the takeoff. It was a little interesting. The
> acceleration on the takeoff roll was underwhelming, and it took a good
> chunk of the runway (2500' at PAO) to get to a rotate speed, this using
> the short field takeoff technique. Nevertheless, the Cherokee departed
> comfortably from the runway and climbed initially at a healthy 500 ft/min
> in the cool morning air.
>
> Before making it onto V195, I cancelled IFR and headed directly to
> about the position where V230 (the 23 deg redial of FRA VOR) intersects
> with the base of the sierras.
>
> We climbed for a good long while. Though the initial climb rate out
> of PAO was good, it soon tapered off considerably, and by the time we
> were at 9000 or so, it was about 100 ft/min. what's always interesting
> to me abou the high-altitude performance of these aircraft is how the
> speed range at which the aircraft will climb is so limited. On Saturday
> morning, it was between 80 and 90 mph. Go outside that range, and go down.
>
> So, after I don't know how long, we were cruising allong at 11.5. When
> we got close to the Mammoth Pass, I let the aircraft climb again, and there
> was some lift to help us. But the time we were over the higher areas of
> the pass, the aircraft was at nearly 13000.
>
> The view was awesome. I didn't get to take pictures but the passengers
> were happy.
>
> Once past the high terrain, I let the plane descend under power, and
> rolled well into the yellow arc (whee!) in the smooth mountain air as
> we passed by KMMH (Mammoth) and turned towards Bishop.
>
> The landing at Bishop was easy and pretty routine.
>
> Odd experience after landing though. I had a mentally difficult time
> getting the aircraft maneuvered to where I could push it into a tiedown
> spot. Basically, there were a few other aircraft on the ramp, incluing
> a couple of expensive ones with larger than average wing-spans, and for
> some reason, my brain just "would not compute."
>
> I suspect it was partly new airport confusion and potentially partly
> hyopxia. Anyway, I think I'll invest in an O2 system if I do much more
> mtn flying.
>
>
>
> Return Leg ( KBIH -> KPAO )
> -----------------------------
>
> Because of a passenger's constraint, we could not return on Monday morning
> in similar cool air conditions that we had gone out in. I was not super-
> happy with this, but I aquiesced to an early evening departure on Sunday,
> around 7pm. I thought that this would be a good compromise between waiting
> for the air to cool and not crossing the mountains in the dark.
>
> As PIC, I think this was the biggest mistake of my trip, and I'll be
> thinking about it for a good while to come.
>
> I got a briefing, and a 15 minute-old PIREP from a Centurion at 12.5
> said the ride through the Mammoth pass was smooth so I felt good about
> the crossing.
>
> We took off from BIH rwy 30 at about 7. The wind was light and variable,
> and 30 seems to be the calm runway there, and it's the longest. The
> density altitude was about 7500. The POH made it clear that I could
> comfortably escape in those conditions, so I tried it, and regret doing
> so.
>
> It's not that there was an accident. There was none. I used the short-
> field takeoff, leaning for best power before t/o, etc, and as in Palo
> Alto, the aircraft accelerated at a meandering pace. However, we were
> off and climbing in less than half the 7100 ft runway.
>
> The first 100 feet or so, the plane climbed normally, and then... it
> would not climb at all.
>
> It was a frightening moment for me, though thankfully not for the
> passengers who did not know something was amiss. (Except for the one
> passenger up front, a pilot herself, though not current.)
>
> Though there were no thunderstorms in the immediate area, there were
> rain streaks visible under clouds that were perhaps 30 miles or more away
> (and in the south, opposite of where we were going), and I think the
> aircraft was caught in some drafts from them. I don't really know for
> sure, though, whether they were related.
>
> In any case, there was maybe a 30 second period when the plane wasn't
> climbing, and was only 200 feet off the ground. Eventually, it started
> to climb again, though with only about 100 ft/ min, and only in the
> narrowest range of airspeeds. I told myself that if took more than
> three more minutes to climb to 1000 ft agl, I would return to the airport.
>
> The plane did start to behave a bit better, and, doing large circles
> in the (thankfully flat) vicinity north of BIH, we slowly clawed our
> way up to about 9000, then headed over to MMH, where we again circled
> to about 12.5, and then we flew the pass. I was expecting downdrafts
> on the eastern side of the sierras, and so I wanted to have altitude
> to spare, and I also approached at a 45 degree angle, to allow for
> an out if things went poorly. However, by now, the plane was out of
> the hot air, and flying more like it's pitiful (but predictably)
> performing regular self. Also, I unexpectedly found lift where I
> expected sink -- and I took it to about 13000.
>
> Once over the mountains, we flew direct palo alto. Over Livermore
> it became obvious that the sunol pass was not going to work vfr,
> so I asked NorCal approach (with whom I was getting vfr flight
> following) if I could go off-frequency to air-file IFR to PAO. He
> said I could stay with him and get the VOR-DME into PAO. While on
> vectors for the approach, we were over San Jose airpot, from which I
> could approach PAO VFR, so I cancelled and went in and landed
> uneventfully.
>
>
>
> what I Learned
> --------------
>
> I can cross the Sierras comfortably in an underpowered light
> plane. It just takes time and patience to get up there, I want
> room to spare, but it's possible. Nice to know.
>
>
> But the more ominous lesson is to take density altitude, aircraft
> performance, and aircraft loading seriously. I had made a classic
> "high, hot and heavy mistake" -- and I paid for it. I didn't do so
> with my life this time, but the pounding in my heart might have taken
> some time off the end!
>
> I flew the airplane at its limits. I flew according to the book
> values, and they were actually more or less right, but I did not
> leave myself safe latitude for them to be wrong. A random variable
> -- some potential downdrafts or other strange winds, for example,
> almost turned my barely acceptable climb rate into a descent.
>
> Though the outcome was succesful, I think this flight is more of
> the "Never Again" variety. If I had to do the whole thing over
> again, I simply would have insisted on a lighter A/C (ie, one
> fewer passener) and/or that we wait until morning and fly back
> under similar smooth, cool, conditions we flew out in.
>
> Thanks for reading!
> Dave J

[Hilton]

Chixfly2 wrote:
> One of my airplanes is a PA28-140 160hp. I finally took the back seats
> out to prevent people from saying, "you don't mind flying me, my wife
> and kids up to Tahoe for the weekend?".

Sure you can do that. Make sure to leave San Jose (or whereever) at 5am.
Take him up on Tuesday, the wife up on Wednesday, and the kids up on
Thursday and Friday.

P.S.: I need to get back up to Tahoe - it's gorgeous in the summer! An hour
to get there, rent a car, and drive to the 'beach'...

Hilton

[Mark]

Nathan Young > wrote in message >...
> Glad to hear you made it safely. Probably the best lesson learned is
> that the real world performance of a 30 year old plane rarely matches
> the numbers in the POH, and that when operating near the edge of the
> envelope - there is little margin for error (or Mother Nature).
>

I'm Curious about something. Everyone says that a 30-year-old
airplane will not perform like when it was a new airplane. However I
never heard anyone explain WHY this is so.

Assuming that a airplane (either a new factory aircraft or 30 year old
trainer) has had it's annual done and engine is up to par (compression
ect..) than why would these values change? An engine close to TBO
will still deliver fuel and power values very close to the POH. The
only source of diminished performance I can think of would be from the
rigging and/or airframe that could be a little out of alignment,
however any large deviations would have to be fixed.

If the performance value of a 30-year-old airplane does not match the
values in the POH for that make/model of aircraft (i.e., performance
values change over time), then I suggest that the FAA needs to address
this issue.

[Mike Rapoport]

You are right, it should match the performance. There are a couple of
reasons why it doesn't.

The flight test data is taken on a perfectly rigged airplane.

In addition to a new engine, the airplane had a new prop.

Airplanes tend to get heavier over time. I have seen three airplanes
weighed and every one was 30 to 100lbs heavier than the W&B indicated.

People and their stuff is probably heavier than they admit.

Most of the performance data is calculated from a limited number of test
points. The airplane wasn't really flown at every point on the performance
chart.

Mike
MU-2


"Mark" > wrote in message
om...
> Nathan Young > wrote in message
>...
> > Glad to hear you made it safely. Probably the best lesson learned is
> > that the real world performance of a 30 year old plane rarely matches
> > the numbers in the POH, and that when operating near the edge of the
> > envelope - there is little margin for error (or Mother Nature).
> >
>
> I'm Curious about something. Everyone says that a 30-year-old
> airplane will not perform like when it was a new airplane. However I
> never heard anyone explain WHY this is so.
>
> Assuming that a airplane (either a new factory aircraft or 30 year old
> trainer) has had it's annual done and engine is up to par (compression
> ect..) than why would these values change? An engine close to TBO
> will still deliver fuel and power values very close to the POH. The
> only source of diminished performance I can think of would be from the
> rigging and/or airframe that could be a little out of alignment,
> however any large deviations would have to be fixed.
>
> If the performance value of a 30-year-old airplane does not match the
> values in the POH for that make/model of aircraft (i.e., performance
> values change over time), then I suggest that the FAA needs to address
> this issue.

[G.R. Patterson III]

Mark wrote:
>
> I'm Curious about something. Everyone says that a 30-year-old
> airplane will not perform like when it was a new airplane.

Not everyone says this. My 25-year-old Cessna 150 met the book performance figures.
At the time, it had a decent paint job, about 600 hours SMOH, and the prop had been
recently overhauled.

My take is that if the plane is in good condition, it will perform as well as it did
when new.

George Patterson
None of us is as dumb as all of us.

[Dave Jacobowitz]

I've heard this, too, to not take the book performance seriously, and
I don't think I agree with it -- at least not for the reasons given:
old airplane. The reason to not take the book performance seriously in
my mind is:

- professional test pilot
- nickless prop
- ISA day
- test aircraft did not have all the accumulated detritus in the back
that probably should be in the weight and balance since you never,
ever take it out of the airplane.

That said, my experience with the PA28-180 this past weekend was that
the plane did in fact fly as the book predicted. If I had a pucker
moment on my flight it was because I had the poor judgment to make a
flight that required the plane to perform as specified by the poh
*AND* I left no room for external factors, such as gusts and
downdrafts upwind of the runway.

Also, though I understand the poster who said that a Cherokee-180
simply is not a 4-place aircraft, I don't quite agree with it. The
aircraft is what it is. It has a useful load of nearly a thousand lbs.
Those pounds could be a lot of fuel, and one or two big people, or a
little fuel and three big people, or four little people, or whatever
combination you like. But to categorically write off capabilities of
the machine because it's easier to plan/accept/think about/trust,
unfairly diminishes the utility of the airplane.

If I had waited to fly back from Bishop in the early morning when
there was no weather and the air was cool, I am positive that I could
say honestly that the flight would have been perfectly safe, with all
four people, and our gear, and our fuel, all in an old rental
Cherokee-180.

Of course, my club just got a 182 on the line that I want to get
checked out in. Faster, more carrying capacity, better climb
performance, better views -- it'd be a much better mount for future
trips.


-- dave j
-- jacobowitz73 -at- yahoo -dot- com

"G.R. Patterson III" > wrote in message >...
> Mark wrote:
> >
> > I'm Curious about something. Everyone says that a 30-year-old
> > airplane will not perform like when it was a new airplane.
>
> Not everyone says this. My 25-year-old Cessna 150 met the book performance figures.