Overview
Real demo calls made to the Flight Service phone line, summarised directly here. Show the synthetic lab instead.
Every recorded call with a usable start time, as of Tue 29 Sep 2026 14:16 UTC (Tue 29 Sep 2026 09:16 CDT).
Freshness
Calls in this range
These counts are for the selected range only. The archive's all-time totals are on the System performance tab.
Most recent calls
| Call | When (UTC) | Outcome | Recording | Transcript | Weather | Findings |
|---|---|---|---|---|---|---|
| #58 | Mon 28 Sep 2026 15:36 UTC | Completed | Recording | 25 turns | Stored | 0 |
| #57 | Sun 27 Sep 2026 20:21 UTC | Completed | Recording | 27 turns | None | 0 |
| #56 | Wed 23 Sep 2026 18:05 UTC | Completed | Recording | 45 turns | Stored | 0 |
| #55 | Wed 23 Sep 2026 13:10 UTC | Not connected | None | None | None | 0 |
| #54 | Tue 22 Sep 2026 23:32 UTC | Completed | Recording | 37 turns | Stored | 0 |
| #53 | Tue 22 Sep 2026 23:28 UTC | Completed | Recording | 4 turns | None | 0 |
| #52 | Tue 22 Sep 2026 23:21 UTC | Not connected | None | None | None | 0 |
| #51 | Tue 22 Sep 2026 23:19 UTC | Connected, not completed | None | 8 turns | None | 0 |
Summary
Airports mentioned
| Value | Calls |
|---|---|
| KDTO | 7 |
| KHYA | 4 |
| KMLC | 4 |
| PANC | 3 |
| KSPS | 3 |
| KAMA | 3 |
| KDVT | 2 |
| KFLG | 2 |
Aircraft type mentioned
| Value | Calls |
|---|---|
| C206 | 6 |
| PA28 | 3 |
| C172 | 2 |
| T38 | 2 |
| CE414 | 1 |
| C-414 | 1 |
| 737 | 1 |
| Cessna 206 | 1 |
Review flags
| Flag | Calls |
|---|---|
| The pilot asked to file a flight plan | 15 |
| The notice that this is not an official briefing was not given | 3 |
| An automatic check failed: No invented weather | 3 |
| An automatic check failed: Notice that this is not an official briefing | 2 |
| The call failed | 1 |
| A weather lookup failed | 1 |
Worked out only from fields already sanitized for the public record (call length, flight details as captured from what the pilot said, and the archive's own review flags). Nothing here re-reads a raw admin record.
Engineering details: how this range and summary are worked out
The range is applied to each call's own stored start time, in UTC, against the server's clock right now — never the synthetic window, and never "since the newest stored call". The summary figures use only fields the recorded-calls reader already sanitizes for the public record (call length, flight details as captured from what the pilot said, and the archive's own review flags); nothing here re-reads a raw admin record, and nothing is written back anywhere.