Narrative:

This is a comment in response to callback #212. There is a story of a pilot who missed a NOTAM for a temporary restr area in a duat briefing. Most likely, this was a flight data center NOTAM. Most pilots (myself included) view flight data center NOTAMS as only pertaining to IFR flight and do not bother to check them for a VFR flight in good WX. Who wants to slog through many pages of airway and approach amendments every time? I believe safety would be improved if temporary flight restrs got moved out of the fdc NOTAMS and put in with the regular NOTAMS. At the very least, put in a local NOTAM referring the user to the flight data center section. Example: !hpn 01/001 NY99 tfr see fdc-xx/XXX for details. This would improve the visibility of these important NOTAMS many times.

Google
 

Original NASA ASRS Text

Title: PLT RPTR SUGGESTS THAT FLT DATA CTR NOTAMS WITH TEMPORARY RESTRS SHOULD BE MORE AVAILABLE FOR PLTS WHO ARE PLANNING VFR FLTS. TEMPORARY FLT RESTRS SHOULD BE PUT IN REGULAR NOTAMS INSTEAD OF FDC NOTAMS.

Narrative: THIS IS A COMMENT IN RESPONSE TO CALLBACK #212. THERE IS A STORY OF A PLT WHO MISSED A NOTAM FOR A TEMPORARY RESTR AREA IN A DUAT BRIEFING. MOST LIKELY, THIS WAS A FLT DATA CTR NOTAM. MOST PLTS (MYSELF INCLUDED) VIEW FLT DATA CTR NOTAMS AS ONLY PERTAINING TO IFR FLT AND DO NOT BOTHER TO CHK THEM FOR A VFR FLT IN GOOD WX. WHO WANTS TO SLOG THROUGH MANY PAGES OF AIRWAY AND APCH AMENDMENTS EVERY TIME? I BELIEVE SAFETY WOULD BE IMPROVED IF TEMPORARY FLT RESTRS GOT MOVED OUT OF THE FDC NOTAMS AND PUT IN WITH THE REGULAR NOTAMS. AT THE VERY LEAST, PUT IN A LCL NOTAM REFERRING THE USER TO THE FLT DATA CTR SECTION. EXAMPLE: !HPN 01/001 NY99 TFR SEE FDC-XX/XXX FOR DETAILS. THIS WOULD IMPROVE THE VISIBILITY OF THESE IMPORTANT NOTAMS MANY TIMES.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.