[VSD distance not correct]

Hello,

please take a look at this screenshot:

EPALO is 18.9NM away, yet in the VSD it is drawn at about 7NM.

The procedure was LGIR 27 EPAL1V. There is a 8000ft at or above restriction at EPALO. It seems that it was drawn at the point where that altitude was reached instead of the real distance.

[Cannot insert airways]

Hello,

I'm trying to insert an airway into a route and I'm not having much success. I'm only familiar to the A300 and the A320 and I'm new to the A350.

I fill out the INIT page:

Then I select the departure 33 AMLU2G, I press TMPY F-PLN and INSERT TMPY:

Then I select AMLUH airways and enter the enroute segment:

Again, I press TMPY F-PLN, but the enroute segment is not visible:

Am I doing something wrong?

[Cabin pressurization with high landing elevation]

Hello,

I set a landing altitude of 6900ft. I was held low during departure and the cabin climbed at about 500fpm to 6900ft. This is exactly right as described in the FCOM.

However, at about 20.000ft during climb, the cabin rapidly depressurized:

This is very unexpected, as according to the FCOM, it should climb to the maximum of the theoretical cabin altitude and the landing elevation and not descend again during climb. It appears that it tried to follow a delta P of 8.1 during climb?

Also, how can it depressurize with all outflow valves completely closed? In that case, I would have expected the cabin altitude to climb.

Descend is also unexpected. Again, it should descend to the higher of the theoretical cabin altitude and the landing elevation. Instead it descended way below the landing elevation at a rate of up to -1500fpm(!):

At some point it climbed again to the selected 6900ft. It does not look like the cabin pressurization controller is implemented correctly.

[Altitude intercept point drawn on curved path instead of straight path]

This screenshot was taken at the SID OPKC RWY 25L BADU1D:

As you can see, the altitude intercept point (FL070) was drawn on a path resembling the actual curved flight path instead of the straight path on the right. I wonder, if this is actually correct, since the A300 cannot draw a curved flight path.

On a related note, the path on the ND looks surprisingly bendy when performing a direct to...

[TCAS STBY message]

The TCAS STBY ECAM message disappears as soon as the transponder is switched to XPDR. Is this actually correct? At that point only the transponder would be on, but TCAS would still be in standby mode. I would have expected the message to only disappear if the switch is moved to TA/RA or TA.

[APU fuel tank hardcoded?]

Could it be, that the APU fuel tank is hardcoded an does not follow the actual tank configuration? Here I managed the pumps to feed the APU from the center tank:

Yet it only drew fuel from the left outer tank:

I remember back when we had the bug that the APU could not be shut off, I also was unable to crossfeed it from the right tanks. It looks like it is somehow hardcoded.

[Incorrect intercept at DAAG]

Hello, I selected the SID SADA1B (Runway 27) with the IZA transition at DAAG. That intercept point is not correct, it should be to the north of the airport, not 30 miles south:

I'm using Navigraph AIRAC 2501.

[How to request route only?]

I have just tried it out again after the last update and the INIT B page is no longer getting filled by the acars request. I assume this was actually a bug and not the intended behavior. It now works again like it used to and is fine for me. If you have an open issue on your side, it can be closed. Sorry for the fuss!

[APU keeps running if start is aborted]

Turn on the APU master switch and press the start button. Then turn the APU master switch off again, while the ACCEL light is shown. 

The APU now keeps its current RPM and consumes fuel for hours:

It resumes the start process where it left off when the master switch is turned on again and start is pressed.

Instead, I would have expected the APU to turn off when the master switch is set to off.

[Why is the init B page getting filled?]

Hello,

I just started flying the A300 again and in my last two flights, the INIT B page got filled with some nonsensical values:

I'm not using the acars function anymore and this screenshot was taken after the INIT A page was filled an nothing else. Where do these values come from and what can I do to prevent the init B page from getting filled?

[Landing distance flaps 20 vs 40]

Hello,

I made some landing calculations for EKCH. This is flaps 40:

And this is flaps 20, otherwise with the same parameters:

I 

Is it correct that flaps 20 requires less landing distance than flaps 40, despite the approach speed being about 10 knots faster?

[How to request route only?]

Have you considered using the CO Route field to load the route? It would be ok, if it would load a locally stored flight plan. It just gets really annoying having to input long routes manually for every single flight.

[Doors warning ECAM inhibition]

I always found it weird, that the APU page is not displayed automatically. This is caused by the ECAM door warnings, giving the DOORS page a higher priority. Now, I'm not sure if I'm correct, because this issue should have been noticed by the advising A300 pilots, but the way how I interpret the FCOM, the door warnings should be inhibited until the second engine is started:

[VOR jumps around in PLAN mode]

I have programmed the SID GMMN/RW35R SADI1D. Scrolling through the waypoints in PLAN mode, I noticed that the CBL VOR on the ND jumps around.

In the first screenshot, it is to the north of the runway, in the second screenshot, it is close to the runway threshold and in the third screenshot it is southwest of the runway. It looks like the relative distance to the center of the ND uses a wrong factor.

[How to request route only?]

Back in the old days, requesting Simbrief data from the ACARS page only filled the route. Now it seems that it fills out everything. Is there any way to request the route only?

[PAPI 30L off]

14 hours ago, richboy2307 said:

The current solution is a stop-gap that acts as a middle-ground for both datasets. Team is working on a more long-term solution.

I think this makes the problem worse. Before you could just ignore the ILS and make a safe visual landing. Now you need to ignore the ILS and the PAPI as well and this makes visual landings even more difficult. Since landings in VMC are much more common, I would prefer if the PAPI is right for that.

[OMDB Statics and VDGS]

On 12/25/2023 at 12:26 AM, Tarzan said:

2. Statics. I removed them but can’t use the gates where they where placed. 

I agree. I would also really appreciate, if all gates would be available please.

[IMM EXIT opens VERT REV page]

I flew a holding and then wanted to leave the holding. I pressed IMM EXIT* on the LEGs page. What happend was that the VERT REV page opened and the aircraft continued to fly the holding. I would have expected it to leave the holding.

I was able to leave the holding with a direct to the next waypoint.

[Do holdings use magnetic course?]

I added a holding to my STAR. Based on the charts, the inbound course would be 265° magnetic and right on the track of the previous leg. I noticed, that 258° were suggested in the FMC and I changed it to 265°.

I then noticed, that the hold was a bit rotated from my previous leg:

The hold was then actually flown at about 270° inbound course:

Could it be, that the holding was constructed using true course instead of magnetic? The holding was around DGAA with a magnetic variation of 4°W.

[FLT CTL page title missing]

I just noticed that the FLT CTL title is missing on the ECAM page:

The FCOM shows the page title in the upper left corner:

It is also visible in this video at 13:15:

https://youtu.be/CSgVmpgHmpQ?si=fHr6X5xSUhpggSB5&t=795

 

[Incorrect turn at ZMCK]

Yes, it was Navigraph AIRAC 2405.

[Incorrect turn at ZMCK]

Thanks Crabby for clarification. This is a misunderstanding, my issue description was not clear. Let's try again:

I'm well aware that it does not draw curved segments. This is how the procedure is drawn during preflight:

This looks absolutely correct to me, just like in the charts with a leftwards turn to final.

Once I arrived, the procedure looks different and it became a rightwards turn:

I would have expected it to still look like in the first screenshot. Again, I fly these procedures using raw data when this stuff happens, but I assume this may be a bug which iniBuilds may want to fix or at least be aware of.

[Incorrect turn at ZMCK]

1 hour ago, Crabby said:

 Pilots had to fly to SER, then outbound on 129 radial using NAV (not RNAV), then at or before 17 dme they would initiate a left turn to intercept using HDG.  Ahh, the days of pilots doing pilot crap.  

Well, that's exactly what I did. What are you trying to tell me? Should we not report bugs anymore, because these bugs may or may not exist in the real aircraft?

[Incorrect turn at ZMCK]

I flew to ZMCK with the ILS Y 29 approach via SER 1. It has an outbound leg to the right at 129° with a left turn towards final. During preflight, the drawing on the ND looked correct for the procedure. However, when flying, the INTC waypoint moved to the left instead of right:

I am using Navigraph AIRAC 2405.

[Turning packs off does not update FLX TO thrust]

That stuff is copyrighted, we shouldn't share those here. But search for the A310, you will find a manual with the same FMC as the ini A300.