How- User defined fix A320 MCDU
Thread Starter
Join Date: Sep 2005
Location: USA
Posts: 57
Likes: 0
Received 0 Likes
on
0 Posts
How- User defined fix A320 MCDU
New guy in the A320. For situational awareness, Tried to build a fix at 30 miles, for a 250 speed/10,000 user created constraint due to going into rural airport with no STAR. the other day I did this via FPLN page, L1, entered destination airport into amber boxes, then 30 mile as radius.
after that a small asterisk would appear to allow me to insert into the flight plan
On a recent flight NO asterisk appeared whatsoever, and we never figured out why.
any MCDU experts have some advice? Aircraft was 2015 year model 321. Honestly don’t know if it was a Thales or Honeywell box.
be gentle. New guy trying to learn.
Thank You
after that a small asterisk would appear to allow me to insert into the flight plan
On a recent flight NO asterisk appeared whatsoever, and we never figured out why.
any MCDU experts have some advice? Aircraft was 2015 year model 321. Honestly don’t know if it was a Thales or Honeywell box.
be gentle. New guy trying to learn.
Thank You
Join Date: Jul 2018
Location: on the edge.
Posts: 117
Likes: 0
Received 0 Likes
on
0 Posts
Hi, Just go to FIX INFO page, insert airport name, then type 30 and choose RADIUS, immediately you will get in the ND a radius of 30 NM centered on the Airport.....did i understand well what you need ?
Only half a speed-brake
Not fully.
He's trying to find why the asterisk did not show up after inserting 30 and getting the ring. Which creates a waypoint at the intersection with F-PLN trajectory.
He's trying to find why the asterisk did not show up after inserting 30 and getting the ring. Which creates a waypoint at the intersection with F-PLN trajectory.
Join Date: Jul 2018
Location: on the edge.
Posts: 117
Likes: 0
Received 0 Likes
on
0 Posts
Ok...so from FCOM:
Based on the above i can only imagine the airport inserted was not the corrrect one ? or maybe the flight plan was not completed thus not intercepting the circle ?
When the circle intercepts the current flight path, the FMGS compute the time, the along path distance and the altitude at the first intersection point, from the current aircraft position (small green font).
A large blue star is then displayed to insert the intersection waypoint into the flight plan.....etc
A large blue star is then displayed to insert the intersection waypoint into the flight plan.....etc
Thread Starter
Join Date: Sep 2005
Location: USA
Posts: 57
Likes: 0
Received 0 Likes
on
0 Posts
Only half a speed-brake
Somehow the tone of OP suggests he would have noticed.
Join Date: Feb 2002
Location: US
Posts: 108
Likes: 0
Received 0 Likes
on
0 Posts
Is it possible that there was a route discontinuity? Maybe the final airway point was more than 30 miles from the field, therefore the 30 NM radius didn't intersect with the flight plan?
Join Date: Jun 2014
Location: Village of Santo Poco
Posts: 869
Likes: 0
Received 0 Likes
on
0 Posts
"...Pushing 4L, after a radius has been entered, calculates whether a radius point exists on the flight plan from the waypoint on the FIX INFO page. IF A RADIUS POINT IS FOUND (emphasis mine), an asterisk is displayed in 4L next to the entered NM radius...
<snip>
"...If a radius point does NOT (emphasis mine) intersect the flight plan, white dashes are displayed in the UTC, DTG and ALT fields on the MCDU..."
So, it sounds like Fifi did not see where the flight plan was going to be within 30nm of the field.
Join Date: Jun 2014
Location: Village of Santo Poco
Posts: 869
Likes: 0
Received 0 Likes
on
0 Posts
Only half a speed-brake
Nice catch. The 'abeam/intersect' cannot be input if this would invalidate the active leg, i.e. replace the current TO waypoint, right?
Last edited by FlightDetent; 31st Dec 2021 at 05:07.
