This has been puzzling several of us given that the real TA IV has something of a reputation for poor handling.

The real pilot's handbook is available online from the Swiss Flying School ... flugschulebasel.ch and has proved useful.

Before departure do a maximum power run-up while setting fuel mixture and propeller pitch to achieve a maximum manifold pressure and rpm. Now look at your trim and set it to nose up by quite a bit.

By doing this when you slowly open the throttle you achieve the best you can without going over the red lines and hopefully with the trim back so far you will unstick cleanly.

In this way I can cruise close to book speeds although rarely achieving 75% power...something feels wrong.

Tom 

I can't get into a cruise climb as the model ( just the IV ! )  is still underpowered ; I've sent a ticket.

Either one will only go to around 2000ft, and trimmed the max speed is around 90 to 95.

The low tail will climb better but it just seems to be the 2000ft mark it plays up.

The rpm does not drop, but the sound of the engine seems to drop off gradually.

I think this is a problem with the FSX-SE versions that are causing the problems, would be interesting to see what the others are using if they could be bothered to add to this and just say "ok here". On my non turbo versions you will see in another thread I had even a problem with the panel state loading incorrect, until found a procedure to workaround this.

Can't see any way forward for the problems with the Arrow's it does get very frustrating just more info would help.

Anthony

Hold fire

At recommended decent power settings (20" and 2300) with mixture rich the Piper assumes a 2000' decent. Holding the pitch to 500' minute causes indicated speed to fall near to stall.

I don't have to non turbo version, so cannot patch files.

I'm using FSUIPC to control all axis, but have rechecked calibration, and they seem fine.

Something's up.

Just checked this, as see less than 500'/minute, so definitely a marked difference to standard operating performance.

Thanks
Martyn

Seemed ok at first, plenty of power. Got to 2500ft put the autopilot on height hold. After a few minutes at 2500ft power seemed to go down  slightly and speed dropped to about 60-70 then stalled.

Always seems to come in at around 2000ft.

No weather conditions, just the default.

Anthony

Martyn wrote: It's a long shot but what happens if you enable 'Carb heat/eng anti-ice' and 'Propeller de-ice' using the keyboard assignments ('H' etc)?

It was worth a try, but no difference.

Anthony

Martyn,

I flew a flight, as you suggested, with Carb heat/eng anti-ice and Propeller de-ice on.  There were no sound anomaly's.  The weird thing though was when I turned them both off the sound still didn't occur.  I tried it several times both from a standing start and from touch and goes. It was all the same with no noise.

The problem with the propeller de-ice is it just toggles on and off with the L key and there is no indication, that I could find, as to whether it was on or off.  I don't know whether any of this helps or not.

Tom

Tried the Turbo III this morning that is exactly the same as the IV, where as  before this latest update it was fine.

I tried all checks now, will leave it to you.....

Anthony

Forgot to mention. If the Turbo is run first, the non-turbo cfg is all reset to zero's when it is loaded again, not good.

Anthony

On top of everything else, my Garmin GTN 750 is basically unresponsive in this aircraft.  It turns on but the buttons are inoperable at times and very slow often if they do work.

I am using P3D v3.4, newest update of that and not V4.  I use SPAD.next for my saitek stuff and have a hotas warthog throttle.  Windows 10 and every other aircraft I use have no issues.  

Needless to say this has been one giant 48-hour headache.    

Just noticed, when this problem happens the fuel flow drops to 10 and the rpm drops to 180.

Mixture has not been altered and throttle is on full. 

Pump is on

Anthony

Are you making sure not to overboost the engine? Here is some info from the FDE developer:

The first point is, with this aircraft you NEVER firewall the throttle. If you use full throttle, you will overboost the engine (Hg of roughly 46 at sea level - that is correct, confirmed by multiple real-world Turbo Arrow pilots). You should see the little square (greenish yellow at the top right of the panel) light up - that is the overboost warning light. You will also hear a kind of bubbling sound, which is the onset of detonation - the result of which is a loss of power, lower fuel flow and eventually complete failure of the engine. Please try the following: Full RPM and Mixture. Throttle - advance slowly to just below the red line on the Manifold Pressure gauge (so roughly 40 - 41 Hg, you'll be able to take off as low as 38, but the red line is critical) Carefully creep it briefly over the red line, check that the overboost light comes on (you may also hear the noise change with the detonation) then bring it straight back below. Take off and fly around, try some climbs but keep the Hg at all times below the red line. You can use your mixture and RPM as normal. You will find that, as pressure decreases with altitude, you will need to gradually increase the amount of throttle used to keep a given Hg, so that around the critical altitude for the turbo (12,000ft) you will probably have full throttle or somewhere near.

Are you making sure not to overboost the engine? Here is some info from the FDE developer:

Yes that was it when he sent me the above to try, works perfect now.

Sorry about the confusion totally my fault all the time. I was pushing throttle to full and keeping it there.

First time I've had a turbo prop  

Thanks

Anthony

I have the original arrow 3 plus the turbo arrows version 3 and 4. it is the Turbo arrows I have the problem with. Each of these have different problems

In the turbo arrow 4 version, as I climb above about 3000 feet, the engine starts to slowly fade out. Just as it did in a previous release for the software for P3DV3. Just flight issued the `fix` I mentioned which cured the problem. Its as if it has fuel starvation. during one flight, I intended to level off at 7000 feet but the engine had other ideas so I reduced my altitude to 3000ft and levelled off. The engine then continued to fade and the fuel flow metre was reducing as the amount of fuel being supplied was becoming less and less.  The throttle RPM was showing 2500 even as the engine note was slowly reducing. If left to continue the engine will either die out or simulate and engine fire.

In the case of the turbo arrow 3 version. The engine starts to fade during the climb but I noticed that if I speed the sim up to x 4 speed the power comes back. In this aircraft I managed to climb to 9000 feet but then in the descent there was an unseen hand constantly pulling the throttle back. I tried increasing the throttle friction but it does n`t make any difference so I spent the flight constantly fighting the ghost in the right hand seat. The throttle wants to drop back to idle if you do not give it any input. All this happens in P3DV4 using a full set of Saitek controls and boxes and with FSUIPC 5 and spad next.

The normally aspirated arrow works perfectly as does the new PA28 161 warrior 2 that has just been released.

Hope the above makes sense

Regards.. Rob

I will try your suggestion and will also try the same aircraft in P3DV3.4  which I still have installed. I have installed all of the Arrows and Warriors  into both sims so I will compare them shortly. The Arrows were working fine in P3DV3.4 but I haven't tried them in P3DV3.4 since the dual installer came out for P3D. version 4. 

 I used to own a PA28 161 warrior 2 and apart from the lack of pitch up when the flaps are lowered that others have mentioned this aircraft is a credit to you guys.

Thanks again.. Rob

The main thing is all is good now.

Thank you Paul and Anthonye for your suggestions.

Regards.. Rob

Has there been anything more to this thread than possible patch application? Very confused... and sad.

Regards,

Mario Di Lauro

Have you read the info posted by Paul (Delta558) on the previous pages of this thread? If this is occurring with the Turbo Arrow variant then you may be overboosting on takeoff.

Thanks

Martyn