Add or choose an aircraft
Add an aircraft before uploading the first engine-monitor log.
How It Works
Create an aircraft, complete the profile, upload one engine-monitor flight, check the import, then use Overview, graph evidence, context, trends, and PDF reports to support a maintenance conversation.
Quick path The full workflow
Add an aircraft before uploading the first engine-monitor log.
Enable the monitors that match the aircraft, installed sensors, and review goal. Muted monitors stay out of flags, cards, timeline markers, and score penalties where applicable.
| 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 | Upload P and C together, in one ZIP, or separately. AlaryIQ pairs matching files when both are present. |
| Raw file | Status | Flights | Latest job | Size | Uploaded | Hash | Actions |
|---|---|---|---|---|---|---|---|
|
2022-05-30-N1234AZ16.2.4.8600-B-USER_LOG_DATA copy.csv
N1234AZ/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 |
Set this in the scope row at the top of the dashboard. It changes what AlaryIQ shows you, not the recorded data. The three settings:
Best starting point for most users.
Shows nearly everything, including minor or exploratory items. Useful for data-heavy review, but noisier.
Shows fewer, more significant findings.
New to the cards? See Reading the data for what each one watches.



Reading the data What each card watches
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.
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.
Why it mattersSustained head heat is a conversation about baffling, fuel distribution, and how the engine is operated — not a number to panic over.
Watches a stable-power window for one cylinder’s EGT wobbling out of step with its peers.
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.
Watches whether each channel is trustworthy before any other card leans on it.
Why it mattersA bad probe, missing channel, or noisy signal can manufacture misleading findings elsewhere — so sensor quality is checked first.
Marks flight and operating conditions — leaning, power changes, pattern work, descent, shutdown — that explain trace movement.
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.
Every context card, explained
Marks a cruise leaning window that stayed rich of peak — fuel flow eased back, EGTs rose, and no peak was crossed. That’s a normal way to lean for power and cooler heads; the card is here so a rising EGT during leaning isn’t misread as trouble.
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.
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.)
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 (the Start Charge card above shows the full read).
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.
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.
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.
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.
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.
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.
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.
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.
Watches how oil pressure settles as the oil warms — once warm, the pressure samples should cluster in a tight, steady band.
What each part means
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.
Controls how readily items surface — the same flight shows more on High and less on Low.
Why it mattersSensitivity changes what surfaces, not the recorded data. Balanced suits most owners; High is an exploratory pass; Low keeps only the most significant items.
Worked examples Card to conversation
Each example turns a card into something you can verify and, if needed, hand to a mechanic in plain language.
A cylinder ran hot — for example, “Cylinder 4 ran hotter in climb.”
Hand off “Cyl 4 ran ~40°F hotter in climb, repeated over three flights” — not “Cyl 4 is broken.”
One cylinder’s EGT will not hold a steady rhythm at stable power.
Treat it as an item to discuss with a qualified mechanic — not a valve diagnosis read off a graph.
A channel looks missing, stuck, stepped, or noisy.
A bad probe can invent problems elsewhere — clear the sensor question before trusting the rest.
An item shows up when you raise sensitivity but not on Balanced.
Treat High-only items as lower-priority evidence to inspect — not automatic problems.
Behind the scenes
AlaryIQ reads the monitor export, normalizes the channels, identifies phases and operating context, checks sensor quality, runs deterministic detectors, builds evidence windows with confidence and caveats, then uses AI to turn that bounded evidence into readable review language.
The AI is not guessing from raw log rows. The detector work happens first. The summary is a plain-language translation of structured evidence.
Areas to check first.
Evidence-backed items to investigate, not diagnoses.
Ranked inspection hypotheses.
How strongly the available data supports the item.
How readily items surface. Balanced is normal; High shows more minor items; Low shows fewer, more significant ones.
The time ranges where the behavior shows up.
Whether a channel is trustworthy enough to interpret.
Conditions that help explain the data. These cards are not always problems.
Cross-flight comparison for the same aircraft.
Plain-language review text based on deterministic evidence.
A shareable advisory evidence packet.