01Start here
Open the customer history
Start with the customer workspace to see aircraft links, invoice history, and the current account picture.
Open customersOnboarding
Follow the role-specific lane that matches the work being done.
Best for aircraft owners, customers, viewers, and auditors who mostly need clarity, approvals, and traceable answers.
Why this feels different
years in aviation
chat bar to start
clunky dashboards to memorize
Choose your lane
Follow the role-specific lane that matches the work being done.
Customer and viewer lanes stay read-only unless the organization grants more access.
The assistant can answer aircraft, record, and billing questions with citations instead of raw guesses.
Secure links, invoices, and customer history all point back to the same aircraft and owner context.
Portal walkthrough
Best for aircraft owners, customers, viewers, and auditors who mostly need clarity, approvals, and traceable answers.
Start with the customer workspace to see aircraft links, invoice history, and the current account picture.
Open customersBrowse the shared documents and aircraft summaries before asking for a deeper explanation in chat.
Browse recordsUse the chat bar for grounded questions like the last annual, open balance, or what was signed off recently.
Ask a questionFollow the shared links, invoice history, and summaries without needing the full maintenance workspace.
Review portal laneCustomer routes
These routes stay focused on aircraft clarity, customer history, and grounded answers.
Use the customer workspace to understand billing, aircraft links, and open items quickly.
Move through manuals, scanned records, and evidence-backed pages without losing the aircraft context.
The assistant should answer with citations, not vague summaries, when you ask what happened or what is due.
Portal, invoice, and summary outputs should stay simple, traceable, and easy to hand off.
A note from Andy Patel
After more than 15 years in aviation, I kept seeing the same pattern: the flying and maintenance work was already demanding, and the record-keeping made it harder than it needed to be.
Owners and customers should be able to understand what happened to the aircraft without needing a walkthrough every time they open the software.
That is why we built myaircraft.us around a one-bar, chat-first approach. Ask what happened, see the evidence, and get the explanation in plain language without losing trust in the record.
Andy Patel
Founder