How It Works

Your first flight review, step by step.

Add your aircraft, upload an engine-monitor log, and review the results. This guide shows you where to start, how to check a finding, and how to share a report with your mechanic.

Start here

One aircraft. One log. Six steps.

You’ll need an AlaryIQ account, your aircraft details, and a log exported from your engine monitor. Complete any account setup prompts before you begin.

  1. 1Add aircraft
  2. 2Upload a log
  3. 3Check the import
  4. 4Start with Overview
  5. 5Examine a finding
  6. 6Save or share

Screenshots show example aircraft and flights. Select any screenshot to enlarge it.

1

Add your aircraft

AlaryIQ Aircraft page showing the Add your first aircraft button and the choice to upload a log file or create an aircraft profile
Create the aircraft profile first, then check that the correct aircraft is selected.

Create a profile

Choose Add your first aircraft and create the aircraft profile. If the aircraft is already in your Fleet, select it.

Enter the required details

Enter a tail number or aircraft label and select the propeller type. For a turbocharged engine, also enter Max TIT and Max MAP using the applicable aircraft or engine documentation.

Match the installed equipment

Add the engine and cylinder configuration and the monitor make and model. Fill in other details you know; leave optional unknowns blank. Missing information may limit some checks or require generic limits.

Before you upload

Confirm the aircraft label and monitor model. You can leave the review settings at their defaults for this first flight.

2

Upload an engine-monitor log

Upload Engine Monitor Log panel prompting the user to choose the aircraft before selecting files
Use an export that contains engine data and confirm the target aircraft before uploading.
Which monitor file should I upload?

Choose the right monitor export

Garmin EIS / TXi / G3X / GI 275 Engine/user log CSV with CHT, EGT, RPM, MAP, fuel flow, oil, voltage, and available GPS or air-data fields.
Dynon SkyView / HDX The log file with engine data. Do not upload an airdata-only export.
JPI EDM Raw .JPI file or supported decoded JPI-style CSV.
Insight G2 / G4 Insight CSV export. For twin or G4 data, confirm engine and cylinder mapping after import.
EI MVP-50P MVP-50P engine data export. Check fuel, TIT, pressure, and engine channels after import.
EI CGR-30P / 30C Select the matching CGR model in the aircraft profile. For paired data, choose CGR-30P + 30C and upload both files, together or separately. AlaryIQ pairs matching files when both are present.

Choose your file

With the aircraft selected, open the upload panel and choose your log file, folder, or supported ZIP. Start with one flight so you can check the import before adding more history.

Check the export

Use the engine-data file. An air-data, position, AHRS, or setup file alone may not contain the readings needed for an engine review.

Uploading a short flight?

Flights shorter than 10 minutes are excluded by default. Enable the option to include short flights when you intend to review a brief flight or ground run.

Start the upload

Confirm the aircraft and submit the files. AlaryIQ reads the log, imports supported flights, and prepares the analysis. Check Uploads for the result.

3

Check the import

Example: completed uploadN1234AZ
Raw file Status Flights Latest job Size Uploaded Hash Actions
2022-05-30-N1234AZ16.2.4.8600-B-USER_LOG_DATA copy.csvN1234AZ/2022-05-30-N1234AZ16.2.4.8600-B-USER_LOG_DATA copy.csv
Completed
1/1
Completed 1/1 19 MB May 1, 2026 b3a17038fd95 Reprocess
The raw file is the Dynon engine-data CSV for N1234AZ.Completed status and 1/1 flights means the upload produced one supported flight.The Reprocess button is available when the upload can be run again.

Look for completion

Open Uploads for the selected aircraft. Check the file name, status, and flight count. The example here shows a completed upload with one supported flight.

If a flight is missing

Check that you uploaded the engine-data export to the right aircraft. For a short flight, check the short-flight option. For CGR files, check the profile’s monitor model and paired files.

If import failed

Read the upload’s error details and correct the file or profile first. Use Reprocess when you need to import the same saved file again.

Then open the flight

N1234AZ Aircraft flight history page with filters, flight rows, CHT flags, trend inclusion, AI Summary, report, open, reprocess, and delete actions
Find the imported flight by date, time, and duration, then open it.

Open Flights

Find the flight you just imported. Match its date, time, duration, and source monitor, and check that analysis has completed.

Open the matching row

The selected flight opens on the dashboard. You do not need an AI Summary or a PDF report to begin reviewing it.

4

Start with Overview

N1234AZ Overview page showing health cards, operating context, Rapid CHT drop review context, sensitivity controls, and key parameter traces
Overview brings together the health cards, operating context, and charts for the selected flight.

Confirm the flight

Check the aircraft and flight at the top of the dashboard. Start with Balanced sensitivity.

Check Sensors first

Missing, noisy, or suspect readings can affect other findings. Open a sensor warning to see which channel is involved before interpreting findings that depend on it.

Choose a card to review

Look through the health cards and Operating Context. Select a finding to see what happened and where it appears in the flight.

Keep the result in context

Few or no findings means this log gave AlaryIQ little to flag. It does not establish the engine’s condition or airworthiness.

Start with Balanced sensitivity

Sensitivity changes how some deviations affect the review; it does not change the recorded data. High gives some deviations more weight, while Low reduces their influence. Some checks keep the same severity at every setting.

Judge each finding by its severity, supporting readings, and sensor quality. A finding that appears only on High is not automatically low priority.

5

Examine a finding

Review Context panel with finding details, possible causes, supporting evidence, confidence, and caveats
Review Context shows the finding, supporting readings, and any limits on the interpretation.

Read Review Context

Select a finding or health card and open its Review Context. Read the severity, affected channels, time window, confidence, and data-quality notes.

Check the possible causes

Use these as leads for further inspection. They are not diagnoses. Where percentages are shown, they express the relative weight of the listed possibilities, not the probability that a part has failed.

Follow it back to the chart

Check the recorded behavior before acting on the description. If the graph, profile, or sensor quality does not support the finding, resolve that question first.

Check the same moment in Graph Explorer

Graph Explorer with metric traces expanded and a selected zoom window
Zoom into the finding and compare the affected channel with related readings.

Find the time window

Use the dashboard graph or Graph Explorer. Show the relevant channels, filter by flight phase, and drag to zoom into the reported event.

Compare related readings

For a temperature change, look at the other cylinders and available fuel flow, RPM, and MAP. Note any power, mixture, or flight-phase change at the same time.

Describe what you can see

Aim for a specific observation: which cylinder or channel, what changed, when it happened, and whether the other readings support it. Reset the zoom to check the surrounding flight.

6

Save or share your review

Save a PDF

After reviewing the flight, choose Download PDF or the flight’s report action. Check the aircraft, date, findings, and charts before sending it to your mechanic.

Add an AI Summary if useful

An AI Summary is optional and depends on your plan and available allowance. It adds a written review of the flight; you can generate a PDF without it. An existing summary can be included in the report.

Share the interactive flight

Use Share this flight to create a read-only link when you want someone to explore the review in the app. This is separate from downloading a PDF.

Bring a specific question

For example: “Cylinder 4 ran hotter than the others during climb. Can we look at the chart together?” The report supports that discussion; inspection and maintenance decisions remain with qualified people.

When you want to go further

More tools for a closer look.

Return to these as you build flight history or have a particular question to investigate.

Adjust aircraft review settings

AlaryIQ aircraft workspace with an arrow pointing to the Settings tab and the review monitor settings displayed
The aircraft’s Settings tab controls which checks are included in its reviews.

Use the defaults to start

You do not need to customize every monitor before reviewing your first flight. Return here when you want to include or mute a particular check.

Make a deliberate change

Open Settings for the aircraft, choose the checks you want included, and select Save Settings.

Understand unavailable checks

Availability depends on the aircraft profile and available analysis data. It is not simply a list of channels in the most recent raw upload. Check the profile, imported readings, and analysis before assuming a sensor is absent.

See all review settings

Review setting options

Choose the checks that apply to your aircraft and review. Muted checks are left out of their associated flags, cards, timeline markers, and score penalties where applicable.

Engine health

Sensors
Checks whether probe traces look trustworthy before other findings lean on them.
Turbo
Reviews boost, TIT, and heat context for turbocharged-engine operation.
Oil System
Watches oil temperature and pressure for behavior that deserves follow-up.
Takeoff Enrichment
Checks whether full-power fuel flow appears adequate during takeoff.
CHT Heat
Flags cylinder-head temperature exposure that may point to heat stress.
EGT Balance
Compares exhaust gas spread so one cylinder does not hide in the average.
Cooling
Compares CHT against power and airflow to explain whether heat is expected.
Cooling Rate
Looks for rapid CHT drops that can indicate aggressive cooling.

Event detection

CHT Rhythm
Looks for repeating CHT-only motion that may separate heat behavior from mixture behavior.
EGT Rhythm
Looks for stable-window EGT wobble that may suggest combustion or valve-related review cues.
CHT/EGT Pairing
Compares paired CHT and EGT movement to see whether temperatures are moving together.
Abnormal Combustion
Flags single-cylinder CHT runaway patterns when EGT does not rise with it.
Transient Divergence
Finds moments where cylinders fan apart and then reconverge after a transient event.
Descent EGT Dropout
Checks descents for one EGT cooling sharply compared with the others.
Induction Leak
Looks for RPM, fuel-flow, or MAP context lining up with an EGT rise.
Mag Check
Reviews ignition-test EGT response when the log includes a usable mag-check window.
Carb Ice
Uses carb-temperature, OAT, and power-loss cues to surface possible carb-ice context.

Aircraft systems

Start Charge
Checks whether voltage or current recovers normally after engine start.
Electrical
Watches bus-voltage behavior for drops, spikes, or unstable charging clues.
Probe Reference
Looks for shared reference behavior that can make multiple probe channels move together.

Multi-engine

Engine Delta
Compares engines against each other and appears only for multi-engine aircraft.

Look closer at one cylinder

Cylinder 1 detail page showing cylinder health cards, heat exposure, CHT range time, cylinder distribution, and cylinder snapshot
Cylinder Detail shows heat exposure, temperature ranges, and comparisons for one cylinder.

Open Cylinder Detail

Choose a cylinder tab or health card. Compare its CHT and EGT behavior, heat exposure, and peer comparison where the log contains the required readings.

Check the probe

A suspect probe can distort the picture. Read the sensor-quality notes alongside the cylinder findings.

Replay the flight

Playback page with cockpit-style instruments, map, trace timeline, and playback controls
Playback follows the recorded flight in time. The available instruments depend on the channels in the log.

Use Playback for timing

Play, pause, scrub, or change speed to see how an engine-data change lines up with the rest of the flight.

Use the channels you have

Engine playback does not require GPS. The map needs position data, and attitude or air-data displays need their corresponding channels. Return to Graph Explorer for precise trace comparisons.

Reading the data What each card watches

Learn to read the graphs behind the cards.

Every health card watches one kind of behavior in the trace data. These samples show the shape to look for — what to notice, and what a graph on its own cannot prove.

Hot CHT

Watches how long each cylinder’s head spends in each CHT temperature band — flagging one that lives in the hot ranges more than its peers.

Cyl 4 spent the most time at 400 °F+ Cyl 1 Cyl 2 Cyl 3 Cyl 4 <375 °F 375-399 400-424 425+ °F
Each bar is one cylinder; the colored segments show how long that cylinder spent in each CHT range over the flight (cooler blue/teal → hot orange/red). Cyl 4’s long orange-and-red tail means it lived at 400 °F+ the most. Time in the hot bands is the exposure to watch — not any single peak.

Why it mattersSustained head heat is a conversation about baffling, fuel distribution, and how the engine is operated — not a number to panic over.

  • Notice which cylinder carries the most orange-and-red time, how big the gap is versus its peers, and whether that lines up with climb, high power, or a hot day.
  • Don’t conclude a specific fault from the bands alone; running warmer than peers is a prompt, not damage.
  • Check next Graph Explorer for companion traces, Cylinder Detail to localize it, and Trends to see if it repeats.

EGT Rhythm

Watches a stable-power window for one cylinder’s EGT wobbling out of step with its peers.

30 F review floor (peak-to-peak) +20 0 F -20 0s 45s 89s Cyl 3 EGT valve-pattern fit other cylinders review floor
Each cylinder’s EGT shown as its difference from the engine average inside the steady-power window. The bold wave is the flagged cylinder; the white dashed line is the fitted valve pattern. Swinging past the dashed review-floor lines is the cue — not a valve diagnosis.

Why it mattersA cylinder that will not hold a steady rhythm at stable power can point to combustion or valve behavior worth a closer look.

  • Notice the affected cylinder, that its wave swings past the review-floor lines, and that the window is genuinely stable power — not a climb, descent, or mixture change.
  • Don’t conclude a valve problem; rhythm is a screening cue, not a borescope.
  • Check next the same cylinder’s CHT, probe confidence, and whether the rhythm shows up across flights.

Sensors

Watches whether each channel is trustworthy before any other card leans on it.

CHT °F CHT 4 keeps dropping out Taxi Takeoff Climb Cruise CHT 4 (dropping out) CHT 1–3 (stable)
One CHT probe (red) keeps dropping out — cutting toward zero and recovering — while its peers track smoothly as the engine warms. The cylinder may be fine; the probe or wiring is the suspect, and findings that lean on this channel get less trust.

Why it mattersA bad probe, missing channel, or noisy signal can manufacture misleading findings elsewhere — so sensor quality is checked first.

  • Notice which channel lost trust, when in the flight, and how — a dropout, stuck stretch, out-of-range, or erratic jump — and which findings lean on that channel.
  • Don’t conclude the cylinder is failing when the more likely story is the sensor.
  • Check next which other cards depend on that channel, and treat them with lower confidence until the sensor is understood.

Operating Context

Marks flight and operating conditions — leaning, power changes, pattern work, descent, shutdown — that explain trace movement.

Operating Context is a row of chips, not findings. Each marks an event — a lean, a mag check, a descent — with its phase and time, so you can read nearby data in the right light.

Why it mattersContext cards are the antidote to false alarms: a lean, descent, pattern cycle, or shutdown explains movement that would look suspicious on its own.

  • Notice which event a card marks and which traces it lines up with.
  • Don’t conclude a context card is a fault — it usually explains the data rather than flagging it.
  • Check next whether a nearby finding sits inside one of these windows before you escalate it.

Every context card, explained

ROP
ROP Leaning

Marks a leaning pattern consistent with remaining rich of peak: fuel flow falls, EGTs rise, and no qualifying peak is detected. It can appear in climb or cruise. The pattern provides context; it does not establish the exact mixture setting.

LOP
LOP Leaning

Marks a lean-of-peak sweep: fuel flow falls, the EGTs peak in turn, then the engine settles lean of peak. A clean LOP pull is a deliberate, efficient setting; the card explains the EGT rise-then-fall so it reads as mixture management, not a fault.

M
Mag check

Looks for a runup mag check by matching the RPM drop to each cylinder’s EGT rise as a magneto is selected. A small RPM drop with an even EGT rise is expected; a weak or missing response on one cylinder is the part worth a look. (No RPM channel means it can’t be evaluated.)

S
Start charge

Checks the seconds after start — the bus should sag for cranking, then recover above the charging line. A clean recovery is the normal signature; a weak or unconfirmed one is the prompt (see the Start Charge example).

CE
CHT/EGT Pairing

Compares one cylinder’s CHT and EGT movement during steady-power windows. How tightly they move together is context for reading ignition, injector, cold-cylinder, mixture, or sensor patterns — not a verdict on its own.

H
Cylinder Harmony

Highlights the best loaded window where all cylinders’ EGTs and CHTs moved together with a steady spread. It’s a reassuring, positive signal — the engine looked well-balanced there — rather than a problem.

CHT
CHT Rhythm

Flags a repeating CHT-only wobble during steady power when fuel flow, MAP, RPM, and that cylinder’s EGT did not move with it. Because nothing else moved, it usually points to the probe, connector, bayonet seating, or very local cooling air — an instrumentation check, not combustion.

DIV
Transient Divergence

Catches short stretches where one cylinder’s EGT or CHT briefly pulled away from the rest. A brief split during a power or mixture change is usually normal; the same cylinder splitting again across flights can point to a fuel, ignition, or intake issue worth checking.

DES
Descent EGT Dropout

Marks low-power descents where one EGT cooled faster than its peers. On a throttled-back descent that’s often just airflow and reduced fuel; the card lets you weigh it against fuel flow, MAP, RPM, and whether it repeats before reading into it.

FF
Fuel-Flow Response

Checks that fuel flow moved sensibly with RPM, MAP, and percent power through a power change. Coherent movement confirms a normal transition; a flat, opposite, or noisy response is the prompt — and it keeps ordinary throttle changes from looking like engine faults.

Start Charge

Watches the seconds around engine start: the bus dips while cranking, then should climb back above the charging line as the alternator picks up the battery recharge.

Bus V start charging line 13.1 V+ cranking dip recovers & holds above the line
Demonstrates a normal cranking dip recovering above the charging line. A brief sag is expected; the graph alone does not confirm battery or alternator health.

Why it mattersA shallow recovery, a slow climb back above the charging line, or a missing recharge current spike can open a battery or charging-system conversation before it leaves you stranded.

  • Notice how deep the cranking dip goes, how quickly the bus climbs back above the charging line, and whether a recharge current (amp) spike follows the start.
  • Don’t conclude a dead battery or failed alternator from one start — cold starts sag deeper, and a single start is not a trend.
  • Check next Trends to see if recovery is slipping over time, the Electrical card for in-flight bus behavior, and a battery/charging check with your mechanic if it repeats.

Oil Pressure vs Temperature

Watches how oil pressure settles as the oil warms — once warm, the pressure samples should cluster in a tight, steady band.

middle 50% Sample density typical warm 56 psi 50 55 60 oil pressure (psi), warm samples
Demonstrates warm oil-pressure samples clustering in a tight band near the typical pressure. The center and width of the band are the read — not any single sample.

What each part means

  • Bars (sample density) — how often warm pressure landed at each value; the tall bars are where it usually sat.
  • Middle 50% — the solid inner box: half of all warm readings fall here. A narrow box means steady pressure.
  • Warm range — the dashed outer box: the full spread of warm samples, edge to edge.
  • Typical warm — the white line and dot: the median warm pressure (here 56 psi), the one number to remember.

Why it mattersWarm oil pressure that sits too low, too high, or keeps wandering instead of settling is a classic prompt to check oil level, the sender, or the pump before a trend builds.

  • Notice the typical warm pressure, the warm oil temperature, and how tight the band is — a wide or shifted band is the prompt, not any single sample.
  • Don’t conclude a pump or bearing problem from one warm-up — cold oil reads higher and more variable by design.
  • Check next Trends for the warm-pressure band over time, your aircraft’s published oil-pressure limits, and an oil-level or sender check with your mechanic if the band drifts.

Sensitivity

Changes how some deviations contribute to the review. The recorded data stays the same.

Deviation Balanced surfaces above here High also surfaces above here both flag this High only
A simplified illustration of a sensitivity-dependent check: a smaller deviation appears only on High. Actual behavior varies by check; some severity thresholds do not change with sensitivity.

Why it mattersStart with Balanced. High gives some deviations more influence; Low reduces their influence. Sensitivity is not a severity or priority ranking.

  • Notice which items or scores change when you adjust sensitivity, then inspect the supporting readings.
  • Don’t conclude a High-only item is a problem; it is an item to inspect, not proof.
  • Check next the graph to confirm a High-only item is visible, phase-relevant, and backed by clean sensors, then return to Balanced.

Worked examples Card to conversation

Four common reviews, start to finish.

Each example turns a card into something you can verify and, if needed, hand to a mechanic in plain language.

Watch

Amber CHT card

A cylinder ran hot — for example, “Cylinder 4 ran hotter in climb.”

  1. Click the CHT card and see which cylinder drives the status.
  2. Open the graph with CHT, EGT, fuel flow, RPM, MAP, and OAT visible (see the Hot CHT sample above).
  3. Decide the phase: climb, cruise, pattern work, or low-airflow ground operation.
  4. Compare Trends to see whether the same cylinder repeats.

Hand off “Cyl 4 ran ~40°F hotter in climb, repeated over three flights” — not “Cyl 4 is broken.”

Review

EGT Rhythm item

One cylinder’s EGT repeatedly rises and falls while power stays steady.

  1. Open the EGT Rhythm finding and note the affected cylinder.
  2. Inspect the highlighted stable-power window (see the EGT Rhythm sample above).
  3. Compare that cylinder’s EGT against its peers in the same window.
  4. Confirm probe confidence so a noisy sensor is not the real story.

Treat it as an item to discuss with a qualified mechanic — not a valve diagnosis read off a graph.

Sensor

Sensor warning

A channel looks missing, stuck, stepped, or noisy.

  1. Click Sensors and identify the suspect channel.
  2. Confirm whether it is missing, stuck, noisy, stepped, or out of step with companion data.
  3. Check which other findings rely on that channel.
  4. Lower your confidence in those dependent findings until the sensor is understood.

A bad probe can invent problems elsewhere — clear the sensor question before trusting the rest.

High only

Item appears only on High

An item shows up when you raise sensitivity but not on Balanced.

  1. Switch Balanced → High only when you want a deeper, exploratory pass.
  2. Note which new items appear (see the Sensitivity sample above).
  3. Open the graph and check the item is visible, phase-relevant, and backed by clean sensors.
  4. Return to Balanced for the normal owner review.

Check severity, sensor quality, and operating context. Appearing only on High does not determine an item’s importance.

Behind the scenes

How the analysis works

AlaryIQ reads the monitor export, checks sensor quality, identifies flight phases, and runs defined checks on the recorded readings. Findings include the relevant time windows, supporting readings, and any limits on the interpretation.

If you request an AI Summary, it uses the analysis results and selected flight data to build a written review. The AI can also examine compressed traces for additional observations, which are checked against the recorded samples. Relevant saved notes and available comparison-flight context may also inform the summary. Review it alongside the charts.

Health cards

Areas to check first.

Findings

Evidence-backed items to investigate, not diagnoses.

Possible causes

Possible explanations to investigate, not diagnostic probabilities.

Confidence

How strongly the available data supports the item.

Sensitivity

Adjusts how some deviations affect the review. Start with Balanced; assess severity separately.

Evidence windows

The time ranges where the behavior shows up.

Sensor quality

Whether a channel is trustworthy enough to interpret.

Operating Context

Conditions that help explain the data. These cards are not always problems.

Trends

Cross-flight comparison for the same aircraft.

AI Summary

An optional written review informed by analysis results and selected flight data.

PDF Report

A report you can save or share with your mechanic.

Read findings as questions, not verdicts: they are areas to investigate, and a clean result is not proof the engine is safe to operate or airworthy. AlaryIQ adds context to recorded data — it does not replace inspection, service data, or pilot judgment.

Start with one flight

Ready to review your first flight?

Create your account, add your aircraft, and upload an engine-monitor log.

Create your account