<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>NAS Daily Logs - The Black Vault</title>
	<atom:link href="https://www.theblackvault.com/documentarchive/tag/nas-daily-logs/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.theblackvault.com/documentarchive</link>
	<description>Discover the Truth</description>
	<lastBuildDate>Sun, 29 Nov 2015 18:39:08 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://www.theblackvault.com/documentarchive/wp-content/uploads/2020/06/cropped-siteicon-2-150x150.jpg</url>
	<title>NAS Daily Logs - The Black Vault</title>
	<link>https://www.theblackvault.com/documentarchive</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">87123917</site>	<item>
		<title>Federal Aviation Administration (FAA) NAS Daily Event Logs</title>
		<link>https://www.theblackvault.com/documentarchive/federal-aviation-administration-faa-nas-daily-event-logs/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=federal-aviation-administration-faa-nas-daily-event-logs</link>
		
		<dc:creator><![CDATA[John Greenewald]]></dc:creator>
		<pubDate>Sun, 29 Nov 2015 18:38:03 +0000</pubDate>
				<category><![CDATA[Military / Defense]]></category>
		<category><![CDATA[Military and Commercial Accidents]]></category>
		<category><![CDATA[aviation]]></category>
		<category><![CDATA[Commercial]]></category>
		<category><![CDATA[FAA]]></category>
		<category><![CDATA[NAS Daily Logs]]></category>
		<guid isPermaLink="false">http://www.theblackvault.com/documentarchive/?p=1997</guid>

					<description><![CDATA[<p>Recently, I was contacted about some very important documents that exist within the FAA holdings, referred to as the NAS Daily Event Logs. The FAA NAS Daily Events Log, prepared each day by the Federal Aviation Administration, provides a unique window into the odd and unusual events that occur within the National Airspace System. &#160; The FAA [...]</p>
<p>The post <a href="https://www.theblackvault.com/documentarchive/federal-aviation-administration-faa-nas-daily-event-logs/">Federal Aviation Administration (FAA) NAS Daily Event Logs</a> first appeared on <a href="https://www.theblackvault.com/documentarchive">The Black Vault</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>Recently, I was contacted about some very important documents that exist within the FAA holdings, referred to as the NAS Daily Event Logs.</p>
<blockquote><p><strong><em>The FAA NAS Daily Events Log, prepared each day by the Federal Aviation Administration, provides a unique window into the odd and unusual events </em></strong><strong><em>that occur within the National Airspace System.</em></strong></p>
<p>&nbsp;</p>
<p><strong><em>The FAA Air Traffic Organization &#8211; office of System Operations Services prepares this document daily, comprising between five and ten pages per </em></strong><strong><em>day, a wealth of information that include reportable events such as:</em></strong></p>
<p>&nbsp;</p>
<ul>
<li><strong><em>Lost communications with aircraft, called NORDO ¬ no radio aircraft;</em></strong><br />
<strong><em>emergency beacon code 7600;</em></strong></li>
<li><strong><em>Displaying or requesting unusual deviations from assigned routing;</em></strong></li>
<li><strong><em>Change of destination while on an IFR flight plan &#8211; COD;</em></strong></li>
<li><strong><em>Security Incidents ¬ terminal evacuation, bomb threats, breach of airport</em></strong><br />
<strong><em>perimeter, airport closure, airport security;</em></strong></li>
<li><strong><em>Emergencies ¬ aircraft displaying emergency beacon code 7700 or reporting an</em></strong><br />
<strong><em>emergency;</em></strong></li>
<li><strong><em>Hijack ¬ aircraft displaying emergency beacon code 7500 or reporting a</em></strong><br />
<strong><em>hijack;</em></strong></li>
<li><strong><em>Aircraft experiencing a disturbance either on the ground or in flight;</em></strong></li>
<li><strong><em>Special Interest Flights ¬ overflights by aircraft from certain nations;</em></strong></li>
<li><strong><em>Special Penetration Air Defense Exercise ¬ SPADE:</em></strong></li>
<li><strong><em>VIP movements;</em></strong></li>
<li><strong><em>Special Speed Authorizations;</em></strong></li>
<li><strong><em>Mechanical Problems;</em></strong></li>
<li><strong><em>Laser Incidents;</em></strong></li>
<li><strong><em>Intrusions into the National Capitol Region Control Center ¬ NCRCC</em></strong></li>
<li><strong><em>And so on.</em></strong></li>
</ul>
<p>&nbsp;</p>
<p><strong><em>The number of incidents each day is large.</em></strong></p>
<p>&nbsp;</p>
<p><strong><em>The NAS Daily Events Log covers the entire nation. Events are not separated  out geographically.</em></strong></p></blockquote>
<p>Back in 2013, I began requesting these logs, and it was not until September of 2015 that my requests began being answered.</p>
<p>Below, you will find the available logs, thus far.</p>
<h3>Declassified NAS Daily Logs</h3>
<p><img decoding="async" src="https://www.theblackvault.com/images/pdf.gif" alt="" /> <a href="https://documents.theblackvault.com/documents/faa/FOIA2013-006320.pdf">January 1, 2013 &#8211; January 31, 2013</a> [192 Pages, 56.2MB]</p><p>The post <a href="https://www.theblackvault.com/documentarchive/federal-aviation-administration-faa-nas-daily-event-logs/">Federal Aviation Administration (FAA) NAS Daily Event Logs</a> first appeared on <a href="https://www.theblackvault.com/documentarchive">The Black Vault</a>.</p>]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1997</post-id>	</item>
	</channel>
</rss>
