VHS Investor Q&A
Concise, investor-friendly answers to the questions we hear most often about the Virtual Highway System.
What is VHS?+
What problem does VHS solve?+
Why is this needed for future eVTOL networks?+
Does VHS replace FAA or air traffic control?+
How does VHS make money?+
What protects VHS from copycats?+
What stage is the prototype in?+
What does the company need funding for?+
Who are the likely customers or partners?+
Why now?+
Vertiports, Private Pads, and Approved Access Nodes
Practical questions investors — and regular people — ask about who builds vertiports, what counts as one, and how access into a structured VHS corridor is actually controlled.
VHS is not limited to major city vertiports. VHS is designed around approved access nodes. A public rooftop vertiport, airport vertiport, hospital pad, rural emergency site, corporate campus, or private landing area could only connect to the VHS network if it meets defined safety, communication, identity, reservation, and transition-volume requirements. A private pad may allow an aircraft to take off or land under applicable aviation rules, but that does not automatically grant access to a structured VHS corridor. In VHS, the rule is simple: no approved access node, no verified aircraft, no valid reservation, no access.
Who is building vertiports?+
What determines whether something is a vertiport?+
Can a parking pad at someone's house become part of VHS?+
What is a VHS-certified access node?+
What stops someone from just entering the VHS highway?+
Is VHS only for major city vertiports?+
Why does this matter to the business model?+
Public Trust and City Readiness
Plain-language answers to the questions cities, residents, and operators raise about a future VHS network.
Does VHS make the sky busier?+
Would aircraft fly randomly over neighborhoods?+
How would emergency aircraft be handled?+
Can VHS support rural areas?+
What happens if someone enters without permission?+
Key VHS Terms
A short reference for the language used across this site and the prototype.
- Vertiport
- A planned aviation facility designed for vertical takeoff-and-landing aircraft.
- Access Node
- Any approved location that could connect to the VHS network, including a vertiport, hospital pad, airport vertiport, rural site, logistics hub, or approved private pad.
- Certified Access Node
- An access node approved to connect to VHS because it meets defined safety, communication, identity, reservation, and transition-volume requirements.
- Transition Volume
- The controlled 3D airspace between a vertiport/access node and an aerial corridor where aircraft enter or exit the network.
- Reservation Window
- The approved time slot assigned to an aircraft for entering or exiting a transition volume.
- Sky Corridor
- A structured aerial route used for organized eVTOL movement between approved access nodes.
- Unauthorized Conflict
- An aircraft or operator attempting to enter a reserved VHS transition volume or corridor without valid permission.
- Emergency Priority
- A VHS status where emergency aircraft receive priority access while lower-priority movement is held or delayed.
Reach out directly or review the prototype.
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 certified 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.
VHS currently includes two connected prototype layers. The public 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.
