(DVLA's response might carry the hallmarks of a standard response, perhaps they've responded so often that cut and paste is easier. Typos are likely to occur, as here.)Perhaps, but when you receive a response to an escalated complaint, and the person responding hasn't even checked to make sure they've mentioned the correct parking firm, it doesn't exactly inspire confidence.
As previously advised, UK Car Park Management Ltd is a member of the International Parking Community (IPC).
While I understand your concerns and that you feel that we have not complied with our duties as the data controller, there is no evidence that VCS has breached any statutory provisions or other legal requirement affecting the Keeper At Date Of Event (KADOE) service. Schedule 4 of POFA 2012 could be applicable at the site in question, as the enforcement scheme at Liverpool John Lennon Airport is not operated under airport byelaws.
Subject: Request for ICA Referral – DVLA Step 2 Complaint Not Properly Investigated
Dear DVLA Complaints Team,
I am writing to request that my complaint be referred to the Independent Complaints Assessor (ICA) for independent review, as I am not satisfied that your Step 2 investigation has been conducted properly or in accordance with your obligations as a data controller.
My complaint concerns the unlawful use of my keeper data by Vehicle Control Services Ltd (VCS), who obtained it via the KADOE scheme and then misused it by asserting keeper liability under Schedule 4 of the Protection of Freedoms Act 2012 (PoFA) in circumstances where such liability cannot apply. The location in question—Liverpool John Lennon Airport (LJLA)—is land subject to statutory control under airport byelaws, which excludes it from the scope of PoFA.
Key grounds for ICA referral:• Misrepresentation of my complaint: Your Step 2 response repeatedly refers to “reasonable cause” under Regulation 27, despite my explicit clarification that my complaint was not about the initial data release, but about the subsequent unlawful use of that data in breach of the KADOE contract and data protection law.
• Factual and legal errors: The response incorrectly suggests that PoFA could apply at LJLA, despite the statutory position that land under byelaws is excluded. This demonstrates a fundamental misunderstanding of the law and undermines the credibility of the investigation.
• Copy-paste errors and irrelevant content: The response inexplicably references UK Car Park Management Ltd, a company entirely unrelated to this case. This suggests a lack of care and attention in handling my complaint and raises serious concerns about the integrity of the process.
• Failure to address KADOE compliance: The DVLA has a duty to ensure that data recipients comply with the terms of the KADOE contract. The response fails to engage with this issue or to consider whether VCS’s conduct constitutes a breach of those terms.
Given these serious procedural and substantive failings, I request that the DVLA now refer this matter to the Independent Complaints Assessor in accordance with the Department for Transport’s published complaints procedure.
Please confirm when this referral has been made.
Yours sincerely,
[Your Full Name]
[Your Address or Email]
[DVLA Complaint Reference Number]
I take it you're not a fan of the IAS! Submitted.The IAS upholds 4% of appeals whereas POPLA upholds 40% of appeals, that fact in itself says a lot.
Note their email was titled Prima Facie Case Recieved which isn't a good start and doesn't give you much faith.
1. The whole of LJLA is land that is under statutory control and therefore there can be no Keeper liability. If a supposedly legally qualified IAS assessor cannot understand that, then let the operator litigate the matter and we will see.
2. The signs are prohibitive and cannot form a contract. Again, if the IAS assessor is really legally qualified to solicitor or barrister level, as they claim but do not evidence, then they would understand basic contract law and know that a prohibitive sign cannot form a contract by conduct.
In conclusion, regardless of the operator’s protestations, there is no Keeper liability, and no contract could have been formed with the driver. The operator may squeal all they like about some presumed identity between Keeper and driver, but any legally trained assessor would know such an inference would never hold water in court—particularly in light of VCS v Edward (2023), where this very operator failed spectacularly to prove their case on appeal. Frankly, the appellant has no issue with them trying their luck again in front of an actual judge, should this appeal be dismissed by the supposedly 'independent' IAS and their so-called legally qualified assessors.
I am the registered keeper of the vehicle. I deny any liability for this parking charge and appeal in full.
I repeat from my previous correspondence with the operator that their suggestion that they may continue to pursue the Keeper “on the reasonable assumption that [they] were the driver” is baseless. The operator, VCS, know this. The operator has already lost on this point in their own appellate case Vehicle Control Services Ltd v Ian Mark Edward (2023) [HOKF6C9C], where HHJ Gargan ruled that it is not appropriate to assume the Keeper was the driver on the balance of probability without supporting evidence. The operator cannot rely on PoFA to transfer liability, nor can they rely on unsupported inference.
The operator then makes the absurd claim that the byelaws are “not currently in use”. This is legally meaningless. Byelaws do not simply fall into disuse or expire by neglect — they remain in force unless and until they are formally repealed or replaced by statute. Unless the operator can produce definitive proof that the LJLA byelaws have been lawfully rescinded, they remain in effect and the land remains under statutory control. That alone disqualifies it as “relevant land” for the purposes of Schedule 4 of the Protection of Freedoms Act 2012. The operator’s assertion is just another example of the misinformation routinely used to support this long-running scam.
I challenge a supposedly legally trained IAS assessor to explain how a sign that ONLY states the following can form a contract:"No Stopping. £100 charge if you stop. Traffic compliance cameras. Private Property. Vehicle Keeper details may be requested from the DVLA. Vehicle Control Services Ltd manage and control this site"
The operator claims their signs create a contractual obligation, but as they well know, and so should any legally trained assessor, the signage does not offer any terms to accept — it is prohibitory in nature. The sign threatens a charge for an act that is forbidden. A contract cannot be formed where the only “offer” is a prohibition, especially when there is no benefit or consideration. This type of sign has been found incapable of forming a contract in multiple persuasive court decisions.
Finally, the operators reference to “continuing to pursue” the Keeper without identifying the driver only further supports my existing complaints to the DVLA and ICO concerning their unlawful misuse of DVLA Keeper data, contrary to the KADOE contract, the BPA/IPC Private Parking Single Code of Practice (PPSCoP), and UK GDPR Article 5 principles.
The operators threat of continued pursuit — despite their admitted lack of evidence and absence of any statutory Keeper liability — is entirely unjustified and amounts to vexatious conduct.
The parking operator bears the burden of proof. It must establish that a contravention occurred, that a valid contract was formed between the operator and the driver, and that it has lawful authority to operate and issue Parking Charge Notices (PCNs) in its own name. I therefore require the operator to provide the following:1. Strict proof of clear, prominent, and adequate signage that was in place on the date in question, at the exact location of the alleged contravention. This must include a detailed site plan showing the placement of each sign and legible images of the signs in situ. The operator must demonstrate that signage was visible, legible, and compliant with the IPC Code of Practice that was valid at the time of the alleged contravention, including requirements relating to font size, positioning, and the communication of key terms.
2. Strict proof of a valid, contemporaneous contract or lease flowing from the landowner that authorises the operator to manage parking, issue PCNs, and pursue legal action in its own name. I refer the operator and the IAS assessor to Section 14 of the PPSCoP (Relationship with Landowner), which clearly sets out mandatory minimum requirements that must be evidenced before any parking charge may be issued on controlled land.
In particular, Section 14.1(a)–(j) requires the operator to have in place written confirmation from the landowner which includes:• the identity of the landowner,
• a boundary map of the land to be managed,
• applicable byelaws,
• the duration and scope of authority granted,
• detailed parking terms and conditions including any specific permissions or exemptions,
• the means of issuing PCNs,
• responsibility for obtaining planning and advertising consents,
• and the operator’s obligations and appeal procedure under the Code.
These requirements are not optional. They are a condition precedent to issuing a PCN and bringing any associated action. Accordingly, I put the operator to strict proof of compliance with the entirety of Section 14 of the PPSCoP. Any document that contains redactions must not obscure the above conditions. The document must also be dated and signed by identifiable persons, with evidence of their authority to act on behalf of the parties to the agreement. The operator must provide an agreement showing clear authorisation from the landowner for this specific site.
3. Strict proof that the enforcement mechanism (e.g. ANPR or manual patrol) is reliable, synchronised, maintained, and calibrated regularly. The operator must prove the vehicle was present for the full duration alleged and not simply momentarily on site, potentially within a permitted consideration or grace period as defined by the PPSCoP.
4. Strict proof that the Notice to Keeper complies with the Protection of Freedoms Act 2012 (PoFA), if the operator is attempting to rely on Keeper liability. Any failure to comply with the mandatory wording or timelines in Schedule 4 of PoFA renders keeper liability unenforceable.
5. The IAS claims that its assessors are “qualified solicitors or barristers.” Yet there is no way to verify this. Decisions are unsigned, anonymised, and unpublished. There is no transparency, no register of assessors, and no way for a motorist to assess the legal credibility of the individual supposedly adjudicating their appeal. If the person reading this really is legally qualified, they will know that without strict proof of landowner authority (VCS v HMRC [2013] EWCA Civ 186), no claim can succeed. They will also know that clear and prominent signage is a prerequisite for contract formation (ParkingEye v Beavis [2015] UKSC 67), and that keeper liability under PoFA is only available where strict statutory conditions are met.
If the assessor chooses to overlook these legal requirements and accept vague assertions or redacted documents from the operator, that will speak for itself—and lend further weight to the growing concern that this appeals service is neither independent nor genuinely legally qualified.
In short, I dispute this charge in its entirety and require full evidence of compliance with the law, industry codes of practice, and basic contractual principles.
Formal Appeal to Vehicle Control Services Ltd
PCN Ref: VCS23023633
Vehicle Reg: HG65 VMX
Site: Liverpool John Lennon Airport
Date of Issue: 8 May 2025
This is submitted in response to Point 2 of your letter dated 4 June 2025. To be clear, my original appeal still stands in full and is reiterated below with an additional clarification.
I am the registered keeper. VCS cannot hold a registered keeper liable for any alleged contravention on land that is under statutory control. As a matter of fact and law, VCS will be well aware that you cannot use the PoFA provisions because Liverpool John Lennon Airport (LJLA) is not “relevant land” under Schedule 4 of the Protection of Freedoms Act 2012.
If LJLA wished to enforce against keepers under Airport Bylaws, that would be within the landowner’s statutory remit. However, not only is that not pleaded here, it is also not legally viable: VCS is not the Airport authority, and your so-called “charge” is neither a penalty nor a statutory enforcement measure. It is plainly a contractual invoice pursued for your own commercial gain, not for the public purse.
Your Notice to Keeper cannot transfer liability to the registered keeper. It does not (and cannot) rely on PoFA, and your attempt to imply that the Keeper is liable by stating that you “may pursue [the Keeper] on the assumption [they] were the driver” is legally embarrassing and nonsensical.
Let me spell this out: The registered keeper cannot be presumed or inferred to have been the driver, nor pursued under some desperate distortion of agency law. If there is no evidence of who was driving, your claim ends there.
If you have forgotten, may I politely remind you that your company lost this argument spectacularly in your own case:
VCS v Ian Mark Edward (2023) [OKF6C9C] (https://www.dropbox.com/scl/fi/zra61px7l3if53o3bp9c4/VCS-v-EDWARD-Transcript.pdf?rlkey=bv4bba389nau5qpfglqkpjq5l&st=7pj9cgb1&dl=0) — where HHJ Gargan confirmed that there is no legal or evidential basis to assume the Keeper was the driver. The judgment even laid out common examples where such an inference is clearly invalid. That ruling leaves no room for your tired fiction that Keeper = driver.
So, do not insult my intelligence or waste my time with more of the same template replies.
If you intend to pursue this charge without identifying the driver, and in full knowledge that your case cannot survive judicial scrutiny, then I can only refer you to the well-established position in Arkell v Pressdram (1971).
Yours faithfully,
[Your Name]
Registered Keeper
I am escalating my complaint to Step 2, having received a wholly inadequate and dismissive response from Carly Williams (Ref: 0405058). Ms Williams’ reply fails to address the core of my complaint, which concerns the misuse of DVLA Keeper data after it was disclosed to Vehicle Control Services Ltd (VCS), a private parking company operating at Liverpool John Lennon Airport.
The DVLA has a legal obligation to ensure that data released under the KADOE contract is used lawfully and in compliance with the relevant Code of Practice. While the Step 1 response focuses entirely on the original request (reasonable cause), it ignores the key issue of how VCS subsequently misused the data in breach of the KADOE contract and UK GDPR.
I attach a detailed supporting statement explaining exactly how the data was used unlawfully by VCS, including evidence that they issued a Notice to Keeper falsely implying that the Keeper could be pursued under the Protection of Freedoms Act 2012—despite the land being excluded from that Act. This is a textbook case of unlawful post-access use and misrepresentation, which DVLA remains jointly responsible for as data controller at the point of disclosure.
Please confirm escalation of my complaint and provide a reference number.
SUPPORTING STATEMENT
Step 2 Complaint to DVLA – Misuse of Keeper Data by Vehicle Control Services Ltd (VCS)
Operator name: Vehicle Control Services Ltd
Date of PCN issue: 8 May 2025
Vehicle registration: [INSERT VRM]
DVLA Ref: 0405058
Step 1 responder: Carly Williams, Data Customer Auditor
I am escalating this complaint to Step 2 because the Step 1 response from Carly Williams demonstrates a fundamental failure to understand the nature of my complaint, the legal duties of the DVLA, and the conditions of data release under the KADOE contract.
1. Misunderstanding of the Complaint
The Step 1 reply wrongly treats this as a challenge to the initial release of data based on "reasonable cause." That is not the basis of this complaint. As I made clear, my concern is the subsequent unlawful use of DVLA-supplied Keeper data after disclosure, in breach of the:• KADOE contract,
• Private Parking Single Code of Practice (PPSCoP), and
• UK GDPR.
The DVLA, as data controller at the point of release, has a duty to ensure that data is only used for the limited purpose for which it was disclosed: the fair and lawful pursuit of a parking charge under the Code of Practice. Once an operator breaches the Code post-access, the continued use of that data becomes unlawful. That is the crux of this complaint, and it was entirely ignored by Ms Williams.
2. Misstatement of Data Controller Responsibility
Ms Williams claimed that once DVLA has released data, the private parking operator becomes the Data Controller. While operators do become independent controllers, the DVLA retains responsibility as the original controller and data provider under the Data Protection Act 2018 and UK GDPR. The DVLA is responsible for ensuring that personal data is not misused as a direct result of its own disclosures.
This position is well established in ICO guidance and reflects the DVLA’s ongoing obligation to enforce the KADOE contract and suspend access where misuse is identified.
3. Breach of KADOE and PPSCoP by VCS
VCS has misused the data by issuing a Notice to Keeper which falsely implies that they can hold the Keeper liable under Schedule 4 of PoFA 2012, despite the location (Liverpool John Lennon Airport) not being “relevant land” for the purposes of that Act.
Specifically, the Notice states:“If... we do not know both the name of the driver and a current address for service for the driver, we may pursue you (the Keeper) on the assumption you were the driver.”
This copies the language of PoFA 9(2)(f) and is intended to mislead the Keeper into believing they can be held liable. This is legally false and in direct breach of the PPSCoP (Section 3.3), which requires operators to act fairly, professionally, and transparently. It is also a breach of the purpose limitation and lawfulness principles under UK GDPR.
4. VCS Has Already Lost on This Point in Court
In the appellate case VCS v Ian Mark Edward [2023] (HOKF6C9C), HHJ Gargan ruled unequivocally at paragraph 5.3 that it is not appropriate to assume the Keeper is the driver without evidence. The judge explained that the assumption is unsound and that there are many common situations where the Keeper is not the driver. The continued use of this tactic by VCS demonstrates a deliberate and knowing misuse of personal data.
5. VCS Are Not a Statutory Authority
It must be stressed that VCS is a private, unregulated parking company with no statutory powers. They cannot issue fines or penalties. The charge is framed to appear like a penalty, when in fact it is nothing more than a speculative invoice, with no lawful basis in contract or statute. This misrepresentation, when linked to DVLA-supplied data, further compounds the breach.
Conclusion and Request
The Step 1 response shows a serious failure to understand:• The DVLA's continuing data controller obligations,
• The difference between lawful access and unlawful post-access use,
• The KADOE requirement to act in accordance with the PPSCoP,
• And the legal limits on private companies misusing Keeper data under false pretences.
I am therefore requesting that this complaint be fully reviewed by the Head of Complaints and not simply passed back to the same department. The DVLA cannot lawfully continue to allow private companies to obtain data on a “reasonable cause” basis and then wash its hands of how that data is used—especially when the use breaches both contractual and legal safeguards.
Please confirm the escalation and provide a complaint reference number for Step 2. I am willing to provide any further material required.
Name: [INSERT NAME]
Date: [INSERT DATE]
I am the registered keeper. VCS cannot hold a registered keeper liable for any alleged contravention on land that is under statutory control. As a matter of fact and law, VCS will be well aware that they cannot use the PoFA provisions because Liverpool John Lennon Airport (LJLA) is not 'relevant land'.
If LJLA wanted to hold owners or keepers liable under Airport Bylaws, that would be within the landowner's gift and another matter entirely. However, not only is that not pleaded, it is also not legally possible because VCS is not the Airport owner and your 'parking charge' is not and never attempts to be a penalty. It is created for VCS's own profit (as opposed to a bylaws penalty that goes to the public purse) and VCS has relied on contract law allegations of breach against the driver only.
The registered keeper cannot be presumed or inferred to have been the driver, nor pursued under some twisted interpretation of the law of agency. Your NtK can only hold the driver liable. VCS have no hope should you try to litigate, so you are urged to save us both a complete waste of time and cancel the PCN.
I am submitting a formal complaint against Vehicle Control Services Ltd (VCS), an IPC AOS member with DVLA KADOE access, for breaching the Private Parking Single Code of Practice (PPSCoP) after obtaining my personal data.
While the Operator may have had reasonable cause at the time of their KADOE request, their subsequent misuse of my data—through conduct that contravenes the PPSCoP—renders that use unlawful. The PPSCoP forms an integral part of the DVLA’s governance framework for data access by private parking firms. Continued access is conditional on compliance.
The DVLA, as data controller, is obliged under UK GDPR and the Data Protection Act 2018 to investigate and take enforcement action when data is misused following release. This complaint is not about whether the data was obtained lawfully at the outset, but whether its subsequent use breached the terms under which it was provided.
I have prepared a supporting statement setting out the nature of the breach and the Operator’s actions, and I request a full investigation into this matter. I have attached the supporting document.
Please acknowledge receipt and confirm the reference number for this complaint.
SUPPORTING STATEMENT
Complaint to DVLA – Breach of KADOE Contract and PPSCoP
Operator name: Vehicle Control Services Ltd (VCS)
Date of PCN issue: 8 May 2025
Vehicle registration: [INSERT VRM]
I am submitting this complaint to report a misuse of my personal data by Vehicle Control Services Ltd (VCS), who obtained my keeper details from the DVLA under the KADOE (Keeper At Date Of Event) contract.
Although VCS may have had reasonable cause to request my data initially, the way they have used that data afterwards amounts to unlawful processing. This is because they have acted in breach of the Private Parking Single Code of Practice (PPSCoP), which is a mandatory requirement for access to DVLA keeper data. The PPSCoP forms part of the framework that regulates how parking companies must behave once they have received keeper data from the DVLA.
The KADOE contract makes clear that keeper data may only be used to pursue an unpaid parking charge in line with the Code of Practice. If a parking company fails to comply with the PPSCoP after receiving DVLA data, their use of that data becomes unlawful, as they are no longer using it for a permitted purpose.
In this case, VCS has breached the PPSCoP and misused the Keeper’s data in the following ways:• The signage relied on at Liverpool John Lennon Airport is incapable of forming a contract. It clearly prohibits stopping and threatens a £100 charge for doing so. This is not an invitation to treat or an offer of terms that can be accepted by conduct. There is no consideration or benefit offered to the driver, which is a fundamental requirement for a binding contract. Therefore, the signage cannot form a lawful contract, and the £100 charge is not a contractual fee but an unenforceable deterrent. A charge issued under these circumstances has no lawful basis.
• The land is under statutory control via airport byelaws, meaning it is not classified as “relevant land” for the purposes of Schedule 4 of the Protection of Freedoms Act 2012 (PoFA). Because of this, the provisions in PoFA that allow a parking operator to pursue the registered Keeper in the absence of driver details do not apply on this site. This is a settled point in parking law, and VCS knows or ought to know that PoFA cannot be invoked in these circumstances.
• Despite PoFA not applying, VCS has deliberately copied wording from Paragraph 9(2)(f) of Schedule 4 of PoFA into the Notice to Keeper. The notice states: “we may pursue you (the Keeper) on the assumption you were the driver.” This is a direct mimicry of PoFA’s statutory language and is used deceptively to suggest that the Keeper can be held liable even when the legal basis to do so does not exist. This is both misleading and unfair, and in direct breach of the requirement under Section 3.3 of the PPSCoP to act “professionally, fairly and transparently.”
• The conduct of VCS in relying on such language has already been criticised in court. In the persuasive County Court appeal case VCS v Ian Mark Edwards [2023] HOKF6C9C, HHJ Gargan made clear in his conclusion at paragraph 35.3 that:“It is not appropriate to draw an inference that, on balance of probability, the registered keeper was driving on any given occasion.”
The judge offered several examples of common scenarios (e.g. company cars, shared family vehicles) to show that assuming the Keeper was also the driver is speculative and unsupported. This is directly relevant, and VCS’s continued use of that assumption—despite this ruling—shows a wilful disregard for the law and judicial guidance.
• VCS is a private company with no statutory or lawful authority to issue penalties for stopping. They are not a public authority, and cannot lawfully impose or enforce fines. The £100 demand is therefore not a penalty lawfully issued under any statutory enforcement power, but rather a speculative invoice dressed up in intimidating language. This is especially concerning given VCS’s background as a former clamping company, a practice now banned in England and Wales under the Protection of Freedoms Act. Their current business model is essentially a continuation of the same coercive tactics, but now using CCTV and misleading notices.
• This behaviour is consistent with what many consider to be vexatious conduct, designed not to recover genuine losses, but to pressure registered Keepers into payment through legally questionable means. It is also arguably in breach of the UK GDPR principles of fairness and purpose limitation, as the DVLA-supplied data is being used in a way that is not compatible with its stated purpose: namely, to pursue a lawful charge in accordance with the relevant Code of Practice.
These actions represent serious, systemic breaches of the PPSCoP and undermine the lawful basis on which VCS was permitted to access and use DVLA Keeper data. They are not minor technical issues but deliberate and recurring tactics used by an unregulated private operator with a track record of aggressive enforcement and disregard for due process.
The DVLA remains the Data Controller for the data it releases under KADOE, and is therefore responsible for ensuring that personal data is not misused by third parties. This includes taking action against AOS operators who breach the conditions under which the data was provided. I am therefore asking the DVLA to investigate this breach and to take appropriate action under the terms of the KADOE contract.
This may include:
• Confirming that a breach has occurred
• Taking enforcement action against the operator
• Suspending or terminating their KADOE access if warranted
I have attached relevant supporting material with this statement. Please confirm receipt and provide a reference for this complaint. I am also happy to provide further information if required.
Name: [INSERT YOUR NAME]
Date: [INSERT DATE]
VCS Limited v Ian Mark Edward (2023) [H0KF6C9C] (https://www.dropbox.com/scl/fi/zra61px7l3if53o3bp9c4/VCS-v-EDWARD-Transcript.pdf?rlkey=bv4bba389nau5qpfglqkpjq5l&st=hmsa1hs4&dl=0)VCS Limited... sounds familiar!
Important Note: If, after the period of 28 days beginning with the day after the Issue Date of this Notice, the amount of the unpaid Charge specified in this Notice has not been paid in full and we do not know both the name of the driver and a current address for service for the driver, we may pursue you (the Keeper) on the assumption you were the driver, for any unpaid balance of the Charge.
35.3. it is consistent with the appropriate probability analysis whereby simply because somebody is a registered keeper, it does not mean on balance of probability they were driving on this occasion, because one simply cannot tell. For example, there will be companies who are registered keepers of vehicles where many drivers have the use of the vehicle from time to time. There will be individual employers are the registered keeper but who allow a number of people who may drive their vehicles. There may be situations where husband and wife are each registered keepers of their respective vehicles but for some reason drive the other. Or there may be situations where husband/wife is the registered keeper of both family cars and the registered keeper regularly drives one car and their spouse regularly drives the other. These are all possibilities which show that it is not appropriate to draw an inference that, on balance of probability, the registered keeper was driving on any given occasion.
The charge has been incurred for the reason stated and liability brought to the attention of the driver by the Terms and Conditions displayed on signage placed at the entrance to the controlled area (site) and in prominent places throughout.
I am the registered keeper. VCS cannot hold a registered keeper liable for any alleged contravention on land that is under statutory control. As a matter of fact and law, VCS will be well aware that they cannot use the PoFA provisions because Liverpool John Lennon Airport (LJLA) is not 'relevant land'.
If LJLA wanted to hold owners or keepers liable under Airport Bylaws, that would be within the landowner's gift and another matter entirely. However, not only is that not pleaded, it is also not legally possible because VCS is not the Airport owner and your 'parking charge' is not and never attempts to be a penalty. It is created for VCS's own profit (as opposed to a bylaws penalty that goes to the public purse) and VCS has relied on contract law allegations of breach against the driver only.
The registered keeper cannot be presumed or inferred to have been the driver, nor pursued under some twisted interpretation of the law of agency. Your NtK can only hold the driver liable. VCS have no hope should you try to litigate, so you are urged to save us both a complete waste of time and cancel the PCN.