Page 1 of 1

Charts

Posted: Thu Nov 17, 2005 4:32 pm
by Bob Webster
'The latest notes on cruise speeds and so on brings me to a question that I have been meaning to ask you experts.

Are there any charts in existence that show the altitude/rpm/mp/fuel flow/%hp relationships for the Ranger engine?

I have the little white Ranger book and the military manual both of which seem to imply full throttle conditions and really aren't all that informative in my mind. I know it isn't a big deal, but I have been a charts and graphs guy most of my flying career. It seems like it is going to burn 10 to 12 gph regardless of what you do to it.

Bob


[Non-text portions of this message have been removed]'

Re: Charts

Posted: Fri Nov 18, 2005 1:35 pm
by Karl Saenger
'Bob,

The military manual AN 01-115CC-1, Appendix II states different
power settings from maximum contiuous to maximum range, sea level to
10'000 ft.

In my experience of operating a UC-61K with an Sensenich 86/54
propeller it burns about 9.5 gallons at 2100 RPM. I do lean the
mixture below 65% even at sea level. Carburetor is a Marvel-Schebler
MA 4-5.

There is no MP figures listed as the UC-61K has no instrument, but
the overhaul manual shows 2100 RPM are approx. 65% at standard.

Please bear in mind that engine and airframe are not factory fresh,
we might not get the stated figures anymore.

Regards

Karl

UC-61K # 891


--- In fairchildclub@yahoogroups.com, "Bob Webster" wrote:
>
> The latest notes on cruise speeds and so on brings me to a
question that I have been meaning to ask you experts.
>
> Are there any charts in existence that show the
altitude/rpm/mp/fuel flow/%hp relationships for the Ranger engine?
>
> I have the little white Ranger book and the military manual both
of which seem to imply full throttle conditions and really aren't
all that informative in my mind. I know it isn't a big deal, but I
have been a charts and graphs guy most of my flying career. It
seems like it is going to burn 10 to 12 gph regardless of what you
do to it.
>
> Bob
>
>
> [Non-text portions of this message have been removed]
>
'