I'm not entirely sure, it was something to do with the conditions for how the "landing" state was being set. The bug ended up disappearing when I was fixing something else entirely at around that part of the code, so now I may never truly know
sometimes it just be that way....the badly timed aerial too close to the ground makes the most sense for me though.
