An ICO Decision Notice should clarify the public record. Where a notice appears to contain a material factual error about a company’s trading history, the issue is no longer technical: it becomes a test of whether the regulator can correct itself when accuracy matters.
Publication snapshot
- The article examines concerns about factual accuracy in an ICO Decision Notice concerning Monarch Aircraft Engineering Ltd.
- It focuses on the disputed assertion that MAEL ceased trading on 2 October 2017, when public company records and the draft narrative point to later activity and administration in January 2019.
- It raises questions about PSC compliance, Companies House records, CAA/ATOL involvement and whether public regulators correct material errors quickly enough.
- It argues for a clear correction mechanism where a Decision Notice contains factual inaccuracies with legal or public-record consequences.
The disputed decision notice
The Information Commissioner’s Office is supposed to be one of the final safeguards for transparency and accountability in public administration. A Decision Notice should resolve an information-rights dispute by applying the law to an accurate factual record.
The concern raised here is that Decision Notice IC-340043-X2N8, concerning a Freedom of Information request about Monarch Aircraft Engineering Ltd, appears to rely on a materially disputed account of MAEL’s trading history. The draft says the notice asserts that MAEL ceased trading on 2 October 2017.
That date is challenged as wrong. The case advanced is that MAEL continued operating beyond October 2017, including through later business activity, before entering administration on 4 January 2019. If that is correct, the error is not cosmetic. It affects the chronology against which regulatory awareness, corporate governance, PSC records and possible oversight failures are assessed.
Why the MAEL timeline matters
Company chronology matters because legal and regulatory duties attach to real events: trading activity, administration, ownership, control, filings, insolvency steps and regulator knowledge. If a public body records the wrong date for a company’s cessation or operational status, it may distort the analysis that follows.
The date reportedly used in the ICO notice as the point at which MAEL ceased trading.
The draft narrative says MAEL continued operating and that relevant corporate and regulatory issues continued beyond the 2017 date.
The draft identifies this as a key date after which no PSC was listed, raising a separate corporate-transparency issue.
The date the draft identifies as MAEL’s administration date, requiring direct verification against Companies House records before publication.
The public-interest concern is straightforward. If MAEL did not cease trading when the ICO notice suggests, the notice may present an inaccurate picture of the company’s financial and operational history. That, in turn, could affect how later readers understand oversight by regulators, shareholders, creditors and public bodies.
The missing PSC issue
The draft raises a second issue: the alleged absence of a Person with Significant Control entry after 24 October 2018. PSC records are not administrative decoration. They are part of the transparency framework through which control of companies is identified and made visible.
The legal significance of the point depends on the company’s status, ownership structure, applicable exemptions, filings at the relevant time and any lawful explanation for the register position. But if there was a reportable PSC gap, the matter is potentially significant because PSC non-compliance can carry legal consequences.
PSC questions that need checking
- What PSC entries appeared on the Companies House register before and after 24 October 2018?
- Was MAEL required to maintain or update PSC information at the relevant time?
- Were any exemptions, corporate control structures or nominee arrangements relevant?
- Was Companies House notified of any change in control?
- Did any public authority, regulator or shareholder know of the alleged gap?
- Was the PSC issue placed before the ICO, and if so, how was it addressed?
The strongest formulation is not that the ICO has already concealed a criminal offence. It is that a decision notice dealing with MAEL should not ignore a legally significant company-record issue if that issue was material to the FOI request and the public-interest context.
A watchdog that will not correct itself?
The draft says that when the alleged error was raised, the response was that the ICO could not amend the Decision Notice once issued and that any challenge must proceed through the appeal route. If accurately described, that position creates an obvious credibility problem.
Regulatory finality has value. Decision notices cannot be endlessly rewritten every time a disappointed requester disagrees. But there is a difference between disagreement and a material factual error. A regulator committed to public-record integrity should have a transparent route for correction where an error is clear, evidenced and capable of misleading future readers.
Finality
Decision notices need legal stability. Public authorities and requesters must know when a dispute has been decided and what appeal route applies.
Accuracy
Finality should not require a public regulator to leave material factual inaccuracies uncorrected where the record can be verified.
The concern is not only this individual notice. If the ICO cannot correct a material factual error without forcing an appeal, the system risks preserving misinformation under the language of procedural certainty.
CAA, ATOL and oversight questions
The draft also raises concerns about the Civil Aviation Authority, the ATOL scheme and MAEL’s financial affairs. It argues that CAA or ATOL-linked involvement may have created oversight or conflict-of-interest questions that should have been addressed more openly.
Those points require careful verification. The relevant questions are not merely whether a public aviation body had some connection with MAEL, but what that connection was, when it arose, what rights or responsibilities it carried, and whether it should have affected the ICO’s analysis of the FOI request.
Oversight questions
- What was the precise CAA or ATOL-linked relationship with MAEL?
- Was there a shareholding, trustee arrangement, creditor interest or other control mechanism?
- Did that relationship create any conflict-of-interest or oversight concern?
- Was the relationship disclosed in relevant filings or correspondence?
- Was the issue raised in the FOI request or submissions to the ICO?
If the ICO notice omitted a material oversight issue, the omission matters because FOI decisions are often read beyond the immediate parties. They become part of the official record.
An appeals process that shifts the burden
The ICO’s reported position is that the route to challenge the notice is appeal. That may be procedurally correct in many cases, but it does not answer the underlying concern: why should the burden of correcting a regulator’s factual error fall entirely on the individual who identified it?
An appeal can be slow, technical and resource-intensive. By the time the issue is resolved, the Decision Notice may already have influenced public understanding, related correspondence or legal argument. Where the point is a narrow factual correction, a full appeal may be a disproportionate remedy.
Appeal
A formal route may be necessary where the legal outcome is disputed or the alleged error affects the decision itself.
Correction note
A public correction mechanism could address verified factual errors without reopening every legal issue.
Audit trail
The original notice could remain available with a transparent correction note explaining what changed and why.
A correction mechanism is needed
This case exposes a practical weakness in information-rights administration. A regulator that publishes legal decisions should also maintain a credible route for correcting material factual inaccuracies in those decisions.
1. Create a correction protocol
The ICO should publish a clear process for handling alleged factual errors in issued Decision Notices.
2. Separate legal appeal from factual correction
Not every correction request should require a full appeal where the issue is narrow, objective and verifiable.
3. Preserve the audit trail
Where a notice is corrected, the public record should show the original wording, the correction and the basis for the change.
4. Escalate legally significant errors
Where an error may affect court proceedings, corporate compliance or possible offences, it should receive senior review.
Transparency cannot operate only outwardly. A regulator that demands accuracy from public authorities must also demonstrate accuracy in its own records.
Closing point
The ICO now faces a simple accountability test. If the Decision Notice is accurate, the record should show why. If it contains a material error, the public should not be told that the only remedy is a slow appeal process.
Decision Notices matter because people rely on them. Courts, journalists, campaigners, requesters and public authorities all read them as official statements of fact and law. That status carries responsibility.
The watchdog’s credibility depends not on never making mistakes, but on correcting them when they are shown.
Disclaimer
This article is general public-interest commentary and does not constitute legal advice. It is based on concerns raised about ICO Decision Notice IC-340043-X2N8 and should be checked against the notice, Companies House records, CAA/ATOL materials, appeal documents, corporate filings and any official ICO response before publication. FOI, company law, PSC compliance, regulatory accountability, public-law and defamation issues are fact-sensitive, and affected parties should seek advice from a suitably qualified solicitor or regulated adviser.

