For one person, a group or a whole company — a new account sees only the data it adds, it’s a blank sheet. Leave the switch off for your own individual login, or switch it on and name a new group / company for a shared one.
SmartSky is a fault‑diagnosis workbench for aircraft SATCOM, datalink and cabin‑comms systems, built for the field‑service engineer (FSE) on the ramp — and for any support division or operator, definable by users, groups and even whole companies.
Raise a snag, analyse LRU logs and get a ranked and fully AI‑automated diagnosis, and log the fix so the next engineer inherits it. It reasons over your own uploaded manuals and closed‑fault history first, then the web — returning likely causes with confidence, the tasks to work in order, suspect LRUs with part numbers, and its sources.
Every squawk is logged under a FW‑ reference and, once closed with the real fix, is fed back into the fault library.
Log in as a user, company or group. You can also request access for a blank‑sheet account — or an admin can set one up pre‑loaded with the databases and manuals it needs.
Every account keeps its own reference library — add the equipment, services, manuals, tools and presentations you work with, visible only to you (or your group / company).
Explore the live demo — no sign‑up →Fault Analysis is the reasoning at the core of SmartSky. Give it the tail, the affected kit and the snag, and it returns a structured result rather than a paragraph of guesswork.
- Ranked likely causes, each with a confidence.
- The checks to work in order, and suspect LRUs with part numbers.
- Every source cited — you can trace where each conclusion came from.
It reasons in order of trust — your uploaded manuals and closed‑fault history first, the open web only as a fallback — and it is scoped to the exact equipment fitted, so the answer is about the box in front of you.
Pulled a BITE or event log off a unit — an SDU, modem, ADM or antenna controller? Add the raw text log and SmartSky reads it against that unit’s own manuals, decodes the fault words and returns ranked causes, ordered checks and suspect sub‑units.
- Grounded in the unit’s documentation, not a generic guess.
- Attach to a ticket so the log travels with the job.
- Cited — every finding traces back to the source.
It turns a wall of hex and fault words into a short, ranked read of what is actually wrong and what to check first.
Equipment is the hardware taxonomy everything else is built on — the ground truth the diagnosis is grounded in.
- Manufacturers → systems → LRUs, structured and cross‑linked.
- Verbatim part numbers — 2Ku, Plane Simple, Iridium Certus / SBD / classic and the rest, exactly as printed.
- Service mapping — every LRU tied to the service it delivers, across the whole fleet.
Anyone can add and verify manufacturers and equipment types, so the reference is kept current by the people using it rather than gatekept — and verified entries are flagged as trusted.
Get the taxonomy right and every diagnosis inherits it: correct manufacturer, correct box, correct part number.
Share a manual, fault log, screenshot, presentation or log‑book entry straight from its list — no download‑and‑attach.
- To a person or your group — it appears in their account, in scope.
- To an external email — a private download link that works without signing in and expires automatically.
- Multi‑manual units let you pick exactly which document to send.
The right document reaches the right engineer in one click, whether they’re inside SmartSky or not.
Every individual user gets a personal Vault — a private store for your own files, upload and download only, that nobody else can see, not even others in your group.
- 6‑digit PIN to lock and unlock it.
- One‑time recovery code if you ever lose the PIN.
- Yours alone — isolated from every other account.
A secure corner of SmartSky for the things that are just yours.
Manuals is the library the diagnosis reads first. Upload the PDFs your engineers rely on and each is chunked, embedded and cited in every relevant answer.
- One row per unit, with a picker when a unit has more than one book.
- Shared manuals — one manual covering a family is marked as a reference on the other units.
- No blanks — a unit with no uploaded manual gets an auto‑compiled web reference you can open and share as a PDF.
Get the library right and every diagnosis inherits it: the right book, cited to the page.
Tickets is where a job begins. Enter the aircraft tail, then pick the affected service, system and type from cascading multi‑select lists, and describe the snag two ways: exactly as the crew reported it, and your own engineer’s read — suspected cause, hardware fitted, history, and anything already tried.
Submit logs the squawk to the Log Book under a unique FW‑ reference, and the button becomes Diagnose. Run it and SmartSky reasons over your evidence in order of trust:
- Your uploaded manuals — retrieved by meaning, not keywords.
- Closed‑fault history — real resolutions from past jobs, weighted above the manuals.
- The open web — only as a fallback when your own sources fall short.
The result lands on its own page: an overall assessment, ranked likely causes with confidence, the tasks to work in order, suspect LRUs with part numbers, and the sources it drew from — every one traceable.
Registration lookup is hyphen‑insensitive, the aircraft photo stays on screen while data loads, and retrieval is scoped to the exact equipment you selected — so the diagnosis is tied to the box in front of you.
Services is the reference for every connectivity path the fleet carries, so a diagnosis is always anchored to the exact service in play rather than a generic guess.
- SATCOM — Ka, Ku and L‑band terminals.
- Air‑to‑ground — cellular / ATG links.
- Datalink — ACARS, ADS‑C, ADS‑B, ATN B1, GLOBALink and more.
Each service is tied to the providers that carry it and the systems and LRUs that deliver it, and is marked current, legacy or retired so you always know what is live on a given airframe.
Because equipment, providers and services are cross‑referenced, choosing a service on a ticket automatically narrows the hardware — and the diagnosis — to what is actually fitted.
Detailed per‑service pages for coverage, terminals and known issues build out from this list.
Tools is your on‑ramp workbench: quick engineering utilities and calculators, plus one‑click access to the systems you already depend on.
- Provider portals — jump straight to each service provider’s status page, coverage map and account tools.
- Link‑budget and margin — sanity‑check EIRP, G/T and Eb/No.
- Antenna geometry — look‑angle, azimuth / elevation and skew from a tail position.
- Cable and power — coax loss by run and frequency, plus power sums.
- Conversions — the unit and reference tables you reach for on the ramp.
The set grows as calculators are added — tell the team which you want first and they drop straight in here.
The Log Book is the running record of every squawk raised in SmartSky, each under its own FW‑ reference and carrying the tail, affected systems, the reported snag, your notes and the full diagnosis.
- Status at a glance — open, diagnosed or closed.
- View — reopen any job’s complete diagnosis result page.
- Close out — record what actually fixed it.
Closing a fault is where SmartSky gets smarter. The resolution you enter is embedded back into the fault library and weighted above the manuals, so the next engineer facing a similar snag is diagnosed from proven, real‑world history — not just documentation.
Over time the Log Book becomes the corporate memory of the fleet: every fix found once is found instantly ever after.
Aircraft is the fleet registry, and the anchor that ties a diagnosis to a specific airframe rather than a type.
- Tail lookup — hyphen‑insensitive, so VHRAN finds VH‑RAN.
- Identity and specs — served database‑first for speed.
- Sticky photo — the aircraft image stays on screen while details load.
- Equipment fitted — the exact systems and LRUs on that tail.
Fast identity and specification data is separated from slower, web‑sourced context — such as where a tail is frequently observed — so the essentials appear instantly and the extras fill in behind them.
Because each tail carries its real equipment fit, the diagnosis reasons over the hardware actually installed: the same boxes you are working on.
Presentations is a private library for briefing decks, training material and reference slides — kept inside SmartSky, not scattered across inboxes.
- Upload with a title, category and notes.
- Open in place — PowerPoint and other Office files are converted server‑side and shown in‑browser as PDF, so nothing downloads and everyone sees the same rendering.
- Large files are supported.
It is access‑controlled: uploads are managed, and the library is visible only to the engineers and companies you grant access to.
Software is the shared store for everything you load onto or configure the kit with — one trusted place instead of chasing versions.
- Installers and firmware, loaders, tools, configs and archives.
- Broad file support — executables, images, hex, archives and more.
- Catalogued with title, category and notes so the right build is easy to find.
Keeping firmware and tooling here means the team always pulls the same, known‑good version — and can see what changed and when.
Screenshots is a visual reference library for the things words cannot capture.
- Config screens and known‑good settings.
- Fault indications — what a failure actually looks like on the panel.
- Annotated shots for quick side‑by‑side comparison.
On the ramp a quick visual match is often faster than a paragraph — this is where those references live, categorised and searchable.
Profile is your account and, for administrators, the control room for who can do what.
- Your details — name, email login and the access level granted to you.
- Access scope — every account sees only its own records, its company group’s, or the entire site.
- Users and company groups — sign in as an individual, or share one company login across a team.
- Avatar or company logo, plus self‑service password change.
Administrators add users and groups, action access requests, set each account’s scope and upload company logos — so a whole support division or outside company can be onboarded with exactly the visibility it should have.