Aircraft virtual tour and aviation digital twin FAQ

An aircraft virtual tour is an immersive digital walkthrough created from 360° visuals and interactive navigation. It allows users to explore an aircraft remotely and can support airline marketing, passenger communication, familiarization, training, sales and technical communication.

A virtual tour focuses mainly on realistic visual exploration. An aviation digital twin can add structured information layers, documents, videos, guided workflows, role-specific modules and operational references. The depth and functionality are defined for each project.

Projects can be created for commercial airliners, regional aircraft, business jets, VIP aircraft, helicopters, historic aircraft and other aviation assets when suitable access and approvals are available.

Typical users include airlines, MROs, lessors, aircraft owners and operators, completion centers, cabin and product teams, passenger-experience teams, marketing, training, engineering, maintenance, sales and leasing teams.

Before the visit, we agree the aircraft, configuration, required areas, access conditions, timing, security requirements and intended deliverables. A capture plan is then coordinated with the customer to reduce disruption and avoid unnecessary aircraft downtime.

The duration depends on aircraft size, access, lighting, the number of cabin zones and the required detail. A focused configuration can often be captured within one working day, while larger or more complex scopes may require additional time.

Yes. Different configurations, subfleets or aircraft types can be created as separate but connected experiences. Shared design elements and modules can be reused while configuration-specific cabins and information remain clearly separated.

Existing approved material can often be integrated as supporting content. Its resolution, rights, visual consistency and suitability are reviewed first. New 360° capture is normally required when a realistic navigable aircraft interior is expected.

Depending on access and approval, the experience can include cabin classes, seats, the cockpit, galleys, lavatories, crew areas, monuments, doors, cargo-related areas and selected technical spaces. Areas can also be excluded from the agreed scope.

Hotspots and modules can contain text, images, video, PDFs, manuals, seat and service information, links, checklists, training prompts and other approved project content. The structure is adapted to the intended audience and use case.

Yes. Navigation, colors, logos, terminology and interface elements can be aligned with the customer’s brand. English, German, French and additional languages can be included when they form part of the agreed project scope.

Yes. A common aircraft environment can support different views or modules for passenger information, marketing, cabin-crew familiarization, maintenance, engineering or other teams. Access and content can be separated according to the project requirements.

Yes. The aircraft experience can be delivered through a hosted link or embedded into an airline, MRO, lessor or project website. The integration method is coordinated with the customer’s web, brand, performance and security requirements.

Yes. Depending on the project, delivery can include hosted web access, customer-hosted HTML, offline EXE packages, mobile app experiences, kiosks and interactive displays. The most suitable format depends on the operating environment and update needs.

Options can include hosting by 360air.space, website embedding, direct links and customer-hosted delivery when agreed. Hosting, maintenance, backups, availability expectations and update responsibilities are defined in the proposal.

Yes. Password protection, controlled links, internal delivery models and customer-specific release processes can be used where appropriate. Confidential information is handled according to the NDA and project-specific requirements agreed with the customer.

Airlines can present cabin products, seats, service features, Wi-Fi, entertainment, amenities and the onboard environment before travel. The experience can support route launches, cabin reveals, booking confidence, upgrade communication and airline brand storytelling.

Interactive aircraft environments can help cabin crew, cockpit crew and other teams become familiar with layouts, equipment locations, service areas and approved workflows before they enter the aircraft. They complement, but do not replace, required certified training.

The experience can provide a shared visual reference for cabin condition, retrofit planning, maintenance communication, technical coordination, customer discussions and approved documentation. The exact information layers depend on the operational need and access model.

Yes. Aircraft owners, operators, lessors, brokers and completion centers can use an immersive presentation to explain cabin layouts, materials, monuments, options and refurbishment concepts. See the broader aviation solutions for relevant use cases.

Yes. Text, documents, links and interactive content can usually be updated without rebuilding the complete experience. When the physical cabin changes, selected areas can be recaptured and additional configurations can be added as separate variants.

The timeline depends on aircraft access, the number of configurations and scenes, editing, interactive features, languages, customer inputs and the approval process. A realistic schedule is provided once the required deliverables and responsibilities are defined.

Pricing depends on the number of aircraft and configurations, capture location and access, the number of areas and scenes, interactive features, languages, custom development, delivery format, travel, hosting and update requirements. A project-specific quotation is prepared after the scope is understood.

Use the contact page to send the aircraft type and configurations, intended users, project goal, preferred delivery format, location, timing and confidentiality requirements. We will review the information, clarify the scope and prepare the next steps and proposal.

Yes. Approved renderings, CAD or 3D data, material samples, seat information, layouts and brand content can be used to create a concept or virtual-staging experience. Accuracy depends on the quality and status of the supplied material, and the finished physical cabin may require a later capture or update.

Project milestones can be defined for structure, visual design, content, language versions and final release. Customer feedback is normally consolidated through nominated contacts, and publication or delivery takes place only after the agreed approval stage has been completed.

The customer identifies the responsible source owners and approvers. 360air.space structures and implements the approved material and can flag visible inconsistencies, while responsibility for technical accuracy, commercial claims and release authorization remains with the customer.

Hosted content can usually be revised, hidden or disabled without rebuilding the complete experience. Customer-hosted or offline packages normally require an updated build and redistribution. The applicable process and response expectations are defined in the project agreement.

Hosted experiences are designed for current desktop and mobile browsers and are tested against the target platforms agreed for the project. Offline apps, kiosks and touch displays are validated for their defined hardware. Legacy browsers or specialized operating environments require separate compatibility checks.

Depending on the delivery model and privacy requirements, analytics can be configured for page views, sessions, selected hotspot interactions or campaign events. The measurement scope, consent requirements, data retention and connection to the customer’s analytics environment must be agreed before implementation.

Links, embeds and selected custom integrations with intranets, learning-management systems or single sign-on can be assessed. Feasibility depends on the available APIs, identity and security policies, customer IT access and the required user flow, so these integrations are quoted separately when needed.

The proposal defines the permitted usage, hosting model, export packages, editable content and handover material. The agreed published deliverables are included in the project scope. Editable project files, source files or extended reuse rights are included only when they are explicitly specified in the quotation or contract.

Potentially, yes. The experience can open defined records or workflows, pass agreed parameters or trigger approved functions in maintenance software such as AMOS and other customer systems. Feasibility depends entirely on the target system, available interfaces, access permissions, browser and hosting environment, and the purchaser’s IT and security requirements. This is a separately scoped option rather than a standard feature.

Yes, when the target environment allows it. The purchaser must provide the final JavaScript, technical instructions, required parameters, dependencies and expected result. 360air.space implements the script as received in the agreed location and does not rewrite, certify or assume ownership of the purchaser’s code unless separate development work is explicitly contracted.

The requested function must first be tested on a representative sample in the intended target environment. The purchaser supplies a working sample script, test access and acceptance criteria. The option should only be purchased or commissioned after the sample has demonstrated the agreed function. The test validates only the tested use case, system version, configuration and environment.

The purchaser remains responsible for the supplied script and the third-party system, API or interface, including functionality, permissions, licences, security approval, data handling, availability and compatibility after software updates. 360air.space implements the script as received and verifies the agreed sample integration. Troubleshooting caused by changed scripts, credentials, APIs, system versions or purchaser environments is outside the original scope unless included separately.