ST. JOHN'S · NL · CANADA
Aviation Super-Intelligence
The collective neural network for Aerospace.Onboard AI that retrofits to the aircraft you already fly, localized AI units at the facilities that serve them, and an orbital or terrestrial AI data centre that learns across the connected fleet. Airline, cargo, patrol, search and rescue, firefighting, defence: one network intelligence, shaped to every mission, without ever writing to a certified system.
The highest-value intelligence in aviation sits in domains that are safety-critical, certification-bound, and IMA-architected. That's a moat for whoever solves it first — and a wall for everyone optimised around existing certified products. AeroMynde is built to live exactly there.
Integrated Modular Avionics, foundation-model AI at the edge, and space-based compute have never converged in a single product. Each is mature alone; together they unlock capability nobody else is positioned to ship.
EASA's AI Concept Paper (Proposed Issue 03, June 2026) caps large off-the-shelf AI models at assurance level IDAL D. AeroMynde's advisory, non-interfering posture is designed exactly at that ceiling — not below the bar, and not chasing an approval that doesn't exist.
Pilot deviation from an issued clearance is the single largest causal category of US runway incursions — and 2026's high-profile runway events at major US airports show the surveillance-only safety net still leaves the last gap open. A system that understands the clearance itself is the missing layer.
AeroMynde deploys as three tiers, each hosting its own model over its own corpus: a ground-facility unit scoped to the air traffic facility it serves, an on-aircraft unit scoped to its aircraft type, and a third tier — an orbital data centre or, in some deployments, a terrestrial one — holding the largest model over a corpus that aggregates both. Capacity rises upward; authority stays down. The aircraft unit is authoritative for pilot-facing time-critical advisories, the ground-facility unit for controller-facing time-critical advisories within its facility — and each keeps that authority with no connection to the third tier. The assignment of functions to tiers is a property of the architecture, not of the hardware: tiers may be co-hosted, subdivided, supplemented by intermediate tiers, or the third tier provided in whole or in part as a third-party service — and an aircraft unit and a ground-facility unit may also communicate over an optional direct link that bypasses the third tier. In every arrangement, authority over a time-critical advisory rests with the lowest tier able to generate it from the inputs available to that tier.
Integrated modular avionics, edge AI and fleet-scale correlation, set out as one architecture — a ground-facility unit, an on-aircraft unit and a third tier, hosted in an orbital data centre or, in some deployments, a terrestrial one — each with its own model and corpus, joined by defined failover and signed, authorized updates. It is a filed design, not yet a fielded system.
Three tiers. Three computers. Three models.The ground facility unit and the aircraft unit each think for themselves and keep working with no link at all. The data centre, orbital or terrestrial, is the largest intelligence in the network: it reasons across every connected facility and aircraft to connect what neither can see alone.
A locally-resident model trained on the aircraft type's document corpus — AFM, QRH, FCOM, FCTM, MMEL, maintenance and fault-isolation manuals, service bulletins — plus operator-licensed navigation data, updated only in maintenance-mode sessions. It transcribes ATC voice from the aircraft's own VHF receiver, parses clearances, maintains the aircraft's own clearance state and baselines, and reasons within cited source passages. It is authoritative for time-critical pilot-facing advisories, and keeps presenting them with no external connectivity for as long as it lasts.
A retrofittable unit installed at an air navigation service provider facility, coupled receive-only to recorded controller-position voice and datalink streams. Its own model — over a facility corpus of surface or airspace model, letters of agreement, procedures and configuration state — builds a controller-scoped clearance state for each position from the voice itself, not from flight strips. A deterministic detector, outside the model, finds the conflicts; advisories go to a controller-facing supplemental display, separate from certified equipment. Controller advisories are generated here from facility voice, not relayed from the aircraft, and continue with no connection to the third tier. Updates stage into an inactive slot and switch without interrupting detection.
The largest model, over a corpus that aggregates every type corpus and — as each provider permits — every facility corpus, running on orbital nodes, terrestrial data-centre nodes, or both. It produces the lower-tier models and sends them down as signed bundles that install only on operator or provider authorization, and correlates fleet health and clearance state across every connected aircraft and facility. For anything time-critical it is supplemental: its advisories are presented only when the receiving unit corroborates them locally, or when they are of a class no single unit can detect.
The architecture is built from 13 capability primitives, each one designed to survive a certification review. Together they are the platform.
Named among the vehicle classes the specification defines the platform for.
Published rotorcraft routes and zones sit in the stored model with their altitude floors and ceilings and their geometry against fixed-wing approach and departure paths, so a rotorcraft’s derived state is checked against a fixed-wing approach clearance wherever route and approach lack procedural separation. Drive-train baselines are taken from health-and-usage monitoring outputs where the operator’s agreement with the system’s manufacturer permits, keyed per component.
On a powered-lift or VTOL aircraft the on-aircraft unit is supplemental to the aircraft’s certified systems under the applicable special conditions, with no authority over and no write path to any of them.
The on-aircraft unit stays on the vehicle and reasons on its own compute; its advisories reach the remote crew station over the command-and-control link or an independent link, and that station is part of the on-aircraft tier. The unit is supplemental to, and distinct from, the command-and-control link, detect-and-avoid, and the remote pilot station’s certified functions, and listens on MAVLink or STANAG 4586 links receive-only.
A balloon position report is a machine-native instrument the facility unit parses into the same clearance-object schema as voice, held in the clearance state as an aircraft-asserted position kept distinct from the clearance record, so the record stays maintained whether or not that position is present or trusted.
Named among the vehicle classes the specification defines the platform for, as “supersonic and hypersonic aircraft”. Nothing in AeroMynde's design is specific to supersonic operation beyond that inclusion.
For a launch or reentry vehicle in atmospheric flight the vehicle-side unit may be hosted at the operator’s telemetry ground segment, downstream of the demodulator, the CCSDS or IRIG-106 telemetry stream standing in for the avionics network with the same non-interference properties. Per-component baselines cover launch-vehicle subsystems reported in telemetry.
A crewed spacecraft’s SpaceWire or point-to-point serial link is attached through a passive link analyser, or its telemetry read at the operator’s ground segment, with no transmit path onto the link. Baselines for spacecraft subsystems reported in telemetry are held per component, and the deviation detector runs on them with a corpus specific to the vehicle type.
The ground-facility unit’s home case: an air traffic control facility, including a remote or digital tower centre serving several aerodromes, or a remote or digital centre exercising procedural control on behalf of several facilities. It couples to the position’s recorded voice channels or a digital voice-switch mirror output as a listener only, one clearance state per controller position.
A service supplier that issues, accepts or monitors operational intents or flight authorisations for uncrewed, cooperative or higher-airspace operations. Its instruments, an operational intent or authorisation expressed as four-dimensional operation volumes and a constraint or airspace reservation, are parsed into the same clearance-object schema as voice and tested by intersection in space and time and, at the interface with the controlled airspace beneath, against the separation applicable in that area.
A vertiport or heliport operator is an authority in its own right. Its obstacle-free volume with its approach and departure surfaces is a class of the stored model, and clearance objects resolving against it are tested with that class’s own separation test rather than the airport surface graph’s.
A launch or reentry range control centre issues machine-native instruments, an aircraft hazard area, transitional hazard area or debris response area with an activation state, and a launch-window or flight-commit determination, parsed into the clearance-object schema and tested by containment. An aircraft’s derived state against an activated hazard area is a cross-authority conflict, even where the area spans flight information regions.
At a mission control centre the controller position is the human or automated position at which instructions originate, and its voice channel includes the countdown or mission voice loop, taken as a listener only. Where the same site also hosts a remote crew station, the vehicle-side unit presenting there and the facility unit serving the position are distinct units of distinct tiers.
Named among the authority classes a ground-facility unit may be installed with, as “an air-traffic space-operations position”. Nothing in AeroMynde's design is specific to such a position beyond the general controller-position definition.
Listens to the aircraft without any path to interfere, and keeps working with no link — normal, autonomous, reconverging.
Understands what was actually said on frequency, and what every party has been cleared to do.
Reasons from the aircraft's own documents and history, and receives new models only through signed, maintenance-gated updates.
Supports controllers where surveillance is absent, degraded or can't be trusted.
Because modern avionics already aggregate the aircraft's data onto shared buses, AeroMynde needs only an authorised listen-only attachment. And its inability to transmit is not a software promise — the transmit path is absent from the hardware itself, verifiable from the design data alone. That single decision is what makes approval on in-service airframes achievable.
Hardware transmit inhibit — not a config bit. Where others ship a bidirectional transceiver held quiet by software, AeroMynde's acquisition hardware simply has no transmit path in any state. Non-interference becomes a property you can verify from the hardware design data — taking the AI software out of the safety argument entirely.
Bus-agnostic by construction. An interchangeable physical adapter per aircraft type — , AFDX mirror port, MIL-STD-1553 bus monitor, CAN, optical — feeding one normalized data representation. The intelligence above it never changes.
No fault propagation path. The unit holds no bus address, never appears as a participating node, and presents electrical loading within the governing bus specification. There is no path for a fault in the box to reach a flight-critical function.
Segregated advisory display. Output goes to dedicated supplemental displays — never onto certified EFIS, EICAS, or operational surfaces, and always clearly annotated as supplemental.
Receive-only at the facility, too. The ground-facility unit couples to recorder or monitor outputs and to one-way datalink taps: no transmit path onto any controller frequency, no address presented to — and no command accepted from — any air-traffic-management system, and no write path to any certified ATM display or control system.
In AeroMynde's design, an installed, avionics-rack-mountable unit on the aircraft performs acquisition and time-critical reasoning, paired with a removable tablet-class device that performs display and pilot interface — joined by a wired or short-range wireless link that never traverses the avionics network. The whole unit is designed to be certifiable as a supplemental advisory system, and to be retrofitted onto in-service aircraft under a Supplemental Type Certificate or an equivalent approval.
Two installed units, structurally parallel in function. On the aircraft, the unit is rack-mounted and attaches to the avionics network as a non-interfering passive listener. At a ground facility, its counterpart is installed at the facility as a receive-only node. Both run their own locally resident model and manuals, so clearance parsing, health monitoring (aircraft) and time-critical advisory reasoning happen locally, with no dependency on external connectivity.
Its non-interference is a property of its hardware, and that posture is the principal precondition for approval to retrofit it onto an in-service aircraft.
A removable tablet-class device — or a panel-mount display — mounted in an approved cradle and segregated from the aircraft's certified avionics displays. It presents; the reasoning stays in the installed unit.
Today it fits existing flight decks as a removable display in an approved cradle; it is designed to be built into the panels of tomorrow's aircraft.
Its output is unambiguously identified as advisory output of a supplemental system, and its alerts are visually and aurally distinguishable from certified alerts.
Every architectural decision in AeroMynde starts from a single rule: the system can inform the people who fly and maintain the aircraft, but it can never put a flight-critical function at risk. Intelligence is additive — never authoritative over the aircraft itself.
AeroMynde attaches as a receive-only listener with a hardware transmit inhibit — no electrical or logical path exists by which the unit can transmit onto a flight-critical bus. Safety isn't a software promise; it's a property of the hardware.
Output is routed to dedicated supplemental displays — for the crew, and where integrated, for air traffic controllers — clearly annotated as advisory. AeroMynde supports the decisions of the people responsible for the flight; it never makes them and never commands the aircraft.
Every answer is bounded to, and cites, a retrievable passage from the approved manual corpus — and an assertion that cannot cite its source is suppressed rather than shown. The system surfaces what the documentation supports; it does not improvise procedures.
Losing connectivity moves the system down a defined ladder without losing anything on the rung below: the aircraft unit alone still delivers every pilot-facing time-critical advisory, and the ground-facility unit alone every controller-facing advisory its facility's inputs support. Each shows its AUTONOMOUS state non-urgently, away from advisories, and passes through RECONVERGING when the link returns.
The on-aircraft unit is designed to be certifiable under / ED-12C for software and DO-254 / ED-80 for hardware, at Design Assurance Level D. The ground-facility unit is a ground-based system, assessed under DO-278A / ED-109A. Updates align with the DO-326A / ED-202A airworthiness security framework, with risk assessed by DO-356A / ED-203A methods. Machine-learning components sit outside the current scope of DO-178C, so the architecture follows the emerging ED-324 / ARP6983 guidance and the EASA Concept Paper's Level 1 guidance — and the ground unit's conflict detection is deterministic, outside the model.
Accumulated state, event logs, structured clearance objects, derived aircraft state and per- baselines flow upward for correlation — subject to each air navigation service provider's data-sharing agreement and to de-identification before aggregation. Models and document corpora flow downward as three-key signed bundles, installed only on the authorization of the aircraft operator or the air navigation service provider, in a maintenance-mode session started by physical action.
This is the line AeroMynde is built around — and the reason a powerful AI can responsibly enter the cockpit. The constraint that makes the system certifiable is the same one that makes it safe.
From the moment of installation, AeroMynde turns raw avionics traffic and decades of manufacturer documentation into real-time, source-cited reasoning the crew and maintenance teams can act on.
A clearance issued at one facility can conflict with an aircraft another facility is controlling. The first facility holds the clearance but not the aircraft's state; the aircraft holds its state but not that clearance. The third tier joins them: it resolves the first facility's voice-derived clearance object against a stored model of the surfaces and airspace, projects the aircraft's avionics-derived state — FMS modes, autoflight target, ground speed, position — onto the same model, and detects the loss of separation. A correlation otherwise unavailable to any single aircraft or any single ground facility, presented at the affected facility and, where the aircraft is equipped, on its flight deck — as a supplemental advisory, subject to network latency.
The system projects a party's derived state onto the stored model of the airport's surfaces to find the protected surface that party is committed to — an equipped aircraft from its avionics, a ground vehicle from its position source — and compares it with the party's own active clearances. When the party holds no active clearance for that surface, the alert identifies a prospective incursion before the party enters it. The same check catches a committed surface that differs from the one cleared, and a clearance already completed, cancelled, expired or superseded.
Transcribes voice on the aircraft's own VHF receiver, parses each utterance into a structured clearance object, and maintains the aircraft's active clearance state — the basis for conformance advisories on the flight deck. A readback only admits a clearance to that state; it is never the test of conformance. Controllers receive their advisories from the ground-facility unit at their facility, and an alert that joins this aircraft's state to another facility's clearance reaches them through the third tier — as a supplemental advisory, subject to network latency.
Where the aircraft is committed to going, checked against where it was cleared to go — resolved against a model of the actual surfaces and airspace. The aircraft's avionics-derived state is projected onto that model to find the protected surface it is committed to, and compared with the surface in its own clearance; an inconsistency raises an alert while a correction is still practical. It is not a readback check: a crew that reads back correctly and then acts otherwise is caught, and so is a crew that never read back at all. Pilot deviation is the largest single cause of US runway incursions; this is the layer built to catch it.
Reasons from deviations in live telemetry, including the central maintenance computer, against the type's full manual corpus — and every answer is bounded to, and cites, a retrievable source passage. If the documentation doesn't support it, the system stays silent rather than improvising.
Learns the individual fingerprint of each tail — per-LRU baselines keyed to the unit and the airframe, surviving component rotation — and flags deviations beyond a set threshold, so they can be acted on before they become a deferred defect or a dispatch problem.
The third tier correlates health trends across tail numbers, operators and aircraft types, then produces updated models and corpora and sends them down as signed bundles, installed on each aircraft only when its operator authorizes it in a maintenance-mode session. One aircraft's experience becomes the whole fleet's foresight.
Connectivity is an enhancement, never a dependency. When the link drops the aircraft unit enters its AUTONOMOUS state and keeps issuing every pilot-facing time-critical advisory on its own authority; a ground-facility unit does the same for its controllers. Only what needs the third tier pauses: cross-tier correlation, fleet learning, updates.
The ground-facility unit is an article in its own right: bought and installed at a facility with no aircraft access, no Supplemental Type Certificate and no agreement with any aircraft operator — only the air navigation service provider's data-sharing agreement and a rack. With no aircraft unit and no third tier present, it still transcribes controller-position voice, keeps each position's clearance state, detects conflicts deterministically and advises controllers. Connect a third tier later and it gains cross-facility and aircraft-derived functions without changing any function it already performs. Retrofittable onto in-service facilities without controller-position tooling procurement.
A vehicle on the movement area carries a position source and its own supplemental display, separate from the vehicle's certified equipment and marked as advisory. Alerts arrive over a channel separate from any controller frequency, and the unit has no transmit path onto any controller frequency and no authority over the vehicle. With a receiver on ground control and its own locally-resident model, it keeps the vehicle's clearance state itself — and a vehicle committed to a surface it is not cleared for is caught the same way an aircraft is.
AeroMynde runs a formal simulation bench that feeds real recorded audio and simulated flight state through the full reasoning stack — with the metrics defined before the code, a frozen test split, commercially licensed data, and a rule enforced in the repository: no number leaves without a run manifest. It's how a claim about readiness becomes evidence instead of a demo.
Overall ASR accuracy and callsign-only accuracy, reported apart — because callsign recognition is the hard part, and hiding it in an average is how demos lie.
Clearance-object extraction scored field by field with match rules defined before implementation — not one flattering aggregate.
Audio end → structured object → alert decision, reported at percentiles. Never a mean.
Detection rate on injected conflicts and nuisance rate on unscripted traffic. Nuisance decides whether an avionics product survives service — it's a first-class output here, not a footnote.
Suppression measured when no grounding document exists. One uncited assertion fails the entire run.
Defined: every message crossing the tap boundary is counted in both directions. Expected: zero.
Commit hash, dataset versions and checksums, seeds, model versions, command line — attached to every figure, enforced by a check that fails the build. The bench culminates in a continuous, timestamped recording of the advisory prototype handling injected conflicts — including the moment connectivity is cut and the system keeps reasoning on its own authority.
AeroMynde retrofits onto the aircraft you already fly — no airframe redesign, no flight-critical integration, and advisories delivered to a segregated supplemental display — a tablet-class device in an approved cradle, or a panel-mount display. It turns the data your avionics already produce into fewer surprises, faster turnarounds, and a stronger safety culture, measured across every tail.
By reading live avionics telemetry against each tail's baseline and the type's manuals in real time, AeroMynde surfaces developing issues early — helping you act before a fault becomes a delay, a cancellation, or an AOG event.
Technicians get cited, manual-grounded reasoning over faults instead of hunting through documentation. A per-airframe baseline flags drift before it becomes a deferred defect — shifting the fleet from reactive to predictive upkeep.
Clearance and conformance advisories add a quiet layer of support on the flight deck — and, through the ground-facility unit, in the tower. Conformance is checked against where the aircraft is committed to going, not against what the crew said back: a correct readback followed by the wrong action is caught, and so is no readback at all. Always advisory, always human-in-command.
What one aircraft learns, the whole fleet inherits. The space tier correlates patterns across your operation and returns validated insight as signed updates — so the value grows with every tail you add and every hour you fly.
We're partnering with a small number of forward-looking airlines and operators to shape AeroMynde on real fleets. Early partners help define the roadmap — and lead on the certification path.
The same certifiable, non-interfering architecture that earns trust in civil aviation is built for the demands of defense — supporting maintenance and aircrew decisions, and running where the network can't reach. AeroMynde is an advisory and sustainment platform: it informs the people in command, and never commands the aircraft.
Manual-grounded reasoning over a per-airframe baseline gives maintenance crews cited decision support when telemetry deviates from that baseline.
The on-aircraft unit's time-critical pilot-facing advisories need no datalink and no ground. In comms-contested or DDIL conditions, when the link degrades past its threshold the unit enters its AUTONOMOUS state — shown on the display, non-urgently — keeps working from its own clearance state and corpus, and passes through RECONVERGING to resynchronize with the fleet when connectivity returns.
Type-agnostic at the application layer, AeroMynde spans diverse and legacy airframes — fast jets, transports, tankers, ISR, and rotary — via interchangeable bus adapters, including MIL-STD-1553 bus-monitor attachment, without flight-critical integration.
Advisory situational awareness, clearance and procedure reasoning support aircrew and operators — always traceable, always advisory, always leaving the human in command. This is the responsible-AI posture defense doctrine demands.
Time-critical pilot-facing reasoning runs on the aircraft with no link at all. What flows upward — accumulated state, event logs, derived aircraft state and baselines — flows for correlation under defined agreements and de-identification; what flows down is a three-key signed bundle that installs only when the operator authorizes it in a maintenance-mode session. A compromised datalink is bounded to erroneous supplemental advisories, denial of supplemental service, or exfiltration of acquired telemetry — none of which can make the aircraft depart from safe operation. Reasoning is cited to its sources, designed for the security and accreditation bar defense requires, from a company building under Canada's controlled-goods regime.
To be unambiguous: AeroMynde is a non-interfering intelligence, sustainment, and decision-support platform. It is not a weapons, targeting, or autonomous-engagement system, and it never controls the aircraft. Command and judgment remain entirely with the people responsible for the mission.
Auditable, cited, human-in-command, and physically incapable of interfering with the aircraft — the very properties that make AeroMynde certifiable for civil flight are what make it a responsible choice for the defense fleet. Further defense applications of the passive-listener architecture are presented under NDA.
AeroMynde's defensibility isn't a single patent — it's the combination of an open white space, a filed IP position, and a certification posture that competitors can't shortcut.
The value is in combining all three tiers in one architecture.
The full three-tier architecture is patent-pending, with the path to utility and international protection open. Filing particulars are part of the NDA briefing.
The specification expressly distinguishes a listener whose transmit path is absent from the hardware from one held quiet by software configuration. That line — verifiable from hardware design data alone — is the centre of the certification argument.
The non-interfering passive boundary, segregated display, and cite-or-suppress reasoning aren't features — they're the configurations that survive an airworthiness review. A competitor who skips them builds something un-certifiable.
The category is open for a focused, certification-native team to define.
AeroMynde built its own patent-intelligence engine, APIS, to search the prior art and map the white space around our inventions. The inventions are our own, and our filings are prepared with patent counsel. APIS isn't the product; it's evidence of how this team turns research into protected IP.
EASA's final AI concept paper, published in June 2026, completes Europe's framework for certifying AI in aviation. AI that assists the crew is its most established path, and that is where AeroMynde is built.
Models that once needed a data centre now run on a single compact computer, which makes reasoning on the aircraft, with no link, practical.
Pilot deviations caused nearly 62% of US runway incursions in fiscal 2024, and severe incursions rose 44% in 2025. Surveillance sees where aircraft are, not what they were cleared to do. AeroMynde is built to hear the difference.
The window for a certification-native AI platform is open now.
The same fluency that earns trust in a certification review is what lets AeroMynde reason about where deployable, defensible intelligence actually lives.
Legacy, modern and military avionics buses — one passive listener class, interchangeable adapters — extended in the specification to ASCB, CSDB, ARINC 453/708, ARINC 818, EIA-232/422/485, analog and discrete signals, Ethernet with TSN, HUMS outputs, wireless intra-communications and uncrewed-vehicle links.
Software and hardware of the on-aircraft unit, at Design Assurance Level D — with machine-learning components acknowledged to be outside the current scope of .
The framework for the ground-facility unit — a ground-based supplemental advisory system whose conflict detector is deterministic and assessable without a machine-learning overlay.
The security framework the signed-bundle update protocol aligns with, with security risk assessed by DO-356A / ED-203A methods.
The European framework for machine learning in aviation. The architecture follows its Level 1 guidance for AI assistance to humans — and AeroMynde participates in its Issue 03 consultation as a named commenter.
The emerging EUROCAE WG-114 / SAE G-34 guidance for machine learning in airborne systems, which the architecture follows.
Leo answers questions about AeroMynde (the three tiers, safety and certification, the team) from our published material.
AeroMynde's leadership covers what this market demands: executive direction and the AI and platform engineering behind it, airworthiness and certification authority, and command-level flight operations.
Michael saw a layer of intelligence inside aerospace that had never been tapped: in every clearance spoken, every manual written and every system on board, spread across flight decks and facilities that never share what they know. That intelligence became AeroMynde. He is the sole inventor of AeroMynde's patent-pending technology.
He saw it from the flight deck. Flying as an airline and corporate pilot, Michael watched the information that keeps a flight safe live in separate places: the tower, the cockpit, the manuals and the aircraft itself. AeroMynde is built to bring it together. He leads the company from St. John's, Newfoundland.
Wesley brings more than two decades of hands-on aviation experience to AeroMynde, spanning rotary-wing, commercial, military and corporate operations. He began his aviation career in 2004 while enrolled in the Aircraft Maintenance Engineer program at the College of the North Atlantic, and has worked full-time in the industry since graduating in 2006.
His career covers an unusually broad range of platforms: utility and passenger helicopters, search and rescue aircraft, commercial airliners, military fighter jets with advanced mission systems, civilian aircraft carrying military systems, and corporate aircraft. That breadth gives him first-hand knowledge of how aircraft are maintained, modified and returned to service across both civil and defence environments.
Wesley has held aircraft certification authority, served as base lead and deployment lead, managed maintenance crews, completed aircraft modifications, and mentored apprentice engineers entering the profession.
At AeroMynde, he leads airworthiness and certification strategy, making sure the platform is built from the outset to integrate safely with certified aircraft systems and meet regulatory requirements for commercial and defence fleets.
Robert is an airline and corporate jet captain with 15 years of commercial flying across Canada's most demanding environments, from coastal Labrador and the high Arctic to international corporate operations. He graduated from Moncton Flight College in 2011 with a diploma in Aviation Technology.
He began his career flying in remote northern and coastal communities, then spent over a decade in airline operations across Atlantic Canada, upgrading to Captain on turboprop airliners. He has since flown as a medevac captain across the Arctic and as a business-jet captain in international corporate aviation.
At AeroMynde, Robert leads flight operations and the pilot's perspective on the platform. He makes sure every feature is designed around real cockpit workflows, crew resource management and the operational realities of airline, medevac and corporate flying.
Aerospace judgment in the loop from day one.
AeroMynde is recruiting experienced aerospace professionals — flight operations, avionics engineering, certification, air traffic management, and airline maintenance — to sit on an advisory board now being formed. The mandate: bring the aerospace community's judgment directly into R&D while the concept is still being shaped, so the platform is built around how this industry actually works.
Review the concept as it develops, pressure-test assumptions against line experience, and guide priorities for the evidence bench and the certification path. Structured input, early — not endorsement after the fact.
Working and recently retired professionals across the aerospace ecosystem. The programme is being formed now — founding advisors help define its shape.
Write to us with your background and where you'd push back the hardest.
The board is being formed. No advisory appointments have been made.
Built with the flight deck, or not at all.
A product that can't be certified is useless. A certified product the people who operate and maintain aircraft won't accept is just as useless — unprofitable, and never on the flight deck. AeroMynde's answer is the Union Engagement Program: giving represented aerospace workforces — pilots, air traffic controllers, aircraft maintenance engineers and technicians, dispatchers, and cabin crew — a voice and a seat from the beginning, from concept to launch.
We intend to work with union and association representatives across every represented craft throughout development — testing the product, providing structured feedback, and shaping an adoption pathway that is realistic within industry standards and working agreements.
Advisory technology lives or dies on trust — in the seat, in the tower, and on the hangar floor. Building that trust starts before the first line of certification paperwork, with the people who will fly with it, control with it, and maintain it — not just the people who approve it.
At an air navigation service provider facility the system operates only under a data-sharing agreement with that provider — one that governs which channels are accessible, how long recorded voice is retained, how personally-identifiable information is handled, and the privacy and labour-relations protections for the controllers whose voice is recorded. Material from a facility is aggregated beyond it only as that provider permits, and operator- and facility-specific content is de-identified before aggregation.
The programme is being formed. AeroMynde intends to engage the established unions and associations representing pilots, controllers, maintenance engineers and technicians, dispatchers, and cabin crew; no union or association has engaged with, endorsed, or partnered with AeroMynde, and none is affiliated with it.
AeroMynde's modus operandi is a single adopted document. It states how this company works — not as aspiration, but as practice. Several of the articles below restate constraints already built into the architecture, the disclosure discipline and the engineering gates described earlier on this page, which means they can be evidenced rather than asserted.
Creator of the wind and of every current beneath the wing — You who set the air in motion before there was anyone to fly through it, we bring You this work with open hands.
You gave us the sky first as wonder, then as craft, then as calling. Now You have given us AeroMynde, and we ask that it be built on stone and not on sand.
Let it rise from St. John's, at the eastern edge of the continent, where the land ends and the ocean begins and the great crossings start — let the first place to see the morning be the first place to see this built.
Bless the small beginnings: the paperwork, the introductions, the unanswered emails, the long nights of drafting that no one will ever see. You have never despised a small beginning, and neither will we.
Send the right people. The partner who sees it before it is finished. The investor who backs the vision and not only the numbers. The mentor who tells us the hard truth in time for it to matter. The team who will carry this further than any one of us could carry it alone. And let us be worthy of them — steady, honest, and unafraid.
Grant the work itself monumental success: contracts that hold, systems that do not fail under load, intelligence that is true, and judgment that is sound. Where there is confusion in the skies, let AeroMynde bring clarity. Where there is delay, let it bring the aircraft on time. Where there is risk, let it see the danger before the danger arrives.
Bless every crew who comes home because something we built saw what they could not see. Bless every passenger delivered safely, every patient moved in time, every remote community reached, every family reunited by a flight that would not have happened without this company existing.
Bless the allies who will one day depend on it to understand one another, that what we build serves protection and never predation, peace-keeping and never harm.
As it grows, keep it clean. Let scale not corrupt it. Let money not command it. Let AeroMynde become large without becoming careless, powerful without becoming proud — and let it evolve into something greater than our own imagining: not merely a company but an institution, a standard others are measured against, a name spoken with trust in hangars and boardrooms and operations centres long after we have handed it on.
And if we are wrong about any part of the path, turn us before we are too far down it. Correct us quickly. Correct us kindly. But correct us.
Give us endurance for the years this will take, courage for the days we want to quit, gratitude on the days it works, and humility on the day it succeeds.
We do not ask for an easy road. We ask for altitude, for clear air, and for fuel enough to finish.
Into Your hands we commit this work.
Amen.
What the invocation asks for, stated as the way we work.
We do not ship what we would not fly behind. Systems hold under load or they do not leave the hangar. Contracts hold when they are tested, not only when they are signed.
The filings, the introductions, the unanswered emails, the long nights of drafting no one will ever see — this is the company too. No one here is ever too senior for the unglamorous work.
We choose partners, investors and colleagues for judgment and honesty before pedigree — and we hold ourselves to the standard we ask of them: steady, honest, unafraid.
Our product is understanding. If what we deliver leaves an operator less certain than before, we have not delivered.
Anticipation is the whole discipline. A risk found early is an engineering decision; found late, it is an accident.
We measure ourselves by crews who came home, patients moved in time, communities reached and families reunited — not by revenue alone. A quarter that grows the second while shrinking the first is a failure.
What we build serves protection and peace-keeping, never harm. This constraint outranks any contract, and we will turn away work that fails it.
Large without becoming careless. Powerful without becoming proud. Growth is never a reason to lower a standard; it is the reason the standard exists.
Bad news travels fastest here. Whoever raises the problem is thanked, and we turn before we are too far down the wrong path — not after.
We are building for decades, not for a round. Endurance on the long days, gratitude on the days it works, humility on the day it succeeds.
Five of the ten are not values language. They restate commitments already made in the architecture and the operating discipline — which is why this page can be checked against the rest of the site.
AeroMynde is designed to plug into the roadmaps of the world's aerospace primes and tier-one suppliers as a design-partner and strategic-investment opportunity — a certification-native AI platform that retrofits to the fleets flying today and is designed to be built into the aircraft of tomorrow.
AeroMynde Ltd. is an independent Canadian venture based in St. John's, Newfoundland. Company names above describe the market and the strategic-partner ecosystem AeroMynde is built to serve, and do not imply any affiliation, partnership, investment, or endorsement.
AeroMynde is pre-revenue by design — the milestones are the story. The architecture is defined and filed, the evidence program is running, and the next phase is a measured demonstration and first design partners.
The full three-tier architecture and its capability primitives defined. The architecture is patent-pending. Brand, legal onboarding pack, and the company's internal AI operations platform stood up. Formal comment filed on the EASA AI Concept Paper Issue 03 consultation.
The simulation bench is live: real licensed audio and simulated flight state through the full reasoning stack, scored against pre-registered metrics with a manifest on every number. It culminates in a continuous recorded demonstration of the advisory prototype — including operation in the AUTONOMOUS state, with the link cut. In parallel: first design-partner conversations and Canada's non-dilutive aerospace & defence funding pipeline.
The passive listener moved from data model to real bus hardware, the certification basis established for the tap, European research partnership formalised, and the patent-pending position advanced to utility and international filings.
From first certified installs to standing up the third tier — on orbital nodes, terrestrial data-centre nodes, or both — turning per-aircraft intelligence into fleet-wide correlated foresight.
Milestones, releases and announcements go out to the list as they happen — no noise, just what moves the company forward.
Get AeroMynde news releases and milestone updates delivered to your inbox.
AeroMynde is raising its pre-seed round to deliver the measured demonstration, secure its first design partners, build the hardware tap prototype, and advance its filed IP toward utility and PCT.
The full investor briefing — capability teardown, defense applications, evidence results, financial model, and the certification file — is shared under NDA. This site is the pre-NDA view.
The investor briefing, the NDA and all legal documents are provided in English.
An avionics box designed to be removed and replaced as a single unit on the flight line, identified by its own part and serial number.
AeroMynde keeps a per-LRU baseline keyed to the aircraft tail and the unit's serial, so a unit that moves between aircraft is tracked as itself. P7
The approval that lets an already-certified aircraft type be modified with new equipment, issued once the modification is shown to meet the applicable rules.
AeroMynde's installed unit is designed for retrofit under an STC or equivalent approval; its hardware non-interference is the principal precondition for that approval.
The lowest of the four lettered software and hardware assurance levels under DO-178C / ED-12C and DO-254 / ED-80, applied to functions whose failure is classified as minor.
AeroMynde is designed to be certifiable at DAL D and deliberately takes no part in any function classified at Level A, B or C.
The RTCA / EUROCAE standard (ED-12C in Europe) that defines how airborne software is developed and verified to a given design assurance level.
AeroMynde's software is designed to be certifiable under DO-178C / ED-12C at DAL D.
The most common avionics data bus on transport aircraft: a one-way, two-wire serial link from one transmitter to a small number of receivers.
AeroMynde attaches to this and other avionics buses as a passive listener with a hardware transmit inhibit — there is no transmit path to inhibit in software. P1
A tablet-class device pilots use for charts, manuals and performance tools in place of paper.
AeroMynde's pilot-facing device is a removable tablet-class device performing display and pilot interface only; the reasoning stays in the installed unit. The evidence bench ends in a continuous recorded demonstration on such a device.
The standard measure of speech-recognition accuracy: words substituted, deleted or inserted, divided by the words actually spoken.
AeroMynde's evidence bench reports callsign-separate WER. No figures are published yet, by design.
The ground service that issues clearances and instructions to aircraft by voice and datalink.
AeroMynde listens to ATC voice receive-only and turns each clearance into a structured clearance object; it never transmits. P3
