Track 06 / United States market entry

Sequence the approvals before the launch date sequences the work.

U.S. entry is a system-of-systems project. The fastest credible path aligns the aircraft, operator, people, infrastructure, airspace, local approvals, commercial model, and safety evidence early.

Market-entry sequence

Define the mission

Specify passenger, cargo, medical, regional, or special mission; routes; payload; weather; utilization; and public benefit before selecting infrastructure or promising service.

Map approval paths

Separate aircraft certification, production, airworthiness, operator authority, personnel qualification, airport/vertiport work, environmental review, and state/local approvals.

Build the operating concept

Define operational control, release information, energy decisions, maintenance, passenger flow, alternates, irregular operations, and accountable ownership.

Create the training and SMS system

Qualify the initial cadre, standardize instructors and evaluators, control records, assess change risk, and connect early operational data to corrective action.

Validate infrastructure and interfaces

Test the full aircraft turnaround, charging, ground movement, ATC, weather, emergency, passenger, and recovery sequence at the intended site.

Enter service in controlled stages

Use limited routes and conditions, defined expansion gates, daily performance review, disciplined configuration control, and objective evidence before scaling.

The central discipline

Do not use one milestone as evidence that the whole system is ready.

A type-certification milestone does not approve an operator. A Part 135 certificate does not approve a new aircraft or route. A vertiport design does not prove utility capacity or emergency readiness. An aircraft order does not create a qualified workforce.

Manage each workstream separately, then control the interfaces between them through one integrated readiness plan.

Readiness evidence

The review should show the current state, the source of truth, the responsible owner, the next decision, and the evidence required for closure.

WorkstreamEvidence question

AircraftWhat configuration, limitations, certification status, and support assumptions are authoritative?

OperatorWhat authority, manuals, programs, management, and records are required for the proposed operation?

PeopleWho must be trained, checked, authorized, standardized, and kept current?

MaintenanceWhich inspection, training, tracking, reliability, battery, software, parts, and vendor controls must be established?

InfrastructureWhich site, energy, fire, access, security, and contingency controls must be proven?

AirspaceHow will the route work in actual traffic, weather, communications, and diversion conditions?

CommercialDoes utilization, turnaround, payload, reliability, and demand remain viable under operating constraints?

Part 135 case study

Should the entrant build a new certificate or use an existing operator?

The comparative case study explains why an established certificate holder may offer the stronger initial path, what advantages it actually provides, and why the 25-hour proving-test requirement must not be mistaken for the entire aircraft-addition process.

Read the Part 135 entry study ↗

Authoritative starting points

Use current source material and document every assumption.

Build a market-entry readiness plan ↗