time trial 200kts groundspeed to autohover

[harock]

how long does it take you to go from cruise to autohover?

 

from:

trimmed cruise 200 kts groundspeed (on hud)

at 1000 feet msl

to a hands off

autohover. at approximately the same altitude (1000 feet msl)

 

also count how many retrims you use during this proceedure

 

my time was 1 minute 57 seconds using trim 6 times

 

this is not a race

 

just a curiouse assesment of the capability of the chopper

and curiosity of peoples use of trim

 

thanks if you participate in this

[AlphaOneSix]

I have not timed myself, but I can tell you right now, that from the moment I start moving the controls to initiate my deceleration, to the time I reach a stable hover, I hold the trimmer down the whole time. I don't have any of my peripherals with me, so I can't try it out, sadly.

[fox_111]

Interesting. I'll try it next time I do a proficiency test flight.

 

That's how I improve my flying technique. I watch the tracs after and analyse what I could improve on.

[dozer76]

That is probably around the time it take me to engage autohover.

[EtherealN]

Hate to be picky, but how'd you get knots and feet onto the Ka-50 HUD? :P

 

That aside, I'll test this in a bit on the assumption that by knots you did mean 200 km/h (no conversion) and 305 meters MSL (with conversion).

 

(Makes a bit of difference which one's are mispellings.)

 

EDIT: Also, Fox_111, I would highly recommend Tacview as a flight analysis kit, truly awesome.

Edited April 16, 2009 by EtherealN

[Mugenjin]

Hate to be picky, but how'd you get knots and feet onto the Ka-50 HUD? :P

 

That aside, I'll test this in a bit on the assumption that by knots you did mean 200 km/h (no conversion) and 305 meters MSL (with conversion).

 

(Makes a bit of difference which one's are mispellings.)

 

EDIT: Also, Fox_111, I would highly recommend Tacview as a flight analysis kit, truly awesome.

 

well, check your options menu? you can change between metric and imperial system.

[EtherealN]

Oh, that's actually right. It's not the units on the real thing so I never even thought of that. :P Whoops.

 

However, 200 knots is 370.4km/h. Some problems occur before that...

[159th_Viper]

Thought I'd quickly give it a bash.......

 

Instant Action mission: Started in the air, did a hard left-bank to clear the HZ and picked up to approx 210km/h....commenced maneuver at approx 210km/h (did not worry about Altitude AGL) and was set up in approx 33 sec's. Must have trimmed a maximum of about 5 times I think......did not consciensly keep count as it's second nature by now.

 

Track

[Zorrin]

If you go into the ABRIS options you can change it to give you imperial units so that it will display knots/feet on your HUD. Needless to say analogue instruments stay the same...

 

It's in one of the setup tabs.

[EtherealN]

As Mugenjun already pointed out. ;)

 

And 200 knots is above vne (it's 370km/h, highest allowed IAS in any condition according to the chart is 305 km/h). That causes me to still think it's a typo and the question really is if the other one is also a typo. 300 meters MSL or 1000 meters MSL can make a bit of difference.

[fox_111]

Hate to be picky, but how'd you get knots and feet onto the Ka-50 HUD? :P

 

That aside, I'll test this in a bit on the assumption that by knots you did mean 200 km/h (no conversion) and 305 meters MSL (with conversion).

 

(Makes a bit of difference which one's are mispellings.)

 

EDIT: Also, Fox_111, I would highly recommend Tacview as a flight analysis kit, truly awesome.

 

That's what I use! It's a powerfull tool!

[Skydoc]

This type of maneuver sounds very similar to the coordination exercise we had to perform repeatedly on Gazelle conversion course in the UK: it was called the "Quick Stop." Its great for learining how to decelerate quickly and the key was to not lose or gain any altitude - hence the coordination exercise.

 

To make it more interesting, you can also enter the "180 Quick Stop" where you start downwind and initiate your decel as you trun 180 degrees into the wind - again great exercise for coordination of controls.

 

These are tactically useful, as you can imagine.

[harock]

i guess i called the units out wrong, i was using hud numbers

[ZaltysZ]

Instant action mission, 25s, 1 trimming at the end.

[Tbag]

47 seconds, didn't watch my altitude, less then 1000m.

[EtherealN]

i guess i called the units out wrong, i was using hud numbers

 

Cheers. :)

 

I'll run some tests on 200 and 1000 meters then.

 

Also, I do understand the confusion that can come there. I have the good fortune of using the same units DCS uses IRL too, though for how long remains to be seen since we're NATOifying a lot of things. >.<

 

Soon I'll have to defect to Russia to keep my proper metric units. ;)

[Yskonyn]

Is the point to keep your altitude within a specific range of the target altitude or are you allowed to veer off into the air and only stop time when you're back on the target altitude?

In other words; is the point of this to time how you can go from full speed into a hover while maintaining altitude or just to get to a hover from full speed by any means possible.

My time differs a LOT between these two.

So for uniformity's sake I'd say you should remain within 500 feet (around 200m) of your altitude while performing the maneuver.

[ZaltysZ]

The point is to keep altitude constant while decelerating. For sake of simplicity, everyone test this in instant action mission: unpause and decelerate.

[EtherealN]

Yskonyn, regarding altitude you could view the exercise like this: you are in a high-threat environment and need to stop. You are at 1000 MSL but only 50 meters AGL, with low hills on both sides, and need to stop. The area around you is covered by enemy radar SAMs so you don't want to ascend above those hills.

 

But since it's an exercise and more meant to train you in coordination as opposed to a specific combat scenario like the one I constructed above, the actual exercise is performed at 1000 meters AGL.

[Yskonyn]

I know, but my point was that there's no use in posting times without a specific set of boundaries. :)

[EtherealN]

Well, the OP didn't regard it as a competition or race. Just do it as close as you want to those parameters and let him know. :)

[Yskonyn]

Sure but how's the given data relevant if everyone's using different parameters to do the exercise? That's the same as asking for brake distances in a car without telling people what car to use. Some will try it in a truck, others in a pickup still others in a lightweight sportscar. ;)

 

Back to the heli, like I said, if I just try to get the quickest time from full speed to hover regardless how, I get vastly superior times as to do that while maintaining altitude. :)

While I did see the 1000 ft / m (whatever) altitude I just wanted to inquire wether that should be a constant value during the maneuver or just the starting and ending altitude.

Edited April 18, 2009 by Yskonyn

[EtherealN]

Well, I'd say it's more like saying which car but not which tyres. Your point is good though. :)

[ZaltysZ]

I will define more precisely.

 

Situation: default instant action mission

Start speed: default speed after unpause

Start altitude: default altitude after unpause

End speed: 0 km/h in all directions, a.k.a. hovering

End altitude: the same as start altitude

Aim: measure time of deceleration without changing altitude or direction during it.

 

This is not a competition. Adequate deviation is allowed. It means that few meters or degrees here and there is allowed, but if you jump up by 50-100m, then this exercise won't be completed correctly.

Edited April 18, 2009 by ZaltysZ