Briefing quality
A briefing is the aviation weather and flight information the service prepares for a pilot's flight. The synthetic events record how long each request took and which lookups ran, not the weather itself, so what this page can show is coverage: which parts of a briefing had their lookups run. It cannot show whether the content was right.
Showing 1,200 synthetic requests, Mon 05 Jan 00:01 UTC to Thu 08 Jan 04:25 UTC. Dates are synthetic. Trends, Predictions and the Improvement queue always use the whole window.
Which parts of a briefing the lookups covered
| Section | Lookup completed | A lookup was skipped: ran out of time | Not part of an alternate check | Placeholder, not live data | Not checked: no data source |
|---|---|---|---|---|---|
| Hazards and pilot reports | 905 | – | 112 | – | – |
| Departure and arrival weather | 1,017 | – | – | – | – |
| Weather along the route | 905 | – | 112 | – | – |
| Winds aloft | 1,017 | – | – | – | – |
| Temporary flight restrictions (TFRs) | 904 | 1 | 112 | – | – |
| NOTAMs | – | – | – | 1,017 | – |
| Special use airspace | – | – | – | – | 1,017 |
"Lookup completed" says the request finished that lookup. It does not say the content was right or current, or that a caller heard it. Sections that are not part of an alternate-airport check are counted as such, not as gaps. 0 briefing requests in this range are left out of this table because the lookups in their record could not be worked out, and 54 requests have no timing record at all. Neither is counted as completed or as skipped.
Briefing requests where a lookup was skipped
1 in this range. A skipped lookup means part of a section was not checked for lack of time; the rest of that section may be complete.
| Request | Started (synthetic) | Sections affected | Preparation time |
|---|---|---|---|
| R-0041 | Mon 05 Jan 05:41 UTC | Temporary flight restrictions (TFRs) | 14.2 s |
How the service handles a lookup that cannot run
In the service's source, a check that stops for lack of time is recorded with that reason ("briefing ran out of time") and is not treated as "nothing found". A different reason is recorded when a source is unavailable. Whether the voice then tells the caller is not measured here.
This is read from the source and not verified against the live service.
What this page cannot tell you
Correctness against official sources Not measured
The events hold no weather, so nothing here can say a briefing was right.
What would measure it: A sample of real briefings compared with the official version by a person.
Spoken wording against the written briefing Not measured
Nothing here reads a transcript or an audio file.
What would measure it: Transcripts or recordings compared with the written briefing.
What the pilot understood or did Not measured
Not visible to the service.
What would measure it: Follow-up with pilots, by a person, in a way pilots agree to.
Engineering details: how sections are worked out
For a briefing that finished normally, the records list lookup groups in a fixed order: airport lookup, current weather, winds aloft (only when no stored copy was found), then for a standard briefing hazards, route weather, and the TFR list and details (only when no stored copy was found). Each group is matched to a lookup by position, and a section's state is taken from whether the lookups behind it ran.
That mapping is only valid for that plain sequence. A record with a retry pass, or with a different number of groups than the sequence predicts, is left unmapped: its sections are not judged, and it is counted above as one whose lookups could not be worked out.
Sections and their states: hazards = Hazards and pilot reports; weather = Departure and arrival weather; route = Weather along the route; winds = Winds aloft; tfrs = Temporary flight restrictions (TFRs); notams = NOTAMs; sua = Special use airspace.