Operational boundary

Aviation Responsibility Notice

Founding beta notice, version AR-1. Effective August 11, 2026.

The operator remains responsible

Each operator remains solely responsible for operational control, airworthiness, maintenance approval and return to service, crew qualification and legality, dispatch and flight release, training and endorsements, fuel quality, source-data accuracy, record retention, regulatory compliance, and every safety-sensitive decision.

Qualified people must verify the work

A Skyvon dashboard, alert, calculation, status, signature, reminder, or workflow does not establish airworthiness, compliance, authorization, or approval. Authorized personnel must independently verify source information and current requirements before acting.

No complete-alert guarantee

The absence of an alert does not mean an aircraft, person, task, document, or operation is compliant or ready. Data may be incomplete, delayed, entered incorrectly, unavailable during an outage, or affected by a software defect.

Official records and continuity

During the founding beta, the operator must decide which system remains its official record and preserve any duplicate records needed for safe, lawful continuity. The operator must maintain practical procedures for outages, exports, manual verification, and recovery.

Configuration and validation

Rules, thresholds, permissions, workflows, and reports must be configured and validated by the operator for its certificates, manuals, approvals, aircraft, people, and applicable regulations. Skyvon does not obtain regulatory acceptance on an operator's behalf.

Questions and reports

Product and workflow questions may be sent to support@skyvonaviation.com. Suspected security issues should be sent to security@skyvonaviation.com. Do not include credentials or unnecessary sensitive operational information.