Home/Workflows/Contingency operations
Operations · Contingency

When the primary stops,
the numbers do not.

A browser on whatever device is to hand reaches the same engine and the same dataset, so a performance answer stays available and the record stays continuous.

Overview

The same answer by another route

Flight deck events sit above the line and dispatch events below it, from the moment the primary application is unavailable to the return to normal.

CONTINGENCY · FALLBACK PATH
STARTCOMPLETEFLIGHT DECKDISPATCHPrimary downBrowser openedResult in handBack to normalDesk notifiedDesk calculatesRecorded

No second dataset

The fallback resolves against the engine and dataset the operation already flies with, so the figures match the primary application.

Whatever device is to hand

A browser session runs on the equipment available at the time, without an installation step at the moment it is needed.

The record has no gap

A contingency calculation is retained like any other, so the sequence of a flight stays complete.

Step by step

From an unavailable application to a retained result

What the platform provides when the primary route is not available, and what the other side holds while it happens.

Flight deckDispatch
01Event

The primary application is unavailable

Whatever the cause, the need for a performance answer does not pause, and the fallback route is provisioned in advance and ready to use.

  • Fallback provisioned ahead of the event
  • No installation step at the moment it is needed
  • Available to the flight deck and to the desk
EVENT

The desk sees the event

02Fallback

A browser on the equipment available

A browser session on whatever device is to hand reaches the platform, with the same inputs and the same limits as the primary route.

  • Runs in a browser on available equipment
  • Same inputs and same limits as the primary route
  • No local data to keep current
FALLBACK

Desk route available in parallel

03Calculation

The same engine, the same dataset

The calculation resolves against the engine and dataset version the operation is flying, so the result matches the one the primary application would have produced.

  • Resolved against the live dataset version
  • Registration-level configuration carried through
  • Result identifies the data behind it
CALCULATION

Same dataset version at the desk

Figures reach the flight deck

DESK PATH
04Desk path

The dispatcher route stays open

Where procedure calls for it, the desk produces the figures and the exchange with the flight deck is captured as it happens.

  • Desk-produced figures available on the same engine
  • Exchange with the flight deck captured
  • Verification step recorded with the result

Verification visible on the EFB

VERIFICATION
05Verification

The exchange is verified and captured

Where figures pass between the desk and the flight deck, the verification step is captured with the result it applies to.

  • Verification recorded against the result
  • Both parties resolve to the same figures
  • Captured at the moment it happens
06Return

Back to the primary route

When the primary application is available again, the flight continues on it, and the contingency work is already part of the same record.

  • Return to the primary route without re-entry
  • Contingency results already in the record
  • No reconciliation step on return
RETURN

Desk sees the return to normal

ON BLOCKS
07On blocks

The record stays continuous

The contingency session and the results it produced are retained with the flight, so the sequence reads without a gap.

  • Contingency calculations retained with the flight
  • Session identified as contingency in the record
  • Available for operational review
CONTINGENCY · SESSION
PRIMARY
Unavailable
LOGGED
FALLBACK
Browser session
ACTIVE
ENGINE
Same dataset version
CONFIRMED
RESULT
Retained
TIMESTAMPED
Evidence

A flight with no gap in it

A contingency session is retained like any other calculation, so the record of a flight is complete whichever route produced the numbers.

  • Contingency calculations retained with the flight
  • Session identified as contingency in the record
  • Dataset version recorded against the result
  • One record covering the flight deck and the desk

Provision the fallback before you need it

Talk to our engineers about how a contingency route fits your procedures and your existing EFB arrangements.