← Back to ThruFly
The platform

Operational intelligence, built around the crew.

ThruFly is designed to put the turn on the crew's own device and give leaders a timestamped view as it happens. Four parts work together, from the first step on the ramp to the pattern across your station.

Four parts

What ThruFly is designed to do.

ThruFly is pre-pilot. This page describes how the platform is designed to work, not results. Illustrations are not product screens.

Turn Procedures

Step-by-step turnaround procedures on the crew member's own device.

  • Procedures set up for your station, one or two to start
  • Each step timestamped when the crew member completes it
  • Designed to keep working when the connection drops

Crew & Equipment

Who is on which turn, and what they are using.

  • Crew assigned to each turn
  • Equipment shown as ready, in use or missing
  • Fewer radio calls to find people and equipment

Station View

A live view of the turns in progress.

  • Every turn and its progress, in one place
  • Issues flagged while the aircraft is still on stand
  • Visibility for the station lead and operations

Operational Intelligence

The record, turned into insight you can act on.

  • A timestamped record of who did what, as the foundation
  • Station health and early risk flags while the aircraft is on stand
  • Patterns across turns, stands and shifts to measure and improve performance
Where it runs, and how it is built

On the device in the crew's hand.

Platforms

  • iOS and Android
  • Phones and tablets
  • Designed to keep working offline, then catch up when coverage returns

Standards

  • Turn procedures designed to align with IATA ground handling practice: the Airport Handling Manual (AHM) and the Standard Ground Handling Agreement (SGHA)
  • Configured to each operator's own procedures and safety rules
  • No third-party certifications yet, such as SOC 2 or ISO 27001

Aligned by design, not certified. IATA does not certify software of this kind.

The Connected Turnaround

One operational picture, from arrival to departure.

Every stage of the turn shows who is working, what equipment is assigned, what has been verified and when.

  1. Arrival

    • Active crew
    • Equipment assigned
    • Compliance verified
    • Timestamp captured
  2. Marshal

    • Active crew
    • Equipment assigned
    • Compliance verified
    • Timestamp captured
  3. Bags

    • Active crew
    • Equipment assigned
    • Compliance verified
    • Timestamp captured
  4. Fuel

    • Active crew
    • Equipment assigned
    • Compliance verified
    • Timestamp captured
  5. Cabin

    • Active crew
    • Equipment assigned
    • Compliance verified
    • Timestamp captured
  6. Pushback

    • Active crew
    • Equipment assigned
    • Compliance verified
    • Timestamp captured
  7. Departure

    • Active crew
    • Equipment assigned
    • Compliance verified
    • Timestamp captured

Illustrative example with invented status. Not a product screen.

The loopCoordinateExecuteVerifyAnalyzeImprove↺
Designed to work offline

Ramp coverage is never guaranteed. ThruFly is designed to keep crews working when the connection drops.

Mobile-first

Built around the phone or tablet in a crew member's hand, not a desk.

Timestamped at the source

Each action is recorded as it happens, creating a verifiable operational record.

Task by task

The same work, with a record.

Examples of how common ramp tasks often run today, and how ThruFly is designed to handle them. Practices vary by station.

TaskHow it often runs todayHow ThruFly is designed to handle it
Reporting damage or an issueRadioed to a lead, written up after the turn, with the timeline rebuilt later.Logged on the device the moment it is found, timestamped and visible to the station lead.
Confirming a step was doneA verbal "done" or a paper tick.Marked complete by the crew member, with the time recorded.
Finding equipmentRadio calls and walking the ramp.Equipment assigned to the turn, with its status shown.
Handing over between shiftsBriefed in person, with details easily lost.Open items and turn status visible on the next shift's devices.
Reviewing a delay afterwardsPiecing together radio logs and memory.A timestamped record of the turn to review.

Illustrative. Not a product screen.

Operational outcomes

Designed around operational outcomes.

The direction ThruFly is built to move each measure. In a pilot, we agree the metrics before we start.

Visibility

Monitor turnaround progress as the work happens.

Without it: delays and communication gaps are found too late.

Accountability

Know which crew completed what, and when.

Without it: tasks are hard to attribute or verify.

Compliance

Maintain documented, verifiable records for audits.

Without it: audit readiness is reactive, not continuous.

Performance

Improve awareness across crews and shifts to help reduce turnaround delays.

Without it: station performance goes unmeasured.

See it on your own ramp.

The easiest way to evaluate ThruFly is a small, well-defined pilot. We agree the metrics, data ownership and exit terms in writing first.