Posky A330/340 and landing crash

[chrissy]

Hi!

First of all thanks for wonderful FSPassengers - I really enjoy flying with this software.
Unfortunately when using Posky A330/340 combined with PSS panel (Posky/PSS merge from avsim) I have two problems:
During takeoff I get a tailstrike even when taking off very smoothly - but the really annoying thing is a landing crash, which happend
several times with A330 and A340. After a longhaul flight that's really very disappointing...

I suppose it has to do with the load and balance of FSPassengers because without it landing works fine.

I have to use the air-file from PSS because only this works with the PSS panel (correct flap setting and other items).

Has anybody an idea how to avoid these crashes? Do I have to use other air-files and an other merge?

I hope somebody could help me in this case!

Thanks a lot in advance,

Christoph

[Dutch64]

Hi Cristoph, welcome here!
Well, first of all, as you know those planes are very long and tailstrikes are easy to get What angle do you have it on during take off?
About the load and balance, during flight, what angle do you read then?

[chrissy]

Hi again!

Thanks for your answer. The angle during takeoff is about 8° up, the angle during landing is about the same when following the
glideslope.

Do I always have to load the plane with fspassengers' load editor or e.g. can I use the load and balance section from the FS menu or
from the PSS load editor and copy it into Posky aircraft.cfg as it can be done when flying without fspassengers?

How are your experiences with posky 330/340 - PSS - fspassengers combined?

Thanks a lot for further replies!

Christoph

[Dutch64]

I had no problems with it but you can disable the loading feature of FsP. Find the more_option.cfg in de fspassengers\config folder and edit this line
DisablePayloadDialogWeightModif=0 into
DisablePayloadDialogWeightModif=1

[chrissy]

Hi!

Thanks a lot - I will try this and load the aircraft via FS menue.

Happy new year!

Christoph

[olseric]

During takeoff I get a tailstrike even when taking off very smoothly - but the really annoying thing is a landing crash, which happend
several times with A330 and A340. After a longhaul flight that's really very disappointing...

Here's the deal with 'em: First, to mirror Dutch, they are long. Tailstrikes occur around 9 degrees. If you are constantly striking the tail,
make sure you are in flaps 1+F, and at proper Vr speed before rotating. V2 (depending upon weight) should be in the neighborhood of
about 160 kts.

When you land, if you're hitting the tail, this is my inital thought: Too slow and not enough flaps. The big busses come in damn near flat.
It is a heavy jet, not a cessna: fly it onto the runway and don't "flare/stall" it onto the runway.

I suppose it has to do with the load and balance of FSPassengers because without it landing works fine.

Grab my A330 from the NWA Pack in the add-ons area. I use it all the time without any issue.

Do I have to use other air-files and an other merge?

The air file will change some of the fight dynamics, however, there should not be such a significant difference between the PSS and
POSKY aircraft that will cause the problem you are describing.

Good luck with it and let us know how it goes...we're here if you need anything else.

[chrissy]

Thanks a lot for your reply, Eric!

Unfortunately I had just another bad trip with the A340-300 from EDDF to FACT.
During descent (Failure in FSP set to 1%) a continuous warning sound started but I could not guess what it was - engines were fine, no
fire detected - I descended wit 330 knots (not in overspeed). Suddenly the FS detected a crash caused by aircraft overstressing - I can't
understand that - it was just a normal descent like each other before...

Restarted the situation - FSpassengers of course has ended the flight with a bad report before - I tried to make a smooth landing but I set
the front gear to hard on the ground so FS detected another crash.

Very disappointing cause I've had rarely these troubles before...

Thanks a lot for your further help!

Christoph

[Dutch64]

Did fs or fsp detect the crash? Anyhow, when you will browse through the forum here you will find that many ppl disable the crash detection
completely. Because sometimes there are "invisible" buildings etc . (glitch of FS and/or addon scenery) in which you can crash (or AI traffic cutting
you in half) and it would be a waste if you will get bad points just for some things behind your control.

[Jetsim]

chrissy wrote:
Hi again!

Thanks for your answer. The angle during takeoff is about 8° up, the angle during landing is about the same when following the
glideslope.

isn't that a high pitch angle for landing?I thaught that you were only supposed to pitch up 1 or2 degrees.
http://www.vc10.com/

[chrissy]

The crash was detected from the FS but could the warning sound come from FsP?
I don't understand the overspeed warning when the aircraft was far from the critical speed - as I've mentioned before. Could there be any
other reason why the aircraft was overstressed during a really normal descent without sudden wind changes or things like that?

Thanks and happy new year to everybody!

Christoph

[olseric]

I'm gonna take a stab at this and say the overspeed warning was thanks to a 180 wind shift. Wind in FS9 is very unreliable if you have not
figured this out already causing sometimes extremely unrealistic conditions.

My suggestion is to 1) Disable FS9 Failures, 2) Disable Aircraft Overstress, 3) Disable Overspeed Penalty. That should take care of
anything that is related to the wind issue.

P.S. Aim for about a 4 degree landing. If you're too nose up, speed up...those things should be touching down around 140 kias or so.

[LukeJGerst]

And believe me, 140 knots isn't too fast! I tend to come in a little high and then float over the runway for a loong time. My airspeed drops
as a result (unless I happen to be intelligent enough to just let the thing land grrrr ), and I keep the nose up to stay in the air (good grief
just put the plane down), causing both a tailstrike and drifting off the centerline, sometimes onto the grass. There has been several times
that I ended up at 120 knots, stalling, 100 feet above the runway. Those are the times you grab your seat, say "ouch, this is gonna hurt,"
and wait for FS to switch to Spot so you can witness the little fireball your plane made right on the grass.

[olseric]

Could there be any other reason why the aircraft was overstressed during a really normal descent without sudden wind changes
or things like that?

Normal descent profile (and this is a generalization for most jet aircraft)...

During inital descent, maintain MACH cruise speed until reaching 300 kias. Then hold 300 kias. The A330/A340 should intially descent
around 3000 fpm, and then slowly taper off to maintain 300 kias without idling out the engines. By the time you are around 11000 ft
(normal altitude expected around 40 DME from the field), you should be around 1500-1800 fpm and still clean. Slow to 250 kias or less
for the 10000' speed restriction and then continue descent.

[Grome]

A340, though it is my fav now, is not the easiest bird to fly, especially the POSKY version.

Here are some of my practical hints:
1) PRE-FLIGHT: in the FSP load dialog carefully observe the CG! Go to the Advanced Fuel Load dialog and empty the first from the top central fuel
tank! You'll not need that fuel in the flight, but your CG will be MUCH closer to the center in that case.
2) TO: let's face the truth, the POSKY FD is not very accurate. Add about 10 knots to the calculated ones to get the tailstrike safe Vr and V2 and
avoid the big bank angles and move the joystick as smooth as you can. Change the simulation rate to 1/4, switch to the outside view and control the
take off visually.
3) I use the folowing descent profile: Vvert. -2800 ft/min max., M0.77 till FL300, then 270 KIAS till FL100, then - 240-235 KIAS till the final approach.
4) The usual Vref lies between 137 and 140 KIAS
5) When the altitude is lower than 100Ft (according to the radio altimeter), I do the following:
a) lower the simulation rate to 1/4
b) switch off AP and AT
c) press W to see the runway and the principal gauges (Vspeed is most needed)
d) idle the engines
e) Flare manually , tuning the vertical speed and the bank angle. vert. speed should be between 0+needle thickness and the 3-d line down and the bank
angle should not exceed 3-d line from the horizon as read on the gauges.

That is the equilibrism, but practicemakes perfect and when you find that balance, you forget about the autoland..

[olseric]

Flare manually

If you're flaring, you're going too fast. It's a heavy...FLY it onto the runway...