Owner: use username DScott and your existing password. Staff: use your individual username and password.
Your management workspace starts here. Website Studio is writable; remaining departments are transparent roadmaps, not simulated live admin controls.
Edit homepage content, colors, typography, layout and section visibility without opening code.
View the existing public system health endpoint.
System health ↗Future integration: communications service health, station settings, and message history.
Future module: aircraft service records and virtual dispatch availability.
Update your personal details and credentials without contacting the Owner. Your airline role and maintenance privileges cannot be changed here.
Changes are saved on this server and become visible to visitors after a page refresh.
This foundation saves to private/studio.json. That file needs to be included in your deployment backups. Font and layout presets are available; image uploads and a drag-and-drop page builder are planned for later.
Manage and publish content for your airline. Drafts stay private until published.
Import an existing page into the editor to replace it with your own published content. You can also hide or restore any original page. This does not erase your own articles.
Content is saved in private/content.json. Keep this file when upgrading and include it in your backups. Knowledge Base documents and external links are supported. Files are stored in persistent data and included in management backups.
Check the real status of connected services. Diagnostic checks happen securely on the server; no credentials or access tokens are sent to the browser. Only Administrators and the Owner can view this dashboard.
Connection results will appear here.
Manage simulated aircraft utilization and inspections, separately from vAMSYS. Maintenance Technicians can work discrepancies; Maintenance Leads may update records and release aircraft. Owner controls automatic synchronization. Nothing here grounds an aircraft in Phoenix.
Opt in to credit flight hours and one landing cycle to aircraft with an existing maintenance record. Tracking starts when enabled; only PIREPs submitted and accepted afterward are eligible. Resuming after a pause starts a new eligibility window. No changes to bookings or aircraft availability.
Loading tracking status…
The vAMSYS Operations API supports the actual Hide in Phoenix setting. Select an aircraft below, then explicitly hide or reveal it. An unresolved grounding order or due inspection blocks reveal. This changes real virtual-airline booking availability.
Report simulated defects, investigate, record repairs and authorize return to virtual service. Grounding flags are informational in vDAL.to; Phoenix booking remains unaffected.
Review pilot reports before creating a work order. Pilot reports alone never ground an aircraft.
Review virtual maintenance record changes, work-order events, releases and accepted PIREP utilization.
This is a virtual maintenance log. Manual initial values are supported; after opt-in, newly accepted PIREPs automatically add flight hours and cycles. Return to service is authorized using the documented work-order workflow. Data is saved in persistent maintenance.json and included in Management Backups.
Create individual accounts. Moderators can manage drafts, Administrators can publish and manage content, and only the Owner can change branding and staff access.
The Owner role is reserved for DScott. Email addresses are contact information only; no mailboxes or outgoing emails are created. Staff accounts are saved in private/staff.json; keep this file during upgrades.
Review the prepared changelog before a deployment. After the approved version is live, Owner can send one update announcement to all pilots and staff. The notification links to the public changelog.
Owner-only management data protection and release tracking. Code deployments and code rollbacks are not available here.
Create a labeled server-side management snapshot before a release. Snapshots preserve staff accounts, content, branding and settings. They do not back up code, .env, or live flight caches.
Download a portable encrypted-at-rest-by-you management archive. Store securely: it contains sensitive staff password hashes.
Restoring replaces saved management data and signs everyone out. A pre-restore snapshot is saved locally. This does not roll back site code.