I have a little puzzle.According to the manual, RC4 calculates the Transition Altitude - specifically always FL180 in the USA.But I do not find this happening. On a flight plan KRDM to KSMF planned for 11000 feet I was cleared to "FL110". The Controller info page shows "Dep TL( FL 60) Arr TL( FL 70)".Also, I note that when I load a FP the cruise altitude shown always seems to show the altitude of the last flight flown and not the current one. Maybe it is taking the Transition data from the last flight too? Should I be putting this in manually?John

The data files show 18,000 feet as the TA both both of those airports as expected. Are you restarting RC for each flight leg with a fresh plan? You can check the TAs in the Controller tab preflight. Any chance that the cruise altitude was entered by mistake in the TA section?The TA and MSA file if you want to look at it (after making a backup copy) is m4.csv. The third column is the TA in feet. Use Notepad or Wordpad to observe it searching for those two airports. Do not use Excel. It must be maintains as a text type file. This file is not altered by your scenery rebuild and is a fixed data file that will need to be replaced or edited to restore.Here are the entries for the airports you mentioned:KRDM,4950,18000KSMF,396,18000(The second column RC uses to determine you intercept or minimum altitude for destination but it is not a direct entry to my knowledge.)In summary see if the TA's are sticky if you don't restart RC. If you find the correct TAs in the Controller tab and you still have this problem then retry the flight starting Debug before you load the plan. Zip it up and submit it per instructions on logging at the thread in the top section of this forum.

I have a little puzzle.According to the manual, RC4 calculates the Transition Altitude - specifically always FL180 in the USA.But I do not find this happening. On a flight plan KRDM to KSMF planned for 11000 feet I was cleared to "FL110". The Controller info page shows "Dep TL( FL 60) Arr TL( FL 70)".Also, I note that when I load a FP the cruise altitude shown always seems to show the altitude of the last flight flown and not the current one. Maybe it is taking the Transition data from the last flight too? Should I be putting this in manually?John

make a log. instructions pinned to the top of the forum. i'd love to see what is happening here.as soon as clearance tells you fl110, you can stop rc, zip up the log, and send it to memake sure you click debug, before loading the .plnjd

Thanks for the ideas on this.In setting up some test situations, I think I may have worked out what is happening. I have actually been able to make identical flight plans produce different results in RC! I think it may be because I habitually save a new Flight Plan using the same file name as the previous one rather than use the long/detailed names given by default. I need to do some more flights to be sure . . .John

Hi, John:Is your environment FSX or FS9, and if FSX are you using the XML FSX plan format?Thanks.

Thanks for the ideas on this.In setting up some test situations, I think I may have worked out what is happening. I have actually been able to make identical flight plans produce different results in RC! I think it may be because I habitually save a new Flight Plan using the same file name as the previous one rather than use the long/detailed names given by default. I need to do some more flights to be sure . . .John

i don't understand. the only flight plan rc cares about is the one you load. how the .pln is made, what it's called, whether it's old or new, is still a .plnthere is nothing in the .pln, that can affect the transition levels, unless one .pln is from egcc and the other one is from katl.i just want to see a log, in the USA, where you're told to climb to FL110thanksjd

Hi, John:Is your environment FSX or FS9, and if FSX are you using the XML FSX plan format?Thanks.

FS9 - I use FS Navigator to generate my flight plans in FS9 format.

i don't understand. the only flight plan rc cares about is the one you load. how the .pln is made, what it's called, whether it's old or new, is still a .plnthere is nothing in the .pln, that can affect the transition levels, unless one .pln is from egcc and the other one is from katl.i just want to see a log, in the USA, where you're told to climb to FL110thanksjd

I agree! I don't understand either. I'll make you a log.John

I've sent JD a log as requested.This is definitely happening ONLY if I save a file using the same name as a previous one, a habit I got into before using RC but I can easily change my ways. I have attached two images of the Controller Info page below.This shows what I get if I save a new flight plan with the same file name as the previous flight:It seems to inherit the transition level and cruise altitude from the last flight.This shows what I get if I save the flight plan under a new name. This is the correct one, of course:That's how I shall do things in future, of course.John

It would be interesting if you could paste in the two plans (same name and new name) with their titles in a reply here. Open each plan with Notepad, then copy and then paste into this forum reply.I'd like to compare the two formats to see if there is any difference.The other question I have is did you modify anything on the Controller page and hit OK either the first or last time?Each save is with FS NAV, correct?

It would be interesting if you could paste in the two plans (same name and new name) with their titles in a reply here. Open each plan with Notepad, then copy and then paste into this forum reply.I'd like to compare the two formats to see if there is any difference.The other question I have is did you modify anything on the Controller page and hit OK either the first or last time?Each save is with FS NAV, correct?

Yes, both plans generated by FS NAV and no changes made to the Controller page on either occasion.Here we are:exported1.PLN - written over previous file[flightplan]title=KRDM to KSMFdescription=KRDM, KSMFtype=IFRroutetype=1cruising_altitude=10800departure_id=KRDM, N44* 15.24', W121* 9.00', +003077.43departure_position=GATE 6destination_id=KSMF, N38* 41.73', W121* 35.45', +000026.25departure_name=Robertsdestination_name=Sacramento Intlwaypoint.0=KRDM, A, N44* 15.24', W121* 9.00', +003077.43,waypoint.1=LMT, V, N42* 9.19', W121* 43.65', +000000.00,waypoint.2=RBL, V, N40* 5.93', W122* 14.18', +000000.00,waypoint.3=MYV, V, N39* 5.92', W121* 34.38', +000000.00,waypoint.4=KSMF, A, N38* 41.73', W121* 35.45', +000026.25,Roberts to Sacramento.PLN - same flight plan written as new file name:[flightplan]title=KRDM to KSMFdescription=KRDM, KSMFtype=IFRroutetype=1cruising_altitude=10800departure_id=KRDM, N44* 15.24', W121* 9.00', +003077.43departure_position=GATE 4destination_id=KSMF, N38* 41.73', W121* 35.45', +000026.25departure_name=Robertsdestination_name=Sacramento Intlwaypoint.0=KRDM, A, N44* 15.24', W121* 9.00', +003077.43,waypoint.1=LMT, V, N42* 9.19', W121* 43.65', +000000.00,waypoint.2=RBL, V, N40* 5.93', W122* 14.18', +000000.00,waypoint.3=MYV, V, N39* 5.92', W121* 34.38', +000000.00,waypoint.4=KSMF, A, N38* 41.73', W121* 35.45', +000026.25,The only difference I am aware of was that I accidentally chose a different departure gate when exporting from FSNav. I notice the cruise altitude in both shows as 10800 although I chose 11000.I have just found something. In with the flight plans are some RC generated files:exported1.rc46, 0 , 0 , 0 , 500 , 1800 , 600 , 1100 ,,,, 0 , 0 , 0 , 1 , 0 **,0,JSY, 0 , 0 , 0 , 0 , 0 ,0,0,SRH, 0 , 0 , 0 , 0 , 0 ,0,0,EGKK, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,I don't know what all those figures mean but I can see that the VOR and airport references date back to a flight I made ages ago. That is probably what is causing the problem? There doesn't seem to be an equivalent file for Roberts to Sacramento.rcd . I have no idea what this file does, but I would guess if I deleted it the problem wouldn't happen.John

Yes, both plans generated by FS NAV and no changes made to the Controller page on either occasion.Here we are:exported1.PLN - written over previous file[flightplan]title=KRDM to KSMFdescription=KRDM, KSMFtype=IFRroutetype=1cruising_altitude=10800departure_id=KRDM, N44* 15.24', W121* 9.00', +003077.43departure_position=GATE 6destination_id=KSMF, N38* 41.73', W121* 35.45', +000026.25departure_name=Robertsdestination_name=Sacramento Intlwaypoint.0=KRDM, A, N44* 15.24', W121* 9.00', +003077.43,waypoint.1=LMT, V, N42* 9.19', W121* 43.65', +000000.00,waypoint.2=RBL, V, N40* 5.93', W122* 14.18', +000000.00,waypoint.3=MYV, V, N39* 5.92', W121* 34.38', +000000.00,waypoint.4=KSMF, A, N38* 41.73', W121* 35.45', +000026.25,Roberts to Sacramento.PLN - same flight plan written as new file name:[flightplan]title=KRDM to KSMFdescription=KRDM, KSMFtype=IFRroutetype=1cruising_altitude=10800departure_id=KRDM, N44* 15.24', W121* 9.00', +003077.43departure_position=GATE 4destination_id=KSMF, N38* 41.73', W121* 35.45', +000026.25departure_name=Robertsdestination_name=Sacramento Intlwaypoint.0=KRDM, A, N44* 15.24', W121* 9.00', +003077.43,waypoint.1=LMT, V, N42* 9.19', W121* 43.65', +000000.00,waypoint.2=RBL, V, N40* 5.93', W122* 14.18', +000000.00,waypoint.3=MYV, V, N39* 5.92', W121* 34.38', +000000.00,waypoint.4=KSMF, A, N38* 41.73', W121* 35.45', +000026.25,The only difference I am aware of was that I accidentally chose a different departure gate when exporting from FSNav. I notice the cruise altitude in both shows as 10800 although I chose 11000.I have just found something. In with the flight plans are some RC generated files:exported1.rc46, 0 , 0 , 0 , 500 , 1800 , 600 , 1100 ,,,, 0 , 0 , 0 , 1 , 0 **,0,JSY, 0 , 0 , 0 , 0 , 0 ,0,0,SRH, 0 , 0 , 0 , 0 , 0 ,0,0,EGKK, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,0,, 0 , 0 , 0 , 0 , 0 ,0,I don't know what all those figures mean but I can see that the VOR and airport references date back to a flight I made ages ago. That is probably what is causing the problem? There doesn't seem to be an equivalent file for Roberts to Sacramento.rcd . I have no idea what this file does, but I would guess if I deleted it the problem wouldn't happen.John

delete all the .rc4 files. at some point you had a .pln called export1, from somewhere to egkk, which has the transition altitudes of 5000 and 6000.then you created another export1.pln, from krdm to ksmf, and because there was a export1.rc4 from a previous time, the transition altitudes were used from the .rc4.the rc4 file is to save customizations to a .pln, a unique .pln - which is based on a unique .pln file name - like katl-ktpa.plnby creating multiple .plns with the same name, is going to be problematic if these rc4 files are not deleted each time.jd

delete all the .rc4 files. at some point you had a .pln called export1, from somewhere to egkk, which has the transition altitudes of 5000 and 6000.then you created another export1.pln, from krdm to ksmf, and because there was a export1.rc4 from a previous time, the transition altitudes were used from the .rc4.the rc4 file is to save customizations to a .pln, a unique .pln - which is based on a unique .pln file name - like katl-ktpa.plnby creating multiple .plns with the same name, is going to be problematic if these rc4 files are not deleted each time.jd

Thanks - as I said above I can easily change my ways (and already have done). Just for interests sake, the main reason I over-wrote was to save a mountain of old FPs accumulating. Now I know I shouldn't, I won't . . . John

Thanks - as I said above I can easily change my ways (and already have done). Just for interests sake, the main reason I over-wrote was to save a mountain of old FPs accumulating. Now I know I shouldn't, I won't . . . John

if you don't use the flight plan customization, which is what rc4 files are for, routinely delete them. if you want to make all flight plans called exported.pln, don't modify anything on the controller's info page, and a rc4 file won't be created. or, just remember to delete exported1.rc4 everytime you create a new exported1.pln file.jd

John H.:Where are the "exported1.pln" files coming from. Is this how FS NAV outputs the file with this default name?Some other types of planners/FMCs if using the same basic name will attach an incrementing number appended to the primary name. See if that option exists.

John H.:Where are the "exported1.pln" files coming from. Is this how FS NAV outputs the file with this default name?Some other types of planners/FMCs if using the same basic name will attach an incrementing number appended to the primary name. See if that option exists.

No - I just used names like that for my own convenience.I'm grateful for all the input but I am fully sorted now that I know that I shouldn't re-use the same name for different plans. It is now just a case of getting used to a different way of doing things. Thank you both for your help and guidance on this.John