Public simulation

See how an arrival gets authorized — one role at a time

This is a public, read-only simulation of the ClearPass Air authorization engine. It runs the same deterministic rules the platform uses, against fixed synthetic fixtures, entirely in your browser. Nothing is stored, sent, or charged.

Simulated sources. External aviation status sources and outbound webhook deliveries are simulated. ClearPass Air does not issue air traffic clearance.

Fictional tenants. All names, tail numbers, and identifiers are invented for illustration and imply no affiliation, partnership, or endorsement.

No real data. No personal information, biometric data, or identity documents are used, requested, or displayed anywhere in this demo.

Role walkthrough

Every party sees a different slice of the same decision, and no single party owns every rule. Pick a lens to see what is checked and who is authoritative for it.

Identity assurance, manifest, consent, minimal disclosure

Passenger

A passenger proves who they are once, then decides what a destination may see. The destination receives a decision and generalized requirement flags — never a persistent ClearPass identifier, an assurance tier, or the underlying identity documents.

Identity assurance level meets the destination's minimum

Rule owner
ClearPass Air identity layer
Disclosed
requirements.identity_requirements_met (boolean)

Occupant appears on the confirmed manifest

Rule owner
Operator
Disclosed
requirements.manifest_requirements_met (boolean)

An active consent grant covers this partner and purpose

Rule owner
The passenger
Disclosed
requirements.data_sharing_authorized (boolean)

Biometric match and liveness confirmed by the identity provider

Rule owner
External identity provider (simulated)
Disclosed
nothing biometric — folded into identity_requirements_met

Run a simulated check

Choose a fixed scenario and run it through the real rule engine. Same input, same output, every time — that determinism is the point.

Select a scenario and run the check. The engine evaluates operator, aircraft, occupants, destination policy, and external status, then returns one explainable decision.

Roadmap / extensions

Extensible ecosystem

The roles below are directions the model extends to — not completed, dedicated personas. They are listed to show how the same identity, consent, and rule-ownership primitives generalize.

Mechanics

Maintenance sign-off as a credentialed assertion on the aircraft.

Dispatchers

Trip release and operational control attribution.

Flight schools

Training-flight roles and instructor-to-student assignment.

OEM / manufacturers

Airworthiness and service-bulletin assertions at source.

Airports

Mixed-use facilities with existing badging and access systems.

Contractors

Time-boxed site access for vendors and service providers.

Regulators

Read-only, consent-aware oversight views.

Future mobility providers

Ground, marine, and other modalities on the same identity layer.