1. Select your station
Use the top station switcher to set VNO, KUN, or another licensed station. All live data and workflows follow this context.
Skyelan Help Center
Start fast and understand every core workflow
This page is a practical user guide for the real product experience: what each section means, what actions are available, and how teams should operate.
Operating rule
If a change can impact flights, passengers, stands, or partners, do not leave it in chat only. Turn it into an action: Task, Incident, or ACK.
Clear owner Clear due time Clear status
Quick Start
First 10 minutes in Skyelan
2. Open Live Flights
Pick one active flight from the board and work from its workspace: notes, tasks, incidents, alerts, and coordination.
3. Turn updates into actions
Do not leave operational changes in chat only. Convert each change into an owned action with priority and due time.
4. Coordinate in Connect
Use role-based channels for teams and partners. For critical updates, use ACK and incident workflows.
Features
What each module does
Operations Overview
1Top-level station situation across flights, tasks, incidents, and channels.2Command Queue surfaces highest-impact items first.3Fast route into active flight workspaces and operations.
Live Flights
1Real-time arrivals/departures with status, ETA/STA, stand/gate, and team.2Filters for arrivals, departures, delayed, followed, and personal focus.3Direct actions: add note, create task, report incident, follow.
Live Map
1Live positions, route lines, and risk overlays for dispatch visibility.2Click a flight to open quick context before full workspace.3Designed for control room awareness and shift handovers.
Tasks
1Workflow by status: To Do, In Progress, Waiting, Done, Overdue.2Assign by person, team, priority, and due time.3Track ownership and updates with clear audit trail.
Connect
1Secure role-based channels across internal teams and partners.2Supports pinned messages, files, direct messages, and incident channels.3Built as an operations communication layer, not generic chat.
Incidents
1Create, assign, track, and resolve operational incidents.2Link incidents to flights, stands, notes, and tasks.3Keep complete history for reporting and post-incident review.
Board Legend
How to read core elements
Scheduled, Boarding, Landed, Delayed, In Progress indicate the current operational state.
STA is planned time, ETA is expected time. Delta shows impact in minutes.
Assigned handling location. Conflicts should move into Task + Connect + Incident when critical.
Pins a flight into your watchlist and raises its visibility.
Confirmation flow for critical updates with accountability trail.
Admin, Manager, Member, and Partner roles control visibility and actions.
Help Center (FAQ)
Frequently asked questions
Where should a new user start?
Launch the onboarding tour, choose the station, open Live Flights, select one active flight, then create your first note or task.
How is Skyelan different from a flight tracker?
Skyelan is action-first. It does not stop at visibility: each update can become a task, incident, alert, or accountable team communication.
When should I use Incident instead of Task?
Use Task for routine execution. Use Incident when safety, SLA, passenger flow, stand conflicts, or official auditability is involved.
How should partner access be managed?
Create partner-specific roles and channels with least-privilege access by station and by operational need.
Is the system mobile-friendly?
Yes. Mobile flows are optimized for Live Flights, Connect, ACK, and fast actions from flight workspace.
How do we keep operations secure?
Use role-based permissions, domain policy, strong passwords, regular role reviews, and ACK for critical communication.
Ready to test live workflows?
Run one full scenario end-to-end: flight update, task assignment, channel update, and ACK.