another if-else block? I'm thinking another database table of banned plane-route combinations, if they don't already have it.
And if their plane maintenance is any indication
Delta runs one of the premier maintenance outfits (Delta TechOps) globally. About a quarter of their TechOps business is for outside airlines. So sure if that's any indication their application architecture is probably pretty decent (it's not).This was an ETOPS flight, yeah? Those come with higher standards for crew training, maintenance, and minimum equipment per the FAA. I wouldn't worry until/unless the FAA starts making noise about revoking Delta's ETOPS certification (which would hurt their ability to fly a bunch of routes and their ability to perform maintenance for e.g. Hawaiian).
Such a rules engine is required for day-to-day ops management of a heterogeneous fleet (e.g. "list nearest airplanes to airport X that can fly non-stop for Y nautical miles to airport Z". Or "create flight plans ensuring that each airplane is certified in both departure & arrival countries"). I doubt hard-coding would be required, as such a system is likely flexible