Almost none. An operator can see a cancellation only by obtaining a current answer from the licensing authority, or by querying a status service connected to that authority; a paper or PDF copy of the licence never shows a later status change. According to press reports of a parliamentary answer, Pakistan's government disclosed in late August 2026 that 50 pilot licences had been cancelled and 33 suspended, a cumulative count rather than decisions taken that month. No complete public, real-time register of those individual decisions was identified for this article.

That is the distinction from Project Icarus. Icarus concerns an allegedly forged privilege presented as genuine. The Pakistan disclosure concerns licences whose regulatory status changed after issuance. A document can be authentic, belong to the right person and still be unusable today.

What Pakistan disclosed, and what it did not

On 29 August 2026, ProPakistani and the Pakistan Observer reported the same parliamentary answer. Pakistan's Ministry of Defence had told the National Assembly that 50 licences were cancelled and 33 suspended. The ministry attributed the actions to the Civil Aviation Rules, 1994.

The official National Assembly questions page confirms that a question bundle was published for Friday, 28 August 2026. We downloaded and text-searched that 307-page official bundle on 2 September 2026; it contains no Ministry of Defence answer on pilot licences, so the reported answer was either given orally or published elsewhere. The counts and the reported loss therefore remain press-attributed here. They are not presented as independently recovered from the parliamentary PDF.

That limitation changes the wording. This is not evidence that Pakistan cancelled 50 licences in one week. It is evidence that the ministry disclosed a cumulative enforcement count that week. The available reports do not give the date, factual grounds or appeal status of every individual decision. They also do not publish the affected licence numbers.

The same answer reportedly put PIA's lost revenue at Rs200 billion between August 2020 and December 2024. That is the ministry's estimate, not an audited loss calculation made available with the question bundle. It belongs in the record as an attributed figure, not as a settled financial fact.

One reader named Aam Aadmi captured the reputational reaction under the ProPakistani report on 1 September 2026: "Not just one or two pilots but many." It is a reader's opinion, not evidence about the cases. Its value is that it shows how an administrative status problem becomes a national trust problem once the count reaches the public.

Cancellation and suspension are different states

Pakistan's Civil Aviation Rules, 1994 give the Director-General different powers over personnel licences. Rule 342 allows the Director-General to vary or suspend a licence. It also allows cancellation with federal approval when one of the listed grounds is satisfied. The grounds include non-compliance with aviation law, failure to keep meeting a requirement, misrepresentation, and ceasing to be a fit and proper person.

The process is not a single red button:

  • A suspension under Rule 342 triggers an investigation. It ends when that investigation is completed or after 30 days, whichever comes first, unless the federal government approves an extension.
  • The authority must serve written notice and state the facts or circumstances supporting the action.
  • A holder can appeal a suspension or variation within 14 days of receiving the notice. The rule also sets a 14-day period for the Director-General to hear that appeal.
  • Rule 348 requires an unannulled suspension or cancellation to be endorsed on the licence with its reasons. An expired suspension record may be removed only after at least three years, subject to the Director-General's assessment.

An operator needs more than a yes-or-no authenticity check. It needs a status response with an effective date, a scope, the authority behind it and, where appropriate, an expiry or review date. A temporary suspension must not be presented as permanent cancellation. A cancellation under appeal must not be silently rendered as if no process existed. The operational result may still be "do not assign", but the legal states are not interchangeable.

Rule 210 creates a parallel duty on the operator. A Pakistani Air Operator Certificate holder must record each crew member's licences, ratings, tests, training, proficiency checks and route qualifications. Those records remain throughout employment, then for a further three months. Keeping a record, however, does not by itself make that record current. A photocopy filed at recruitment can satisfy a filing habit while missing a suspension imposed later.

Issued: active Authority record and copy agree Status changes Authority: suspended or cancelled Old copy Still looks active to the naked eye Visual inspection No status signal. The stale copy passes. Result: unknown, not valid. Current authority query Returns status, effective date and issuer. Result: actionable at assignment time.
A status change lives in the authority's record. The old document does not update itself.

What an operator can actually see today

The answer depends on who asks, which State issued the licence and whether the request is connected to an official system. There is no single global public search box for every personnel licence.

The issuing authority can see its own record

The Pakistan Civil Aviation Authority is the authoritative source for a Pakistani licence. An airline employing the pilot should therefore have an authenticated route to confirm the licence number, holder identity, privileges, medical dependencies and current enforcement status. The public material reviewed for this article does not establish a universal PCAA endpoint that foreign operators, lessors or ground teams can query without an account or formal request.

That absence matters at the point of use. A foreign operator receiving a pilot dossier may have a genuine-looking licence, a correct number and a matching identity. Unless it obtains a fresh authority response, it still cannot infer that no suspension was imposed after the copy was made.

ICAO provides an infrastructure, not universal coverage

The International Civil Aviation Organization now permits States to issue an Electronic Personnel Licence, or EPL. ICAO's EPL programme page describes a QR-based automated flow: an inspector scans the code, ICAO routes a query to the licensing authority's server, and the authority returns the required licence data.

ICAO also provides a manual query service for authorized inspectors. It requires registration and asks for the State of issue and licence number. ICAO warns that the result depends on participating States and must not be treated as the sole source for a licensing decision. In other words, the architecture can carry live status, but it is neither an open consumer lookup nor proof that every Pakistani licence is connected today.

Foreign authorities still rely on bilateral verification

The FAA's current foreign licence verification process illustrates the traditional model. For specified US certificate applications, the FAA contacts the foreign civil aviation authority to verify validity and currency. The FAA tells applicants to allow approximately 45 to 90 days. That is an authoritative process for those applications, but it is not a real-time airline roster check.

The delay explains why a stale-copy problem persists even when a formal path exists. A regulator-to-regulator letter is appropriate for certification. It is too slow to be the only control when an operator is assigning crew, onboarding a contractor or responding to an overnight safety notice.

Airline authorisation is not pilot-level status

EASA's Third Country Operator system answers a different question: may this non-EU airline conduct commercial air transport into the European Union? It does not publish the current status of every licence held by that airline's pilots.

The distinction is visible in the record. EASA's current public TCO status report, as retrieved on 2 September 2026, lists PIA under TCO code PAK-0001. That tells a contracting party that the airline appears on EASA's authorized list as of the report date. It does not tell a dispatcher whether a named pilot's individual licence was suspended yesterday.

How one licensing crisis reached an entire airline

The 24 June 2020 statement by Pakistan's federal aviation minister said a significant number of PCAA-issued pilot licences had been obtained fraudulently. The European Commission later recorded that disclosure in recital 49 of Implementing Regulation (EU) 2021/883.

The same official decision connects the disclosure with apparent deficiencies in PCAA safety oversight. EASA then suspended the TCO authorisations of PIA and Vision Air from 1 July 2020. The Commission asked for evidence across more than pilot licensing. It widened its attention to cabin crew certification, maintenance engineer licensing and airline certification. The trust failure propagated from individual records to the authority responsible for the whole system.

The FAA made a separate system-level decision on 15 July 2020. It downgraded Pakistan to Category 2 under the International Aviation Safety Assessment programme. The agency said Pakistan's civil aviation authority did not comply with ICAO safety standards at that time. Category 2 is a judgment about the State's oversight, not a finding that every pilot licence is false.

Recovery also happened at system level. On 29 November 2024, EASA lifted PIA's TCO suspension. The European Commission said PIA and PCAA had made substantial progress in safety performance and oversight capabilities. Its December 2024 regulation records remote checks in personnel licensing, airworthiness, operations, quality management and safety management, then says no significant safety issue was found overall in that review.

That restoration did not erase the original lesson. Aviation journalist Tahir Imran Mian called it "a crucial milestone" in The News on 30 November 2024. The quote is an expert assessment, not proof of compliance. The primary record behind it is the Commission's decision and EASA's authorisation.

What the relying operator can know 1. Visual copy Appearance and printed data Cannot prove current status 2. Employer file Last recorded verification Currency depends on refresh rules 3. Authority response Authoritative status at response time May require access, consent and delay 4. Connected status proof Issuer-authenticated result at scan time Works only when authority and governance connect
A scan is useful only if it reaches a current, authoritative status source.

The operator workflow: verify at the moment of assignment

A quality or flight-operations director should treat licence status as a live dependency, not a recruitment document. The practical control has six stages.

  1. Identify the authoritative issuer. Record the State, authority, licence number and holder identity from the credential. Do not use contact details printed on an unauthenticated copy.
  2. Match privileges to the duty. "Licence active" is insufficient. Confirm the licence class, aircraft rating, instrument privileges, language endorsement, medical dependency and any operational limitation required for the exact assignment.
  3. Request current status through an authenticated channel. Use the authority's portal, an authority-to-authority exchange, an approved EPL query or a verifiable status service controlled by the issuer. Save the response time and source.
  4. Render temporary states accurately. A suspension needs an effective time and, when known, an expiry or review trigger. A cancellation needs the authority decision and any status relevant to appeal. Neither should be compressed into an ambiguous "invalid" label.
  5. Fail closed when the status source is unavailable. An old copy is not evidence of continuing validity. Define who can quarantine an assignment, who contacts the authority and what evidence releases the hold.
  6. Subscribe to change, then re-check at risk points. Recruitment is only the first event. Re-check at renewal, role or aircraft-type change, return from extended leave, safety notice, audit exception and before accepting a subcontracted crew roster.

The evidence retained for audit should be narrow and dated: the credential identifier, the authority queried, the status returned, the verification time, the privilege match and the operator decision. Storing a screenshot of personal data forever is not the objective. Proving which authoritative status informed the assignment is.

What a verifiable status credential changes

A tamper-evident credential solves two separate problems only when both are designed.

The first is document integrity. The issuer records a cryptographic fingerprint of the credential. The operator recomputes that fingerprint from the presented record. A mismatch exposes alteration.

The second is lifecycle status. The issuer publishes an authenticated state change tied to the same credential identifier. The verifier checks that state at the moment of use. The old PDF may still look pristine, but the status response says suspended or cancelled.

That architecture must preserve five properties:

  • Issuer authority. Only the licensing authority, or a tightly governed delegate, may change regulatory status.
  • Freshness. The result shows when it was queried and when the state took effect.
  • State semantics. Active, suspended, cancelled, expired and superseded mean different things. The verifier does not invent equivalence.
  • Privacy. A public proof should not expose a pilot's name, birth date, medical data or employment history. A predictable identifier may still be correlatable even when the document itself is not published.
  • Fallback. When the status network or issuing authority is unavailable, the operator follows a defined authority-confirmation process. It does not convert "unreachable" into "valid".

This is not a blockchain requirement. ICAO's EPL flow can connect directly to a licensing authority server. A signed status list can work. A permissioned registry can work. A public ledger can make revocation evidence independently available. The test is operational: can the relying operator authenticate the issuer, bind the status to the exact credential, know how current the result is and preserve a reviewable receipt?

What the system still cannot prove

Live status is powerful, but bounded.

  • It cannot prove that the person presenting the credential is its holder. Identity matching remains a separate check.
  • It cannot prove current competence, fitness for duty or recent flight experience. Licensing, medical, training and operator authorisation remain different layers.
  • It cannot make an incorrect decision correct. If an authority records the wrong status, the system will faithfully return the wrong status until correction.
  • It cannot resolve an appeal. The system can expose that a decision is under review only if the governing authority defines and publishes that state.
  • It cannot cover a State that does not participate. An empty result outside a connected network proves no regulatory conclusion.

Those limits are why the Pakistan case should not be reduced to "put licences on blockchain". The failure is institutional and operational before it is technical. The status issuer must be legitimate, the relying operator must actually query it, and the response must stop the assignment when required.

AeroCert's take

AeroCert's take: the current AeroCert verification path can distinguish a certificate that is not recorded, a recorded certificate that remains active, and a recorded certificate that has been revoked. The public verifier reads revocation from the registry and can show revocation details when the issuer has published them. That is the status-change property a static PDF lacks.

It would be inaccurate, however, to claim complete pilot-licence lifecycle coverage today. AeroCert does not currently encode suspension as a native on-chain state. Before a pilot-licensing deployment could promise active, suspended and cancelled results, it would need temporary-state semantics, authority governance, privacy-preserving identity binding, appeal handling and an operational fallback to the regulator.

The product lesson is narrower and stronger: a credential verifier must answer "what is its status now?", not only "has this file changed?" The operator lesson is immediate: record the authority response that informed each assignment. See how AeroCert verification works, or review the current status and revocation interfaces on the developer platform.

Sources

Primary and official sources:

Press and commentary, used for context rather than primary proof: