features

Flight status

Airport trips matched before dispatch

Flight status lives inside the reservation workflow. The admin app checks airline code, flight number, service type, pickup and drop-off context, then stores matched flight details so dispatchers and drivers stay aligned.

IATA/ICAO Airline selection stores both code systems
36h gate Future flights can be queued for later checking
ETA/ETD Matched schedules include live timing context
Airport fit Origin and destination airports are cross-checked
Airline search Flight number Terminal and gate Schedule match

Flight workflow

Check the flight where the reservation is created

When a flight is entered, the system normalizes the flight number, chooses a schedule window based on airport direction, searches flight schedules, and stores a flight pack with origin and destination airport data.

01

Select airline

The reservation stores airline name plus IATA and ICAO codes for cleaner matching.

02

Enter flight number

Whitespace is stripped before schedule lookup to avoid preventable mismatch errors.

03

Match by trip type

From-airport and to-airport jobs use different time windows to find the right schedule.

04

Share status

Matched origin, destination, terminal, gate, ETA, and status can flow to operations.

Admin surfaces

Flight matching is embedded in reservation logic

The admin reservation screens document airline, flight number, no-match states, queued checks, matched flight cards, departure and arrival detail, terminal, gate, bag claim, and timezone context.

Service-type windows

Lookup windows change for from-airport, to-airport, and non-airport service types.

Queued verification

Flights too far in the future can be marked for automatic checking closer to departure.

Airport context

Origin and destination airport records attach to the matched schedule.

Mismatch feedback

No-match states ask staff to double-check date, time, location, airline, and flight number.

Operational updates

Status, ETA, terminal, and gate data reduce dispatcher calls and driver uncertainty.

Reservation sync

The flight pack stays inside the reservation instead of living in a separate checklist.

Controls that matter

Flight fields visible in reservation creation

Airline Airline name, IATA code, ICAO code
Flight number Required number with invalid and no-match states
Schedule Departure, arrival, timezone, ETA, and ETD
Airport detail Origin, destination, terminal, gate, and bag claim
Queue logic Automatic check can be delayed when the date is outside the lookup window