The officer report for the most recent decision is available on the public access site. I would describe it as very technical and also very tetchy. The technical arguments are:
- the council argues that the condition applies every night and so the because the airport can’t demonstrate it has been broken every night, there has not been a continuous breach
- Similar to that, there is a technical argument that there were long gaps between individual events. Up to 300 days between a QC1 movement at night and the next one. The argument here seems to be that due to the infrequent occurrences, the council couldn't possibly enforce the condition.
- There is a debate over a Hercules departure in 2012, which the airport claim is QC1 and the Council can't find evidence to prove it is (because their usual sources for civilian aircraft doesn't include it, naturally). As the Herc was the only claimed QC1 departure in 2012, then if proven not to be Qc1, then it breaks the 10 year chain, even if the council lose the argument on the other points.
The tetchy points are various points relating to "if this goes to appeal, we will raise these points.....". These seem to mainly relate to the quality and consistency of reporting between 2008 and 2014 when movements reported as QC 0.5 back then, have been classified as Qc 1.0 in the CLUED application.
It all seems a complete mess tbh. It's obvious the council are determined not to approve these. An appeal will drag it out for months, if not longer. All the while, they could just sit down and draw up what a new set of rules should look like for the 21st century with a quota system that actually incentivises and favours Qc 0.25 movements and put this through planning.
- the council argues that the condition applies every night and so the because the airport can’t demonstrate it has been broken every night, there has not been a continuous breach
- Similar to that, there is a technical argument that there were long gaps between individual events. Up to 300 days between a QC1 movement at night and the next one. The argument here seems to be that due to the infrequent occurrences, the council couldn't possibly enforce the condition.
- There is a debate over a Hercules departure in 2012, which the airport claim is QC1 and the Council can't find evidence to prove it is (because their usual sources for civilian aircraft doesn't include it, naturally). As the Herc was the only claimed QC1 departure in 2012, then if proven not to be Qc1, then it breaks the 10 year chain, even if the council lose the argument on the other points.
The tetchy points are various points relating to "if this goes to appeal, we will raise these points.....". These seem to mainly relate to the quality and consistency of reporting between 2008 and 2014 when movements reported as QC 0.5 back then, have been classified as Qc 1.0 in the CLUED application.
It all seems a complete mess tbh. It's obvious the council are determined not to approve these. An appeal will drag it out for months, if not longer. All the while, they could just sit down and draw up what a new set of rules should look like for the 21st century with a quota system that actually incentivises and favours Qc 0.25 movements and put this through planning.
Last edited: