M.K.K. EnterprisesVirtual Highway System
Resource center

Written material on the transition-access layer.

Briefs, architecture notes and a pilot plan explaining why controlled access, corridor coordination and trusted transition-volume management have to exist before advanced air mobility can scale.

Featured brief

VHS Integration Brief: how future networks could coordinate vertiport access

A prototype-stage, diligence-facing look at how a reservation-based access and visualization layer is designed to support future vertiport-to-corridor coordination.

Read the brief
VHS · ResourceIntegration Brief
More resources

Framework, architecture and pilot material.

Framework

VHS Framework

How VHS fits into the broader ecosystem as a focused, prototype-stage transition-volume access layer.

Open Architecture

Technical architecture — prototype to platform

The layered, conceptual architecture of VHS, from access-node registry through the regulator-visibility layer.

Open Pilot plan

First pilot demonstration plan

A simulated approved access-node environment exercising normal access, conflict hold, modeled emergency priority and unauthorized entry.

Open Integration

Aircraft integration guide

What an operator or manufacturer would need to exchange with VHS for a reservation-governed transition.

Open Q&A

Diligence question library

Answers on what VHS is, how access is controlled, public-trust questions and city readiness.

Open Founder's note

Why I am building VHS

A note from the founder on why the structure has to exist before the aircraft arrive.

Open
About the current prototype

Two connected layers, neither certified.

A tested technical software core implements reservation, readiness, conflict, transition-volume and access-decision behavior. A diligence-facing visualization consumes a canonical demo.v1 payload generated from that technical layer.

The visualization demonstrates four scenarios: normal access granted, conflict hold and release, emergency priority, and reservation conflict — access denied.

Neither layer is a certified or deployed aviation system. The private API is locally verified and is not publicly exposed.

FAA / UAM Framework Alignment

A narrower, access-focused layer within the UAM ecosystem.

VHS is designed as a PSU-aligned transition-volume access layer. In FAA Urban Air Mobility framework discussions, a Provider of Services for UAM, or PSU, is a broader service/data role supporting UAM operations. VHS is narrower and focused: it addresses the access-control problem around approved access nodes, transition volumes, reservation windows, conflict holds, corridor entry/exit, and emergency priority.

VHS is not replacing FAA, air traffic control, aircraft operators, or vertiport operators. VHS is a prototype-stage concept intended to support future coordination and visualization around structured aerial access.

VHS is not FAA-approved, certified, or deployed. References to PSU terminology describe alignment with publicly discussed FAA UAM concepts, not regulatory status.

About the Current Prototype

VHS currently includes two connected prototype layers. The visual prototype demonstrates normal access, conflict hold and release, emergency priority, dashboard visibility, and inside-aircraft status concepts. Separately, M.K.K. Enterprises has developed a tested technical software core and locally verified API implementing the underlying reservation, readiness, conflict, transition-volume, and decision logic.

Neither prototype is a certified or deployed aviation system. VHS is not connected to live aircraft, does not replace air traffic control or regulatory authority, and has not yet completed independent operational validation.