1 hour ago, Stearmandriver said:

Did it ever occur to you to just turn off the autopilot and flight directors and, you know... Fly?  That's the first thing I'll always ask a crew when I see something like this develop in training or on a line check.  "You got into this business because you like flying, right?  It's ok to be a pilot every once in a while".  😁

No it never did. 😂

I am trying to work out the FMS. And by the way, I did fly it AND land on this flight, so there’s that. Hey, you do you and let me do me. 👍

Well, i did round two and things were looking up. I got the same runway 9 instruction, and I entered it into the FMS, again with a discontinuity. And then…WASM crash. I tried to load from autosave but the AP just was messed up and stopped 100% working. 

I also got the infamous Back on track error dialog when trying to load the A350, so it appears I have a flight or two after reinstalling before things go south. Bummer, because i really like this plane. 

10 hours ago, jon b said:

I used to fly along side him hauling night freight at his previous airline, when he’d just set that up.

He sold it for 2 million I believe?

I confess that for most tubeliners - as a 'definitely not a real airline pilot' - I can generally wing it for stuff like this and usually find a way, approved or not, of recapturing the approach glide slope and ILS.

But I can't with the Inibuilds A350.  In fact, even after reading their VERY comprehensive manual and watching ALL of the excellent Youtube run-throughs, I haven't made a successful ILS landing in it yet!!  And I'm pretty certain it's nothing to do with the A350 modelling...I'm pretty certain it's all me 

Hi @AJZip2 and @RobJC:

I'm not asking you to retry the A350 any more...🙂...you folks need a breather from the A350...

However, your ILS landing issues in this a/c reminded me of one (curious) thing that I faced only in the A350. Basically, I found that the (iniBuilds) A350 avionics sometimes fails to autotune the ILS frequency of the chosen Approach (does not happen with the A340). So, you will not (automatically) see the correct ILS frequency on the PFD/ND (see e.g., the 3rd screenshot from the bottom of my (recent) A350 post in the Screenshots Forum). 

If I recall correctly, in my (ORD->LHR) flight, the (LHR/EGLL) ILS 27R frequency (110.30) never showed up on the PFD, even though I'd correctly set the arrival to the ILS 27R Approach. So, I'd to manually set the ILS ID "IRR" on the RAD/NAV page of the MCDU, for the frequency to show up. And, of course, if you do not have the correct ILS frequency, then the LOC/GS guidance will not work for you. You can try to fly this behemoth (recalling that I'd nearly 400 pax in my A350-1000 flight) down to the runway, but I've not been too successful with such attempts...🙂...landing all over the place...

Anyway, indeed, today, I confirmed my observation, thanks to AI inquiry. See, below, along with the manual work-around solution, that I've bolded the text for.

"The iniBuilds A350 for MSFS sometimes fails to autotune the ILS frequency due to SimConnect communication errors, issues with MSFS scenery data, or conflicts with third-party tools like Beyond ATC (BATC). While it should automatically pull ILS frequencies from the navdata, users often need to manually input the frequency into the RAD NAV page when it fails. 

Key Reasons for ILS Autotune Failures:

• BATC Incompatibility: The autotune function is currently broken when using Beyond ATC, as the A350 does not always receive the frequency updates, requiring manual tuning.
• Scenery/Navdata Conflict: If the airport scenery in your Community folder does not correctly define the ILS, or if you are not using updated Navigraph data (using default MSFS data), the aircraft may fail to recognize the ILS.
• WASM Issues: As a complex WASM aircraft, it may suffer from issues in MSFS where the SimConnect events, which are responsible for updating cockpit radios, are not processed correctly. 

Workarounds:

• Manual Input: Manually enter the ILS frequency (e.g.,) and identifier in the RAD NAV page of the MCDU.
• Verify Approach Data: Ensure the arrival runway and approach are selected in the F-PLN page to help the system populate the frequency.
• Updates: Ensure both the iniBuilds A350 and your AIRAC cycle (Navigraph) are updated, as patches are planned to address these bugs."

I think sometimes in the SIM a bit of separation from a certain (troublesome) aircraft is desirable. Who knows, the distance from (or absence of) it, might draw you back to it (again) in the future...🙂...

Cheers...!

6 hours ago, fluffyflops said:

He sold it for 2 million I believe?

Not bad…🙂…

During my on-line search, I was accidentally led to PPRuNe, a while ago, and found the discussions (real Pilot talk…not by Wannabes…🙂…) quite fascinating.

However, I just read that, “While it was once considered a premier resource, some users on Reddit suggest that the influx of non-professional and casual users, has led to a decline in quality, according to a Reddit post.”

In my defense, I only happened to peruse the posts there, but never actually participated…🙂…

11 minutes ago, P_7878 said:

During my on-line search, I was accidentally led to PPRuNe, a while ago, and found the discussions (real Pilot talk…not by Wannabes…🙂…) quite fascinating.

However, I just read that, “While it was once considered a premier resource, some users on Reddit suggest that the influx of non-professional and casual users, has led to a decline in quality, according to a Reddit post.”

Personally, I don’t go near it , I don’t like it, full of arrogance, and I told its founder Danny as much. He just smiled and said luckily for him there’s plenty of people that do go there.

I prefer the much more gentlemanly forums at Avsim, here people have a genuine passion for aviation and piloting.

In the so called “real world” I find there are two types of people who want to be airline captains, those that want to fly airplanes , and then those who want to be a captain.

Edited February 23Feb 23 by jon b

1 hour ago, P_7878 said:

Hi @AJZip2 and @RobJC:

I'm not asking you to retry the A350 any more...🙂...you folks need a breather from the A350...

However, your ILS landing issues in this a/c reminded me of one (curious) thing that I faced only in the A350. Basically, I found that the (iniBuilds) A350 avionics sometimes fails to autotune the ILS frequency of the chosen Approach (does not happen with the A340). So, you will not (automatically) see the correct ILS frequency on the PFD/ND (see e.g., the 3rd screenshot from the bottom of my (recent) A350 post in the Screenshots Forum). 

If I recall correctly, in my (ORD->LHR) flight, the (LHR/EGLL) ILS 27R frequency (110.30) never showed up on the PFD, even though I'd correctly set the arrival to the ILS 27R Approach. So, I'd to manually set the ILS ID "IRR" on the RAD/NAV page of the MCDU, for the frequency to show up. And, of course, if you do not have the correct ILS frequency, then the LOC/GS guidance will not work for you. You can try to fly this behemoth (recalling that I'd nearly 400 pax in my A350-1000 flight) down to the runway, but I've not been too successful with such attempts...🙂...landing all over the place...

Anyway, indeed, today, I confirmed my observation, thanks to AI inquiry. See, below, along with the manual work-around solution, that I've bolded the text for.

"The iniBuilds A350 for MSFS sometimes fails to autotune the ILS frequency due to SimConnect communication errors, issues with MSFS scenery data, or conflicts with third-party tools like Beyond ATC (BATC). While it should automatically pull ILS frequencies from the navdata, users often need to manually input the frequency into the RAD NAV page when it fails. 

Key Reasons for ILS Autotune Failures:

• BATC Incompatibility: The autotune function is currently broken when using Beyond ATC, as the A350 does not always receive the frequency updates, requiring manual tuning.
• Scenery/Navdata Conflict: If the airport scenery in your Community folder does not correctly define the ILS, or if you are not using updated Navigraph data (using default MSFS data), the aircraft may fail to recognize the ILS.
• WASM Issues: As a complex WASM aircraft, it may suffer from issues in MSFS where the SimConnect events, which are responsible for updating cockpit radios, are not processed correctly. 

Workarounds:

• Manual Input: Manually enter the ILS frequency (e.g.,) and identifier in the RAD NAV page of the MCDU.
• Verify Approach Data: Ensure the arrival runway and approach are selected in the F-PLN page to help the system populate the frequency.
• Updates: Ensure both the iniBuilds A350 and your AIRAC cycle (Navigraph) are updated, as patches are planned to address these bugs."

I think sometimes in the SIM a bit of separation from a certain (troublesome) aircraft is desirable. Who knows, the distance from (or absence of) it, might draw you back to it (again) in the future...🙂...

Cheers...!

No breather over here! I loaded up the A350-1000 and got the crash on loading in every time, while the 900 was just intermittent. And that allowed me to track down the source of my WASM crashes. I had leftover debris from a pushback tool, and when i deleted it the A350 (both variants) are solid. I suspect this caused the 777F crash as well. 

The A350 is currently my favorite plane. Love it. 

5 hours ago, AJZip2 said:

I confess that for most tubeliners - as a 'definitely not a real airline pilot' - I can generally wing it for stuff like this and usually find a way, approved or not, of recapturing the approach glide slope and ILS.

But I can't with the Inibuilds A350.  In fact, even after reading their VERY comprehensive manual and watching ALL of the excellent Youtube run-throughs, I haven't made a successful ILS landing in it yet!!  And I'm pretty certain it's nothing to do with the A350 modelling...I'm pretty certain it's all me 

I have had no problems with ILS in the A350 so it has to be you. 😅

6 minutes ago, RobJC said:

I have had no problems with ILS in the A350 so it has to be you. 😅

Of that, I have absolutely no doubt 😂

2 hours ago, P_7878 said:

Hi @AJZip2 and @RobJC:

I'm not asking you to retry the A350 any more...🙂...you folks need a breather from the A350...

However, your ILS landing issues in this a/c reminded me of one (curious) thing that I faced only in the A350. Basically, I found that the (iniBuilds) A350 avionics sometimes fails to autotune the ILS frequency of the chosen Approach (does not happen with the A340). So, you will not (automatically) see the correct ILS frequency on the PFD/ND (see e.g., the 3rd screenshot from the bottom of my (recent) A350 post in the Screenshots Forum). 

If I recall correctly, in my (ORD->LHR) flight, the (LHR/EGLL) ILS 27R frequency (110.30) never showed up on the PFD, even though I'd correctly set the arrival to the ILS 27R Approach. So, I'd to manually set the ILS ID "IRR" on the RAD/NAV page of the MCDU, for the frequency to show up. And, of course, if you do not have the correct ILS frequency, then the LOC/GS guidance will not work for you. You can try to fly this behemoth (recalling that I'd nearly 400 pax in my A350-1000 flight) down to the runway, but I've not been too successful with such attempts...🙂...landing all over the place...

Anyway, indeed, today, I confirmed my observation, thanks to AI inquiry. See, below, along with the manual work-around solution, that I've bolded the text for.

"The iniBuilds A350 for MSFS sometimes fails to autotune the ILS frequency due to SimConnect communication errors, issues with MSFS scenery data, or conflicts with third-party tools like Beyond ATC (BATC). While it should automatically pull ILS frequencies from the navdata, users often need to manually input the frequency into the RAD NAV page when it fails. 

Key Reasons for ILS Autotune Failures:

• BATC Incompatibility: The autotune function is currently broken when using Beyond ATC, as the A350 does not always receive the frequency updates, requiring manual tuning.
• Scenery/Navdata Conflict: If the airport scenery in your Community folder does not correctly define the ILS, or if you are not using updated Navigraph data (using default MSFS data), the aircraft may fail to recognize the ILS.
• WASM Issues: As a complex WASM aircraft, it may suffer from issues in MSFS where the SimConnect events, which are responsible for updating cockpit radios, are not processed correctly. 

Workarounds:

• Manual Input: Manually enter the ILS frequency (e.g.,) and identifier in the RAD NAV page of the MCDU.
• Verify Approach Data: Ensure the arrival runway and approach are selected in the F-PLN page to help the system populate the frequency.
• Updates: Ensure both the iniBuilds A350 and your AIRAC cycle (Navigraph) are updated, as patches are planned to address these bugs."

I think sometimes in the SIM a bit of separation from a certain (troublesome) aircraft is desirable. Who knows, the distance from (or absence of) it, might draw you back to it (again) in the future...🙂...

Cheers...!

Well, interestingly, it has indeed been 27R at EGLL I've been trying to land at!!!!
 

Thank you for giving me hope that it's not - OK, not all - user error on my part 😊

10 minutes ago, AJZip2 said:

Of that, I have absolutely no doubt 😂

One thing I find extremely helpful is i have a default flight i use to test every plane out. For the Citation, Fenix, 777F and A350 it is KDEN to KLAX. I use the same SIDs and STARs and time compression to shorten up the long stretches. I know the waypoints, and understand exactly what should happen when. It is my shakedown flight. Usually within a flight or two i have sorted out whatever issues i was having, and then i try new routes to make sure i have it down. In the A350 my two shakedown flights went great, and had autoland going as well. Now i am just working through some other situations, like i totally stuffed above lol. 

Edited February 23Feb 23 by RobJC

1 hour ago, RobJC said:

I have had no problems with ILS in the A350 so it has to be you. 😅

I've a vague feeling that the (virtual) class-action lawsuit (lawyers) defending those (unfortunate) 400 pax, have not yet served notice.

Of course, you were the A350 Pilot-in-Command of that Miami bound (Delta) flight ...🙂...?

2 hours ago, RobJC said:

No breather over here! I loaded up the A350-1000 and got the crash on loading in every time, while the 900 was just intermittent. And that allowed me to track down the source of my WASM crashes. I had leftover debris from a pushback tool, and when i deleted it the A350 (both variants) are solid. I suspect this caused the 777F crash as well. 

The A350 is currently my favorite plane. Love it. 

"It is hard to fail, but it is worse never to have tried to succeed"
- Theodore Roosevelt

[Side Note: I almost daily used to take the local Roosevelt Road in the Chicago suburbs, for several years ...🙂...]

10 minutes ago, P_7878 said:

I've a vague feeling that the (virtual) class-action lawsuit (lawyers) defending those (unfortunate) 400 pax, have not yet served notice.

Of course, you were the A350 Pilot-in-Command of that Miami bound (Delta) flight ...🙂...?

haha true but I don't attribute that debacle to an ILS issue. The A350 was trying to get me to fly further out to make room to get lower, but oh no I knew better lol. So I would say I have had maybe 7 or 8 flights and except for the unfortunate passengers of DAL007 everything else has been solid on the ILS front. This is such a great plane.