Hey,

 

first of all: thanks a lot for keeping the product up to date! I could finally come back to flying the IFly in FS9 again.

But there's one thing that hasn't been fixed...

 

I'll give you an example:

I climbed out of YSSY, TA was 10,000ft. Now I'm descending back to YSSY, TL is FL110. I did my Descent checklist early enough. In my opinion the F/O should push the baro button at FL110, because it's the TL that I entered on the Descent page in my FMC. But instead he's announcing "Transition Level" at 10,000ft and pushing the baro button right there.

Shouldn't he push the button at TL which is FL110?

 

 

If I instead push the baro button at TL/FL110, my F/O pushes it again at 10,000ft and I get back to the standard QNH.

I believe we can't read the data off the descent page due to an SDK limit.

 

We can only read the TA in the FMC, not the TL.

 

So in cruise, update the TA in the FMC to match the TL.

 

That's what FS2Crew can read.

I was about to post the same problem here. Did a flight from EHAM to LDDU, with EHAM having a TA of 3000ft and LDDU a TL of 10500ft. FS2Crew wasn't reading the TL of LDDU but the TA from EHAM when descending to LDDU. Problem with FS2004. I think the manual should be updated accordingly. 

Again, in cruise, update the TA in the FMC to match the TL.  We can't read the TL.  So update the TA.

 

Cheers,