VHS Q&A
Understand the system from the boundary outward: the operating problem VHS addresses, the decision architecture behind it, the commercial model, the competitive landscape, the patent-pending position, and what remains to be validated.
NO VALID RESERVATION — NO ACCESS.
VHS answers one question: who is authorized to enter the protected transition space, and when. A request is an input. An authorization is an explicit outcome issued against evaluated resource state. The three aircraft-facing outcomes are fixed, and they mean the same thing on every page of this site.
- Authorized to enter, one bounded interval
- HOLD
- Valid request, conditions not yet satisfied
- DENIED
- Refused outcome, recorded with its reason
Every answer carries a classification so a reader can tell what is built from what is described, proposed, illustrated or still to be validated.
- Implemented and verifiable in the current build.
- Described in the filed provisional application; not necessarily implemented.
- A proposed commercial structure. Not booked revenue or contracted pricing.
- Arithmetic illustration of a planning model. Not a forecast.
- External figures, reproduced with their scope and year.
- Planned or dependent on validation that has not been completed.
What VHS Is
The shortest accurate description of the system: what it governs, what it refuses to govern, and the one rule that decides entry.
What is VHS?
VHS — the Virtual Highway System — is a prototype-stage transition-access coordination layer developed by M.K.K. Enterprises. It decides which verified aircraft may enter the controlled transition volume above an access node, and when. It is manufacturer-, operator- and aircraft-class neutral: eVTOL (electric Vertical Takeoff and Landing) and other powered-lift aircraft, helicopters and commercial UAS (Unmanned Aircraft Systems) are evaluated against the same resource and the same rules.
What problem does VHS solve?
Between a landing surface and the wider airspace there is a coordination gap. As throughput at an access node grows, the transition volume above it becomes the bottleneck: multiple operators, multiple aircraft classes and multiple schedules all need the same small piece of sky at overlapping times. VHS gives that transition a reservation-based access model so contention is arbitrated consistently instead of ad hoc.
What single question does VHS answer?
Who is authorized to enter the protected transition space, and when. That question is deliberately narrow. Everything in the architecture exists to answer it consistently and to prove afterwards that it was answered that way.
What is VHS not?
It is not air traffic control, not a UTM (Unmanned Aircraft System Traffic Management) platform, not avionics, not a navigation system, not fleet management, not an aircraft manufacturer, not a vertiport owner and not a claim to own urban airspace. It holds no regulatory authority and carries no FAA (Federal Aviation Administration) mandate.
What exactly is a Transition Volume?
A digitally defined three-dimensional region of airspace anchored to an access node, through which an aircraft enters or leaves the structured network. It is treated as a single resource that can be claimed by one authorized aircraft for one bounded interval.
What does “NO VALID RESERVATION — NO ACCESS” mean?
Without a valid reservation matched to the aircraft, the resource and a bounded interval, the transition volume is not enterable through VHS. There is no informal path, no override by seniority and no exception for convenience.
Does VHS fly, route or control the aircraft?
No. VHS issues an access decision about one resource. Navigation, flight control, separation assurance and detect-and-avoid remain with the aircraft, the operator and the applicable aviation systems. VHS never commands an aircraft.
Why now?
Aircraft programmes across several classes are converging on commercial readiness and access-node plans are moving from concept to capital. The coordination layer between them is the part still missing. Building it at prototype quality now is what makes it credible later.
The Transition-Access Boundary
Why M.K.K. chose one narrow operational function instead of an airspace platform, and why a narrow function can still be consequential.
What VHS actually controls
- Shared airspace / corridor environmentCoordinated by existing aviation systems. Outside the VHS boundary.
- Access node / approved siteThe landing surface and its operator. Not owned or run by VHS.
VHS governs one layer: the protected transition volume above an approved access node. The surface below and the shared airspace above remain under their existing owners and authorities.
Why focus on the transition boundary rather than the whole airspace?
Because that is where movement is densest, least separated and most consequential, and because it is a bounded engineering problem with a definable owner. Broad airspace management already has established owners and long regulatory horizons; the access boundary at a node is where a determinate, provable answer can actually be built and adopted.
Why not broaden the scope to capture more value?
Because scope discipline is what makes the system provable, adoptable and defensible. A broad claim invites regulatory collision, competitive collision and an unfinishable engineering task. The narrow claim can actually be built, checked and integrated beside what already exists.
Can the same architecture support on-ramp and off-ramp operations?
Yes. Entry into the structured network and exit from it are both transitions across the same controlled boundary, governed by the same reservation, evaluation and evidence model. The direction of travel is an attribute of the request, not a different system.
At what point does this become urgent?
When simultaneous demand at one node routinely exceeds one movement at a time. Below that, informal coordination is sufficient. Above it, the absence of a deterministic arbiter becomes both a throughput limit and an accountability gap. When that threshold is reached at any given site is not something M.K.K. can predict.
How can a narrow layer matter commercially?
Because some functions are small in scope and load-bearing in effect. A system can specialise in a narrow operational function while that function remains important to a much larger transportation ecosystem. The question is not how much of the industry you own; it is whether the part you own has to work.
Isn’t VHS just UTM?
No. UTM is a broad traffic-management concept across an operating area. VHS is an access-control authority over a single exclusive resource at a node, producing a binding outcome for one aircraft and a replayable record of why. Scope, unit of control and output are all different.
Are there conceptual analogies for that pattern?
Several, offered strictly as conceptual illustrations of a pattern: payment-network authorization performs a narrow decision function inside a much larger banking and commerce ecosystem; railway interlocking governs a narrow but critical junction; runway-incursion protection addresses a limited but consequential movement boundary; internet routing and security layers perform specialised functions without owning the internet.
Go deeper
None of these comparisons implies that VHS has comparable revenue, adoption, market position, regulatory standing, valuation, network effects or maturity. VHS is a prototype-stage system with no deployment. The comparison is to the shape of the function, nothing else.
How does that pattern apply to VHS?
Transition access is the narrow operational boundary M.K.K. is building around: one resource, one decision, one evidence trail. VHS does not attempt to own aircraft, airspace, vertiports or traffic management — it attempts to be the layer that answers who may enter the protected transition space, and when.
How the System Works
Request, validate, evaluate, decide, record, replay. What each aircraft-facing outcome means and what happens when the interval ends.
A request asks. The authoritative decision answers.
- RequestInput only
- ValidateWell-formed, in scope
- EvaluateResource state, versioned policy
- DecideOne authoritative outcome
A request is an input. It carries no permission of its own. The decision is issued against evaluated resource state, then recorded so it can be reconstructed later.
What does ACCESS GRANTED mean?
The aircraft is authorized to enter the specified transition volume for one bounded interval. The claim is exclusive for that interval, and the authorization is recorded with the state and policy version that produced it.
What does HOLD mean?
A temporary waiting outcome. The request is valid but one or more required conditions are not currently satisfied — most often the volume being claimed by another operation, but timing, sequencing and site conditions can each produce it.
What does DENY mean?
DENY is the refusal action the engine takes; DENIED is the resulting aircraft-facing outcome. The request is closed with a recorded reason. It is not a waiting state and it does not resolve on its own.
What happens after a reservation is released?
The resource returns to available. Release is a resource-lifecycle event, not an aircraft-facing decision, and it does not by itself authorize the next requester — the next request is evaluated again on its own merits.
Deterministic Decisions
Why the outcome is a function of evaluated state and versioned policy, and why an unknown never becomes access.
What does deterministic mean?
Given the same recorded inputs, their ordering and the policy version that applied, the engine reaches the same outcome every time. No randomness, no learned model and no operator improvisation sits inside the decision path.
Why does determinism matter in aviation infrastructure?
Because an access decision that cannot be reconstructed cannot be reviewed, audited or defended. Aviation review culture depends on being able to establish exactly what was known and what was decided. Determinism is what turns a decision into evidence rather than an assertion.
Does AI or an LLM decide whether an aircraft receives access?
No. No AI or language model participates in an operational decision. The decision logic is explicit, versioned and replayable. This is a deliberate architectural constraint, not an implementation detail.
What role do rules and versioned policies play?
The conditions a request is evaluated against live in a versioned policy authority rather than being scattered through code paths. A decision records the version that applied to it, so the rule set in force at any past moment is knowable.
What happens when required information is missing?
The condition is not satisfied, so entry is not authorized. Depending on whether the information may still arrive within the window, the outcome is a HOLD or a DENY — never a permissive assumption.
What is fail-closed behaviour?
The system's default in the absence of proof is refusal, not permission. If the engine cannot establish that entry is authorized, it does not authorize entry.
Can the same recorded inputs produce a different outcome later?
Not under the same policy version. Replaying recorded inputs with the version that applied reproduces the original outcome. A different outcome under a newer policy version is a legitimate, visible difference — which is precisely why the version is recorded with the decision.
Why is UNKNOWN not treated as GRANT?
Because an unknown state is indistinguishable from the worst case. Treating uncertainty as permission would convert a missing message into an authorized entry into a possibly occupied volume. UNKNOWN never becomes ACCESS GRANTED.
When Demand Conflicts
One aircraft enters, one waits. What produces HOLD, how physical conflict is resolved before priority, and how abnormal conditions are treated.
Overlapping demand on one transition volume
Overlapping request for the same interval.
Aircraft A holds a valid bounded reservation, so the interval is allocated to it. Aircraft B's overlapping request is answered with HOLD — a valid request whose conditions are not yet satisfied, re-evaluated when the resource state changes. Emergency and priority handling follow their own governed rules; this plate illustrates ordinary exclusive allocation only.
What happens when two aircraft request overlapping access?
The resource admits one claim at a time, so the requests are ordered and evaluated in that order. One receives ACCESS GRANTED; the other receives HOLD and is re-evaluated later. The ordering is part of the recorded evidence.
What makes the reservation exclusive?
The resource admits one claim at a time. While a claim is active, no other claim on the same volume for the overlapping interval can be authorized. Exclusivity is the property that makes the outcome meaningful — one aircraft, one volume, one time-bounded interval.
Why isn’t HOLD the same as DENY?
HOLD is temporary and re-evaluable: the request remains alive and will be decided again. DENIED closes the request. Collapsing the two would hide the difference between waiting and being refused — operationally and in the evidence record.
What is resolved first — conflict or priority?
Physical conflict. The engine establishes whether the resource can be occupied at all before any priority or sequencing preference is applied. Priority reorders who is considered next; it never places two operations in the same volume.
What happens during emergency operations?
The prototype demonstrates emergency-priority behaviour in a controlled scenario: qualifying movement receives priority while lower-priority movement is held. Physical conflict is still resolved before priority is considered.
Can a HOLD later become ACCESS GRANTED?
Yes — only when the request is re-evaluated and every applicable condition is satisfied at that later moment. Release of the contended resource is necessary but never sufficient on its own.
How are simultaneous requests serialized?
Concurrent requests are ordered and evaluated in that order rather than resolved in parallel. Ordering is part of the recorded evidence, which is what allows a reviewer to reconstruct why one request was granted and another held.
Can a HOLD later become DENIED?
Yes. When re-evaluation establishes the request cannot be authorized at all — the window elapsed, the claim is no longer valid, or a condition is failed rather than merely unmet for now — the refusal is recorded with its reason.
Proving What Happened
Built to be checked, not just believed. What a decision record holds and how it is reconstructed later.
From recorded state to deterministic reconstruction
- Input / recorded stateRequest and resource state as observed
- Versioned evaluationThe policy version in force
- DecisionGranted, Hold or Denied
- Evidence recordWritten with its reason
- Deterministic replaySame inputs, same outcome
Replay is not a playback animation. It is reconstruction of the decision from the recorded inputs, resource state and the policy version that governed it at the time — which is what makes the outcome checkable rather than asserted.
What is an evidence record?
The structured fact of a decision: which request was evaluated, the relevant resource state at that moment, the versioned conditions applied, the outcome, its reason, and enough ordering information to reconstruct the sequence. It is structured fact, not a narrative log line.
What does VHS preserve after a decision?
The inputs as received, their ordering, the resource state considered, the policy and vocabulary versions in force, and the issued outcome with its reason. That set is what makes later reconstruction possible.
Can an operator see why an aircraft received HOLD?
Yes. Each outcome carries a reason classification and the evidence trace behind it, so the condition that was not satisfied can be identified rather than inferred.
What is deterministic replay?
Re-running recorded inputs, in their recorded order, through the same decision logic and the versioned authorities that applied at the time, producing the same sequence of outcomes a reviewer can step through.
Is replay merely an animation?
No. An animation redraws a stored picture. Replay recomputes the decisions. If the logic or the recorded facts disagreed with the original outcome, replay would surface that disagreement rather than hide it behind a rendering.
Why does policy versioning matter?
Because rules change and history should not. Recording the policy version with the decision means a later rule change cannot silently rewrite the meaning of an earlier decision.
Can a later policy change rewrite what happened historically?
No. Replay of a past decision uses the past version. A new version applies to new decisions.
Why is an auditable decision preferable to an unexplained result?
Because infrastructure is adopted on the basis of accountability as much as capability. A decision that can be checked can be reviewed, corrected, insured and defended. An unexplained result can only be trusted or distrusted.
Technical Architecture
Where authoritative decisions are made, how state and time are kept separable, and what integration would require.
How is the boundary enforced in the software itself?
Operational decisions are produced only by the governed decision authorities. The presentation layer may display, order and reconcile governed facts, but it may not invent decisions, conflicts, priority, reservations, geometry, time, policy or evidence. That separation is enforced by architecture tests in the build.
What gets reconstructed during replay?
The sequence of requests, the resource state transitions, the evaluations performed and the outcomes issued, each tied to the version of the rules that applied. Visualization renders that reconstruction; it does not produce it.
How is resource state different from an aircraft decision?
They are deliberately separate. A decision is issued to an aircraft; a resource state describes the transition volume itself, which moves between IDLE, claimed and Released as its lifecycle proceeds. Released describes the resource returning to available — never an aircraft-facing decision.
What does 4D mean operationally?
Three spatial dimensions plus time. An allocation is only meaningful when three spatial extents and one bounded time interval are all present, together with the identity the claim belongs to. A region with no window, or a window with no identified operation, is not a reservation and cannot be evaluated.
Why does vocabulary versioning matter?
Because the words are part of the record. If the meaning of a decision term drifted between versions, a past record would be read incorrectly. Versioning the vocabulary keeps the semantics of an old record stable.
What does an operator need to integrate?
A way to identify the operation, a way to submit a request for a bounded interval, and a way to receive and act on the returned outcome. The interface is defined by a canonical data contract; security-sensitive detail is shared under direct technical review rather than published.
What happens if communication is degraded?
Fail-closed. If the state of the volume, the reservation or the participant cannot be established, access is withheld rather than assumed. Degraded-mode behaviour beyond controlled scenarios is prototype-stage and subject to validation.
What does it not prove?
Real-world performance, throughput at a live site, integration with operator and vertiport systems, behaviour under real degraded conditions, regulatory acceptability, or safety adequacy. Those require validation that has not been performed.
Where VHS Fits
The boundaries with air traffic control, UTM, flight planning and the aircraft itself — stated plainly.
One narrow layer inside a large ecosystem
- Aircraft / operatorFlight control, navigation, detect-and-avoid
- Flight planning / UTM / traffic coordinationExisting and emerging coordination services
- Shared airspaceGoverned by the applicable aviation authority
- VHS transition-access boundaryReservation, decision, evidence, replay
- Vertiport / approved access nodeOwned and operated by the site
VHS does not replace air traffic control, UTM services, aircraft systems, manufacturers, operators, airports or vertiport owners. It specializes in a single operational boundary and interoperates with the layers around it.
How does VHS interact with FAA air traffic control?
VHS is not an air traffic control system and holds no regulatory authority. It governs access to a defined transition resource; final authority over airspace remains with the appropriate aviation authorities. Any operational relationship would be defined with regulators, not asserted by the system.
How does VHS interact with UTM?
UTM (Unmanned Aircraft System Traffic Management) and comparable systems handle planning, authorization and traffic awareness across a wider area. VHS answers a narrower question those systems leave open at the boundary: who may enter this specific transition volume, and when. They are complementary layers, not substitutes.
How is VHS different from flight planning?
Flight planning declares intent ahead of time. VHS decides permission at the boundary against the actual state of the resource. A plan does not clear an aircraft into an occupied volume; an access decision does or does not.
Does VHS require the operator to change how it flies?
No. VHS governs whether and when a transition may occur, not how the aircraft is flown. Existing procedures, autonomy and crew responsibilities are unchanged.
Is VHS only for eVTOL?
No. The resource being protected is the transition volume, not a particular airframe. Any aircraft class that can be identified, can hold a reservation and can act on an outcome fits the same model.
Can helicopters use the same transition-access architecture?
Architecturally yes, and rotorcraft are the largest existing population of vertical operations. Whether a given helicopter operation can participate at a given site depends on identity, reservation and communication requirements that have not been validated in the field.
Can commercial drones use it?
Architecturally yes. Commercial UAS operations are already the largest source of new vertical activity, and the same request, evaluation and evidence model applies. Field validation has not been performed.
Does aircraft neutrality increase the addressable infrastructure opportunity?
It is intended to: a node that serves rotorcraft, UAS and powered-lift under one access model is a broader opportunity than one serving a single class. That is a business thesis about the model, not a validated adoption result.
Competitive Landscape
Adjacent companies, where the overlap actually sits, and the honest answer to what would stop an incumbent from doing this.
Who operates in adjacent space?
The deck identifies three adjacent focus areas: ANRA — vertiport and traffic coordination, the closest overlap; OneSky — flight planning and monitoring; Airspace Link — airspace access and awareness. These are descriptions of focus area, not assessments of their capabilities.
What is the VHS positioning in one line?
Reserved for one. One enters — one waits. Every decision is recorded. VHS controls who enters the protected transition space and when.
Where does VHS overlap with ANRA, and where does it differ?
The overlap is the vertiport and coordination context. The difference in the VHS position is the unit of control: an exclusive, time-bounded transition volume assigned to one aircraft, with a deterministic decision and a replayable evidence record behind it. M.K.K. does not assert what ANRA's systems can or cannot do.
How does the VHS focus differ from OneSky?
OneSky's described focus is flight planning and monitoring — intent and observation across an operating area. VHS's focus is a binding access decision at a single protected resource at the moment of movement.
How does the VHS focus differ from Airspace Link?
Airspace Link's described focus is airspace access and awareness at a regional and regulatory level. VHS operates at the node boundary, allocating one volume to one aircraft for one interval with an evidence trail.
Could these companies become partners rather than competitors?
Plausibly. A coordination or planning platform still faces the question of who enters a specific transition volume and when, and a deterministic, evidence-producing answer to that question is complementary to a broader platform. No such relationship exists or is claimed.
Could an incumbent build transition-access functionality?
Yes — that possibility is real and should be assumed. Any credible answer to competitive risk has to start there rather than deny it.
What would make that harder?
The provisional patent position; a working deterministic implementation rather than a specification; the evidence, replay and versioning properties, which are difficult to retrofit onto a system not designed for them; integration depth at each site; and the neutrality required to sit between operators who compete with each other. None of these is a guarantee.
Patent-Pending Architecture
A provisional patent application has been filed. Patent pending. What that does and does not mean, in public-safe terms.
What has M.K.K. filed?
A provisional patent application concerning controlled, time-bounded access to defined transition infrastructure, together with related coordination and visualization concepts. Status: PROVISIONAL PATENT APPLICATION FILED — PATENT PENDING.
What does patent pending mean?
That an application has been filed and is not yet examined or granted. It is not an issued patent, not an allowance of claims, and not a legal monopoly. It establishes a filing position and permits the “patent pending” designation.
What does the provisional application generally concern?
At a conceptual level: digitally defined Transition Volumes, exclusive time-bounded allocation, aircraft-bound access authorization, the transition between an access node and a shared corridor, multi-node coordination, and evidence and visualization architecture.
Is the Transition Volume the only concept described?
No. The filing also describes corridor concepts, departure and arrival transitions, coordination across multiple nodes, and evidence and visualization architecture. Detailed claim language is not reproduced publicly.
Is every VHS Transition Volume exactly 500 feet wide?
No. The provisional application describes a reference cylindrical implementation of approximately 500 feet in diameter while also describing parameterized, configurable geometry. Footprint, ceiling, buffers and shape are configuration for a given site and its approved operating context.
Go deeper
The same discipline applies to the illustrative corridor altitudes, directional corridors, speed-classified lanes and spacing values that appear in the provisional. They are reference and configurable embodiments used to describe the architecture — not immutable VHS limits, and not published operating parameters for any site.
Does filing a provisional guarantee a patent?
No. A provisional is not examined. A non-provisional application must be filed within the applicable period, and any resulting claims are subject to examination, amendment and rejection.
How does M.K.K. protect the idea while still explaining the product publicly?
By publishing the architecture and withholding the implementation. Concepts, boundaries, decision semantics and evidence properties are explained openly; interface specifics, internal decision structures, security-sensitive material and claim language are shared only under direct technical review.
How VHS Could Make Money
The proposed commercial structure: three revenue lines, what a customer would be paying for, and which parts recur. Proposed pricing, not booked revenue.
Three proposed commercial lines
- Site activation$150K–$250Kper vertiport
- Annual network assurance$75K–$125Kper vertiport, per year
- Network integration$300K–$750Kper deployment
- Site activation10 × $150K $1.50M
- Annual network assurance10 × $75K $750K ARR
- Network integration1 × $500K $500K
$2.75M modeled Year-1 value is not ARR. The recurring component of this illustration is $750K ARR. The remaining $2.00M is one-time activation and integration work that does not repeat.
All figures are proposed pricing and an illustrative management model. They are not booked revenue, contracted pricing, a forecast, or evidence of customers. Pricing, adoption and timing remain subject to validation.
Who potentially pays M.K.K.?
Access-node developers and operators, infrastructure owners connecting a site to a structured network, and network-level participants commissioning an integration. Aircraft operators participate through the interface; regulators are stakeholders rather than customers.
What are customers paying for?
Configured, verified transition-access control at a site, continued assurance of that control over time, and the engineering needed to connect sites into a coordinated network. In short: permission control at the boundary, and the ability to prove it afterwards.
What is Site Activation?
A one-time engagement of $150K–$250K per vertiport covering transition-volume configuration, interfaces, verification, testing and deployment for that site.
What is Annual Network Assurance?
A recurring service of $75K–$125K per vertiport annually covering software maintenance, policy updates, replay verification, evidence integrity and support. This is the recurring component of the model — and it is a service name, not an acronym.
What is Network Integration?
A $300K–$750K engagement per network deployment covering network engineering, airport and operator adapters, training and launch support. It is network-level rather than per-site.
Which revenue is one-time and which is recurring?
Site Activation and Network Integration are modelled as one-time. Annual Network Assurance is the recurring line. The distinction matters because only the recurring line contributes to ARR.
Why is recurring revenue strategically important?
Because assurance obligations persist for as long as a site depends on the access layer: policy changes, replay verification and evidence integrity are continuing duties, not a delivery milestone. A model resting only on activation fees would have to keep selling new sites to stand still.
Does VHS require nationwide adoption to work commercially?
No. The model is built on connected sites, and the illustrations at 10 and 19 sites are deliberately small. Whether a small network is commercially viable in practice is unvalidated.
Understanding the Numbers
The illustrative model, stated as arithmetic. Modeled Year-1 value and modeled ARR are different quantities and are kept separate here.
What does ARR mean?
ARR is Annual Recurring Revenue — recurring revenue annualised over a one-year period. It is a finance metric. It is not the name of a service, and it must not be confused with Annual Network Assurance, which is the proposed recurring service that would generate the recurring revenue in this model.
Go deeper
Within the current illustrative model, ARR comes only from the Annual Network Assurance line at the deck's conservative $75K per connected site per year. Site activation and network integration are one-time and are excluded from ARR.
How does the illustrative $2.75M 10-site Year-1 model work?
Three modelled components at the conservative end of the proposed ranges, plus one modelled launch-network integration.
- Site activation10 × $150K = $1.50M
- Annual network assurance10 × $75K = $750K
- Network integration1 × $500K = $500K
Go deeper
The distinction that matters: $2.75M modelled Year-1 value is not $2.75M ARR. Of that total, $1.50M is one-time site activation and $500K is one-time network integration. The recurring component — the ARR — is $750K.
Is the $2.75M figure ARR?
No. $2.75M is modelled Year-1 value, of which $2.0M is one-time ($1.50M activation plus $500K integration) and $750K is recurring. The illustrative ARR is $750K.
Why does the model use $75K instead of the top of the $75K–$125K range?
Because the conservative end of a proposed, unvalidated range is the defensible one to model with. Using the top of the range would inflate every illustration by two-thirds without adding information.
What does the 19-site recurring example mean?
19 × $75K = $1.425M ARR. The deck describes that level as targeting support for the lean operating base. It is a management planning target based on the current $75K recurring planning assumption — not guaranteed breakeven, not proven operating cost, not guaranteed profitability and not a runway guarantee.
What does the recurring model look like at different site counts?
Arithmetic at the conservative $75K annual assurance assumption per connected site. These are illustrations of the recurring model, not sales forecasts or booked revenue.
- 10 sites10 × $75K = $750K ARR
- 19 sites19 × $75K = $1.425M ARR
- 500 sites500 × $75K = $37.5M ARR
- 1,000 sites1,000 × $75K = $75M ARR
- 2,500 sites2,500 × $75K = $187.5M ARR
- 5,000 sites5,000 × $75K = $375M ARR
Is any of this revenue booked? Are there signed contracts?
No. There is no booked revenue, there are no signed customer contracts, and none of the figures on this site is a sales forecast.
What would have to happen before these economics become validated?
A real site would have to accept the proposition, pay a real activation price, renew a real assurance obligation, and a network integration would have to be scoped and delivered. Until then the model is structurally reasoned but commercially untested.
Why the Market Could Matter
The aviation activity that could produce demand for transition access — and why aircraft counts are never converted into VHS revenue.
How large is the existing rotorcraft population?
10,573 active U.S. rotorcraft in 2024, with an FAA forecast of 14,665 by 2046. External market evidence, cited for scope; it is not a VHS customer count.
How large is the commercial UAS population?
424,516 active Part 107 commercial UAS in 2025, with an FAA base forecast of 540,845 by 2030. External market evidence.
What are the Advanced Air Mobility projections?
AAM (Advanced Air Mobility) projections referenced in the deck describe 1.615M annual departures, AAM operational Year 6, across 32 markets and 367 aircraft. External market evidence, not an M.K.K. deployment plan.
Why doesn’t this site publish a TAM figure?
Because an honest one cannot be derived from the approved material. The credible unit is connected access nodes, and no validated national count of future VHS-eligible nodes exists. Multiplying aircraft populations by site pricing would be arithmetic without meaning.
What does a connected-site network mean?
Multiple access nodes operating under coordinated configuration and shared evidence practice, so that movement between them can be reasoned about rather than treated as independent events. Network Integration is the modelled commercial engagement that would build it.
Can a small network establish a viable proof point?
That is the thesis behind emphasising 10 connected sites: enough nodes to exercise coordination between them, small enough to be achievable, and sufficient to produce evidence a larger buyer would want to see. It is a plan, not a result.
How does a multi-site deployment differ from a one-site deployment?
A single site is configuration and verification. Multiple sites introduce network engineering, adapters, coordination between nodes and shared operating procedures — which is the modelled basis for the separate Network Integration line.
Do FAA forecasts predict M.K.K.’s site count or revenue?
No. FAA and industry figures describe aircraft activity. They say nothing about M.K.K. adoption, pricing or revenue, and no statement on this site should be read as implying otherwise.
From Prototype to Operations
What exists today, what does not, and what a controlled pilot would have to establish before anything operational.
What does the working prototype currently prove?
That the decision model runs: a deterministic decision core over structured scenarios; ACCESS GRANTED, HOLD and DENIED outcomes with recorded reasons; transition-volume state management; conflict handling and controlled sequencing; emergency-priority behaviour in a controlled scenario; recorded evidence and deterministic replay; and a guided public demonstration.
Is VHS operational today?
No. There is no live deployment and no live operations. The system runs as a prototype with controlled scenarios.
Is VHS FAA certified or FAA approved?
No. VHS is not certified, not approved, not operationally authorized and carries no FAA mandate.
Has it completed field validation?
No. Nothing has been field validated in live aviation operations.
What would a controlled pilot need to establish?
That the decision model behaves correctly against real inputs at a real site, that integration with operator and node systems is workable, that evidence and replay hold up under external review, and that the operating procedures around an authorized transition are sound.
What would independent validation add?
Third-party confirmation of the determinism and evidence properties the architecture claims. A self-asserted determinism claim is weaker than an externally checked one, and the difference matters to both regulators and buyers.
How could VHS begin with one site?
A single access node with a defined transition volume, one or more participating operators, and a configured policy is a complete instance of the model. Exclusivity, evaluation, decisions and evidence all function at one node — the network is an extension, not a prerequisite.
What must happen before commercial aviation deployment?
Site definition and configuration, integration with the relevant access-node and operator systems, defined communications and identity requirements, independent technical and safety review, engagement with the applicable authorities, and a controlled pilot. None of these is complete.
Building M.K.K.
Stage, raise, the eighteen-month objective, the capabilities being added, and the risks that come with them.
What stage is VHS at?
Prototype stage with a working deterministic decision core, structured scenario processing, ACCESS GRANTED / HOLD / DENIED outcomes, recorded evidence, deterministic replay and a guided public demonstration. It is not certified, not deployed and does not control real aircraft.
What does the $2.0M raise fund?
A seed-stage $2.0M raise supporting an 18-month pilot-readiness plan. The stated purposes are team, platform, independent validation, patent strategy and a controlled pilot package.
Exactly what percentage of the $2.0M goes to each category?
The approved material does not provide a percentage allocation, and M.K.K. does not publish one it has not committed to. The stated purposes are team, platform, independent validation, patent strategy and a controlled pilot package; a detailed budget is a diligence conversation, not a website figure.
Why an 18-month plan?
It is the period the plan targets for reaching pilot readiness: hiring the specialist leadership, hardening the platform, obtaining independent validation, advancing the patent strategy and assembling a controlled pilot package. It is a plan horizon, not a delivery guarantee.
What is pilot readiness?
The state in which a controlled pilot could responsibly be attempted: a hardened platform, defined site and integration requirements, independent technical review, and an agreed pilot plan with the relevant parties. It is the objective of the current 18-month plan, not a present condition.
Who would the company hire?
The plan identifies three specialist leadership roles: a Technical Lead, an Aviation & Regulatory Lead and a Commercial Partnerships Lead. None is filled.
What milestones would make VHS materially more valuable?
Independent validation of the determinism and evidence properties; a signed design partnership at a real site; a completed controlled pilot producing external evidence; progression of the patent position beyond provisional; and a first connected multi-node deployment. None has occurred.
What are the principal commercial risks?
Adoption timing tied to an aviation sector that is itself early; regulatory dependency; the possibility that access control is bundled by a larger platform; long infrastructure sales cycles; unvalidated pricing; and execution risk in a small team. None of these is resolved today.
Safety, Accountability & Public Trust
Fail-closed behaviour, emergency handling, and why the final access decision is not probabilistic.
What is the core safety principle?
Fail-closed. Absence of proof is not permission. If the engine cannot establish that entry is authorized, it does not authorize entry.
Does failure default to access?
No. Failure defaults to refusal. That is the single most important behavioural commitment in the architecture.
What happens if state cannot be established?
Access is withheld. The doctrine is fail-closed: if the state of the volume, the reservation or the participant is unknown, the engine does not assume in favour of entry. UNKNOWN never becomes ACCESS GRANTED.
What is the difference between normal priority and emergency handling?
Normal priority influences the order in which valid requests are considered. Emergency handling is a classification carried on the request that raises that ordering preference under the applicable policy. Neither is an exemption from evaluation, and neither can override exclusivity.
Why make the system understandable to people outside aviation?
Because aerial activity over communities is ultimately accepted or rejected by people who do not read aviation documents. A system that can only be explained to specialists is harder to consent to.
Can someone determine afterwards why access was permitted?
Yes, that is the purpose of the evidence and replay design: re-run the recorded inputs under the policy version that applied and step through the same sequence of outcomes.
Can the public see what is happening?
The architecture includes public-facing presentation concepts for structured access. What any specific site would publish is a decision for that site, its operators and the applicable rules.
Is VHS a safety-critical certified system?
No. VHS is not certified, not FAA-approved and not operationally authorized. Independent technical and safety review is planned work that has not been completed. Nothing on this site should be read as a safety claim.
Looking for something more specific?
Additional technical, commercial, regulatory, integration and implementation questions, kept behind the curated subjects for diligence, specialist research and investor follow-up.
Filters on this page only. No external service.
Aviation & Finance Glossary
The language used across this site and the prototype. Aircraft-facing decisions and transition-volume lifecycle states are deliberately kept separate, and ARR means Annual Recurring Revenue — not Annual Network Assurance.
- Access node
- Any approved location that could connect to the VHS network — a vertiport, airport vertiport, hospital pad, rural site, logistics hub or approved private pad.
- Transition volume
- The controlled, exclusive 3D region above an access node through which an aircraft enters or leaves the structured network.
- Reservation
- A claim binding one identified operation to one resource for one bounded time interval. A precondition for access, not access itself.
- Request
- An aircraft's submitted intent to enter a transition volume in a stated window. Confers no access, no priority and no reservation.
- Authorization
- The explicit outcome the engine issues against evaluated resource state: ACCESS GRANTED, HOLD or DENY.
- ACCESS GRANTED
- The aircraft is authorized to enter the volume for one bounded interval.
- HOLD
- A temporary waiting outcome. The request is valid but one or more required conditions are not currently satisfied.
- DENY / DENIED
- DENY is the refusal action; DENIED is the aircraft-facing refused outcome, recorded with its reason.
- IDLE
- A neutral state — nothing is claimed and no decision is in progress.
- Released
- A transition-volume lifecycle state: the resource has returned to available. Never an aircraft-facing decision.
- Evidence record
- The structured fact of a decision: what was evaluated, the resource state, the versioned conditions, the outcome, the reason and the ordering.
- Deterministic replay
- Reconstruction of a past decision sequence by re-running recorded inputs through the same logic and the policy version that applied.
- Emergency priority
- Modeled sequencing preference for qualifying emergency movement, applied only after physical conflict is resolved. Prototype policy behavior, not a deployed aviation authority.
- Unauthorized conflict
- An aircraft entering a reserved transition volume without a valid authorization.
- 4D trajectory
- Three spatial dimensions plus time.
- eVTOL
- Electric Vertical Takeoff and Landing aircraft.
- AAM
- Advanced Air Mobility.
- UAS
- Unmanned Aircraft System.
- UTM
- Unmanned Aircraft System Traffic Management.
- PSU
- Provider of Services for UAM/UTM — a service provider role within the wider traffic-management ecosystem.
- FAA
- Federal Aviation Administration.
- ADS-B
- Automatic Dependent Surveillance–Broadcast.
- GPS
- Global Positioning System.
- GNSS
- Global Navigation Satellite System.
- SBAS
- Satellite-Based Augmentation System.
- GBAS
- Ground-Based Augmentation System.
- AGL
- Above Ground Level.
- SWIM
- System Wide Information Management.
- AR
- Augmented Reality.
- VR
- Virtual Reality.
- ARR
- Annual Recurring Revenue — a finance metric. Not to be confused with Annual Network Assurance, which is the name of a proposed recurring service.
- Annual Network Assurance
- The proposed recurring commercial service: software maintenance, policy updates, replay verification, evidence integrity and support. $75K–$125K per vertiport annually (proposed).
- Site Activation
- The proposed one-time engagement per vertiport: transition-volume configuration, interfaces, verification, testing and deployment. $150K–$250K (proposed).
- Network Integration
- The proposed engagement per network deployment: network engineering, airport and operator adapters, training and launch support. $300K–$750K (proposed).
Have a question we did not answer?
The architecture is on Technology, the decision model is on the VHS Engine, and the commercial context sits with Partners / Investors. If a diligence question is missing, ask it directly — an unanswered question is more useful to us than a guessed answer.
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.
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.