What aircraft parameters influence the gliding "BACK TO FLY" behaviour?

I have the mystery that the “BACK TO FLY” keybind in MSFS successfully
teleports the LS8 (Asobo glider) and 172 (Asobo GA plane) instantly up in the
air. But for the gliders I’m working on the planes are just being accelerated
along the ground a little way. I’ve tried swapping every .cfg file in the
SimObjects/Airplanes folder for one from a stock aircraft to narrow my problem
down without success. Could any clues be provided what aspect of the SimObject
influences that BACK TO FLY behaviour? I think I could fix it if pointed
approximately in the right direction. Thanks.

Hello @B21 Can you send us your package for investigation ? (see [3) provide
private content](https://devsupport.flightsimulator.com/articles/5483/how-to-
report-a-bug-or-crash.html)) Best regards, Yohan

thanks - each of our gliders behave similarly. Is it ok for you to download
the simplest, which is the K7 here:
https://flightsim.to/file/34815/schleicher-k7-glider ? Using a controls
keybind for the “BACK TO FLY” (I think Ctrl-Alt-U might be the default) you’ll
see the glider given what looks like a forwards “shove” but it’s not enough to
get it airborn. Other gliders slide along the ground without getting airborn
at all. But the Cessna 172 does an awesome immediate jump in altitude, so
something is ‘different’ in these gliders but I’ve failed to work out what it
can be.

Hello @B21 The issue come from ui_certified_ceiling being at -1 in your
aircraft.cfg, when the game try to teleport your glider, it will check this
value to know if the new position will be above it and will abort the
teleportation if it’s the case, due to it being at -1 the new position will
always be above it resulting in your glider never teleporting up. For example
in the dg1001 this value is at 15750. Best regards, Yohan

Hello @B21 The issue come from ui_certified_ceiling being at -1 in your
aircraft.cfg, when the game try to teleport your glider, it will check this
value to know if the new position will be above it and will abort the
teleportation if it’s the case, due to it being at -1 the new position will
always be above it resulting in your glider never teleporting up. For example
in the dg1001 this value is at 15750. Best regards, Yohan

ah, excellent - many thanks for your help.

Another question on “BACK TO FLY” - is there a definitive reliable way (as there is with SLEW) to detect when the pilot has triggered this action? Just looking at the altitudes and airspeeds and trying to guess is proving impossible. Or is there something I can put into all our glider aircraft.cfg’s that completely disables it? It’s a major problem if we’re stuck with this energy boost with no way to detect it.