Aircraft Parking & Hangar Management Software
Know what is available before you assign the stand.
Manage FBO ramp, remote and hangar spaces with a clear booking calendar. Record dimensions, restrictions, occupancy windows and applicable rates against each parking space and aircraft visit.
Aircraft space is a finite resource
A stand may be free now but booked overnight. A hangar may have an aircraft-size restriction. FlightStratix keeps space definitions and booking dates together so the next allocation is easier to review.
Built around the way you work
Each capability is part of the connected FlightStratix workspace.
Define each space
Record location, type, size/weight limits, door dimensions, towing needs, restrictions and active status.
Book against the aircraft visit
Attach a tail, customer, movement and booking window to a selected space with its charging unit and currency.
See conflicts on the calendar
Review a 14-day Gantt-style occupancy view and identify overlapping bookings before confirming changes.
Close and bill parking
Track open and closed bookings, applicable day/night/hour/movement rates and invoice linkage.
From start to finish
Parking and hangar bookings with fit, timing and billing context
Know which positions are occupied, which aircraft fit and which bookings still need closing.
Create accurate space records
Define ramp positions, hangar bays and remote stands using dimensional and operational limits, including wingspan, length, height, weight, door clearance and tow requirements. A space can have its own default currency and hourly, daily, nightly or movement rate.
Booking linked to the aircraft visit
Associate a parking booking with the movement, tail, customer, aircraft type, chosen space and UTC start/end period. A booking can also be created manually when the aircraft is not yet part of a standard handling request.
See collisions before they become apron surprises
Use the 14-day occupancy calendar to scan ramp and hangar allocations; overlapping reservations surface as conflicts. Bookings and spaces remain visible together so the coordinator does not need a separate whiteboard.
Charge for actual space use
Close a booking with its billed units and agreed rate. Closed parking records can feed the FBO billing queue alongside finalised fuel and confirmed ramp charges. This preserves a traceable source for the resulting invoice line.
Manage stand and hangar capacity with operational restrictions
A parking space is more than an empty rectangle
Create ramp, remote and hangar spaces with physical and operational characteristics: maximum wingspan, length, height, weight or aircraft category, hangar door dimensions, towing requirement and local restrictions. An active/inactive state prevents unavailable spaces from being treated as normal inventory. Those fields matter when the person accepting a request must decide whether a given aircraft can use a particular stand or bay, rather than relying on a rough spreadsheet note.
Reservations connect an aircraft to a specific time window
A parking booking records the relevant tail, aircraft type, operator/customer, assigned space, start and end, charging unit, currency and status. Bookings may originate from a ramp movement or be created manually. The 14-day calendar displays spaces as rows and days as columns, with bookings marked by status. Overlap detection flags conflicting time windows; operational restrictions and staff judgement still determine whether the proposed allocation is suitable.
Keep the commercial consequence of occupancy visible
Each space can hold a default rate charged by night, day, hour or movement. The booking records billed units and its progression from open to closed, attached to draft invoice or invoiced. Once eligible, a closed booking can enter the FBO billing builder alongside fuel and other station services. The system connects a commercial charge to the source booking, rather than expecting accounts to recreate occupied nights after departure.
Coordinate parking with the aircraft visit
The handling workspace treats parking as a stage in the visit. The ramp board can show the aircraft's assigned stand or hangar, and staff can enter the parking workflow from the active visit context. This reduces the risk of a CSR confirming an aircraft movement while the space allocation is left in a separate calendar. It is still a planning and tracking tool, not an airport authority stand-clearance system.
Multi-location visibility without inventing a network optimiser
Fx FBO supports multiple configured FBO locations with ICAO/IATA identifiers, ramp spots, hangar bays and local contact details. A location-specific inventory should be maintained for each station. The source documents support managing those records; they do not establish automatic cross-location relocation suggestions, GIS stand drawings or automated hangar-door clearance sensing.
Keep each booking connected to the movement.
Review availability before assigning space
Check the stand or hangar booking against the intended arrival and departure. Keeping the booking beside the movement helps the station review overlaps and communicate a change without maintaining a second allocation list.
Explore movement and ramp coordinationCarry the booking into the commercial record
Parking and hangar activity can create charges that depend on the recorded booking. Keep the operational dates and source activity accessible when preparing station billing, especially when a planned departure changes.
Connect parking with station billing- Define inventorySet up spaces and limitsComplete
- Allocate spaceAssign to aircraft visitComplete
- 03Review overlapsCheck the occupancy calendarIn review
- 04Close bookingEnd the occupancy periodPending
- 05Prepare chargesSend to FBO billingPending
See it in context
An overnight request at a full hangar
A customer asks for heated hangar parking for two nights. The CSR checks the aircraft dimensions against suitable bays, reviews the 14-day calendar and sees that the first choice overlaps an existing booking. A different available space can be selected and the booking linked to the visit. After the stay, the recorded billed units become available for invoicing through FBO billing.
An operational example
An operator requests a heated hangar for a late-arriving aircraft. The FBO checks height and door-width restrictions, finds a suitable bay and confirms a two-night booking. A later request collides with that bay on the calendar, so staff allocate another space before arrival. The original booking is closed and charged when the aircraft leaves.
Where it fits in FlightStratix
Frequently Asked Questions
Does the system check hangar dimensions?
The stored space records include physical limits and restrictions, and the FBO platform has aircraft fit rules. Accurate results depend on the aircraft and hangar data entered.
Can I bill by night or hour?
Parking rate units include night, day, hour and movement. Billing follows the configured booking and billed units.
Can we manage hangars and outside stands?
Yes. The FBO parking inventory supports ramp, hangar and remote space types.
Is this a 3D hangar-layout system?
No such 3D layout capability is established by the supplied feature reference. This page covers the documented inventory, bookings and calendar.
Explore FlightStratix solutions
Make parking availability and billing traceable.Book an Fx FBO demo.
Book a 30-minute walkthrough tailored to your operation.