To help troubleshoot, please run 2022.013 with ac_ai logging turned on. If the troublesome code is triggered, you will get an assertion error. At that point, grab your ge.log, zip and upload it for analysis (a saved game from that game second or the one before would help too).
Example command line (activates ac_ai supplemental logging to ge.log and autosaves every game second rolling over after 255 saves): Winharp32.exe -l ac_ai -S000010255
The log entries of interest will look something like:
100232 Combat5.c:1580 - G TCR:AirAttacker: BOm.. AirTargetType =
100232 Combat5.c:1602 - G BOm:target_type = 109, range=1325, bearing=208
100232 Combat5.c:1658 - WR.attack_type=6, auto_flag=1
100232 Combat5.c:1696 - after case, gflag=0, wrange=0, WR.weapon_range=0, attack type (type_aa)=4