For aviation maintenance shops
From squawk to sign-off, one record carries the whole job.
Dash Aero is the maintenance-event platform for aviation shops. Mechanics capture work at the aircraft, not from memory at the bench. Owners see real status without calling. Nothing reaches the customer until you publish it.
An animated record card assembles a maintenance event in seventeen beats: the empty event record for aircraft N492DA rises in and the tail number stamps on; a squawk chip — intermittent CAS msg — flies in and docks, acknowledged by a radar-ping ring so the squawk does not vanish; a work item (CAS card R&R) unfolds with an Open state pill; three evidence captures — a photo, a measurement, and a voice note — arc in and land; a finding card assembles beside it with Observation, Cause, and Proposed-action rows typing in at a human cadence; a $4,830 estimate chip pops onto the finding; the authorization stamp slams down — Approved — line 1 of 1 · financial + technical; the work-item state advances Open to In work to Work performed while a connector line draws; an independent inspector chip slides in and its checkmark self-draws — Inspection approved; a five-dimension readiness matrix fills cell by cell; the evidence and signatures arc into a records packet that squash-bumps on each absorb; a lock seal stamps the packet — Signed · v1; the badge flips from Internal to Published, audience chips fan out to the Owner and DOM, and the hero glow warms; a phone frame slides in showing the owner timeline view of the same facts; the record settles with a breathing caret; then the scene fades and resets for a seamless restart.
Sound familiar?
Every aircraft tells the same story of scattered work.
The squawk that vanishes.
A pilot reports a discrepancy and waits. Days later nobody can confirm whether anyone saw it, let alone acted on it. The report lives in a sent-items folder and a memory that may or may not be shared.
The status reconstruction.
A customer calls for an update. You put them on hold and rebuild the answer from text threads, a spreadsheet, and the foreman’s recollection. The customer hears the fiction assembling in real time.
The surprise invoice.
The work was authorized by a handshake and a nod. The bill lands with line items the customer has never seen. The phrase they use is "financially ambushed" — to their mechanic, their accountant, and the next shop they call.
Your shop runs on skill. Your paperwork runs on memory.One of those scales.
The turn
Every visit becomes one maintenance event.
The squawk, the findings, the photos, the approvals, the inspections, the tests, the records, the invoice — one record, carried from the first call to the signed-off delivery. Everyone works from the same facts. Everyone sees the view that’s theirs.
The object model draws itself: Aircraft, Request, Event, Work, Finding, Authorization, Record — seven independent entities joined by the relationships that govern them.
Aircraft → Request → Event → Work → Finding → Authorization → Record
Mechanic Workbench
Capture work standing at the aircraft.
Task cards and hold points, finding capture that keeps observation separate from cause and proposed action, a diagnostic log, evidence attached as it’s gathered, and offline hangar mode that syncs the moment signal returns.
Your careful work finally looks as careful as it was.
At the aircraft
- Task card
- Hold point · work performed
- Finding
- Observation · cause · action
- Evidence
- Photo · measurement · voice
- Hangar mode
- Offline · syncs on signal
Shop Control
Run the shop from a command center, not from memory.
A Today view, a work board with gated columns, a decisions queue with owners, blockers surfaced with a name on each, and delivery readiness earned across eleven independent dimensions — not a single rounded percentage.
Explain any delay in ten seconds, not ten phone calls.
Today
- Today
- What matters this shift
- Work board
- Gated columns · no skips
- Decisions
- Queue · owner · due
- Readiness
- 11 dimensions · each earned
Operator Portal
Your customers stop calling — because they already know.
A role-adaptive home for owner, DOM, pilot, or accounting; a findings inbox with per-line approvals; a live event timeline; and the records package delivered with the invoice it backs.
The invoice is never a surprise, because every line was approved when it happened.
Your customer's view
- Home
- Role-adaptive · owner · DOM · pilot
- Findings
- Inbox · per-line approval
- Timeline
- Live event · same facts
- Records
- Package · delivered · locked
A record's status flips from Internal to Published. The audience fan opens — Owner and DOM — and the audit line appends the signature: version 2, published by S. Ortiz at 2:14 pm.
The signature trust mechanic
Internal by default. Published deliberately.
Mechanics write frankly. Findings develop honestly. And none of it reaches the customer until you choose the audience and hit publish. Versioned, correctable, and audited — every time.
A correction amends the record; it never overwrites it. The original wording survives to the finding, and so does every change since.
The plan
Three steps to your first signed-off event.
Tell us about your shop
Locations, fleet mix, and the tools you run on today. The messier, the better — that’s where the platform earns its place.
See it configured for your workflow
Your event profiles, your forms, your terminology. Not a demo with our data — your shop’s vocabulary on every screen.
Run it on real jobs
A live maintenance event, with our team alongside yours through the first squawk to the signed-off delivery.
Three planned steps connect into one governed sequence — the connectors line-draw between them, and each step’s check self-draws.
Built inside a working shop
Proven at a real aircraft, not on a whiteboard.
Dash Aero is developed and proven inside a working aircraft maintenance operation — every screen earns its place at a real aircraft before it ships. Your shop gets the product, under your brand.
One platform, no forks: the same product runs a single-hangar shop and a multi-location enterprise.
What changes
The same record, four reasons it matters.
Mechanic
Credit for careful diagnosis — your reasoning survives the record, not just the result.
Owner
Real status without a phone call. You look at the record; the record is the answer.
Inspector
Sign with evidence, not pressure. The authorization sits beside the work it permitted.
General manager
Proud of the operation — and able to prove it. Every event is a defensible artifact.