Preflight Review¶
Ritual — instantiates Necessary-Condition Closure Design
Runs a time-sensitive all-condition check before a high-consequence action.
A Preflight Review is a time-boxed sweep of the entire necessary-condition set performed in the final window immediately before a high-consequence action, whose distinctive concern is freshness: it re-confirms that every condition is still true now, not merely that it was true when first checked. Its identity is last-moment completeness under a recency requirement. It runs the whole list quickly and close to the action, catching conditions that were green yesterday but have silently decayed — rather than debating any single condition's importance.
Example¶
A charter crew is about to depart. Hours earlier, dispatch confirmed fuel, weather, weight-and-balance, and airworthiness. Immediately before pushback the captain runs the Preflight Review — the aircraft's before-takeoff checklist read against reality right now: flight controls free and correct, fuel quantity matching the fresh load sheet, current ATIS weather, trim set, no new maintenance write-up since dispatch. Everything from the earlier check is re-touched, and the one thing that has changed is a just-issued NOTAM closing the intended departure runway. Because the review re-checks freshness rather than trusting the morning's green, the crew catches it and re-plans before rolling. The whole idea of reading a fixed list at the last moment is why the written preflight check exists at all[1].
How it works¶
Take the full necessary-condition set as a fixed list. Run it rapidly and completely just before the action, and for each item confirm the evidence is current, not merely that it once passed. Any newly-decayed or newly-unknown condition is treated as a stop. The emphasis is speed, completeness, and recency at the decision boundary — it is a re-confirmation ritual, not a forum for deliberating over which conditions matter.
Tuning parameters¶
- Recency window — how fresh a prior check must be to still count, versus requiring live re-confirmation. Tighter windows catch more decay but cost time right when time is short.
- Sweep completeness — full-list every time versus only the conditions prone to change. Full sweeps are safest; deltas-only is faster but can miss a surprise decay.
- Time budget — how long the review may take before it eats into the action window. A tight budget keeps it a sweep rather than a re-litigation.
- Abort authority — who can halt on a failed item, and whether a hold auto-triggers or requires a call.
When it helps, and when it misleads¶
Its strength is that it is the last net before commitment and the sibling built specifically for conditions that expire — weather, fuel, clearances, live system state. Its failure mode is rushed rote: a preflight run as fast recitation can tick items without truly re-checking freshness, which is exactly the decay it exists to catch. It also presumes the list is complete, so an omitted condition is invisible to it. The guarding discipline is to keep the sweep genuinely verifying rather than reciting, to leave list maintenance to other mechanisms, and to protect the time budget so the review is not compressed into meaninglessness.
How it implements the components¶
necessary_condition_set— it runs the complete set as a fixed list; completeness at the last moment is the point.condition_evidence_record— its defining move is confirming each condition's evidence is current, enforcing the archetype's recency requirement.rehearsal_or_probe— the final sweep is a lightweight live probe of each condition's present state rather than a paper re-read.
It does not independently adjudicate each condition's non-substitutability (non_substitutability_test) or poll a named owner for a per-condition veto (condition_owner_map, blocker_decision_rule) — that owner-by-owner judgment is its ritual twin Go/No-Go Condition Review; the preflight instead re-sweeps the whole set for freshness at the last moment.
Related¶
- Instantiates: Necessary-Condition Closure Design — it is the final freshness gate before an irreversible action.
- Consumes: All-Conditions Checklist supplies the fixed list the sweep re-confirms.
- Sibling mechanisms: All-Conditions Checklist · Blocker Register · Condition Coverage Test Suite · Dependency Closure Map · Go/No-Go Condition Review · Limiting-Factor Board · Readiness Gate Scorecard without Averaging · Red-Team Precondition Challenge · Weakest-Link Postmortem
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Preflight Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it runs a time-sensitive all-condition check before a high-consequence action.
Independent corroboration: The frozen evidence defines Preflight Review as 'Runs a time-sensitive all-condition check before a high-consequence action', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Aviation & Aeronautics
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Time-sensitive all-condition review before consequential action descends most directly from aviation preflight practice.
Related originating lineages:
- Disaster Management & Risk Reduction — Disaster management independently uses pre-activation readiness checks for response operations.
- Engineering & Design — Safety engineering generalized readiness review to other hazardous systems.
- Military & Strategic Studies — Mission-readiness checks materially generalized preflight logic to coordinated operations.
Review resolution: Both blind reviewers agree that aviation aeronautics is the primary origin. Reconciliation resolves alternate origin disagreement. Formative alternate lineages are retained as disaster_management, engineering_design, military_strategic_studies; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=convergent describes the relationship among origin lineages.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] The written preflight checklist entered aviation after the 1935 crash of the prototype Boeing Model 299, when it was recognized that a complex aircraft had too many pre-takeoff steps to be left to even a skilled pilot's memory; a fixed list read before every flight became standard practice. withdrawn registry ↩