- Upon reaching orbit in the abort mode ATO, I've never succeeded to use the ITEM+35 +1 or +2 to program an OMS-1 or OMS-2 burn, it loads like a burn with 0 velocity. Maybe it has to be defined in the mission file?
It was mission specific.
I loaded target for ATO ( aiming for 105 Nm Apogee) or AOA target ( Locations KSC or white sands, shallow one or not for example etc)
For AOA, you can use target that you can find in ascent fdf part 7-1 ( you can see the little number after the slash, which would correspond to item35 + that specified target in real life)
You can feed leo tools with those peg 4 parameters ( and usually you will have to file with the Theta angle because our more lofted orbit shape will not be exactly the same than the one used in those files)
I spoke a bit about it there
https://forum.flightgear.org/viewtopic.php?f=19&t=34315
- In a few situations, I was badly choosing to fly a TAL abort but finally ended in orbit. In that situation, I was never able to get the DAP to go back to OPS 104, it seems to get locked in Aerojet mode trying to get into attitude for the TAL reentry, with the FWD RCS switch-off forever.
If you fly a late TAL, the AP will probably - as you saw - put you on Orbit as you have enough propellant to be past 25kft Vi and in a standard insertion profile.
You can still ( it is what I do) order a manual cutoff when you have the speed to reach the correct TAL site that you choose ( like for a late TAL due to equipment failure for example)
You got the inertial speed there for a 51° orbit launch
Manual MECO before what would have done the AP