Frequently Asked Questions.

Radiant Runways is a government-grade, cloud-native SaaS platform built for airport authorities and civil aviation regulators. It centralizes aeronautical and non-aeronautical revenue management — automated billing, real-time dashboards, compliance reporting, and security intelligence — across a unified seven-module ecosystem.

Radiant Runways is designed for civil aviation authorities, airport operators, ministries of transport, and ground operations teams. Each module is purpose-built for a specific stakeholder — from airport finance teams and security officers to pilots, ABOs, and commercial airlines.

The platform currently includes seven integrated modules: Boarding Management System (BMS), Admin App, Pilot App, ABO Portal, Landing Authorization, Commercial Airline App, and SIMA (Security & Intelligence Management App). All modules share a single data model and are designed to work together seamlessly.

No. Radiant Runways is airport-first — built specifically for airport authorities and operators, not retrofitted from airline software. Unlike conventional aviation technology platforms, which are designed around airline workflows, every feature in Radiant Runways reflects the operational and regulatory needs of airports.

All modules use role-based access control (RBAC) with Multi-Factor Authentication (MFA) enforced across every user role. Access is managed by authorized admins through the Admin App, ensuring only vetted personnel can access sensitive operational and financial data.

Yes. Radiant Runways is designed for multi-airport deployment — including national-scale rollouts. SIMA provides intelligence visibility across all airports simultaneously. The platform is currently live across 15 airports.

Manual entry ensures passenger data can still be captured and validated.

Yes — biometric face matching highlights mismatches instantly.

They are escalated to Supervisor with controlled approval workflows.

Yes — every action is logged with user, timestamp, and decision.

The system ensures no passenger is missed by enabling manual capture and validation, ensuring every passenger is accounted for.

Yes — all actions including scans, escalations, approvals, and rejections are fully logged for audit and investigation purposes.

By combining biometric verification, real-time validation, and structured workflows, the system minimizes human error and ensures consistent decision-making.

Radiant Runways integrates with industry-standard flight tracking and surveillance systems to automatically monitor aircraft movements in real time. This enables the platform to detect aircraft entering airport airspace, identify unregistered aircraft, and maintain a comprehensive history of aircraft movements once registration is completed.

Yes. Radiant Runways exposes a REST API and supports standard IATA message formats for integration with airport operational databases (AODB), government border systems, airline departure control systems, and financial management platforms. Our implementation team designs the integration as part of onboarding — at no additional cost.

The Admin App is built to government-grade security standards. All users are required to authenticate with multi-factor authentication (MFA). Role-based access control ensures users can only access data relevant to their function. All actions are logged in an immutable audit trail with timestamps and actor IDs. Data is encrypted in transit and at rest.

Yes. The Admin App is designed for civil aviation authorities overseeing networks of airports. A single admin account can manage multiple airports, each with its own revenue data, user base, and operations view. The platform is currently live across 15+ airports in The Bahamas and is built for regional and national authority deployments.

When an aircraft operator registers in the system, all previously detected aircraft movements are automatically linked to their account and queued for billing. No historical revenue is lost — the system retrospectively reconciles historical flight activity, ensuring complete trip records, including timestamps, routes, and Maximum Take-Off Weight (MTOW) data, are available for accurate billing and reporting.

Without a registered profile, pilots and aircraft are invisible to the system — which means no tracking, no compliance verification, and no billing. Registration links every pilot to their aircraft and every aircraft movement to a revenue event. It's the foundation of operational accountability in general aviation.

By requiring every pilot and aircraft to register before operating, the system ensures no landing, departure, or overnight stay goes untracked. Every movement is linked to a registered owner and a billing event — closing the revenue gap that unregistered general aviation creates. Airports stop losing fees they were never even aware they were owed.

The system is designed to ensure that all aircraft must be registered and approved before operations. Unregistered aircraft are flagged, and their movements cannot be linked to a billing or compliance record. Combined with integrated flight tracking in the Admin App, the airport authority gains visibility even over aircraft that haven't registered — enabling proactive enforcement.

Registration requires a valid passport and pilot license. Both are uploaded directly within the app. The system tracks expiry dates and alerts pilots when documents are approaching renewal — so compliance doesn't lapse between registration and active operations.

Once an aircraft is registered and approved, every trip created through the app is linked to that aircraft's profile. Movements are tracked through trip creation, escort requests, and after-hours approvals — all of which feed into the airport authority's Admin App. Integrated flight tracking provides an additional layer of verification for aircraft movements at the airport.

Yes, based on workflow stage and approvals.

It captures real-time aircraft movement directly from devices, eliminating manual errors.

Discrepancies are flagged instantly for corrective action.

Yes, invoices are generated monthly through background jobs.