About Dash Aero
Built inside a working shop, not a boardroom.
Dash Aero is developed and proven inside a real aircraft maintenance operation. Every screen earns its place at the aircraft before it ships. Your shop runs the same product, under your brand.
A maintenance event carries a lot: the original squawk, the findings, the photos, the measurements, the approvals, the inspections, the tests, the parts, the records, the invoice. For decades that story fragments across phone calls, text threads, email chains, sticky notes, spreadsheets, and memory. The mechanic does careful work that looks careless in the write-up. The owner calls for status because they have no other way to know. The inspector signs under pressure. The records scramble starts after the aircraft has departed.
Dash Aero carries the whole job in one maintenance-event record. Mechanics capture work at the aircraft. The shop reviews and publishes what the customer needs to see — nothing more, nothing by accident. Questions, approvals, deferrals, and acknowledgments return to the same event. Work proceeds through inspection, testing, records, and delivery on one spine, not five systems.
The product earns its shape at a real aircraft first. The hangar writes the requirements; the screen follows. Your shop gets that product — configured for your event profiles, your forms, your terminology, under your brand.
The boundaries
What Dash Aero is not.
Saying no to these is a product decision, not a footnote. Each boundary keeps the platform trustworthy for liability-sensitive work.
- Not a parts marketplace, parts catalog, or inventory ERP
- Not a fleet-tracking, dispatch, trip-planning, or crew-scheduling system
- Not a generic work-order tool bolted onto a spreadsheet
- Not an authoritative fleet-wide maintenance-control or compliance system
- Not a general-ledger, payroll, or billing system
- Not an autonomous AI authority — AI proposes, humans commit and sign
One platform, no forks
The second-shop test is a release criterion.
The same product runs a single-hangar shop and a multi-location enterprise. We treat that as a promise the product has to keep before the second shop ever arrives — not a story we tell after the fact.
A small independent shop gets one organization, one location, strong defaults, and almost no administrative overhead. A multi-location enterprise activates a hierarchy of legal entities, divisions, locations, work centers, and teams — configuration inheritance, delegated administration, identity provisioning, versioned APIs — on the same product.
Enterprise depth stays out of the small-shop workflow, and small-shop defaults never create unsafe shortcuts at enterprise scale. Progressive activation carries both ends.
The productization test below is how we hold ourselves to it.
- A second, materially different aviation shop configures identity, roles, forms, approvals, quality gates, records rules, notifications, and integrations through supported product mechanisms
- No application fork, no rewritten core workflow, no tenant-specific branch
- Its customers receive a coherent shop-branded experience — your brand, not ours
- Its data stays isolated and exports cleanly during offboarding
- One product upgrade serves both shops
Principles
What Dash Aero optimizes for.
Correctness and traceability first
Source facts, evidence, authority, and audit commit before anything derives, publishes, or analyzes them. Dash Aero earns being right before it earns being fast.
Internal by default, published deliberately
Mechanic notes, images, and findings never reach a customer automatically. Publication is an explicit, versioned, audience-scoped action — correctable, never a side effect.
Mechanics do the work
Dash Aero carries organization, capture, and reuse so the mechanic spends the day at the aircraft instead of at the bench reconstructing it. Point-of-work usability is a correctness constraint, not polish — mechanics are helped, never surveilled.
One product, progressively activated
A small shop gets strong defaults and almost no administrative overhead. A multi-location enterprise activates hierarchy, delegation, and controlled configuration on the same product — no tenant fork, no separate authority model.
Who it's for
Built for the people who do and depend on the work.
Each role works from the same committed facts and sees the view that belongs to it. Pick the one that sounds like your seat — it links straight to the screen built for it.
Mechanics and inspectors
Capture performed work, findings, and evidence at the aircraft — task cards, hold points, diagnostic log, photos, borescope, NDT — bound to the right work context as it happens.
See the Mechanic WorkbenchShop operations and DOMs
Run scheduling, blockers, authorization, quality, records, and delivery from one command center — AOG insertion, findings review, the completeness matrix, and 11-dimension delivery readiness on one screen.
See Shop ControlAircraft owners and operators
See the role-appropriate, deliberately-published view of the same committed facts — and act on it. Findings inbox with line-item approvals, live timeline, records library, no surprise invoice.
See the Operator PortalVendors, experts, and collaborators
Scoped, expiring, audience-bound access for OEMs, engineers, component shops, NDT, insurers, and regulators — exactly who you need, exactly what they need, and not a day longer than that.
See Collaboration Rooms