On every job I've worked for Lockheed-Martin, there have been code reviews, and they beat the hell out of you on requirements. Code reviews probably wouldn't have caught this bug however. Depending on humans to catch bugs is futile. A lack of automated testing may be the culprit, especially boundary conditions testing. Or maybe management did something stupid (but typical) like let an EE write code.
Apparently 90% of the avionics code is in Ada. So I bet the problem is either in C/C++ code or else somebody let an IT monkey or EE geek turn off runtime-constraint checking or maybe they did an unchecked conversion.
somebody let an IT monkey I'm betting it's the switch from -180 to +180 Longitude. I've written several moving map programs, and mine don't handle the situation either. They're for land use, so it's overhead I don't need.
(said some stupid stuff above, like reversing longitude with latitude and 190 degrees instead of 180 - yeah, I do this for a living - sheesh)