Without your brief I can't comment on why you didn't get the Wyton NOTAM. However if you or anyone else has a problem with a brief it's very important to find out why.
I think a clue is in your own post. You posted yesterday (1 August)
PS: The final indignity! I've just managed to login, did a UK Narrow Route Briefing from EGSC (Cambridge) to EGSP (Peterborough Conington) for 28th July between 1200 - 1800, with a route width of 60nm, including misc notices (i.e. TRA's). This showed stuff as far afield as Southampton, Newark, Norwich and Waddington. No mention of Wyton's TRA for the Red Arrows though! Arrgghhh!
Your brief would not include NOTAM that were no longer valid at the time you took the brief and the Wyton one expired on 28 July. What you get is a PRE-FLIGHT Information Bulletin.
At the top of your brief are the criteria that were used in selecting the NOTAM to be included. There's also a number beginning R like this R0200323. Quoting this number will allow AIS to retrieve the brief and give you the answer.
Common reasons for non-inclusion include that the activity was not active during the validity period of the brief.
It is important to note that any entry in the "UTC Date of Flight" box has no effect on the validity. It is what is in the "UTC Validity Period" boxes that is important. If they are left blank the brief will be valid for 48 Hrs from when the Submit button is clicked.
The Wyton NOTAM was valid from 14:25 to 15:02 on 28 July (i.e. 15:25 to 16:02 Local) 15:02 - there's precision for you.
There have been occaisons when users have entered the date in the wrong (i.e. non-ICAO) format, e.g. entering 050706 thinking that's 5 July 2006 when in ICAO speak it's 6 July 2005 or of course mixing UTC and Local.
If you drop an email to
[email protected] with either the R number described above or the date and approx time you took the brief, together with your login details they'll dig it out and find out what went wrong. Far better to find out the reason than for an incident ot occur on some future date.
(Incidentally that's one of the reasons for login being required)
Mike