Michael,

 

The standard OAT at 32K is -48.4 ... so all is (should be) ok right now.

The MD-11 EHAM-KLAX was uneventfull as far as high TAT was concerned. Now for the first time since August 2011 I had an issue with TAT in the 737NGX. On a KJFK-KLAS flight at 17000 feet I realized the FPM had dropped to 500 and the airspeed was starting to decay. OAT was +37C. But I continued on eventually reaching FL280 where the OAT was +47C. I decided to return to Kennedy. A new ticket for support.

 

Michael Cubine

Michael,

 

Did you happen to check the reported upper level wind data for your flight/route ... what was supposed to be sent to FSX?

Michael,

 

Did you happen to check the reported upper level wind data for your flight/route ... what was supposed to be sent to FSX?

 

Vaughan

 

Are you referring to the wind and temperature by waypoint at 6,9,12,18, 24 etc. in the coded route weather?

 

I did check this and saw nothing unusual.

 

Michael Cubine

Michael,

Thanks for checking your report was OK.

 

Yesterday I took a test flight DTW-KFK PA46T 25000.

This aircraft does not see the actual OAT ... it thinks all is ok outside!

AS20112 reported average wind 033 06 -25.1C

 

I took a bunch of screenshots and seen a temperature change (the problem) .. during cruise.

 

 

These two screenshots were 6 minutes apart.

I have been having this problem with the Flight1 Cessna Mustang for a couple of weeks at least. Yesterday for instance flying BNA-CLE, the oat at fl180 registered 101 degrees and the tat was a plus 75 (approximate) and since the Mustang has FADEC, the N1 was 82 percent, the rate of climb was around 400 fpm and the tas was about 240, or 50 kts or so below normal. I had originally set my filed altitude to fl230, but had to change it to fl190 because it took soooo long to climb to that altitude. I tried turning off the as2012 and re-starting it, but no change.

For those with "unusually high TAT's" What is the Ram rise at mach .79? I actually am curious about this. SAT-TAT=ram rise. So whenever I look at the FMS prog page 2 I see the SAT. It is allways the correct temperature,e.g -54 at FL350. When I look at the TAT on the EICAS I see something like -25. The air is warmer due to the effect of friction and adiabatic compression. This is perfectly normal and realistic. On a CE421 at a TAS of 200KIAS the ram rise is a whole 4 degrees C. You can add that to the freezing level for icing conditions because that is the temp of your alluminum. The air temp probe is subject to this same effect and hence the higher temp. Watch the ram rise as you climb and go from 160 to 250 and then to 320 and then to mach speeds at higher altitude. The ram rise always goes up, TAT goes down but not as fast as SAT(bigger diff between SAT and TAT) This is perfectly normal and I believe modeled correctly.

 

If anyone has a ram rise chart fot the NG we can see if it is correct TAT for conditions.

Marc,

 

You see "the SAT. It is allways the correct temperature,e.g -54 at FL350. When I look at the TAT on the EICAS I see something like -25." values.

 

Just to verify, this topic is about pilots seeing (+) positive values that cause planes to fall out of the sky.

Just wondering if anyone else has seen a problem with the temp +50F and the dew point -40 (values from my previous screenshots here) causing aircraft performance problems during climb or cruise?

 

My first guess is this wrong data is being sent to MSFS by Active Sky.

Hi Guys, I also had similiar problems when I installed as2012 (tats ,severe wind direction changes etc) and after several days of hair pulling and a few tickets to Damien, I discovered the culprit to be FSinn (whether on line or not).. Cure... Disable vatsim weather by default in the options box...go to add-ons(in the plane) FScopilot >Settings>Disable anything to do with weather (Cavok etc) and and reboot computer..I've had no problems with it since (jumping altimiters etc..) Hope this can be of some help Regards Fred

Marc,

 

You see "the SAT. It is allways the correct temperature,e.g -54 at FL350. When I look at the TAT on the EICAS I see something like -25." values.

 

Just to verify, this topic is about pilots seeing (+) positive values that cause planes to fall out of the sky.

 

Sorry my bad. I should probably look and see if I have a plus sign there :Idea: actually!

Hi Guys, I also had similiar problems when I installed as2012 (tats ,severe wind direction changes etc) and after several days of hair pulling and a few tickets to Damien, I discovered the culprit to be FSinn (whether on line or not).. Cure... Disable vatsim weather by default in the options box...go to add-ons(in the plane) FScopilot >Settings>Disable anything to do with weather (Cavok etc) and and reboot computer..I've had no problems with it since (jumping altimiters etc..) Hope this can be of some help Regards Fred

 

I'm sorry to tell you I've never had anything to do with FSInn or FsCoPilot but I HAVE had the problems with engine-killing temperatures coming through............

 

Therefore, that isn't the general cause.

I have the same problem

This has happened before the last service pack and since on AS2012 with FSX/LDS 767/latest FSUIPC etc. As others have mentioned, closing and restarting AS2012 cleared the problem. Has happened in UK Irish and US airspace. high TAT in the climb thus reduced performance. Doing DUB-JFK on Thursday so will record detailed info and raise a ticket as well as posting here. DWC enabled btw.

I'll second what 767CP mentioned. Restarting AS2012 will solve the problem for me. I also have the latest build while experiencing the problem.