Purpose: Call Clearance Delivery, copy your IFR clearance in CRAFT shorthand, and read it back. Routes come from the FAA preferred-route and TEC database, plus real recent ATC clearances.
Static plays under the voice; the browser's voice itself can't be filtered to sound like a radio. Saved on this device.
Speech: nothing spoken yet
Write with one finger or a pencil; scroll the page with two fingers.
Hold the red Push to talk at the bottom of the screen (or Space) while you speak: initial call, "ready to copy", readback, "say again" or "request full route".
Training aid only, not for navigation or flight planning; check everything against current charts and the Chart Supplement. Routes: FAA NFDC Preferred Routes (03-Sep-2026 to 29-Oct-2026 cycle) plus ATC-cleared routes from ForeFlight. Frequencies: FAA NASR, OurAirports elsewhere. Routes and your last pick sync across your browsers under a random code; nothing else is stored. Speech recognition is your browser's (Chrome uses Google, Safari uses Apple).
Training aid only, not for navigation or flight planning. Routes: FAA NFDC Preferred Routes Database (TEC, low and high preferred routes), effective 03-Sep-2026 to 29-Oct-2026, downloaded 17-Oct-2026; plus ATC-cleared KSBA routes from ForeFlight, pulled 17-Oct-2026, and any routes you bring back with "Get routes from ForeFlight (via Claude)", which uses your own ForeFlight connector. Those routes, and your last route and altitude pick, are kept on this device and on this site under a random sync code the app makes, so the app finds them again in your other browsers (on iPhone, Claude's link opens in the Claude app's own browser); nothing else about you is stored. The FlightAware link opens FlightAware's list of recently filed routes for the pair (filed, not necessarily flown as filed). Departure procedure names spoken from a route (e.g. GAUCH3 as "Gaucho Three") are a best guess. TEC aircraft classes per Redbird Flight's TEC summary: J jet; M turboprop/special 190 kt+; P non-jet 190 kt+; Q non-jet 189 kt or less; the number after the letters is the highest altitude for that class. TEC routes with a name (e.g. SBAQ27) are read by name as departure city, phonetic letter and digits ("Santa Barbara Quebec two seven"), following the "Ontario Papa 16" example in that summary; the digit-by-digit reading is an assumption. US airport frequencies: FAA NASR 28-day subscription (FRQ frequency data), refreshed on this site each cycle ("Update FAA data" in Departure details); OurAirports is the fallback and covers everywhere else. Where a field has no Clearance, Ground or Tower frequency, the app uses the approach or center frequency OurAirports lists for that field; if none is listed, it borrows the nearest field's (within 80 km) and says so in Departure details. Check either against the Chart Supplement. Airport names, frequencies and navaid names: OurAirports (public domain), bundled 17-Oct-2026: about 25,500 airports, i.e. every US, Canadian and Mexican airport and seaplane base plus worldwide airports with an ICAO code. Small fields often have no published Clearance Delivery or departure frequency in that data; the app then uses typical defaults, which you can edit in Departure details. KSBA departure: Santa Barbara Five (SBA5), on radar vectors maintain 3000, expect filed altitude 5 minutes after departure (FAA chart AL-378). Other airports get typical defaults (radar vectors, 3,000 ft or field elevation + 2,000, expect filed altitude in 10 minutes); check them against your charts in Departure details. Departure frequency is picked from the published sector split where there is one. Filed-altitude choices follow the odd/even IFR cruising rule (14 CFR 91.179, from memory); with "VFR departing Class C" they follow the VFR rule, odd or even thousands + 500 (14 CFR 91.159(a), checked 21-Oct-2026). Routes from ATC clearances (ForeFlight or the bundled library) don't limit the altitude. Speech recognition is done by your browser: Chrome sends audio to Google, Safari uses Apple's service.