No. Every pilot who flew into that airport prior to that accident said the same thing: "this runway configuration is an accident waiting to happen." No one was surprised when it finally did.
Unlike
jhugz, I've actually been to Lexington.
Even post-relocation of the runway, those taxiways leading out to the big runway still do not have great signage. They moved the runway, but they didn't do so hot on the signs. It remains a threat—but one that should have been (could have been, and, by myself and the Captain flying into and out of Lexington, was) mitigated appropriately by cross-checking runway heading against the HSI and your mental model of where the airplane is, using high threat taxi procedures, observing sterile cockpit, and so on.
It's one of those things that falls under "yeah, I can see that happening"—which is why there are now three paragraphs in the SOP about confirming you're entering the right runway, and confirming you're pointing the right way. It's really common sense stuff, but now, it's written.
That, however, is another matter.
Remember, a handful of weeks ago a C-17 landed at a small airport instead of MacDill. These things DO happen on ALL experience levels.
Does not change the fact that someone will at LEAST be getting in trouble for it.
Incidentally, I'm underwhelmed by that incident.
For those wondering if you get fired for this offense: The Colgan Saab Captain who mistakenly landed at the wrong airport enroute to Lake Charles was able to keep his job. He went through a handful of retraining sims. I can't comment on the FO, never met him.
However, I'm not privy to the details of the discussion that may have occurred between ALPA and Colgan. Nor do I know how Silver and the Teamsters may handle the the Fairmont incident.
I'll be curious as to what really happened. If you mess up, you fess up—and if you are honest about it I think you're alright to keep your job. It's not likely that you'll ever do it again after the (you know) storm subsides.