17:04 fetchyfox.com ↗
Advertisement Paid promotional content from KYNOURA HOLDINGS LTD. Not connected to any airport operator, airline or government agency. Disclosure

FetchyFox · Airport Operations Platform · Canada

One forecast for the airport’s hardest season.

Snow, wind and visibility decide how a Canadian terminal staffs, trades and moves. FetchyFox folds screening, car parking and concession data into a single forecasting engine, so the morning rush is anticipated rather than absorbed — deployed in weeks, on the headcount the airport already has. Capability details live on fetchyfox.com.

See what FetchyFox forecasts Open the winter file

One feed, curb to gate · Live in weeks · SOC 2 controls underneath

SCREENING

The queue, modelled

Checkpoint demand is projected from the conditions of the day, so rosters move before the line forms.

CAR PARKS

Fill and price, live

Deck occupancy and pricing follow the arriving wave in real time, not in tomorrow’s report.

CONCESSIONS

Trade as it happens

Takings from every outlet arrive on one feed, reconciled without the month-end merge.

A snow-covered airport runway at first light, cleared lines running towards the horizon
Winter is a forecasting problem long before it becomes a clearing problem.
Sponsored Article

This page is paid promotional content created by KYNOURA HOLDINGS LTD. All product claims are the sponsor’s own statements. This is not an independent news article.

The winter file

What the desk reads before the first departure

A winter morning is settled by figures that usually sit in separate rooms: the state of the runways, the shape of the screening wave, deck occupancy and takings. The winter file is what those figures look like on one page.

Runway state, illustrative winter morning
Runway Surface Code Braking Trend
06L/24R Swept, packed snow at the shoulders 4 good 0.41 Improving
06R/24L Dry, cleared to full width 6 dry 0.58 Steady
10/28 Light cover, sweep under way 3 medium 0.29 Watching
15/33 Cleared, frost at the threshold 5 good 0.47 Steady

Illustrative conditions only. The figures an airport acts on come from its own systems — the platform reads them and projects what they are about to become.

TYPE I

The hot wash

Applied heated, straight off the truck. The clock on that aircraft starts as the fluid runs off the wing.

TYPE IV

The long coat

The thickened fluid with the longer window, and the one snowfall rate eats into first.

THE CLOCK

Holdover, kept beside the forecast

Snow rate, wind and fluid type set the window the crew works against. The desk keeps that window where the day’s plan is made.

Clearance window

The fifty minutes a snow event turns on

A sweep is choreographed long before the first plough moves. On the desk every step carries a time against it, and a forecast behind it.

03:55

Snow begins over the field

The sweep plan is already posted, with the window the crew will work inside.

04:10

06L/24R comes off the board

Traffic moves to the parallel while the ploughs line up at the holding point.

04:22

Convoy sweep, full length

Ploughs run in echelon centreline to edge, with the shoulders taken last.

04:35

Friction pass

A decelerometer run over the cleared surface sets the runway condition code.

04:48

Back in service

The code is published and the first arrival is still ninety minutes away.

Illustrative sequence, shown to explain how a clearance window is run.

How it works

How the winter picture gets built

Three moves — and none of them ask the airport to give up what it already runs.

01

Bring the feeds together

Screening, car parking and point-of-sale data join one layer. Nothing on the floor is swapped out for it.

02

Project the morning

Throughput, occupancy and takings are carried hours forward, so the shape of the day is known before it lands.

03

Move the shift early

Rosters, pricing and passenger messaging shift while there is still time for the change to matter.

The platform

Six things the desk leans on

Capabilities across operations, revenue and the passenger side, all reading from the same feed.

CAP-01

Screening throughput

Demand at the checkpoints modelled ahead of the wave, so staffing lands where the crowd is going to be.

CAP-02

Parking yield

Deck occupancy and pricing in one view, moving as cars arrive and leave through the day.

CAP-03

Terminal flow

Movement through the concourses read forward, so crowding arrives as a forecast instead of a surprise.

CAP-04

Weather disruption analysis

What a storm does to gates, staffing and trade, worked out while the storm is still over the field.

CAP-05

Spend per departing passenger

Takings across every outlet, live on one feed, with no month-end merge to wait for.

CAP-06

Screens, not downloads

Journey information pushed to the terminal’s own displays. Travellers install nothing to be guided.

Jet bridges and an aircraft at a snow-covered terminal apron in the blue light of dusk
Airside at the change of light — one feed underneath all of it.
Why it exists

Three teams, one snowfall

At 03:55 the snow is still only weather. By 05:30 it has turned into a staffing question at the checkpoint, a pricing question in the car park and a sales problem in every cafe past security — three problems, three systems, one snowfall.

That is the seam the platform was built to close. Winter is where it shows most plainly: rosters are set from a forecast nobody shares, the deck is watched by eye until it fills, and the tills are counted weeks after the passengers went home.

The snow was the same for every desk in the building. The picture of it was not.
— from the FetchyFox platform briefing

FetchyFox runs the feeds those three desks already keep as one: throughput, occupancy and takings carried forward, conditions folded into the model, and the reporting assembled without anyone sitting up over spreadsheets at dawn.

Deployment is measured in weeks and runs on the team already in place. The full capability list, terms and pricing live on fetchyfox.com.

Two airport workers clearing snow from an apron beside a snow plough blade
Ground crew working the apron between sweeps.
What changes

The same winter morning, run two ways

Without a shared feed On the desk
Rosters built from last winter’s guess Staffing follows a modelled wave
The deck discovered once it is full Occupancy and price followed live
Takings counted at month end Revenue visible while the day trades
Spreadsheets merged by hand at dawn One board, assembled on its own
Next step

See FetchyFox at work, in full

The full capability list, deployment terms and case material live on FetchyFox’s own site. There is no form here and nothing is asked of you — anything worth discussing is handled over there.

Open fetchyfox.com

No payment details on this page · This page is sponsored content · Service details are on fetchyfox.com

Questions

What operators ask first

What does a roll-out actually involve?

A pilot terminal goes first: the feeds are connected, then the forecasts are checked against the weeks that follow before the platform spreads across the field. The systems already on the floor stay where they are.

Is equipment on the floor replaced?

No. Point-of-sale and gate systems are read, not swapped. The platform sits above what the airport already operates.

How is passenger data treated?

Passenger details are guarded, the airport keeps ownership of its own commercial figures, and SOC 2-compliant controls sit underneath the whole stack. Screens that face travellers are built to WCAG accessibility standards.

Do travellers need to install anything?

Nothing at all. Information reaches the terminal’s own screens — gate boards, wayfinding, assistance points.

Will it add to the payroll?

It is designed to run without extra people. Forecasts, reporting and reconciliation that once took analyst hours assemble themselves as the platform switches on.

Who should I contact about this page?

KYNOURA HOLDINGS LTD, Agias Phulaxeos 67 (Drakos House) Office 4, 3025 Limassol, Cyprus. Company No. HE 360375 · VAT CY10360375N. [email protected]