{
 "slug": "qualification-event-receipt",
 "topic_id": "TOPIC-140",
 "cluster": "Aviation, MRO & Aerospace Airworthiness Identity",
 "tier": "Tier B",
 "title": "Pilot qualification records: the training entry that makes a crew legal",
 "summary": "Crew legality depends on recency, checkrides and line checks. Each is a row created by a training system, approved by an instructor's login, and rarely questioned until an accident makes it central.",
 "lede": "A crew is legal because a database says so. Recency current, checkride passed, line check complete, type qualified. Each of those facts is a row, entered by a scheduler or an instructor, approved under a login, and trusted absolutely by every system downstream.",
 "date": "2023-11-06",
 "category": "Vertical",
 "author_id": "nadia-ferreira-strand",
 "tags": [
  "pilot training records",
  "crew qualification",
  "Part 121",
  "licence fraud",
  "instructor approval",
  "flight operations"
 ],
 "image_title": "Qualification Event Receipt",
 "schema": "Article",
 "key_takeaways": [
  "Training management systems are built for scheduling and compliance reporting. Instructor approval is a login-bound action, often applied in batch after a session.",
  "The measurable signal is the delay between the training event and the approval. It is exportable and almost never examined.",
  "A dual-signed qualification receipt makes the record portable across employers — which benefits the crew member as much as the operator."
 ],
 "body": [
  {
   "type": "h2",
   "text": "Prerequisites"
  },
  {
   "type": "diagram",
   "kind": "flow",
   "alt": "From training event to flight legality",
   "caption": "Four steps, and the evidence at the end is a row an account created.",
   "nodes": [
    {
     "label": "Training event occurs",
     "note": "simulator or line"
    },
    {
     "label": "Instructor records it",
     "note": "login to the training system",
     "bad": true
    },
    {
     "label": "Qualification status updates",
     "note": "derived field"
    },
    {
     "label": "Crew rostered as legal",
     "note": "on the strength of that row",
     "bad": true
    }
   ]
  },
  {
   "type": "ul",
   "items": [
    "Export access to your training management system: event records, instructor approvals, timestamps.",
    "A list of the qualification events that gate legality — not every training item, only those a scheduler checks before assigning a crew.",
    "Your current instructor delegation policy, including what administrative staff may enter on an instructor's behalf."
   ]
  },
  {
   "type": "h2",
   "text": "Step 1 — Identify the gating events"
  },
  {
   "type": "p",
   "html": "Most training records are informational. A small set determines whether a crew member may operate. Under Part 121 those typically include proficiency checks, line checks, recurrent ground and flight training, and recency of experience items."
  },
  {
   "type": "p",
   "html": "Instrument only these. Applying evidentiary controls to every training item produces resistance without proportionate benefit."
  },
  {
   "type": "h2",
   "text": "Step 2 — Measure the approval delay"
  },
  {
   "type": "p",
   "html": "For each gating event type, compute the interval between the event end time and the instructor approval timestamp. Report the distribution by instructor."
  },
  {
   "type": "table",
   "caption": "Interpretation bands. A long tail matters more than the median.",
   "head": [
    "Delay",
    "Reading"
   ],
   "rows": [
    [
     "Under 1 hour",
     "Approval at the debrief, alongside the event"
    ],
    [
     "Same day",
     "Approval at end of duty; normal and defensible"
    ],
    [
     "1–7 days",
     "Approval decoupled from the event; recollection-based"
    ],
    [
     "Over 7 days, in batches",
     "Queue clearing; the approval is administrative"
    ]
   ]
  },
  {
   "type": "p",
   "html": "Batch approval is not misconduct and usually reflects an instructor with a heavy schedule and a system that makes batch approval the path of least resistance. It does mean that the approval attests to a record rather than to an observation."
  },
  {
   "type": "h2",
   "text": "Step 3 — Check who can enter on whose behalf"
  },
  {
   "type": "p",
   "html": "Ask your training administration team a direct question: can a scheduler or administrator record a completion under an instructor's account? In many operations the answer is yes, because grade sheets arrive on paper and someone has to key them."
  },
  {
   "type": "p",
   "html": "That practice is operationally necessary and evidentially fatal. It means the instructor's approval is not an act by the instructor."
  },
  {
   "type": "h2",
   "text": "Step 4 — Specify the receipt"
  },
  {
   "type": "p",
   "html": "Two signatures over one canonical statement: the instructor who conducted the event, and the crew member who completed it."
  },
  {
   "type": "code",
   "text": "{\n  \"type\": \"manav-stmt/1\",\n  \"action\": \"qualification_event\",\n  \"render\": [\n    \"Event: [proficiency check | line check | recurrent]\",\n    \"Crew member: [name] — [certificate number]\",\n    \"Aircraft/device: [type] — [device qualification]\",\n    \"Date: [date]  Duration: [hours]\",\n    \"Outcome: [satisfactory | unsatisfactory | items repeated]\",\n    \"Grading basis: [syllabus reference, revision]\"\n  ],\n  \"signers\": [\"instructor [cert]\", \"crew member [cert]\"]\n}"
  },
  {
   "type": "p",
   "html": "The crew member's signature is not a formality. It is what converts the record from something done to them into something they can carry."
  },
  {
   "type": "h2",
   "text": "Step 5 — Make it portable"
  },
  {
   "type": "p",
   "html": "This is the part that changes the incentive structure. A pilot moving between operators currently rebuilds their training history through letters, and an operator hiring them verifies through correspondence."
  },
  {
   "type": "p",
   "html": "A signed qualification receipt is the crew member's record, verifiable by any future employer offline. That is a genuine benefit to the individual, which matters because it converts a control that looks like surveillance into one that looks like a credential."
  },
  {
   "type": "h2",
   "text": "Failure traps"
  },
  {
   "type": "ol",
   "items": [
    "Do not gate the record entry. If signing fails, the event still happened and must still be recorded; the receipt is additive.",
    "Do not attempt to instrument simulator sessions through the simulator vendor's system. Sign at the debrief, on a device, where the instructor and crew member are both present.",
    "Do not publish a crew member's full training history. Portability means the individual controls disclosure, not that the record is public."
   ]
  },
  {
   "type": "h2",
   "text": "Where the record is thin"
  },
  {
   "type": "table",
   "caption": "What the row usually contains, and what it should",
   "head": [
    "Element",
    "Typically",
    "Should"
   ],
   "rows": [
    [
     "Who certified",
     "An account",
     "A named instructor with a credential"
    ],
    [
     "What was certified",
     "A qualification code",
     "The event, the manoeuvres, the outcome"
    ],
    [
     "When",
     "A timestamp",
     "Bound inside the signature"
    ],
    [
     "Whether it changed later",
     "An audit table",
     "Detectable by verification failure"
    ]
   ]
  },
  {
   "type": "h2",
   "text": "Objections and honest limits"
  },
  {
   "type": "p",
   "html": "<strong style=\"font-weight:600\">“Instructors are individually accounted for.”</strong> By account. In an investigation the question is whether that instructor was at that terminal, and a shared or delegated login cannot answer it."
  },
  {
   "type": "p",
   "html": "<strong style=\"font-weight:600\">“This is a lot of signing for routine training.”</strong> Bind the qualification-affecting events only — checkrides, line checks and recency-critical entries — not every training interaction."
  }
 ],
 "faq": [
  {
   "q": "Does this imply instructors falsify records?",
   "a": "No. Documented licence and training-record fraud exists internationally but is rare, and the argument here is about evidentiary strength and portability, not suspicion."
  },
  {
   "q": "What if the crew member disputes the outcome?",
   "a": "They decline to sign, and the record shows an instructor signature without a crew signature. That is more informative than the current state, where the record shows completion regardless."
  },
  {
   "q": "Does this work for distributed or remote training?",
   "a": "Yes, with an asynchronous signing flow. The constraint is that both parties sign the same canonical statement, not that they are physically together."
  },
  {
   "q": "Is any of this required?",
   "a": "No. Part 121 Subparts N and O prescribe training content and recordkeeping, not the evidentiary form of instructor approval."
  },
  {
   "q": "Which training records need binding?",
   "a": "The qualification-affecting subset — checkrides, line checks and recency entries — not every training interaction."
  },
  {
   "q": "Why bind the contents rather than the code?",
   "a": "So an alteration to what was certified is detectable, rather than sitting silently in an audit table."
  },
  {
   "q": "Who asks for this evidence?",
   "a": "Any regulator or investigator establishing whether a crew was legally qualified for a specific flight."
  }
 ],
 "sources": [
  {
   "t": "14 CFR Part 121 — Operating requirements: domestic, flag, and supplemental operations",
   "u": "https://www.ecfr.gov/current/title-14/chapter-I/subchapter-G/part-121"
  },
  {
   "t": "ICAO — Annex 1, Personnel Licensing",
   "u": "https://store.icao.int/en/annex-1-personnel-licensing"
  },
  {
   "t": "Reported cases of licence and training-record fraud in international operations."
  },
  {
   "t": "Operator training management system documentation on approval workflows."
  },
  {
   "t": "FAA — regulations and policies",
   "u": "https://www.faa.gov/regulations_policies"
  }
 ],
 "related": [
  {
   "slug": "operational-control-receipt",
   "title": "The dispatch release and the MEL deferral",
   "category": "Vertical"
  },
  {
   "slug": "rts-signature-uniqueness-test",
   "title": "Unique to one individual",
   "category": "Vertical"
  },
  {
   "slug": "licence-issuance-receipt",
   "title": "Licensing and permit issuance",
   "category": "Compliance"
  }
 ],
 "image": "https://cdn.twc.sh/images/igcache/Qualification%20Event%20Receipt/1500_900/blog.jpg",
 "wordcount": 859,
 "url": "/blog/qualification-event-receipt.html",
 "reading_time": "4 min read",
 "seo_title": "Pilot qualification records and crew legality",
 "meta_description": "Crew legality rests on recency, checkrides and line checks — rows created by a training system and approved by an instructor's login.",
 "hub": {
  "slug": "topics/airworthiness-identity",
  "title": "Aviation and airworthiness identity"
 },
 "answer": "Recency, checkrides and line checks — each recorded as a row created by a training system and approved by an instructor's login. The legality of a flight rests on those rows, and they are rarely bound to the instructor as an individual or to the specific event they certify.",
 "answer_q": "What makes a crew legal, and what records it?",
 "glossary": [
  {
   "term": "Recency",
   "def": "The requirement that a crew member has performed defined activities within a defined period to remain qualified."
  },
  {
   "term": "Line check",
   "def": "An evaluation conducted during normal operations, distinct from a simulator checkride."
  },
  {
   "term": "Derived status",
   "def": "A qualification flag computed from underlying event records. Only as good as those records."
  }
 ],
 "checklist": {
  "title": "Binding qualification events",
  "id": "bind",
  "desc": "Four steps.",
  "steps": [
   {
    "name": "Identify the qualification-affecting subset.",
    "text": "Checkrides, line checks, recency entries. A minority of training records."
   },
   {
    "name": "Sign at the instructor's device.",
    "text": "Not the shared training terminal."
   },
   {
    "name": "Bind the event contents, not the code.",
    "text": "So a later change to the record is detectable."
   },
   {
    "name": "Retain to the regulator's period.",
    "text": "Which usually exceeds the training system's life."
   }
  ]
 },
 "cta": {
  "title": "Where this fits in Manav",
  "html": "Manav binds an airworthiness or operational signature to the exact record it certifies, on a credential under one individual's sole control, and produces a receipt an auditor or a regulator can verify years later without access to the operator's systems.",
  "href": "../docs.html",
  "label": "See signature binding"
 }
}