Frequently Asked Questions

ADX-1 is an automated radio dispatch and flight-following appliance for small aviation operators. It listens to pilot calls on your dispatch frequency, uses speech recognition to understand structured flight-following requests, replies over the radio using approved phraseology, opens and closes flight records, watches expected return times, escalates late or overdue aircraft, and logs the operation. Pilots keep using the radio. ADX-1 keeps the dispatch watch.

No. A tracker shows where an aircraft is. ADX-1 shows the operational state of the flight. It knows whether flight following was opened, what the pilot said they were doing, how long they expected to be out, when the aircraft becomes late, when it becomes overdue, who was notified, and how the flight was closed. ADS-B supports situational awareness. The dispatch state starts with the radio call.

ADX-1 is built for small aviation fleets that use radio-based flight following or self-dispatch. Good fits include helicopter operators, flight schools, training fleets, production flight operations, maintenance test flight operations, experimental flight test groups, utility aviation operators, tour operators, small local aviation operations, and operators with roughly 2–15 aircraft. ADX-1 is especially useful when aircraft open and close flight following by voice over a company or aviation utility frequency.

Pilots use the dispatch radio. A typical opening call sounds like: 'Dispatch, Helicopter Three Eight Five Two Quebec, training flight, forty-five minutes.' ADX-1 hears the call, transcribes it, extracts the aircraft, flight type, and duration, then replies over the radio with a structured confirmation. The pilot does not need to open an app, log into a web portal, or send a text message to start flight following.

Yes. ADX-1 can transmit approved, structured dispatch phraseology over the dispatch radio using text-to-speech and push-to-talk control. It can say things like: 'Flight following active,' 'Flight following cancelled,' 'Say again,' 'Say flight type,' and 'Say duration.' ADX-1 does not improvise freeform operational instructions.

Yes. ADX-1 uses speech-to-text to convert pilot radio calls into text. The dispatch dialog engine then parses the transcript for aircraft, flight type, duration, and intent. The system is designed around bounded aviation dispatch calls, not open-ended conversation.

ADX-1 uses speech recognition and text-to-speech as part of the radio interface. The dispatch behavior itself is deterministic and state-machine based. That means ADX-1 follows configured rules, approved phraseology, known aircraft, known flight types, expected durations, correction logic, and escalation thresholds. It is not a freeform radio chatbot.

ADX-1 can ask for missing information. If the pilot gives a callsign but omits the flight type, ADX-1 can ask for the flight type. If the pilot gives a callsign and flight type but omits the duration, ADX-1 can ask for the duration. If the callsign is unclear, ADX-1 can ask the aircraft to say again. The system is designed to ask instead of guessing.

ADX-1 uses structured readbacks so the pilot hears what the system understood. If the readback is wrong, the pilot can correct or cancel the event immediately using clear language such as 'negative' or 'cancel.' The system can undo the event during the correction window and return to idle. Speech recognition is useful, but ADX-1 does not treat it as perfect.

ADX-1 is designed for aviation radio, but radio conditions still matter. Recognition can be affected by weak reception, clipped transmissions, terrain, antenna placement, rotor noise, wind noise, simultaneous transmissions, interference, or unclear phraseology. That is why ADX-1 uses structured calls, readbacks, missing-field prompts, pilot correction language, known aircraft lists, known flight types, and manual fallback.

ADX-1 automates routine radio desk tasks for flight following. It can listen for pilot calls, open and close flight-following records, watch expected return times, update displays, send alerts, and log events. It does not replace human authority, operational judgment, safety decision-making, or emergency response coordination.

No. Pilots remain responsible for safe aircraft operation. ADX-1 supports the dispatch and flight-following process. It does not control the aircraft, command the pilot, or make pilot decisions.

ADX-1 is designed with manual fallback. If automation is unavailable, unreliable, misleading, or operationally undesirable, personnel can switch to manual dispatch mode and use the radio normally.

In manual dispatch mode: automated radio transmissions are disabled, human personnel use the dispatch radio normally, flight-following status is managed manually, active flights are accounted for manually, open and close events are recorded manually, late and overdue aircraft are escalated manually, and automation is restored only after verification.

Yes. ADX-1 monitors critical system functions such as radio ingest, dispatch state engine, radio broadcast, internet connectivity, SMS availability, and display status. If a critical function is degraded or faulted, the system can show that status so personnel know automation may not be reliable.

The standard ADX-1 package includes the dispatch appliance, aviation radio integration, radio audio ingest, radio transmit / push-to-talk interface, speech-to-text dispatch processing, text-to-speech radio response, ADS-B receive capability, local flight state engine, operations display, SMS escalation setup, health monitoring, and manual dispatch controls.

ADX-1 is local-first. The dispatch radio loop, state engine, and operational display are designed around local appliance operation. Internet-connected services such as SMS escalation are monitored through system health.

Core local dispatch functions are designed around local operation. Internet is needed for services such as SMS escalation and any cloud-connected support features. If internet or SMS is unavailable, ADX-1 can show degraded status and the operation can use manual procedures.

ADX-1 is designed to work with an authorized aviation dispatch or utility frequency and approved operating procedures. The exact configuration depends on your radio environment, station authorization, antennas, frequency plan, and local procedures.

Typical setup includes: aircraft list, callsign formats, recognized callsign prefixes, flight types, expected duration rules, radio phraseology, dispatch frequency, responder groups, SMS workflows, late and overdue thresholds, display settings, METAR airport, manual fallback procedure, and operational acceptance checks. ADX-1 is configured around the way your operation actually dispatches aircraft.

Yes. Flight types can be configured around the operation. Examples may include training, production flight test, experimental flight test, ferry, demonstration, VFR-to-destination, maintenance test, or other operator-specific categories.

Yes. ADX-1 is designed for small fleets. The aircraft list, callsign patterns, fleet identifiers, and aircraft display behavior are configured during setup.

The standard appliance is intended for a local dispatch environment. Multiple locations, multiple radios, or more complex dispatch structures may be supported as custom configurations.

ADX-1 can log: radio-derived open events, radio-derived close events, transcripts, structured readbacks, corrections, cancellations, aircraft identifier, flight type, expected duration, open time, close time, flight duration, late or overdue state, SMS alerts, responder actions, manual extensions, manual closeouts, last-known ADS-B data, and system health state.

When something goes wrong, the first questions are basic: Was flight following opened? What did the pilot say? How long were they expected to be out? When did the flight become late? When did it become overdue? Who was notified? What was the last-known location? Who closed the alert? How was the flight resolved? ADX-1 helps preserve that record.

Yes. ADX-1 records can support reporting on flight volume, open and close activity, late or overdue events, aircraft utilization, flight types, responder actions, and operational trends.

The ADX-1 Dispatch Appliance is $3,199 one-time hardware and setup. The Operations Subscription is $249/month.

The subscription includes software updates, support, configuration changes, responder updates, fleet changes, phraseology updates, SMS workflow support, warranty coverage, and overnight-shipped preconfigured replacement hardware if the unit fails.

The subscription includes replacement support and overnight-shipped preconfigured replacement hardware if the unit fails. The replacement unit is configured for your operation so the dispatch watch can be restored without turning the failure into an IT project.