Entry out of range scratchpad A320

[pineteam]

Hello guys,

Twice I had the same issue on A320 Neo. ATC asked us to descend to FL240 by waypoint XXX. We were cruising at FL390. I tried to enter FL240 as a constraint in the waypoint XXX but it does not accept it and the message « Entry out of range » is displayed. Any idea why? The vertical speed required to comply with the constraint was only 1200 feet/ min. I can’t remember how many track miles to destination were remaining but quite a lot. Not sure if it has to do with the cruise phase. I had this issue twice at 2 different flights and both on Neos.
Also did you notice when you insert a ‘direct to’ waypoint,it sometimes go to the alternate route page on the opposite MCDU. Funny glitch and could not find anything about it on the FCOM either.

[FlightDetent]

No access to NEOs for me. On the old ones, however: If you changed the FCU alt first, and way before TOD, new ALT CRZ would be accepted by the FMGS. Inserting CSTR equal to CRZ ALT triggers the same message you got.

[OPEN DES]

Descent outside of 200Nm from destination is considered a cruise descent. I.e. no transition to FM descent phase. CRZ altitude updated in PROG page.

[RUMBEAR]

My guess is the FMGC was still in Cruise Phase as you mentioned it was an early descent. Altitude CSTR cannot be entered ar or above the cruising level.

[neilki]

Honeywell

Originally Posted by RUMBEAR

My guess is the FMGC was still in Cruise Phase as you mentioned it was an early descent. Altitude CSTR cannot be entered ar or above the cruising level.

I've seen this on the Honeywell neos if you're navigating to an ABEAM point. Clear The AB using Direct To and you should be able to build the constraint.
Given enough time in cruise this monkey found an answer :-)

[pineteam]

Thank you Guys for your time! I think that must be it. I Will insert the constraint before starting an early descent next time.
@ Neilki: Interesting, I Will try that too!
Happy flying. =)