Time to Climb

[Hank]

Pulling Carl's idea out of the "how high have you been" thread, this is the place to put your time to altitude. Please include (at least) the following:

• Model
• Prop (2, 3, scimitar, Top Prop, Q Tip, 4 blade; aluminum, composite, carbon fiber; etc.)
• field elevation
• altitude climbed to
• time from brake release to level off

You can of course include other pertinent information like OAT, loading, fuel burned, IAS, etc. I'll post my time from 264 to 9000 msl later this week.

Carl's original suggestion was "Time to 10,000 msl." It will be a few more days before I'm heading west, but I'll try to put that in, too. Stopwatch on, ya'll!

C'mon, bonal! I'll be taking pictures, too.    

[carl]

pictures too . wooohooo ! 

 i might have to take a vacation day to do this . 

[M20F]

To be useful really need to include altimeter setting, IAS, temp, FF or EGT, weight, and power settings or it is going to be all over the place.  In the what is the best RPM thread you have people climbing 25/25, 26/26, WOT/25, etc. which obviously makes a big difference.  Overall I find my 67F to be pretty close to book numbers in terms of rate of climb.

[kmyfm20s]

I think Wednesday I should be able to do this:)

[bonal]

OK well I guess I'm all in FWIW on the other thread 900fpm @ 119mph through 4000' 650fpm @ 115mph through 6000' and that's with 1 Pax 50% fuel. This should be fun...

[bonal]

Field elevation will make a difference so perhaps it should be a target AGL elevation for the test.

[Shadrach]

Everyone should use WOT 2700rpm, noting time at 1000' intervals to 10,000'MSL. This way we have apples to apples even if you live at a higher elevation. The numbers of the folks in the high country can still be compared to everyone else's (unless you live somewhere like telluride or Leadville).

[ArtVandelay]

You'll need to still adjust for density altitude and gross weight.

[aviatoreb]

Is fair if I wait a month and a half for -25F?

[aviatoreb]

4 hours ago, Shadrach said:

Everyone should use WOT 2700rpm, noting time at 1000' intervals to 10,000'MSL. This way we have apples to apples even if you live at a higher elevation. The numbers of the folks in the high country can still be compared to everyone else's (unless you live somewhere like telluride or Leadville).

My redline is 2650.

[Shadrach]

7 hours ago, aviatoreb said:

My redline is 2650.

Awww, my heart bleeds for you and the 4 bladed cross that you must bear! 

[cnoe]

18 hours ago, M20F said:

To be useful really need to include altimeter setting, IAS, temp, FF or EGT, weight, and power settings or it is going to be all over the place.  In the what is the best RPM thread you have people climbing 25/25, 26/26, WOT/25, etc. which obviously makes a big difference.  Overall I find my 67F to be pretty close to book numbers in terms of rate of climb.

Oh, the results are going to be "all over the place" alright. That's what makes it fun. I feel for the poor soul who's forever ridiculed for his slow numbers. 

And why would anybody climb at anything less than WOT and 2,700 RPM (unless you're redline is lower of course)?

Let's see, I weigh about 135#, and this shouldn't take more than 15 minutes at most, so that's about 4.5 gallons of fuel, then add in another 4 gallons for the 30 minute reserve during descent. Let's make it even safer by rounding up to 10 gallons total. But wait; I need 8 gallons minimum in each tank for the climb angle to prevent starvation, so let's go large and put 16 gallons total. That's 231# pilot and fuel plus an empty weight of 1740# for a takeoff weight of 1,971#. Woo hoo!

Now, Vy in my plane is supposed to be 101-94 mph depending on altitude. I assume that's at gross and might go up a little at significantly lighter weights. But I have no expertise in these computations, so maybe someone could help me out. In any case I imagine the (indicated) airspeed to 10K will be controlled more by cooling needs than by Vy. Then again, if I left the cowl flaps in "trail" I bet I could easily make 10K with oil-T/CHTs in the green. Hmmmmmmm.

It would sure be fun to see everybody's results.

 

[Mooneymite]

Should we record the times in seconds, minutes, hours, or days....? 

[aviatoreb]

37 minutes ago, Mooneymite said:

Should we record the times in seconds, minutes, hours, or days....? 

Fortnights

[carl]

this is all just to mess up the atc controllers . 

pure fun 

 i will be setting a new personal altitude

record . 

[Hank]

15 minutes ago, aviatoreb said:

Fortnights

Time in fortnights. Indicated airspeed in furlongs per fortnight.  

[Guest]

25 minutes ago, aviatoreb said:

Fortnights

Strange, I thought Mooneys were much faster than that?

Clarence

[Hank]

38 minutes ago, M20Doc said:

Strange, I thought Mooneys were much faster than that?

Clarence

Are we fast enough to measure in milliseconds? Think about this:  both Corvettes and Chevettes measure speed in MPH. The units are generally not related to the values measured.

[cnoe]

1 hour ago, carl said:

this is all just to mess up the atc controllers . 

pure fun 

 i will be setting a new personal altitude

record . 

Great idea; while in the neighborhood I might as well shoot for my stated service ceiling of 17,999'. I've got oxygen. It might be a good idea to set the altimeter to 29.92" and stop a little shy of 18K. Probably wouldn't be a bad idea to keep an eye on the transponder to keep pressure altitude at 17,900' or less as well. ATC likely doesn't see too many Class Alpha busts but I sure don't need to be calling any TRACONS. I once took a Remos GX to 14,500' with the doors off. Pressure altitude was well over 15K. I had to descend due to the cold temps as I started to uncontrollably shiver. At least in the Mooney I'll have doors and a heater. Fun stuff.

[Mooneymite]

1 hour ago, M20Doc said:

Strange, I thought Mooneys were much faster than that?

Clarence

Horizontally, not necessarily vertically.

[aviatoreb]

2 hours ago, Hank said:

Are we fast enough to measure in milliseconds? Think about this:  both Corvettes and Chevettes measure speed in MPH. The units are generally not related to the values measured.

How about a Jiffy?

• The jiffy is the amount of time light takes to travel one fermi (about the size of a nucleon) in a vacuum."

[Hank]

This is my favorite time unit, from nuclear physics and Tom Clancy:

A shake is an informal unit of time equal to 10 nanoseconds, or 10^−8 seconds. It has applications in nuclear physics, helping to conveniently express the timing of various events in a nuclear explosion. 

[aviatoreb]

10 minutes ago, Hank said:

This is my favorite time unit, from nuclear physics and Tom Clancy:

A shake is an informal unit of time equal to 10 nanoseconds, or 10^−8 seconds. It has applications in nuclear physics, helping to conveniently express the timing of various events in a nuclear explosion. 

But come one - the Jiffy?!!!  The Jiffy is just a cool time unit.

[Hank]

Shake as in one half of "two shakes of a lamb's tail." What's cooler than that for time? Besides "furlongs per fortnight" as units of speed, of course.  

[cnoe]

+1 for Jiffy.

Sorry Hank but 40 years ago, before the advent of 7-11, my parents owned a small convenience store called Jiffy Mart. I got all the free Icees I could drink, so I'm biased.

Sent from my iPad using Tapatalk