@Cik:
alright. you say you can halt INS align before it’s at 8.0/10 and still be ok? what’s the cutoff and is the extra drift modeled? (does it get less accurate the less you align?) i’m kind of curious because it would be nice to have the escorts take off first, and if they don’t need a perfect align that would solve the “escorts on top of everyone else” problem. can you elaborate?
thanks. i think understand now; i’d never used the flightplan button up until i just noticed it, heh. guess i never needed it. i think it’s workable now; i just have to get decent at setting up the mess that is multi-package ops. wish me luck.
Yes the drift is modeled but you normally have to disable GPS to see it. The INS alignment goes through several phases. Without too much detail the minimum flyable nav state is ready at ~90 seconds at align status code 70. Between 90-480 seconds the alignment improves. The “0.8” of the readout refers to “0.8nm per hour of drift.” The other number is the status code which starts at 99 and counts downward as the alignment continues. The “10” code represents 1X normal error CEP. In BMS it’s possible to align down to code 8 (80% NCEP) and in real life down to code 6 (60% CEP).
I don’t think it’s possible to schedule T/O times closer than 60 sec apart for an airbase. That might not restrict you from editing the steer 1 times after creation though.