Crabby

Really weird, I have not seen this behavior in other flights I have flown. Not even the FMC gobbly gook spd/alt restrictions/predications or the T/D. Are you using Navigraph in the sim as I am?

Class A airspace is from FL180 to FL600, so that does not matter. Class B airspace is generally 0 feet to 10000 feet msl, therefore you should be at or under 250 there anyhow. Most Class B has a speed restriction of 200 knots. This is why the speed limit is not applicable. In essence, no matter what Class B you are in you will already be below 250 knots if you are legal. Yes, you can delete the speed limits in some aircraft, however that is like my truck. It can do well over 100 mph (Go 5.7 L Hemi!), but I will hit the speed limit before I hit the engine limit. I will guarantee you that if you go screaming into DGAA below 10K at 285 you will end up with several numbers to call at a minimum.

Ok, after filing out INIT B I see the same as you. Have you flown this? If you have, does the aircraft follow those altitudes in Prof mode? If you have not flow it, see if they change in the course of the flight.

Ok, the plane defaults to 250 at and under 10K. As far as Ghana, they are a council member of ICAO. ICAO specifically states that operations at/below 10K are restricted to 250. Ghana's own regulations call out the penalty/suspension for exceeding speed limits in "critical phase of flight". They define critical phase of flight as below 10000. I have seen reference to China not having this limit and they too are council members of ICAO so there is that. Apparently, they never adopted ICAO airspace classification with the exception of Sanya Oceanic space where they use feet and there is the ICAO/FAA restriction. However, mention was made that most pilots flying into and out of China are flying Boeing and Airbus so having the restriction as "law" does not matter as those aircraft are speed restricted by default. On Boeing you can change it (not sure if higher or not would have to look) and on Airbus there does not appear to be a way to change it. At the end of the day the restriction is to make it easier to see traffic and other hazards like birds. I would not see a need to exceed that speed giving the proximity to the arrical airport when reaching 10K.

Have you flown an RNAV with this plane? It is not like any other aircraft you have flown. Go to Youtube and search INI A300 RNAV tutorial. If you miss one step, it will not work just like in the real plane. As for the DCT TO, don't know never seen that.

I loaded up: KRO2F KRO UN604 INBET INBE2B LTFM From LGAV to LTFM I don't see anything wrong with the SID and I am using Navigraph sim data. Not sure what may be happening on your end.

I have not seen this anywhere I have flown so far (US, Alaska, Canada, Mexico). This actually sounds like a problem with the in sim nav data base or if you are using the Navigraph in sim replacement data, try it without because the A300 cannot read that. I load up a flight to there just to see what is in the FMC for me.

I have them. You mean you have not searched for the FCOM and POM for your planes? What did you or didn't you do withing the t/o performance calculator? For example, did you change the flaps settings? Did you select the packs off option? Did you try different slats/flaps settings?

Yea, that is why I stopped paying attention to the first load and never reported it at all. To me it is only a very very very minor nuisance.

I am not sure where it is at in the FMC and I am not in the plane at this time. I guess I also wonder why you would want to change the speed at that altitude/flight level as there is an actual speed limit there. Granted we are in a sim, but most folks want to fly realistically and in real life you cannot go 285 at that altitude.

Yes, however the DEFAULT speed limit at/below 10K(FL100) is 250 and it should absolutely slow down unless you changed the default. Did you change it to 285? That could be the reason for the asterisk.

My first thought is that the weather was different.??? The temp is right around 78F (that is what I understand). Your density altitude is right around 3600 ft. We have to remember that a SAFE takeoff calculation is not mere calculating what speed you have to pull the yoke back at. V1 is critical. The is the speed where you would have to reject a takeoff and is largely based on the calculated distance down the runway where you will still have enough room to stop. All takeoffs should be planned as rejected and all landings planned as a go-around. Actually, taking off or landing is just an acceptable outcome. Being close to MTOW means you will need more room left over to reject a takeoff and safely stop before running off the runway. Not saying the EFB might have an issue, but it is also as possible that it is doing its job and telling you the takeoff parameters are not safe. As you stated, you are very close to max takeoff weight before you even start making calculations. Might have to dump some boxes or fat people. Another way to look at it. MTOW means you can takeoff, it does not mean you should.

EREKA does not have an altitude or speed constraint on the chart. The first constraint is ASGAR at FL090. Most of the time you would want to be at 10k (or FL100) within 30 nm of your destination. EREKA is a bit over 40 nm. It looks like the FL100 is being predicted (the asterisk). I will have to check the FCOM, but the normal indications there are, for example, 5000 for AT that altitude, +5000 for at or above, and -5000 for at or below. So, I believe that altitude is predicted. However, you would have been close to FL100 at that point and the aircraft would possibly be beginning its speed reduction to 250 and it takes a while to do so.

How many times? First load (after install or update)? Ideas require more info. For example, with the exception of the last update, I had a CTD on first load (including all prior updates). However, it would never happen again until another update. V1.08 was the first time I did not CTD on first load. Not saying this is normal, as it is not, but that has been my experience.

Oh, remember I said this was reason 5000 I use Axis and Ohs. There are an additional 4999 reasons. Only one of them is I never beat my head against a door do to weird sim/addon behavior. AAO and other things I do mean I almost never have to wait on devs or Asobo to enjoy my sim. I like controlling my own life.

Reason 5000 I love using Axis and Ohs. No problems, no changes for me.

Don't let the door hit you in the butt on the way out. Hot pockets in the freezer.

Yep, some people like to go fishing and some like to hang around hoping a fish will fall out of the sky. Good luck. You could have fixed your "problem" in less time than it took to read my post. So, keep ignoring me and grab another hot pocket.

You can do anything you want. I created my own custom cameras and assigned them to one of my hat switches. You don't need anyone else to do this for you.

I don't speak German and too lazy to translate it. From the title of the thread, you need to check your throttle calibration.

Not sure about some things, but you would not get an armed message on the PFD when you hit the Final 3.0 FPA button. I hit that before I hit the Profile button to get the Prof Des message in the PFD. I believe this is where things are going sideways.

I would expect to see V1.07 shortly after it is released.

I fly them all the time. Are you sure you are at the platform altitude and NOT in Profile mode of any kind? You must be on ALT HOLD or in LVL Change. On the FMC did you see the FPA 3.0 change to some figure above or below the glide?

I saw this early on, like V1.0-1.03 ish. With 1.0.6 I don't see this behavior at all, even at light loads. I fly only the PAX version.

Version? Xbox or PC?