<rss version="2.0" xmlns:atom="https://www.w3.org/2005/Atom">
  <channel>
    <title>Transport Research International Documentation (TRID)</title>
    <link>https://trid.trb.org/</link>
    <atom:link href="https://trid.trb.org/Record/RSS?s=PHNlYXJjaD48cGFyYW1zPjxwYXJhbSBuYW1lPSJkYXRlaW4iIHZhbHVlPSJhbGwiIC8+PHBhcmFtIG5hbWU9InN1YmplY3Rsb2dpYyIgdmFsdWU9Im9yIiAvPjxwYXJhbSBuYW1lPSJ0ZXJtc2xvZ2ljIiB2YWx1ZT0ib3IiIC8+PHBhcmFtIG5hbWU9ImxvY2F0aW9uIiB2YWx1ZT0iMCIgLz48L3BhcmFtcz48ZmlsdGVycz48ZmlsdGVyIGZpZWxkPSJpbmRleHRlcm1zIiB2YWx1ZT0iJnF1b3Q7TWV0ZW9yb2xvZ2ljYWwgV2F0Y2ggT2ZmaWNlcyZxdW90OyIgb3JpZ2luYWxfdmFsdWU9IiZxdW90O01ldGVvcm9sb2dpY2FsIFdhdGNoIE9mZmljZXMmcXVvdDsiIC8+PC9maWx0ZXJzPjxyYW5nZXMgLz48c29ydHM+PHNvcnQgZmllbGQ9InB1Ymxpc2hlZCIgb3JkZXI9ImRlc2MiIC8+PC9zb3J0cz48cGVyc2lzdHM+PHBlcnNpc3QgbmFtZT0icmFuZ2V0eXBlIiB2YWx1ZT0icHVibGlzaGVkZGF0ZSIgLz48L3BlcnNpc3RzPjwvc2VhcmNoPg==" rel="self" type="application/rss+xml" />
    <description></description>
    <language>en-us</language>
    <copyright>Copyright © 2026. National Academy of Sciences. All rights reserved.</copyright>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <managingEditor>tris-trb@nas.edu (Bill McLeod)</managingEditor>
    <webMaster>tris-trb@nas.edu (Bill McLeod)</webMaster>
    <image>
      <title>Transport Research International Documentation (TRID)</title>
      <url>https://trid.trb.org/Images/PageHeader-wTitle.jpg</url>
      <link>https://trid.trb.org/</link>
    </image>
    <item>
      <title>First 8 Hours of Volcanic Eruptions: A Northwest Airlines Example &amp; Recommendations of Revised Flow of Ash Information for Aviation</title>
      <link>https://trid.trb.org/View/757372</link>
      <description><![CDATA[This paper describes the conceptual framework and existing protocol for improving or streamlining the standardization of information and data exchange between Volcano Observatories, Volcanic Ash Advisory Centers and Meteorological Watch Offices.  These organizations all deal with disseminating hazard and advisory information to the aviation community regarding airborne volcanic ash and volcanic eruptions.  There are currently 5 steps involved in notifying aircraft pilots and dispatchers about volcanic eruptions and volcanic ash.  Time is crucial in getting the hazard warnings out, and interorganizational relations and coordination need to be tight and trusting.  The paper bases its information on a Northwest Airlines experience and also on the deficiencies noted in the standardization and information dissemination system.]]></description>
      <pubDate>Thu, 07 Jul 2005 08:28:52 GMT</pubDate>
      <guid>https://trid.trb.org/View/757372</guid>
    </item>
    <item>
      <title>NOAA's NWS Volcanic Ash Program: Current Status and Plans for the Future</title>
      <link>https://trid.trb.org/View/756688</link>
      <description><![CDATA[The National Oceanic and Atmospheric Administration (NOAA) operates four Meteorological Watch Offices (MWO) and two of the world's nine Volcanic Ash Advisory Centres (VAACs), and as such, plays an important role in the worldwide volcanic ash network.  The International Civil Aviation Organization (ICAO) defines the operational responsibilities of the two VAACs.  The National Weather Service's (NWS) Alaska Aviation Weather Unit manages the Anchorage VAAC.  The NWS's National Centers for Environmental Prediction (NCEP), the National Environmental Satellite, and the Data and Information Service (NESDIS) Satellite Analysis Branch jointly manage the Washington VAAC.  All of these centers together are responsible for providing ash dispersion forecasts and volcanic ash advisories for an area that ranges widely from the Pacific Ocean eastward over the United States and much of the Atlantic Ocean.  This presentation explores NOAA's Volcanic Ash Program.  It discusses future plans and the current status in the areas of research and development, operations, and policy development.]]></description>
      <pubDate>Mon, 20 Jun 2005 09:44:15 GMT</pubDate>
      <guid>https://trid.trb.org/View/756688</guid>
    </item>
  </channel>
</rss>