Aer·Ops
AER-OPS · EST. 2026 · AVIATION TECHNOLOGY

Aviation operations, written down properly.

We are building tools for the people who keep aircraft flying — material planners, stores, repair managers, operations desks. The data they work with is scattered across spreadsheets, emails and legacy systems. We put it in one place and make it useful.

Explore Solutions → Get in Touch
FOCUS · NARROWBODY FLEET · A320NEO / 737MAX STAGE · EARLY · PROTOTYPE DOMAIN · AEROPS.SPACE REACH · DEVRESOURCES@AEROPS.SPACE
§ 01 — Focus Areas

What we're building, in plain language.

A / 01

Supply-chain analytics

Readable views of consumption, lead times and repair cycles across fleets.

Material planners spend hours stitching together reports from three different systems to answer one question. We want to shorten that loop.

Concept
A / 02

Spare-parts tracking

A single, honest record of where a rotable is and what its status is.

A removed component leaves the hangar and its status gets rebuilt from email threads. We think it should live in one place with the serial number attached.

Prototype
A / 03

Operational tools

Small, focused tools for the operations desk — AOG triage, loan tracking, repair orders.

Not a platform. Narrow things that solve one problem a planner has at 2am, built close to how the work actually gets done.

Concept
A / 04 →

More features coming soon

We're building in short cycles. See the full roadmap on the Solutions page.

MEL deferral tracker · shop-visit calendar · stock-health alerts · and whatever the people doing the work say they need next.

View roadmap →
Solution Areas
3units
Analytics · Parts · Ops
Capabilities Mapped
12items
See status table
Active Prototypes
2live
Internal testing
Founded
2026y
Founder-led

Who we build for

Operators of narrowbody fleets, their stores and planning teams, and the MROs and repair vendors they work with. The tools we design assume the day-to-day of A320 family and 737 family maintenance — but the ideas carry.

Illustrative scope — not a customer list.

§ 02 — Status Legend

Where things stand.

Live

Working and usable today.

Prototype

Functional early version, in internal testing.

Concept

Planned or being explored. Not built yet.

STATUS · AT · A · GLANCE

Capability Area Status

Nothing is marked Live yet. We'll update this table as capabilities move to production.

Studio
AerOpsEst. 2026
Scope
OperationsParts · Planning · Ops
Focus
NarrowbodyA320 · 737
Stage
EarlyPrototype phase

If you work in planning, stores, repairs or operations and any of this sounds familiar, write to us at devresources@aerops.space.

§ Solutions

Three areas we're working on.

Supply-chain analytics

Concept
Problem it addresses. Planners stitch together consumption, lead-time and repair-cycle data from several systems to answer a single demand question. Each answer takes hours and the trail isn't reusable.
Capabilities
    AIRCRAFT on-wing REMOVAL U/S tag STORES GRN · bin SERVICEABLE bin · ready REPAIR vendor SHIP OUT repair order PN · SN pair tracked at every step · ATA chapter noted at removal

    Illustrative — not real data. Flow shows a typical rotable loop.

    Spare-parts tracking

    Prototype
    Problem it addresses. A removed component leaves the hangar and its status gets rebuilt from email threads. By the time anyone asks "where is tail X's APU valve", the trail is in six places.
    Capabilities
      PART RECORD PN · SN · ATA status · location MAINT MSG RECEIVING STORES REPAIR VENDOR LOAN POOL AOG DESK One record. Six sources update it. Everyone reads the same line.

      Illustrative — not real data. Shape of a part-record hub.

      Operational tools

      Concept
      Problem it addresses. Operations desks juggle MEL deferrals, AOG events, loan returns and shop visits in parallel. Context lives in heads and chat threads.
      Capabilities
        T+0 T+2h T+6h T+12h T+24h T+48h AOG DECLARED tail VT-XX · ATA 29 PART ID LOAN ARR. RELEASED return to service RO raised vendor dispatched U/S shipped to repair shop Timeline reconstructed from a real pattern — hours shown are indicative only.

        Illustrative — not real data. One tail, one AOG, from call to release.

        § Method

        How we approach it.

        01 / Understand

        The operation first

        We spend time with the people who do the work. The spreadsheet they actually use. The email thread that solves the problem. The reason the official system is being bypassed.

        02 / Prototype

        Build the narrow thing

        A small, usable tool that handles one real case. Not a platform. Not a dashboard with ten tabs. Something that fits into a planner's day without asking them to change it.

        03 / Refine

        With feedback, in the loop

        Short cycles. We watch how the prototype gets used, what gets ignored, what gets requested. We cut, rename and rework, then do it again.

        § Roadmap

        What's next.

        Q4 · 2026

        Rotable tracking v1

        First usable version of the part record. Removal, GRN, repair-order and loan events tied to a single PN/SN view.

        Prototype
        Q1 · 2027

        Consumption analytics

        Readable views of consumption and lead-time patterns by ATA chapter and vendor, drawn from the same underlying record.

        Concept
        Q2 · 2027

        AOG triage board

        A narrow desk tool for operations: live AOGs, part identification, loan status and shop-visit timing in one view.

        Concept
        Beyond

        More features coming soon

        MEL deferral tracking, repair-order dashboard, stock-health alerts and the parts of the operation that still live in email threads.

        Exploring
        § About

        Early-stage, founder-led, aviation-first.

        01 / Vision

        What we want to see.

        Aviation operations run on a lot of institutional memory and a lot of workarounds. The data exists — it is just scattered across systems and inboxes. The vision is simple: the people who plan, buy, repair and dispatch should be able to see the same picture, at the same time, with the serial number attached.

        02 / Mission

        What we're doing about it.

        Designing and building small, specific tools alongside operators. Honest about what works today, what is in prototype, and what is still a sketch. We'd rather release one well-fitted tool than a long roadmap of promises.

        03 / Focus

        Where our attention is now.

        Narrowbody fleets — A320 family and 737 family. Material planning, stores, rotable tracking and operations-desk tools. We're learning in the open with people who do this work every day.

        04 / Honesty

        What we're not.

        No customers to name. No airline logos to list. No funding rounds, no certifications, no approvals. If someone shows you a page like this with those things on it at this stage, be suspicious. We're early, and we think the work is more interesting that way.

        § Team

        Who's building it.

        A small founding team with backgrounds split across aviation operations and software engineering. We work closely with practitioners in planning, stores and operations desks.

        More team members joining soon.

        § Contact

        Write to us.

        Direct channels.

        If you work in aviation operations, planning, stores, repairs or MRO technology, we would like to hear from you. The form opens your email app with a pre-filled message — nothing is sent or stored by this page.

        Email devresources@aerops.space
        Domain aerops.space
        Response Usually within 48 hours
        Stage Early · open to conversation
        Please enter your name.
        Please enter a valid email.
        Please choose an area.
        Please write a short message.
        This form opens your email app. No data is stored on this site.
        Your email app should have opened with a draft. Nothing was sent by this page.
        § Privacy

        Privacy policy.

        LAST UPDATED · OCTOBER 10, 2026

        This site is static. It has no backend, no accounts, no login, no database.

        What we collect

        Nothing is submitted to or stored by this site. The contact form validates your entries locally and then opens your own email application with a pre-filled message. We only receive what you then choose to send from your email app.

        Cookies and tracking

        No cookies are set by default. No analytics scripts are included at the time of this update. If analytics are added later, this policy will be updated and the specific service and what it collects will be named here.

        Fonts

        This site loads fonts from Google Fonts. Google may receive your IP address and basic request information when fonts load. This is standard for sites using the Google Fonts service.

        Data contact

        For any question about this policy, write to devresources@aerops.space.

        Changes

        This policy will be revised as the site evolves. The last updated date above reflects the most recent revision.