cannot re-engage PROF
-
Fuel, weights, CofG and PERF entries can be input directly into the MCDU by the EFB, unless pilots choose instead to manually enter these, which is fine.
I keep seeing similar issues with FLC vs. PRF whereby PRF absolutely refuses to engage.
I usually climb out initially on FLC until constraints and/or busy airspace are out of the way after which I try selecting PRF mode, except it won’t engage. -
I appear to have the same issue.
I noticed a warning about a wrong cruise FL (FMC shows 350 max, I've set 300 for CRZ) shortly after takeoff.
When I click around on the autopilot panel, I get a lot AFCAS TARGET warnings on the ECAM display, which disappear and re-appear after a split second. -
I’m a bit at a loss with PRF not engaging.
My present route is MDPC-TAPA and whilst PRF was initially enabled somehow it switched to FLC and I could not re-engage it (maybe at CLB call-out).
My selected FL is within the MCDU max (FL310 vs. FL350) and I’ve tried different routes between the airports.
BATC is clearing me to climb through SID constraints, which I’m happy to do (though I wonder if this has something to do with it?).
PRF has been OK up until now in my other flights but then I didn’t chop and change CLB modes.
Has anyone found a workaround to allow PRF to be re-engaged?
-
I noticed something interesting during my recent flight. When I was cleared for an initial climb altitude, the same issue occurred as before, but this time I received an announcement from the cabin that they were prepared for descent. This made sense to me; it seems the plane believes I have activated the App mode, similar to Airbus. As a result, all the T/C and T/D indicators disappeared. Interestingly, I found that in some cases, I am able to re-engage the profile mode during approach when my altitude aligns with the green circle on the ND.
To make sure if something is causing this, I am listing the addons and hardware I am using:
honeycomb throttle quadrant (I also use its knobs for alt and spd)
Thrustmaster TCA Yoke
Saitek rudder pedals
Navigraph Simlink
BeyondATC
REX Atmos Core
RealTurb CAT Areas Global for MSFS -
I had the same issue tonight, took off from KORD, flight seemed normal. Cruise altitude was FL340, max in the FMS was FL350. I saw a message about invalid altitude on the FMS, and I couldn't use PROF mode after that (I was using HDG select mode on departure waiting for BATC to clear me to my first waypoint). After that the aircraft seemed to be incapable of climbing, and even in FLCH the aircraft was unable to reach cruise altitude and wouldn't climb at more than 200 knots or so. I was using a Simbrief F100 profile so wouldn't have been overweight...70,518 lbs for ZFW and 12,545lbs of fuel. Eventually I gave up the flight, very annoying.
-
I've just had a similar issue, except I was trying to climb above MAX ALT (as computed by the FMS). Shortly after departure whilst in heading mode the plane kicked me out of PROF and wouldn't engage (even if I reduced my cruise altitude below MAX ALT).
-
Sometimes doesn't engage PROF yes, it gives me this error sometimes when I change the original CRZ altitude. Imagine it came from Simbrief FL350, and I see OPT altitude is FL340 so I change it to FL330, on the CDU Screen I see "wrong cruise altitude", some warning like that, not sure the sentence now, I know from there that I can't engage PROF, all flight, even in flight cruise. Think could be something with the Simbrief initial import... don't know.
PS: Doens't know it it is an "error", it just doesn't engage. -
Has anyone had any luck for a workaround for this? It is happening almost every flight for me now. Still on climb from takeoff and boom... it goes into speed hold at 140 kts. Then the rest of the flight is all manual. No way to 'reset' it to get the profile back.
-
I have a similar issue taking off from Southend (EGMC) and using Sayintentions.ai. As soon as LVLCH or HDG is used there is no way to enable PROF mode again and speed needs to be calculated manually. This has been going on since the initial release of the F100.
Can we please have a solution to this bug?.
Thank you.
Christian C./