Here is a problem that I have not previously encountered in RC3 or 4. I created a short flight plan from KLCI to KORE (around 60nm) in a Cessna 172 to test some new cloud textures and overcast. I requested 5,000' in the flight plan but was only cleared to 3000'. The problem with this picture is that Mt Monadnock is right in the flight path at about 3700' and each of my requests for a higher altitude was denied "due to traffic". Is this correct? Shouldn't MSA play a role here?

yes it should. but if it was a tower enroute flight (less than 80 miles), i don't believe i give you anything higher than your crossing restriction.that is hard one to decide which process over rides the other tower enroute/crossing restriction or msa. i'm sure it is msa. what is the msa at the arrival airport? departure? what does rc think the msa's are?jd

The approach plates show MSA for KLCI varies from 4300' to 5500' depending on approach vector. MSA for the KORE is 4300'. I fly mainly all GA single or twin, so many of my flights are short haul to practice approaches. An 80 mile flight in a single engine Cessna could take an hour with a strong headwind, so I may fly less than 80 miles to practice. I usually file between 4,000 and 8,000' depending on flight path and distance. Are you saying that any flight below 80 nm will be mandated at a lower altitude now in RC4? Shouldn't it at least be above MSA and MEF?

Neil,John was asking what RC showed as the msa, not the plates. Load the pln and view the Controller's Tab. What's the msa show there for KLCI?It does appear something's not right. With Teminal Enroute flights (80m or less), more often than not you are given a cruise altitude lower than what you filed, but that altitude should never be below the msa.

RC shows KLCI's msa to be 3400ft. Neil was clr'd to 3000ft. Hmmm... not cool.

>RC shows KLCI's msa to be 3400ft. Neil was clr'd to 3000ft.>Hmmm... not cool.I didn't have the time tonight to try another flight, but tomorrow I'll try another flight with the same plan and some new ones. This must be new in RC4, since 3.1 would clear me as filed. In the real world, I fly that route often and similar in the area and usually at 5,000 eastbound and 6000 westbound. MHT is the closest class C airport and is served by Boston Approach TRACON. Can you describe what the correct functionality in RC should be given a short flight such as this (80 nm)? What should I expect? When the clearance was obtained and readback, it included the requested altitude. When I was handed off by tower to approach/departure, I was told to climb and maintain 3000 and resume own navigation. I requested 5000 and was told unable.

tower enroute, is essentially no center controller. you are handed off from departure to approach. the 80 miles we chose was arbitrary.there is a tutorial in the manual for tower enroute, and tower enroute is also covered in the atc basics, i believe.in tower enroute (and this may be new in v4, i can't remember), you can never be approved higher than your crossing restriction is going to be.as a work around, not elegant, but i believe it will work for you, is choose turbo prop on the general options screenjd

As John said, choose tprop or jet (even though you're a prop) as a work-a-round for now. RCv4 knows nothing of right/wrong altitude for direction of flight. Up to you to file correct altitude. It's on the list.