sddjd

More often than not the carriers are highly sensitive to having any aircraft bearing their logo/name while on the ground, in repair following an incident. Frequently logos are painted over or otherwise covered even while AOG teams are en route, and scrap/replacements are carefully controlled. Whether it makes a difference is debatable (and no reporter would ever be fooled), but it's been an m.o. for decades presumably to reduce the reaction by the uninformed public in the area.

"along with a bunch of other prep work to ensure the engine does not rotate during the flight. The lack of lubrication under pressure would be heck on the bearings, and would obviate the whole point of hauling the engine along" I understand in layman's terms why this would be the case; the question it raised in my mind is if the same is true for an engine that is shut down in flight some hours prior to arrival (ie: the BA 744 that continued onwards from LAX on 3). Is a shut-down engine still protected by other active systems/connections while it windmills in flight, or is similar damage inflicted by said windmilling at cruise (of course in addition to whatever caused the shutdown)?

"And all we had left was this one bolt...." B) Thanks for posting- these incidents so often (understandably) escape public documentation.

Thanks guys, will try to catch a video of the behavior as the steps to reproduce seem to be setting up for normal flight. Will post here and to a ticket once I'm able to capture it. Now what are the odds it'll be like a noise in the car- obvious until at the service drive?

I've been through many trim related discussions but have not seen a report of my current issue. Frequently the Alt Trim handle will spike to the full nose-down position. This behavior occurs either during the initial takeoff roll, or (most often) during final approach; it's frequent enough that I have one of my interior views centered on the handle so that I can anticipate and correct it before digging a hole in the runway B) I've updated via ops center, have no axis assigned to trim (via sim nor via FSUIPC, I use keyboard cmd), etc. Further, I've not even found an option to shortcut an axis or command to the Alt Trim handle. It's been relatively easy to circumvent now that I watch for it at the suspect times, just wondering if this has been seen.

Beware the specs and FAQ: In response to a question about 120hz at 1080p versus hz at 4K the response was as follows: "Hi That is correct, it runs 4K off 30HZ Regards" This puts it squarely in the realm of 30hz 4K monitors that were universally panned for their jerky/blurry mouse and window performance as pc monitors. Minimum for a smooth experience at 4K on pc is 60hz, and some newer models are now bettering that by a good margin.

And we saw how that played out with Fedex/UPS and the a380F....

Speculation only clouds the scenario. It's ostensibly similar to Helios 522 and that flight had no such wild circumstances; assuming no funny business with the black boxes the weather's holding and crews are on site so we'll know soon enough exactly what occurred.

Count me in for this one as well- I've made the (unsupported) mod to add the two internal tanks when flying QF, but would love a variant that accounted for these in the FMS!

Hi Andy, I also experienced an dual failure following a long-haul over the pole. If you've addressed to possible corruption issue you might also post the chain of failures that preceded the dual shutdown. I'm curious as my own was self-inflicted, resulting after an extended failure on my behalf to properly address a low fuel temp condition. That cascaded into other warnings and eventual glider mode short of Hong Kong :blush:

More than a bit stumped at the fact that my copy of ASN seems convinced that Los Cabos was sunny and clear (to 20k) with wind around 6kts all weekend through Monday. Anyone else having trouble finding the mystery hurricane in our hyper-realistic "live" weather add-on...? What might my settings be lacking? :blush:

Thx. Can't seem to trace it- I have no assignments for pitch or pitch trim in FSUIPC or FSX. Have confirmed that all these have nothing assigned at all and re-applied. Nothing. Only reaction I'm able to get is pitch up using keys, but no elevator trim...

Thanks both for the replies. Not working for me, but at least I'm off in the right direction to find the issue (ie: not a T7 item).

Apologize if it’s plainly listed but I haven’t been able to locate info on how to accomplish this (searches return innumerable posts regarding the other trim discussions). I have had no success mapping a key or joystick switch to pitch trim. Initially I thought this was not feasible in the T7, but I’ve seen others comment that they’ve done so. Any simple method or link to other posts? Thanks!! Dan D

I can identify; living there in the 80's I had a famously bumpy approach into LHR on a BA Tristar. Just as we crossed the runway threshold we were slammed onto the rwy; not freefall, but accelerated downwards from what I'd guess was still 100' up with a several-degree bank to the left (I was in the window seat watching as the left tip looked set to dig a furrow). Was truly shocking how violent the downwards slap was, not to mention the sound of the airframe as we hit the runway. We got to de-plane via rolling airstairs on the taxiway after that one.

Yes, engines running. Generally I start a fresh FSX session (default flight, default MS aircraft, then move to origin and load 777). I've since been reading up on low fuel temps; a Boeing paper notes that descent to altitudes as low as 250 may be necessary (assuming no polar temp inversion). Could be I went into this unprepared with an incorrect fuel type and let my tanks turn to slush, then solid...? Still not sure why that would lead to an oil temp spike instead of a flameout, but what a sim!

Just wondering if anyone has comment or insight on a corner into which I flew myself yesterday :blush: I was roughly mid-route JFK-HKG overnight when I received the "fuel temp low" warning. New to me, I looked up its meaning and some suggested resolutions (CDU was set to warn at -38). I was cruising at that time pre-step and so was "only" at 33k. I dropped to 300 and increased speed to just below max allowed. The warning remained lit through the duration of the flight. Upon descending into HKG at approximately 180agl the left engine oil temp spiked into the red; didn't slowly climb, it jumped. As I pulled up checklists the same warning appeared for the right engine. FF appeared normal, though simultaneously I received low pressure indicators for the left tanks. While I was still trying to make sense of these warnings oil pressure in both engines dropped, followed shortly thereafter by shutdowns/failures in both within sight of the airport. At that point, not wanting to end my flight in the drink I reset all failures and continued. I tend towards long overwater and polar flights, but this is a first. My question is whether I created my own little disaster by failing to solve the fuel temp issue, or if the double oil/engine issue might have been a program crash (FSX had been running a LONG time at that point). I can't imagine the odds of such a thing happening without user error. Might my left tanks have finally frozen, the single heat exchanger on that side (vs two on the right) being the reason it began there...? Not using saved states, etc, FYI. Was certainly jarring to have the rug pulled out in such a fashion. B)

Nice vid! Had my own first experience with truly foul weather yesterday arriving at Domodedovo. Last 20 miles were all in the red, and the first time I had to hand-throttle and hand fly the bird onto the rwy.... not sure if it was exciting in a good or bad way :blink:

ACA, just a quick question- have you bound the controls to FSUIPC, meaning processing each axis via the utility? I had similar issues with my Saitek setup dropping out while in FSX, as if the controls just stopped sending input to FSX. Having the axes mapped via FSUIPC keep my controls functioning even after the windows/FSX side vanished. You may have done this already, just noting what worked for me.

Good point, though the EU went the opposite direction and determined that first sale applied. Going a bit off topic, the Vernor case was a bit more complicated in that there were valid questions as to whether Vernor actually owned the software (purchased from an entity that had upgraded, which per A'desk's terms at the time didn't release the prev version, etc). More generally, even the skewed USSC would have a hard time supporting a publisher waving a TOU and revoking a buyer's right to use the software.

Correct on both counts. Autodesk tried similar restrictions on customers' right to own and re-sell their seats onwards and was roundly defeated in the resulting court actions. Essentially the publisher retained the rights to the software with regard to mods, decompling, etc, but the customer absolutely had rights to truly "own" what they'd purchased. The "right to use" terminology didn't fly. Methinks I need to use "right" one more time in that paragraph... B)

Just a note to owners of the 787-8 pack. A query to Aerosim regarding any info on a dash 9 expansion revealed that there are "no plans at the moment". The paint kit includes textures (raked wing tip areas labeled "for 9" and fuselage extension areas) that would allow for the -9. It's unfortunate that the expansion may not happen. If so inclined it might be worth while for current owners to email the authors, not complaining, but expressing your support for such an expansion were it to be released in the future.

I had a problem where my 787 was saved as the aircraft in the default flight, which caused my gauges to not respond. Once I saved the default flight back to one using a Microsoft FSX aircraft no more gauge issues. Might be worth a try...

Oh my, voodoo, a Spectrum? Am I dating myself by admitting to having toyed with a ZX81? B) My two cents, I'm okay with updates that are not nagware, and allow ME to choose. Incrementals are fine as long as they don't interrupt my sim time. I finally blocked a certain add-on manufacturer's access after their control center "update" then forced me to re-download newer versions of all their sceneries. This at a time when I had a brief hour or so after work for FSX. Personally, I'd like to see an option to leave the Ops Center running in the sys tray to receive updates automatically in off-hours selected by the user (wishlist item only, no feature request intended!)

B) Definitely seems to be a record. Their dev speed is solely their business, but it struck me recently that the real aircraft went from concept to roll-out in five years (and that goes back as far as when the eventual -300 was to be a trijet). I still love my 763 so will keep an eye out.... indefinitely.