Posts by FrankLFRS

Quote from Jet-Pack (IPACS)

It should automatically activate on the approach, too. You don't have to set the approach mode that high up. The speed constraint 210 kt will already slow you down to a similar speed anyways.

Yes that’s right. But the T/D being weird, I descend with a FPA and do all manually for the moment (until the next update).

About departure, the A320 follow something and finish to reach the next real waypoint. But flies out of the flight plan drawing, and sometimes too far setting the A/P off automatically.

I’m asking a friend what mean 16R/2 and INTCPT in the F-PLN...

[ANSWER]: the meanings of 16R/2 and INTCPT in the MCDU

16R/2 take off 16R fly 2 Nm ahead

H112 then head 112°

INTCPT until intercepting the 97° course to ELMOO

C097

ELMOO

For example, the A320 completely misses this departure. And many others (Geneva 23L u-turn to Zurich, Aspen, and many, each time there’s things like 16R/2 in the MCDU I’d say)

You completely clear your flight plan.

You select Palm Spring as destination.

You delete the target runway.

You click on APP.

You select R13RY.

You now can see the whole RNAV approach from. PSP to KPSN 13R.

Prepare the reste of your flight plan passing by the PSP point.

In the Airbus you have to be at 8000 ft when reaching the PSP point. You also have to select approach mode in the MCDU. You have to control your speed. You have to set APPR mode on in the FCU.

Your RNAV approach will start at PSP to the runway. It’s a 30 or 40 Nm approach. I start at 250 kts...

Yes I did have all of the waypoints. See the attachment.

Jet-Pack (IPACS) thanks again, things I miss more when preparing the flight plan are the total distance and the altitude of the airports. Because, I often don’t have the time for a long flight, and, the altitude to know whether or not I’m going to land in clouds etc.

In this case we see the whole approach, but if there’s a flight plan, coming from west for example, we would have a part of this approach. I may also miss and option to force the whole approach what ever happens would be fine too.

You definitely rock!

Is a thousand thanks ok for you?

So 1000THANKS

Hi. We don’t have this approach (neither into the MCDU).

iPad Pro 11-inch iPadOS 14.0.1 A320.

Quote from Eduardo Navarro

Beautiful and realistic cocks, clouds, 3D buildings

I know what you mean by cocks , but behave bro!

Infinite Flight is the worst of them. The most expensive, the most impostor, the most thief.

A very very toxic community. (this post would have been killed for sure on their forum, the author would have be threatened my mods)

The last pettiness of them is to publish a beta for their next version. But if you want global you have to pay it in the current version and install the beta. But on iOS in a beta all in-apps can be free for testing during the beta program.

They really are detestable. And the most unbelievable is to see their doggy-doggy followers gaping in front of their Supreme Guide.

---

Proud to be an Aeroflyer

I only saw Aspen with taxyway lights like Denver

It's shaper on iPad than on iPhone, but a bit blurry. Yes something sharper would be fine.

Quote from Jet-Pack (IPACS)

That movement has been in there for years

It's a placebo effect of the new update

Thanks.

There's a little jolt at touchdown:

Stare at the throttle UI control (which is steady) to see the cockpit move in a jolt.

I've just noticed that the A320 cockpit is moving at touchdown!

Was it the same before the update?

Hi. I do it manually until the bug is patched.

I add many waypoints all along the route to guess the flight level thought by the simulator.

I set, if necessary, the constraint altitudes of origin and destination in the MCDU F-PLN.

I set the maximum flight level I found in MCDU F-PLN as cruise altitude.

Then I calculate the top of descente like this: (FL CRZ - FL AIRPORT) / 3 + 3 or 4 Nm to decelerate. At this remaining distance, it’s the top of descente, so I set -3° in “FPA mode”, I also set my target altitude.

Before 10000 ft, I slow down with spoilers not to lose my 3° slope.

When I reach the target altitude I activate approach mode in the MCDU to make the plane decelerate waiting for flaps 1, 2 etc.

To descend, I also manually target the constraints altitudes because the plane actually doesn’t give a damn about.

It’s tricky but It works.

Trick: to find your destination altitude, go to location, never click on the map, search your airport with the keyboard.

Dear Jet-Pack (IPACS)

Subject: A320 MCDU F-PLN no constraints at origin and at destination (iOS/iPadOS 14 up to date)

I tried Cold&Dark yes/no, setting departure or arrival yes/no. No change. I’ll remain focused whenever I have a case OK with constraints.

Maybe that this issue is the reason of the T/D weird behavior.

I did screenshots of a 100% failing case. The MCDU contains altitude under the ground, probably based at sea level.

(Please note that it is a quick flight plan and that I know it is completely out of reality)

Thank you

Dear Jet-Pack (IPACS)

About the descent profile reaching sea level.

I kind of found why. But I don’t know how to reproduce it.

Sometimes, often, there’s no altitude constraints at origin runway and at destination runway in the MCDU F- PLN. It just happened to me from Denver to Aspen. If you manually set those altitudes in the flight plan in the MCDU, it seems to be back ok.

BUT, when descending, the original sea level altitudes are still set in mind of the A320. The plane wants to reach the profile that must be 5400 or 7600 feet lower.

I aborted the flight.

Yes a rattle sound of the objects shaked inside the cockpit

Firstly set your location, choosing for good between Cold & Dark or other. Don't do it after your flight plan is made.

Tap on your origin airport and set it as origin.

Tap on your destination airport and set it as destination.

Select a runway as origin.

Select a runway as destination.

Select a APP in destination I = IL,S L = LOC, D = DME, R = RNAV, X = ?.

Select SID tapping DEP. Each SID is a very long way including a group of waypoints and constraints.

Select STAR tapping ARR. Each STAR is a very long way including a group of waypoints and constraints.

So for a short travel, I think you should not use SID and STAR, this is what I do. Instead I insert waypoints for departure, a waypoint in front of the runway, etc. I also insert many waypoints between. For the moment it is necessary to know the cruise altitude in the mind of the simulator. One of you waypoints should contain the cruise altitude. And the most important, without them, the finale altitude may not be set as a constraint in the last "waypoint" (runway).

It works like LEGO bricks:

ORIG > RWY > DEP > ROUTE > ARR > APP > RWY > DEST

With DEP & ARR (SIDs & STARs), they will add many waypoints far away from the airport. Sometimes those waypoints overlay your destination or origin. This is why it could be completely confused.

In the MCDU:

you'll have to set ALT CRZ, INDEX COST, FLIGHT NUMBER, WEIGHT, PERFORMANCES.

There are 2 alerts in the ND that have to be cleaned (TCAS and WIND SHEER).

Quote from Jet-Pack (IPACS)

Did you set the altitude to zero then pull the knob? That's not how you should fly the approach!

Always push it with the first constraint of an ILS approach as a target altitude. From DECELERATE (because no T/D arrow for the moment).

The plane follows the green dot descent profil and suddenly (under 10000 ft, maybe after de waypoint) the green dot decent profile vanished upper. As if the profile of descent suddenly changed. The green dot descent profile reaches the top the altitude PFD strap.

The plane reaches the altitude before the waypoint/constraint (a few Nm before).