Well,
Wageslave has already identified the
sole cause of this incident. Why bother even having an investigation?
Holes require errors elsewhere and I don't see "errors" in the info given elsewhere.
An ATIS not being available to the crew is a latent error; a hole in the cheese. Poor communication by ATC is a latent error; another hole. Poorly written/ overly verbose NOTAMs are latent errors; another hole. There's three potential "holes" not related to the crew, without going into any sort of depth whatsoever.
Of course there will be factors that led the crew into this event but we are very familiar with all of them and therefore should routinely ensure that we do not fall foul of any of them
Nobody (intentional acts of destruction aside) sets out routinely to cause an incident or accident. Your comment quoted above is therefore nonsense. Of course we should be (and are) familiar with factors introducing threats into the operation, and of course we routinely do everything we can (TEM, good CRM practice) to avoid falling foul of them. Yet, with all that in mind, incidents and accidents still happen. Taking the absurdly simplistic approach that there's only one cause of any accident or incident flies in the face of years of accepted investigative practice.