Handlers, hotels, catering and airport risk — organised per flight

The problem

Every flight to a new airport means a dozen emails: handler, hotel, catering, transfer, slot. Airport information is scattered between websites, old briefings and the memory of the most senior captain, and the risk assessment lives in a Word file.

How BXI solves it

In BXI, services are tabs of the flight. Handler, hotel and catering requests (and cancellations) go out from templates; favourite handlers are remembered per airport; crews see handler phone numbers, hotel and transfer details in their app.

Airports are enriched with AvioWiki data — opening hours, providers, runways, operational notes — and the Airport Risk Assessment categorises each airport per aircraft type with a weighted questionnaire and immutable history.

Key capabilities

• Handler registry with favourites; handler requests and cancellations by email template.
• Hotel, catering and transfer providers per flight, with catering inventory.
• Airport registry enriched from AvioWiki (hours, providers, runways, notes) and Air Support PPS.
• Airport Risk Assessment: category A/B/C per aircraft type, weighted questions, forced categories, immutable history, PDF and Word output.
• Slot requests tracked as flight checklist tasks.
• Crew see handlers (tap-to-call), hotel and transfer details in BXI Mobile.

What it changes in your day

Organising a trip becomes a checklist instead of an inbox. When an inspector asks how you assessed a category C airport, the answer is a dated PDF, not a search through email.

Where Handling, Airports & Risk sits in BXI

Handling sits on the flight record from Flight Planning, feeds the briefing PDF and the crew app, and uses airport data shared with the Certifications module for airport qualifications.